Octopi won't connect with new Klipper install

General Discussion
1

Basic Information:

Printer Model: Creality Ender-5 S1
MCU / Printerboard: STM32F401
Host / SBC :Raspberry Pi 4B 8GB 64bit Raspbian Bullseye
klippy.log: klippy.log (15.0 KB)

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

I have been using Octopi for months connected to my Ender-5 S1 and decided I would install Klipper. I am following the instructions at OctoPrint for Klipper - Klipper documentation. I had issues with using “~/printer_data/comms/klippy.sock” (The new “Printer” would not appear in the drop down menu to select) but fixed those by using “/home/pi/printer_data/comms/klippy.sock” and then modifying the permissions of the directories (ie. 777).

Now I have the “Serial port” showing up in the Connection dropdown menu (And selected) in the top left section of the Octopi interface. The instructions say to “click Connect” but when I do thgat I get the following log from OctoPi:

Changing monitoring state from "Offline" to "Detecting serial connection"
Performing autodetection with 7 port/baudrate candidates: /home/pi/printer_data/comms/klippy.sock@115200, /home/pi/printer_data/comms/klippy.sock@250000, /home/pi/printer_data/comms/klippy.sock@230400, /home/pi/printer_data/comms/klippy.sock@57600, /home/pi/printer_data/comms/klippy.sock@38400, /home/pi/printer_data/comms/klippy.sock@19200, /home/pi/printer_data/comms/klippy.sock@9600
Trying port /home/pi/printer_data/comms/klippy.sock, baudrate 115200
Connecting to port /home/pi/printer_data/comms/klippy.sock, baudrate 115200
Could not open port /home/pi/printer_data/comms/klippy.sock, baudrate 115200, skipping
Trying port /home/pi/printer_data/comms/klippy.sock, baudrate 250000
Connecting to port /home/pi/printer_data/comms/klippy.sock, baudrate 250000
Could not open port /home/pi/printer_data/comms/klippy.sock, baudrate 250000, skipping
Trying port /home/pi/printer_data/comms/klippy.sock, baudrate 230400
Connecting to port /home/pi/printer_data/comms/klippy.sock, baudrate 230400
Could not open port /home/pi/printer_data/comms/klippy.sock, baudrate 230400, skipping
Trying port /home/pi/printer_data/comms/klippy.sock, baudrate 57600
Connecting to port /home/pi/printer_data/comms/klippy.sock, baudrate 57600
Could not open port /home/pi/printer_data/comms/klippy.sock, baudrate 57600, skipping
Trying port /home/pi/printer_data/comms/klippy.sock, baudrate 38400
Connecting to port /home/pi/printer_data/comms/klippy.sock, baudrate 38400
Could not open port /home/pi/printer_data/comms/klippy.sock, baudrate 38400, skipping
Trying port /home/pi/printer_data/comms/klippy.sock, baudrate 19200
Connecting to port /home/pi/printer_data/comms/klippy.sock, baudrate 19200
Could not open port /home/pi/printer_data/comms/klippy.sock, baudrate 19200, skipping
Trying port /home/pi/printer_data/comms/klippy.sock, baudrate 9600
Connecting to port /home/pi/printer_data/comms/klippy.sock, baudrate 9600
Could not open port /home/pi/printer_data/comms/klippy.sock, baudrate 9600, skipping
Changing monitoring state from "Detecting serial connection" to "Error"
Changing monitoring state from "Error" to "Offline after error"

This is the permissions of the files:

pi@octopi:~/printer_data/comms $ ls -al
total 8
drwxrwxrwx  2 pi pi 4096 Oct 12 17:25 .
drwxrwxrwx 10 pi pi 4096 Sep 29 08:44 ..
lrwxrwxrwx  1 pi pi   10 Oct 12 17:25 klippy.serial -> /dev/pts/1
srwxrwxrwx  1 pi pi    0 Oct 12 17:25 klippy.sock

Here is the OS info:

pi@octopi:~/printer_data/comms $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

I haven’t even got to the point of flashing the printer.

Any help most appreciated.

2

Hello @Valdhor !

Try one of these:

/home/pi/printer_data/comms/klippy.serial
/tmp/printer
3

Can you explain why?

From what I can ascertain /tmp/printer was the old way of doing it.

Klippy.sock is the socket connection whilst klippy.serial is the virtual serial port.

4

Have you Moonraker installed? Its only then.

to connect to OctoPrint

Have you even tried to do ?

5

I don’t have anything other than Octoprint installed.

With the issues I had getting the port “/home/pi/printer_data/comms/klippy.sock” to even show up in the menu’s I was loath to modify it.

I added port “/home/pi/printer_data/comms/klippy.serial” and it connected OK.

Thank you.

Now onto flashing the printer.