RE: I am at a complete loss, MMU2S fails to even fail consistently
Is anyone concerned at all about the false advertising: Prusa videos showing magical mulitcolor prints, but very few users, even on Prusa forums achieving even mediocre success? I have a MK3 with MMU2 and could not get it to work after 6 months of trying, reading forums, and watching youtube videos.
The fact that Prusa is not selling a MK3 with MMU2 factory assembled is a big red flag. My first assumption is always user error in assembly. But I see others are facing very same issues. I strongly recommend Prusa to sell an MK3S with MMU2S fully assembled to prove that it can print multimaterials out of the box. I would buy one today! (even though I already have an MK3 and MMU2)
RE: I am at a complete loss, MMU2S fails to even fail consistently
Well...... New plan..... I'm going to finish reassembling my ANET A8 first..... so I can print parts to make the MMU2S work.... Yes, it IS that ridiculous. I'm thinking they let scope creep keel them with the chimney design.
The MK3S design with magnets seems solid... seems like a different switch/sensor should be used for the bondtechs.
Now here's the kicker... Why is it even possible for the *IR sensor* to have a false filament runout event on MMU2?..... How can the filament be cut WHILE in the bowden tube, unless the tube gets disconnected/severed catastrophically?
IF the FINDA still shows filament presence, the IR sensor shouldn't be used for filament runout - only to sense when the filament arrives at gears....for initial load! I'd rather have a longer piece of filament kick back out of the system and have FINDA dictate filament runout.... OR at least look for an IR-FINDA disagree, and have a handling procedure there...
Otherwise, if the FINDA isn't used to deal with/detect filament runout before the IR, then what are you going to have to do with the remaining/ran out filament that it has to eject? It will be too short, and get stuck in the tube....requires some dissassembly...
FIRMWARE FIRMWARE FIRMWARE.