Solved [Solved]Prevent docking/undocking of probe during multiple G30

[Ralms]

Hi everyone,

As I continue to program my printer, I've ran into a behavior which I wonder if there is an easy solution.

Essentially, the printer is a Voron 2.4, which 4 independent Z motors and to level it, I call G30 4 times as per the documentation:

Here is the bed.g

G28 ; home
G30 P0 X30 Y300 Z-99999 ; probe near a leadscrew
G30 P1 X30 Y60 Z-99999 ; probe near a leadscrew
G30 P2 X270 Y60 Z-99999 ; probe near a leadscrew
G30 P3 X270 Y300 Z-99999 S4 ; probe near a leadscrew and calibrate 4 motors

The probe is a Klicky probe, which is a switch type probe, but since connected to the 1LC is defined as type 8.
It's set with:

M558 P8 C"^121.io2.in" H5 F200:100 K0 T2000 

To be clear, the calibration is working fine.
However, the printer is calling deployprobe.gand retractprobe.g for every single G30 Pn call, which makes it walk back and forth a bunch of times unnecessarily.

I know that I can essentially use empty deployprobe.gand retractprobe.g files and have my macros called when needed, but I'm trying to avoid this, to not run the risk of having G30 called and not having the probe.
Is there any way flag G30 so it doesn't call deployprobe.gand retractprobe.g?
Or something like the macro parameters that I can send to G30, where it in turn does a pass-thru of the unrecognized parameters to deployprobe.gand retractprobe.g?

Thank you

(Board Duet 3 MB6HC, with 1LC running firmware 3.5.2 )

[jay_s_uk]

@Ralms call M401 to undock the probe and then do all your probing routines. That should prevent it docking it between.
Then M402 at the end

[Ralms]

@jay_s_uk said in Prevent docking and undocking of probe during multiple G30 Pn:

@Ralms call M401 to undock the probe and then do all your probing routines. That should prevent it docking it between.
Then M402 at the end

That did the trick.
Thank you!

Need to look into submitting some documentation improvements after finishing coding the printer lol