The attached job file and associated G-code fails to load and run in Mach.

At the line where the tool changes to Tool 12, there is a status message that says "nested comment found, Block = M06 T12"

Whats the problem here? It ran up to that point and went thru a couple of tool changes?

Side question (since I can't run the code and I'm just getting used to these wizards), does it stop at the tool change so I can manually change the tool and can I reset Z then to adjust for tool length, since the tool table gives me no length values. I have NMTB 30 holders, so I can measure and fix all the tool lengths, but there's no way I see to enter that into the table.

That line has a comment on it - M06 T13 (Center drill)- I think mach3 objects to comments on the same line as code. You can change the setting in the new job dialog to not show comments, or simply edit that line and add an <enter> key to make the comment appear on a new line. I will fix the program to do that.

On the General Config screen, near the top left of the page is a radio box for tool change- you have 3 choices, Ignore, stop and wait for start, or auto tool changer. You want to set it to stop.

Yes, if you have repeatable tool holders you can set up the tool table so it will automatically set the Z values when you make a tool change. How to do it is more complicated than I can write here, have a look at the mach manual for details. There may also be a video on it.

No-the T13 line works ok, it's down about line 50 where the T12 tool change is that hangs it up.

This is your problem,

M06 T12 (end mill (long))  <------- Parenthases inside of parenthases


It sees it as a message inside a message (nested)    (xx(yy))

(;-) TP

Look in your tool table (NFW) and see if the description for tool #12 is (long) if so change it to just LONG.

Just a  thought, (;-) TP

I have already fixed the code to make the comment on a new line, but it looks like that is not the real problem. It will be harder to be sure no nested parens occurs, but I guess Ill have to do it.

Thanks. Changing the tool table entry to remove the parentheses cleared it up.

ROn you really should change it back to the same line. The notes are there for a reason and it can be confusing if the NOTE is actually on another line.

(;-) TP

Yes, I guess a comment on a line with code is OK. I should have figured that since no one had trouble with that before.