- Posts: 572
- Thank you received: 115
Tool touch-off in QTDragon
Please Log in or Create an account to join the conversation.
- seebaer1976
- Offline
- Junior Member
-
- Posts: 37
- Thank you received: 5
JohnnyCNC wrote:
seebaer1976 wrote:
JohnnyCNC wrote:
I did some digging and found that QTDragon doesn't use the macros for the probing that happens on the Offsets and Tool screens. It is done in the Python code in qtdragon_handler.py file. I'm going to attempt to make a change so that any values that are shown, entered on the screen or in the .ini file are treated at units in the specified by LINEAR_UNITS in the .ini file. Having some values in MM and others in Inches is confusing. If successful I'll have to learn how to contribute changes."In 2.8 the macros for probing are in nc_files/probe/basicprobe/macros"
The macros are used for the probing done on the Probe screen. This is a great learning exercise.
Hi,
have the same problem that I don't get my manual tool change macro to work properly.
the marco calculates and the qtdragon_handler.py calculates again and this gives me a value that is twice as large.
Unfortunately I can't get any further because I can't program python.
qtdragon - new tool length after a manual tool change
best regards
I gave this remap a try but after the Z up where it waits for the tool change to happen I don't get a dialog where you indicate the tool change is complete.
hi, thanks for your help.
I get the dialog box that I have to confirm that I have changed the tool. he also does the touch test. only there is a double offset at the end.
under axis the script works fine, without errors.
think that in qtdragon_handler.py this code section could possibly be responsible for the duplication:
Please Log in or Create an account to join the conversation.
hi, thanks for your help.
I get the dialog box that I have to confirm that I have changed the tool. he also does the touch test. only there is a double offset at the end.
under axis the script works fine, without errors.
think that in qtdragon_handler.py this code section could possibly be responsible for the duplication:
I should have the remap working on my machine today. Then I will be able to see what is happening. You using are also using the touch plate button on the tool screen correct?
Thanks
John
Please Log in or Create an account to join the conversation.
- seebaer1976
- Offline
- Junior Member
-
- Posts: 37
- Thank you received: 5
JohnnyCNC wrote:
hi, thanks for your help.
I get the dialog box that I have to confirm that I have changed the tool. he also does the touch test. only there is a double offset at the end.
under axis the script works fine, without errors.
think that in qtdragon_handler.py this code section could possibly be responsible for the duplication:
I should have the remap working on my machine today. Then I will be able to see what is happening. You using are also using the touch plate button on the tool screen correct?
Thanks
John
yes i use too
I also just saw that c-morley missed an update on github in the '/nc_files/remap_lib/python-stdglue/stdglue.py', maybe that will help.
stdglue.py on github
I don't know how to correctly link it with the 'qtdragon_handler.py', because I don't have the python experience for.
mfg
markus
Please Log in or Create an account to join the conversation.
#2000=[#5063+#5223] (touch point + NP shift)
#2001=[#2000-#2002+#2003] (New - diff + old)
#2002=[#2000] (Remember the touch point old)
#2003=[#2001] (Remember offset old)
The above translates into:
#2000 = (Z Probe result + G54 Z Coordinate)
#2001=[#2000 - 0.0000 + 0.0000] (New - diff + old)
So in the end #2000 - #2003 all equal the same value.
I have it going through all the correct motions except it is missing the target Z for the top of the stock. I likely have something set improperly. So much more to learn. This is the first time I have had to really dig into the G-Code. Up until now the CAM program took care of it all.
Please Log in or Create an account to join the conversation.
- seebaer1976
- Offline
- Junior Member
-
- Posts: 37
- Thank you received: 5
Please Log in or Create an account to join the conversation.