# Random print fails - can not update MCU mcu as it is shutdown **URL:** \ **Category:** General Discussion\ **Created:** [August 20, 2023, 11:04pm UTC](https://klipper.discourse.group/t/random-print-fails-can-not-update-mcu-mcu-as-it-is-shutdown/10031 "2023-08-20T23:04:55Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Xirro](https://avatars.discourse-cdn.com/v4/letter/x/e47774/32.png) [@Xirro](https://klipper.discourse.group/u/Xirro)\ **Post date:** [August 20, 2023, 11:04pm UTC](https://klipper.discourse.group/t/random-print-fails-can-not-update-mcu-mcu-as-it-is-shutdown/10031/1 "2023-08-20T23:04:55Z")
### Basic Information: Printer Model: Voxelab Aquila S2 MCU / Printerboard: Raspberry Pi 4B / Creality 4.2.7 board [klippy.zip](https://klipper.discourse.group/uploads/short-url/jmAYFhdMocLRmHwyEAaVsSTfU97.zip) (803.6 KB) ### Describe your issue: Hi, In the past few days, I have been trying to do several prints with both 0.2mm and 0.4mm nozzles and I noticed the print with 0.2mm nozzle fails much earlier. However, in either case, during a longer print it is prone to fail regardless. The error message I keep getting is: Can not update MCU ‘mcu’ config as it is shutdown Once the underlying issue is corrected, use the “FIRMWARE\_RESTART” command to reset the firmware, reload the config, and restart the host software. Error configuring printer This usually happens after several minutes of print time to hours if I’m (un)lucky. Using the “FIRMWARE\_RESTART” command seems to solve my problem temporarily, but I would love to know what is actually causing this problem and how I can get it fixed. ---
**Author:** ![Blake100](https://avatars.discourse-cdn.com/v4/letter/b/7c8e57/32.png) [@Blake100](https://klipper.discourse.group/u/Blake100)\ **Post date:** [August 21, 2023, 12:03am UTC](https://klipper.discourse.group/t/random-print-fails-can-not-update-mcu-mcu-as-it-is-shutdown/10031/2 "2023-08-21T00:03:41Z")
Hello, This thread delt with the same thing: > [@\[mcu host\] Can not update MCU 'mcu' config as it is shutdown after system reset/start](https://klipper.discourse.group/t/mcu-host-can-not-update-mcu-mcu-config-as-it-is-shutdown-after-system-reset-start/4048): > > Printer Model: Modified ANET A8 with E3D-V6 extruder, capacitive leveling sensor, 2 stepper for z-axis MCU / Printerboard: BTT SKR MINI V1.2 with additional stepper for extruder [klippy.log](https://klipper.discourse.group/uploads/short-url/zHWgTzgnmlBTIeL8tmlBMw9165r.log) (536.1 KB) Hello, If the MCU host is activated in the printer.cfg the error message “Can not update MCU ‘mcu’ config as it is shutdown” appears after a system start or restart. Raspberry Pi as MCU [mcu host] serial: /tmp/klipper\_host\_mcu The mcu host is only integrated and has no further function (int… I hope this helps. Happy Printing, Blake ---
**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\ **Post date:** [August 21, 2023, 6:18am UTC](https://klipper.discourse.group/t/random-print-fails-can-not-update-mcu-mcu-as-it-is-shutdown/10031/3 "2023-08-21T06:18:37Z")
> [@Xirro](#): > > Can not update MCU ‘mcu’ config as it is shutdown See [Can not update MCU '\' config as it is shutdown](https://klipper.discourse.group/t/can-not-update-mcu-name-config-as-it-is-shutdown/9392) This is not an error that happens during printing, and also your log does not reflect this. There are two instances of this error in your log, and both are in the context of Klipper being restarted. This is explained in the link above. ---
**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\ **Post date:** [May 4, 2024, 8:59pm UTC](https://klipper.discourse.group/t/random-print-fails-can-not-update-mcu-mcu-as-it-is-shutdown/10031/4 "2024-05-04T20:59:00Z")