Mcu 'rpi' unable to connect

General Discussion
1

Basic Information:

Printer Model:Neptune 4 Pro with OpenNeptune

klippy.log (1.2 MB)

MCU / Printerboard:
Host / SBC
klippy.log

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:

Hey guys.2 days ago i shutdown my printer properly and today when i turned it on it felt weird then the “mcu ‘rpi’: Unable to connect” error code popped up.Everything is up to date and i dont know what to do

…

2

This file

[mcu rpi]
serial = /tmp/klipper_host_mcu

is likely missing or corrupted. Details at the link below.

3

I didnt touch any mcu config yet.Its worked until 2 days ago.

My code looks like this:

[mcu rpi] 

serial: /tmp/klipper_host_mcu




[adxl345]

cs_pin: rpi:None

spi_bus: spidev0.2

I dont know what happened with it

4

On a RPi the first suspect is the SD card. They do wear out.

In anu case Klipper has to read that file to enable the [mcu rpi]. You could comment out the lines and all the accelerometer references. Klipper should be happy but obviously the accelerometer will no longer work.