Skip to content
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

Potential issue with delta printers #924

Closed
T3P3 opened this issue Oct 25, 2023 · 4 comments
Closed

Potential issue with delta printers #924

T3P3 opened this issue Oct 25, 2023 · 4 comments
Assignees
Labels
bug Bug that has been reproduced Done - Needs Testing
Milestone

Comments

@T3P3
Copy link
Contributor

T3P3 commented Oct 25, 2023

https://forum.duet3d.com/topic/33886/y-slope-with-3-5-0-rc1-not-seen-with-3-4-6/14

@T3P3 T3P3 added the bug Bug that has been reproduced label Oct 25, 2023
@T3P3 T3P3 added this to the 3.5.0 milestone Oct 25, 2023
@dc42
Copy link
Collaborator

dc42 commented Nov 1, 2023

User reports it is solved by the latest 3.5.0-rc1+ build, see forum thread.

@dc42 dc42 closed this as completed Nov 1, 2023
@dc42
Copy link
Collaborator

dc42 commented Apr 5, 2024

Issue is not solved and affects 3.5.0-rc.3. See https://forum.duet3d.com/post/335641 and the following posts.

@dc42
Copy link
Collaborator

dc42 commented Apr 5, 2024

Found two causes:

  1. We were only allowing step times to be calculated late (beyond the move duration) in the last segment of the move. On delta printers we have previously seen that the last two steps may be calculated late. When input shaping is enabled the last segment may contain only one step, so the penultimate segment may have a late step calculation. This should have led to a step error being logged, but the code to record step errors was not working because the error status was being cleared when the move was seen to have completed (or in this case, aborted).
  2. A delta move may sometimes have zero net steps but a DM is still created in case the carriage needs to move up and then down by the same amount during the move. However, if the move really didn't require any steps then although totatSteps was set to zero one step was always taken.

I have tested the fixes locally and provided a binary to the users who reported the problem.

@dc42
Copy link
Collaborator

dc42 commented Apr 10, 2024

Confirmed fixed.

@dc42 dc42 closed this as completed Apr 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bug that has been reproduced Done - Needs Testing
Projects
None yet
Development

No branches or pull requests

2 participants