Timeline for Weird behaviour of rotary encoder values
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 7, 2017 at 17:19 | vote | accept | Norman | ||
| Aug 7, 2017 at 17:19 | answer | added | Norman | timeline score: 1 | |
| Aug 2, 2017 at 22:47 | comment | added | dandavis |
no, it means you need to check not just that the gpios are different, but that they are 0 (or 1) and have changed, but not the other. something like if (digitalRead(outputB) != aState && aState==1)
|
|
| Aug 2, 2017 at 15:38 | comment | added | Norman | @dandavis Does it mean that the encoder is broken? | |
| Aug 1, 2017 at 17:09 | comment | added | dandavis | most rotary handler only fire on the leading or trailing edge, you fire on both... | |
| Jul 30, 2017 at 18:41 | review | First posts | |||
| Jul 30, 2017 at 19:43 | |||||
| Jul 30, 2017 at 18:36 | history | asked | Norman | CC BY-SA 3.0 |