| ??? 03/30/10 00:09 Read: times |
#174613 - What about the others? Responding to: ???'s previous message |
I've found few switches that settle that quickly. Moreover, I've found few manufacturers that will claim that they do.
20 to 50 ms seems to be more reasonable, depending on the switch type. What's found in keyboards/keypads, generally, is a much more uniform switch than what one sees in the typical pushbutton. It's a cost thing, I guess. So you figure there's something wrong with the way IBM decided to do it, encoding, I mean? It seems to work OK in my keyboards, and those attached to nearly a billion other computers. RE |
| Topic | Author | Date |
| switch input > interrupt (debouncing) | 01/01/70 00:00 | |
| double post | 01/01/70 00:00 | |
| Why the extra hardware? | 01/01/70 00:00 | |
| wow | 01/01/70 00:00 | |
| other ISR recommendation | 01/01/70 00:00 | |
| or the other solution (my favorite) | 01/01/70 00:00 | |
| using timer | 01/01/70 00:00 | |
| Some switches have very long bounce time | 01/01/70 00:00 | |
| a lot depends on the switches themselves | 01/01/70 00:00 | |
| which is a $#@!! disaster | 01/01/70 00:00 | |
| Remember that there is more than push buttons out there | 01/01/70 00:00 | |
| What about the others? | 01/01/70 00:00 | |
| Majority of implementations synchronizes with key down | 01/01/70 00:00 | |
| Now I'm confused ... | 01/01/70 00:00 | |
| Not Sure About The Code | 01/01/70 00:00 | |
More info on PC keyboard | 01/01/70 00:00 | |
| Short spikes | 01/01/70 00:00 | |
| The real problem with debouncing | 01/01/70 00:00 |