[Bug]: After Marlin Update, ignore crc mismatch, restoring a config M112 ERROR when no bed mesh is stored about octoprint-eeprom-marlin HOT 2 OPEN

Apologies for somehow missing this issue, I have only just picked it up.

selecting restore a backup containing a mesh map

This plugin doesn't back up the saved mesh at the moment, it only backs up what you can configure in the UI. A plugin like UBL Mesh Edit can do that. If your backup has a mesh map in it, that is interesting - your log doesn't seem to show any commands like that being sent to the printer from the plugin to 'attempt' to restore the mesh either.

This is how I understand this issue:

• EEPROM is reset to default values - this doesn't include anything for the saved mesh, which is empty
• You restore the backup in the plugin, but this doesn't restore the mesh
• You go to print, but it doesn't start because the printer can't load a mesh (mesh saved slot is empty)

If you do it after running bed levelling, there is the extra step:

• EEPROM is reset to default values - this doesn't include anything for the saved mesh, which is empty
• You run bed levelling, which saves a mesh in EEPROM
• You restore the backup in the plugin, doesn't touch the mesh
• You go to print, it now has a mesh to use so the printer is happy?

If I've understood it correctly, this is expected behaviour with how these things were designed to work. Let me know if that's not right.

from octoprint-eeprom-marlin.

Thanks for the reply, life is nuts.
I updated the title as no bed mesh is stored in the backup, that was my mistake.
So this is what happens.

EEPROM is reset to default values - this doesn't include anything for the saved mesh, which is empty
You restore the backup in the plugin, but this doesn't restore the mesh
Printer Halts M112

EEPROM is reset to default values - this doesn't include anything for the saved mesh, which is empty
You run bed levelling, which saves a mesh in EEPROM
You restore the backup in the plugin, doesn't touch the mesh
Printer is happy no halt.

After looking at the process, maybe a check to see if a mesh is stored before restoring the config could be added to the plugin warning users it will halt the printer.

Using this on a lot of printers and when the marlin config gets a crc mismatch due to marlin update on them, none of which is the plugins fault, and forgetting to run the bed level when one is in a hurry can drive you nuts.

from octoprint-eeprom-marlin.