| ??? 08/29/06 15:12 Read: times |
#123329 - Ok, why not do this Responding to: ???'s previous message |
debounce becomes a breeze if you handle all keypad processing in a timer interrupt. Then just disable the timer interrupt during LCD operations and no conflict will ever happen.
the disable will, at the worst make the debounce time a bit longet. Erik PS in that scheme, you need separate the 'calculation' of the display and the actual writing to the display or the disable time may become prohibitive. |
| Topic | Author | Date |
| Detect Key is held down | 01/01/70 00:00 | |
| Like a Debounce...? | 01/01/70 00:00 | |
| Key held down | 01/01/70 00:00 | |
| Holly Bad Ideas Batman!! | 01/01/70 00:00 | |
| Remember the old CMOS setup for PC's? | 01/01/70 00:00 | |
| (a bit of) the schematic would be helpful | 01/01/70 00:00 | |
| Schematic | 01/01/70 00:00 | |
| No | 01/01/70 00:00 | |
| Schematic | 01/01/70 00:00 | |
| Ok, why not do this | 01/01/70 00:00 | |
| I'll try | 01/01/70 00:00 | |
| Schematic | 01/01/70 00:00 | |
| "Typo" | 01/01/70 00:00 | |
| Aside: Block comments | 01/01/70 00:00 | |
| is that true? | 01/01/70 00:00 | |
| Yes | 01/01/70 00:00 | |
| Thank you | 01/01/70 00:00 | |
| an element of style | 01/01/70 00:00 | |
I'd not | 01/01/70 00:00 |