Can't run first job with qtdragon_hd

Progress! It has to do with my toolchange operation. I started commenting out one line at a time in my gcode file and it was able to run after I commented out "T3 M6".

Now I just have to figure out why that's causing a problem.

Here are my toolchange related config settings. I'm using a manual toolchange operation. I want the machine to go to G53 X100 Y100 Z0. I have TOOL_CHANGE_QUILL_UP = 1 because I want it to raise Z all the way up before moving to the toolchange position.

In my INI, here's my EMCIO section:
In my postgui file, here's my tool change info. I've tried it with the unlinkp lines commented and uncommented, and it hasn't changed the behavior.
According to this , I expected a little message box to appear showing to facilitate the manual toolchange, but that never happened.

Try replacing the Tool.tbl file to the attached and everything will work.

It looks like my linuxcnc instance can't find the M6 tool change procedure. 

In my INI, I set PROGRAM_PREFIX like this:
Looking in that directory, there are a couple of tool change demo g-code files. Do I need to write one and name it "M6.ngc"? 

Ok so my previous post isn't right, that tab is just displaying descriptions of various gcodes from ~/linuxcnc-dev/lib/python/qtvcp/lib/mdi_text.py.

But I'm still pretty sure it has something to do with my toolchange configuration.

www.forum.linuxcnc.org/21-axis/42888-how...axis?start=10#213214

This fixed it. Looks like it was a problem with the dialog. This is the tool change section in my postgui file now:
 

Troubleshooting this only took 3 days, but hey, that's linux for you I guess.

So loading the tool_dialog is not necessary - it's included in the screen code.
I seem to remember you have multiple entries for tool change - some commented out.

I also fixed the LED color problem - the limits were like that too.

Yeah I think all the LEDs in the qtdragon_hd.ui file were green on and green off.

I did have the toolchange HAL settings in a few different places but I'm pretty sure I only ever had one set of them active. I've been trying to cobble together this config from a few different reference sources so I'm not 100% sure where the best place to put everything is. What file are you referring to for the "screen code"?

By screen code I mean the files that produce the screen. qtdragon - usually hidden from the user.

Qtvcp's builtin component is smart enough to check to see if the other toolchanger component is loaded - it will give a warning in the terminal about it but will use the previously loaded one.

Yes I understand it's hard to piece together a config from examples and best practices change over time.

in the file qtvcp_postgui.hal was the appropriate location to connect the signals for toolchanging. it's called after the qtdragon screen has initialized and added it's HAL pins.

Some sparse information here:
linuxcnc.org/docs/devel/html/gui/qtdragon.html#_hal_pins