| ??? 03/23/10 19:33 Read: times |
#174446 - The real problem with debouncing Responding to: ???'s previous message |
In software anyway is it ties up timers and its rarely done properly and its a pain because you are dealling with asyncronous signals which is why i tend to use seperate hardware either the max single input or 8 input jobbies or my own debouncer if I am using a CPLD the code for which you will find in the code library. |
| 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 |