In this ecosystem you have different players:
-
Klipper Host software running on your RPi
- Processes your config
- Does all the management
- Reads and processes your gcode to be printed
- etc
-
Klipper Firmware on your printer, aka
[mcu]
- Typically connects to the Klipper Host via the serial paths in your
printer.cfg
- Receives the command from Klipper Host
- Manages your printer’s hardware
- Typically connects to the Klipper Host via the serial paths in your
-
Klipper Host MCU, aka
[mcu rpi]
- Typically connects to the Klipper Host via
/tmp/klipper_host_mcu
- Allows to use the RPi as kind of MCU to manage hardware, e.g. for ADXL IMUs etc
- Typically connects to the Klipper Host via
-
Moonraker
- Typically connects to Klipper Host via
/tmp/klippy_uds
or~/<datapath>/comms/moonraker.sock
or the-a
argument in the env - Other connection paths can be specified in the
moonraker.cfg
- Serves as an interface process to direct information and commands between, e.g. a webinterface (fluidd, mainsail etc) and the Klipper Host
- Typically connects to Klipper Host via
-
Webinterfaces, e.g. fluidd, mainsail, klipper-screen etc
- Connect to Moonraker via a http port
- Allows the user to monitor and command the printing process
In your case the connection between Klipper Host and Moonraker was not working due to a mismatch in the connection paths.