MCU Unable to connect to Rpi4

Basic Information:

Printer Model:Ender5+
MCU / Printerboard:Creality v2.2
Host / SBC RPI4
klippy.log

Klippylog162491.crdownload.zip (89.8 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:

Mainsailos micro SD card went bad, so I made a new one. I can ssh so that’s good, and I used Kiuah for installing Klipper, i flashed the control board through the USB cable it looked good on the computer screen. But the two units aren’t communicating. ‘MCU” : Unable to connect.

Have you installed the Klipper mcu part on the Raspberry Pi as described here: RPi microcontroller - Klipper documentation ?

Thanks for your time. I have not done that. Please tell me which section I should use to install the Klipper MCU part.

Thanks again

You need:

  • Install the rc script
  • Building the micro-controller code

Thanks, I’m going to do that right away. Thanks

I followed the script and rebooted the mainsail; I am still receiving the same error.

Here’s what I see on the terminal screen:

Installing micro-controller code to /usr/local/bin/

Attempting host MCU restart…

pi@BigBrother:~/klipper $ sudo service klipper start

pi@BigBrother:~/klipper $

Most Creality boards MUST be flashed via SD card. But if Klipper could connect before your Pi crashed the MCU had klipper firmware on it. It is possible you corrupted it with the USB flash attempt. Try flashing from a SD card.

Thanks for your time, so my board is a Creality V2.2, it has that 8 Bit thing on it, all info points toward a flash with a USB cable. I hope that I’m wrong. Please advise.

my klipper screen says moonraker connected but klipper is disconnected.

Thanks

I also ran: dmesg to see if the board registers in the operating system, it does yeah so thats good.

Moonraker connects klippy to the web interface.

Klippy connects to a MCU running klipper firmware.

What do you get if you use KIAUH to “find mcu” (advanced options)?

in Kiauh dir. It said no such file or dir.

Well out of no where I turned to look at klipper screen to turn it off, I what I saw was a operating klipper sceen, wow, the interface on the computer also is fuctional. I’m very happy at this monment I read that the 8 Bit board was slow at rebooting, but darn. Thank you to everyone here today to help me. I can’t help to believe it was one of those items suggested that made it all come together.

Well it stop working again, I tried to reopen and klipper is reporting STARTUP/ don’t know what thats all about.

So I now know that thesettings in some regards in correct that was working I have the bed/extruder hot it moved and homed good. That said I’m looking for some more thoughts why the coms were broken. Thanks for your thoughts.

Klippy Log,

klippy(3).log.zip (306.4 KB)

klippy(3).log.zip (306.4 KB)

So after powering down and restarting, it shows up again, weird, right?

Could be the for most of the log the problem was

Loaded MCU 'mcu' 134 commands (v0.13.0-540-g57c2e0c96 / gcc: (GCC) 5.4.0 binutils: (GNU Binutils) 2.26.20160125)
MCU 'mcu' config: ADC_MAX=1023 BUS_PINS_spi=PB3,PB2,PB1 BUS_PINS_twi=PD0,PD1 CLOCK_FREQ=16000000 MCU=atmega2560 PWM_MAX=255 RECEIVE_WINDOW=192 RESERVE_PINS_serial=PE0,PE1 SERIAL_BAUD=250000 STATS_SUMSQ_BASE=256 STEPPER_OPTIMIZED_UNSTEP=40 STEPPER_STEP_BOTH_EDGE=1
mcu 'rpi': Starting connect
mcu 'rpi': Unable to open port: [Errno 2] No such file or directory: '/tmp/klipper_host_mcu'
mcu 'rpi': Unable to open port: [Errno 2] No such file or directory: '/tmp/klipper_host_mcu'
mcu 'rpi': Unable to open port: [Errno 2] No such file or directory: '/tmp/klipper_host_mcu'
mcu 'rpi': Unable to open port: [Errno 2] No such file or directory: '/tmp/klipper_host_mcu'

@EddyMI3D Caught that it was the [mcu_rpi] not the main MCU. I missed it and led you down the wrong path.