qtdragon_hd touchoff and probing issue
04 Sep 2023 19:20 #279869
by JohnnyCNC
Replied by JohnnyCNC on topic qtdragon_hd touchoff and probing issue
I've tried this:
rtn = self.CALL_MDI_WAIT("o900", self.timeout)
if rtn != 1:
return 'o900 failed: {}'.format(rtn)
and this:
ACTION.CALL_MDI("o900")
This is the contents of o900.ngc although I have tried a number of variations.
%
o<0900> sub
(PRINT,Doing o900 stuff)
#4002 = 9.8765432
o<o900> endsub
%
rtn = self.CALL_MDI_WAIT("o900", self.timeout)
if rtn != 1:
return 'o900 failed: {}'.format(rtn)
and this:
ACTION.CALL_MDI("o900")
This is the contents of o900.ngc although I have tried a number of variations.
%
o<0900> sub
(PRINT,Doing o900 stuff)
#4002 = 9.8765432
o<o900> endsub
%
Please Log in or Create an account to join the conversation.
04 Sep 2023 22:47 - 04 Sep 2023 22:47 #279893
by cmorley
Replied by cmorley on topic qtdragon_hd touchoff and probing issue
I think it is working (I tested too) but in probe routines you can't print any msgs.
I just added: ACTION.CALL_MDI("#4002 = 9.8765432") into probe down.
How do I know it worked? I'll tell you a voodoo trick.
after running probe 'down' go to the MDI entry.
enter these commands one after the other:
;py,from interpreter import *
:py, print(this.parameters[4002]))
then look in the terminal for the output.
you should see that parameter 4002 is set to 9.8765432
Chris
I just added: ACTION.CALL_MDI("#4002 = 9.8765432") into probe down.
How do I know it worked? I'll tell you a voodoo trick.
after running probe 'down' go to the MDI entry.
enter these commands one after the other:
;py,from interpreter import *
:py, print(this.parameters[4002]))
then look in the terminal for the output.
you should see that parameter 4002 is set to 9.8765432
Chris
Last edit: 04 Sep 2023 22:47 by cmorley.
Please Log in or Create an account to join the conversation.
05 Sep 2023 00:41 #279901
by JohnnyCNC
Replied by JohnnyCNC on topic qtdragon_hd touchoff and probing issue
Thank you Chris,
I was checking to see if it worked by exiting LCNC and looking in the linuxcnc.var file. I'm going to go give it a try.
John
I was checking to see if it worked by exiting LCNC and looking in the linuxcnc.var file. I'm going to go give it a try.
John
Please Log in or Create an account to join the conversation.
05 Sep 2023 01:00 #279903
by JohnnyCNC
Replied by JohnnyCNC on topic qtdragon_hd touchoff and probing issue
Thanks again Chris. It is working great.
Now to learn about doing an M6 remap in Python.
John
Now to learn about doing an M6 remap in Python.
John
Please Log in or Create an account to join the conversation.
05 Sep 2023 01:44 #279908
by cmorley
Replied by cmorley on topic qtdragon_hd touchoff and probing issue
keep us posted!
Please Log in or Create an account to join the conversation.
10 Sep 2023 14:39 - 10 Sep 2023 14:39 #280402
by JohnnyCNC
Replied by JohnnyCNC on topic qtdragon_hd touchoff and probing issue
Using Versa Probe, how do I set the Auto_Zero function to default to ON?
What would the use case be where you would want it to be OFF?
What would the use case be where you would want it to be OFF?
Last edit: 10 Sep 2023 14:39 by JohnnyCNC.
Please Log in or Create an account to join the conversation.
10 Sep 2023 18:10 #280420
by cmorley
Replied by cmorley on topic qtdragon_hd touchoff and probing issue
There is a button 'Tool Measure' on the versa probe screen that turns it off or on.
I would guess if you are repeating a program that only uses one tool.
You could change the qt_auto_probe.ngc to ignore the button state if you like.
I would guess if you are repeating a program that only uses one tool.
You could change the qt_auto_probe.ngc to ignore the button state if you like.
Please Log in or Create an account to join the conversation.
11 Sep 2023 11:43 #280472
by rodw
Replied by rodw on topic qtdragon_hd touchoff and probing issue
Heare, Hear, I really think Chris took a wrong turn a long time ago.Thanks Chris.
Having the purple dot in the cross-hair doesn't make sense to me. Having the purple dot show where to place the probe tip and the cross-hair show where zero will be after the probing is completed is how I interpreted the image the first time I saw it. I found the images and can have it the way I like it. LOL
I can wait tyo try the functions on the UTILS tab. I always wanted something like that.
Are probe_basic and basic_probe the same thing?
Thanks
John
The following user(s) said Thank You: nwallace
Please Log in or Create an account to join the conversation.
11 Sep 2023 22:22 #280505
by JohnnyCNC
Replied by JohnnyCNC on topic qtdragon_hd touchoff and probing issue
I've since switched to Versa Probe but I liked the graphics in basic_probe better. I got the touch-off working with my M6 remap at least basically. I have now commited to switching to my ODroid H2+, with Debian and LCNC 2.9.
Please Log in or Create an account to join the conversation.
08 Jan 2024 00:21 #290168
by JohnnyCNC
Replied by JohnnyCNC on topic qtdragon_hd touchoff and probing issue
I finally got my workpiece touch-off using a 3D probe and my M6 remap with auto tool measurement working in QTDragon_HD. My M6 remap is now all Python. I am using VersaProbe at this time. I still need to try BasicProbe and see which one I like better.Hi Chris,
yes you are right, tested on the machine: measuring a tool with the tool sensor actually sets the Z of current WCS.
Of course, if you follow this by measurement of the workpiece with the workpiece tool probe, current WCS Z previously set get overwritten by this - as expected.
Anyone here actually using qtdragon_hd with both tool sensor and workpiece probe?
With older qtdragon all of this is handled by ngc probing subs, most likely this is why this got unnoticed.
Please Log in or Create an account to join the conversation.
Moderators: cmorley
Time to create page: 0.178 seconds