Basic Information:
Printer Model: Prusa Mk3 clone
MCU / Printerboard: einsy Rambo with atmega 32u2
Host / SBC: Ubuntu 22
klippy.log
klippy.zip (978.0 KB)
Describe your issue:
Hi I have anther of these usual MCU disconnects. I have flashed the atmega32u2 chip for the invalid_bytes problem , changed usb, changed printer electrical cable, put an ups . Maybe anyone here can help me understand whats happening by looking at the logs?
This is the dmesg output:
[Mon Nov 18 16:53:12 2024] cdc_acm 2-3:1.0: ttyACM0: USB ACM device
[Mon Nov 18 21:25:15 2024] usb usb2-port3: disabled by hub (EMI?), re-enabling…
[Mon Nov 18 21:25:15 2024] usb 2-3: USB disconnect, device number 8
[Mon Nov 18 21:25:16 2024] usb 2-3: new full-speed USB device number 9 using xhci_hcd
[Mon Nov 18 21:25:16 2024] usb 2-3: New USB device found, idVendor=2c99, idProduct=0002, bcdDevice= 1.00
[Mon Nov 18 21:25:16 2024] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Mon Nov 18 21:25:16 2024] usb 2-3: Product: Original Prusa i3 MK3
[Mon Nov 18 21:25:16 2024] usb 2-3: Manufacturer: Prusa Research (prusa3d.com)
[Mon Nov 18 21:25:16 2024] cdc_acm 2-3:1.0: ttyACM1: USB ACM device
journalctl doesn’t contain anything related to usb at the time of disconnection
Thanks everyone in advance.