qtDragon toolchange and toollength setting

Flyer007 wrote:

I am finishing a 3 axis mill right now using qtDragon_hd as gui.

Using 2.9pre from buildbot

Used pcconf to build base machine.
Followed documentation to change .ini to qtdragon requirements
Left the axis tool change dialouge over the QTpostgui one since it worked
using the basic probe screen

I can t99 m6 q43 in midi to prompt for a probe load. (M61 btn doesn't do offsets)
Probe in probe screen what I want and auto zero.
Then midi a t# m6 q43 to load whichever tool with offset in tool table I want (since I don't have tool sensor or plate)

So it is working in pre2.9

I will get my files up later as I am away from machine.
 

Ok, sounds good. Would love to see your files. Thanks for your troubles.

Ok, so here is the complete folder/s of my current machine, minus the screens to reduce space.

Note:  Work in progress troubleshooting a vistacnc PS4 MPG so some default pcconf items have been commented out.  

So looking at these INI files, neither have remap entries in them.
I think you two have talking of two different types of tool probing.

If you want auto tool probing (automatically move tool to probe and measure it when ever a tool change is requested), you need remap entries in the INI.

For instance in GMoccapy this describes what needed:
linuxcnc.org/docs/devel/html/gui/gmoccap...i_file_modifications

QtDragon would need similar entries

Weird stuff going on. Comparing my machine with the files Flyer sent.Flyer:
SUBROUTINE_PATH = /home/mill/linuxcnc/nc_files/probe/basic_probe/macros/Does not exist, fresh 2.9pre buildbot version (and NO I am not forgetting his home dir name)Me:
SUBROUTINE_PATH = /home/cnc/linuxcnc/nc_files/examples/probe/basic_probe/macros/
Does exist.

I added the M6 rules[RS274NGC]PARAMETER_FILE = linuxcnc.var
SUBROUTINE_PATH = /home/cnc/linuxcnc/nc_files/examples/probe/basic_probe/macros/
 I readded in .hal the

#  ---manual tool change signals---

loadusr -W hal_manualtoolchange
net tool-change-request     iocontrol.0.tool-change       =>  hal_manualtoolchange.change
net tool-change-confirmed   iocontrol.0.tool-changed      <=  hal_manualtoolchange.changed
net tool-number             iocontrol.0.tool-prep-number  =>  hal_manualtoolchange.number
net tool-prepare-loopback   iocontrol.0.tool-prepare      =>  iocontrol.0.tool-prepared

I even changed the probe line in .ini[PROBE]#USE_PROBE = versaprobeUSE_PROBE = basicprobe
 
And I get same results. Namely nothing, only that changed is that the 'old' style dialog box for a manual toolchange appears (which is logical since you use the loadusr -W hal_manualtoolchange
I suspect that there is some code in qtDragon that messes things up. When I add the loadusr -W hal_manualtoolchange line in the hal file I get the old dialog. But when I remove the line LinuxCNC does not start up and craps out with the message:
./qt.hal:339: Pin 'hal_manualtoolchange.change' does not exist


 

The path difference is just because where I put the macros.

Did you see Chris' note? What is the expected behavior you trying for right now?

cmorley wrote:

So looking at these INI files, neither have remap entries in them.
I think you two have talking of two different types of tool probing.

If you want auto tool probing (automatically move tool to probe and measure it when ever a tool change is requested), you need remap entries in the INI.

For instance in GMoccapy this describes what needed:
linuxcnc.org/docs/devel/html/gui/gmoccap...i_file_modifications

QtDragon would need similar entries
 

That is indeed what I am looking for.  I thought I mentioned before that the gmoccapy way does not work in the new version of LinuxCNC and qtDragon. I used to use gmoccapy and the behaviour for toolchange and measuring is exactly what I want in qtDragon.
Will try one more time, if it doesn't work I will change back to gmoccapy (not happy about that prospect).