MK4S MMU3 "Parking"
I have a MK4s with a MMU3 and in the midst of doing a print job the printer stated it was reloading the filament and then went to parking and hung there. I checked the and there was filament all the way from the MMU to the Extruder. Is there a way to recover from this? I tried a hard reset but all that did was go back to start. Losing my print job. Anyway how is the best way to recover and get the print restarted. BTW my understanding is a "hard reset" is turning the printer off and then back on. Is that correct? I also thought that if you were in the middle of a print that the printer would continue the print. Am I incorrect?
RE: MK4S MMU3 "Parking"
I wish they would complete the MMU firmware/SW support. I paid full price for a complete product, not a prototype.
Having to reset / power-cycle the printer on common failure modes is completely inacceptable.
Example: Accidentally disable the side filament sensor on Core one (which is not involved in MMU printing), and it results in misleading errors during the next print when loading filament from FINDA to nozzle. It is an old problem, it is understood, nothing happens. But they're designing wooden oak cabinets for this.
RE: MK4S MMU3 "Parking"
I agree, this is not a "well-rounded" product. I had bought an MMU2S together with my first MK3S, but kept it in the box. Last year when the upgrades for the MK4S/MMU3 came out, I ordered those upgrades together. Sometimes the combo works just fine, but then suddenly not. Mostly it works if I stand next to the printer and if I go into the next room the probability for problems rises. 🙂
I have it in a Prusa Enclosure and making adjustments to the MMU3 (tension, sensor etc.) is really awkward. I do have the hinged top, but I have my spools on there, so I have to put those to the side first if I want to open the lid.
I have the feeling that every time I use it it puts in some serious effort to remind me how much I do not need it in my life. 🙂
RE:
The MK4S/MMU “parking” bug didn’t show up until firmware version 6.4.0. It bit me a couple of times, but I reverted to 6.2.6 and it has been reliable again. No word from Prusa, as far as I’ve seen, that they’ve even acknowledged the problem.
The mediocre support for their established MMU product makes me not inclined to throw more money their way for the INDX, which so far is still vaporware.
MK4S/MMU3