Wont connect to printer

Get Help
1

What is the problem?

Same issue I had here. Everything was working fine. I did the 1.6.1 update. Powered off the Ender to change the bowden. Turned it back on the RPi does not see the Ender.

In the UI, I get:

State: **Offline after error**
No more candidates to test, and no working port/baudrate combination detected.

With only "Auto" as the options in Serial Port.

lsusb does not show the printer connected. Here's the dmesg | tail -n 20

[  128.441939] usb 1-1.4: Device not responding to setup address.
[  128.661716] usb 1-1.4: device not accepting address 10, error -71
[  128.662047] usb 1-1-port4: unable to enumerate USB device
[  157.291703] usb 1-1.4: new full-speed USB device number 11 using xhci_hcd
[  162.771660] usb 1-1.4: new full-speed USB device number 12 using xhci_hcd
[  162.871905] usb 1-1.4: device descriptor read/64, error -32
[  163.311892] usb 1-1.4: device descriptor read/64, error -32
[  163.531650] usb 1-1.4: new full-speed USB device number 13 using xhci_hcd
[  163.631890] usb 1-1.4: device descriptor read/64, error -32
[  163.851876] usb 1-1.4: device descriptor read/64, error -32
[  163.971901] usb 1-1-port4: attempt power cycle
[  164.631655] usb 1-1.4: new full-speed USB device number 14 using xhci_hcd
[  164.631921] usb 1-1.4: Device not responding to setup address.
[  164.851941] usb 1-1.4: Device not responding to setup address.
[  165.071650] usb 1-1.4: device not accepting address 14, error -71
[  165.171653] usb 1-1.4: new full-speed USB device number 15 using xhci_hcd
[  165.172008] usb 1-1.4: Device not responding to setup address.
[  165.391881] usb 1-1.4: Device not responding to setup address.
[  165.611654] usb 1-1.4: device not accepting address 15, error -71
[  165.611962] usb 1-1-port4: unable to enumerate USB device

lsusb

Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
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

So its not even seeing the Ender in the OS. I thought it could be a Python 2 vs 3 so I ran the upgrade script. No changes.

What did you already try to solve it?

  • Different cords
  • Different power supplies
  • New image (.18 Octopi and 1.5.2 OctoPrint)
  • New card
  • New RPi
  • Connecting with my Win 10 laptop and using Cura does work

Have you tried running in safe mode?

Yes, no difference

Did running in safe mode solve the problem?

No

Systeminfo Bundle

You can download this in OctoPrint's System Information dialog ... no bundle, no support!)
octoprint.log (122.6 KB)
octoprint-systeminfo-20210601165135.zip (30.1 KB)

Additional information about your setup

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

OctoPi 0.17
OctoPrint 1.6.1
Raspberry Pi 4 B
Ender 3 Pro

2

Hello @wh1skey6 !

You already had a successful print after the update to 1.6.1:

2021-06-01 09:22:26,969 - octoprint.startup - INFO - ******************************************************************************
2021-06-01 09:22:26,971 - octoprint.startup - INFO - Starting OctoPrint 1.6.1
2021-06-01 09:22:26,971 - octoprint.startup - INFO - ******************************************************************************
...
2021-06-01 09:33:14,673 - octoprint.util.comm - INFO - Changing monitoring state from "Operational" to "Starting"
2021-06-01 09:33:14,684 - octoprint.printer.standard.job - INFO - Print job started - origin: local, path: CE3PRO_HeadphoneOrganizerRemix.gcode, owner: dlam, user: dlam
2021-06-01 09:33:14,690 - octoprint.plugins.PrintJobHistory - INFO - Try reading Temperature from PreHeat-Plugin...
2021-06-01 09:33:14,701 - octoprint.plugins.PrintJobHistory - WARNING - ... PreHeat Button Plugin not installed/enabled
2021-06-01 09:33:14,757 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-06-01 09:33:14,773 - octoprint.util.comm - INFO - Changing monitoring state from "Starting" to "Printing"
2021-06-01 09:33:16,882 - octoprint.util.comm - INFO - Printer seems to support the busy protocol, will adjust timeouts and set busy interval accordingly
2021-06-01 09:33:33,756 - octoprint.util.comm - INFO - Telling the printer to set the busy interval to our "communicationBusy" timeout - 1s = 2s
2021-06-01 09:34:14,802 - octoprint.plugins.PrintJobHistory - INFO - Temperature from Printer '65.0' Tool 'tool0' '220.0'
2021-06-01 09:37:28,511 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2021-06-01 09:52:28,512 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2021-06-01 09:55:06,130 - octoprint.util.comm - INFO - Finished in 1311.460 s.
2021-06-01 09:55:06,131 - octoprint.util.comm - INFO - Changing monitoring state from "Printing" to "Finishing"
2021-06-01 09:55:06,146 - octoprint.printer.standard.job - INFO - Print job done - origin: local, path: CE3PRO_HeadphoneOrganizerRemix.gcode, owner: dlam
2021-06-01 09:55:06,182 - octoprint.plugins.PrintJobHistory - INFO - Print result:success, CaptureMode:successful
2021-06-01 09:55:06,192 - octoprint.plugins.PrintJobHistory - INFO - Start capturing print job
2021-06-01 09:55:06,215 - octoprint.plugins.PrintJobHistory.SlicerSettingsParser - INFO - Start parsing Slicer-Settings
2021-06-01 09:55:06,223 - octoprint.util.comm - INFO - Changing monitoring state from "Finishing" to "Operational"

So the installation went fine.

You may check the other usual culprits in this case: the way the USB cable goes, power of the printer, restart the printer, EMI producing devices

3

It wasn't after I unplugged both the Pi and printer that the problem occurred so I wasn't sure if a power cycle triggered some weird nuanced issue. Question though, how I "used" to connect due to whatever issue was use a USB cable that had the power pin active. I'd plug that into the printer when the printer was off. Then I would connect Octoprint and it would connect. Then turn on printer.

If I did it any other way, it wouldn't connect. (Printer was on or power pin was taped over). Any ideas on how these would all be related?

4

For what its worth, I figured it out. The micro USB end has to be nested into the port at a specific angle.

5

Creality hardware... Likes things it's way or no way. Sometimes you get it first try, sometimes the colour of the USB cable is wrong. I have similar issues with mine & a particular USB cable, breathing heavily near it disconnected. Found another cable that made a secure connection and seems to be good so far, not disturbed by air any more.

1 Like