Change in speed behavior from v0.33.5 and v0.33.6

[robeastwood]

I'm using an ESP32 and I have noticed a change in behavior going from 0.33.5, when updated to 0.33.6 the maximum speed seems to be limited.

Is this an intentional change? I couldn't see anything mentioned in the changelog but I can see in the diff that there are some modifications around SUPPORT_UNSAFE_ABS_SPEED_LIMIT_SETTING etc. I am not familar enough to follow what exactly the outcome of this is.

Is there any guidance on this speed limit and how it might be increased/allowed for?

[gin66]

Sorry for the inconvenience. It is fixed in 0.33.7

[robeastwood]

Sorry, but no I don't think it is. 0.33.7 still has the same speed limit

[gin66]

Could you please make sure, that there is no cached version. #335 has mentioned the same issue and my hw test on esp32 confirmed successful fix with 0.33.7

[robeastwood]

Yes, I have flipped between versions:
0.33.5 (works ok)
0.33.6 (speed limited)
0.33.7 (speed limited)
I've been clearing and re-downloading & compiling multiple times over many hours last night in the process of trying to find out why the heck my project was doing something different now after build, even with the same codebase. Until i reaslised it was the library version.

There's definitely something up with it that's still apparent in 0.33.7 as far as I can tell.

[gin66]

I have checked on my hardware again and it works. Or at least I cannot reproduce the issue.
Do you have more details from your setup? Eventually small test code ?

[robeastwood]

Hmm. Ok thanks for checking yours. Odd, not sure how it would be unique to my setup but I'll see if i can extract a basic example out of it. The difference is quite significant, I filmed a quick video on a test rig. This is the exact same code, same parameters - the only change is the library version: https://photos.app.goo.gl/ZapnuVZNs4Q1NqsS7

[gin66]

Thanks for sharing the video. Looks nice and the effect is clear. Still there is no more info, which helps to identify the root cause.

Anyway, there is an additional difference between 0.33.5 and 0.33.6/7, which will show up only in the following case:

1. Stepper 1 is allocated
2. setAbsoluteSpeedLimit() is called to set the speed limit
3. Another stepper is allocated

V0.33.5 will overwrite at step 3 the setAbsoluteSpeedLimit() value, while 0.33.6/7 will not. Same would be valid if the memory storing the absolute speed limit (max_speed_in_ticks) gets corrupted somehow.

Is in your application setAbsoluteSpeedLimit() in use and will there be more steppers allocated afterwards ?

[robeastwood]

Last night I tried to extract the code to a bare-minimum example, but it did not show the same problem. So the version incompatability issue must be quite deeply buried inside my usage.
I am using setSpeedInHz to control the speed. I have not used setAbsoluteSpeedLimit anywhere as far as I know. and there's only one stepper motor involved.

There must be something weird going on in my code, but I don't know what. It's quite a messy codebase tbh, I am tempted to clean it all and simplify but I need time to do this that I haven't got right now unfortunately.
But if I can get a simple demo of the symptoms I will share it.