-
-
Notifications
You must be signed in to change notification settings - Fork 19.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] S-curve deceleration lost steps #26861
Comments
Please download Also, please attach your configs. |
And fill out "Steps to Reproduce" in detail. |
run_logs.zip |
If I increase STEPPER_TIMER_RATE, things will improve. I suspect that calc_timer_interval will have a bias in the calculation and that this bias will accumulate,If the deviation between frequency and final_rate at the end of deceleration stage is large, it is easy to produce mechanical impact |
Can you see if the change in #26881 makes any impact to this, or if we are chasing a separate issue? |
Greetings from the Marlin AutoBot! Disclaimer: This is an open community project with lots of activity and limited |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Did you test the latest
bugfix-2.1.x
code?Yes, and the problem still exists.
Bug Description
I tested the S-curve. In the deceleration stage, the last deceleration step could not reach the set end speed because of the accuracy of the floating point number conversion. (The cumulative value of deceleration time cannot reach the total deceleration time, but the number of deceleration pulses is reached)
Bug Timeline
No response
Expected behavior
No response
Actual behavior
No response
Steps to Reproduce
No response
Version of Marlin Firmware
marlin 2.1.x
Printer model
No response
Electronics
No response
LCD/Controller
No response
Other add-ons
No response
Bed Leveling
None
Your Slicer
None
Host Software
None
Don't forget to include
Configuration.h
andConfiguration_adv.h
.Additional information & file uploads
No response
The text was updated successfully, but these errors were encountered: