qtdragon_hd touchoff and probing issue
29 Aug 2023 23:10 #279326
by Vector
Replied by Vector on topic qtdragon_hd touchoff and probing issue
Awesome! (re fix to the auto_tool_probe sim for qtdragon)
Please Log in or Create an account to join the conversation.
30 Aug 2023 08:07 #279351
by cmorley
Replied by cmorley on topic qtdragon_hd touchoff and probing issue
unfortunately it didn't fix it. But I now have a system I can test installed versions on so can work a little less blindly.
Please Log in or Create an account to join the conversation.
30 Aug 2023 08:27 #279353
by cmorley
Replied by cmorley on topic qtdragon_hd touchoff and probing issue
qt_auto_tool_probe uses remap of m6 to add tool probing to tool changes.
It's integrated with Versa probe so you can control a few things such as probe speed.
It uses HAL pins read from Versa for this.
It also uses INI setting for tool change / tool probe location.
With a few changes in the NGC file you could ignore the Versa settings all together.
The rest of Versa probing ie material probing, doesn't need or use remap.
Parameters #5070 and #5063 are for probe results and current coordinates:
linuxcnc.org/docs/2.9/html/gcode/overvie...:overview-parameters
if you need to remap m6 for two different uses you would need to make a custom remap.
(I didn't read the printnc stuff to see what it is doing with M6.)
Chris
It's integrated with Versa probe so you can control a few things such as probe speed.
It uses HAL pins read from Versa for this.
It also uses INI setting for tool change / tool probe location.
With a few changes in the NGC file you could ignore the Versa settings all together.
The rest of Versa probing ie material probing, doesn't need or use remap.
Parameters #5070 and #5063 are for probe results and current coordinates:
linuxcnc.org/docs/2.9/html/gcode/overvie...:overview-parameters
if you need to remap m6 for two different uses you would need to make a custom remap.
(I didn't read the printnc stuff to see what it is doing with M6.)
Chris
The following user(s) said Thank You: tommylight
Please Log in or Create an account to join the conversation.
03 Sep 2023 23:45 #279768
by JohnnyCNC
Replied by JohnnyCNC on topic qtdragon_hd touchoff and probing issue
I'm finally get back to this. I am working on migrating from LCNC 2.8.4 + QTDragon to LCNC 2.9 + QTDragon_HD. I am also going to give Versa Probe a try. Right now, I am just playing with probing and preparing to get my M6 remap going. To do that I need to write some values to some custom numbered parameters from within Python. In probe_routines.py to be specific. How can I update a numbered parameter from within the Python code?
Thanks
John
Thanks
John
Please Log in or Create an account to join the conversation.
04 Sep 2023 08:17 #279798
by cmorley
Replied by cmorley on topic qtdragon_hd touchoff and probing issue
Parameters can currently only be manipulated in NGC files or remap python code.
Ui python can not directly set or read parameters.
Ui python can not directly set or read parameters.
Please Log in or Create an account to join the conversation.
04 Sep 2023 12:49 #279821
by JohnnyCNC
Replied by JohnnyCNC on topic qtdragon_hd touchoff and probing issue
Thanks Chris.
It just occurred to me how that I can get the data I need without storing it in a custom parameter. But before I do that and end up reinventing the wheel. My current workflow is:
Probe the work with a 3D probe:
At each tool change, via my remap, If the tool length in the tool table is > 0 then just use the tool with that offset. If the tool length is 0 then go to the tool setter and measure the tool and use the measured offset.
Is that possible using what already exists in Versa Probe and the Python remap?
Thanks
John
It just occurred to me how that I can get the data I need without storing it in a custom parameter. But before I do that and end up reinventing the wheel. My current workflow is:
Probe the work with a 3D probe:
At each tool change, via my remap, If the tool length in the tool table is > 0 then just use the tool with that offset. If the tool length is 0 then go to the tool setter and measure the tool and use the measured offset.
Is that possible using what already exists in Versa Probe and the Python remap?
Thanks
John
Please Log in or Create an account to join the conversation.
04 Sep 2023 14:49 #279835
by cmorley
Replied by cmorley on topic qtdragon_hd touchoff and probing issue
By modifying qt_auto_probe.ngc I think you could do what you want.
tool offset parameters are available in 5401-5409
Some experiments should tell the tale.
tool offset parameters are available in 5401-5409
Some experiments should tell the tale.
Please Log in or Create an account to join the conversation.
04 Sep 2023 15:44 #279840
by JohnnyCNC
Replied by JohnnyCNC on topic qtdragon_hd touchoff and probing issue
Thanks,
I will give it a try.
I will give it a try.
Please Log in or Create an account to join the conversation.
04 Sep 2023 16:40 #279846
by JohnnyCNC
Replied by JohnnyCNC on topic qtdragon_hd touchoff and probing issue
I took a look at qt_auto_probe.ngc. That looks like the place where I will apply the value at tool change that i saved when I probed the work with my 3D probe.
I save the location of Z minus the length of my probe in a custom parameter 4001-4008 representing G54-G59.2. This would need to happen in probe_routines.py. In 2.8.4 qtdragon this was done in probe_z_minus_wco.ngc. Today I have been trying call a .ngc file to save the value to #4001 using an mdi call from withing probe_down in probe_routines.py but no luck so far.
I save the location of Z minus the length of my probe in a custom parameter 4001-4008 representing G54-G59.2. This would need to happen in probe_routines.py. In 2.8.4 qtdragon this was done in probe_z_minus_wco.ngc. Today I have been trying call a .ngc file to save the value to #4001 using an mdi call from withing probe_down in probe_routines.py but no luck so far.
Please Log in or Create an account to join the conversation.
04 Sep 2023 18:31 #279858
by cmorley
Replied by cmorley on topic qtdragon_hd touchoff and probing issue
can you show your code?
Please Log in or Create an account to join the conversation.
Moderators: cmorley
Time to create page: 0.208 seconds