Timeline for ISR not working as it is supposed to
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 12, 2015 at 21:34 | comment | added | James Waldby - jwpat7 |
The PinChangeInt library checking pin values is one thing that makes it slow; I used it a few months ago but found it too slow, so used ISR()'s instead. ... At the hardware level, PCI doesn't distinguish rising/falling, merely detects changes. ... I didn't imply "multiple functions in the ISR", but instead reading a pin and branching to one section of the ISR or another depending on its value. Thanks for the comment!
|
|
| Nov 12, 2015 at 9:38 | comment | added | frarugi87 | 1 applies (partly) to standard interrupt handling. The OP is using a library that handles the pinchange events checking the pin values. Your sentence, however, is wrong, since the arduino interrupt handling does not allow for multiple functions in the ISR, so if you attach both rising and falling you won't be able to use the former you attached | |
| Nov 12, 2015 at 5:50 | history | edited | James Waldby - jwpat7 | CC BY-SA 3.0 |
added 5 characters in body
|
| Nov 12, 2015 at 5:34 | history | edited | James Waldby - jwpat7 | CC BY-SA 3.0 |
re sample and hold vs cycle time
|
| Nov 12, 2015 at 1:02 | history | answered | James Waldby - jwpat7 | CC BY-SA 3.0 |