MCU / Printerboard:MKS GEN L V1.0/MKS ROBIN NANO v1.2
Hi everyone, I’m from China.
Some time ago, I kept receiving “losing communication with MCU” due to too many errors. There is really no solution to effectively. I have changed a lot of accessories. In fact, I have replaced the following: Replaced three new devices and installed a new Armbian system, the MCU lost communication, the MKS GEN L1.0 motherboard was replaced, the MCU lost communication The MKS Robin Nano 1.2 was replaced, and the MCU lost communication Replaced the new power supply, the same MCU lost communication, replaced the new driver, still shows that the MCU lost communication, unplugged unrelated pins, probed, lost material, MCU lost communication Replaced 2, brand new data cable with magnetic ring, (4-inch data cable), the same MCU lost communication data cable is attached to 5V power supply, the motherboard and the host do not supply each other, and GND, D+, D- are reserved, and it also shows that the MCU has lost communication. Updated motherboard firmware and system, MCU lost communication The above interfaces are well wiring, but still can’t find the reason The frequency of the motherboard and host is completely normal, and the reason is not found. Can anyone help to analyze it?
I struggled with the same problem a lot.
No cable or magnetic ring solve my problem
I was using a sonic pad at that time, but it was giving an MCU loss error at some times.
there was no solution. I installed Raspberry Pi4 and Klipper.
but the problem still persist, mcu lost
When UART communicated, all my problem was solved.
print for a very long time and the connection is never lost.
I used only shielded cable for UART
You can try it, maybe your problem will be solved too
Since both of you are new here, you might read How-To Trouble-Shoot
Search for " Connection Problems to the Printer Board"
… and of course use USB, not UART!
The result still doesn’t work. MCU communication is also lost. I have already called up the dmesg file on the host. Can you help me analyze it? dmesg.txt (34.1 KB)
In your above posted klippy.log I found serial = /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
The syntax seems wrong (=), have a look here Frequently Asked Questions - Klipper documentation
and the USB id doesn’t make sense.
I would try serial: /dev/ttyACM0
or serial: /dev/ttyACM1
Yes, I connected through USB, you mentioned “The syntax seems wrong (=)”, but in the printer.cfg configuration, fill in “[mcu]
serial:/dev/serial/by-id/usb-Klipper_lpc1768_1F001616A6175753C6B9524F050000F5-if00”
I think I have found the cause of the fault. I highly suspect that it is the Y-axis electromechanical or Y-axis wire failure. I am very unsure of the cause. I just replaced the new electromechanical and new connecting wires today. So far, the status is normal and it is a temporary fault. The reason is the Y-axis electromechanical/connection cable, which is still being investigated further.
the cause of the “losing communication with MCU” fault has been found. The fault is “poor contact in the extruder electromechanical wiring” causing MCU interference. I have replaced the new connection line, and the “losing communication with MCU” has not appeared again since. So far, the machine has been running normally for 8 hours! ！！！！！
！！！！！