How can I continue g-code tomorrow ?

[AykutCanturk]

Dear friends,

I want to stop (pause) mach3 while running and shutdown everything and tomorrow I want to continue where I stopped the system.

I wonder how do you do it. I get the last coordinates, last line of gcode that will be processed and "tomorrow" I try to continue after entering last coordinates and line number... without moving the mill of course.

but... "Radius to end of arc differs from radius to start on Line #" messages are making this operation impossible. Also entering all this last coordinates makes me crazy..

Can you suggest some way to do it ? Any way to stop mach3, stop spindle, shutdown computer and tomorrow continue from last point...

best regards...

[neilw20]

1. You need to reference the machine using good limit switches.
2. You need to put lots of M1's in the code so you can pause program at the end of a z up move. Write down the line number when you pause it. If you are using subroutines, make sure the M1 is in the main part of the program.
3. When you turn on machine again, reference it.
4. Load the program.
5. Scroll through to the the line where you paused.
6. Click 'run from here', and follow prompts.

If you are using loop counters in the program, starting from a run from here is often a problem because you can't restore the original machine (PC) state.

note: You need to reference the machine, because if you are using microstepping drivers then it almost certainly be somewhere between steps.

After turning on and referencing the machine, you must be able to reliably get to the same start position.
Even a temperature change can make limit switches start in a slightly different position.

Easiest is to have a reference hole drilled in the job and see that it hasn't 'moved'.

[AykutCanturk]

thanks my friend, this is how I exactly try to do it but....

when I stop the progam at that line:
G3X45.000Y17.059I-0.005J1.001

I cannot continue because ti says "Radius to end of arc differs from radius to start on Line #", which I believe its normal because it losts the program flow.

1. You need to reference the machine using good limit switches.
2. You need to put lots of M1's in the code so you can pause program at the end of a z up move. Write down the line number when you pause it. If you are using subroutines, make sure the M1 is in the main part of the program.
3. When you turn on machine again, reference it.
4. Load the program.
5. Scroll through to the the line where you paused.
6. Click 'run from here', and follow prompts.

If you are using loop counters in the program, starting from a run from here is often a problem because you can't restore the original machine (PC) state.

note: You need to reference the machine, because if you are using microstepping drivers then it almost certainly be somewhere between steps.

After turning on and referencing the machine, you must be able to reliably get to the same start position.
Even a temperature change can make limit switches start in a slightly different position.

Easiest is to have a reference hole drilled in the job and see that it hasn't 'moved'.

[Torchhead]

well....don't stop in the middle of an Arc. The reference for arcs may not be absolute. It's like stopping your car out in the middle of a busy highway and expecting it to be in the same spot 24 hrs later. I know there are long jobs but what in the world would prompt a machinist to stop in the middle of a job and punch out and go home? I know in my shop the jobs get finished before the machine is turned off...period. If you have 10 more minutes left you stay and finish the run.

If precision is important the advice neilw20 gives is valid and from experience. Stop at a point where the machine is either between cuts (Z is up) or it's on a G00 or G01.

Tom caudle
www.CandCNC.com