problems with Verser Probe Screen 2.9
- theoneandonlyoreo
- Away
- New Member
-
Less
More
- Posts: 8
- Thank you received: 0
24 May 2025 12:59 #329042
by theoneandonlyoreo
problems with Verser Probe Screen 2.9 was created by theoneandonlyoreo
I'm trying to install probing on LinuxCNC 2.9 using the Axis GUI. The tab appears, with icons, when I run linuxcnc. When I click any buttons, I get errors that certain pins are not defined (ps_probe and such). These pins, I gather, are dynamically created by probe_screen.py.
I'm not sure where in the sequence it is executed but it appears in the [DISPLAY] section in the EMBED_TAB_COMMAND variable (with -u) and the postgui.hal file. In that HAL file, the current problem is that "loadusr -W psng/python/probe_screen.pl" causes linuxcnc to shutdown before the main GUI screen appears. The debug info says that probe_screen.py did not return. If I remove -W, the GUI launches and everything is fine until I try to interact with the items on the PSNG tab.
There are so many oddities in this install. For example, in probe_screen.py there are many calls to _("some string") which is an adaptation for other languages. Why it is used when gettext is not imported, I have no idea. I made a pass-through function that returns the string: def _(message): return message. I feel uneasy about making changes like this.
I'm an experienced linux user, programmer, and electrical engineer but this is kicking my ass. Has anyone else had problems like this? Should I be starting with a different version or fork? Is there some other way to get probing macros?
I'm not sure where in the sequence it is executed but it appears in the [DISPLAY] section in the EMBED_TAB_COMMAND variable (with -u) and the postgui.hal file. In that HAL file, the current problem is that "loadusr -W psng/python/probe_screen.pl" causes linuxcnc to shutdown before the main GUI screen appears. The debug info says that probe_screen.py did not return. If I remove -W, the GUI launches and everything is fine until I try to interact with the items on the PSNG tab.
There are so many oddities in this install. For example, in probe_screen.py there are many calls to _("some string") which is an adaptation for other languages. Why it is used when gettext is not imported, I have no idea. I made a pass-through function that returns the string: def _(message): return message. I feel uneasy about making changes like this.
I'm an experienced linux user, programmer, and electrical engineer but this is kicking my ass. Has anyone else had problems like this? Should I be starting with a different version or fork? Is there some other way to get probing macros?
Please Log in or Create an account to join the conversation.
- theoneandonlyoreo
- Away
- New Member
-
Less
More
- Posts: 8
- Thank you received: 0
24 May 2025 16:52 - 24 May 2025 16:54 #329062
by theoneandonlyoreo
Replied by theoneandonlyoreo on topic problems with Verser Probe Screen 2.9
It appears that the pins in question (probe.toolchange-change, etc) would be created by probe_screen.py.
In the INI file,
And from custom_postgui.hal
In the INI file,
EMBED_TAB_NAME=PSNG
EMBED_TAB_COMMAND=halcmd loadusr -Wn gladevcp gladevcp -c gladevcp -u psng/python/probe_screen.py -x {XID} psng/probe_screen.glade
EMBED_TAB_LOCATION = ntb_user_tabsAnd from custom_postgui.hal
# Ensure all toolchange pins are free to use
unlinkp iocontrol.0.tool-number
unlinkp iocontrol.0.tool-prep-number
unlinkp iocontrol.0.tool-change
unlinkp iocontrol.0.tool-changed
unlinkp iocontrol.0.tool-prepare
unlinkp iocontrol.0.tool-prepared
net tool-change probe.toolchange-change <= iocontrol.0.tool-change
net tool-changed probe.toolchange-changed => iocontrol.0.tool-changed
net tool-number probe.toolchange-number <= iocontrol.0.tool-number
net tool-prep-number probe.toolchange-prep-number <= iocontrol.0.tool-prep-number
net tool-prep-loopback iocontrol.0.tool-prepare <= iocontrol.0.tool-prepared
net tool-prep-loop iocontrol.0.tool-prepare <= iocontrol.0.tool-prepared
#loadusr -W probe_screen
loadusr -W /home/cnc/linuxcnc/configs/lycnc/psng/python/probe_screen.py
Last edit: 24 May 2025 16:54 by theoneandonlyoreo.
Please Log in or Create an account to join the conversation.
- Aciera
-
- Offline
- Administrator
-
Less
More
- Posts: 4368
- Thank you received: 1946
24 May 2025 17:30 - 24 May 2025 17:33 #329065
by Aciera
Replied by Aciera on topic problems with Verser Probe Screen 2.9
You need to remove this from your hal
You are already loading probe_screen.py with the EMBED_TAB_COMMAND in the INI.
To troubleshoot the pin problem, comment all lines with 'probe.' pins so the config starts up and use the 'Show Hal Configuration' tool to check if the pins are there.
loadusr -W /home/cnc/linuxcnc/configs/lycnc/psng/python/probe_screen.pyYou are already loading probe_screen.py with the EMBED_TAB_COMMAND in the INI.
To troubleshoot the pin problem, comment all lines with 'probe.' pins so the config starts up and use the 'Show Hal Configuration' tool to check if the pins are there.
Last edit: 24 May 2025 17:33 by Aciera.
Please Log in or Create an account to join the conversation.
- theoneandonlyoreo
- Away
- New Member
-
Less
More
- Posts: 8
- Thank you received: 0
24 May 2025 20:52 #329074
by theoneandonlyoreo
Replied by theoneandonlyoreo on topic problems with Verser Probe Screen 2.9
That's a good suggestion. I comment out the offending lines and looked around "Show HAL Configuration"
Turns out, probe.* pins don't exist. HOWEVER, gladevcp.* has all the pins that have been implicated, including gladevcp.toolchange-change and gladevcp.ps_probe_max
The Z-height probing routine kicks off a message complaining that probe.ps_probe_max is not available so I thought I'd try to name it at the outset. I tried using EBMED_TAB_COMMAND to adjust the component name with -c probe but that doesn't run.
I dug around some more and found a line in probe_screen.py that was commented out.I un-commented it and it may have this particular problem. Makes me nervous because there are other lines nearby that are commented out...
Thanks for the tip, Aciera. Great handle, too.
Turns out, probe.* pins don't exist. HOWEVER, gladevcp.* has all the pins that have been implicated, including gladevcp.toolchange-change and gladevcp.ps_probe_max
The Z-height probing routine kicks off a message complaining that probe.ps_probe_max is not available so I thought I'd try to name it at the outset. I tried using EBMED_TAB_COMMAND to adjust the component name with -c probe but that doesn't run.
EMBED_TAB_COMMAND=halcmd loadusr -Wn gladevcp gladevcp -c gladevcp -u psng/python/probe_screen.py -x {XID} psng/probe_screen.gladeI dug around some more and found a line in probe_screen.py that was commented out.
self.halcomp = hal.component( "probe" )Thanks for the tip, Aciera. Great handle, too.
Please Log in or Create an account to join the conversation.
- andypugh
-
- Offline
- Moderator
-
Less
More
- Posts: 23344
- Thank you received: 4953
25 May 2025 16:07 #329114
by andypugh
Replied by andypugh on topic problems with Verser Probe Screen 2.9
Which version of Linux, LinuxCNC and psng are you using?
I have done some work on psng to adapt it for Gtk3 / Python3 on Debian 12+
However, on my test machines, whilst it loads without errors, there are no graphics visible in the embedded tabs.
I have done some work on psng to adapt it for Gtk3 / Python3 on Debian 12+
However, on my test machines, whilst it loads without errors, there are no graphics visible in the embedded tabs.
Please Log in or Create an account to join the conversation.
Time to create page: 0.073 seconds