LinuxCNC stops executing on this line of Gcode...
- mjohnsonsa
- Offline
- Senior Member
-
- Posts: 51
- Thank you received: 0
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
Please Log in or Create an account to join the conversation.
JT
Please Log in or Create an account to join the conversation.
- mjohnsonsa
- Offline
- Senior Member
-
- Posts: 51
- Thank you received: 0
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.
Please Log in or Create an account to join the conversation.
JT
Please Log in or Create an account to join the conversation.
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?
Please Log in or Create an account to join the conversation.
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:
net tool-change <= iocontrol.0.tool-change
net tool-change => hal_manualtoolchange.change
net tool-changed <= hal_manualtoolchange.changed
net tool-changed => iocontrol.0.tool-changed
net tool-prep-loop <= iocontrol.0.tool-prepare
net tool-prep-loop => iocontrol.0.tool-prepared
net tool-prep-number => hal_manualtoolchange.number
net tool-prep-number <= iocontrol.0.tool-prep-number
Please Log in or Create an account to join the conversation.
- mjohnsonsa
- Offline
- Senior Member
-
- Posts: 51
- Thank you received: 0
Please Log in or Create an account to join the conversation.
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.
Please Log in or Create an account to join the conversation.
- mjohnsonsa
- Offline
- Senior Member
-
- Posts: 51
- Thank you received: 0
# ---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
Please Log in or Create an account to join the conversation.
The second idea is probably better:
linuxcnc.org/docs/2.7/html/gui/axis.html#_manual_tool_change
Please Log in or Create an account to join the conversation.