probing - false triggers during g1 and g0 moves

I am using a home made probe to do cutter length correction after manual tool changes. If I leave the probe hooked up, the acceleration during machining will sometimes trigger the probe and stop a non probing
( g0,g1,g3 etc.) G code. I had assumed the probe was only active during the G38 straight probe motion but that is obviously not the case. Is there a way to turn off the probe input without resorting to unplugging it each time it is used?

Thanks
John

Hi

You should be able to unlink whatever you have linked to motion.probe-input and re-connect when required, using a M Code script
See
linuxcnc.org/docs/2.5/html/hal/basic_hal.html#_unlinkp
and
linuxcnc.org/docs/2.5/html/gcode/m-code....d_sec_m100_to_m199_a

regards

Or block the input with a switch...

John

Which leads to possibly using the 'and' component and a gcode settable bit (say using M62, M63)
to mask the probe input in the gcode when you dont want it to be enabled.
.

thanks for the suggestions. I have investigated modifing the hal.ini file to include anding a setable variable. I like simple solutions and adding a toggle switch as John has suggested will work until I get ambitious.

thanks
John

maybe I should just make a better probe grin