| ??? 03/23/10 16:48 Read: times |
#174435 - using timer Responding to: ???'s previous message |
thats also an idea i thought of immediately after the previous suggestion, but I would really like to cut out the [(debounce time + myfudge)*2] seconds before calling the function, it is not a 'time critical' application, i.e other events success depend on it being quick, but it is certainly desirable to cut out say (at worst)
[5000us+500us]*2 so 11000us actually, this is still so tiny, and still a worse case debounce time (i havent measured the switches debounce time yet as they havent arrived) i may do this erik, thank you to both of you. |
| 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 |