Increasing horizontal_move_z during Z_TILT_ADJUST

Basic Information:

Printer Model: Voron Trizero (V0.2 mod with tillable bed)
MCU / Printerboard: Double BTT SKR Pico
Host / SBC: BTT pi
klippy.log

Describe your issue:

I have a Voron Trizero with zero click (small version of Klicky) probe. I don’t know if it is some strange interaction between Klicky macros and Klipper, or if it just some bug on Klipper. But every time I do a Z_TILT_ADJUST command, the printer uses the “horizontal_move_z” height on the first 3 measurements points, make the initial corrections and then increase the horizontal_move_z height, or apply it twice, for the next measurements. So, because of it the Z tilt processes takes too long to finish.

I made a small video to exemplify the problem. If you take a look at it, you can observe the different Z height between the first XY move to the second XY move.

https://youtu.be/GWYkflWfZSs?si=XDhoosJ7XM-8lM8v

klippy-5.log (6.7 MB)

Most probably your Klicky integration is resetting toolhead offsets during Z_TILT_ADJUST execution.

Currently Z_TILT_ADJUST code is using a constant value of “horizontal_move_z” when changing probe points, so it must be something else which reacts on klipper events and screwing Z position

Also i did see you have there third-party “z_calibration”, as a tryout - try to disable it, maybe it’s causing this.

Thanks for your help. I uninstalled the Z_Calibration plugin, but nothing changed. Any other idea? There is any way of monitoring Klipper events to try to detect what is triggered by this event?

Your configuration have 2 User variables which controls Klicky debug ouput
try to enable them and analyze Klicky debug messages.
Or collect All of them and send here - I will try to analyze.

[gcode_macro _User_Variables]
variable_verbose = False
variable_debug = False

Klipper also can produce additional messages in log, to enable it you need to add “-v” options in klipper startup string.

The verbose and debug variables are true. But how do I change the Klipper startup string do “-v”?

Usually there is a file which control klipper startup: /etc/systemd/system/klipper.service
you can try to edit it with elevated permissions

sudo editor /etc/systemd/system/klipper.service

introduce changes, then save and reboot.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.