Okay, I have gone through everything I can think of to help my friend troubleshoot is Core X Y conversion to Klipper…
If somebody can tell me how to do it, I will attach the config file and the klippy log (edit… figured it out…)
Here’s the problem we are having… Z axis will move properly to trigger the bltouch the first time, but then will not lower the bed to allow the sensor to deploy the second time.
By doing a manual trigger of the probe, we can get the printer to think it’s at zero, but then it will not accept any commands for moving up or down. It does not throw any errors oh, it just does not move.
It is a hypercube build corexy running on an SKR 1.4 TURBO with TMC2209 steppers.
As far as I can remember, the hypercube uses a lead screw for the Z axis. If that’s true, the rotation_distance for the Z axis needs to match the pitch of the lead screw. That means it should be either 2 or 8. It looks like you changed the rotation_distance to a bunch of weird values, none of which are correct. You also need to reduce max_z_velocity to a sane value. You started at 25, but ended at 250. For a lead screw driven Z axis, 10 is a good place to start.
Also note that the rotation_distance for X and Y need to match your hardware. For common 20 tooth pulleys, the rotation distance should be 40.
And finally you mentioned that you’re using 2209 drivers, but you’ve configured the Z axis and the extruder for 2208 drivers. X and Y are both configured for 2209 drivers. Are you really mixing, or is that a mistake in the config?
Rotation_distance is a value that describes the hardware you’re using. It’s strongly recommended not to “calibrate” that value. It will lead to confusing results.
Compounding errors of incorrect rotation_distance and incorrect max Z velocities likely created weird results. It’s possible the axis was moving, but the move was so much shorter than expected that it didn’t appear to be moving. With a rotation_distance of 60, the Z axis would move at about 13% of the commanded speed and distance. So telling the printer to move 5mm would actually only move 0.67mm.
Now, when he homes, it homes correctly, but after homing, the z moves in the opposite direction. I think I may have seen a discussion with that issue here, but do you have a quick solution for that?
Is he issuing gcode commands to move the axis, or clicking buttons in a web frontend like Octoprint or Mainsail? If he’s clicking buttons the axis could be moving in the correct direction, just the opposite of the way he thinks it should move.
Yup… Inverted the Z control in Fluidd, and works perfectly now
Thanks one more time!
Now to start searching for MY problems… My bltouch is behind my x gantry, and is 77mm behind the nozzle, and 10mm to the left (when looking at it at the front)… I have the offset set correctly (I think), but when it homes, it puts the nozzle in the middle of the bed, not the probe… then it gives me a “move out of range” error, trying to move the y axis to -55mm…
[bltouch]
)
