| ??? 12/06/09 16:58 Modified: 12/06/09 17:05 Read: times |
#171487 - Step by step Responding to: ???'s previous message |
Hi Akhil,
For this task, for example: 1.- Implement a function that return the code (any you like) of the key pressed. Include debounce and possibility of one or more key pressed simultaneously. 2.- Use this value to make decisions: - give some maximum/minimum time for repetitions of MODE key - incremente A, B or C - and so on Probably you will need some counter for timing (10mS for example?) Once you implement some code, came again with the specific difficulties you find, and many professionals of this forum will be glad of helping you. Daniel |
| 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 |