mmu2s reports as mmu3
this seems to be a common issue but no one has a fix or answer as to why its doing it, but after updating firmware on both my mk3s and mmu2s to the latest (3.14.0 for printer and 3.02 for mmu2s) it has been updated for quite a while now (pretty much since the release of the firmware), however i just got a new laptop and setup prusa slicer. i thought i was being smart and found the profile files on my old laptop and copied them to the new one in the same location, everything was working great prusa slicer was exactly how i had it setup on my old laptop, just the new version as my slicer was a few versions behind. anyway i sliced and threw a print on (using prusalink/connect witch also has been setup for a while with no issues) however now the printer tells me the gcode was sliced for a different printer.....weird considering i didn't change anything. oh well i know it was sliced for the correct printer to i told it to continue...the print finished with no problems. after that i looked into it, and printed an "old" (from a month or so ago) that was from the old laptop and slicer. it too now displayed the same message...so i started looking into it, opened up a serial connection and apparently now my mmu2s is convinced its an mmu3, the printer is also convinced its an mmu3. the hex file was from the mmu2s location on the site, and i verified it to the github file it should be mmu2s....so why is it saying its mmu3....this seems like a bug in the firmware that its changing the name on mmu2s's. does anyone have a work around for it or any ideas if i missed something, its also weird that it started well after the update
RE: mmu2s reports as mmu3
Double-check that the firmware files you flashed are indeed for the MMU2S and MK3S. Even if you downloaded them from the correct source, it's worth redownloading the firmware from the Prusa website or GitHub to rule out corruption or mix-up.
RE: mmu2s reports as mmu3
The firmware literally no longer supports MK3S+MMU2. I've created a pull request to add new variant that works as expected. Despite how easy the code fix was I'm suspicious of whether this'll actually work in Prusa's packaging and deployment process.
RE: mmu2s reports as mmu3
sorry for not updating for anyone who's having this issue as well, i found i just needed to change the printer in prusaSlicer to have mmu3 and everything seems to be working fine. perhaps some documentation should be included on the download page for the firmware, or in the readme or something that says you will need to setup a new printer in the slicer.