Tearing my hair our trying to flash Klipper

[drpeej]

I have spent 2 days trying to get Klipper to work

I keep getting this



I have checked and double checked everything and done a clean installation twice

When I run ls /dev/serial/by-id I get this

pi@mainsailos:~ $ ls /dev/serial/by-id

usb-Klipper_stm32f446xx_1F000A000550314D35323820-if00

pi@mainsailos:~ $

The start of my printer.cfg file is like this

[include mainsail.cfg]

[mcu]
# run ls /dev/serial/by-id/ in ssh terminal to get the controller name
serial: /dev/serial/by-id/usb-Klipper_stm32f446xx_1F000A000550314D35323820-if00

I attach my moonraker log

I can't think of anything else to try

Can anyone advise please?

Peter

 

[Indeed]

The error message is about the [mcu rpi] section in printer.cfg, it's not about the main [mcu] section.

The [mcu rpi] section refers to using the Raspberry Pi as an extra mcu, and connect stuff like a vibration sensor and maybe other things as well.
The [mcu] section refers to the primary mcu, such an Octopus or similar.

Your printer.cfg has an [mcu rpi] section but klipper can't find the configured comm socket "/tmp/klipper_host_mcu".
It's probably because the "klipper linux mcu Service" is not running.

I don't know if you are going to use the Raspberry Pi as an extra mcu, or if that section was just included in printer.cfg by default when klipper was installed.
In any case, you can comment out a couple of lines in printer.cfg and with a little luck get things going again.

Then, if you need an [mcu rpi] section for use with an [adxl345] and an [input_shaper] section, you can troubleshoot the "klipper linux mcu Service" later.
Or just leave the lines commented out if you don't need them.

Comment out these lines in printer.cfg, make them look like this:

#[mcu rpi]
#serial = /tmp/klipper_host_mcu

#[adxl345]
#cs_pin = rpi:None

#[resonance_tester]
#accel_chip = adxl345
#probe_points =
#        175, 175, 20

For reference, this is from the attached klippy-6.log:

mcu 'rpi': Starting connect
mcu 'rpi': Unable to open port: [Errno 2] No such file or directory: '/tmp/klipper_host_mcu'

More about using Raspberry Pi as an extra mcu: https://www.klipper3d.org/RPi_microcontroller.html

 

[drpeej]

The error message is about the [mcu rpi] section in printer.cfg, it's not about the main [mcu] section.

The [mcu rpi] section refers to using the Raspberry Pi as an extra mcu, and connect stuff like a vibration sensor and maybe other things as well.
The [mcu] section refers to the primary mcu, such an Octopus or similar.

Your printer.cfg has an [mcu rpi] section but klipper can't find the configured comm socket "/tmp/klipper_host_mcu".
It's probably because the "klipper linux mcu Service" is not running.

I don't know if you are going to use the Raspberry Pi as an extra mcu, or if that section was just included in printer.cfg by default when klipper was installed.
In any case, you can comment out a couple of lines in printer.cfg and with a little luck get things going again.

Then, if you need an [mcu rpi] section for use with an [adxl345] and an [input_shaper] section, you can troubleshoot the "klipper linux mcu Service" later.
Or just leave the lines commented out if you don't need them.

Comment out these lines in printer.cfg, make them look like this:

#[mcu rpi]
#serial = /tmp/klipper_host_mcu

#[adxl345]
#cs_pin = rpi:None

#[resonance_tester]
#accel_chip = adxl345
#probe_points =
#        175, 175, 20

For reference, this is from the attached klippy-6.log:

mcu 'rpi': Starting connect
mcu 'rpi': Unable to open port: [Errno 2] No such file or directory: '/tmp/klipper_host_mcu'

More about using Raspberry Pi as an extra mcu: https://www.klipper3d.org/RPi_microcontroller.html

Thanks, thats really helpful. Its also similar to the advice I was given by the person I bought the kit from.

Unforunately I have had to retire to my bed feeling unwell so I cant check it out till tomorrow when I hope ill be feeling better

Peter

 

[MaxA]

Thanks - this worked for me - TLDR
I commented out the include pi.cfg in the Printer.cfg and commented out the lines for ADXL in pi.cfg. I'll circle back around later to troubleshoot the service. I imagine its a systemctl or KIAUH run through or shakedown as both the Picobilical and PI showed up using ls /dev/serial/by-id cmd. TBH I've never used the ADXL and I'm not too concerned with the pi temp in the pi.cfg file.
Was not having issues until after adding a DSI LCD Waveshare 4.3. Waveshare came on no problems there w/ the exception of the pi. Reflashed the SKR Pico and the PI - still no joy. But after commenting this out everything appears as normal on the Waveshare, with KlipperScreen. Meaning I'm not seeing the error reported on the Waveshare of MCU not available. Two nights into troubleshooting and was ready to move on to finishing the build so this saved me some time for sure.
Looking forward to sanitizing cabling as I had made significant changes adding a external PSU and moved all electronics to the bottom of the V0.

Hope this may save some other folks time / troubleshooting as not as much info on the Waveshare 4.3 and Klipper configs as one might expect.