Issue with G38.5

Hi new here.

Using linuxcnc 2.8.4-1 and having issues with g38.5 commands.  The probe I am using is a magnetic encoder on a rail and spring system to measure distance.  My hal is setup so that a displacement of >0.005in will trigger the probe input.  The gcode starts with a g38.3 to probe the piece to get its location.  Then using g38.5 command to determine the edge of a part by moving in z until the probe falls off.  I've had issues with "probe tripped during non probe move" so I am controlling the activation of the probe input signal with a digital io pin.  I am still getting "probe tripped during non probe move" errors and confused as to why it is still happening.  

Hal config:
#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

Gcode:

M64 P3    (enable probing) 
G38.3 F15 Y1.6  (probe vertically into the part)
G38.5 Z4 F25 (drag off edge) 
M65 P3    (disable probing) 
G4 P0.1 (dwell to make sure the signal was sent to disable probing)
 

Awesome thank you!

Colleague, please publish the entire part of the hal file for controlling the probe shutdown? Including the commands addf + loadrt + something like this net probepin parport.0.pin-13-in-not => and2.3.in0

vers 2.84.

For real-time kernel5.4.254 or 5.4.290, there is only version 2.9.4. Apparently, this patch isn’t there?

As planned, I installed 2.9.4 with both 254 and 290 cores. The test result is bad - excellent jitter (less than 1000), but the same sensor response error (when performing G38.5, the sensor moves, the response stops, stops and flies out error The sensor was activated during working movement - but in the g-code program there are no commands of the form G1-G3 at all!). 
In addition, a completely new mistake for me is misalignment of axes (joints)! First, Joint0 (this is the first X motor), then Joint3 (the first Y motor) - XXYYZ circuit.

I am quite proficient with build-install-clone commands and have the ability to simultaneously have and use all the versions under investigation on a single HDD. Currently installed and used alternately are
2.8.4 and 4.19. 195-rtai-amd64 - works almost flawlessly, except for a known (and already fixed in 2.9.7) bug (I easily ported it to 2.9.4, as well as matrixkin from 2.10 to 2.9.7 and 2.9.4), so I have to do without G38.5
2.9.4 with kernels 254 and 290 - they are unable to work due to a bug for multi-engine configurations, see forum.linuxcnc.org/9-installing-linuxcnc...-2-9?start=60#339123
2.9.7 - of course, I don't like userspace, but I am ready to use it for G38 tasks. It is unable to work due to this, forum.linuxcnc.org/38-general-linuxcnc-q...bing?start=10#338958, bug

If you insert M66 P0 L0 between the probe moves then the queue might be cleared as a side effect.

Great news, thanks for the idea. I'll check it out tomorrow with version 2.9.7 and let you know the results.

linuxcnc.org/docs/html/gcode/m-code.html...programmed%20timeout)%20occurs.