#Ztilt problem

76 messages · Page 1 of 1 (latest)

dry ridge
#

hello, i am having issues for a couple of weeks now and i taught it was the bl touch that broke so i installed a IDM scanner. but i get the same results. it worked before i updated klipper. but i cant seem to find out what is wrong now. can someone with a ender 5 pro based mercury one and double Z share me his printer config so i can compare?

spark apex
#

Did you unplug any steppers when you did this?

#

increasing range often is a sign the z steppers are swapped

#

if thats not it, might just be a IDM issue

edgy linden
#

When I was having the same issue, it was because I had ztilt probing stepper Z1 first instead of stepper Z. After switching the steppers it went away. And ztilt functioned properly. Every so often I still get probe point increasing usually just restarting Z tilt again will fix it.

dry ridge
dry ridge
edgy linden
#

This is my z tilt config

#

On 5+

runic cove
#

@dry ridge Can you share your stepper_z and stepper_z1 config? Also, what mainboard are you using?

dry ridge
dry ridge
edgy linden
#

Have you tried running probe accuracy test? To verify the probe is reading correctly. But that wouldn’t explain why it wasn’t working with a different probe as well.

#

What version of klipper did you update to?

runic cove
#

the z_position should never be 0 for the Plus.

spark apex
#

Would be around -30 I believe

#

And over 400

runic cove
#

Yeah, since the front left of the bed should be 0,0

spark apex
#

Position is the point that it pivots

runic cove
#

Exactly, the leadscrew position.

spark apex
#

Which on the stock z is the lead screws and linear rods

#

Tmc settings as well

edgy linden
#

I have been meaning to fix that. When I first switched to klipper, I wasn’t exactly sure how to set that up right but it’s always worked with the way it is so I haven’t worried about it.

dry ridge
dry ridge
dry ridge
dry ridge
runic cove
#

Since the front left corner of the bed should be defined as the origin (0,0), with the leadscrew being to the left, it would be in the negative range.

edgy linden
edgy linden
spark apex
#

also try sending the command STEPPER_BUZZ STEPPER=stepper_z and STEPPER_BUZZ STEPPER=stepper_z1

#

make sure the first one moves your left motor, and the second moves the right motor

spark apex
#

Did you try the Stepper buzz commands

dry ridge
dry ridge
spark apex
#

With the command?

dry ridge
spark apex
#

Good

#

Tmc section?

dry ridge
spark apex
#

You also did the buzz on z1?

dry ridge
spark apex
#

Only asking because it's possible to plug both into z

#

The first z driver has split z, which I am not a fan of

#

And you have 4 start lead screws?

#

When you command it to move 10mm, does it move 10mm?

dry ridge
spark apex
#

Or is it moving 5 or 20mm

dry ridge
#

yes the moving distances are correct

spark apex
#

Hmm not sure what else it could be

#

You could run a probe accuracy test

#

Also verify the z motor couplers are tight on the steppers and lead screws

#

I have forgotten to tighten those before

#

And that will cause z tilt to fail

dry ridge
#

what i notice now when i use the command to buzz stepper Z1 is that it doesnt move it each time i buzz. i will try with a new wire and if that doesnt work i will try new motor

dry ridge
spark apex
#

That could be from a loose coupler

dry ridge
#

doing a z tilt now

spark apex
#

That would do it

dry ridge
#

thank you very much for the help

mighty violet
# runic cove It goes by the position of the pivot points of Z which are the leadscrews.

Yes, I agree that it goes by the position of the pivot points of Z. However, that is not the lead screw location! That is the pivot point on top of the tank. The arm is rigid from the lead screw to the tank so the vertical lift is the same there as at the screw. But to calculate the geometry, you have to use the pivot point at the tank. Position your nozzle directly over the screw and that is the pivot point. Though it will sneak up on it using the screw locations and the error tolerance, the is not correct.

spark apex
#

and the issue was fixed