Double MCU failure/errors and failed print

[heavy]

Basic Information:

Printer Model: 2 ender 3 printers with instances
MCU / Printerboard: Btt pad 7 running two printers 4.2.2 & 4.2.7
klippy_E235.log (4.6 MB)

klippy_E400.log (4.6 MB)

Describe your issue:

I had both printers finally running perfectly. Today i powered on the printers and started getting the errors below on both printers.
Could not connect to the fluidd web interface either. reset and rebooted and that took care of the problems. I then started a print on E235 and it failed about 1 hour in. After that both printers have been flashing the same errors. I am stumped. i havent touched the config in a couple days! attatched both printer klippy’s

Failed automated reset of MCU ‘rpi’
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

&

Lost communication with MCU ‘rpi’
Once the underlying issue is corrected, use the
“FIRMWARE_RESTART” command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown

…

[EddyMI3D]

In both cases the issue is:

b'Got EOF when reading from device'

Got EOF when reading from device

Got EOF when reading from device Background This is actually an error raised by Linux operating system (OS) of the host and only reported by Klipper. It indicated that the contact to an attached hardware (mostly the MCU in this case) is lost. This can happen when the USB port is reset or the OS thinks the hardware has been disconnected. This error often appears in conjunction with the Timeout with MCU / Lost communication with MCU errors Reasons Unreliable connection between the printer-bo…

[heavy]

Thank you for the response! bummer! sounds like more senseless tinkering instead of printing. I’ve been at this for just shy of 2 weeks upgrading 3 printers to klipper after years of marlin headaches. hoping this isn’t a reoccurring thing with klipper as well.