# Can not update MCU mcu config as it is shutdown

**URL:** <https://klipper.discourse.group/t/can-not-update-mcu-mcu-config-as-it-is-shutdown/10134>\
**Category:** General Discussion\
**Created:** [August 27, 2023, 4:48am UTC](https://klipper.discourse.group/t/can-not-update-mcu-mcu-config-as-it-is-shutdown/10134 "2023-08-27T04:48:13Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![BigChief](https://avatars.discourse-cdn.com/v4/letter/b/4491bb/32.png) [@BigChief](https://klipper.discourse.group/u/BigChief)\
**Post date:** [August 27, 2023, 4:48am UTC](https://klipper.discourse.group/t/can-not-update-mcu-mcu-config-as-it-is-shutdown/10134/1 "2023-08-27T04:48:13Z")

</div>

Printer Model: Cr-10 Smart Pro  
Sonic Pad  
[moonraker .log](https://klipper.discourse.group/uploads/short-url/dS779kW2AGjDhR57L6NseuJF0Fr.log) (49.5 KB)  
[klippy .log](https://klipper.discourse.group/uploads/short-url/jALFJSFUy5RCcXWYtfblpCpPrLc.log) (3.6 KB)

Can not update MCU mcu config as it is shutdown  
Klippy shutdown mid print  
What can I do, can you help me?

---

<div class="post-metadata">

**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 27, 2023, 6:32am UTC](https://klipper.discourse.group/t/can-not-update-mcu-mcu-config-as-it-is-shutdown/10134/2 "2023-08-27T06:32:21Z")

</div>

[Can not update MCU '\<name\>' config as it is shutdown](https://klipper.discourse.group/t/can-not-update-mcu-name-config-as-it-is-shutdown/9392) is not an error that occurs during printing.

Since you are using a SoLame Pad no proper diagnose can be done what the actual error was that lead to your shutdown.

---

<div class="post-metadata">

**Author:** ![BigChief](https://avatars.discourse-cdn.com/v4/letter/b/4491bb/32.png) [@BigChief](https://klipper.discourse.group/u/BigChief)\
**Post date:** [August 27, 2023, 7:32am UTC](https://klipper.discourse.group/t/can-not-update-mcu-mcu-config-as-it-is-shutdown/10134/3 "2023-08-27T07:32:25Z")

</div>

Thank you for your attention  
I could not fully understand, What can I do?

---

<div class="post-metadata">

**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 27, 2023, 8:13am UTC](https://klipper.discourse.group/t/can-not-update-mcu-mcu-config-as-it-is-shutdown/10134/4 "2023-08-27T08:13:35Z")

</div>

Unfortunately, with the available information I cannot offer any more guidance, except:

- Make sure that you are using the latest Sonic Pad firmware (also see [Creality Sonic Pad and Alternatives](https://klipper.discourse.group/t/creality-sonic-pad-and-alternatives/6324))
- Potentially contact Creality support

---

<div class="post-metadata">

**Author:** ![BigChief](https://avatars.discourse-cdn.com/v4/letter/b/4491bb/32.png) [@BigChief](https://klipper.discourse.group/u/BigChief)\
**Post date:** [August 27, 2023, 8:23am UTC](https://klipper.discourse.group/t/can-not-update-mcu-mcu-config-as-it-is-shutdown/10134/5 "2023-08-27T08:23:41Z")

</div>

I spoke to Creality support they wrote,  
"USB disconnection is related to the user’s actual AC power grid environment with strong interference.

Users can check to see if there are frequent jumps in the line where the studio printer is located, AC inductive loads: AC fans, AC compressors, AC motors and other electrical appliances exist.

This MCU disconnection, USB to serial cable can significantly improve the connection line of the anti-interference capability"

Do you think the solution, Because I changed it.

---

<div class="post-metadata">

**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 27, 2023, 8:36am UTC](https://klipper.discourse.group/t/can-not-update-mcu-mcu-config-as-it-is-shutdown/10134/6 "2023-08-27T08:36:10Z")

</div>

For a common understanding: The error messages in the log cannot be used for diagnosis. The recorded error is not the root cause, but a consequence of an **earlier error that is not recorded** in the log.

Creality’s statement is a possibility, but since the true error is not known, I cannot give any more advice.

---

<div class="post-metadata">

**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:** [July 7, 2025, 7:06pm UTC](https://klipper.discourse.group/t/can-not-update-mcu-mcu-config-as-it-is-shutdown/10134/7 "2025-07-07T19:06:44Z")

</div>

Closed on July 7, 2025, 7:06pm UTC


