Basic Information:
Printer Model: Creality CR-5 Pro H
MCU / Printerboard: Creality 3D v2.5.1 (8-bit mainboard with ATMega2560)
Host / SBC: Raspberry Pi Zero 2W
klippy.log (76.6 KB)
Describe your issue:
Klipper will connect just fine after the printer is power cycled. However, it will not reconnect if a firmware_restart is issued, and will only reconnect after powercycling the printer again.
It appears that just restarting klipper is OK
This wouldn’t be so bad if the default behaviour of fluidd’s “save and restart” when editing the config wasn’t a firmware_restart.
I’ve tried dmseg but it all seems to be fine, even when the printer is stuck after a failed MCU restart.