QTDragon_hd with auto toollength measurement

I found this example that was my starting point for my previous gmoccapy installation. The workflow is described at the end and is the same as min.

vers.by/en/blog/archive/auto-tool-measurement

Ok thanks for explaining and maybe re-explaining

couple more questions.
What version of linuxcnc are you using?
Can you test the sim config of qtDragon_hd to see if it's toolchange dialog works?

I will do a little more investigating..

the python based remap will honour such settings of tool change position, spindle on or off,G30 based on the usual INI settings.
tool setter position and probing speed would be added INI setting - at least at the moment.

thanks

Ok I think we are getting somewhere...

in your qtdragon main HAL file look for (near the bottom)

change to:
And let me know if the tool change dialog works.

Chris

and I stand corrected - Gmoccapy does have auto tool probing built in
More investigating...

cmorley wrote:

and I stand corrected - Gmoccapy does have auto tool probing built in
More investigating...
 

You are more a detective now then a programmer Keep up the good work. QTDragon will be great if the M6 T commands are remapped and some nice dialog boxes appear.

>What version of linuxcnc are you using?

Using the buildbot version of 2.9 pre, so almost every day a new version

>Can you test the sim config of qtDragon_hd to see if it's toolchange dialog works?

I did, and it does not work in the sim configuration

>the python based remap will honour such settings of tool change position, spindle on or off,G30 based on the usual INI settings.
tool setter position and probing speed would be added INI setting - at least at the moment.

I was not really clear in what I meant with not putting all the functionality in a python script. I should have said that what would be nice is that all the movement commands would be in seperate .ngc files. The .ngc files contain g-code, that is a language that most users of LinuxCNC speak for sure. That way machinists (like myself) can adept the code to suit their particular machine. Most other remap routines work that way and it is very flexible (once the user gets it working).

Really appreciating the time and effort you are putting into this. A lot of users will benefit from the very nice UI that qtDragon is and soon the remapped routines for a tool change.
I will be happy to test things out on my machine.