Probe tripped during non-probe move

a no wiring solution is to and.2 the probe input with a digital input and in your gcode probing routine issue a M67 or M68 command to turn the input on and off. simple and effective.

so... it would look something like this:

loadrt probeon output_type=0

Addf and2.0 servo-thread

addf probeon.update servo-thread

setp probeon.0.enable TRUE

# ---probe signal---

net probe-in => motion.probe-input

but now im stuck, how do I link the M68 E0 Q1 to the probe?

forum.linuxcnc.org/pathpilot/45292-probe...-run?start=20#240731

I have the same tool length sensor that was linked earlier in this thread. I haven't had any problems with it triggering during cutting, but I did have an issue with the probe triggering after retraction, if I had the spindle spinning during probing. For larger diameter tools I get more accurate touch results if I spin the spindle slowly while touching off the tool, so I wanted to retain this feature.

Here is my HAL, which also ands two inputs, one for the tool setter and one for the touch probe.
net M64-and-in                  motion.digital-out-00                 and2.13.in0
net tool-sensor-and-in       hm2_5i25.0.7i77.0.0.input-16   and2.13.in1
net tool-sensor                  and2.13.out                                or2.1.in0
net probe-sensor               hm2_5i25.0.7i77.0.0.input-00    or2.1.in1
net probe-or-tool-sensor    or2.1.out
net probe-or-tool-sensor    motion.probe-input

I wrapped any G38 moves in the tool touch off subroutine with:
M64 P00
(G38)
M65 P00

The default state of motion.digital-out-00 is 0, so this code will also prevent the tool touch probe from triggering outside of a tool touch routine.