??? 12/06/09 17:15 Read: times |
#171488 - Another idea... Responding to: ???'s previous message |
Hi Akhil,
first, there's no need to do this by the help of interrupts. You can also manage it by periodically polling the corresponding port lines. More, I don't think, that multiple pressings of the "mode" button is a good idea. Operators tend to press the buttons too fast later, which will result in trouble. Why not changing the mode by keeping the "mode" button pressed and simultaneously pressing the "up" and "down" buttons to select the "A", "B" or "C" first? You can have three LEDs then, one for "A", one for "B" and one for "C". Keeping the "mode" button pressed and pressing the "up" and "down" buttons makes one LED after the other turning on and by this showing you which of "A", "B" or "C" is selected. Kai Klaas |
Topic | Author | Date |
one key, multiple jobs assigned to it | 01/01/70 00:00 | |
Step by step | 01/01/70 00:00 | |
What methods do you have for keeping track of time now? | 01/01/70 00:00 | |
Timing in Siemens ;)? | 01/01/70 00:00 | |
RC circuit | 01/01/70 00:00 | |
Yep, touché!... | 01/01/70 00:00 | |
Another idea... | 01/01/70 00:00 | |
State machine | 01/01/70 00:00 | |
State Transition Diagram | 01/01/70 00:00 | |
Timers can help!! | 01/01/70 00:00 | |
In theory, zero timers are needed | 01/01/70 00:00 | |
"I do not have any timer interrupts left." | 01/01/70 00:00 | |
Software timers | 01/01/70 00:00 | |
To check debounce | 01/01/70 00:00 | |
what happens when![]() | 01/01/70 00:00 |