Hi all, I'm hoping someone might have some insight into an error I encountered today. I have a roughly 11,000 line G code program, with a bad cutter compensation code (Length of cutter compensation entry move is not greater than the tool radius) about 4,500 lines into the program. The read-ahead doesn't see the error until the motion of the machine is about 1,500 lines into the program (~5 minutes of run time in). It reports the error at that point through the linuxcnc.error_channel, but continues to run until about line 2,800 and then halts (~8.5 minutes of run time in).
It seems like the interpreter is flushing some queue before stopping motion rather than aborting when it sees the error. Is this the intended behavior? I could abort from the UI when I encounter an error on the error_channel, but I would have assumed that the interpreter would have done that. Is this expected behavior? -John _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
