-
Notifications
You must be signed in to change notification settings - Fork 72
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
Default Low/High on startup #100
Comments
It's more complicated that that. The ability to enable reporting of individual digital pins needs to be added first, which is a big change from how Firmata has historically worked so it will not land until Firmata 3.0, which has no definite schedule. |
My advice is if you are controlling potentially dangerous equipment, is not to use Firmata, but to design a simple protocol that will meet your needs while giving you full control over the code running on your Arduino. |
I understand.
I recommend to copy this few lines to : And firmatabuilder should have an extra checkbox to enable it too. That would be already a HUGE help to us, beginners. < OFF > My personal opinion is, that currently Firmata is more stable than any other "ad-hock" created serial service. |
Is it possible to define a global variable (or activate any hidden feature) to: force all pins to work in INVERTED mode?Where Something like: #define ENABLE_INVERT_MODE |
No, there's currently no such option. However, the startup values are directly in the ino file and can easily be changed there. |
Rather than waiting, |
I think it would make life easier for beginner {like me ;-) } if the firmatabuilder would "ask about" the default settings of output pins.
Temporary I'll try to use the method mentioned here: #firmata/arduino#166 (comment)
but it can have serious consequences if predefined to a different state as it should be when the board starts.
< OFF >
For example:
I'm building currently a 8+8 relay-board roller-shutter system.
Those 230V tube-motors are very strong and those heavy metallic things can basically cut off a child's head...
< /OFF >
The text was updated successfully, but these errors were encountered: