Offline (Error: No more candidates to test, and no working port/baudrate combination detected.) when PSU powers printer back up

Get Help
1

What is the problem?

Just started a couple of days ago. When print finishes and PSU shuts printer down..All ok.
When Psu turns printer on with connect automatically set, get this: Offline (Error: No more candidates to test, and no working port/baudrate combination detected.)
The quickest way to get back up is to reboot the Pi

What did you already try to solve it?

Tried changing firmware

Have you tried running in safe mode?

Don't know what safe mode is

Did running in safe mode solve the problem?

WRITE HERE

Complete Logs

octoprint.log, serial.log or output on terminal tab at a minimum, browser error console if UI issue ... no logs, no support! Not log excerpts, complete logs.)

WRITE HERE

Additional information about your setup

Pi 4 with latest version Creality E3V2 with 4.2.7 board.
Only thing that changed recently was the Access Anywhere plugin

OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible
Too big...here is snippet:troublelog.log (3.0 KB)

Why not have one place in Octorpint to gather all pertinent logs. My octoprint log is too big for this application. Couldn't find a serial log. What is the normal baud rate between the printer and the Pi?

2

Funny you should say that, systeminfo bundles are a new feature in 1.6.0 - a single zip file with all the important logs & details.

Blue words are links. Reading is the best way to learn :slightly_smiling_face:

When you turn the printer on, does unplugging the USB cable and plugging it back in make a difference? In the log snippet above (you can upload larger files, or zip them if neccessary) there is no device connected to the Pi apparently.

3

No, only rebooting pi. Not even restarting octoprint will fix it. Not really a full stopper. As long as PSU shuts the printer down when print is done, I can reboot pi before printing. If I start a print right after one finishes, before PSU shuts printer down, print starts fine. Only after PSU shuts it down. The only update I remember lately was Access Anywhere. In that snippet, the printer was indeed plugged in. Please note: As long as printer is operational, printing is fine. This is only an issue when telling PSU to power printer on after it's been off. (It goes off 10 min after print is done. Prior to this happening, I could slice an object in Cura and tell it to print with Octoprint, it would turn on printer and start the print.

4

I've not heard of that issue directly, but maybe it can happen.

When you turn the printer back on, SSH to the Pi and run lsusb. See what is reported there (paste it).

Next, unplug and re-plug the printer. Run dmesg | tail -n 20 to see if any errors were reported. You can also paste this here.

5

It's doing a 12 hr print now. Also, PSU and Access Anywhere updated again. Broke PSU, loaded the previous one by .zip file. It would turn printer on, but, I had a print end at 10pm last night and printer was still on this AM. The main reason I us Octoprint is to shut printer off when done. A good many of my prints end at night or when I'm away.

6

It will connect if I unplug and replug the usb on printer. lsusb same before and after.

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
Bus 001 Device 008: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
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:
[87002.503710] ch341 1-1.2:1.0: ch341-uart converter detected
[87002.509155] usb 1-1.2: ch341-uart converter now attached to ttyUSB0
[87029.963713] usb 1-1.2: USB disconnect, device number 6
[87029.964578] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0
[87029.964696] ch341 1-1.2:1.0: device disconnected
[87059.446275] usb 1-1.2: new full-speed USB device number 7 using xhci_hcd
[87059.582400] usb 1-1.2: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.64
[87059.582417] usb 1-1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[87059.582432] usb 1-1.2: Product: USB Serial
[87059.591265] ch341 1-1.2:1.0: ch341-uart converter detected
[87059.596759] usb 1-1.2: ch341-uart converter now attached to ttyUSB0
[87205.091922] usb 1-1.2: USB disconnect, device number 7
[87205.092800] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0
[87205.092922] ch341 1-1.2:1.0: device disconnected
[87213.068403] usb 1-1.2: new full-speed USB device number 8 using xhci_hcd
[87213.204581] usb 1-1.2: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.64
[87213.204601] usb 1-1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[87213.204618] usb 1-1.2: Product: USB Serial
[87213.214677] ch341 1-1.2:1.0: ch341-uart converter detected
[87213.219006] usb 1-1.2: ch341-uart converter now attached to ttyUSB0

Possible that Octoprint doesn't play well with the UPS? Was working fine till about a week ago.
I'm running apcupsd for the ups. Been running ok for more than a month.

7

Well, guess what? Disabled Access Anywhere (spaghetti detective) and if connects.??? With Jyers firmware, when connection failed printer says it received a M112, emergency stop. Disabled TSD and it now connects.

Edit: Spoke too soon. was able to connect several times, so did a print and tried to connect after PSU shut it down, and getting the same problem: "printer reports error serial status mismatch".

8

I'm guessing you are using PSUControl but that's only because we don't have any useful logs to work from. If that's the case then continue reading.

First of all make sure you are on the latest PSUCoontrol. See Releases · kantlivelong/OctoPrint-PSUControl · GitHub

Once you've done that follow Troubleshooting · kantlivelong/OctoPrint-PSUControl Wiki · GitHub and provide the logs. Serial logs could be useful here so turn that on as well.

Once there are some logs to work from we can go from there.

9

I'm still looking at this. The PSU problem is fixed. I'm using the older version I loaded from the zip file and it has been working. I'm not going after the PSU control until I have this problem fixed. I believe it has to do with port selection in the pi because I also have a usb UPS connection. Still looking for now.

Edit: so far, updated pi (sudo apt-get update; sudo apt-get upgrade) and reverted back to my earliest Marlin fimware. So far working ok---doing a 14 hr print now.

Edit2: Found if I load fw from early March (both Marlin and Jyers, the error goes away. Jyers fw v 1.2.2 has ' * Fixed Serial Connection Issue". If I load an earlier one, no error.

Edit3: Preliminary testing with the new PSU control along with PSU Control-RPI-GPIO seems to be working also.

Edit4: Since printer would connect using old fw, retried PSU Contol with the RPI-GPIO and it seems to
work.

10

Embarrassing, found the send m112 came back on in my Octoprint options. Don't know how or why it came back on. Turned it off and next reboot was back on? Turned it off again this time it seems like it stays off? Anyway i loaded Jyers 1.3.1 and using the updated PSU plugin and it seems to be running fine now. Connects every time now. Closing this.