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

[sender]

After updating octoprint to v3 (python?) I cant get connection to my printer. This worked well for over 2 years with the previous installation.

I get:

I tried other cables, resetting, restarting, rebooting, log checking etc... can't find any relevant.

Have you tried running in safe mode?

Yes

Did running in safe mode solve the problem?

No

Systeminfo Bundle

See attached
octoprint-systeminfo-20211029134525.zip (138.2 KB)

same issue:?

Offline (Error: No more candidates to test, and no working port/baudrate combination detected.)

I was encouraged when I found this post until I read the part about "I don't know what I am doing" You were kidding, right? I tried this anyway figuring I had nothing to loose. The only way I know of to fix this is to restore from backup. Here is what I got... pi@octopi:/dev $ sudo del ttyAMA0 sudo: del: command not found

Extra info:

2021-10-29 13:44:14,662 - Changing monitoring state from "Offline" to "Detecting serial connection"
2021-10-29 13:44:14,748 - Performing autodetection with 0 port/baudrate candidates: 
2021-10-29 13:44:14,750 - Changing monitoring state from "Detecting serial connection" to "Error"
2021-10-29 13:44:14,753 - Changing monitoring state from "Error" to "Offline after error"
2021-10-29 13:45:07,259 - Changing monitoring state from "Offline" to "Detecting serial connection"
2021-10-29 13:45:07,379 - Performing autodetection with 0 port/baudrate candidates: 
2021-10-29 13:45:07,380 - Changing monitoring state from "Detecting serial connection" to "Error"
2021-10-29 13:45:07,384 - Changing monitoring state from "Error" to "Offline after error"
2021-10-29 13:52:31,177 - Changing monitoring state from "Offline" to "Detecting serial connection"
2021-10-29 13:52:31,240 - Performing autodetection with 0 port/baudrate candidates: 
2021-10-29 13:52:31,240 - Changing monitoring state from "Detecting serial connection" to "Error"
2021-10-29 13:52:31,242 - Changing monitoring state from "Error" to "Offline after error"

[Charlie_Powell]

Try some of the solutions in this post:

OctoPrint can't connect to my printer

OctoPrint only shows one port "AUTO" to connect to The underlying operating system (e.g. OctoPi) isn't even seeing your printer's serial port. This is something you have to solve outside OctoPrint first before you can proceed. Check the following: Make sure the cable you are using for the connection between your printer and OctoPrint is a fully connected cable and not a power-only charging cable. If in doubt, try multiple cables and/or buy one specifically suited for data transfer. Verify th…

Halfway through your log file, it does look like the printer connected. All the other times there's no devices connected.

Can you remember what you did for that attempt that made it work

2021-10-29 13:24:10,991 - octoprint.util.comm - INFO - Serial detection: Performing autodetection with 7 port/baudrate candidates

[sender]

Hi, thanks for responding!

Yes out of I think 20 times it connected. I think it had to do with some sort of order in powering on/off the Pi and the printer.I tried every combination after that 1 time but it never worked again.

Strange thing is, it always worked, never hicked up...

I read the post and tried the solution but no reveal.

[Charlie_Powell]

If you run dmesg -w and then unplug and plug in the printer, does anything appear? does the printer appear under lsusb?

[sender]

@Charlie_Powell

dmesg -w

[  622.480549] rpi_firmware_get_throttled: 8 callbacks suppressed
[  622.480559] Under-voltage detected! (0x00050005)
[  627.500508] usb 1-1.1.3: new full-speed USB device number 9 using dwc_otg
[  627.600569] usb 1-1.1.3: device descriptor read/64, error -32
[  627.820494] usb 1-1.1.3: device descriptor read/64, error -32
[  628.040501] usb 1-1.1.3: new full-speed USB device number 10 using dwc_otg
[  628.140574] usb 1-1.1.3: device descriptor read/64, error -32
[  628.360502] usb 1-1.1.3: device descriptor read/64, error -32
[  628.480644] usb 1-1.1-port3: attempt power cycle
[  629.140519] usb 1-1.1.3: new full-speed USB device number 11 using dwc_otg
[  629.580509] usb 1-1.1.3: device not accepting address 11, error -32
[  629.680522] usb 1-1.1.3: new full-speed USB device number 12 using dwc_otg
[  630.120522] usb 1-1.1.3: device not accepting address 12, error -32
[  630.120649] usb 1-1.1-port3: unable to enumerate USB device
[  651.600777] Under-voltage detected! (0x00050005)

pi@octopi:~ $ lsusb
Bus 001 Device 008: ID 0424:7800 Standard Microsystems Corp.
Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I don't know what the printer is

[Ewald_Ikemann]

@sender

[ 651.600777] Under-voltage detected! (0x00050005)

BTW: the undervoltage is still there. This can corrupt USB connection too.

Already tried this: ?

Put tape on the 5V pin - Why and how

First of all this whole tutorial isn't a mandatory mod - you just need it if you run into issues (weird things are happening and you've already ruled out the more common suspects) or if the always running fan and illuminated display (even when the printer is turned off) disturbes you. I'm starting with the why part: If you connect a 3D printer via USB to your Raspberry Pi it can lead to all sorts of power related issues. Most of the time those issues occur only if you turn on your pi before …

[sender]

Appreciate al the replies!

Thing is, it worked for over 2 years with these cables and power supply... what's new in v3 octoprint causing this?

[Ewald_Ikemann]

@sender

v3 octoprint

V3 OctoPrint

[sender]

@Ewald_Ikemann

V3 OctoPrint

Upgrading your OctoPrint install to Python 3

If you are still running Python 2 and using OctoPrint 1.7.0+, you will start to see warnings like this: [image] You need to upgrade your OctoPrint install to use Python 3, as Python 2 is end-of-life and a future OctoPrint version will no longer support running using Python 2. In addition, there's at least 39 plugins that already don't support Python 2 and more will follow, that you won't be able to take advantage of. You should upgrade as soon as possible. How can I upgrade? The process is s…

[sender]

I tried this and yes, now when I power down the printer the display is not lighted anymore... That better!

I tried some in and out and the printer is now "seen". I am going to print right away I need something and then troubleshoot further...

[foosel]

@sender

what's new in v3 octoprint causing this?

OctoPrint doesn't cause undervoltage. Python 3 doesn't cause undervoltage. Inadequate power supplies, inadequate wiring and back powering cause undervoltage.

[sender]

I know, but what's the point? I do not care about them... as long as it works... and is did for 2 years stable.

[foosel]

Undervoltage means it works until it doesn't. Now it apparently doesn't. You can try to argue about this all day but the fact of the matter is, undervoltage has again and again been proven to be one of THE biggest reason for a whole variety of symptoms, which is why it should be your utmost priority to fix this when it's being detected. And with "fix it" I don't mean disabling the Pi Support Plugin, but actually fix the underlying problem.

And since fixing the back powering apparently fixed your issue, I'd say you just saw a very good example of how undervoltage can be cause or symptom of a whole range of issues yourself.

[sender]

I'm not arguing, I agree, but having 3 PSUs of good brands, cables, etc. I can't solve that way, so I need to do else.

[sender]

So I replaced my PSU with a formal original pi psu and the error about insufficient power is gone. I still cannot connect to my ender 3d pro again... what's next?

The bundle:
octoprint-systeminfo-20211105152546.zip (60.8 KB)

[sender]

Please help

[Ewald_Ikemann]

Does the printer connect to a PC running pronterface?

And please turn off the DEBUG. It fills the log over 80% - but does not help here.

What is this plugin?

Convert TF to SD (1.0.2)

And this one does not work with Python 3.7:

Filament Sensor Revolutions

[sender]

Instantly after updating octoprint it did not connect anymore... I will try pronterface soon but bet it will... any other thoughts?

[Charlie_Powell]

@Charlie_Powell

If you run dmesg -w and then unplug and plug in the printer, does anything appear? does the printer appear under lsusb ?

You were getting errors in the log about reading from the USB ports previously, are these still occurring? Previously, it was the OS unable to communicate with the USB device. Trying to work out what is broken is key here.

You have 3 things that could be broken:

• The Pi's USB ports - through undervoltage, damage, etc. they may not be working correctly. Plugging the printer into another device could test if this is the case.
• The USB cable, swapping the cable with a known working (for communication) cable is the obvious way to test this.
• The printer's USB port or something else on the printer mainboard. This is probably the most difficult to test, since most people don't have another printer to quickly test with.

[sender]

Hi, I do very much appreciate all the help and replies!

But why is it so hard to get this: It worked for over a year very well. Even moments before I updated to the latest version of octoprint. I do not believe that an update suddenly broke the physicals... and as linked above, I am not the only one with this sudden issue.
After updating I tried 3 different power supplies, 3 different DATA usb cables and I bought an original raspberry pi power supply, all to no avail of the connection problem.

But a said before, I will rule this out.

Is there any other that I can check from octoprint perspective?