Multi color printing with Prusa's MMU V2 & Duet?
-
If it uses sensorless homing normally, wouldn't installing a normal endstop switch correct for that issue?
-
Yes, sure. And it should be easy to do.
-
I was hoping to pick up the MMU2 to put on a custom printer with a Duet 2 board.
Is this something anyone has already accomplished or would it be supported by Duet at any point in time?Or is this only a home grown venture?
-
@oliman I was going to. Awaiting a bit more reviews on the MMU2 and maybe the first design iterations.
-
Thanks @bartolomeus, I'll keep an eye out on reviews but I think I'm convinced the MMU 2 will be better than the Palette+. At least the design principles of the MMU 2 seem more dependable (also I'm not a fan of the custom Palette+ splicer).
Anyways, maybe someone will come out with a more mod friendly or printer independent MMU 2 clone. I would rather support Prusa, but not at the expense of taking a gamble of the MMU 2 not working with a non-Prusa printer.
I'm sure someone smarter than me will figure it out soon.
-
For sure, MMU2 seems more reliable, and easier/cheaper to fix if it brakes. And interfacing it with the Duet/Duex is easy if you remove the electronic, and wire motors to the Duet. Then it is just a matter of a few G-Codes as macros to use it. Maybe ask Prusa if they can sell it without the electronic?
BTW, I'm working on my own filament multiplexer, but a mix between v1 and v2: a passive mux above the extruder, like in the v1, but a simple loader, not Bowden, like in v2. I'm waiting for mini-clutch to test my design.
-
Someone is already designing an alternative. The design is on thingiverse. He also has a thread on this forum somewhere,
-
In fact, there are 2 designs on Thingiverse (both guys are on this forum). I started mine because it is different in many ways...
-
@fma Do you really think it would be easier without MMU v2 electronics? I think it should be possible to send the code to change the filament. But it is true you would need to change Duet FW to support this.
I really hope it will go this way. -
Well, wiring the motors on the Duet is a solution you can use right now, without any modification, so anyone can do it, and it does not need too much efforts nor skills...
I'm not sure it will be possible to communicate with the electronic, as it uses a SPI bus (MOSI/MISO/CLK are available - maybe not on a header, though - but it needs an additional CS - chip select - signal).
-
If the Prusa MMU needs 3 stepper motors, I wonder whether there is any cost saving compared to a 5-input Diamond, or a QuadFusion if 4 colours is enough for you; plus the 1 or 2 additional stepper motors and drivers. Also the Diamond and the Quad can do colour mixing, although the mixing isn't perfect.
If the MMU communicates with the main electronics via SPI, then you could connect it to the daughter board connector on the Duet. Of course, RRF would need to be modified to support the MMU.
-
@fma said in Multi color printing with Prusa's MMU V2 & Duet?:
In fact, there are 2 designs on Thingiverse (both guys are on this forum). I started mine because it is different in many ways...
Do you have any links to these?
-
Have a look at this thread: https://forum.duet3d.com/topic/6346/multi-material-filament-feeder-repurpose-e1-stepper-driver
There are links to both.
-
@dc42 for me the benefit of the mmu2 is that it remains direct drive, and doesn't add mass to the X carriage.
-
Just to add something to the mix, there is a company called RD4 which makes a multi filament feeder. It's called the RDB. They did approach me and asked if I would be willing to test one of their units, which I agreed to do. I signed a Non-Disclosure Agreement with them but alas they never did send me a unit or provide me with any information (if they had, I could not of course divulge anything). I note however that they have a stand at the TCT show so I'll stop by and see what's what.
Yet another alternative is the Pallete2 system by Mosaic.
Finally, the cheapest option is to pause the print, retract the filament, load new filament, purge and resume. Essentially, that is all that any of these systems do albeit in a semi automatic way. Unlike the Diamond and the Quad (and to some extent the pallette2) which have all the filaments loaded so switching between them is simple a matter of changing tools (which can be done "on the fly" without pausing the print).
-
I've made an MMU2 unit from some scrap parts I had laying around just as a Proof of Concept to see how if i could get it to work with Duet.
I haven't implemented any tramming which i do believe is important to avoid jams especially stringing is a problem.
I also think for it to be sort of reliable it needs to use some sort of filament sensor to check if the switch is successful or not so the print may be saved through manual intervention, though I haven't really found a way to solve this with Duet. I really would like to have some sort of conditional checking. -
If the objective is just add collors one can create a multi pen filament colorizer (like this https://www.thingiverse.com/thing:11742 but with all colors you want)
Also I discussed with a friend to have a special tool that holds a pen (grabbed from a 100 color carousel) and just draw each layer perimeter with the color you want
-
Hi, I built my own MMU2 and configured the Selector and bearing rotation mechanism with endstopless homing, but I cannot figure out how to configure the extruder drive motor with the five drive gears. How do I do that on the duet. What commands do I have to add to my config.g. Thanks
-
I am not familiar with the MMU2. Can you explain in more detail what the requirement is?
-
@dc42 the most critical actions for mmu is during unload/load of a filament where it could slip or jam. The way MMU2 handles it is to use a filament sensor to detect potential problems during load/unload.
Example when loading, move filament forward and check status of filament sensor. If doing this for X step and the filament sensor doesn't detect the filament you would do a retry phase, e.g back filament some and retry and if still doesn't succeed pause print for manual intervention.
Same principal would be used for unloading to verify it succeeds.Unfortunately I don't see a way to solve this with Duet with its current functionality, and I don't have any suggestion on how it could be solved using GCode. Wish there were some sort of advanced scripting support.