Printer wont connect - No more candidates to test, and no working port/baudrate combination detected

[Webof]

I am really new to all this and really struggling to make this work. Any help greatly appriciated

What is the problem?

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

What did you already try to solve it?

tried 3 different cables in different ports

Have you tried running in safe mode?

No

Did running in safe mode solve the problem?

WRITE HERE

Systeminfo Bundle

Changing monitoring state from "Offline" to "Detecting serial connection"
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
Trying port /dev/ttyS0, baudrate 115200
Connecting to port /dev/ttyS0, baudrate 115200
Unexpected error while connecting to serial port /dev/ttyS0, baudrate 115200 from hook default: SerialException: '[Errno 13] could not open port /dev/ttyS0: [Errno 13] Permission denied: '/dev/ttyS0'' @ comm.py:_open_serial:3775
Could not open port /dev/ttyS0, baudrate 115200, skipping
Trying port /dev/ttyS0, baudrate 250000
Connecting to port /dev/ttyS0, baudrate 250000
Unexpected error while connecting to serial port /dev/ttyS0, baudrate 250000 from hook default: SerialException: '[Errno 13] could not open port /dev/ttyS0: [Errno 13] Permission denied: '/dev/ttyS0'' @ comm.py:_open_serial:3775
Could not open port /dev/ttyS0, baudrate 250000, skipping
Trying port /dev/ttyS0, baudrate 230400
Connecting to port /dev/ttyS0, baudrate 230400
Unexpected error while connecting to serial port /dev/ttyS0, baudrate 230400 from hook default: SerialException: '[Errno 13] could not open port /dev/ttyS0: [Errno 13] Permission denied: '/dev/ttyS0'' @ comm.py:_open_serial:3775
Could not open port /dev/ttyS0, baudrate 230400, skipping
Trying port /dev/ttyS0, baudrate 57600
Connecting to port /dev/ttyS0, baudrate 57600
Unexpected error while connecting to serial port /dev/ttyS0, baudrate 57600 from hook default: SerialException: '[Errno 13] could not open port /dev/ttyS0: [Errno 13] Permission denied: '/dev/ttyS0'' @ comm.py:_open_serial:3775
Could not open port /dev/ttyS0, baudrate 57600, skipping
Trying port /dev/ttyS0, baudrate 38400
Connecting to port /dev/ttyS0, baudrate 38400
Unexpected error while connecting to serial port /dev/ttyS0, baudrate 38400 from hook default: SerialException: '[Errno 13] could not open port /dev/ttyS0: [Errno 13] Permission denied: '/dev/ttyS0'' @ comm.py:_open_serial:3775
Could not open port /dev/ttyS0, baudrate 38400, skipping
Trying port /dev/ttyS0, baudrate 19200
Connecting to port /dev/ttyS0, baudrate 19200
Unexpected error while connecting to serial port /dev/ttyS0, baudrate 19200 from hook default: SerialException: '[Errno 13] could not open port /dev/ttyS0: [Errno 13] Permission denied: '/dev/ttyS0'' @ comm.py:_open_serial:3775
Could not open port /dev/ttyS0, baudrate 19200, skipping
Trying port /dev/ttyS0, baudrate 9600
Connecting to port /dev/ttyS0, baudrate 9600
Unexpected error while connecting to serial port /dev/ttyS0, baudrate 9600 from hook default: SerialException: '[Errno 13] could not open port /dev/ttyS0: [Errno 13] Permission denied: '/dev/ttyS0'' @ comm.py:_open_serial:3775
Could not open port /dev/ttyS0, baudrate 9600, skipping
Changing monitoring state from "Detecting serial connection" to "Error"
Changing monitoring state from "Error" to "Offline after error"

WRITE HERE

Additional information about your setup

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

WRITE HERE

[b-morgan]

You have provided almost no information about your system. We are not omnipotent, without the information asked for in the template, all we can do is sympathize.

There is no such thing as too much detail. Start with what system are you running OctoPrint on and what printer (make and model) are you connecting to. Follow that up with clicking on all the blue text which are links to additional instructions on how to provide the information we need to help you.

[Webof]

Sorry very new to all this

So I am using a Pi 4b 2 gb

trying to connect an Ender 3 V2

I tried flashing the latest stable image onto the PI but it wouldnt run stating that it needed more recent version.

I then loaded the most up to date version 64 nightly and that connects, via the internet allowing me to see the PI but can not connect to the printer as per the error message included.

Thank you for the response happy to add more detail if anyone knows what else might be needed?

David

[Webof]

I am trying to work through anything i can find on here, have now tried blocking off the power pin on the USB cable to see if its a backpowering issue which did not help.

[b-morgan]

Creality printers are notoriously finicky about the quality of the USB cable. This is mostly caused by EMI which the printer is sensitive to and a generator of (an often deadly combination). First you need a high quality, shielded, short USB data cable with ferite cores on both ends. I think one like this is what you need.

Also verify that your USB cable is actually a data cable and not a power-only cable. If you have a cell phone with the same connector, use each cable with the cell phone attached and verify that you can see the it. If it doesn't show up, then that cable is most likely a power only cable.

[Webof]

Thank you, will give that a try, is it a problem that would show up on the Pi specifically? the Cable that came with the printer connected fine when I ran the printer direcrtly from a PC octoprint instance.

So confusing! thank you for the swift reply really appricated !

[b-morgan]

If the cable worked with the printer when connected to another system. Then it is a data cable and we have eliminated that possibility. Try routing the cable differently, i.e. move the RPi to the other side of the printer and see if that changes the symptoms.

I believe that in the end, you will need to tape over the 5v pin to resolve the other issue that Creality printers have, drawing power from USB instead of the printer's power supply to run the electronics. This is most often seen when the display on the printer remains lit when the printer is turned off.

[Webof]

Ok, I have tried multipule angles of routing and tried each of the sockets on the PI, I will do this again with the blocked off 5 v supply and see if that changes anything!

[Webof]

Ok so I checkeed that the 5v supply on the power cable isn't active by turning the printer off at the switch and then seeing if the electronics turn on when attached to the Pi, they did not.I took the tape back off the Pin and tried again and this time it did.

While the printer was not being back powered I still could not get a response from trying to connect on the Pi tab on the PC, the log says the same.

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

I will try another cable and see if it makes any difference.

[Webof]

Tried a few different cables and angles all with the 5 v supply blocked off no luck continues to have the same error.

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

[Charlie_Powell]

If you can get SSH access setup, you can do some debugging from there.

If you plug the printer in, run lsusb and see if there is anything that looks like a printer shows up. If there is nothing, try plugging in a USB drive or something, run lsusb again and see if it detects other devices.

Next to try can be running dmesg -w, then plugging in USB devices. You should see some activity on the console relating to the new USB devices.

You can also plug the printer in to a PC or something to test it is recognised as a device. It's all about testing as many things to rule out stuff and find the problem.

[tyeth]

Octoprint incorrectly assumes the default linux port of /dev/ttyS0 (serial interface 0) rather than the first USB device (/dev/ttyUSB) which is more commonly required by users. It does this because printers are communicated with over Serial connections, and the usb printer device shows up as a USB serial connection.
Try manually setting the options in the Connection control panel, set the port to the one including USB in the name and you can leave the baud rate on auto or try setting it to 115200 (default for my printer brand and a lot I've encountered) or 57600 (older devices)

[Webof]

@Charlie_Powell

lsusb

Just trying this now, thank you or your reply, been a busy work week will see what I can do, are these commands just added in the termial tab? sorry -very- new to this.

[Webof]

@tyeth

/dev/ttyUSB

Hi I tried the abopve ut doesnt seem to e letting me to try and connect via the USB

[tyeth]

The port definitely appears in the dropdown menu that says serial port and is currently /dev/ttyS0

If there isn't another port in that list you want to replug the cable or try another. Also worth rebooting sometimes.

When my Snapmaker Original is disconnected (powered off at the controller) it isn't in the list even though the usb cable is connected:

Whereas my snapmaker 2 A350 is currently connected:

I used to leave them both with Serial Port set to Auto and auto-reconnect enabled, but occasionally didn't reconnect due to timeouts when using the touchscreen to jog/change filament so I went and manually specified in the Octoprint settings for one of them.