Power failure and resurrection on a CNC machine

Nightowl

In response to your comments, here are mine...

Line 13 - M3 would stop the spindle spinning
Line 19 - I know where they are, but at what point can the values be 'recovered' and saved
Line 52 - Not in config.g, but I CAN find G3 in the toolpath (gcode) files (e.g. "G3X31.755Y28.580I3.175J0.000" from a Vectric CAD file (these are G2 - clockwise, and G3 - counterclockwise, arc movements)
Line 60 - OK, understood
Line 61 - I think movement is controlled by G1 X*Y*X*  with speed defined with F*, e.g. G1X49.124Y56.098F3683.0
Line 64 - No, there are no extruders

infiniteloop

@nightowl999 OK, now I have edited (faked) a resurrect.g, easy to read as it is really short. I've reflected some of your comments…

; File "0:/gcodes/Calibration Toolpath.gcode" resume print after power failure at 2022-05-29 16:49


G21					; sets units to mm
G92 X182.895 Y658.930 Z66.000		; sets the position for X, Y and Z
G60 S1					; save to slot 1 for latter use of M24

T-1 P0					; this enables the macros tpreN.g and tpostN.g to be called by the following T0
T0						; change(!) to tool T0, call the corresponding macros

M3 S10000				; set spindle speed - don’t worry, we create a macro with this line like we created HelloWorld :-)

M98 P"resurrect-prologue.g"		; runs the user-defined resurrect-prologue.g

G10 L2 P1 X147.00 Y584.00 Z67.00	; restore the coordinates for coords-system #1
G54					; select coordinate system 1

G17					; or G18, G19 - needed for circular moves

M23 "0:/gcodes/Calibration Toolpath.gcode"		; select the interrupted CNC file
M26 S249				; set file offset from the start of the interrupted file
G0 F6000 Z68.000			; rapid move to above saved Z height
G0 F6000 X182.895 Y658.930		; rapid move to saved XY axes
G0 F6000 Z66.000			; rapid move to saved Z height

G21					; sets units to mm
M24					; start/resume SD print

With the G0 movements, formerly known as line 61, you misunderstand my concerns: It's not the syntax, but what path is safe for these head moves on a CNC? Are you fine with the movements as they are done in resurrect.g?

So, your homework for now: carefully check my faked resurrect.g, especially with regard to the position of the M3 command: shall the spindle start that early in the recovery process?

infiniteloop

@nightowl999 In case you can put the M3 before resurrect.g, the solution is pretty simple: Here is a macro which just stores the spindle speed in the file "RestoreSpindleSpeed.g", which in turn can be called from your resurrect-prologue.g. The only thing left to figure out is how to insert the call of "SaveSpindleSpeed.g" into the M911 command.

; SaveSpindleSpeed.g
; Macro to store the actual spindle speed (RPM) at the time this is called
; To restore the saved datum, call the macro "RestoreSpindleSpeed.g".
; Requires RRF 3.4 and a CNC configuration with valid spindles[0] entry in the object model

var fName = "RestoreSpindleSpeed.g"

echo >{var.fName} "; "^var.fName
echo >>{var.fName} "; Spindle speed saved from running """^{job.file.fileName}^""" CNC file"
echo >>{var.fName} ""
echo >>{var.fName} "M3 S"^{spindles[0].active}
echo >>{var.fName} ""
echo >>{var.fName} ";EOF"

Nightowl

@infiniteloop said in Power failure and resurrection on a CNC machine:

So, your homework for now

It's a very long time since I've had homework!

With regard to the G0 movements, I need to ask a question. If the XYZ values are saved when the power loss workflow starts (based on the M911), then these should be fine in this circumstance, but would change when overwritten by the next power loss event. Have I got that right?

It was suggested to me that the spindle should start before the axes move, as it would then cut its way through an obstruction, rather than not and end up it breaking and damaging the stock.

The most important axis save is the Z axis. With a power failure X and Y can physically stay where they are, although I appreciate their respective 3 dimensional locations must be saved as the axes must be re-homed after restarting.

Note: I get that a 3D printer should not re-lay material a second time following restart, but this is not an issue for the CNC. As the part to be cut has already been cut, it will only cut air.

infiniteloop

@nightowl999 said in Power failure and resurrection on a CNC machine:

If the XYZ values are saved when the power loss workflow starts (based on the M911), then these should be fine in this circumstance, but would change when overwritten by the next power loss event. Have I got that right?

Perfectly!

It was suggested to me that the spindle should start before the axes move

Fine, than you can try my latest macro

The most important axis save is the Z axis. With a power failure X and Y can physically stay where they are, although I appreciate their respective 3 dimensional locations must be saved as the axes must be re-homed after restarting.

Yeah, I ask because, with 3D printers, all X/Y moves above the current Z-height of the print are perfectly safe. That's what resurrect.g assumes. However, with routers, this might be different - I simply don't know that.

–––––

I have been looking in how to insert a macro call into M911 - alas, the reality check on my printer fails: although configured, M911 does not execute on a simulated power loss. Could you help me out with that?

It's simple: out-comment the M911 line in your config, then put something like this below:

M911 S13.1 R24.0 P"M98 P""SaveSpindleSpeed.g"" M913  X0 Y0  G91 M83 G1 Z3 E-5 F1000"

Parameters can be different on your milling machine (especially S and R of M911).

If you have put the "SaveSpindleSpeed.g" macro into /sys before, you should find the spindle speed at power-off in the macro "RestoreSpindleSpeed.g" after you have repowered your mill.

Nightowl

@infiniteloop

Just so I'm clear (sorry), do I need to run a project file and power off during that, or will the file be generated without running a project file?

Also, there isn't a file of that name in the \sys folder yet.

Also also I probably don't need to include anything after Y0 as I don't have an extruder (except perhaps the Z3?)

Nightowl

@infiniteloop

Talk about slow! I'm not getting topic updates, so missed the bit about writing the macro.

I've done it now and, with the spindle running, switched off the machine at the mains, then turned it back on again.

This is the resulting SavedSpindleSpeed.g file...

; SaveSpindleSpeed.g
; Macro to store the actual spindle speed (RPM) at the time this is called
; To restore the saved datum, call the macro "RestoreSpindleSpeed.g".
; Requires RRF 3.4 and a CNC configuration with valid spindles[0] entry in the object model
var fName = "RestoreSpindleSpeed.g"
echo >{var.fName} "; "^var.fName
echo >>{var.fName} "; Spindle speed saved from running """^{job.file.fileName}^""" CNC file"
echo >>{var.fName} ""
echo >>{var.fName} "M3 S"^{spindles[0].active}
echo >>{var.fName} ""
echo >>{var.fName} ";EOF"

I've also written a RestoreSindleSpeed.g file with just a REM line at Line 1, and this is what's in it when I run the SavedSpindleSpeed.g file...

; RestoreSpindleSpeed.g
; Spindle speed saved from running "null" CNC file

M3 S0

;EOF

infiniteloop

@nightowl999 said in Power failure and resurrection on a CNC machine:

I've also written a RestoreSindleSpeed.g file with just a REM line at Line 1.

Then, something goes wrong. The macro RestoreSpindleSpeed.g is generated by a call of SaveSpindleSpeed.g. So, if you have put SaveSpindleSpeed.g into the M911 line in your config,g, then cut power off …
After repowering the machine, RestoreSpindleSpeed.g should be to find in your /sys folder of the SD card. Every time you see it in /sys, you can delete it right away. It is just needed until you have run your resurrect.g - which in turn calls resurrect-prologue.g, into which you - hopefully - have insert the line

M98 P"RestoreSpindleSpeed.g"

As long as no job is in progress during the power fail, you will get "null" as CNC file name, and if the spindle speed is 0, the resulting M3 S0 is ok.

I probably don't need to include anything after Y0

That's right for your router.

Nightowl

@infiniteloop
So I tried to experiment a little...

I ran a small gcode file which set the spindle speed to 18,000rpm then initiated a power cut.

When I ran the RestoreSpindleSpeed.g from the MDI, the spindle started up - at 18,000rpm.

This is the file:

; RestoreSpindleSpeed.g
; Spindle speed saved from running "0:/gcodes/Calibration Toolpath.gcode" CNC file

M3 S18000

I've now added the M98 line to resurrect-prologue.g file, so it looks like this:

; resurrect-prologue.g
M98 "RestoreSpindleSpeed.g"

infiniteloop

@nightowl999 said in Power failure and resurrection on a CNC machine:

This is the file:

That's what I've expected. The only thing I miss is my beloved ";EOF" at the end of RestoreSpindleSpeed.g

Now the big question: does this setup what you want or do you need additional functions to be restored after a power off? With the same technique, we could generate a complete replacement or a better suited version of resurrect.g.

Nightowl

@infiniteloop

That's awesome, thank you

Because this is following a power failure, and from a safety perspective, there are some procedures I will need to initiate from starting up after the power failure (it's never my intention to be away from the machine while it's running, by the way).

I understand the machine must be homed, so it knows where it is, return to its last known XY location, remember what file it was running, remember where in that file it had got to, then wait for me to say OK for it to carry on. At the 'carry on' it should start the spindle and plunge slowly down to it's last known Z height then continue the project.

Simples!

I think the parameters for most of that will be in the resume.g file?

I've added the EOF line!

infiniteloop

@nightowl999 said in Power failure and resurrection on a CNC machine:

I think the parameters for most of that will be in the resume.g file?

That depends. Currently, your resume.g is mainly meant to be called after a pause - I doubt you want this to permanently call for permission to continue. Also, at that stage of resurrect.g, i.e. when resurrect.g calls resume.g, the spindle is already running. Nothing to dream of - you want to be asked before.

A better place to ask might be your resurrect-prologue.g. From there, you can cancel further execution of resurrect.g.

I understand the machine must be homed, so it knows where it is, return to its last known XY location, remember what file it was running, remember where in that file it had got to, then wait for me to say OK for it to carry on. At the 'carry on' it should start the spindle and plunge slowly down to it's last known Z height then continue the project.

The question here is: does resurrect.g what you want? As I said, we can insert a dialog in the prologue which then asks for permission to continue … but are you fine with the part of resurrect.g which follows on the call of the prologue?

Nightowl

@infiniteloop
So it's about the event timing (I'm not sure I actually meant the resume.g file!)...

On power fail, the M911 string initiates the SaveSpindleSpeed.g file which writes the RestoreSpindleSpeed.g file, taking (some) information from the active job file and elsewhere, and the default resurrect.g file is also written.

On power resume, the resurrect.g file calls the resurrect-prologue.g file, which calls the RestoreSpindleSpeed.g file to set the variables and other information ready for the specific file to continue.

It might be worth homing the machine on power resume and for it to wait there until I allow it to continue (if everything is OK, or Cancel if I need to stop the project.

Cancel will be the same as Cancel Job on the DWC.

On OK, the spindle should move to the last known XY, turn on at the saved Spindle speed, thendrop down to the last known Z height and continue on it's way.

So, in answer to your question, I think the resurrect.g file does do what I want, except for the homing sequence, which I think is necessary. I could be wrong, if all the necessary information is held in the resurrect.g file and precludes the need to home. That's what I'm not sure about.

Thank you!

infiniteloop

@nightowl999 said in Power failure and resurrection on a CNC machine:

On power fail, the M911 string initiates the SaveSpindleSpeed.g file which writes the RestoreSpindleSpeed.g file, taking (some) information from the active job file and elsewhere, and the default resurrect.g file is also written.

Correct.

@nightowl999 said in Power failure and resurrection on a CNC machine:

On power resume, the resurrect.g file calls the resurrect-prologue.g file, which calls the RestoreSpindleSpeed.g file …

Up to here: correct.

… to set the variables and other information ready for the specific file to continue.

No, the file RestoreSpindleSpeed.g just restores the previously saved spindle speed - that's it. After that, it returns control back to resurrect-prologue.g (which, at this point, has no more instructions available), and, after finishing execution of the prologue, control returns to resurrect.g which then executes all lines following the call of resurrect-prologue.g.

I think the resurrect.g file does do what I want, except for the homing sequence, which I think is necessary.

That's the main job of resurrect-prologue.g - allow me to cite the documentation:

At the very least, your sys/resurrect-prologue.g file must do the following:
Home the printer, without crashing the head into the print. On a delta, or on a Cartesian or CoreXY printer with a Z max homing switch, you can home all axes. On other types of printers you may have to skip homing Z and use a G92 command to tell the printer the current Z coordinate. If you choose not to home an axis, then even if the print head hasn't moved since power down, the motor positions will change by up to 4 full steps compared to their position at power down. Note: recent firmware versions write a G92 command containing the coordinates at the time of failure into resurrect.g, just before the call to resurrect-prologue.g. So you may get away without homing axes. But it is still best to home any axes that you can (typically X and Y on a cartesian or CoreXY printer).

Nightowl

@infiniteloop

I’m definitely going to try and help others with this in the future, as payback for all your help!

Although I feel like I’m wading through treacle, I’m learning as I go!

infiniteloop

@nightowl999 said in Power failure and resurrection on a CNC machine:

Although I feel like I’m wading through treacle, I’m learning as I go!

Don't worry, it's easy. Just take your commented resurrect.g and follow the lines. Near the beginning, you will come up with the line

M98 P"resurrect-prologue.g"

At that point, the control flow is handed over to the macro (which in turn can call other macros). After the macro (or chain of macros) is done, control goes back to the next line in resurrect.g. That's all - just one command after the other. Well, and some of the commands (the macros) contain their own list of commands … so what?

infiniteloop

@nightowl999 OK, I've done some homework myself, here's an updated version of the macro SaveSpindleSpeed.g (it has become a bit more complex, but you can just copy it):

; SaveSpindleSpeed.g
; Macro to store the actual spindle speed (RPM) at the time this is called
; To restore the saved datum, call the macro "RestoreSpindleSpeed.g".
; Before it activates the spindle, RestoreSpindleSpeed.g asks whether to continue with the print or not.
; If not, the process can be stopped with these two lines in resurrect-prologue.g:
;
;	if {global.abort_process == true}
;		abort									;;; please not that this line must be indented
;
; Requires RRF 3.4 and a CNC configuration with valid spindles[0] entry in the object model


var fName = "RestoreSpindleSpeed.g"

echo >{var.fName} "; "^var.fName
echo >>{var.fName} "; Spindle speed saved from running """^{job.file.fileName}^""" CNC file"
echo >>{var.fName} ""
echo >>{var.fName} "; set up the global variable abort_process so we can abort further execution of resurrect.g:"
echo >>{var.fName} "if {!exists(global.abort_process)}"
echo >>{var.fName} "    global abort_process = true"
echo >>{var.fName} "else"
echo >>{var.fName} "    set global.abort_process = true"
echo >>{var.fName} ""
echo >>{var.fName} "; now comes the dialog:"
echo >>{var.fName} "M291 S3 R""Resurrect:"" P""Continue with <"^{job.file.fileName}^">?"""
echo >>{var.fName} ""
echo >>{var.fName} "; we will only arrive here if the dialog was closed with OK:"
echo >>{var.fName} "global abort_process = false"
echo >>{var.fName} "M3 S"^{spindles[0].active}
echo >>{var.fName} ""
echo >>{var.fName} ";EOF"

This will generate the macro RestoreSpindleSpeed.g as before, but I've added a dialog to it which asks whether you want to continue (of course, before the spindle is turned on).

In order for all this to work, you will have to modify your resurrect-prologue.g like this:

; resurrect-prologue.g

M98 P"RestoreSpindleSpeed.g"
if {global.abort_process == true}
		abort
; abort terminates this and all other macros in the call chain, so 'rien ne va plus'

; Continuation has been approved, so here we go:"
;
; Here, please home your axes
;
; at the end of this, control goes back to resurrect.g

As long as you didn't modify your resurrect-prologue.g in the meantime, you can simply replace its contents with a copy from the black box above.

Then, you should add your homing commands - I've commented where to put them.

Hope this helps…

Nightowl

This is brilliant, thank you @infiniteloop

I'll check it out tomorrow morning (it's a bit too late here to wake the neighbours!) and let you know how I get on.

I really can't tell you how much I appreciate your help.

Thanks again, my friend

infiniteloop

@nightowl999

This is brilliant

No, it’s attentive reading. The technique for the dialog is tricky, so it helped that I remembered the thread "Echo commands…", where @mikeabuilder explained the technique in detail - BTW, it was your thread, and he addressed his "trick" to you. So you could have written the code as well. At least, you were told how to do it…

In fact, a good programmer spends at least 95% of his time on reading, 100% on meditation and the remaining 5% on coding, tests and debugging - at most…

[Edit] Oh, I forgot: When we finally fall asleep (which is rare), we dream of an algorithm to calculate a 'something' of which we only know the result: 42

Nightowl

@infiniteloop said in Power failure and resurrection on a CNC machine:

No, it’s attentive reading.

I beg to differ. What you have done for me is brilliant, even if it's simple to you!

Anyway, on with the experiment...