-
-
Notifications
You must be signed in to change notification settings - Fork 19.3k
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] (Toolchange + ubl) Z axis not resumed perfectly after toolchange(on singlenozzle) #17229
Comments
The const bool tbls = planner.leveling_active;
set_bed_leveling_enabled(false); …and then at the point where set_bed_leveling_enabled(tbls); When leveling is enabled / disabled, under most systems the Z position is immediately corrected. With U.B.L. it might require an extra step (such as a zero-length move) to prime the Z offset when leveling is enabled in the same spot. To narrow down the issue we will need to add some logging and examine the details. In the meantime, you can try replacing the It would also help to see if this same issue occurs with ABL-Bilinear. If the problem does not go away then we have to examine the way Z correction is applied when turning UBL on and off. |
@thinkyhead #if HAS_LEVELING
// Set current position to the physical position
TEMPORARY_BED_LEVELING_STATE(false);
#endif |
Hallo, I thing i have the same problem. |
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. |
Video on youtube
https://www.youtube.com/watch?v=YXJ7z3-pArs
SINGLE NOZZLE + UBL on + (Z RAISE or not , Park or Not )
After homing , with a measurement tool
Each tool change , raise z axis by the amount of UBL , increment this amount each toolchange called and never resume the exact origin position, after some tool change the head have too much offset and print is dead
No bug with UBL off
My Help
If I enable SINGLE NOZZLE on the branch below , bug disappear. See Line 869 in toolchange cpp
No bug in all situation with G1 Z1 /n G1 Z-1, or G10/G11
The text was updated successfully, but these errors were encountered: