No more candidates to test, and no working port/baudrate combination detected

Get Help
1

What is the problem?

After updating to 1.7 there is no way to connect.
"No more candidates to test, and no working port/baudrate combination detected."
No problems with previous Octoprint version (1.6)

What did you already try to solve it?

I tried several ports and cables with no luck.
I tried to revert to 1.6 using pip install https://github.com/OctoPrint/OctoPrint/archive/1.6.0.zip but after the installation Octoprint tells me 1.7 yet ...

Have you tried running in safe mode?

no

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-systeminfo-20211017080817.zip (34.6 KB)

WRITE HERE

Additional information about your setup

Geetech A10, firmware 2.0.8

2

There was a template that you should have used to describe your problem. You may consider this a waste of time to fill in that template, but actually we need the information provided in this template to be able to help you out. I suggest you open a new thread to copy the template and take the time needed to fill in the information.

Otherwise we won't be able to help you

1 Like
3

Why did you delete the template?

There is some stuff we need to know in order to help you.

At least upload the octoprint.log and tell us something about your system.

Bildschirmfoto vom 2021-10-16 17-34-51
Bildschirmfoto vom 2021-10-16 17-34-51578×566 37.9 KB

4

Sorry ...
done !

5

Looking at your logs, here are the attempts to connect to your printer:

2021-10-16 10:32:38,515 - octoprint.util.comm - INFO - Serial detection: Performing autodetection with 66 port/baudrate candidates: /dev/ttyUSB0@115200, /dev/ttyUSB0@250000, /dev/ttyS31@115200, /dev/ttyS31@250000, /dev/ttyS30@115200, /dev/ttyS30@250000, /dev/ttyS29@115200, /dev/ttyS29@250000, /dev/ttyS28@115200, /dev/ttyS28@250000, /dev/ttyS27@115200, /dev/ttyS27@250000, /dev/ttyS26@115200, /dev/ttyS26@250000, /dev/ttyS25@115200, /dev/ttyS25@250000, /dev/ttyS24@115200, /dev/ttyS24@250000, /dev/ttyS23@115200, /dev/ttyS23@250000, /dev/ttyS22@115200, /dev/ttyS22@250000, /dev/ttyS21@115200, /dev/ttyS21@250000, /dev/ttyS20@115200, /dev/ttyS20@250000, /dev/ttyS19@115200, /dev/ttyS19@250000, /dev/ttyS18@115200, /dev/ttyS18@250000, /dev/ttyS17@115200, /dev/ttyS17@250000, /dev/ttyS16@115200, /dev/ttyS16@250000, /dev/ttyS15@115200, /dev/ttyS15@250000, /dev/ttyS14@115200, /dev/ttyS14@250000, /dev/ttyS13@115200, /dev/ttyS13@250000, /dev/ttyS12@115200, /dev/ttyS12@250000, /dev/ttyS11@115200, /dev/ttyS11@250000, /dev/ttyS10@115200, /dev/ttyS10@250000, /dev/ttyS9@115200, /dev/ttyS9@250000, /dev/ttyS8@115200, /dev/ttyS8@250000, /dev/ttyS7@115200, /dev/ttyS7@250000, /dev/ttyS6@115200, /dev/ttyS6@250000, /dev/ttyS5@115200, /dev/ttyS5@250000, /dev/ttyS4@115200, /dev/ttyS4@250000, /dev/ttyS3@115200, /dev/ttyS3@250000, /dev/ttyS2@115200, /dev/ttyS2@250000, /dev/ttyS1@115200, /dev/ttyS1@250000, /dev/ttyS0@115200, /dev/ttyS0@250000
2021-10-16 10:32:38,516 - octoprint.util.comm - INFO - Serial detection: Trying port /dev/ttyUSB0, baudrate 115200
2021-10-16 10:32:38,518 - octoprint.util.comm - INFO - Connecting to port /dev/ttyUSB0, baudrate 115200
2021-10-16 10:32:38,553 - octoprint.util.comm - ERROR - Could not set low latency mode on serial port, continuing without
Traceback (most recent call last):
  File "/home/simone/OctoPrint/venv/lib/python3.6/site-packages/serial/serialposix.py", line 135, in set_low_latency_mode
    fcntl.ioctl(self.fd, termios.TIOCGSERIAL, buf)
OSError: [Errno 25] Inappropriate ioctl for device

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/simone/OctoPrint/venv/lib/python3.6/site-packages/octoprint/util/comm.py", line 3758, in default
    serial_obj.set_low_latency_mode(True)
  File "/home/simone/OctoPrint/venv/lib/python3.6/site-packages/serial/serialposix.py", line 146, in set_low_latency_mode
    raise ValueError('Failed to update ASYNC_LOW_LATENCY flag to {}: {}'.format(low_latency_settings, e))
ValueError: Failed to update ASYNC_LOW_LATENCY flag to True: [Errno 25] Inappropriate ioctl for device
2021-10-16 10:32:38,742 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #1 with timeout 2.0s
2021-10-16 10:32:38,764 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-10-16 10:32:39,109 - octoprint.plugins.shutdownprinter - ERROR - send status off 1
2021-10-16 10:32:39,171 - octoprint.plugins.shutdownprinter - INFO - eventView
2021-10-16 10:32:39,497 - octoprint.plugins.octovox - ERROR - Failed to update printer status: Failed to update one or more statuses. 
2021-10-16 10:32:40,775 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #2 with timeout 2.0s
2021-10-16 10:32:40,798 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-10-16 10:32:42,787 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #3 with timeout 2.0s
2021-10-16 10:32:42,814 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-10-16 10:32:43,239 - octoprint.plugins.pluginmanager - INFO - Loaded plugin repository data from https://plugins.octoprint.org/plugins.json
2021-10-16 10:32:44,804 - octoprint.util.comm - INFO - Serial detection: Trying port /dev/ttyUSB0, baudrate 250000
2021-10-16 10:32:44,815 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #1 with timeout 2.0s
2021-10-16 10:32:44,837 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-10-16 10:32:46,828 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #2 with timeout 2.0s
2021-10-16 10:32:46,863 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-10-16 10:32:48,849 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #3 with timeout 2.0s
2021-10-16 10:32:48,865 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0

According to your logs, your printer is connected to /dev/ttyUSB0 so you shouldn't bother trying with other serial ports (i.e. /dev/ttySnn, which are serial ports from your computer, and not connected to anything in particular).

It seems that OctoPrint is able to send the M110 N0 command, but your printer isn't responding in time. Could you try to enable serial logging (Settings, Serial, General, Serial logging at the bottom of the menu), try to reconnect to the printer and then upload the serial.log file.

Also it would help us if you could tell us more about the computer it's running from, since it doesn't seem to be running off a Pi and OctoPi.

6

Thanks ...
please find new bundle with serial.log
octoprint-systeminfo-20211017122123.zip (23.7 KB)

Octoprint is installed on Ubuntu 18.04.5 lts
CPU Atom N270

7

You've selected the wrong port:

2021-10-17 12:20:43,073 - Performing autodetection with 7 port/baudrate candidates: /dev/ttyS0@115200, /dev/ttyS0@250000, /dev/ttyS0@230400, /dev/ttyS0@57600, /dev/ttyS0@38400, /dev/ttyS0@19200, /dev/ttyS0@9600
2021-10-17 12:20:43,074 - Trying port /dev/ttyS0, baudrate 115200
2021-10-17 12:20:43,110 - Connecting to port /dev/ttyS0, baudrate 115200
2021-10-17 12:20:43,142 - Unexpected error while connecting to serial port /dev/ttyS0, baudrate 115200 from hook default: SerialException: 'Could not configure port: (5, 'Input/output error')' @ comm.py:_open_serial:3779
2021-10-17 12:20:43,325 - Could not open port /dev/ttyS0, baudrate 115200, skipping
2021-10-17 12:20:43,326 - Trying port /dev/ttyS0, baudrate 250000
2021-10-17 12:20:43,333 - Connecting to port /dev/ttyS0, baudrate 250000
2021-10-17 12:20:43,340 - Unexpected error while connecting to serial port /dev/ttyS0, baudrate 250000 from hook default: SerialException: 'Could not configure port: (5, 'Input/output error')' @ comm.py:_open_serial:3779
2021-10-17 12:20:43,565 - Could not open port /dev/ttyS0, baudrate 250000, skipping

It should have been /dev/ttyUSB0 and not /dev/ttyS0...

Which user is OctoPrint running as ?

8

sorry ... here it is ..octoprint-systeminfo-20211017134319.zip (26.1 KB)

default user is simone ... it this the answer you expected ?

9

@simonegiusti :
Do you have another program running that accesses the printer?

And as @SwHawk said: Try another USB port : /dev/ttyUSB0

10

Not expecting any kind of answer in particular, but this info tells us which kind of user runs the processes and if we should look for permission issues. I assume not, as you said the printer worked fine with OctoPrint 1.6.0, and I assume the same user ran the OctoPrint instance then.

11

no other device but the printer

12

@SwHawk yes ... working perfectly before upgrading to 1.7 ...
Any info from serial.log ??

13

Only that the printer doesn't answer in the 2s after the M110 N0 command is sent by OctoPrint, which OctoPrints assumes as a timeout... You could try to increase the timeout windows to see if something changes. These settings are located in Settings, Serial, Intervals and Timeouts, and then Timeouts.

Also, in order to restore functionality, I'd suggest you try to install OctoPrint 1.6.0 inside another Python virtual environment. Something along the lines of:

mkdir ~/OctoPrint1.6
cd ~/OctoPrint1.6
python3 -m venv .
bin/pip --no-cache-dir install --upgrade pip
bin/pip --no-cache-dir install https://github.com/OctoPrint/OctoPrint/archive/1.6.0.zip

And then change your system setting to start that instance rather than the 1.7 one located in the other Python virtual environment.

If you're able to connect to the printer with 1.6, then activate serial logging as well and upload the serial.log file, so that we can compare and see what seems to be the problem...

14

Sorry, I did not mean device, I meant program/application that may access the printer.

15

@SwHawk I installed 1.6 and it works !

image
image1920×1528 122 KB

LOG: octoprint-systeminfo-20211017181806.zip (35.2 KB)

16

OK that's definitely strange, but according to the serial.log file you provided and the screenshot you took, the serial port should be /dev/ttyUSB0 and the Baudrate should be 2500000. Could you try specifying those settings to the 1.7.0 instance ? You would perhaps need several attempts before it works. Though anything beyond 20 attempts is certainly pointless. You should wait a few seconds between each attempts, just to be sure. Before doing so, you would have to deactivate the 1.6.0 instance obviously...

EDIT: looking at your 1.6.0 systeminfo bundle, for this instance, you're using Python 2.7 and no virtual environment, how did you install it ? Because we're looking at two things that behave differently with different underlying software, so there's too much variables to take into account for what could go wrong. Besides, Python 2.7 is deprecated since 2020, so you shouldn't really use it anymore, but that's a totally different debate...

17

Thanks ..
I'm really a dummy .. I installed 1.6 simply following copying your code ...

18

Not saying that at all, just trying to figure out what's happening. That's very strange, because in the code I provided, I specifically asked for the Python 3 binary by providing the python3 command...

19

Anyway now 1.7 works again !
All settings seems to be correct but no plugin is active because it's booting in SAFE mode (how to remove Safe??) ...octoprint-systeminfo-20211017191127.zip (37.8 KB)

OctoPrint 1.7.0 Python 3.6.9

20

Glad it works, even though we couldn't determine what was wrong in the first place...

According to the logs:

2021-10-17 19:07:42,413 - octoprint.startup - INFO - ******************************************************************************
2021-10-17 19:07:42,417 - octoprint.startup - INFO - Starting OctoPrint 1.7.0
2021-10-17 19:07:42,507 - octoprint.startup - INFO - Starting in SAFE MODE. Third party plugins will be disabled!
2021-10-17 19:07:42,507 - octoprint.startup - INFO - Reason for safe mode: setting in config.yaml
2021-10-17 19:07:42,508 - octoprint.startup - INFO - ******************************************************************************

it's because there's a setting in the config.yaml file that tells it to. Those settings are one time settings, since the instance started, the next start should be in regular mode, with plugins activated. So all you need to do is restart octoprint.

Although bear in mind that any of the plugins could be causing the issue. If so, I suggest you disable them all, then reactivate them one at a time to see if the plugin causes the connection issue.