LinuxCNC stops executing on this line of Gcode...

My GCODE is generated by AutoDesk Fusion CAM and it worked fine until I installed JA14. Now whenever I start a program when it gets to this line it just sits there and does not progress:

N20 G53 G0 Z0.

I think this is where it used to prompt a dialog asking me to hit continue once the tool was changed and maybe that is why it stops because it is waiting for me to hit okay, but the problem is there is no dialog. Any help would be appreciated, thank you

P.S. Complete file is attached.

Matt

Probably waiting for spindle at speed feedback at line N35. Runs in a sim fine.

JT

I watch the code execute in the window and it seems to stop on the N20 line. Does the line that is highlighted not necessarily represent the line it is stuck on?

It never had a problem before setting up the JA14 branch, it may not be the branch but perhaps something in my new configuration. Is there anything in the configuration I could change to continue execution? I do not see a way in Fusion to not write those lines and I do not really like having to edit the exported Gcode manually each time (which is what I am doing now in the interim).

Thanks.

To find out which line causes the problem comment them all out except the first and last then start uncommenting and testing. The file runs fine in a simulator.

JT

mjohnsonsa wrote: N20 G53 G0 Z0.

When it stops, is the spindle at the top of travel?

You mention not wanting to hand-edit the G-code, but that seems to hint that you have figured out what you need to do to the code to make it run?

However, this is the first motion line, so I am wondering if motion is disabled, or adaptive feed is zero, or rapid-overr0ide is set to zero, something like that?

I think this is where it used to prompt a dialog asking me
to hit continue once the tool was changed and maybe that is
why it stops because it is waiting for me to hit okay, but
the problem is there is no dialog.

If you are using hal_manualtoolchange and do not see the
'Tool change' popup dialog then you may have omitted
or improperly connected the tool change management
pins.

Typical hal connections for hal_manualtoolchange are:

Yes, it travels to the top limit and then just sits there, no prompts, no errors, nothing.

mjohnsonsa wrote: Yes, it travels to the top limit and then just sits there, no prompts, no errors, nothing.

OK, so it is completing the G53 G0 line, so must be stalling on the toolchange.

Have a look with halmeter at the iocontrol.0.tool-change pin and the iocontrol.0.tool-changed pin. If the former it 1 and the latter is 0 it's the situation that Dewey described.

This is what is in my .hal file and I did not put it there (at least not willingly, maybe I copied it from a sample file accidentally) I do not have any kind of tool changer and it looks like it is referencing IO so I am guessing that is my problem? Should I just remove it?


# ---toolchange signals for custom tool changer---

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

You can either short-circuit the loops or connect them to hal_manualtoolchange.

The second idea is probably better:
linuxcnc.org/docs/2.7/html/gui/axis.html#_manual_tool_change