Ender 3 V3 SE Printers Stop Communicating

General Discussion
1

Basic Information:

Printer Model: Ender 3 V3 SE (2)
MCU / Printerboard: CR4NS200320C13 (I believe)
Host / SBC RPi3 B
klippy Printer 1.log (2.1 MB)
klippy Printer 2.log (2.0 MB)

klippy.log

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

…So, I’m not even sure if this is a problem or just a power saving feature. But I have two printers attached to a single pi. They work without a problem for normal printing activity. But what I have noticed is when I leave them on and idling during the night or long (several hours) periods of time, they will stop communicating with the pi. Restarting frameware or the pi doesn’t fix the communication. But power cycling the printers does. I’m starting up a 3d printing farm and wanted to see if anyone else has seen this, if it’s actually a problem or a feature, and how to prevent it from happening? I’d like to make it so the printers, even when idling always remain in communication with the pi and Klipper.

I really appreciate any advice and help :slight_smile: <3

2

According to the log:

Timeout with MCU 'mcu' (eventtime=244853.551359)
Transition to shutdown state: Lost communication with MCU 'mcu'

Reason and possible causes are described here: Timeout with MCU / Lost communication with MCU

And no, it is not a power saving feature.

1 Like
3

Thanks for this reply! I feel stupid, I thought that error was more of a generic error meaning the printer lost connection for any reason. I’ll test the easy stuff tonight (USB cables) and then the other things and see if that fixes the problem! Thanks again for the help!

4

With my E3 V3 SE, I found that ditching the USB cable and going down the UART route gave me a much more reliable connection to the printer.
With USB (tried many cables) most times I would need to hard reset the printer a few times before it would connect to the Pi, with the GPIO connection, first time every time.

1 Like
5

Thanks for the reply! I think you’re right on the money. I tested a single printer for months using my USB A to C cable I bought for my Meta Quest 2. It never had communication problems for any diration of time. I bought some Amazon Basic cables, which I believe are the problem. I plugged one printer in with my high quality cable and the other with the Amazon Basic. The problem has gone away. I think I did find a cable that works, which aren’t cheap. But I’ll just buy those in the future. Then I’ll research the UART route. I’m doing a farm, so I’d like to avoid a lot of hands on work if possible. But if I have to go that route, then so be it.

Thanks for the advice everyone!

6

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