search

zruncho3d / DuelingZero

Dueling Zero - a Dual Gantry V0 mod. Enable dual-color, dual-material, and even multi-part printing... with the same speed and quality as single-extruder printing.
GNU General Public License v3.0
205 stars 15 forks source link

Not an issue - Just a question... #3

Open dsred opened 1 year ago

dsred commented 1 year ago

Dear zruncho3d,

I saw your design and find it very excellent for building an IDEX-System. Thank you for your effort!!!

I'm planning to build one just on a lager scale than 120x120mm. My question is regarding klipper: Beside adjusting all the macros, is there any additional changes in der source code of klipper necessary to get the two independent gantries running in klipper?

Is there any need to run two skr boards? I have an octopus pro lying around, including two ebb36 can modules. Would'n that be also an possible setup?

Thank you very much, dsred

dsred commented 1 year ago

Dear zruncho3d,

I properly should have done this before but after reading all your documentation including software-readme most my questions are clear now.

To run klipper you will need to work with this repository: https://github.com/Tircown/klipper-zruncho And the need of two skr boards seems also to arise from current klipper limitations.

Do you know if this implementations will find they way into the official klipper branch at some point. Is there still development going on here?

Thank youvery much, dsred

zruncho3d commented 1 year ago

Hi. FWIW, I don't know anyone who's looking to build one at the 120x120 size; it really makes more sense in the 170x170-ish range, and honestly I should increase the width by 20mm by default so that you can get closer or to the full 170-180 width of a Prusa Mini or K3 bed.

Re: Klipper code - it's really just the one-file change required to move two gantries with T0 and T1 commands and have them home. Use this branch, until further notice: https://github.com/zruncho3d/klipper-orig/commits/dual_gantry_unsquashed

Tircown had made some changes with unanticipated side effects and I don't recall if the branch you reference is that one. I recently rebased this branch on the latest kilpper and it all worked fine, as all changes are to the one kinematics file.

Run whatever you've got; the beauty of Klipper is that it doesn't matter what drivers, or number of them, you use. I've been meaning to switch to an Octo Pro recently to have the possibility of later deploying RRF support. That would be one board with the CAN side built in, so it'd be pretty clean to wire, at least as clean as you can get without going to gantry boards. EBBs are my favorite toolboard because of easy DFU flashing and larger connectors and low price, and EBB36 should be fine here; just don't print the shrouds for square boards like mine (EBB42).

Re: official Klipper - Kevin's policy is to prioritize patches for integration with higher numbers of printers affected. That's fair, and this isn't a board-value patch 😄 . In the long run though, I think that policy is actively harmful for code like this which could make Klipper the best choice for a kind of kinematics. But the good news is that it doesn't matter what Kevin does. It's just one file, thanks to great work by Tircown. And I know Tircown would love to improve that code for mergeability over time too. If we get a bunch of Dueling Zeros, I'm sure Kevin would be more receptive to inclusion, and I'd love to see that in the release notes someday, especially because the number of people whose code would be broken is very low.

So ... are you gonna build one, and be the first in the world beyond the original to get one working? 😄

jeremiahvpratt commented 1 year ago

Hey zruncho! Is this still the recommended branch for klipper? Also, the klipper firmware section of the software page is currently missing a link to the dual gantry firmware repo (which is understandable if the main branch is unstable and you still recommend this alternative)