Can not connect to printer anymore

What is the problem?

WRITE HERE

I upgraded Octoprint a few months back, and ever since I can not connect to my printer via USB.

What did you already try to solve it?

WRITE HERE

I have tried multiple ports on the raspberry pi, different cables, played with

Have you tried running in safe mode?

WRITE HERE

Yes, it still says "no serial port found"

Did running in safe mode solve the problem?

WRITE HERE

no

Systeminfo Bundle

You can download this in OctoPrint's System Information dialog ... no bundle, no support!)

WRITE HERE

Additional information about your setup

OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible

WRITE HERE

[ 0.000000] Linux version 5.10.103-v7+ (dom@buildbot) (arm-linux-gnueabihf-gc c-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1529 SMP Tue Mar 8 12:21:37 GMT 2022
[ 0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
[ 0.000000] CPU: div instructions available: patching division code
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instructio n cache
[ 0.000000] OF: fdt: Machine model: Raspberry Pi 3 Model B Rev 1.2
[ 0.000000] random: fast init done
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] Reserved memory: created CMA memory pool at 0x34000000, size 64 M

Printer is a CR6SE, running on a Pi3 Mod B

octoprint-systeminfo-20220908224054.zip (140.3 KB)

Here is output from my dmesg

[ 5798.697657] usb 1-1.4: new full-speed USB device number 4 using dwc_otg
[ 5798.830698] usb 1-1.4: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.64
[ 5798.830720] usb 1-1.4: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 5798.830735] usb 1-1.4: Product: USB Serial
[ 5798.913395] usbcore: registered new interface driver usbserial_generic
[ 5798.913466] usbserial: USB Serial support registered for generic
[ 6885.638619] usb 1-1.4: USB disconnect, device number 4
[ 6887.726024] usb 1-1.3: new full-speed USB device number 5 using dwc_otg
[ 6887.869073] usb 1-1.3: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.64
[ 6887.869095] usb 1-1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 6887.869111] usb 1-1.3: Product: USB Serial
[ 6890.760620] usb 1-1.3: USB disconnect, device number 5

thank you

Try it with and without SD card inserted in the printer

I tried that yesterday too. Still nothing.

I am getting message "no serial port found" now in the gui. I don't know if this is a new message or not. Is the OS not seeing the usb's on the Pi? is the Pi bad? Or is that a generic message when the printer isn't seen?

I wanted to add that I was able to connect the printer to my PC and control it via Cura, so the problem is either with the software upgrade, or the Pi.

What results do you get if you run lsusb on the terminal?

The other thing to do is to run dmesg -w, and then plug in the printer and you should see 'live' if the USB device is being recognised and if there are no errors. If it connects & disconnects straight away, there's probably an issue somewhere. It won't be an issue with OctoPrint upgrades, as this kind of thing is beneath it in the OS level.

here is my dmesg -w after unplugging and plugging back in -- I couldn't watch the screen, as I am isolating because of covid

[ 4722.141581] usb 1-1.5: USB disconnect, device number 4
[ 4736.513460] usb 1-1.5: new full-speed USB device number 5 using dwc_otg
[ 4736.646527] usb 1-1.5: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.64
[ 4736.646548] usb 1-1.5: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 4736.646564] usb 1-1.5: Product: USB Serial

here is my lsusb and lsusb -v info

under the -v it said it couldn't open the usb adapter

pi@octopi:~ $ lsusb

Bus 001 Device 004: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter

Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter

Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

pi@octopi:~ $

pi@octopi:~ lsusb Bus 001 Device 004: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub pi@octopi:~

Bus 001 Device 004: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x1a86 QinHeng Electronics
idProduct 0x7523 HL-340 USB-Serial adapter
bcdDevice 2.64
iManufacturer 0
iProduct 2
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0027
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 98mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 1
bInterfaceProtocol 2
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 1

Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 0
bDeviceProtocol 1
bMaxPacketSize0 64
idVendor 0x0424 Standard Microsystems Corp.
idProduct 0xec00 SMSC9512/9514 Fast Ethernet Adapter
bcdDevice 2.00
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0027
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 2mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 255
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 4

Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0
bDeviceProtocol 2 TT per port
bMaxPacketSize0 64
idVendor 0x0424 Standard Microsystems Corp.
idProduct 0x9514 SMC9514 Hub
bcdDevice 2.00
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0029
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 2mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0
bInterfaceProtocol 1 Single TT
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 12
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0
bInterfaceProtocol 2 TT per port
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 12

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0
bDeviceProtocol 1 Single TT
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0002 2.0 root hub
bcdDevice 5.10
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0019
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 12

You need to go into your router and search thru your Ethernet cable. Works every time

How will that help when the issue is not with the network, but the USB connection to the printer?

I wanted to verify that the OS saw the USB ports, so I put a thumb drive in one of the ports, and mounted it. I was able to mouth it and write to the USB. This tells me it's not the hardware or the OS, and it's something with octopirint that the upgrade changed.

I also put a camera in one of the USB ports, and Octoprint doesn't see it either.

Any suggestions? Do I wipe and reinstall?

1 Like

You might try 'ls /dev/tty*` and look for the proper usb device to connect to. Probably something like /dev/ttyUSB0. Then in the connection screen on octoprint verify that the correct device is selected before you click the 'connect' button.

Another thing that might interfere is the speed (baud rate) of the port. Some people use the fastest speed available, but I have found that limiting the connection baud rate to 57600 is more than adequate for good connections as well as the handling the fastest print mode my printer handles. I never get retransmit errors with octoprint. Higher speeds inherently are more sensitive to interference.

I don't know if there are any printers with changable baudrate out there. I know that marlin supports that feature with BAUD_RATE_GCODE, but I highly doubt that it is enabled on any stock firmware.

Even if it was enabled you can't just connect with a random baudrate - you have to connect with the fixed baudrate, change the baudrate via gcode and then connect again with the new baudrate.

Hello @Kermit5432 !

That was already mentioned (#8).

Fixed baud rate is correct. I use repetierhost firmware and configured the baud rate before I compiled the firmware. Repetier compiles it into the firmware as fixed for that machine. Marlin firmware is similar but uses a different approach to setting it..

I have never used a printer with OEM firmware so have no experience in how that would work but to me it seems that setting a baudrate that is more than adequate for the capabilities of the printer but stays below the rate where transmission errors begin to be experienced is wise. For me that approach says to use either 115200 or 57600 in most cases.

I have seen threads here where the user had configured 250000 as the baud rate and was getting significant retransmission percentages (and having trouble with the prints).

In this case the OP is having trouble connecting after an update, so it seems reasonable that the baud rate may be a factor to consider.

Have you tried to connect to a PC with Pronterface?

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