G31 overshoot just stops.
No error message displayed.
Is it only an internal "error signalled" that stops the axis ?

"If the probe does not trip even after overshooting the programmed
point slightly, an error is signalled."

Thanks,
Russ

Hi Russ

This was a major hindrance when I was writing my probing routines. I never did get a definitive answer but I couldn't find anywhere where an error was signalled. Maybe to a plugin - I don't know - but not to the user nor to CB that I could find. The other question I couldn't get an answer to was "why would G31 overshoot the programmed point anyway?".

Ian

Thanks Ian, I vaguely remember the overshoot discussion you mention.
I suppose the sequence not completing is an adequate "displayed error" in itself.
Was just curious.
Thanks again,
Russ

YEP I agree it was a BEACH that there was not an error signal. When running LONG probing routines it woul dbe NICE if the REcorded data SHOWED WHERE in the routine A PROBLEM existed. Even a simple parameter NUMBER like "9999" Where the 9999 means an overun. and it is VERY easy to spot in a data file.

X1.000 Y2.000 Z.000 A0.000
X9999  Y9999  Z9999 A9999

SOrry for the ramble but when you are probing intake ports on race engines and the routine runs for hundreds of thousands of probes these things become very important to know.

NOW back to the regularly scheduled program,

(;-)TP