qtDragon toolchange and toollength setting

Machine is homed, G54 exists and everything works.
Using latest LinuxCNC from builtbot. Working probe and working toolsetter and even a touchplate.

qt.ini has line
DISPLAY = qtvcp -d qtdragon

---

Doing a tool change using the M61 Qn button (selecting a tool in the tool tab)



Nothing happens, no tool measurement

---

Doing a M6Tn in the MDI window

Message dialog appears for a manueal toolchange, click OK


Then LinuxCNC hangs and waits for something I guess... Noithing happens and I have to use the ESCAPE key to get LinuxCNC responding again.

after using ESC key multiple times:

---

For your information, tool probing in VersaProbe window works as it should.

---

LinuxCNC version and startup messages (with qtvcp debug on)


LINUXCNC - 2.9.0-pre0-5037-g5c3942cc4

Can you post your config files?"

cmorley wrote:

Can you post your config files?"
 

They are generated from pncconf. But sure I will attach them.

Hmmmm......there is a few things I see interesting,

qtNew.ini file
1. not using the qtdragon.pref file
2. don't have the macro's folder path
3. Don't list [PROBE] section
4. You pull in the qtdragon_postgui.hal but you also have the tool change commands in the qtNew.hal

I think #4 is most likely the issue, As when you are calling the M6 it can't give you the appropriate tool change popup dialouge box.

I would comment out the qtDragon_postgui.hal load in the qtNew.ini and test.

Flyer007 wrote:

Hmmmm......there is a few things I see interesting,

qtNew.ini file
1. not using the qtdragon.pref file
2. don't have the macro's folder path
3. Don't list [PROBE] section
4. You pull in the qtdragon_postgui.hal but you also have the tool change commands in the qtNew.hal

I think #4 is most likely the issue, As when you are calling the M6 it can't give you the appropriate tool change popup dialouge box.

I would comment out the qtDragon_postgui.hal load in the qtNew.ini and test.

 

As I mentioned before, it is a pncconf configuration. When I ask everybody is adamant that toolchangelength measurement should work. But nowhere does is say how.

I do get the proper dialog box. If I load the halmanualtoolchange module myself I get a warning and a very simple dialogbox. So it does work. Linuxcnc just stalls after clicking ok in the dialogbox.

I purged and removed LinuxCNC today and installed a totally fresh set of files. And it still doesnot work at all. Could it be that the version I use is too new? Maybe this whole toolchanging just doesn't work with pre2.9 I noticed that lots of files changed location and nowhere is that documented.
 
Thanks for taking the time (again) to look into this, it is very annoying to spend my time on this, I want to make chips and dust. I am about to go back to gmoccapy, that works good.

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.

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