Upgraded Printer from MK3-MMU2s to MK3s-MMU2s - Now MMU is mostly dead - Help
I just finished taking my time upgrading my MK3 with the smaller extruder and MMU2s to the MK3s with the MMU2s. I feel I have to be specific due to all the confusion over which combination of hardware one has now. I decided a good move would be to flash both the MK3s AND the MMU2s, even though I knew the MMU2s already had the newest firmware in it.
I'm using a PC with Ubuntu as the host PC. Programming the MK3s went fine. Not so much with the MMU. I programmed it, and it finished in a much quicker time than th eMK3s did, as usual. But then it was completely unresponsive. I've tried reflashing both boards again, but now the MMU appears dead.
Prior to the MMU2s firmware upgrade, when I powered the printer on the MMU would flash LEDs, grind stepper motors, make a bunch of clattering noises, and eventually everything would settle down. Now, all I can see after a little detective work is upon power up or pressing the reset button on the MMU board, the diode D9 blinks in patterns, but doesn't seem repeatable enough for me to give anyone a clue. It's about 16 blinks, five in succession, a hiccup, 2 to 5 more, another hiccup, and then another 5 or so blinks.
As I continue to play with it, I can power the board up and get a green light on indicator 1, but pressing reset turns all five LEDs on.
Dmesg returns the following:
[54712.130002] usb 1-6: new full-speed USB device number 33 using xhci_hcd
[54712.281743] usb 1-6: New USB device found, idVendor=2c99, idProduct=0003, bcdDevice= 0.01
[54712.281750] usb 1-6: New USB device strings: Mfr=2, Product=1, SerialNumber=3
[54712.281754] usb 1-6: Product: Original Prusa i3 MK3 Multi Material 2.0 upgrade (bootloader)
[54712.281758] usb 1-6: Manufacturer: Prusa Research (prusa3d.com)
[54712.281761] usb 1-6: SerialNumber: 59373332363315060C12
[54712.287807] cdc_acm 1-6:1.0: ttyACM0: USB ACM device
[54719.885016] usb 1-6: USB disconnect, device number 33
[54743.381193] usb 1-6: new full-speed USB device number 34 using xhci_hcd
[54743.532149] usb 1-6: New USB device found, idVendor=2c99, idProduct=0003, bcdDevice= 0.01
[54743.532158] usb 1-6: New USB device strings: Mfr=2, Product=1, SerialNumber=3
[54743.532165] usb 1-6: Product: Original Prusa i3 MK3 Multi Material 2.0 upgrade (bootloader)
[54743.532170] usb 1-6: Manufacturer: Prusa Research (prusa3d.com)
[54743.532175] usb 1-6: SerialNumber: 59373332363315060C12
[54743.537626] cdc_acm 1-6:1.0: ttyACM0: USB ACM device
[54746.197302] usb 1-6: USB disconnect, device number 34
[54746.197712] xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[54746.198020] xhci_hcd 0000:00:14.0: WARN Cannot submit Set TR Deq Ptr
[54746.198021] xhci_hcd 0000:00:14.0: A Set TR Deq Ptr command is pending.
[54746.198025] xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[54746.198198] xhci_hcd 0000:00:14.0: WARN Cannot submit Set TR Deq Ptr
[54746.198199] xhci_hcd 0000:00:14.0: A Set TR Deq Ptr command is pending.
[54746.198201] xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
And I'm unable to reflash the MMU. So.... it's MOSTLY dead. Any ideas? In the meantime, I'll try a Windows 10 computer and see if that OS has better luck.
And booting into Windows 10 gives me the same results. PrusaControl cannot see the MMU. Device manager will show the MK3 when I connect to that, but shows nothing when I connect to the MMU.
Oh, if it helps, I am very familiar with AVR and have the tools to put a bootloader back in there if I could have access to it. I'm assuming the 2x3 header is the ICSP port. If so, I'd probably also need to know which pins are which for programming.
It's starting the bootloader during powerup as evidenced by the dmesg logs, if you can get the flash timing just right you should be able to get it to flash. You may need to use avrdude manually to specify the port if PS won't autodetect, but doing so and poking the reset button to get it to pass through the bootloader stage while it's looking for a device to flash should get you sorted.
Had the same thing last week.
Yep - that 6-pin header is the ICSP header.
And yep you can flash via this header - that's how I revived my MMU2S unit.
Take a meter and measure which pin connects to the sheep - this is the GND pin - rest is the standard ICSP pin layout.
Szafran, where did you get the bootloader file?
If I do reprogram the bootloader I'm going to try using the Microchip PICKit4. In the meantime, I'm going to try VintagePC's idea. I do know what the serial port is in Linux, so I may be able to force the port name. I'm already a member of dialout, so I have permission to write to that port as soon as it's instantiated... That may be the way to go.
Or... I can waste so much time on this it would be cheaper to buy a new board and go from there.
All files are on the github pages:
I've flashed from Windows using:
"c:\Program Files\Arduino\arduino-1.8.9\hardware\tools\avr\bin\avrdude.exe" -C "c:\Program Files\Arduino\arduino-1.8.9\hardware\tools\avr\etc\avrdude.conf" -v -v -c usbasp -p atmega32u4 -e -D -b 57600 -U flash:w:MM-control-01.hex:i
But if at least one of your MMU status LEDs is blinking after printer power on/reset then your bootloader is probably ok. Try the FW first.
One thing to note - after flashing this way I'm unable to flash via USB anymore, just the ICSP way. The MMU is visible normally in the OS, but PrusaSlicer gives errors that it can't properly reboot the MMU for flashing.
Well, as much as I was looking forward to the thrill of the hunt as I determine why my MMU unit failed and how to fix it, I don't get to. Prusa has asked me to return the PCB in exchange for a replacement. It's all about time management. I like solving problems, but I also like being productive. In the meantime, I'm a single filament print house.
I did buy an MK2s - MK2.5s upgrade kit and a ruby nozzle for my less used printer last night. For all the complaints I see on these forums, I have to say I don't harbor the slightest frustration toward Prusa. I'm normally an early adopter. I ordered my MK3 and the MMU within days of their respective announcements and waited patiently for them to ship. During that time they've improved the deals, giving me more features than I bought either without raising the price or actually lowering it. And the print quality/reliability continues to improve. Add to that what they've just done: Do a warranty replacement of one of the very first MMU2 boards they shipped in volume at no cost... I'm happy. I'll stick with this company! A little patience is all it takes to recieve excellent customer service.
I'm going through the same thing myself. I tried updating my MMU2S to the latest 1.0.6 firmware and the update process failed. Now my MMU2S seems almost dead as well. I see the diode D9 blinks for a few seconds during start-up (and the MMU2S is visible to PS during this time) but that is all. When D9 stops blinking the MMU2S is disconnected from the computer and there are no other start-up sounds or movements. Also no LED will light on the front of the unit.
I'm in the process of working through it with Prusa Support now.
As a bonus I now see an SPI error message when I power-on the printer itself. Even with the MMU2S disconnected I see this error since the firmware update failed. I think this part may have been my fault though. I was connected to the MMU2S with the micro-usb cable to flash the 1.0.6_MMU2S firmware but I did not think to disconnect the USB to my printer. In other words I was connected to both MK3S and MMU2S with USB connection at the same time. Even though I was only flashing MMU2S firmware and I'm sure I selected the correct device in PS, the failed MMU2S update has likely bricked my MMU2S and possibly damaged my MK3S as well. Lesson I learned here is only connect ONE device at a time when flashing firmware.
So I just managed to bring my MMU2S back to life!
Here's what I figured out. First my laptop which I typically use to update my printer is running KDE Neon that is based on the latest Ubuntu LTS (18.04). I have never had a problem with this until I tried to flash MMU2S firmware 1.0.6 which failed and like rob-w5 my MMU2S was basically dead. I had diode D9 blinking during MMU2S startup but that was it. Also my laptop and PS would only see the MMU2S during these first few seconds while D9 was blinking.
I tried repeatedly to reflash 1.0.6 by trying to time pushing the reset button and press flash as suggested by vintagepc to no avail. I also tried this process in a Windows VM using a program called Xloader (as suggested by Prusa support) but nothing would work. The MMU2S would disconnect after only a few seconds. Not enough time to flash the firmware. At this point I only had Xloader installed on Windows I had not yet downloaded PS. After Xloader failed I responded to the latest Prusa support email to inform them Xloader was a bust.
I was ready to give up but at the last minute I decided to try the previous 1.0.5 firmware for the heck of it. Now, to be clear I'm back on my Ubuntu based laptop and I try flashing 1.0.5 with PS again using vintagepc's suggestion. This still fails to flash but I notice now that my laptop and PS can at least see the MMU beyond the first few seconds after being powered on or reset. Progress! So I try a few more time to flash 1.0.5 using PS in Ubuntu. Still no luck but at least the MMU2S seems to remain connected now.
OK back to the Windows VM and try Xloader again with 1.0.5. Fail. My new found hope is short lived and quickly starting to fade. As a last ditch effort I now decide to download and install the Windows version of PS and give it one last go AND IT WORKS!!! My MMU2S is fully alive again and running firmware 1.0.5.
So I turned off my Windows VM and I'm back to Ubuntu PS and I again tried to flash MMU2S_firmware_1.0.6. This time I was sure to only have the micro-usb cable connected to my laptop and MMU2S. NO USB cable plugged into the MK3S. I hit flash and guess what? Same problem. Firmware update failed. Reboot MMU2S and its dead again. Tried to flash MMU2S_1.0.5 and it fails as before.
Startup Windows VM use PS to flash MMU2S_1.0.5 and MMU2S comes back to life. Proceed to flash MMU2S_1.0.6 using PS in Windows and it works.
From here I still remain curious. I also run Arch Linux on my desktop computer. Before shutting down the Windows VM, I again downgraded to MMU2S_1.0.5 and made sure everything was working before another quick test. This time instead of using my Ubuntu based laptop, I connected the MMU2S to my desktop running Arch Linux. I copied the PrusaSlicer.appimage and the MMU2S_1.0.6_firmware from my laptop to my desktop so to be sure I'm using the exact same files. Open PS and try again upgrading to MMU2S_1.0.6 and it works! Still connect to desktop using Arch I try downgrading to MMU2S and it again works. Reflash 1.0.6 again using Arch Linux and goes off without a hitch.
I ran into this today while updating my firmware. Printer went well, but the mmu 1.06 flash killed the mmu with the same symtems, LED D9 flashing for while then an apparently dead unit. Contacted Prusa Research but in the meantime came here and saw these posts. vintagePCs suggestion seemed simple so I tried that. In the PS firmware flasher I selected the 1.05 file, pressed the mmu reset button and it started to flash but stopped, indicating it couldn't find the mmu and gave me a red message telling me to press the reset button on the mmu. When I did the flash continued and completed successfully. So my mmu is up and running on 1.05 again. I haven't tried the 1.06 update again yet. I'm using Ubuntu 18.04.3 LTS with KDE so I think I'll update that before I try again or wait to see if a fix comes out.
Thanks to all for the helpful info.
I had some free time this evening so I decided to give the 1.06 update a shot again. I updated my Kubuntu system, downloaded the new PS 2.1.0 and tried it again. Same as before, failed flash. Tried the press the MMU reset button thing a few times, nope.
I decided to try troy-p3s method of using a different OS. I only have one PC running and didn't want to change it so I thought I could try using a live linux distro. I tried a few that weren't quite what I was looking for. I finally tried Slax. It has a GUI and had a file manager. I went to my main HD, ran the PS appimage, It ran, flashed 1.06 and had success. Went to the printers LCD and checked the MMU version and it still showed 1.05. I tried flashing again, still 1.05. Hmm, lets try switching power off and on. That did it. It now reads 1.06 so alls well in printerland again.
I just bought the MMU2S and spend a while for assembling it. to to I've just checked that MMU2S is discovered by the printer (ok, fw version :1.0.5), and decided to upgrade to 1.0.6. And I ran into the same problem. It started to download and for unknown reason, it just stopped in the middle and failed.
Well, my MMU2 is now dead (unrecognized by the printer and my PC). I will have a try from post shortly, thank you for posting.
Laptop Mint 18.3 (ubuntu-based)
PS 2.1.0 (appImage freshly installed)
sure looks like everyone having flashing mmu problems is running linux, i suspect the problems are something to do with the USB port handling under various lunix distros . so far it looks like Slax and Arch live images may work
Yes you're right. But I never encountered this kind of issue thanks to the linux structure itself (file based for peripheral access). So no driver is required. Linux version is 126.96.36.199...
BTW, good news, the sequence described by mike-I8 works like a charm. Just check out the release 1.0.5 from the github and reset the MMU every time the system asks for :-). the MMU is back to life.
Thank you all for your valuable posts.
I hope that PRUSA team will find a workaround for ubuntu based system.
I ran into the same issue while trying to upgrade my MMU2s with firmware 1.0.6: after the upgrade attempt, the D9 diode was flashing then the MMU2s seems dead. I'm running Debian (buster and sid). It turns out that disabling ModemManager, allowed me to flash my MMU2s and get it working again.
I disabled ModemManager:
$ sudo systemctl stop ModemManager.service
then reset the MMU2s as instructed by PS, and that's it !