Auto save error

Basic Information:

Printer Model: voron 2.4 (DIY)
MCU / Printerboard: MONSTER8 V2
Host / SBC RPİ 4
klippy.log

klippy (3).log (123.0 KB)
Hello everyone, first of all, I congratulate all friends on the new year. I wish you a good year.

I encountered an interesting situation for the 2nd time. yesterday I printed a few small parts and turned off my printer. when I turned on my printer this morning, klipper gave an error. since it did not reach the data in the auto save section, I manually entered the z_offset, extruder pid information, hotbed pid information again and the system turned on. as far as I understand, it does not see the auto_save section in the printer.cfg file. I reinstalled my system 3-4 days ago. I have never encountered such a situation before.



Can you please upload the printer.cfg

exactly. when i reinstalled the first device i uploaded the backup files to the printer cfg file. it wouldn’t accept it. i deleted the save_config section at the bottom and redid all the settings. then save_config worked… now i deleted the section at the bottom but now it won’t accept it.

The section at the end has to stay there.

#*# <---------------------- SAVE_CONFIG ---------------------->
#*# DO NOT EDIT THIS BLOCK OR BELOW. The contents are auto-generated.

I have now copied the relevant section and added it to the printer.cfg file… I will immediately make a bed mesh to the system and try it. I will inform you about the latest situation in a little while. thanks

It didn’t work, and I still don’t know what to do.
klippy (4).log (6.5 MB)
mainsail.cfg (16.1 KB)
printer.cfg (9.5 KB)

  1. Delete the entire auto-save section at the bottom of the config.
  2. Remove the #*# from

    Do NOT use this combination anywhere in your config, except what Klipper created on its own

i don’t use this data. i did a reinstallation. everything seems to be in order now :ok_hand:. thanks for everything :pray:. what’s stuck in my head: my printer, which i turned off normally, turned on the next day with these errors. maybe i made a systemic error while installing. right now it’s fine for a day… it will be clear in 2-3 days :grin: