2nd MCU loses communication after a print and needs to be reflashed..?

General Discussion
1

Basic Information:

Printer Model: Ender 3 V2
MCU / Printerboard: SKR Mini E3 V2 (main), Creality 4.2.2 (secondary)
Host / SBC: Raspberry Pi 4
klippy.log (299.9 KB)

klippy.log

I have a Ender 3 V2 that I’ve done a bunch of things to; one of them being replacing the stock Creality 4.2.2 board with a SKR Mini E3 V2. I did this because I added the 2nd Z screw and stepper motor and wanted to have separate Z outputs. Failing to read that the Mini E3 has a parallel dual Z output, I decided to use my original 4.2.2 board as an external 2nd MCU. I’m running only the extruder and my CR Touch from that while everything else is on the Mini E3.

It all seemed to be working fine, and then I started to have issues where I would get a time out while it was probing the bed for a bed mesh, or the extruder would not be extruding. This would be after a single successful print. Restarting Klipper and the firmware would then end up giving me a MCU failure and it couldn’t talk to the external 4.2.2 board.

Played with USB cables, used different ports on the Pi 4 running everything, making sure it was still seen if I did a “ls /dev/serial/by-id/*” (which it was) with no success. Ended up remaking the Klipper.bin file and reflashing the board. Once I did that, everything started to work again.. until after a print or 2 and it would all happen again.

Anyone have any thoughts of WTF could be going on? Is the board suddenly failing? It was working fine prior to it being removed but I also know that means nothing.

Of course after I did some (failed) printing last night, when I turned it back on this morning to get a Klipper.log file it came right up. But this has happened twice so far.
…

2

Welcome omgmyspleen,

did you try a fresh SDcard?

Good luck, hcet14

3

Thank you,

I did, and like I said it will work perfectly after reflash for a print or two and then starts to have issues.

This 4.2.2 board was used in the printer as the only MCU for about 2 years with no issue; this only started once I started using it externally as a 2nd MCU.

4

Your log seems to include only:

error: Can not update MCU 'mcu' config as it is shutdown
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

And it always mentions the ‘mcu’, which seems to be the SKR board.
This seems a bit strange overall, since this is not an error per se. See Can not update MCU '<name>' config as it is shutdown

5

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.