Problem with simultaneous connection of two printers

General Discussion
1

Basic Information:

Printer Model: Made by me
MCU / Printerboard: Mks Robin Nano and BTT SKR 1.4 TURBO
klippy.log (1.2 MB)
klippy.log

Hello, my name is Alfredo Collie and I am from Venezuela, I hope you are doing very well, I installed Klipper on 2 machines on a MKS Pi v1.1, both print perfectly, the problem I have is when I want to print simultaneously on both printers, When I open Fluidd I connect one perfectly, I go to the other and it tells me to restart the firmware. When I do so, the one that was already connected is disconnected and so on, it is impossible to connect with both simultaneously. I have installed: 2 instances of Klipper 2 instances of Moonraker 1 Printscreen with its configuration for the two printers. 1 Fluidd .
What problem will I have?
Thanks for your help beforehand

2

Hello @alfredcollie !

The Klipper is a firmware solution that splits into two parts:

  1. The host on the SBC/PC that does the calculation work
  2. And the client that runs on the printer’s mainboard and does the connection to the hardware

So both make one unit an can not be separated.
For your second printer you need a second Klipper host.

More information here:

3

I have 2 instances of klipper installed

4

I see.

I assume you stick to this information, yes?

https://www.klipper3d.org/FAQ.html#can-i-run-multiple-instances-of-klipper-on-the-same-host-machine

1 Like
5

According to your log it seems the troublemaker is the host MCU according to RPi microcontroller - Klipper documentation

Depending on your Linux skills, you need to either:

  • Duplicate them to have two instances with two different endpoints OR
  • Deactivate it in one of your configs, this means remove the [mcu rpi] section
6

I already have created two instances of klipper and moonraker
I deleted [mcu rpi] from one of the printer.cfg and it no longer connects

What else can I do

7

Deleting the entire [mcu rpi] section will not cause a malfunctioning connection between Klipper and board.
Post a new klippy.log

8

This is the message that appears when removing MCU RPI
Unknown pin chip name ‘rpi’

I can’t send the klippy.log it’s too big

9

Archive klippy.log

10

Adding the RPI MCU again connects the printer immediately

11

You need to remove

[adxl345]
cs_pin = rpi:None
spi_bus = spidev0.2

in this case as well

12

Thank you a million, your help is effective, excellent day

13

I have 4 and yes the usb is a pain …insted of dev/by-id/* use dev/by-path/*

This allows you to connet through a usb hub also but important … you cannot move them around just keep plugged into the same usb

14

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.