Timeline for Interrupt on button press + debouncing
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 18, 2022 at 23:06 | vote | accept | user1584421 | ||
| Dec 17, 2022 at 3:37 | answer | added | DrG | timeline score: 0 | |
| Dec 14, 2022 at 16:02 | answer | added | 6v6gt | timeline score: 2 | |
| Dec 13, 2022 at 15:23 | history | edited | user1584421 | CC BY-SA 4.0 | added 2 characters in body |
| Dec 13, 2022 at 9:14 | comment | added | user1584421 | @jsotola Thanks! You are right, I edited the question. | |
| Dec 13, 2022 at 9:14 | history | edited | user1584421 | CC BY-SA 4.0 | added 58 characters in body |
| Dec 13, 2022 at 7:12 | answer | added | the busybee | timeline score: 1 | |
| Dec 13, 2022 at 5:03 | comment | added | 6v6gt | I'd probably take a simpler approach. If the ISR is triggered, accept that and toggle the led then set a timer, as you have already done (lastDebounceTime). Use the timer to prevent subsequent calls of the ISR having any effect. When the timer expires (after 50ms) the ISR again behaves normally. An interrupt is, however, not usually the best way for handling a button and simply polling it every X ms is usually enough. | |
| Dec 13, 2022 at 0:32 | history | asked | user1584421 | CC BY-SA 4.0 |