Closed sharpie7 closed 2 weeks ago
Thanks for open a new issue. The #262 was already quite long. I assume, you are using the latest FastAccelStepper v0.30.15 with the getCurrentSpeedInTicks()
-bugfix ? Could you please check ?
Thanks. For some reason, Github is still showing me the latest version in master as 0.30.14.
Edit: I don't see the fix in the issue branch either. Do you need to do a push?
Refresh didn't work, but your link did.
With 0.30.15 I see no problems any more.
Thanks for quick bug-fix. I know from experience that maintenance is hard and this library does very well!
As mentioned in the previous issue, I am detecting a different issue with deceleration that occurs from speeds around 2000 steps/s. I used your issue 262 test program with the minSpeed and maxSpeed changed and ran it for about 8 hours on an ATMEGA168.
Output is:
The same error sequence occured six times in the period I tested. The target values that caused the problem were either 1978 or 1979. I don't believe it occurs every time those values are used, but only sometimes.
Edit: the values reported in the
Speed errors
were 1978972 or 1977992.Test program: