Resolved KIAUH Klipper Install Issue on Octopi 1.1.0

General Discussion
1

Basic Information:

Printer Model: Creality Ender 3, heavily modified
MCU / Printerboard: BTT SKR Mini E3 V3
Host / SBC: Raspberry Pi 4B with 4 GB memory
klippy.log: not needed for this discussion

Describe your issue:

I had problems with using KIAUH to install Klipper on an Octopi 1.1.0 image. The problem turned out to be cockpit error.

A lot has changed since I first used KIAUH. At that time there was an option to use a separate directory, ~/klipper_config, for the printer.cfg file. That option was deleted, but I did not understand why. Changes in Klipper caused me to believe that the Klipper installation by KIAUH was either incomplete or did not work.

  1. I had thought that the default location for the Klipper printer.cfg file was in the home directory, and I liked the idea of the dedicated klipper_config directory. I found a post on the Internet that told how to modify the ~/klipper/scripts/install-octopi.sh file to specify the path to the configuration file by modifying the Klippy argument . As most of you probably know, the current default location for the configuration file is ~/printer_data/config. KIAUH installs a sample file there, but it won’t run a printer.
  2. When I first installed Klipper, the serial port for the printer in OctoPrint was /tmp/printer. This no longer works. The correct printer port is ~/printer_data/comms/klippy.serial. When I tried using this in OctoPrint, it did not work, but /home/pi/printer_data/comms/klippy.serial does work.
  3. Likewise, the change in location of the klippy.log file from /tmp to ~/printer_data/logs caused me to believe that Klipper was not running since I could not see a log file.
  4. My initial installation of Klipper used the /etc/init.d directory for the Klipper system service definition, and this is where the ~/klipper/scripts/install-octopi.sh command file places the file. When I did not see a klipper file there I thought that the KIAUH installation did not work. Now I see that it did not work as I had expected it to, but worked as intended.

I would like to thank Sineos for helping me understand my failings. KIAUH works just fine on OctoPrint, at least if the user knows what they are doing. Now, if I could just get my touchscreen display to work again…

2 Likes
2

Thanks for sharing this. :+1:

Regarding the display, it might be best to open a new thread and provide all necessary information:

  • Exact type of the display
  • klippy.log
  • Old configuration / How did you work with it before? / Special OctoPrint plugin / KlipperScreen, etc.