# Probe error on 2nd print **URL:** \ **Category:** General Discussion\ **Created:** [August 13, 2026, 6:17pm UTC](https://klipper.discourse.group/t/probe-error-on-2nd-print/26238 "2026-08-13T18:17:39Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![dthree](https://avatars.discourse-cdn.com/v4/letter/d/d6d6ee/32.png) [@dthree](https://klipper.discourse.group/u/dthree)\ **Post date:** [August 13, 2026, 6:17pm UTC](https://klipper.discourse.group/t/probe-error-on-2nd-print/26238/1 "2026-08-13T18:17:39Z")
### Basic Information: Printer Model: Sovol SV08 MCU / Printerboard: Stock Host / SBC Built in klippy.log _Fill out above information and_ _ **in all cases attach your** _ **`klippy.log` _file_** (use zip to compress it, if too big). _Pasting your_ `printer.cfg` _is **not** needed_ _ **Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there** _ ### Describe your issue: Just moved to mainline on an SV08 with the Sovol eddy sensor. Started with eddy-ng, but switched over to the built-in probe support and disabled eddy-ng. Setup, calibration, and printing work fine. HOWEVER, after I finish one print, the next print fails while doing a z home. It will also fail if I try the z home manually. The error is “Probe triggered prior to movement”. After restaring the machine, I can print one time again before having to reboot. I figure there must be some configuration issue from the prior eddy-ng install that is affecting this. I’ve attached my macro and printer.cfg files in addition to the klippy log. [printer.cfg](https://klipper.discourse.group/uploads/short-url/kTkrjrJXf9o24F6PTxjEcGa8NBK.cfg) (25.6 KB) [sovol-macros.cfg](https://klipper.discourse.group/uploads/short-url/wVaMOgGmwBhPEQaQHpl0PJ56o9W.cfg) (22.8 KB) [klippy(3).log](https://klipper.discourse.group/uploads/short-url/ggIFiSkUxMvHCHBBEHYL7ryAVLT.log) (8.7 MB) ---
**Author:** ![cardoc](https://avatars.discourse-cdn.com/v4/letter/c/ec9cab/32.png) [@cardoc](https://klipper.discourse.group/u/cardoc)\ **Post date:** [August 13, 2026, 9:50pm UTC](https://klipper.discourse.group/t/probe-error-on-2nd-print/26238/2 "2026-08-13T21:50:49Z")
Welcome fellow Sovol refugee. A quick scan of your klippy.log (which has the REAL printer.cfg in it) finds the following 1. your configuration still has [probe\_eddy\_ng eddy] section. 2. If you are using eddy tap as probe then [probe\_pressure] is useless. Deleting it also allows you to get rid of klippy/extras/probe\_pressure.py, klippy/extras/z\_offset\_calibration.py, AND the dirty flag. 3. Your [[probe\_eddy\_current]](https://www.klipper3d.org/Config_Reference.html?h=eddy#probe_eddy_current) section doesn’t have a `tap_z_offset:` defined. It defaults to 0.0 but a small offset may Be needed. Your `start_print` macro seems okay but check your start g-code in your slicer for Sovol gibberish. I prefer to ONLY call the macro and delete everything else. ---
**Author:** ![nefelim4ag](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/nefelim4ag/32/2387_2.png) [@nefelim4ag](https://klipper.discourse.group/u/nefelim4ag)\ **Post date:** [August 13, 2026, 10:52pm UTC](https://klipper.discourse.group/t/probe-error-on-2nd-print/26238/3 "2026-08-13T22:52:04Z")
FWIW, You can simply use safe\_z\_home, which can simplify things. A probe triggered before movement normally means that it is. ```auto G28 Z G0 Z10 F1000 G0 Z2 F1000 G4 S1 M400 PROBE TAP_THRESHOLD=0.4 ``` And you have: ```auto [probe_eddy_current my_eddy_probe] sensor_type = ldc1612 max_sensor_hz = 8433215 descend_z = 2.0 ``` So, probe should be triggered when probe detects distance \<= to 2mm So, probably you did not retract before homing. Or you are seeing the error right after G28 Z: ```auto G0 Z2 F1000 PROBE # > useless here TAP_THRESHOLD=0.4 ``` So, it is triggered here. -Timofey ---
**Author:** ![dthree](https://avatars.discourse-cdn.com/v4/letter/d/d6d6ee/32.png) [@dthree](https://klipper.discourse.group/u/dthree)\ **Post date:** [August 14, 2026, 7:25pm UTC](https://klipper.discourse.group/t/probe-error-on-2nd-print/26238/4 "2026-08-14T19:25:25Z")
Thanks for that, I will try these suggestions. > your configuration still has [probe\_eddy\_ng eddy] section. Since it was in the section marked “DO NOT EDIT THIS BLOCK OR BELOW. The contents are auto-generated.” I was too scared to remove 🙂 ---
**Author:** ![dthree](https://avatars.discourse-cdn.com/v4/letter/d/d6d6ee/32.png) [@dthree](https://klipper.discourse.group/u/dthree)\ **Post date:** [August 14, 2026, 7:32pm UTC](https://klipper.discourse.group/t/probe-error-on-2nd-print/26238/5 "2026-08-14T19:32:04Z")
Thanks, I will look into safe\_z\_home and see if I can figure out where I need to do a z hop. What can’t figure out is why I don’t get this error after restarting the machine. ---
**Author:** ![cardoc](https://avatars.discourse-cdn.com/v4/letter/c/ec9cab/32.png) [@cardoc](https://klipper.discourse.group/u/cardoc)\ **Post date:** [August 14, 2026, 7:37pm UTC](https://klipper.discourse.group/t/probe-error-on-2nd-print/26238/6 "2026-08-14T19:37:44Z")
> [@dthree](#): > > Since it was in the section marked “DO NOT EDIT THIS BLOCK OR BELOW. The contents are auto-generated.” I was too scared to remove 🙂 Nothing magic in this section, is simply storage for persistent info Klipper uses across multiple sessions. NEVER change a number but deleting a section won’t cause problems. ---
**Author:** ![dthree](https://avatars.discourse-cdn.com/v4/letter/d/d6d6ee/32.png) [@dthree](https://klipper.discourse.group/u/dthree)\ **Post date:** [August 16, 2026, 12:55am UTC](https://klipper.discourse.group/t/probe-error-on-2nd-print/26238/7 "2026-08-16T00:55:05Z")
Tried the safe\_z\_home but then I couln’t use a homing\_override so I just put the z home XY coords there. Found your BED\_MESH\_ADJ\_FROM\_TAP macros from another thread and worked them into my start print and removed a bunch of unneeded stuff. Working now. Thanks for the help and those macros. ---
**Author:** ![cardoc](https://avatars.discourse-cdn.com/v4/letter/c/ec9cab/32.png) [@cardoc](https://klipper.discourse.group/u/cardoc)\ **Post date:** [August 16, 2026, 2:06am UTC](https://klipper.discourse.group/t/probe-error-on-2nd-print/26238/8 "2026-08-16T02:06:37Z")
Please mark a solution. Did you remove [probe\_pressure] and the “dirty” python modules? ---
**Author:** ![dthree](https://avatars.discourse-cdn.com/v4/letter/d/d6d6ee/32.png) [@dthree](https://klipper.discourse.group/u/dthree)\ **Post date:** [August 16, 2026, 7:56pm UTC](https://klipper.discourse.group/t/probe-error-on-2nd-print/26238/9 "2026-08-16T19:56:37Z")
Yes, I did remove [probe\_pressure] and those untracked python modules so the install is clean now, but that did not solve the problem. I think the issue was having PROBE in the [homing\_override] so I removed that, only calling PROBE from within START\_PRINT. ---
**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/klipper/original/1X/64419bf2aac6639e6ef5cef200dcd456b0a01ac3.png) [@system](https://klipper.discourse.group/u/system)\ **Post date:** [September 16, 2026, 5:57am UTC](https://klipper.discourse.group/t/probe-error-on-2nd-print/26238/10 "2026-09-16T05:57:28Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.