Kernel version | Linux Repetierserver 5.15.84-v8+ #1613 SMP PREEMPT Thu Jan 5 12:03:08 GMT 2023 aarch64 GNU/Linux
SBC model | RPi 3 Model B (aarch64)
Power supply used | (EG: 5.1V 2.5A original raspberry)
SD card used | (EG: SanDisk ultra)
Additional Information (if applicable)
Software title | Repetierserver
Was the software title installed freshly or updated/migrated? fresh
Can this issue be replicated on a fresh installation of DietPi?
← If you sent a “dietpi-bugreport”, please paste the ID here →
Bug report ID | echo $G_HW_UUID
Steps to reproduce
I connect my new Anycubic Vyper to the Pi3, but there is no serial port created. Works fine with a windows PC, and I can use a different 3D printer (Kobra) on the raspberry. Kobra has a ch341 USB-2-serial interface, which is not properly recognized by the OS.
Expected behaviour
Plug in 3D printer, serial port is created and works.
Actual behaviour
I tried installing a driver from GitHub - juliagoda/CH341SER: CH341SER driver with fixed bug, and now I see the interface in lsusb: Bus 001 Device 008: ID 1a86:7523 QinHeng Electronics CH340 serial converter
in dmesg I get errors:
[ 3363.482620] usb 1-1-port4: attempt power cycle
[ 3364.086299] usb 1-1.4: new full-speed USB device number 15 using dwc_otg
[ 3364.502256] usb 1-1.4: device not accepting address 15, error -32
[ 3364.582360] usb 1-1.4: new full-speed USB device number 16 using dwc_otg
[ 3365.000187] usb 1-1.4: device not accepting address 16, error -32
[ 3365.000365] usb 1-1-port4: unable to enumerate USB device
/dev/ttyUSB0 or something like that (that is what my octoprint is connecting to my Anet A8 is on)
Make sure your baud rate on Repetier server is set to 115200
If you can get to a shell do a
lsusb
and see if the printer device shows up on the list
Also doesn’t it have a tcp/ip connection built in…see if you can see the ip of the device at port 8876
What user are you running the repetier server as? The user that is running the program is needed in the dialout group for it to be able to get out
I have an Anycubic Kobra connected to the same Pi, that one works fine and is on ttyUSB0. The Vyper doesn’t show, even with the same cable and when I disconnect the Kobra.
With lsub, I did see the CF340 device after installing the driver from github I mentioned. I did a clean install of dietpi 18.5.2 beta, connected the Vyper, and dmesg throws the same error messages. Nothing pops up in /dev. Next I’ll do another clean install of the latest stable release and try the 3rd party driver again. Would be great if anyone has a clue what the error messages in dmesg mean…
I tried different cables and different ports. Error messages are always the same. I even tried a powered USB hub between the printer and the Pi, didn’t make a difference:
[ 103.759031] usb 1-1.3: new high-speed USB device number 17 using dwc_otg
[ 103.862297] usb 1-1.3: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice= 6.63
[ 103.862345] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 103.862370] usb 1-1.3: Product: USB2.1 Hub
[ 103.862392] usb 1-1.3: Manufacturer: GenesysLogic
[ 103.863829] hub 1-1.3:1.0: USB hub found
[ 103.864279] hub 1-1.3:1.0: 4 ports detected
[ 104.175032] usb 1-1.3.4: new full-speed USB device number 18 using dwc_otg
[ 104.279020] usb 1-1.3.4: device descriptor read/64, error -32
[ 104.491037] usb 1-1.3.4: device descriptor read/64, error -32
[ 104.707026] usb 1-1.3.4: new full-speed USB device number 19 using dwc_otg
[ 104.811023] usb 1-1.3.4: device descriptor read/64, error -32
[ 105.023027] usb 1-1.3.4: device descriptor read/64, error -32
[ 105.131536] usb 1-1.3-port4: attempt power cycle
[ 105.783081] usb 1-1.3.4: new full-speed USB device number 20 using dwc_otg
[ 106.199025] usb 1-1.3.4: device not accepting address 20, error -32
[ 106.303026] usb 1-1.3.4: new full-speed USB device number 21 using dwc_otg
[ 106.719022] usb 1-1.3.4: device not accepting address 21, error -32
[ 106.719391] usb 1-1.3-port4: unable to enumerate USB device
[ 157.297628] usb 1-1.3: USB disconnect, device number 17
[ 169.807065] usb 1-1.2: new full-speed USB device number 22 using dwc_otg
[ 169.891029] usb 1-1.2: device descriptor read/64, error -32
[ 170.079033] usb 1-1.2: device descriptor read/64, error -32
[ 170.267017] usb 1-1.2: new full-speed USB device number 23 using dwc_otg
[ 170.347020] usb 1-1.2: device descriptor read/64, error -32
[ 170.535022] usb 1-1.2: device descriptor read/64, error -32
[ 170.643210] usb 1-1-port2: attempt power cycle
[ 171.247028] usb 1-1.2: new full-speed USB device number 24 using dwc_otg
[ 171.663029] usb 1-1.2: device not accepting address 24, error -32
[ 171.743045] usb 1-1.2: new full-speed USB device number 25 using dwc_otg
[ 172.159033] usb 1-1.2: device not accepting address 25, error -32
[ 172.159285] usb 1-1-port2: unable to enumerate USB device
brand new pi4, clean dietpi install v8.15.2. Same problem:
lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
dmesg
[ 84.210330] usb 1-1.3: new full-speed USB device number 3 using xhci_hcd
[ 84.290580] usb 1-1.3: device descriptor read/64, error -32
[ 84.478560] usb 1-1.3: device descriptor read/64, error -32
[ 84.666326] usb 1-1.3: new full-speed USB device number 4 using xhci_hcd
[ 84.746571] usb 1-1.3: device descriptor read/64, error -32
[ 84.934556] usb 1-1.3: device descriptor read/64, error -32
[ 85.042990] usb 1-1-port3: attempt power cycle
[ 85.646328] usb 1-1.3: new full-speed USB device number 5 using xhci_hcd
[ 85.646610] usb 1-1.3: Device not responding to setup address.
[ 85.854611] usb 1-1.3: Device not responding to setup address.
[ 86.062330] usb 1-1.3: device not accepting address 5, error -71
[ 86.142328] usb 1-1.3: new full-speed USB device number 6 using xhci_hcd
[ 86.142682] usb 1-1.3: Device not responding to setup address.
[ 86.350544] usb 1-1.3: Device not responding to setup address.
[ 86.558321] usb 1-1.3: device not accepting address 6, error -71
[ 86.559024] usb 1-1-port3: unable to enumerate USB device
[ 95.290326] usb 1-1.1: new full-speed USB device number 7 using xhci_hcd
[ 95.370581] usb 1-1.1: device descriptor read/64, error -32
[ 95.558557] usb 1-1.1: device descriptor read/64, error -32
[ 95.746326] usb 1-1.1: new full-speed USB device number 8 using xhci_hcd
[ 95.826562] usb 1-1.1: device descriptor read/64, error -32
[ 96.014563] usb 1-1.1: device descriptor read/64, error -32
[ 96.122932] usb 1-1-port1: attempt power cycle
[ 96.726326] usb 1-1.1: new full-speed USB device number 9 using xhci_hcd
[ 96.726602] usb 1-1.1: Device not responding to setup address.
[ 96.934543] usb 1-1.1: Device not responding to setup address.
[ 97.142323] usb 1-1.1: device not accepting address 9, error -71
[ 97.222336] usb 1-1.1: new full-speed USB device number 10 using xhci_hcd
[ 97.222593] usb 1-1.1: Device not responding to setup address.
[ 97.430553] usb 1-1.1: Device not responding to setup address.
[ 97.638323] usb 1-1.1: device not accepting address 10, error -71
[ 97.639361] usb 1-1-port1: unable to enumerate USB device
Hope you can use this for pinpointing the problem. Will also get in touch with Anycubic, see what they say.
Nacubic support suspects a faulty mainboard. Will hopefully send replacement. I’ll keep you posted once it happened - perhaps it really is a hardware problem oin the printer’s side.
Replacement board came today. I replaced the old one, and now USB connection works without a hitch on a fresh install of DietPi. So it was the printer’s hardware after all. Sorry for the confusion!