Work with probe
09 Feb 2021 20:52 #198199
by andypugh
Replied by andypugh on topic Work with probe
Are you homed?
Please Log in or Create an account to join the conversation.
09 Feb 2021 22:12 #198206
by CBollweg
Replied by CBollweg on topic Work with probe
Of course
Please Log in or Create an account to join the conversation.
09 Feb 2021 22:25 #198208
by andypugh
Replied by andypugh on topic Work with probe
I don't know, then.
I guess you can jog the machine normally, but the buttons on the probe screen don't work?
I guess you can jog the machine normally, but the buttons on the probe screen don't work?
Please Log in or Create an account to join the conversation.
10 Feb 2021 00:23 #198228
by CBollweg
Replied by CBollweg on topic Work with probe
Yes, joging is possible, only the buttons on the probe screen don't work.
Please Log in or Create an account to join the conversation.
10 Feb 2021 09:32 #198255
by andypugh
Replied by andypugh on topic Work with probe
Looking in the glade file:
github.com/verser-git/probe_screen_v2/bl...e_screen.glade#L1117
The jog buttons should call the handler "on_btn_jog_pressed"
This should be handled in the python file:
github.com/verser-git/probe_screen_v2/bl...probe_screen.py#L360
That contains a comment about being in manual mode. Which GUI are you using? Some make manual mode more obvious than others.
I would be tempted to add a tell-tale in on_btn_pressed to make sure that the routine is called. something like "print("somebody pressed my buttons")" right after the def command, and indented the same as the self.command.mode line.
(Though I think you would need to start linuxcnc from the command line to _see_ the output of the print command. If you don't know how to do that, just open a terminal and type "linuxcnc")
github.com/verser-git/probe_screen_v2/bl...e_screen.glade#L1117
The jog buttons should call the handler "on_btn_jog_pressed"
This should be handled in the python file:
github.com/verser-git/probe_screen_v2/bl...probe_screen.py#L360
That contains a comment about being in manual mode. Which GUI are you using? Some make manual mode more obvious than others.
I would be tempted to add a tell-tale in on_btn_pressed to make sure that the routine is called. something like "print("somebody pressed my buttons")" right after the def command, and indented the same as the self.command.mode line.
(Though I think you would need to start linuxcnc from the command line to _see_ the output of the print command. If you don't know how to do that, just open a terminal and type "linuxcnc")
Please Log in or Create an account to join the conversation.
11 Feb 2021 12:51 #198387
by CBollweg
Replied by CBollweg on topic Work with probe
Hi andy,
thanks for your answer. When i start linuxcnc in the terminal i get:
/usr/lib/python2.7/dist-packages/gladevcp/tooledit_widget.py:64: GtkWarning: Invalid input string
self.wTree.add_from_file(os.path.join(datadir, "tooledit_gtk.glade") )
/usr/lib/python2.7/dist-packages/gladevcp/tooledit_widget.py:401: GtkWarning: Invalid input string
renderer.set_property('visible', bool)
**** probe_screen GETINIINFO ****
Preference file path: /home/hafven/linuxcnc/configs/Backup/probescreen_axis/probescreen_axis.pref
**** PROBE SCREEN INFO ****
**** To many increments given in INI File for this screen ****
**** Only the first 5 will be reachable through this screen ****
46137347
toolnumber = 0 False
thanks for your answer. When i start linuxcnc in the terminal i get:
/usr/lib/python2.7/dist-packages/gladevcp/tooledit_widget.py:64: GtkWarning: Invalid input string
self.wTree.add_from_file(os.path.join(datadir, "tooledit_gtk.glade") )
/usr/lib/python2.7/dist-packages/gladevcp/tooledit_widget.py:401: GtkWarning: Invalid input string
renderer.set_property('visible', bool)
**** probe_screen GETINIINFO ****
Preference file path: /home/hafven/linuxcnc/configs/Backup/probescreen_axis/probescreen_axis.pref
**** PROBE SCREEN INFO ****
**** To many increments given in INI File for this screen ****
**** Only the first 5 will be reachable through this screen ****
46137347
toolnumber = 0 False
Please Log in or Create an account to join the conversation.
11 Feb 2021 12:57 #198388
by CBollweg
Replied by CBollweg on topic Work with probe
Using the axis gui.
Also using a xhc-whb04-06. May that course Problems ?
Also using a xhc-whb04-06. May that course Problems ?
Please Log in or Create an account to join the conversation.
11 Feb 2021 13:06 #198389
by andypugh
Replied by andypugh on topic Work with probe
Did you add a debug print to the Python handler? And is anything printed when you press the button?
It is _possible_ that the too-many-increments is breaking it.
It is _possible_ that the too-many-increments is breaking it.
Please Log in or Create an account to join the conversation.
11 Feb 2021 13:14 #198390
by alkabal
Replied by alkabal on topic Work with probe
Maybe you can try revised version :
github.com/alkabal/probe-screen-ng
or
github.com/linuxcnc-probe-screen/probe-screen-ng
Yes you need to have less than 5 value for jog increment in you ini file
[DISPLAY]
...
...
INCREMENTS = 1mm .1mm .05mm .01mm .001mm
I also use a XHC-WHB04b-6 with revised probe screen.
github.com/alkabal/probe-screen-ng
or
github.com/linuxcnc-probe-screen/probe-screen-ng
Yes you need to have less than 5 value for jog increment in you ini file
[DISPLAY]
...
...
INCREMENTS = 1mm .1mm .05mm .01mm .001mm
I also use a XHC-WHB04b-6 with revised probe screen.
Please Log in or Create an account to join the conversation.
11 Feb 2021 13:30 #198392
by CBollweg
Replied by CBollweg on topic Work with probe
ok, i had 7 Increments. Changed this an will try later on
Please Log in or Create an account to join the conversation.
Time to create page: 0.112 seconds