Probe /Tool setter trip stops program run ???

Oops I missed a ; at the end of a line

Do custom user M-codes (M100-199) work in Path Pilot? If they do you could set up a couple custom M-codes that link and unlink the hal pin for the probe input.

I looked at mcodes and subs and physical relays,etc but it ends up as something you have to remember to turn on and off and OLD code will not work without mods.

It could be done with a and2 and use motion.motion-type(5) BUT motion-type is a s32 value so it cannot be compared to a bit Also looked at conv_s32_bit to cnvert that s32 value to a bit, BUT you cannot load it in PP (

( TP

I messed around with conv_s32_bit last night anyways, and it looks to me that the name is a bit misleading. Even if it were part of PP, I dont think it does what you're after.

Rod's idea is the easiest, but I didnt suggest similar because I'm 99% certain halcompile isnt included either. Though, there may be a thread here on how to add it.

Otherwise, I have had really good response from Tormach with emailing them ideas and beta testing. You might try opening some discussion with them if it's worth it to you.

Did you check the PP log and see if it showing where the probe/setter is getting tripped? it may be a piece of PP code that is in error or due to modifications is not working correctly.

THe main problem is larger machine always create a resonate freq that tends to rattle the limit switches. The main culprit is teh Z top limit and seeing how with a BP CNC the quill IS a ballscrew you have to protect the quill from bottoming out on the high limit it HAS to be there.

ALSO there are times where we preload things while the machine is running like changing out the probe or tool setter. IF you do that in PP then it trips the machine offline and stops.

The function is really a silly function. IF you want it it should be an option you can turn ON/OFF with a mcode. THe normal function should default to OFF then you can turn it ON when you want it.

What I have to do now is to use a pair of relays to BLOCK the probe / toolsetter signals . For each probe I have to crowbar across the inputs so that PP thinks there are not active. BUT when you need to use the probe /toolsetter you have to REMEMBER to release the relay so PP can see the signals again.

NO ONE in teh CNC world does it like Linuxcnc is doing it. (;-(

( TP