How to fix "Queue is not empty after probing"
- andypugh
-
- Offline
- Moderator
-
Less
More
- Posts: 19773
- Thank you received: 4601
08 Dec 2025 22:27 #339885
by andypugh
Replied by andypugh on topic How to fix "Queue is not empty after probing"
The second example is compiled-out by
github.com/LinuxCNC/linuxcnc/blame/maste...s274ngc_pre.cc#L1542
(But I am not clear why, the commit message doesn't really say: github.com/LinuxCNC/linuxcnc/commit/b96c...de5e67d2dde0339bece3 )
So, it must be the first one causing the issue.
Did you try adding a queue-buster as suggested? (Not that that is the right fix, but maybe it will tell us something)
github.com/LinuxCNC/linuxcnc/blame/maste...s274ngc_pre.cc#L1542
(But I am not clear why, the commit message doesn't really say: github.com/LinuxCNC/linuxcnc/commit/b96c...de5e67d2dde0339bece3 )
So, it must be the first one causing the issue.
Did you try adding a queue-buster as suggested? (Not that that is the right fix, but maybe it will tell us something)
Please Log in or Create an account to join the conversation.
- abs32
- Offline
- Senior Member
-
Less
More
- Posts: 68
- Thank you received: 1
09 Dec 2025 05:37 #339896
by abs32
Replied by abs32 on topic How to fix "Queue is not empty after probing"
Yes, I tried it and reported the result—it doesn't help.
Please Log in or Create an account to join the conversation.
- abs32
- Offline
- Senior Member
-
Less
More
- Posts: 68
- Thank you received: 1
17 Dec 2025 21:54 #340257
by abs32
Replied by abs32 on topic How to fix "Queue is not empty after probing"
I conducted a large series of experiments with different sensor settings and different ini + hal settings.
First, I achieved smooth operation of the sensor (of my own design) in version 2.8.4. The Chinese sensor could perform 40,000-50,000 continuous measurements (with 38.5 disabled). My sensor completed the entire task, more than 500,000.
That is, it has been established that the quality of the sensor directly affects the appearance of the error “Probe tripped during non-probe move”.
And with the same settings in version 2.9.7, the error “Queue is not empty after probing” recurs. That is, the appearance of the error does not depend on the sensor. The question remained: does this error appear during the working stroke 38.2-38.3 and the reverse?
I disabled the “until open” movement option, as in version 2.8.4, and the error “Queue is not empty after probing” did not appear. Previously, it was not possible to obtain more than 25,000 measurements. The experiment was interrupted at 40,000. Consequently, the error “Queue is not empty after probing” occurs when executing g38.5, during execution. After g38.3, I have a G1 up command.
To disable the possibility of 38.4-38.5 on the defunct Russian forum (к сожалению, я не помню имени автора решения, но честь ему и хвала), such a modification of hal was proposed and tested by me over hundreds of hours of work and hundreds of thousands of measurements -
First, I achieved smooth operation of the sensor (of my own design) in version 2.8.4. The Chinese sensor could perform 40,000-50,000 continuous measurements (with 38.5 disabled). My sensor completed the entire task, more than 500,000.
That is, it has been established that the quality of the sensor directly affects the appearance of the error “Probe tripped during non-probe move”.
And with the same settings in version 2.9.7, the error “Queue is not empty after probing” recurs. That is, the appearance of the error does not depend on the sensor. The question remained: does this error appear during the working stroke 38.2-38.3 and the reverse?
I disabled the “until open” movement option, as in version 2.8.4, and the error “Queue is not empty after probing” did not appear. Previously, it was not possible to obtain more than 25,000 measurements. The experiment was interrupted at 40,000. Consequently, the error “Queue is not empty after probing” occurs when executing g38.5, during execution. After g38.3, I have a G1 up command.
To disable the possibility of 38.4-38.5 on the defunct Russian forum (к сожалению, я не помню имени автора решения, но честь ему и хвала), such a modification of hal was proposed and tested by me over hundreds of hours of work and hundreds of thousands of measurements -
#датчик probe
net probe-in <= parport.0.pin-13-in-not
#net probe-in => motion.probe-input (это в случае работы с G38.5)
#здесь пытаемся убрать ошибку "probe tripped during non-probe mode"
#https://www.cnc-club.ru/forum/viewtopic.php?f=15&t=31612
# Загружаем компонент select8
loadrt select8 count=1
addf select8.0 servo-thread
## Сигнал от датчика подаем на вход разрешения select8
net probe-in select8.0.enable
## Номер режима ведем на вход выбора
net motion-mode motion.motion-type select8.0.sel
## Выход 5 select8 - ко входу для датчика
net probesel select8.0.out5 motion.probe-input
The following user(s) said Thank You: grandixximo
Please Log in or Create an account to join the conversation.
- grandixximo
-
- Away
- Premium Member
-
Less
More
- Posts: 105
- Thank you received: 114
26 Dec 2025 01:34 - 26 Dec 2025 02:48 #340510
by grandixximo
Replied by grandixximo on topic How to fix "Queue is not empty after probing"
@
abs32
can you share a screenshot after running on your system
latency-histogram
for a few minutes with a few glxgears running?
can you share a screenshot after running on your system
latency-histogram
for a few minutes with a few glxgears running?
Last edit: 26 Dec 2025 02:48 by grandixximo.
Please Log in or Create an account to join the conversation.
- abs32
- Offline
- Senior Member
-
Less
More
- Posts: 68
- Thank you received: 1
27 Dec 2025 08:17 #340575
by abs32
Replied by abs32 on topic How to fix "Queue is not empty after probing"
да пожалуйста.
According to my observations, the queue error simply replaced the error Probe tripped during non-probe move.
According to my observations, the queue error simply replaced the error Probe tripped during non-probe move.
Please Log in or Create an account to join the conversation.
- grandixximo
-
- Away
- Premium Member
-
Less
More
- Posts: 105
- Thank you received: 114
28 Dec 2025 06:23 #340614
by grandixximo
Replied by grandixximo on topic How to fix "Queue is not empty after probing"
could you run
latency-histogram
instead of latency-test?
I think you might be onto something, I use a custom version with probe tripped during non-probe move disabled, and I never see queue error...
latency-histogram
instead of latency-test?
I think you might be onto something, I use a custom version with probe tripped during non-probe move disabled, and I never see queue error...
Please Log in or Create an account to join the conversation.
- grandixximo
-
- Away
- Premium Member
-
Less
More
- Posts: 105
- Thank you received: 114
31 Dec 2025 23:53 #340812
by grandixximo
Replied by grandixximo on topic How to fix "Queue is not empty after probing"
I just checked master has new option for
[TRAJ]
NO_PROBE_JOG_ERROR = 1
in the .ini file, you could use that to check if the issue goes away?
you have to make sure your version supports this, it's just been added 4 months ago
[TRAJ]
NO_PROBE_JOG_ERROR = 1
in the .ini file, you could use that to check if the issue goes away?
you have to make sure your version supports this, it's just been added 4 months ago
Please Log in or Create an account to join the conversation.
Time to create page: 0.082 seconds