Probe /Tool setter trip stops program run ???

Your original post said you didn’t want a tripped probe to stop a running program.  The pins I suggested should achieve that.

Maybe I’m misunderstanding what you’re trying to do.  Are probes part of a subroutine of your running program? 


 

I do probing from any and everywhere The ONLY time the probe trip should work is when it is actually probing..

I did test your suggestions (

Years ago I spent over a year searching for the holy grail of a canned one function saves all "Protected Mode motion" to SAVE THE PROBE . Unless you can change the laws of physics it does not exist. That is why MOST controller depend on YOU to use a protected move when you have the probe installed. You only make protected moves in G1 mode and never faster than what the probe can safely trip at. All probe trips have overtravel depending on the feedrate it is programed at.

In other words when you put that $5k probe in the spindle you had better have your brains turned ON.  

BUT I am never too old to learn a new trick if you have one (

( TP

I do see there is a convertor to convert conv_s32_bit could that be used to convert If motion-type == 5 then sig = True ??

Sorry, took your first post literally.

I think Tormach takes the approach they do because their customer base is largely inexperienced machinists who like the machine thinking for them with the probe sometimes haha.

I've no experience with conv_s32_bit, but assuming Tormach didnt strip it from the source code, it's worth a try. 

Have you verified that motion.motion-type goes to 5 during all of your probing scenarios in PathPilot?

 

Hya Snow, Yes so far every instance of probing shows up as mode 5. My experince with CNC is IF a function is not 100% functional then DON"T use it. It will bite you sooner or later. This function gives a FALSE impression that it will always save your probe . Not gonna happen (. IF all the stars and moons align perfectly MAYBE. But that is a BIG$$$$$$ maybe .

I will let you know if it works IF I can figure it all out. So far I have not found any example of it being used.

( TP

OK no luck here. It appears that Tormach removed the library as I get a no such file or directory error when trying to load the function.

Another one of those " Close but No Cigar" functions. My PP file folder is getting full of them now.

SO back to looking for a function to compare to to block the probe pin when not probing.

( TP

It would be very trivial if you used a custom component but I suspcet halcomp is removed from your systemmto. Maybe you can create the hal file on another machine
Something like this in one line of code

You could also take the gcode approach using a digital input M62-M65 and and2. This is simple and works well