I am trying to debug an issue with an extension that has to do with using the probe as a virtual endstop. The relevant sections of the config are: [stepper_z] step_pin: PB3 dir_pin: PB2 enable_pin: PA5 endstop_pin: probe:z_virtual_endstop microsteps: 32 full_steps_per_rotation: 200 rotation_distan…

Weba @voidtrance ! I think this belongs more to the General Discussion sub-forum (I’ll move it). Please attach the klippy.log to your next post. [image] voidtrance: why does it set the toolhead position to the probe offset instead of 0? Are you sure this is 10 mm? Or ist it 5 mm: #homing_…

Here is the Klippy log. klippy.log (73.0 KB)

I am not sure what you mean. The retract is 5mm: _retract_move: [0.0, 0.0, 15.0, 0.0] which is 10 + 5. That is consistent with the toolhead position + 5mm: toolhead set_position [0.0, 0.0, 9.995000000000005, 0.0] _retract_move: [0.0, 0.0, 15.0, 0.0] What I was asking why is the toolhead positio…

Git version: 'd8659974-dirty' Untracked files: klippy/extras/.#pid_calibrate.py, klippy/extras/gcode_shell_command.py, klippy/extras/led_interpolate.py, klippy/extras/loop_macro.py, klippy/extras/pizza_oven.py, klippy/extras/settling_probe.py, klippy/extras/state_notify.py, klippy/extras/temp_tracke…

I am the owner of that repository. That is just a straight fork of Klipper without any changes. I can try without the extensions. The changes to the actual Klipper files are purely debug prints, no other code changes.

The exact same thing happens when remove all extensions: Git version: 'd8659974-dirty' Modified files: klippy/extras/homing.py, klippy/extras/probe.py, klippy/toolhead.py _do_home_z_via_probe: homing_info(speed=5.0, position_endstop=10.0, retract_speed=5.0, retract_dist=5.0, positive_dir=False, se…

[image] voidtrance: That is just a straight fork of Klipper without any changes. Then why bother? Point Kiauh to offical repo and reinstall.

Again, I am lost. What do you mean? I am not trying to fix a “broken” Klipper. I am trying to understand how Klipper works because I need to debug an extension. Reinstalling Klipper won’t help with that at all.

[image] voidtrance: _probing_home I’m not sure if it helps: diff --git a/klippy/extras/homing.py b/klippy/extras/homing.py index 5b484529b..ce4f020f7 100644 --- a/klippy/extras/homing.py +++ b/klippy/extras/homing.py @@ -259,7 +259,9 @@ class Homing: probe_session.run_probe(gcmd) …

So, in my example, why would the toolhead be at 10mm (which coincidentally is the probe offset)? If I change the probe offset to 20, I get _probing_home (result): [0.0, 0.0, 350.0575, 0.0] _probing_home (toolhead): [0.0, 0.0, 20.0, 0.0] toolhead set_position [0.0, 0.0, 20.0, 0.0] The toolhead po…

Homing probe virtual endstop

General Discussion

nefelim4ag August 10, 2026, 10:45pm 18

They can’t, that is it. When klicky is attached, it will contact with the surface before nozzle.
So, it is below nozzle.

I will find a picture of Klicky and attach it here

Topic		Replies	Views
Bed Probe Offset- How does it really work? What I've learned General Discussion	4	3684	November 4, 2022
Reviving the dockable_probe Developers	137	8692	June 15, 2025
How to create multiple probes for multiple manual_steppers? General Discussion	23	594	December 17, 2025
Current Klipper logic for max X and Y doesn't seem to make sense and it prevents only the less damaging type of crash Features	9	444	October 9, 2024
BIQU MicroProbe V2.0 on Spider with Klipper? General Discussion	65	5807	February 15, 2024

Homing probe virtual endstop

Related topics