Teensy 4.1 not delivering correct pulses

[johnruehlz]

I compiled GRBLHAL from the web builder for Teensy 4.1 for an T41U5XBB and I am undershooting my target consistently, shorter distances are worse than farther distances. For instance, moving 5mm which should be one rotation may only rotate 1/4 turn. Moving 100mm may turn 19.5 turns instead of 20. I tried my old arduino grbl controller with the same settings and it ran perfectly.

I built a pulse counter using an arduino to count to the Teensy pulses and it was consistently less then required pulses. (IE 2000pulse/mm only returns 1990 pulses) Then I would recalculate the settings and adjust and the pulses would still not consistently reach 2000 pulses. It would get close but if I performed the same action 5 times it would may reach 2000 pulses once.

[terjeio]

I am not able to check this until I am back home at the end of the month.
There was a fix for incorrect step timing recently and this was verified by the user so odd that it does not work for you.

[johnruehlz]

I was able to figure out the issue, it seems that 1. I was reading the pulses poorly and they were correct. 2. It seems when the enable signal to the driver is occurring after the pulses begin, the issue was remedied by turning the stepper enable to always on.

[dresco]

If it's any help, there is also setting $680 for inserting an additional delay between the enable signal and the first output.

I have some integrated closed loop steppers that need extra time between enable and input signals, but fwiw I just run with steppers always enabled also..