"Probe tripped during non-probe move" while Probing

Hi at all,

I am new in CNC and use LinuxCNC with Probe Basic.
Last week i installed an 3D Probing-Sensor that basicaly works fine,
but if i try calibrating or probing, in the middle of probing-process, the probing tool is switching correctly in slow move, but i get an error "Probe tripped during non-probe move" and probing stopps
I'm a little confused about this problem.
Can someone give me an hint, how to solve this problem?

Many thanks to all.
Best regards
Jens

Try inverting the input in hal.
Usually that is it, not always.

Hi Tommylight,

I Checked it in the HAL-Monitor and i think the switching is correct.
So if I would convert it, I allways would get this error.
Should i try this anyway?

Some more information about the behavior.
If I, for example do a calibration on a round Sample, it starts with probing Z, then X (all works fine) and while probing Y i get this error.
The Problem is, that this error appears on different steps of probing. Some times on Z, other times on other axis.

So I think the main funktionality should be correct, but maybe there is a software-Problem or the Probing-Tool maybe gives more then one signals by touching...

Is there an option to log the Switching Behavior on probing?

Best regards
Jens

Maybe there is noise causing false-triggering of the probe. Or possibly the acceleration of the system is high enough to trigger it?

You could try debouncing the probe signal in HAL (with the debounce component) but don't over-do it or the probe results will become inaccurate.

Halscope is far better than any logging to see what is going on...

andypugh wrote:

Maybe there is noise causing false-triggering of the probe. Or possibly the acceleration of the system is high enough to trigger it?

You could try debouncing the probe signal in HAL (with the debounce component) but don't over-do it or the probe results will become inaccurate.

Hi,

at first, to be concrete, i bought this one.  3D Probe
It has an optical indicator and if i can see, this indicator shows me, that it should work perfect.
On every error, the indicator shows, that there was a tipping.
So with this information together with the error, in my opinion this only could be coused if the tipping-signal isn`t clear and the system gets more then one signal on touching.

So the next step is to analize the signal with the Halscope (thanks to rodw)
Parallel I will test if it will change something to speedup a little bit.

Many thanks for the hint about "debounce", i will have a look at it.

Best regards
Jens 

 

short update

debounce with value "3" -> problem solved!

Many thanks
Jens