Probe tripped during non-probe move deadlock

abs32
Offline
Senior Member

22 Nov 2025 18:37 - 22 Nov 2025 18:42 #338993 by abs32

Replied by abs32 on topic Probe tripped during non-probe move deadlock

I installed version 2.9.4 and 2.9.7 and they work worse, replacing this error with another one - Queue is not empty after probing.
In this regard, I ask you to publish a complete road map on what is quoted here forum.linuxcnc.org/38-general-linuxcnc-q...obing?start=0#333528"
a solution to this topic.
It says about "Great HAL": www.forum.linuxcnc.org/38-general-linuxc...dlock?start=0#332412

Now I have such entries in hal -

net probe-in <= parport.0.pin-13-in-not
net probe-in => motion.probe-input

By analogy with "Great HAL" I assume this -

loadrt flipflop count=0 
loadrt flipflop count=1
addf flipflop.0                 servo-thread
addf flipflop.1                    servo-thread
setp   flipflop.0.set FALSE
setp   flipflop.0.data  TRUE
net probep-in        parport.0.pin-13-in-not  => flipflop.0.clk #при этом отключить базовый вариант
net probere-set      motion.digital-out-00    => flipflop.0.reset
net probefiltered   flipflop.0.out           => motion.probe-input  parport.0.pin-01-out

However, how can this be related to the M64 P0 + M65 P0 call?
It is not clear why the Greet HAL example contains addf flipflop.1 (in addition to addf flipflop.0) if flipflop.1 is not used in any way according to the example?

Last edit: 22 Nov 2025 18:42 by abs32.

Please Log in or Create an account to join the conversation.

Time to create page: 0.056 seconds