M500 did not work anymore?!
After changing steps per mm with command M92 the command M503 shows the new values. Then give a M500 to store them in EEPROM. After Power OFF an ON the values are the old default values.
RE: M500 did not work anymore?!
The buddy board used in the mini, mk4 etc doesn’t allow you to store values.
RE: M500 did not work anymore?!
But in https://help.prusa3d.com/de/article/buddy-specific-g-codes_633112#m-codes M500 is described. So it should work as described. 🙁
RE: M500 did not work anymore?!
If you follow the link, buddy is mentioned with "????"
https://reprap.org/wiki/G-code#M500:_Store_parameters_in_non-volatile_storage
RE:
https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/848
https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/767
https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/808
I could list many more. However the 767 issue is the main one and is currently open.
Its been this way since the mini was first released and anything using the buddy board is the same, so the Mk4 and the XL too currently. It is why if you retrofit a bondtech extruder on the mini you have to add the desired settings for steps per mm etc to your start gcode to load them for each print as you can not save.
As mentioned in the github issues if you read them this is a designed in operation and given how long its been open then I can't see it changing at this point. Miracles do happen however occasionally.
So this isn't a case of it doesn't work anymore, more a case of it has NEVER worked with this hardware.