QtDragon_hd + Basic Probe - probing results not displayed

Hi guys,

after performing probing (with Basic Probe routine), the results are not displayed in the GUI immediately. The results appear only after pressing the probing button again. Additionally, the values from the previous probing are still displayed each time a new probing is performed.It seems that the GUI is not being updated properly to reflect the new probing results.I am using the QtDragon_HD GUI with the Basic Probe routine. After performing several tests, the current situation is as follows:

• If you press the button for Z-axis height probing (probe down routine), the probe starts moving. If you change the feedrate or rapid override potentiometer value during this movement, the program does not wait for the probing to finish, but instead immediately displays the previously measured value in the table (in the case of the first probing, it shows 0).
• If you press the button for Z-axis height probing (probe down routine), the probe starts moving. If you don’t change the feedrate or rapid override potentiometer value during this movement, the program waits for the probing to finish, and only after successful probing does the value in the table update — however, once again it shows the previously measured value (or 0 in the case of the first probing)

Can someone explain to me why, even after a successful probing, the currently measured value is not displayed, but instead the value from the previous measurement is shown?
Could this be caused by a synchronization issue between the Basic Probe widget and the measurement subroutine?

Thanks a lot!

Can you post your config files?

Okay, I will also make a video about what's happening and post it 

@cmorley

I’m attaching a video showing the Z-axis height measurement in the QtDragon GUI using the Basic Probe.
Note: For debugging and troubleshooting purposes, I made two modifications in my case:

• The probe_down function (in probe_routines.py) was adjusted to perform a single-touch measurement because of time.
• In the parse_input function (in basic_probe.py), a message was added in the "COMPLETE" section, which appears in the top right corner of the window. This message should appear after a successful measurement.

In the video, three consecutive measurements were performed:

• In the first measurement, a debug message popped up immediately after starting the probing, caused by a change in the feedrate value via the potentiometer — I consider this behavior undesirable. At that moment, the Z-axis measurement value was immediately updated to 0, and nothing else happened afterward.
• In the second measurement, the feedrate value changed again during the measurement, and right after this change, the Z-axis value from the first measurement was updated.
• In the third measurement, I set the potentiometer so that its value would not change spontaneously during the measurement. The measurement went smoothly, and the Z-axis value was updated only after the Z-axis returned to its start position. However, this value was already delayed since the first measurement.

Additional note: If the feedrate value does not change during the first measurement, it doesn’t affect the measurement itself. Even in that case, the first displayed Z-axis measurement value will be 0.

I hope I explained everything clearly



EDIT: added config files:
 
 

I see you are missing the abort INI entry:
linuxcnc.org/docs/stable/html/gui/qtdrag...tml#_abort_detection
This is how the probing routines detect errors.
Please add it and the file it requires and try the probing again.

I have added the missing part to the INI file and change basic_probe.py, probe_routines.py and probe_subprog.py to the original files from v2.9 from github.

After performing additional measurements, it appears that the issue of bad synchronization between the measurement process and data updating in the widget mainly occurs when the feedrate value changes during probing. If the value remains stable throughout the measurement, the probe measurement cycle completes correctly.

The video shows four consecutive measurements:

• The first measurement was completed without issues.
• In the second measurement –> at 37 seconds in the video, the feedrate oscillate from 52% to 51% and back during the probe measurement, after which the value in the table for the Z axis changed. However, the measurement had not yet been completed.
• The third measurement –> similarly to the second, at 1:06 the feedrate oscillate from 40% to 41% (a very quick oscillation), after which the value on the axis Z changed.
• The fourth measurement was completed without issues (no feedrate oscillation).

Do you have any idea how a change in feedrate could affect the value update in the widget?

I don't exactly know how it would, but there could be an explanation if the override is constantly dithering. Maybe as the python is updating the override it misses a message back from the probe routine. The probe routine and the screen sends messages back and forth at start and finish of probing.

If you run in debug mode (DISPLAY = qtvcp -d qtdragon) and run linuxcnc from a terminal, we maybe able to see the difference in commands

I've took additional measurements using the debug mode and terminal output. Attached is a video containing two following measurements.

In the first measurement, the feedrate value was constant throughout the probing. In the second measurement, the value was deliberately changed by feedrate potentiometer.



The terminal output shows that in the second measurement, the following lines were added:
[DEFAULT.QTVCP.QT_ACTION][DEBUG]  CALL_MDI Command: G91 (qt_action.py:182) 

The command M64 P4 at the beginning and M65 P4 at the end were added and are necessary for "turn on" and "turn off" of my probe.

Terminal output also in attachment: