LinuxCNC 2.10 becomes unresponsive if aborted during tool change #3675
Description
Tested with 2.9 too, behaviour is as-expected there.
To reproduce use a simple G-code routine with tool changes.
eg
M6 T1 G43
G1 F50 X10
M6 T2 G43
G1 F50 X10
M2
Open LinuxCNC and sim-axis config
Load the file, and open the Halshow window.
Add iocontrol.0.tool-change and tool-changed
unlink tool-changed (right click on the pin in halshow watch is the easiest way to go)
Open a terminal and set up python to send aborts:
python3
import linuxcnc
c=linuxcnc.command
c.abort()
Run the code and send an abort during normal motion. The program stops, all is well, the program can be re-started.
See that manually toggling tool-changed in halshow when tool-change is set allows the tool-changes to complete.
Now send an abort from Python while tool-change is set and without having set tool-changed, so that the system thinks it is mid-change.
In my testing the machine can then not be caused to re-run the G-code, or do MDI, or very much at all.
Metadata
Metadata
Assignees
Type
Projects
Status