Go Down

Topic: Program run switch (Read 2 times) previous topic - next topic


Well, when making a prototype board such as the Arduino.. you gotta realize they're thinking more of a "general" population when they implement pins, buttons.. etc..

Doesn't seem like what you're trying to explain would have a whole lot of uses.. but then again, it's not very clear what you're explaining!

From the sounds of it.. couldn't this all be done on the Software side?

Only running the program after a button is pushed.. then another button push to turn it off?

I'm sorry if this isn't the right idea.. just confused on what you're explaining:D


Yes exactly except in a switch, the only change im suggesting is that a smd or dip switch be mounted  on the side (can access it with shield on) connected to ground with pulldown resistor 5v and a io pin.


you don't get it....

for prototyping it is way easier to have something built in.
you probably haven't experienced it to the fullest...
i need to wait till someone who knows what im talking about to reply

Way to get added to my "do not help list"!

You can't have a "one-design-fits-all" as a prototyping board - it's not practical cost-wise or size-wise. Compromises are always made.


Actually a built in push-button might not be a bad idea. After all, we have a built in LED on pin 13 for output, why not a built in button on pin 12 for input? It would mean people could run something a little more interesting than Blink without any external hardware at all.



If your just connecting directly to the pins its usefull to have a switch, for running the program, or somthing else. EVEN THE SPARKFUN PROTOSHIELD HAS ONE

Go Up