Work Coordinates - Saved after power off?

Don't think so Colin, sorry.
Alex

 

PS - too late to say this now, but I usually make a note of the machine co-ordinates immediately after setting work zero.
Alex

 

Pause job, return to work zero, switch to machine co-ordinates, write them down. Next time you switch on machine home axes, jog to machine co-ordinates you wrote down, set work zero.
Alex.

 

Sorry Colin, I think I'm mixing up the Colins. Your not using the Duet controller are you? I could give you an answer tomorrow after I've looked up the G code, but I suspect someone else might answer your question first.
Alex

 

Hi Colin, have just checked you are using Duet so I will be interested to know if it has remembered your work co-ordinates. If it hasn't the second part of my post works - home axes, jog to machine co-ordinates you recorded, set work co-ordinates. If your workbee is as reliable as mine you'll be within 0.1mm.
Alex.

 

RAM vs. ROM. He's cycling the power, it will lose the memory of where it was. I regularly pause work (Feedhold) when I run out of time, but leave the PC and controller powered on until I can resume while turning off my spindle and shopvac. Making note of the WCS and re-zeroing the machine works if you're completely done the g-code you are running, but I tend to move my machine to work X0,Y0 in case someone (me) trips over the power cords. If you know it's at your work 0,0 you can recover without ruining your stock. For example, on the aluminum plates I'm currently cutting I use Fusion 360 and make separate G-codes for each operation (pockets, circular holes, contours) which allows me to split 3 hours of milling time into manageable chunks. (The maximum time between wife and kids interruptions is about 45 minutes in my house).

EDIT: I was wrong, the Duet does write it to ROM and keeps the WCS from that link if you use the M500 command. GRBL based machines do not, AFAIK.

 

@sharmstr I rarely like being proven wrong twice in the same thread, but I'd be much happier if it's true. I'll test mine tonight. Although it's a tinyG. I've also got GRBL loaded on a couple Nano boards I can test too.

 

So $#, look at WCS numbers, power off, power on, $# and see if the numbers are the same. Got it. The tinyG's firmware was a branch from GRBL originally, hopefully that's one of the functions they carried over.

 

Hi Colin, that is great news. Did you use the m500 code that @sharmstr found a reference to or did it remember anyway? Alex.

 

I am now totally confused, I checked again the thread @sharmstr quoted and found these two quotes from DC42;

"What do you all think should be the mechanism for saving coordinate systems to the SD card?

(a) Automatically save them whenever they are changed. This could result excessive wear on the SD card if they are changed frequently.

(b) Save them whenever a job is paused.

(c) Save them when you ask to save them explicitly, using M500 or a similar command.

(d) Something else?"

and;
"Thanks, both of you. I'll add the workplace coordinate settings to the M500 saved parameters."

I know I'll need to get my head around both G-code and the capabilities of the Duet (an instruction book would be nice) but I think I'll leave this one until I need it. The Duet does remember the workplace co-ordinates by default so I don't need to worry about this particular aspect yet.
Alex.

 

A lot of this techie stuff goes over my head - probably down to age and declining number of brain cells, but I would like to know more about the capabilities of the Duet. I guess the 3d printer forum might be a good place to start looking for info.
Thanks for your input @sharmstr - we now know the Duet stores WCS on power down.
Alex.

 

So the tinyg board does NOT hold the WCS coordinates after a power cycle. I was pretty sure I tested that when I started to use it a couple years ago. That just gives me one more reason to buy a Black Box.