Quote: Originally Posted by
h3rk 
Right on!
Quote: Originally Posted by
h3rk If the 'tied' output turns on with one press. The timer would cause it to turn off after set time. Possible use would be an actuator. It would prevent someone from having to use limit switches on their rocker-panel rocket launchers.
Already done!
Quote: Originally Posted by
h3rk All of my ideas can't be top-notch, but I have my moments. But I think you may know I'm not advertising all of them...yet. But you get to the good ones by blurting out all of the bad ones and getting them outta the way.
Keep them coming!
Quote: Originally Posted by
P3D4T0R Sweet... Thank you.
I was wondering for the outputs if there could be a "save state" and/or "default state" option. What I mean is when the computer is powered off the board will keep whatever state it was in but also be able to return to its default state if wanted. I dont know if that made sense, if it didn't ill fix it later.
Quote: Originally Posted by
h3rk I like that idea. The each output could have two attributes like:
.state.default=1
.state.last=0
done.
Not the last state, but default state is saved as can be referred to by pushing the big 'ol default button on the screen. It is also the state that is loaded when the app starts. So if you want your lights on when the board comes on, but not your 3gillion dB bullhorn, you can set that.
Quote: Originally Posted by
greenman100 Already implemented.
You beat me to it!
