Work with probe

My changes to the probe screen code are mostly wrapped up, but I still have an issue that I can't seem to sort out and I am confused by some of the problems I am seeing.

Here is what I changed:
- Added support for gscreen in error poll.
- Reworked the ocore and gcode functions to wait for the interpreter idle rather than using linuxcnc.wait_complete(). I found that wait_complete() frequently returns before an action is complete. This causes erratic problems and frequently would end up picking up the result for the search probe rather than the final one.
- Changed the way MDI mode is entered by putting a call to mdi_start() at the beginning and mdi_end() at the end of every button press function. These functions save the current mode, set MDI mode and then at the end set the mode to the saved mode.
- Set the spin button defaults, resolution and increments to work with Imperial units.

The problem that I can't seen to figure out is errors about not being in MDI mode. I found that Gscreen sets the mode to manual when the interpreter goes idle if the GUI is set to manual. I fixed this and verified that the mode is set to MDI but I still get random errors unless I set the mode to MDI in the GUI. I am out of ideas for now.

I could use some feedback.
Is anyone else seeing these problems? Erratic behavior, probe functions returning before the final probe is finished, errors if not in MDI mode?
It would be helpful to know the problems I am seeing are Gscreen related. Is anyone using probe_screen with Gscreen?
Anyone have clues about why I am getting MDI mode errors?

Here is a patch file for probe_screen.py is anyone is interested in the code.

thank you for sharing your work
but patch link is broken

patch download is ok

Hello,

I saw you have created this feature for linuxcnc This is a great feature and I would like to thank you all who developed it and for making it available to us.
I don't have a probe yet and I want to see it in action as a simulation but I faced some problems: the first one was to place the files from the archive in the correct path to be read and displayed by axis. After reading a few times the posts where you detailed where to put the files, I could see the Axis showing the probe_screen tab.
I turned on the mill and started to push buttons and I saw some movements and errors saying the ngc files (all x+, x-, y+, y- and down) could not be found, I cannot figure out how to solve this. I'm attaching my ini file and I am asking you for a little help.
Another problem is that when pushing the button X+ the spindle is moved down and in opposite direction (with my settings in ini file the X axis moves in right direction)
I'm a beginner using linuxcnc and the cnc mill but I've one remark. I think an operator first determines where Z zero is and then he starts probing. I think the probing operations should be disabled until the Z0 is determined by touching-off or probing or by manually setting Z0. I saw that when pressing any button Z carriage moves down then it moves in horizontal direction (X or Y) but NO retraction to a safe Z after probing
Regards,
Adrian
PS. Sorry for my English
I'

mecatron_cj wrote: Hello,

I turned on the mill and started to push buttons and I saw some movements and errors saying the ngc files (all x+, x-, y+, y- and down) could not be found, I cannot figure out how to solve this. I'm attaching my ini file and I am asking you for a little help.

Regards,
Adrian
PS. Sorry for my English
I'

See attachments post in this post forum.linuxcnc.org/forum/49-basic-config...robe?start=100#72001
If your file structure looks the same try changing
SUBROUTINE_PATH = /root/linuxcnc/nc_files/ngcgui_lib:/root/linuxcnc/nc_files/ngcgui_lib/utilitysubs
to SUBROUTINE_PATH = subroutine

Adrian,
To find the ngc files you need add the path to them in the [RS274NGC] section in your .ini file.
Here is what I am using:
SUBROUTINE_PATH = /home/cbrady/linuxcnc/nc_files/ngcgui_lib:/home/cbrady/linuxcnc/nc_files/ngcgui_lib/utilitysubs:./probe/macros
It's the last entry on the line that points to the probe ngc files. I placed the probe files in a subdirectory in the directory for where my configuration lives. That's why I use "./" as the prefix. You can use the full path if it's more clear.

If you are experimenting without a probe the movement may look confusing. Probing for an edge first moves away from the measured surface and then toward it. If you are using the buttons to measure inside surfaces then the probe moves down first, but ti does not for outside surfaces. Not sure if this is the issue or not.