Non-blocking issue about stepperdriver HOT 6 CLOSED

What I would really like to do is use interrupts for the timing, which would make the entire motor activity async, but I didn't have time to look into that and there are other libraries which do this better.

from stepperdriver.

Try taking a look at the AccelStepper library, it has been around for a longer time.
With interrupts, maintaining the functionality across different chips becomes an issue.

from stepperdriver.

The non-blocking implementation has three phases. First you do startMove() which precalculates the timings and sets up the step counters, then you call nextAction() periodically at the indicated intervals to trigger the pulses. Each call returns how many milliseconds you have until the next move, and you can use that to decide if you have enough time to do something else.

You do not need to call stop() unless you want to cancel the move, because it will reset all the step counters to zero. If you take too long between nextAction() calls, the timing of the pulses will be off, the motor movement will be less smooth but that's about it.

If you do need a lot of time while the motor is moving, I am thinking that you could try to use fewer microsteps to increase the step interval.

from stepperdriver.

Closing, assumed resolved.

from stepperdriver.

Has anyone found a good solution to this problem? I am using ESP32 AsyncWebServer and when the motor is moving it freezes and jerks for a second when requests are made. Is there another library that someone has found that uses interrupts?

from stepperdriver.

Thank you very much @laurb9. I'll check it out.

from stepperdriver.