Lost Communication with the MCU 'EBB42-1'

General Discussion
1

Basic Information:

Printer Model: Custom
MCU / Printerboard: Manta M8P
Host / SBC CB2
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:

Getting lost communication erros to my head one EBB42 tool board. I uploaded the data to the Sineos github analyzer but just cant see if there is anything wrong. I compared to a print that was normal and it appears to be about the same. Can anybody look at my klippy log and help me point out possible errors? Thank you!
klippy (EBB42-1 4-22-25).log (4.5 MB)

…

2

See Timeout with MCU / Lost communication with MCU. Often this is a sign of general hardware instability, and unfortunately, Klipper can detect that something went wrong (i.e. the relevant MCU stopped responding) but not the specific cause.

3

Thank you Sineos, we will keep digging around the hardware until we get to the bottom of it.

4

Hi all. After chasing my tail for a couple weeks I can now say the problem is solved. What was it? EMI from the stepper motor wires. Solution, reroute USB cables. Reducing EMI on the motor wires with ferrite beads will obviously help too. I hope our struggles will help somebody out there with similar issues. Thank you.

2 Likes
5

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