Usbserial module not registering USB Serial support for ch341-uart

General Discussion
1

Basic Information:

Printer Model: FLSUN QQ
MCU / Printerboard: MKS Robin mini V2 (they renamed it to FLSUN hispeed V1.0)
klippy.log
klippy(10).log (151.3 KB)

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:

The output follows the ideal dmesg output from here How-To Trouble-Shoot, but the line

usbserial: USB Serial support registered for ch341-uart

is missing and i suspect that is why /dev/ttyCH341USB0 (which shows up right now) is not mapped to /dev/ttyUSB0.

few questions:

  1. is this leading to klipper not able to connect (see klipper.log, connection timeout)?
  2. how to fix this? usbserial does show up in lsmod, just that its not doing what it is supposed to

additional infos:

lsusb has the line

Bus 003 Device 009: ID 1a86:7523 QinHeng Electronics CH340 serial converter

lsb_release -a

No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 22.04.3 LTS
Release:	22.04
Codename:	jammy

uname -r

6.5.0-18-generic

LattePanda Sigma

nothing relevant in /dev/serial/by-id or /dev/serial/by-path

printer.cfg:

[mcu]
serial: /dev/ttyCH341USB0

[virtual_sdcard]
path: /home/nestspace/printer_2_data/gcodes
on_error_gcode: CANCEL_PRINT

[printer]
kinematics: none
max_velocity: 1000
max_accel: 1000
dmesg 
[    3.680890] usbcore: registered new interface driver usbserial_generic
[    3.680907] usbserial: USB Serial support registered for generic
[    3.935457] usbcore: registered new interface driver cdc_acm
[    3.976374] usbcore: registered new interface driver btusb
[    3.987571] input: BJYP-KX Device BJYP-KX-V2.29 as /devices/pci0000:00/0000:00:14.0/usb3/3-5/3-5.2/3-5.2:1.0/0003:28E9:028A.0003/input/input21
[    4.006125] hid-multitouch 0003:28E9:028A.0003: input,hiddev1,hidraw2: USB HID v1.10 Device [BJYP-KX Device BJYP-KX-V2.29] on usb-0000:00:14.0-5.2/input0
[   57.614680] usb 3-8: new full-speed USB device number 8 using xhci_hcd
[   57.764250] usb 3-8: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.63
[   57.764256] usb 3-8: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[   57.764258] usb 3-8: Product: USB2.0-Serial
[   57.773891] usb_ch341 3-8:1.0: ttyCH341USB0: ch341 USB device
[   57.774073] usbcore: registered new interface driver usb_ch341
[  365.276704] usbcore: deregistering interface driver usb_ch341
[  365.277015] usb_ch341 3-8:1.0: ch341 usb device disconnect.
[  365.315596] usb_ch341 3-8:1.0: ttyCH341USB0: ch341 USB device
[  365.315726] usbcore: registered new interface driver usb_ch341
[  376.570289] usb 3-8: USB disconnect, device number 8
[  376.570685] usb_ch341 3-8:1.0: ch341 usb device disconnect.
[  387.534022] usb 3-8: new full-speed USB device number 9 using xhci_hcd
[  387.683161] usb 3-8: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.63
[  387.683165] usb 3-8: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[  387.683166] usb 3-8: Product: USB2.0-Serial
[  387.685251] usb_ch341 3-8:1.0: ttyCH341USB0: ch341 USB device
2

Looks like the board is not correctly flashed.
Closely follow the information on top of Klipper-for-MKS-Boards/MKS Robin Mini V2.x/generic-mks-robin-mini-v2.cfg at main · makerbase-mks/Klipper-for-MKS-Boards · GitHub and also refer to Issues flashing the printer board for further pointers.

3

thank you for your reply. What clockrate and baud rate shd i make menuconfig with? i followed that instruction very close and got the klipper.log error.

4

If no special requirements are mentioned then leave the default values. If you suspect you might have already messed them up, then run make distclean

Did you also follow:

# After running "make", run the following command:
#   ./scripts/update_mks_robin.py out/klipper.bin out/Robin_mini.bin
# Copy the file out/Robin_mini.bin to an TF card and then restart the
# printer with that SD card.
5

yes i have. the filename also changes to ROBIN_MINI.CUR

on another note, i noticed the raspi (latepanda) seems to be supplying power to the robin board (i turn off printer and board light still on, i plug in usb with printer off and board light turns on)

6

Well, this is what USB is commonly doing. There are some reports that it might be problematic on some boards, but I have not seen any hard evidence for these claims. Some put tape on the USB VCC pin.

I think the board is just not correctly flash. Follow the information in the above link.

7

Wow i just had to restart the rpi (latepanda) while my printer was pluged in

How intuitive

8

Usually not needed but could be some side effects in the Linux Operating System, e.g. due to previous updates.

9

Is there any solution? I currently have the exact same problem only on a MKS Robin E3.
I have even tried to flash a marlin version, which worked without any problems but after klipper is flashed the screen freezes at “update 100%” and when I repower it the screen shows “boot” and nothing happens.
I am quite sure this is caused by the board not being able to read the config on my host (linus laptop wich multiple instances). I am not getting any output on /dev/serial/by-id and everything eles is also just the same for me as for toshinari.

10

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