Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dead spot at max and min boundaries when wrap set to false #5

Open
Cat30Mk3 opened this issue Feb 23, 2024 · 1 comment
Open

dead spot at max and min boundaries when wrap set to false #5

Cat30Mk3 opened this issue Feb 23, 2024 · 1 comment

Comments

@Cat30Mk3
Copy link

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.

@Cat30Mk3
Copy link
Author

Cat30Mk3 commented Feb 23, 2024

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

@cwkowalski
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants