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

[BUG] (Toolchange + ubl) Z axis not resumed perfectly after toolchange(on singlenozzle) #17229

Closed
studiodyne opened this issue Mar 21, 2020 · 4 comments
Labels
Bug: Potential ? F: U.B.L. Needs: More Data We need more data in order to proceed

Comments

@studiodyne
Copy link
Contributor

studiodyne commented Mar 21, 2020

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

#if HAS_LEVELING && DISABLED(SINGLENOZZLE)                         
   // Set current position to the physical position
   TEMPORARY_BED_LEVELING_STATE(false);
#endif

No bug in all situation with G1 Z1 /n G1 Z-1, or G10/G11

@studiodyne studiodyne changed the title [BUG] (Toolchange + ubl) Z axis not resumed perfectly (on singlenozzle) [BUG] (Toolchange + ubl) Z axis not resumed perfectly after toolchange(on singlenozzle) Mar 21, 2020
@thinkyhead
Copy link
Member

thinkyhead commented Mar 31, 2020

The TEMPORARY_BED_LEVELING_STATE(false) line is equivalent to this:

const bool tbls = planner.leveling_active;
set_bed_leveling_enabled(false);

…and then at the point where tool_change exits it causes this to be done:

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 TEMPORARY_BED_LEVELING_STATE with the code described above to see if it makes any difference. If it does, this would indicate a possible problem with TEMPORARY_BED_LEVELING_STATE.

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 thinkyhead added Bug: Potential ? Needs: More Data We need more data in order to proceed labels Mar 31, 2020
@studiodyne
Copy link
Contributor Author

studiodyne commented Mar 31, 2020

@thinkyhead
Don't forget , I've a SINGLENOZZLE printer , but i have no idea if the bug exists on other configuration.
But the question is why ' SINGLE NOZZLE ' is disabled and other configuration not ?
I have enabled this branch and all works fine

#if HAS_LEVELING                          
   // Set current position to the physical position
   TEMPORARY_BED_LEVELING_STATE(false);
#endif

@McUtty
Copy link

McUtty commented May 17, 2020

Hallo,

I thing i have the same problem.
After toolchange the Z Axes don't come down.
If i print a part with every tool his own layer, there is no problem. In gcode is a Zxxx command after toolchange.
If i print a part with more then one tool a layer, at fierst time, there is no Zxx in gcode, only Xxx, Yxx Exx, but in second layer. Then the X-Axes comes down. There is a Zxx command for the next layer.
If i manualy change the tool, it don't comes down.

@github-actions
Copy link

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.

@github-actions github-actions bot locked and limited conversation to collaborators Jul 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug: Potential ? F: U.B.L. Needs: More Data We need more data in order to proceed
Projects
None yet
Development

No branches or pull requests

3 participants