MMU2S not recognized after firmware 3.13.2 (3.0.1) upgrade
I was hoping the new firmware was going to fix the misc issues that still with existing MMU2S unit. But - the firmware renders the MMU2S unit not recognized by the printer firmware. (says N/A in the support screen). I do notice that the installable firmware file has the string "mmu3" its name. I hope that's just indicative of being for both units. The firmware installs fine. channel lights flash, and the moving selector drives back and forth on startup - but it's not recognized after that.
planning on rolling back the firmware. Hoping for a better resolution.
RE: MMU2S not recognized after firmware 3.13.2 (3.0.1) upgrade
I was hoping the new firmware was going to fix the misc issues that still with existing MMU2S unit. But - the firmware renders the MMU2S unit not recognized by the printer firmware. (says N/A in the support screen). I do notice that the installable firmware file has the string "mmu3" its name. I hope that's just indicative of being for both units. The firmware installs fine. channel lights flash, and the moving selector drives back and forth on startup - but it's not recognized after that.
planning on rolling back the firmware. Hoping for a better resolution.
The printer needs to be on 3.13 then once you have installed the latest mmu firmware (yes it will show as mmu3 but works for mmu2 and 2s) you need to rentable the mmu in the Settings menu
Please help me out by downloading a model it's free and easy but really helps me out https://www.printables.com/@Hello_474427/models
RE:
I installed the main board firmware that was included in the package with the MMU2S firmware. 3_13_2_7080 is the number on it.
I am not clear on “reenable the MMU in the settings menu”
when I look at Support menu it shows a MMU as N/A. When I rolled back it shows the MMU version number.
RE: MMU2S not recognized after firmware 3.13.2 (3.0.1) upgrade
I installed the main board firmware that was included in the package with the MMU2S firmware. 3_13_2_7080 is the number on it.
I am not clear on “reenable the MMU in the settings menu”
when I look at Support menu it shows a MMU as N/A. When I rolled back it shows the MMU version number.
Follow step 19 to re-enable the mmu https://help.prusa3d.com/guide/10b-mk3s-setup-and-calibration_334155
Please help me out by downloading a model it's free and easy but really helps me out https://www.printables.com/@Hello_474427/models
RE: MMU2S not recognized after firmware 3.13.2 (3.0.1) upgrade
Worth checking I guess. I assumed that since it was in MMU enabled state before the upgrade, and since it did some startup actions, it was already there.
but I’ll do it again and check that to be sure.
thanks!
RE: MMU2S not recognized after firmware 3.13.2 (3.0.1) upgrade
Worth checking I guess. I assumed that since it was in MMU enabled state before the upgrade, and since it did some startup actions, it was already there.
but I’ll do it again and check that to be sure.
thanks!
If you have done the upgrade right It will be disabled. It's caught alot of people.
Please help me out by downloading a model it's free and easy but really helps me out https://www.printables.com/@Hello_474427/models
RE: MMU2S not recognized after firmware 3.13.2 (3.0.1) upgrade
thanks for the explanation, this has caught me out as well.
RE: MMU2S not recognized after firmware 3.13.2 (3.0.1) upgrade
I think the instructions for flashing firmware to the MMU need to make this point (about resetting the unit to "On") VERY much more explicit, because it is not an intuitively obvious result of the upgrade and is bound to confuse people like me. The diagnostic message "MMU: N/A" is not helpful.
And while I'm on the subject, the same instructions need to address the software problem with managing the USB port for the MMU flash process. I run the PrusaSlicer/manager program on a Linux system (Fedora 39). My experience was that I could set permissions on the ttyACM0 port to give read/write permissions to the slicer, but it didn't matter because some process about two seconds into the flashing sequence would reset the port permissions to root-only access. The only way I could manage to update the MMU firmware was by running the slicer as root. Which is neither standard procedure nor obvious.
I'm just posting here in this relevant thread in the hopes that someone in authority reads it.
RE: MMU2S not recognized after firmware 3.13.2 (3.0.1) upgrade
I'll add to the idea to put it in as a step in the upgrade guide ... took me an hour to figure it out with a lot of head scratching.