Probe /Tool setter trip stops program run ???

Hi Guys I noticed that PP will stop the program run IF it sees an errant probe trip or tool setter trip .  I assume that function is BASED in LinuxCNC. Is there a way to turn it OFF  ??.

( TP

Off the top of my head, one option would be to use the and component to “and” whatever the the probe pin is with something like “halui.mode.is.mdi”. Or maybe “halui.mode.is.auto-not”.  There may be better pins, but you get the idea.  Then it wouldn’t be valid unless the interpreter is in manual mode.  

He said WHAT ?????? ( I am horrible at AND,OR,MUX they make my brain hurt.

It only needs to work IF you are in G38nn mode if that is a mode.

( TP

OK here goes. IS this anywhere close to working ?? I am not sure how to handle the motion.motion-type( ) Type 5 is probing

HALL entry for the probe and setter

net probe-in <= hm2_[HOSTMOT2](BOARD).0.gpio.049.in_not debounce.0.4.in
net setter-in <= hm2_[HOSTMOT2](BOARD).0.gpio.036.in_not debounce.0.5.in

##*******************************************************

net P_sig1 and2.0.in0 <= hm2_[HOSTMOT2](BOARD).0.gpio.049.in_not debounce.0.4.in

net P_sig2 and2.0.in1 <= motion.motion-type(5)

net P_active probe-in <= and2.0.out

##*******************************************************

net s_sig1 and2.1.in0 <= hm2_[HOSTMOT2](BOARD).0.gpio.036.in_not debounce.0.5.in

net s_sig2 and2.1.in1 <= motion.motion-type(5)

net s_active setter-in <= and2.1.out

No, I am afraid that won't work. and2 requires two bit type inputs. motion.motion-type is an s32 type pin.

Everything else you have seems like it should work. So long as and2 is in the hal file, and if it is, you increased the count by one, and address them according.

As far as pins to try in lieu of motion.motion-type, you could try:

I don't find any signal that fits the entire parameter of blocking it other than motion-type = 5 (probing)

Is there any way in HAL to convert IF motion-type == 5 to T/F ??

( TP