Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

USB disconnect/timeout issues with Ender 7 with ch341-uart USB2Serial #34

Open
ganzgustav22 opened this issue Apr 20, 2022 · 2 comments
Labels
GH - Bug Something isn't working GH - Evaluation Needed

Comments

@ganzgustav22
Copy link

Browser

Chrome

Device

Other (Please tell us below)

Operating System

Linux

What happened

From time to time (usually every few hours, sometimes it lasts longer, for maybe 12 hours) I get disconnected from the printer because of those dreaded Linux Kernel USB issues Linux and especially the Pi platform have been plagued by for years.

This happens only on a Pi4. No, it's not a wiring/shielding/grounding or power supply issue. Switched the exact same sdcard from the Pi4 over to a Pi3B+ and the problem is gone.

Linux kernel log looks like this when it happens:

[45407.479837] ch341-uart ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[45407.480360] ch341-uart ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[45407.580037] ch341-uart ttyUSB0: usb_serial_generic_write_bulk_callback - urb stopped: -32
[45407.606245] ch341-uart ttyUSB0: usb_serial_generic_write_bulk_callback - urb stopped: -32
[45407.657376] ch341-uart ttyUSB0: usb_serial_generic_write_bulk_callback - urb stopped: -32
[45407.732291] usb 1-1.3: USB disconnect, device number 3
[45407.733660] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0
[45407.733766] ch341 1-1.3:1.0: device disconnected
[65765.234395] usb 1-1.3: new full-speed USB device number 4 using xhci_hcd
[65765.380539] usb 1-1.3: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.64
[65765.380562] usb 1-1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[65765.380580] usb 1-1.3: Product: USB Serial
[65765.385347] ch341 1-1.3:1.0: ch341-uart converter detected
[65765.392747] usb 1-1.3: ch341-uart converter now attached to ttyUSB1
[74477.881226] ch341-uart ttyUSB1: usb_serial_generic_read_bulk_callback - urb stopped: -32
[74477.884539] ch341-uart ttyUSB1: usb_serial_generic_read_bulk_callback - urb stopped: -32
[74478.083060] ch341-uart ttyUSB1: usb_serial_generic_write_bulk_callback - urb stopped: -32
[74478.083842] ch341-uart ttyUSB1: usb_serial_generic_write_bulk_callback - urb stopped: -32
[74478.089993] usb 1-1.3: USB disconnect, device number 4
[74478.092247] ch341-uart ttyUSB1: ch341-uart converter now disconnected from ttyUSB1
[74478.092346] ch341 1-1.3:1.0: device disconnected

What did you expect to happen

No random USB disconnects

How to reproduce

  • Connect an Ender7 (probably other printers with ch341 USB2Serial will also show the issue) to fluiddpi
  • Print something that takes a few hours
  • Wait until the print stops and Klipper giving an error message
  • Check Linux Kernel log with "dmesg" to see if you got those "urb stopped" messages

Additional information

No response

@matmen matmen transferred this issue from fluidd-core/fluidd Apr 20, 2022
@matmen
Copy link
Member

matmen commented Apr 20, 2022

I'm not sure if this would be a FluiddPi issue. I personally can't reproduce this, though maybe you are willing to troubleshoot: Is this reproducible on a clean Raspberry Pi OS install with Klipper / fluidd installed via KIAUH?

@ganzgustav22
Copy link
Author

It's not a bug in the Fluiddpi components or changes to the base Raspberry Pi OS image, indeed. It's a kernel and/or Pi firmware issue within Raspberry Pi OS. But it affects FluiddPi users, so I thought I report it here so that people can find it when they face the same issue.

I can open an issue on the Raspberry Pi github, but my experience is that these issues often do not get fixed because they are sporadic, hard to debug and need specific hardware.

Sometimes they get fixed "by accident", when a larger kernel release bump occurs, sometimes they get re-introduced later, etc. it's quite annoying.

What still left to try is using the Pi4 USB-C power connector as a workaround (It's basically the same old USB controller from the older Pis, so there is hope that it works with that one). Need to order a cable first and power the Pi4 via it's GPIO pins. I can report back if that turns out successful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
GH - Bug Something isn't working GH - Evaluation Needed
Projects
None yet
Development

No branches or pull requests

2 participants