hal setup for probe
11 Sep 2020 01:10 #181695
by lllars
hal setup for probe was created by lllars
What do I need in my hal file to get probing working in QtDragon?
The probe gui seems to be working fine, but there's no response when I trigger the probe. For example, if I tap on one of the buttons to probe an outside corner, then the machine starts jogging the x-axis. I then bump the probe with my hand, but the machine just keeps jogging as though nothing happened.
Here's what I've got in my hal file at the moment, comments show other things I've tried:
I've verified that qtdragon.hal_led_probe, hm2_7i95.0.inmux.00.input-14-not, and motion.probe-input all turn yellow in Hal Show when I bump the probe.
The probe gui seems to be working fine, but there's no response when I trigger the probe. For example, if I tap on one of the buttons to probe an outside corner, then the machine starts jogging the x-axis. I then bump the probe with my hand, but the machine just keeps jogging as though nothing happened.
Here's what I've got in my hal file at the moment, comments show other things I've tried:
# --- Probe ---
# net qtdragon.hal_led_probe <= hm2_7i95.0.inmux.00.input-14
# net probe_in <= hm2_7i95.0.inmux.00.input-14
# net probe-in => motion.probe-input
# net probe-in hm2_7i95.0.inmux.00.input-14-not => motion.probe-input
net qtdragon.hal_led_probe hm2_7i95.0.inmux.00.input-14-not => motion.probe-input
# net qtdragon.hal_led_probe <= probe_inI've verified that qtdragon.hal_led_probe, hm2_7i95.0.inmux.00.input-14-not, and motion.probe-input all turn yellow in Hal Show when I bump the probe.
Please Log in or Create an account to join the conversation.
11 Sep 2020 04:28 #181718
by cmorley
Replied by cmorley on topic hal setup for probe
IIRC the probe rapids to position first -rapids won't stop it the probe trips - only feed moves. (i've bent a probe because of a rapid)
net probe_in hm2_7i95.0.inmux.00.input-14
net probe-in motion.probe-input qtdragon.hal_led_probe
The probe LED on the screen should follow the probe contact ( test by hand )
you could also watch the motion.probe-in pin on halmeter to confirm.
Chris
net probe_in hm2_7i95.0.inmux.00.input-14
net probe-in motion.probe-input qtdragon.hal_led_probe
The probe LED on the screen should follow the probe contact ( test by hand )
you could also watch the motion.probe-in pin on halmeter to confirm.
Chris
The following user(s) said Thank You: lllars
Please Log in or Create an account to join the conversation.
11 Sep 2020 17:07 #181775
by lllars
Replied by lllars on topic hal setup for probe
Thanks for the feedback!
I was getting scared off by the rapid, thanks for that hint. The probe appears to be working correctly when it goes into the final feed move. It is definitely disconcerting that the machine doesn't stop when the probe triggers before that move though.
The on-screen probe LED never lights up. Not even during probing. I checked Hal Show for hal_led_home_p, and confirmed that pin is not triggered by probe action. Do I need a line for that in my hal file?
Also I tried the two "net" lines you provided, but that gives me an error on startup:
I was getting scared off by the rapid, thanks for that hint. The probe appears to be working correctly when it goes into the final feed move. It is definitely disconcerting that the machine doesn't stop when the probe triggers before that move though.
The on-screen probe LED never lights up. Not even during probing. I checked Hal Show for hal_led_home_p, and confirmed that pin is not triggered by probe action. Do I need a line for that in my hal file?
Also I tried the two "net" lines you provided, but that gives me an error on startup:
Debug file information:
Can not find -sec RS274NGC -var PARAMETER_FILE -num 1
Note: Using POSIX realtime
./dynamyte_4000.hal:65: Pin 'qtdragon.hal_led_probe' does not exist
5047
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtimePlease Log in or Create an account to join the conversation.
11 Sep 2020 18:28 #181780
by cmorley
Replied by cmorley on topic hal setup for probe
any qtdragon related pins must be connected in the post gui file.
Please Log in or Create an account to join the conversation.
11 Sep 2020 19:12 #181785
by lllars
Replied by lllars on topic hal setup for probe
hmm... still no on-screen LED despite trying all the permutations I can think of.
I currently have in my normal hal file (dynamyte_4000.hal):
And in qtdragon_postgui.hal:
This works for probing, just doesn't illuminate the LED
Note that it seems my version of qtdragon (derived from the full hd version) uses qtdragon.hal_led_home_p instead of qtdragon.hal_led_probe (mentioned in the qtdragon doc here: linuxcnc.org/docs/2.8/html/gui/qtdragon.html#_hal_pins)
I currently have in my normal hal file (dynamyte_4000.hal):
net probe-in motion.probe-input <= hm2_7i95.0.inmux.00.input-14-notAnd in qtdragon_postgui.hal:
net probe-in qtdragon.hal_led_home_pThis works for probing, just doesn't illuminate the LED
Note that it seems my version of qtdragon (derived from the full hd version) uses qtdragon.hal_led_home_p instead of qtdragon.hal_led_probe (mentioned in the qtdragon doc here: linuxcnc.org/docs/2.8/html/gui/qtdragon.html#_hal_pins)
Please Log in or Create an account to join the conversation.
11 Sep 2020 20:32 #181789
by lllars
Replied by lllars on topic hal setup for probe
Is there any documentation for the basic probe gui? I haven't been able to find anything substantial.
I'm currently struggling with getting calibration working. There are 3 rows of fields at the bottom of the probe gui. The rows starting with "clear x", "clear y", "clear all" buttons. Are these meant to display the calibration values? They are all 0's for me.
I've been running the calibration routine for an internal diameter. It does not populate those rows. I've found www.linuxcnc.org/docs/devel/html/gui/qtv...ets.html#_basicprobe which states:
And the link in my last post says:
So I have those lines in my qtdragon_postgui.hal. Am I meant to customize them for my setup in any way? If so, I don't understand what I need to do.
Initially I was getting an error and the calibration routing would not run. The error was 'NameError: global name "ngc" is not defined'. I fixed(?) that by changing "ngc" to "sub" in line 274 of basic_probe.py (under def cal_btn_clicked)
Now the cal routine runs, but does not populate those 3 rows. It also gives me lots of errors in status window. See attached photo.
I'm currently struggling with getting calibration working. There are 3 rows of fields at the bottom of the probe gui. The rows starting with "clear x", "clear y", "clear all" buttons. Are these meant to display the calibration values? They are all 0's for me.
I've been running the calibration routine for an internal diameter. It does not populate those rows. I've found www.linuxcnc.org/docs/devel/html/gui/qtv...ets.html#_basicprobe which states:
requires extra analog motion pins for probe settings.And the link in my last post says:
These pins must be connected in the postgui file for probing to work:
net xwidth motion.analog-out-00 => qtdragon.x_width
net ywidth motion.analog-out-01 => qtdragon.y_width
net avg_dia motion.analog-out-02 => qtdragon.avg_diameter
net edge_angle motion.analog-out-03 => qtdragon.edge_angle
net edge_delta motion.analog-out-04 => qtdragon.edge_delta
net xminus motion.analog-out-05 => qtdragon.x_minus
net yminus motion.analog-out-06 => qtdragon.y_minus
net zminus motion.analog-out-07 => qtdragon.z_minus
net xplus motion.analog-out-08 => qtdragon.x_plus
net yplus motion.analog-out-09 => qtdragon.y_plus
net xcenter motion.analog-out-10 => qtdragon.x_center
net ycenter motion.analog-out-11 => qtdragon.y_center
net cal_offset motion.analog-out-12 => qtdragon.cal_offsetSo I have those lines in my qtdragon_postgui.hal. Am I meant to customize them for my setup in any way? If so, I don't understand what I need to do.
Initially I was getting an error and the calibration routing would not run. The error was 'NameError: global name "ngc" is not defined'. I fixed(?) that by changing "ngc" to "sub" in line 274 of basic_probe.py (under def cal_btn_clicked)
cmd = "PROBE {} {}".format(sub, parms)Now the cal routine runs, but does not populate those 3 rows. It also gives me lots of errors in status window. See attached photo.
Please Log in or Create an account to join the conversation.
11 Sep 2020 20:36 #181790
by PCW
Replied by PCW on topic hal setup for probe
The error message is telling you what to fix...
you need to increase the number of AIO pins
man motion
you need to increase the number of AIO pins
man motion
Please Log in or Create an account to join the conversation.
11 Sep 2020 20:55 #181794
by lllars
Replied by lllars on topic hal setup for probe
Oh duh. Now that you mention it I even remember reading that instruction and deciding to ignore it because I wasn't sure if it applied to my hardware (7i95 btw).
So Thanks! That fixed most of the error messages. I am still getting one though: "Unknown oword number", and the 3 rows still are not populated
So Thanks! That fixed most of the error messages. I am still getting one though: "Unknown oword number", and the 3 rows still are not populated
Please Log in or Create an account to join the conversation.
12 Sep 2020 02:53 #181813
by cmorley
Replied by cmorley on topic hal setup for probe
can you post terminal printout when it errors?
Please Log in or Create an account to join the conversation.
12 Sep 2020 16:45 #181900
by lllars
Replied by lllars on topic hal setup for probe
Ok, I found a major issue: qtdragon_postqui.hal wasn't being loaded. Instead, my ini file had:which was just an empty file.
So, I fixed that, and the on-screen probe led is now working. But, otherwise the behavior is the same. Still getting the oword warning and blank calibration data.
I've attached my console output.
POSTGUI_HALFILE = custom_postgui.halSo, I fixed that, and the on-screen probe led is now working. But, otherwise the behavior is the same. Still getting the oword warning and blank calibration data.
I've attached my console output.
Please Log in or Create an account to join the conversation.
Moderators: cmorley
Time to create page: 0.083 seconds