M500 command not surviving reboot  

Re: M500 command not surviving reboot

I'm seeing this same behavior. What needs to happen to get the mk2 to save PID values?

Re: M500 command not surviving reboot

I'm seeing this same behavior. What needs to happen to get the mk2 to save PID values?

You need to put it in the slicer settings so it's in the gcode instead. Or recompile the firmware.

Re: M500 command not surviving reboot

Just to confirm - are you saying this is expected behavior with the default firmware? If so no problem, I've already put the values into the connect script in Octoprint. I'm just worried that saving to EEPROM doesn't seem to be working and have been trying to troubleshoot that issue.

Re: M500 command not surviving reboot

Just to confirm - are you saying this is expected behavior with the default firmware? If so no problem, I've already put the values into the connect script in Octoprint. I'm just worried that saving to EEPROM doesn't seem to be working and have been trying to troubleshoot that issue.
That's right, by design not being allowed to save to EEPROM. Not sure why they did that.

Re: M500 command not surviving reboot

Just to confirm - are you saying this is expected behavior with the default firmware? If so no problem, I've already put the values into the connect script in Octoprint. I'm just worried that saving to EEPROM doesn't seem to be working and have been trying to troubleshoot that issue.
That's right, by design not being allowed to save to EEPROM. Not sure why they did that.

Thanks man, that saves me a lot of troubleshooting! Now to learn how to compile Marlin to cook in the new PID values and enable EEPROM saving.

Re: M500 command not surviving reboot

There will be a reason why EEPROM saving is disabled. When you find out, can you please let us know!

Thanks

Peter

Re: M500 command not surviving reboot

There will be a reason why EEPROM saving is disabled. When you find out, can you please let us know!
Short version - EEPROM saving is intentionally disabled because it's broken. The assertion seems to be that the PID values as shipped are correct and thus should not need to be changed, which is demonstrably untrue.

I've gone pretty far down the rabbit hole on this. Building the firmware with current releases of the Arduino IDE is broken because of an error that was resolved in Marlin nearly a year ago. The instructions Prusa provides in the Github are hilariously incomplete and don't work at all. The EEPROM saving ifdefs are commented out in the source code. If you attempt to enable them, the code no longer compiles, and if you fix those errors, it doesn't work anyway.

For anyone looking to compile the firmware: This github issue comment outlines the process very well. With that setup you can change the default settings to a value that actually works on your printer while we wait for EEPROM saving to be re-enabled.

For anyone looking to fix their PID values: It seems that using GCODE in your slicer or print server might be the best option for the moment.

Re: M500 command not surviving reboot

Thanks for the update on this!

Peter

Re: M500 command not surviving reboot

If I insert a M92 to adjust my extruder esteps in my start up code will it stick for the whole print? When I was doing it manually via octoprint, the temporary nature of M92 seemed very temporary - like didn't survive individual extrude commands. In fact, I seem to get apparently random behavior of the "stickiness" of the M92 command. Thoughts?

-Tom

Re: M500 command not surviving reboot

Tom

It will stick until another M92 command is issues or the printer is power cycled.

I know this from personal experience (my filament drive pulley is rather small and requires 175.5 s/mm)

Peter

Re: M500 command not surviving reboot

Also the first beta test of the multi-material upgrade used standard drive pulleys which differed in size.

I used the M92 command after each tool.

I suspect that when testing the extrusion via OctoPrint, you will need to set to relative extrusion, that is issue an M83 command:

T0
M92 E161.3
M83
G1 E100 F300

{T0 is default, so you won't need it}

Peter

Re: M500 command not surviving reboot

Hmmm, I'll look into that. Thanks Peter!