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

Issue #23540, Eliminate unwanted Z movement when parking head #23565

Closed

Conversation

Bob-the-Kuhn
Copy link
Contributor

Description

This is a work around for issue #23540.

Root cause is not yet known.

Early in the pause feature it attempts to do a retract but in doing so it also moves the head to the unleveled location. The same unwanted head movement also happens when restoring the head at the end of the pause.

Normally the unwanted head movement moves the head away from the print (upwards towards the park position) but, in the case where the nozzle is the probe, this is towards the print.

This work around turns off leveling before the E movement command and then restores it to it's former state immediately afterward.

In the case of UBL bilinear leveling, if the leveling matrix value is posiitive then the unwanted head movement will be towards the bed/print. If the matrix value is negative then the unwanted head movement is away from the bed (toward the park position).

Requirements

For this to be a problem the bed probe must trigger AFTER the nozzle touches the bed, PAUSE must be enabled and LEVELING must be enabled.

The DUET Smart Effector is an example of a probe that triggers after the nozzle touches the bed.

This isn't a problem for the vast majority of users because they use probes that trigger before the head touches the bed.

Configurations

See Issue #23540 for config files and for a gcode file that can be used to safely test for this issue.


This fix has been tested on a delta printer using a DUET Smart Effector and a BTT Smart Filament Sensor with UBL bilinear leveling enabled.

@github-actions
Copy link

Thanks for your contribution! Unfortunately we can't accept PRs directed at release branches. We make patches to the bugfix branches and only later do we push them out as releases.
Please redo this PR starting with the bugfix-2.0.x branch and be careful to target bugfix-2.0.x when resubmitting the PR.
It may help to set your fork's default branch to bugfix-2.0.x.
See this page for full instructions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant