Time to retire the MMU2S
It is time to declare the MMU2S retired. After all the recent firmware updates to support the new hardware, every 3.13 version breaks the MMU2S.It still works on old firmware if you can live with the annoying incomplete file or gcode for the wrong printer errors. I held out hope with FW3.13.3 and had the same problems as before. So, I have disassembled the MMU2S, reverted the hardware back to the MK3S+, and will do manual filament changes for multi-color prints from this point forward.
Prusa team, perhaps you should just announce that this device is now retired.
RE: Time to retire the MMU2S
Everyone is having issues with the update in MMU2, and prusa is not answering? I have same issue
It is time to declare the MMU2S retired. After all the recent firmware updates to support the new hardware, every 3.13 version breaks the MMU2S.It still works on old firmware if you can live with the annoying incomplete file or gcode for the wrong printer errors. I held out hope with FW3.13.3 and had the same problems as before. So, I have disassembled the MMU2S, reverted the hardware back to the MK3S+, and will do manual filament changes for multi-color prints from this point forward.
Prusa team, perhaps you should just announce that this device is now retired.
RE: Time to retire the MMU2S
100% agree. I have been wanting to remove it for ages but haven't had the time and patience to rip that piece of crap back off of my printer and revert the printer. Super lazy programming on Prusa's part not to create firmware updates that work on it. It never worked well in the first place, but ever since the last several updates it has gotten worse and worse. Every time I print recently I have to reboot and reboot and reboot the printer until finally it decides to finish the startup sequence without an error. I waste 30-40 minutes of messing with the thing every time I want to print something. I just flashed the firmware today with the same hopes you had and now even that painful process isn't working. The MMU2S just loses power completely in the middle of startup. What a piece of trash. Saying it needs more power is stupid. It worked for years on the power it has, the problem is Prusa's lousy firmware, not power.
RE: Time to retire the MMU2S
I ended up removing the MMU2S, reverting back to the MK3S+ to have a good working unit, and then sold all of it as a package deal; used the money to buy a new MK4 kit and am up and running again.
RE: Time to retire the MMU2S
Sounds like a good plan!
RE: Time to retire the MMU2S
Mh, I am happy with my MMU2S and the old firmware, it runs without problems since I added the additional power supply.
So I will not retire it any time soon.
If at first you don't succeed, skydiving is not for you.
Find out why this is pinned in the general section!
RE:
Saying it needs more power is stupid. It worked for years on the power it has, the problem is Prusa's lousy firmware, not power.
I beg to differ. There actually is a power issue - this is why the upgrade comes with an additional board to fix the issue. My MMU2 also worked without issues for some time but developed the known "all LEDs blinking" problem after a year or so and the issue is gone with the additional power supply. Why this happend after some time I do not know, perhaps increased friction has increased the power needed by the motors or some corrosion led to higher resistance somewhere...
If at first you don't succeed, skydiving is not for you.
Find out why this is pinned in the general section!
RE: Time to retire the MMU2S
Yes sorry. I retract my statement about lousy programming, turns out it is just bad design. After looking into it more, my assumptions were wrong, there is definitely a power issue. So I scraped my connectors and cleaned them with alcohol and was able to get it limping along again until I take the time to add power. I have four or five of those power boards around here in my hobby robotics stuff. One day I might take the time to install one. From the forums and my own experience it appears that lots of people had no issues until after a given firmware update like me. That made me conclude that it was a programming issue. But I don't print very often and before I do I often check for and apply any updates before printing a new job. So I guess that there could just be accumulated oxidation or increased friction in the system, as you mentioned, that has happened since I last used the machine and this is causing the issue and not the update.
Saying it needs more power is stupid. It worked for years on the power it has, the problem is Prusa's lousy firmware, not power.
I beg to differ. There actually is a power issue - this is why the upgrade comes with an additional board to fix the issue. My MMU2 also worked without issues for some time but developed the known "all LEDs blinking" problem after a year or so and the issue is gone with the additional power supply. Why this happend after some time I do not know, perhaps increased friction has increased the power needed by the motors or some corrosion led to higher resistance somewhere...
RE: Time to retire the MMU2S
I did like the MMU2S, it is a good device and worked well in the correct configuration. I see some people had some power issues, I never had that problem. Mine was purely a result of firmware updates. I know this because rolling back to the previous firmware fixed the problem. Though I also had the issue of the incomplete file errors after moving to the new Prusa Slicer. Everything still worked as long as I ignored the warnings. All of this gave me a good reason to upgrade to the MK4. But, before selling the MK3, I felt it was necessary to remove the MMU2s so the buyer did not think they were getting a shoddy setup.
My suggestion to retire the MMU2S is based simply on the reality that an organizations cannot continue to provide product support indefinitely for every device they create. Software vendors figured this out a long time ago. I think Prusa needs to take the same approach so that they do not have to shoehorn every new firmware version to fit every product.