Probe error on 2nd print

General Discussion
1

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 (25.6 KB)

sovol-macros.cfg (22.8 KB)

klippy(3).log (8.7 MB)

2

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] 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.

3

FWIW,
You can simply use safe_z_home, which can simplify things.

A probe triggered before movement normally means that it is.

	G28 Z
	G0 Z10 F1000
	G0 Z2 F1000
	G4 S1
	M400
	PROBE TAP_THRESHOLD=0.4

And you have:

[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:

	G0 Z2 F1000
	PROBE # > useless here TAP_THRESHOLD=0.4

So, it is triggered here.

-Timofey

4

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 :slight_smile:

5

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.

6

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.

7

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.

8

Please mark a solution.

Did you remove [probe_pressure] and the “dirty” python modules?

9

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.