Category: Basic Configuration
I broke a brand new (happily inexpensive!) bit today. Right after program start, the spindle shut down, and the work kept going. I hit E-stop, but not in time.
The culprit was code generated by kirimoto, which contained an M6 for an initial tool change. I missed it when configuring kirimoto -- that M6 shouldn't have been there -- but even so, it should have paused.
It's reproducible -- M6 shuts down the spindle, but the program keeps going.
I use hal_manualtoolchange, set up pretty much by the book:
# ---manual tool change signals---
net tool-change-request <= iocontrol.0.tool-change
net tool-change-confirmed => iocontrol.0.tool-changed
net tool-number <= iocontrol.0.tool-prep-number
# ---Use external manual tool change dialog---
loadusr -W hal_manualtoolchange
net tool-change-request => hal_manualtoolchange.change
net tool-change-confirmed <= hal_manualtoolchange.changed
net tool-number => hal_manualtoolchange.number
# ---ignore tool prepare requests---
net tool-prepare-loopback iocontrol.0.tool-prepare => iocontrol.0.tool-prepared
The only mention of tools in the .ini is "TOOL_TABLE = tool.tbl" in EMCIO.
I ran halshow, watching the hal_manualtoolchange pins, and the ioctrontrol tool-* pins. The iocontrol.0.tool-prepare/prepared loopback flashes on briefly when I hit M6, but that's the only change I can see. (I didn't use halscope.)
Any ideas? Am I missing some config?
