Timeline for Where to place debouncing circuit for remote mounted buttons and rotary encoders
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 27, 2015 at 14:21 | vote | accept | GisMofx | ||
| Jul 29, 2015 at 14:05 | comment | added | GisMofx | I need to see how that will affect my code. Each states' main loop will need to have the polling routine added. Maybe I need to create separate a polling thread. Although, the current interrupt driven inputs do work with the system. | |
| Jul 29, 2015 at 14:00 | comment | added | Spehro 'speff' Pefhany | I suggest using polling at < 1kHz, not interrupts. Your events would be the de-bounced changes from the (timer interrupt-driven) polling routine. | |
| Jul 29, 2015 at 13:55 | comment | added | GisMofx | My device uses an event driven state machine and the button and rotary encoder are using interrupts. I'm using the "debounce" circuit suggested from the datasheet-I added it to my question. | |
| Jul 29, 2015 at 13:47 | comment | added | Spehro 'speff' Pefhany | Then, no worries. But do worry about ESD from fingers etc. Also RC is not a debouncing circuit unless it is combined with a Schmitt trigger input. RC may be used for other reasons (filtering and ESD) but debounce is easy and good in firmware. If it requires external debouncing you may be doing something wrong (like using port change interrupts rather than polling). | |
| Jul 29, 2015 at 13:45 | comment | added | GisMofx | The encoder is the mechanical type. | |
| Jul 29, 2015 at 12:57 | history | edited | Spehro 'speff' Pefhany | CC BY-SA 3.0 |
added 213 characters in body
|
| Jul 29, 2015 at 12:51 | history | answered | Spehro 'speff' Pefhany | CC BY-SA 3.0 |