gin66

From the datasheet the Seeduino Xiao could drive three steppers: _Three 24-bit Timer/Counters for Control (TCC), with extended functions: • Up to four compare channels with optional complementary output •...

The code uses this formula to calculate from steps to the required speed: ``` v = sqrt(2 * s * a) ``` On call to `getNextCommand()`, the code is currently...

On deceleration, the ramp steps are counted down. Means the relation for the next point sy is ``` sy = sx - planning_steps ```

2ms = 0.002 seconds ?!

no special reason. Actually could have chosen 1ms or 3ms. For avr this makes a difference, because the manageSteppers() task per stepper is pretty slow. Driving three steppers at full...

if the stepper shall run forward and backward, then a direction pin is required. The direction pin can be controlled by the application by any means (e.g. shift register or...

You are right. It should be `engine.setExternalCallForPin(exampleCallback);` Your example callback looks good.

cool. The implementation was just missing. Having no test for a feature opens the door for failure… Fix has been pushed to master. But still no test….

attachToPulseCounter just gives access to real-time data instead of calling a lengthy API function. It is great for verifying having no pulse losses during development for esp32 So I wait...

Pity. So the implementation is faulty and I need to debug it. Hopefully I can do it over the weekend.