# Print fails, Can not update MCU 'can0' config as it is shutdown **URL:** \ **Category:** General Discussion\ **Created:** [July 2, 2023, 3:04pm UTC](https://klipper.discourse.group/t/print-fails-can-not-update-mcu-can0-config-as-it-is-shutdown/9259 "2023-07-02T15:04:36Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![petyusa](https://avatars.discourse-cdn.com/v4/letter/p/f08c70/32.png) [@petyusa](https://klipper.discourse.group/u/petyusa)\ **Post date:** [July 2, 2023, 3:04pm UTC](https://klipper.discourse.group/t/print-fails-can-not-update-mcu-can0-config-as-it-is-shutdown/9259/1 "2023-07-02T15:04:36Z")
### Basic Information: Printer Model: Artillery Sidewinder X2 MCU / Printerboard: Raspberry PI 4, SKR 1.4 Turbo, EBB 36 `klippy.log` Hi, Today I started to get errors during prints. I had a 1,5 hours long print finished successfully, then ran another, but it failed after ~1,5 hours, I ran that again, now it failed after almost 2 hours. The error message I’m getting is “Can not update MCU ‘can0’ config as it is shutdown”. After I click Firmware Restart, I get a message that the klippy host is not started, try again in a few moments, but it doesn’t work. The only thing that works is if I restart the rpi. I attached the klippy log (had to remove a lot of its contents, I removed most of the logs created during printing, and multiple instances of printer.cfg, I didn’t change that at all), can you help what could cause this issue? ---
**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 2, 2023, 3:14pm UTC](https://klipper.discourse.group/t/print-fails-can-not-update-mcu-can0-config-as-it-is-shutdown/9259/2 "2023-07-02T15:14:02Z")
Hello @petyusa ! > [@petyusa](#): > > I attached the klippy log (had to remove a lot of its contents, I removed most of the logs created during printing, and multiple instances of printer.cfg, I didn’t change that at all), can you help what could cause this issue? The klippy.log does not appear in your post. If it is too large, you can zip (compress) it. But never remove something from it. ---
**Author:** ![petyusa](https://avatars.discourse-cdn.com/v4/letter/p/f08c70/32.png) [@petyusa](https://klipper.discourse.group/u/petyusa)\ **Post date:** [July 2, 2023, 3:18pm UTC](https://klipper.discourse.group/t/print-fails-can-not-update-mcu-can0-config-as-it-is-shutdown/9259/3 "2023-07-02T15:18:03Z")
[klippy.zip](https://klipper.discourse.group/uploads/short-url/3duvjXtaE1af6S2Qnh3hS8cIUhc.zip) (2.0 MB) Strange, I’m sure I attached, but here’s the full file compressed. ---
**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 2, 2023, 3:45pm UTC](https://klipper.discourse.group/t/print-fails-can-not-update-mcu-can0-config-as-it-is-shutdown/9259/4 "2023-07-02T15:45:37Z")
Have you already checked the cabling to the can board? The connectivity to the can board is quite unstable. ---
**Author:** ![petyusa](https://avatars.discourse-cdn.com/v4/letter/p/f08c70/32.png) [@petyusa](https://klipper.discourse.group/u/petyusa)\ **Post date:** [July 2, 2023, 3:49pm UTC](https://klipper.discourse.group/t/print-fails-can-not-update-mcu-can0-config-as-it-is-shutdown/9259/5 "2023-07-02T15:49:21Z")
I’ve been using it for almost a year now. Is there a way to check the connectivity? First I would try just to reconnect it, and test, if it seems bad, I would recrimp the connectors. ---
**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 2, 2023, 3:57pm UTC](https://klipper.discourse.group/t/print-fails-can-not-update-mcu-can0-config-as-it-is-shutdown/9259/6 "2023-07-02T15:57:32Z")
If the board is mounted to the extruder, it can appear that due to the movement cables can weaken and break. First you may check at the points where the cables get to the board. ---
**Author:** ![petyusa](https://avatars.discourse-cdn.com/v4/letter/p/f08c70/32.png) [@petyusa](https://klipper.discourse.group/u/petyusa)\ **Post date:** [July 3, 2023, 7:57pm UTC](https://klipper.discourse.group/t/print-fails-can-not-update-mcu-can0-config-as-it-is-shutdown/9259/7 "2023-07-03T19:57:29Z")
Thanks for your help, I reconnected the wire on both ends, since then I printed a few parts, everything was fine, checked the logs, bytes\_invalid was always 0. ---
**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:57pm UTC](https://klipper.discourse.group/t/print-fails-can-not-update-mcu-can0-config-as-it-is-shutdown/9259/8 "2024-05-04T20:57:55Z")
Closed on May 4, 2024, 8:57pm UTC