how to get rid of the probed dumping non-probe mode error?

Colleagues, there is Probe. And there is a constantly appearing error 
probe tripped during non-probe mode

To combat this error, I specified the following in the configuration file -
loadrt select8 count=1
addf select8.0 servo-thread
net probe-in select8.0.enable
net motion-mode motion.motion-type select8.0.sel
net probesel select8.0.out5 motion.probe-input

The error frequency is immediately sync. However, with such a conciguration, the g38.4 and g38.5 command does not work

When you enter (midi mode) the g38.5 command (options), nothing happens. And when you enter the g48.4 command (parameters), nothing happens either, but an error message appears - probe is already clear when starting g38.4 or g38.5 move, while in fact the sensor is in the "contact is" state and this is visible with the eyes - contact with the body is and the contact LED is lit.

This error disappears and the g38.4 + g38.5 commands are executed normally if "those" entries in the configuration file are deleted.

The question is: how to get rid of the probed dumping non-probe mode error?

Thank you, I'll try

v2.8.4

from what has been said here - www.forum.linuxcnc.org/38-general-linuxc...dlock?start=0#332382

I inserted the following lines into my hal -
#Negate Encoder Position
setp mult2.2.in0 -1.0
setp comp.0.in0 0.005 # Threshold value for encoder
net enable-probe <= motion.digital-out-03 => and2.1.in1

# Encoder position and comparator
net negated-encoder-out <= mult2.2.out
net negated-encoder-out comp.0.in1 # Connect to comparator input
net encoder-threshold-met <= comp.0.out => and2.1.in0

# AND logic to trigger only during probing motion
net probe-trigger and2.1.out motion.probe-input

when I start, I get an error -
parameter or pi 'mult2.2.in0' not found

from what has been said here - www.forum.linuxcnc.org/38-general-linuxc...dlock?start=0#332412

I inserted the following lines into my hal -
setp flipflop.0.set FALSE
setp flipflop.0.data TRUE
net probepin parport.0.pin-13-in-not => flipflop.0.clk
net probereset motion.digital-out-00 => flipflop.0.reset
net probefiltered flipflop.0.out => motion.probe-input parport.0.pin-01-out

when I start, I get an error -

parameter or pi 'flipflop.0.set' not found

What am I doing wrong?

yes.
in the second option it was necessary to add -
loadrt flipflop count=2
addf flipflop.0 servo-thread
addf flipflop.1 servo-thread

LNCNC started without errors.

However, the scanning program worked crookedly - the probe reached the workpiece, rested on it and went to the side.


but it’s not yet possible to launch the first option; I don’t know which loadrt + addf are needed for and2.1
I found about others -
loadrt mult2 count=3
addf mult2.2 servo-thread
loadrt comp count=1
addf comp.0 servo-thread

This option completely ignores the sensor operation G38.3 F550 Z0!
loadrt flipflop count=2
addf flipflop.0 servo-thread
addf flipflop.1 servo-thread
setp flipflop.0.set FALSE
setp flipflop.0.data TRUE
net probepin parport.0.pin-13-in-not => flipflop.0.clk
net probereset motion.digital-out-00 => flipflop.0.reset

My simple task is to find the bottom when the sensor is triggered, to move away from the found bottom without triggering an error "non-probe mode error" 

 

if -
##Negate Encoder Position
loadrt mult2 count=3
addf mult2.2 servo-thread
loadrt comp count=1
addf comp.0 servo-thread
loadrt and2 count=2
addf and2.1 servo-thread

setp mult2.2.in0 -1.0                    
setp comp.0.in0 0.005                   # Threshold value for encoder
net enable-probe    <=    motion.digital-out-03    =>    and2.1.in1
#
# Encoder position and comparator
net negated-encoder-out <= mult2.2.out
net negated-encoder-out comp.0.in1       # Connect to comparator input
net encoder-threshold-met    <=    comp.0.out   => and2.1.in0

then, when the command is executed -
M64 P3
G38.3 F15 Z0

the machine does not respond to the sensor.

And in the usual configuration -
        net probe-in        <= parport.0.pin-13-in-not
        net probe-in => motion.probe-input

the sensor is triggered, the machine understands this, but sometimes there is an error "non-probe mode"

What am I doing wrong?