Reading Step/Dir inputs about esp32encoder HOT 4 CLOSED

Sure, not a bad idea at all. There are a few different modes in the lib, it would be fairly straight forward for you to add a new mode and submit a Pull Request.

from esp32encoder.

I have tried the different modes and had some success with single edge. I also tried tweaking the library without much luck. A lot of your coding is outside of my current limited understanding of assumed low level higher efficiency and/or esp specific. I spend most of my time with higher level code without as good of a grasp of the nuts and bolts that make it work so well.

Side note, looking around, I have not found a description of how the different encoder modes count or any limitations with specific GPIO pins. Do you have that posted somewhere?

Thanks again!

from esp32encoder.

It looks like using the mode attachSingleEdge(aPin, bPin) is doing the trick. Steps to aPin and Direction to bPin.

Looking over the library and with testing, I think single edge only counts the rising edge of aPin (steps) and increments the count per state of bPin. Is that correct, or is there some extra increments bouncing back and forth that I am missing?

With my bench tests and debounce timing settings in the library, high speed stepping appears limited. My application is pretty slow, but others may not be able to make use. I also have had some erratic loss of observed steps, but that probably is loose jumper wires/breadboard on my test or the lacking MCU/stepper library I was initially using to simulate steps.

from esp32encoder.

Sounds like this is resolved then :)

from esp32encoder.