Spoilboard Surfacing - 2D Adaptive Clearing - Tool Bottoming Out

Air test identified need to increase the Y max machine limit by a hair so that the Y600 path would run.
Was just running the program and it was working like a charm, but about half-way though it just quit running.  Strange.  No VFD fault codes, spindle was cool to the touch.  I didn't catch at depth of cut it was running at time of program quitting.  No error indicators in Axis user interface.  I do think I need to reduce the feed rate during the cut.  Seemed it was beginning to chatter if I am assuming correctly that is in the indicator based on the pitch of noise being heard.

Anyone with suggestions for items to check for why the program would just abruptly stop?  Spindle turned off, it was if the 'E'-stop button was pressed, quite odd.

No immediate idea why it quit, but a helpful tool to debug is to run LCNC from the terminal.  Leave the terminal open in the background and if/when it stops you can check the terminal output.

The output may be cryptic when/if it vomits, but you can copy/paste the output - at least the last few lines before it stops - and paste it here.

tommylight wrote:

A few years back i had one such case where the machine would go into e-stop while working very rarely, this was a plasma CNC with parallel port control, turned out keyboard being near the main torch cable triggered it.
Removing keyboard and mouse cables as far from spindle and mains cables as a starting point, maybe...
 

Could be any number of things burping or causing interference I s'pose; the OptiPlex control computer, Mesa 7i76E, VFD,I dunno.  Appreciate your input.  The control computer and its accompanying keyboard are in the neighborhood of 3 feet, possibly a smidge more from enclosure, VFD and it's main cable.

Funny thing is, I created a second program that surfaced the short distance Y depth and it too quit about 1/3rd way into it.  Ran it a second time and it ran in its entirety.  Would seem there is an issue.  Think I will take spumco's suggestion and hopefully be provided some insight as to what is happening.

spumco wrote:

No immediate idea why it quit, but a helpful tool to debug is to run LCNC from the terminal.  Leave the terminal open in the background and if/when it stops you can check the terminal output.

The output may be cryptic when/if it vomits, but you can copy/paste the output - at least the last few lines before it stops - and paste it here.
 

I will certainly do as recommended.  Since the anomaly occurred twice, two different programs, it could be that it is easily repeatable.  Fun fun fun.  Appreciate the guidance.

- Darryl