Gmoccapy Stop Mid-Run

Hobby 3-axis mill, Raspberry Pi 4B, official download - reports as Gmoccapy 3.4.6.
Done several jobs since swapping from AXIS.

Running code - then stop.
No pop-up messages.
Found the Gmoccapy Log - nothing.

Cancelled job, but machine would not jog.
De-activate controls (Green/Red PB), then activate - machine jogs.

Need some hints on where to look, or a list of typical problems.
Thanks,
John.

 

That is a not known problem.

Running code means MDI Macros or commands, or AUTO programs?

How do your code end? 
I recommend M2 as stop

Running a code file in AUTO, as accomplished many times before.

Code generated by CamBam from a FreeCad stl model.
Code end is M30.

One problem was that when the machine stopped, the line-of-code highlight also disappeared.
But, on reflection, I could have inspected the cutter position on the DRO and estimated the last successful line reasonably closely.
Then do a "start-from-here", CAREFULLY.

Is there any way to get the machine to record each code line as it is completed ?
Just line number that is overwritten each line would be sufficient.
Then I could read that location after a stop to identify bad code.

I do not know a solution to do what you are asking for.
The question for me is, why the code stops?

If you just press pause, the program will continue after you pressed resume.

also recording the line might not help, as the interpreter reads ahead and so machining line 1000 interpreter may have already passed Line 1250

I imagine using python and code an own control might work.

Norbert

The machine was unattended (briefly) as I moved around the workshop.

I admit that, if the machine was in the Pause state, I may not have noticed it.
Better error/status reporting next time.

I use standard USB mouse and keyboard.
This fault could indicate some EMI effect on one of those connections.

I found in the manual:
- gmoccapy.program.current-line (s32 OUT) - Indicates the current working line of the program.
Need then to generate a display, or memory location, with a one event memory.

Thanks for the comments,
John.

Was this an one time fault or did it happen again with this g-code file? Or also with other files?

The easiest way to get the last line is to monitor the pin gmoccapy.program.current-line with halscope.