Solved M500 does not seem to save parameters

[TomasL]

When I am calibrating my printer, and determine Z=0, with G92 Z0 and then enters M500, the new Z0 is not stored in config-override.g.
What am I doing wrong here.

[jay_s_uk]

@tomasl thats not how it works
what type of printer do you have? what type of probe do you have?

[TomasL]

Home built Prusa I3-steel, E3D Hermera, Duet3 WiFi, Duet IR-probe, 3-point adjustments on the bed.
This is what I do:
Homing all axis.
Navigate the nozzle to where the fixed bed location (the adjusting screw that is the reference for bed leveling)
Issues the following commands
M561
M564 S0
Lowering the nozzle so it touches the bed (so I can move a piece of paper under the nozzle)
The paper is 0,1mm thick, so I lower the nozzle an additional 0,05 mm
issues the command G92 Z0
Issues the command M500
I would have thought that the new offset would end up as a new z-axis limit in the config-overide file.

Obviousl I got something wrong or dont understand.
(I was told to use the M500 command to save the new Z-limit)

[jay_s_uk]

@tomasl https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_testing

[droftarts]

@tomasl See M500 for a list of parameters that are stored, and how. Basically, you need to use M500 P31. But make sure you understand what is being saved, because what it needs to know is the probe offset, ie the position of the nozzle above the bed when the probe is triggered.

Ian

[TomasL]

Ok, so I was told wrong then, and the edit in config.g is all that needs to be done, and I do not need to send any M500 commands

[tecno]

@droftarts

https://docs.duet3d.com/User_manual/Reference/Gcodes#m500-store-parameters

Above is the correct link to what you wanted to point out Ian

[tecno]

@tomasl

No you got info based on that you READ latest documentation which you obviously did not

[droftarts]

@tecno said in M500 does not seem to save parameters:

@droftarts

https://docs.duet3d.com/User_manual/Reference/Gcodes#m500-store-parameters
Above is the correct link to what you wanted to point out Ian

Yes and no! I generally point at the individual Gcode pages, which currently forward to the relevant section of the single large Gcode page, because eventually we are going to update the documentation so all Gcodes have their own page. There will still be a single large Gcode page, which collects all the individual pages together too, as people love it for searching; it's a feature that is hopefully 'coming soon' to the wiki software.

Thanks, I've edited my link so it is correct.

Ian

[TomasL]

@tecno Yes I read the documentation, then I was instructed on another forum that I need to do an M500 command, obviously that was not correct.