-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AutomationShield Hardware Style Guide #19
Comments
Pot:
https://www.tme.eu/sk/details/ca9mv-10k/potenciometre-jednootackove-tht/acp/ca9mv-10k/ Shaft e.g. https://www.tme.eu/sk/details/ca9ma5-b/gombiky-pre-montazne-potenciometre/acp/ca9ma-9005-black/ |
Change the positioning and size for the pin labels on the shields. The headers tend to obscure them for reading. |
Take care of shorting to ground by placing components over the USB connector of the Arduino. FloatShield made this mistake, do not repeat it. |
This sticky issue and the post summarizes some hardware design practices for the AutomationShield devices. The current list is quite randomly organized, make sure you read it all. Please comment any other ideas that are generically valid.
Creed
The creed of an AutomationShield hardware device are, that it shall be
Generic notes
Programming Port
when using the device. No applications for theNative Port
.3.3V Compatibility
Make the shield 3.3 V compatible at all cost: New shields and updates to old shields (especially those with fast dynamics) should be made 3.3 V compatible. Here are some concepts to consider:
AREF
pin doesn't change anything, device still takes internal reference though. This has been tested on the Zero / Due / Uno without issues.The text was updated successfully, but these errors were encountered: