RPi as a secondary MCU with multiple Klipper instances

General Discussion
1

Hi, I have RPi with installer two Klipper instances for my two printers.
Also I install klipper_mcu as described in manual (RPi microcontroller - Klipper documentation).
In printer.cfg of first printer I write:

[mcu host]
serial: /tmp/klipper_host_mcu

All works fine.
Then I write in second printer printer.cfg:

[mcu host]
serial: /tmp/klipper_host_mcu

And I got error in one of the printers:

Timeout with MCU ‘host’ (eventtime=25.172420)
Transition to shutdown state: Lost communication with MCU ‘host’

the other printer continues to function normally.

Please help me, how can I set up a connection to klipper_host_mcu for multiple printers?

2
3

I think that’s just for running a second front-end instance. I’m guessing he wants to run the pi as a secondary MCU for two printers so that he can make use of the GPIO inputs on the Pi itself on two machines at once.

@kain_pl If the above is true, I’m not quite sure it’s possible. You’re better off finding a different secondary MCU for the second printer if you’re just trying to control separate devices.

4

Yes it is true, thanks.
Through several experiments and various configuration options, I finally realized that what I want - I can not achieve. Sad but true, so I will look for other options.

5

I wrote a server on a node.js that manages raspberry pins and forked the Mainsail - I added the necessary buttons there. Enough for me for now :slight_smile:

6

If you’re just turning things on and off again, mainsail is the “Wrong” layer to be editing. Looks like Moonraker (the API layer that Mainsail and Fluidd talk to) also has the ability to tweak power supplies and other devices remotely. This is useful for Home Assistant or Homeseer integrations especially.

https://moonraker.readthedocs.io/en/latest/configuration/#options-common-to-all-power-devices