Lost communications with MCU

General Discussion
1

Basic Information:

Printer Model: Voron2.4 v2 350
MCU / Printerboard: Leviathan, Nitehawk-SB, Eddy probe
Host / SBC Pi 4B
klippy.log
klippy.log.zip (4.2 MB)

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:

I keep getting the error Lost communications, some time it’s Lost communications with MCU ‘Mcu’ and some time it’s Lost communications with MCU ‘Eddy’. It can happen at different times during a print. This is a fairly new build. The cables going to the Nitehawk and Eddy are factory cables with factory ends, they are tightly seated. I am at a loss on how to fix this.
…

2

See Timeout with MCU / Lost communication with MCU

3

This is my latest Lost communication error. The 6 hour print was 80% complete when it shut down. I thought my problem was due to using a web cam so I was running this print without the web cam but that didn’t help. Any ideas?

klippy-4.log.zip (3.7 MB)

4

Is there any fix for the constant error Lost Communication to MCU? I know about all the usual fixes, check wire connections, replace cables, shield cables, over heating but after all these there must be something in the Klipper software that is causing this. I am lucky if I can get one good print out of three. When a print fails it like 80-90% complete. If this is a error that can never be fixed how about Klipper putting a restore point in the software so that the print could be finished after the error.

5

I have a good feeling that if you were to start a “General Discussion” post and include all the requested information regarding your printer and issue (including your klippy.log) you’ll get some specific information that will be helpful.

1 Like
6

Thanks, I have already added a post with all the required information.

7

Where? Not in this thread.

8

General discussion. I was hoping the developers were working on a solution like a save point that’s why I posted here.

9

Posts moved here. Please refrain from double posting or similar actions. This neither makes it easier for the supporters nor will it gain any more traction.

Regarding the error message: You need to be aware that Klipper is only reporting a symptom. In this case, the missing heartbeats for an MCU.
Klipper has no way of knowing why these heartbeats are suddenly no longer received, and there are multiple possible causes.
As unfortunate as it is, the only option is to systematically exclude each point one by one.

1 Like