Primary MCU must be unaliased? Pure CANBUS setup, No primary MCU

Is it possible to have a configuration setup where there is no mcu that does not use an alias?

In other words, I just converted my Voron 2.4 to a pure CANBUS toolhead driven setup. Each Z axis has it’s own board (SHT42), The X and Y have their own board (Huvud, I did CANBus on the X and Y a year before I did the Z change hence the difference) and the Stealthburner actual toolhead board (SB2040).

When I was redoing my setup after switching over the Z axis drives I made an alias for all my mcus on the Z drives (Z, Z1, Z2, Z3) and I keep getting the error that “serial” wasn’t defined under mcu. It was only after I changed the “Z” stepper to just be [mcu] in the config that it worked.

As more and more people go to this kind of “decentralized” stepper driver setup utilizing CANBUS, I can see that having a “primary” board might become a thing of the past.

Is there a way to tell Klipper I have no primary board? Or maybe a future iteration of Klipper not rely on an unaliased [mcu] and instead throw an error if the kinematics don’t match up with the specified drives (I say I have a cartesian but I don’t define a y axis, or I have a core xy but I don’t specify 4 z drives etc.)

This setup is not supported by Klipper and likely leads to unwanted behavior. See Multiple Micro-controller Homing and Probing - Klipper documentation

Note that an axis with multiple steppers (eg, stepper_z and stepper_z1) need to be on the same micro-controller in order to use multi-mcu homing. For example, if an endstop is on a separate micro-controller from stepper_z then stepper_z1 must be on the same micro-controller as stepper_z.

I noticed that after I posted, I have some further questions but they are more development related so I’ll start a relevant topic in the developer section. Thanks.

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