Linuxcnc stops executing ngc file for unknown reason

Hi, I'm experiencing an unknown issue,
the machine stops running at a specific line of the g-code sequence, the file is attached as fur_cutting_stop1824.ngc,
this issue repeatedly happens, and its the first time i encounter it.
i also attached a screen-shot when the machine stops as 1.png.
.ini and .hal config files are also provided.

i set the machine in auto run mode via python interface, the issue happened,
and I used the linuxcnc UI to run the fur_cutting_stop1824.ngc the issue happened,
with no error reported, and the positions of the axis are within allowed range.

could someone help me to identify the cause?

Your program at the bottom seems to go from positive z5. To a rapid of z0 with no retract. Could this be it?

giantstone wrote: could someone help me to identify the cause?

Is it hanging, versus stopping out of autorun?

Hanging occurs when some instant logical condition necessary to the new motion mode (g0 vs g1) is unsatisfied, while the previous mode didn't consider it necessary and thus ran fine.

A typical cause is the spindle-at-speed logic interfering with motion starts, when the at-speed signal is defective or misconfigured. There's no timeout or other error displayed, and things just hang. This can be intermittent and thus frustrating to debug, because if something changes in the machine, programs (that used to work) mysteriously stumble into the problem, and there's no messages to help you diagnose the source.

shouldn't be this reason because there are other lines the same as " z5 rapid to z0" and linuxcnc did not hang.

It looks like the program has stopped, rather than having hung (though I am not 100% sure that the Axis buttons update if the program is started from the Python interface, which you mentioned doing)

Did the spindle stop?

Waiting for spindle-at-speed is one possible explanation if the G-code is still running. But the GUI buttons do appear to show a stopped condition.

Do you have any hardware buttons connected to stop / pause?

andypugh wrote: But the GUI buttons do appear to show a stopped condition.

Yes, but he didn't indicate if that was the program's direct result, or he pressed stop himself after it was hanging.