Moonraker not connected to klipper

General Discussion
6

from line 312

Good luck, hcet14

7

Thank you. Found it. I looked multiple time

8

Added the line to [mcu rpi] and it hasn’t made any difference

9

klippy.log (566.7 KB)

new klippy.log after adding that line

10

Have you done the things mentioned here?

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

As far as you need them…

11

Why don’t you start over by answering my stupid questions :wink:

What do you want to do?
Please describe your HW setup.

Just running Klipper on your Ender?

Do you have an ADXL345 hooked up?

Moonraker is connected see line 15508.

webhooks client 1965300248: Client info {'program': 'Moonraker', 'version': 'v0.8.0-41-g348b7f5'}

Do you really need the RPi as a secondary MCU?

12

At the moment I have a ender 3 v2 with 4.2.7 board, sprite pro extruder, cr touch. No adxl345

That now has klipper firmware on it.

Rpi is attached to ender via usb. Rpi has mainsailos installed. I connect to the rpi via ssh and the ip address on my Windows tablet.

13

As indicated by @EddyMI3D, follow the instructions in the link he provided. The error messages in your log are not related to Moonraker.

14

Understood. One question, your cr touch is connected to your 4.2.7 board?

If yes, you don’t need the RPi as a secondary MCU.

My advise would be, start over. Follow the excellent Klipper documentation. Don’t copy stuff from somewhere in the www (particularly macros). If your Ender is pretty original (not regarding the extender), start with klipper/config/printer-creality-ender3-v2-2020.cfg at master · Klipper3d/klipper · GitHub. Just use stuff you understand. Do you know GitHub - th33xitus/kiauh: Klipper Installation And Update Helper? Have a look here About the Knowledge Base category / Table of Contents. If you have problems come back here and use the “search” button first. Almost everything was asked before :wink: I guess you come from Marlin, if yes you have to read a lot. If you don’t find the answer, ask here. People here are friendly and helpful.

15

Followed the instructions in the link and still the same

16

Please provide a new log.

17

I don’t have a spare laptop to put linux on so that is why i have the rpi running klipper.

18

klippy (2).log (143.9 KB)

19

Does it work with

[mcu host]
serial: /tmp/klipper_host_mcu

instead of

[mcu rpi]
serial: /home/pi/printer_data/comms/klippy.serial

?

1 Like
20

Follow @EddyMI3D advice and in addition it looks like the “host mcu” process is not correctly started.

  1. Make sure to have followed the above link to the letter. In doubt, repeat it. Especially important

    cd ~/klipper/
sudo cp ./scripts/klipper-mcu.service /etc/systemd/system/
sudo systemctl enable klipper-mcu.service

  2. Issue the commands (or reboot)

    • sudo service klipper-mcu restart
    • sudo service klipper restart

  3. Show the output of ls -al /home/pi/printer_data/comms/klippy.serial

21

Changing to mcu host gives a new error.

unknown pin chip name ‘rpi’

22

That is not as fatal as the previous errors.

Just swap rpi with host

[adxl345]
cs_pin = rpi:None

to

[adxl345]
cs_pin = host:None
23

output of ls -al /home/pi/printer_data/comms/klippy.serial is /dev/pts/2

24

From your config:

[mcu rpi]
serial = /home/pi/printer_data/comms/klippy.serial

[adxl345]
cs_pin = rpi:None

this seems correct and in-line with your startup arguments:

Args: ['/home/pi/klipper/klippy/klippy.py', '/home/pi/printer_data/config/printer.cfg', '-l', '/home/pi/printer_data/logs/klippy.log', '-I', '/home/pi/printer_data/comms/klippy.serial', '-a', '/home/pi/printer_data/comms/klippy.sock']

The error:

mcu 'rpi': Wait for identify_response
...
serialhdl.error: mcu 'rpi': Serial connection closed

Looks like something went wrong during RPi microcontroller - Klipper documentation

25

Just restarted everything an I now have a connection to the printer.

Thank you everyone

1 Like