You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Been running auto z on my voron 2.4 for almost a full year now with close to 0 issues when suddenly the Z offset is to high.
No worries tries to adjust, make sure nozzle is clean and so on
Issue continues
So I do a calibrate_z and it gave me a new z position endstop so I changed that value to the new suggestion
Then i realized G0 z0. 1 is a bit to high. So I adjust the switch offset
I adjust from 0.498 to 0.5, from 0.5 to 0.51 and this continues to 0.55 but still the distance between the bed and nozzle isn't 0.1 just slightly above.
It doesn't feel like the offset is changing no matter what I do
I've tried adjusting the klicky probe, changed the clicky probe switch.
The only thing I haven't tried changing is the whole Z endstop assembly.
So I'll happily take any suggestions on what the freak could possibly be the issue.
I'm at a loss haven't had a single issue with it until now.
Thanks
The text was updated successfully, but these errors were encountered:
Been running auto z on my voron 2.4 for almost a full year now with close to 0 issues when suddenly the Z offset is to high.
No worries tries to adjust, make sure nozzle is clean and so on
Issue continues
So I do a calibrate_z and it gave me a new z position endstop so I changed that value to the new suggestion
Then i realized G0 z0. 1 is a bit to high. So I adjust the switch offset
I adjust from 0.498 to 0.5, from 0.5 to 0.51 and this continues to 0.55 but still the distance between the bed and nozzle isn't 0.1 just slightly above.
It doesn't feel like the offset is changing no matter what I do
I've tried adjusting the klicky probe, changed the clicky probe switch.
The only thing I haven't tried changing is the whole Z endstop assembly.
So I'll happily take any suggestions on what the freak could possibly be the issue.
I'm at a loss haven't had a single issue with it until now.
Thanks
The text was updated successfully, but these errors were encountered: