SOLVED: Best start for QTDragon: Simulation or Axis config

Hi all,

I would like to start using QTDragon on my mill. I got Axis running with my new 2.8 PC in minutes. Works fine.
Now I want to start with QTDragon. I tried copying my Axis config and changed the manual tool change HAL as indicated in the manual.

I can home in QTDragon. However, when I start a gcode file, the file is not executed and no tool change dialog shows up.

Any hints? Should I rather start with the QTDragon sim config instead?

Thanks
Domca

nothing happens when you press cycle start? you are in Auto mode?

Hi Chris,

correct. I load the file, press cycle start and nothing happens. I will start LCNC today from the command line and review the log files. Had not had any time to do that yet. I just hoped anybody had a quick fix for this.

Thanks!

there is also a log file under status tab in qtdragon

Also if you can post your config files...

Hi Chris,

I am now on my machine. If I run the same ngc file in the sim version of qt dragon, the first thing that pops up is the tool change dialog. I don't get that on my real config. I already compared configs of the sim and my machine and could not find the difference.

I suspect the tool change dialog to be the problem.

Attached is my config and the ngc file I try to run. the qtdragon.pref.zip is not a zip. I just added.zip because of the file filter in the forum.

Thank you very much!

Try adding to HAL file


net tool-prep-loop iocontrol.0.tool-prepare iocontrol.0.tool-prepared
net tool-change-loop iocontrol.0.tool-change iocontrol.0.tool-changed

Hi Chris!

Thanks! The first line did it. It is now working.
However, if I also add the second line, I get an error:

custom_postgui.hal:4: Pin 'iocontrol.0.tool-change' was already linked to signal 'tool-change-loop'

I have the line
net tool-change hal_manualtoolchange.change <= iocontrol.0.tool-change
in my postgui.hal

Which of the two commands is required? Do I loose anything if I do not include the line
net tool-change-loop iocontrol.0.tool-change iocontrol.0.tool-changed

Thanks!

Skip the second line then - it must be already connected and I missed it