You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using your example "BasicRotaryEncoder.ino", with wrap set to false, when counter reaches max or min boundary, the first step in opposite direction does not generate an interrupt. This applies to both max and min boundaries.
The text was updated successfully, but these errors were encountered:
Hi Mathew, I just discovered your "LeftOrRight.ino" example, and confirmed it presents the same issue:
stepping the encoder clockwise functions correctly, (continuously raising interrupts and reporting "Right ->") but the first step counterclockwise IS LOST EVERY TIME. Then, as I continue counterclockwise it functions correctly raising interrupts and reporting "<- Left". Then the first step clockwise IS LOST EVERY TIME. I'm using a basic encoder without VCC pin, and an ESP32-WROOM-32E. EncoderType::FLOATING
I just setup this library to test an EC11J rotary encoder (a 5-pin with a switch) on an ESP32-S3. I have a similar, but not identical issue-- it only counts every other rotation of the encoder. Otherwise, it's a brilliantly easy and lightweight library. Perhaps this is because of the encoder type, I'll investigate further.
Using your example "BasicRotaryEncoder.ino", with wrap set to false, when counter reaches max or min boundary, the first step in opposite direction does not generate an interrupt. This applies to both max and min boundaries.
The text was updated successfully, but these errors were encountered: