kelvinAFrom asking around, and research, it sounds like Klipper might run into issues with the dual MCU setup I'd need. This is becuase boards like the RPi (and I assume the Orange Pi) are not realtime. The main concern is the dual ZM (main z gantry) axis, which ideally should move at the same time.
This is what I'm currently planning:
- Octopus Pro
- X1
- Y1
- ZM
- ZM
- W1
- V1
- E1
- S1
- Octopus Pro
- X2
- Y2
- Z1
- Z2
- W2
- V2
- E2
- S2
Where
- X[number] = X for IDEXY head [number]
- W = Either the rotational bed axis motor or the belt bed motor
- V = Rotational axis motor in the Slime [gd0088]
- S = Extruder motor in #SecSavr Select [gd0091]
- (also, I just found out about Hackaday.io's hashtag feature while typing this log)
Discussions
Become a Hackaday.io Member
Create an account to leave a comment. Already have an account? Log In.
Yes, there are a few limitations in klipper with multi-mcu setups. I know that paired motors are supposed to be on the same MCU. I believe that it's recommended for limit switches to sit on the same MCU as the motors they control, as well. ie, your X end stop should be on the same mcu as your X motor(s). You might want to double check that one, but I'm pretty sure.
Are you sure? yes | no