Probe tripped during non-probe move deadlock

Buster.
If you teach how exactly, poke your nose into the "download, enter" type of instructions, then I can. Alas, in this area (patches, sources) I am weaker than in other areas.
While I’m trying to put v2.9.4 on the free partition and even with this there are problems - in the instructions
linuxcnc.org/docs/2.9/html/getting-start...#cha:Installing-RTAI
the required repository is specified with an error, the kernel itself is installed with errors, and For several years now they have forgotten to indicate in the instructions what to do first -

apt-get purge linuxcnc-uspace
apt-get purge linuxcnc-doc*

and then more
apt-get install linuxcnc

abs32 wrote:

Buster.

Buster is a long way out of support now (end of life was June 2024).
It sounds like you are running with RTAI, which does work on Bookworm (I run it much of the time)

While I’m trying to put v2.9.4 on the free partition and even with this there are problems - in the instructions
linuxcnc.org/docs/2.9/html/getting-start...#cha:Installing-RTAI
the required repository is specified with an error, the kernel itself is installed with errors, and For several years now they have forgotten to indicate in the instructions what to do first -

apt-get purge linuxcnc-uspace
apt-get purge linuxcnc-doc*

and then more
apt-get install linuxcnc

Well the "they" above is to a large extent me.
You _probably_ don't need to purge the docs packages.
I have updated the instructions, but it will take a while for the updates to find their way to the web server.

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 -
By analogy with "Great HAL" I assume this -

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?

Do you still get this error without the flipflops and filters etc? Noe of this HAL complexity should be needed.

If there is a problem (possibly with repeated G38.2 commands) than please raise an issue on the Github so that it can be tracked. Not everyone reads every forum post (I don't) and so the forum is not a good place to report issues.

github.com/LinuxCNC/linuxcnc/issues

This error appeared and continues to appear in versions 2.8.4 and 2.9.4 when executing G38.5. By tricking hal for version 2.8.4, the problem is partially solved.

It is impossible to verify that the problem has been solved in version 2.9.7 because a new error, “Queue is not empty after probing,” appears much more frequently in it (and in 2.9.4 as well) -
forum.linuxcnc.org/38-general-linuxcnc-q...bing?start=10#338958
github.com/LinuxCNC/linuxcnc/issues/3650

I tested a „clean“ 2.9.7+ setup, without my M64/M65-flipflop solution, but no, the issue was not (completely) fixed.

It kinda improved, but the „probe triggered“ fault is still happening.
I was not able to finish even shorter milling programs (<5 mins).

But the „queue full“ bug did indeed not appear anymore.