Klipper Broken Again?

General Discussion
1

Basic Information:

Printer Model: Anycubic Predator
MCU / Printerboard: SKR 1.4 Turbo
klippy.log
klippy.log (325.7 KB)

Describe your issue:

“MCU ‘rpi’: Unable to connect.
Once the underlying issue is corrected, use the ‘FIRMWARE_RESTART’ command to reset the firmware, reload the configuration, and restart the host software.
Error configuring printer.”

After updating Klipper and Mainsail, etc., via the update manager inside the Mainsail web interface, Klipper stopped connecting to the MCU. I then SSH’d into the printer, did some basic ‘apt-get update’ and ‘apt-get upgrade,’ but after that, nothing worked. On my screen, I could see the Raspberry Pi booting up, but I could not connect anymore. No WLAN, no LAN, therefore no SSH.

I had no choice but to reflash the Raspberry Pi, reinstall Klipper, and everything else. The first “new to me” thing was that I was unable to flash Klipper to the MCU. Suddenly, I had to specify a FLASH_DEVICE, so I did, but I still got the same Flash Error. I was told to put the SKR board in bootloader mode or manually put the klipper.bin onto the SD card if flashing was not working, so I did that. I renamed it to firmware.bin as described and checked if it was flashed to the MCU and renamed to firmware.cur. It’s weird; I never had to do that before. Usually, it just worked.

In the printer.cfg, I put the MCU serial I got from the ‘ls /dev/serial/by-id/*’ command, as usual, and it doesn’t work anymore. Since then, I have been unable to connect to the MCU. Is there anything new that I don’t know yet? Is there a new update from RaspiOS, Klipper, or something else that is broken again? I appreciate any help.

TLDR:
After updating via the Mainsail Update Manager, RPi is not connecting to MCU.
After updating Raspbian too, everything broke, so I reinstalled everything from scratch.
Everything works except I’m still unable to connect to the MCU. [MCU] serial is correct using ‘ls /dev/serial/by-id/*.’
Help?! :sob:

2

Check if Debian 11 (Bullseye) udev bug - No board or serial found is applicable

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

You have the Pi set up as a secondary MCU for your adxl. When you reinstalled the OS you deleted all of files that make that work. You need to reinstall that.

https://www.klipper3d.org/RPi_microcontroller.html

4

Thank you, I checked and I am on “deb11u4”, i asume, if i understood it correctly, that the OS is not at fault.

5

I took your advice and simply commented out the lines for the ADXL, and boom, it indeed worked. I now installed the ADXL following the guides provided by klipper3d.org, but sadly, I’m unable to get the ADXL working again.

I wired everything up, installed the dependencies, enabled SPI, and added those lines in printer.cfg. But as soon as the ADXL is commented in, the MCU is not connecting. Any idea what I’m missing?
klippy(1).log (417.6 KB)

6

See @jakep_82 answer. You need to setup the RPi MCU again as per above linked documentation.

7

I did that, same result :frowning:

8

Please reboot your Pi, then make sure that the Klipper MCU service is actually running. You can do this with the command

systemctl status klipper-mcu.service

and the output should look like:

 klipper-mcu.service - Starts the MCU Linux firmware for klipper on startup
     Loaded: loaded (/etc/systemd/system/klipper-mcu.service; enabled; preset: enabled)
     Active: active (running) since Sun 2023-10-08 15:13:50 UTC; 2 days ago
       Docs: https://www.klipper3d.org/RPi_microcontroller.html
   Main PID: 4392 (klipper_mcu)
      Tasks: 1 (limit: 1003)
     Memory: 504.0K
        CPU: 2min 30.397s
     CGroup: /system.slice/klipper-mcu.service
             └─4392 /usr/local/bin/klipper_mcu -r -I /tmp/klipper_host_mcu

When up and running, then provide a fresh klippy.log.

9

I checked, and the service was not running. I did set up the rpi mcu again, and now it works, dont know why it weren’t working before, third times the charm I guess :slight_smile:

Everything is up and running again, thank you very much :heart_eyes:

10

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.