-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to upgrade MMU2S firmware to 3.13.* #4417
Comments
You can just update the MMU2 with a cable directly in the MMU2 from
PrusaSlicer with the MMU2 hex file
Den fre. 29. sep. 2023 kl. 12.43 skrev tbatur ***@***.***>:
… I have 2 MK3S+ (with MMU2S) printers. Before version 3.13.*, when I
updated the printer firmware, the MMU2S firmware was also updated
automatically.
But when I upgrade to this latest version (3.13.0, 3.13.1, 3.13.rc2) only
the printer is updated, and when I activate the MMU in the settings it says
that I have to update its firmware too.
I have tried this on both my printers with 5 different cables, I even
bought 1 new data cable, and there is no problem with data exchange. I also
tried it on both macOS and Windows but the result is always the same. It
gives the following error. I have also contacted live support about this
but they have not found a solution either.
As a result, I had to revert back to 3.12.2. I don't know if anyone else
has this problem, but I couldn't upgrade.
[image: Screenshot 2023-09-29 at 13 32 15]
<https://user-images.githubusercontent.com/12153900/271546230-680973a6-9fa3-4d18-a5a0-5a36945d0a57.png>
—
Reply to this email directly, view it on GitHub
<#4417>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA5EA6HJFUKA7HUQRAV7JS3X42Q37ANCNFSM6AAAAAA5MI27X4>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
Med venlig hilsen / Kind regards
*Henrik Johansen Koch*Hans Erik Nielsens Vej 7, DK 3650, Ølstykke, Denmark
*T +45 4710 0305*
*F +45 7734 0307*
*M +45 4068 0305**E-mail ***@***.***
***@***.***>*
|
I guess you didn't read exactly what I wrote. That's exactly how I tried it. Also, There is no separate hex file for the MMU2S. |
Looks like you try to update the MMU with the printer firmware. You need to download the separate hex file for the MMU. (The one I linked is compatible with Printer Firmware 3.13.2-RC1) |
Sorry. I just answered what you wrote: "Before version 3.13., when I
updated the printer firmware, the MMU2S firmware was also updated
automatically"
I have never seen this been done automatically. I have always done this
with a micro usb cable from the PC to the MMU2+.
And with the last version, I also did a "manually" update but with success
/Henrik
Den fre. 29. sep. 2023 kl. 13.49 skrev tbatur ***@***.***>:
… You can just update the MMU2 with a cable directly in the MMU2 from
PrusaSlicer with the MMU2 hex file Den fre. 29. sep. 2023 kl. 12.43 skrev
tbatur *@*.
*>: … <#m_-3666623279175231635_> I have 2 MK3S+ (with MMU2S) printers.
Before version 3.13., when I updated the printer firmware, the MMU2S
firmware was also updated automatically. But when I upgrade to this latest
version (3.13.0, 3.13.1, 3.13.rc2) only the printer is updated, and when I
activate the MMU in the settings it says that I have to update its firmware
too. I have tried this on both my printers with 5 different cables, I even
bought 1 new data cable, and there is no problem with data exchange. I also
tried it on both macOS and Windows but the result is always the same. It
gives the following error. I have also contacted live support about this
but they have not found a solution either. As a result, I had to revert
back to 3.12.2. I don't know if anyone else has this problem, but I
couldn't upgrade. [image: Screenshot 2023-09-29 at 13 32 15]
https://user-images.githubusercontent.com/12153900/271546230-680973a6-9fa3-4d18-a5a0-5a36945d0a57.png
<https://user-images.githubusercontent.com/12153900/271546230-680973a6-9fa3-4d18-a5a0-5a36945d0a57.png>
— Reply to this email directly, view it on GitHub <#4417
<#4417>>, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA5EA6HJFUKA7HUQRAV7JS3X42Q37ANCNFSM6AAAAAA5MI27X4
<https://github.com/notifications/unsubscribe-auth/AA5EA6HJFUKA7HUQRAV7JS3X42Q37ANCNFSM6AAAAAA5MI27X4>
. You are receiving this because you are subscribed to this thread.Message
ID: @.*
*> -- Med venlig hilsen / Kind regards Henrik Johansen KochHans Erik
Nielsens Vej 7, DK 3650, Ølstykke, Denmark T +45 4710 0305 F +45 7734 0307
*M +45 4068 0305**E-mail @.*** *@*.***>*
I guess you didn't read exactly what I wrote. That's exactly how I tried
it.
—
Reply to this email directly, view it on GitHub
<#4417 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA5EA6AYW4DUWK6Y3IL2HCDX42YUNANCNFSM6AAAAAA5MI27X4>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Med venlig hilsen / Kind regards
*Henrik Johansen Koch*Hans Erik Nielsens Vej 7, DK 3650, Ølstykke, Denmark
*T +45 4710 0305*
*F +45 7734 0307*
*M +45 4068 0305**E-mail ***@***.***
***@***.***>*
|
@tbatur You are trying to flash the printer firmware on the MMU. This will never work! The MMU has it's own separate Use this MMU firmware with 3.13.0: For 3.13.1 and 3.13.2 you will need MMU FW 3.0.1 |
It's done now. I didn't try it because the name of that file only says MMU3, thank you. |
Yes, it is done with that file, but they should fix the name of that file. Because of the name it looks like it's only for MMU3. |
Closing as resolved. |
I have 2 MK3S+ (with MMU2S) printers. Before version 3.13.*, when I updated the printer firmware, the MMU2S firmware was also updated automatically.
But when I upgrade to this latest version (3.13.0, 3.13.1, 3.13.rc2) only the printer is updated, and when I activate the MMU in the settings it says that I have to update its firmware too.
I have tried this on both my printers with 5 different micro USB cables, I even bought 1 new data cable, and there is no problem with data transfer. I also tried it on both macOS and Windows but the result is always the same. It gives the following error. I have also contacted live support about this but they have not found a solution either.
As a result, I had to revert back to 3.12.2. I don't know if anyone else has this problem, but I couldn't upgrade.
The text was updated successfully, but these errors were encountered: