Notifications
Clear all

Firmware 1.0.3 for the MMU2 unit  

Page 1 / 3
  RSS
Jakub Dolezal
(@jakub-dolezal)
Membre Admin
Firmware 1.0.3 for the MMU2 unit

UPDATE: final version 1.0.4 is out https://shop.prusa3d.com/forum/general-discussion-announcements-and-releases-f53/firmware-1-0-4-final-for-the-mmu2-unit-t27891.html

Hi guys,
this is an upgrade of the firmware for the MMU2 control board inside the multi-material unit. This is a final release for every MMU2 owner.

What is new?

Power panic support
This firmware version ensures that power panic works correctly on MK3 printers with MMU2. In case of a power surge, the printer will save the latest G-code instructions and after the power is restored, rehomes and continues with the print.

Smarter operation
In the previous firmware versions, when the filament was loaded to the extruder during a power-on (e.g. resetting the printer), the user had to manually remove the filament first. Otherwise, the MMU2 unit was unable to finish the initializing sequence. Starting this firmware release, the unit finishes the sequence with filament loaded and when there is a need to move with the selector (e.g. a user wants to use another filament slot), the printer indicates with all LEDs flashing red to unload the filament first or in case of resuming the print after a power failure, the printer unloads the filament by itself.

Faster Individual Filament Calibration
Now, there is a possibility to speed up the movement of pulleys while adjusting the filament position during the PTFE length calibration by pressing the left/right button for a longer period of time. Also, the maximum value of the PTFE tubing length was increased. These two changes should help users with custom modifications (such as using the MMU2 inside an enclosure with longer PTFE tubing).

IMPORTANT: To enter the service menu (if needed), please
-> turn the printer on and let it boot all the way
-> Reset the printer using the X button next to screen and immediately press the middle button on the MMU2 unit and hold until all LEDs turn red.

---

Supported printers:
Original Prusa i3 MK3 Multi Material 2.0
Original Prusa i3 MK2.5 Multi Material 2.0

Download link:
https://www.prusa3d.com/drivers/

Firmware flashing guide:
https://manual.prusa3d.com/Guide/Upgrading+the+firmware+v1.5/66

Please report any bug here:
https://github.com/prusa3d/MM-control-01/issues

We wish you a successful calibration and look forward to your feedback!

Assembly manuals

/ Knowledge Base
The guy behind Prusa assembly manuals...

Publié : 13/12/2018 11:35 am
maxx78
(@maxx78)
Estimable Member
Re: Firmware 1.0.3-RC1 for the MMU2 unit

what is the new max. lenght for the PTFE tube ?

Publié : 13/12/2018 12:43 pm
Jakub Dolezal
(@jakub-dolezal)
Membre Admin
Topic starter answered:
Re: Firmware 1.0.3-RC1 for the MMU2 unit

Hi,
it is 791.7 mm according to our FW devs.

Assembly manuals

/ Knowledge Base
The guy behind Prusa assembly manuals...

Publié : 13/12/2018 10:04 pm
Daniel
(@daniel-19)
Trusted Member
Re: Firmware 1.0.3-RC1 for the MMU2 unit

Still no filament sensor option enabled, very pitty, after that long time between the previous version and this version nothing special expect power panic. TheZeroBeasts firmware has much much more improvements within shorter times, and also the filament sensor is enabled since a while in his fw. Still no fixes on the github issues what I have posted months ago. Pitty pitty pitty

Publié : 13/12/2018 11:03 pm
AbeFM
(@abefm)
Membre
Re: Firmware 1.0.3-RC1 for the MMU2 unit

""-> Reset the printer using the X button next to screen and ""

X button next to screen?

I maintain an informal list of San Diego, CA 3D printing enthusiasts. PM me for details. If you include a contact email and I can add you to the informal mailing list.

Publié : 13/12/2018 11:33 pm
Jonathan Kayne
(@jonathan-kayne)
Trusted Member
Re: Firmware 1.0.3-RC1 for the MMU2 unit


""-> Reset the printer using the X button next to screen and ""

X button next to screen?

He's referring to the reset button below the knob on the right of the LCD screen. It has an X marked on it

Jonathan Kayne
Virginia Tech Class of 2021 - Electrical Engineering
Thingiverse Profile: https://www.thingiverse.com/jzkmath/about "I am always thinking about making. My future begins when I wake up and see the light." - Miles Davis

Publié : 13/12/2018 11:54 pm
Jakub Dolezal
(@jakub-dolezal)
Membre Admin
Topic starter answered:
Re: Firmware 1.0.3 for the MMU2 unit

Final version released! See the first post 😉

Assembly manuals

/ Knowledge Base
The guy behind Prusa assembly manuals...

Publié : 18/12/2018 11:15 am
Peter L
(@peter-l)
Honorable Member
Re: Firmware 1.0.3 for the MMU2 unit

One of the listed changes is "smarter operation."

From the release notes, it turns out that this means the MMU can initialize itself with filament loaded, rather than just erroring out.

Publié : 18/12/2018 5:16 pm
Zaiden
(@zaiden)
Active Member
Re: Firmware 1.0.3 for the MMU2 unit

It is unbelievable that the biggest issue which causes every single print to fail using the MMU2 is not fixed yet. Upon filament change in multi color use, the speed setting is reset to 100% no matter what you set it in Slic3r. This may be fine with PLA, but I use only PETG so I've yet to be able to use this $300 paperweight. Awesome.

Kudos to the support team that said this would be fixed on the "next update". 👿

Publié : 19/12/2018 3:35 am
JuanCholo
(@juancholo)
Honorable Member
Re: Firmware 1.0.3 for the MMU2 unit

the speed setting actually switches to a bunch of different speeds depending on the slicer settings.

it can go anywhere from 0 to 100%

https://github.com/prusa3d/Prusa-Firmware/issues/1300

this is a big bug that needs to be fixed.

“One does not simply use a picture as signature on Prusa forums”

Publié : 19/12/2018 4:31 am
Panayiotis
(@panayiotis)
Active Member
Re: Firmware 1.0.3 for the MMU2 unit

Hey, regarding the speed changes, check https://github.com/prusa3d/Prusa-Firmware/releases/tag/v3.5.1

For me the biggest issue is that the firmware does not use the filament sensor to verify that the filament has reached the extruder.

Publié : 19/12/2018 9:12 pm
Peter L
(@peter-l)
Honorable Member
Re: Firmware 1.0.3 for the MMU2 unit


It is unbelievable that the biggest issue which causes every single print to fail using the MMU2 is not fixed yet. Upon filament change in multi color use, the speed setting is reset to 100% no matter what you set it in Slic3r. This may be fine with PLA, but I use only PETG so I've yet to be able to use this $300 paperweight. Awesome.

Kudos to the support team that said this would be fixed on the "next update". 👿

Are you using the print speed adjustment on the printer to set the speed?

Is there a reason you're not using the filament profile in Slic3r?

Publié : 19/12/2018 11:55 pm
Nikolai
(@nikolai)
Noble Member
Re: Firmware 1.0.3 for the MMU2 unit

Thanks for the update! Again a step forward to a better MMU2.
@josh: Independent of any bugs which are related to the speed knob and need to be fixed, I would suggest to adjust the speed settings in the Slic3r instead. I'm not using the speed knob at all and it's working fine for me.

Often linked posts:
Going small with MMU2
Real Multi Material
My prints on Instagram

Publié : 20/12/2018 5:29 am
Colin
(@colin-4)
Estimable Member
Re: Firmware 1.0.3 for the MMU2 unit


It is unbelievable that the biggest issue which causes every single print to fail using the MMU2 is not fixed yet. Upon filament change in multi color use, the speed setting is reset to 100% no matter what you set it in Slic3r. This may be fine with PLA, but I use only PETG so I've yet to be able to use this $300 paperweight. Awesome.

Kudos to the support team that said this would be fixed on the "next update". 👿

Uh, you mean this?

https://github.com/prusa3d/Prusa-Firmware/releases/tag/v3.5.1

M220 speed factor:
On multi-material printers, speed factor is currently set to 100 % before filament change by Slic3r PE. This ensures that filament change will proceed with defined speed and thus higher reliability.
There is now a possibility to save and restore speed factor on MK2.5 and MK3 printers using the following G-codes:
M220 Sxxx sets speed factor
M220 B sets backups current speed factor
M220 Sxxx B sets speed factor and backups current speed factor
M220 R restore saved speed factor
These M-codes are the same as on MK2 printers with Firmware 3.1.0 and allows Slic3r PE to backup speed factor set by the user (by rotating the knob on the printer) before filament change and then to restore is when filament change if finished. This will fix issues #1364 and #1208.

Publié : 20/12/2018 1:22 pm
Jon
 Jon
(@jon-9)
Trusted Member
Re: Firmware 1.0.3 for the MMU2 unit

I don't understand the issue with the print speed setting. I print solely in multicolor PETG and rarely have a print failure. I have many 24+ hour successful prints My only big change was to set the # cooling cycles to 4.

can someone explain the issue to me?

Publié : 20/12/2018 4:58 pm
Mirar
(@mirar)
Estimable Member
Re: Firmware 1.0.3 for the MMU2 unit

So I tried to flash this and it seems like it's now bricked and can't be flashed, not sure how I should feel about this.

Using Slic3rPE 1.41.2,

avrdude: Version 6.3-20160220-prusa3d, compiled on Nov 22 2018 at 16:13:18
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2014 Joerg Wunsch

System wide configuration file is "/tmp/.mount_Slic3rxD4hmN/usr/bin/resources/avrdude/avrdude.conf"

Using Port : /dev/ttyACM0
Using Programmer : avr109
Overriding Baud Rate : 57600
AVR Part : ATmega32U4
Chip Erase delay : 9000 us
PAGEL : PD7
BS2 : PA0
RESET disposition : dedicated
RETRY pulse : SCK
serial program mode : yes
parallel program mode : yes
Timeout : 200
StabDelay : 100
CmdexeDelay : 25
SyncLoops : 32
ByteDelay : 0
PollIndex : 3
PollValue : 0x53
Memory Detail :

Block Poll Page Polled
Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack
----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
eeprom 65 20 4 0 no 1024 4 0 9000 9000 0x00 0x00
flash 65 6 128 0 yes 32768 128 256 4500 4500 0x00 0x00
lfuse 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00
hfuse 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00
efuse 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00
lock 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00
calibration 0 0 0 0 no 1 0 0 0 0 0x00 0x00
signature 0 0 0 0 no 3 0 0 0 0 0x00 0x00

Programmer Type : butterfly
Description : Atmel AppNote AVR109 Boot Loader

Connecting to programmer: Found programmer: Id = "CATERIN"; type = S
Software Version = 1.0; No Hardware Version given.
Programmer supports auto addr increment.
Programmer supports buffered memory access with buffersize=128 bytes.

Programmer supports the following devices:
Device code: 0x44

avrdude: devcode selected: 0x44
avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.00s

avrdude: Device signature = 0x1e9587 (probably m32u4)
avrdude: safemode: hfuse reads as D8
avrdude: safemode: efuse reads as CB
avrdude: reading input file "/home/mirar/prusa/prusa3d_fw_MMU2board_1_0_3.hex"
avrdude: writing flash (19966 bytes):

Writing | ###########################avrdude: error: programmer did not respond to command: set addr
avrdude: error: programmer did not respond to command: write block
# ***failed;
###################### | 100% 1.15s

avrdude: failed to write flash memory, rc=-1

avrdude: safemode: Verify error - unable to read lfuse properly. Programmer may not be reliable.
avrdude: safemode: Verify error - unable to read lfuse properly. Programmer may not be reliable.
avrdude: safemode: Sorry, reading back fuses was unreliable. I have given up and exited programming mode
avrdude: error: programmer did not respond to command: leave prog mode

avrdude done. Thank you.

The MMU does not boot properly now...

Publié : 20/12/2018 10:28 pm
AbeFM
(@abefm)
Membre
Re: Firmware 1.0.3 for the MMU2 unit


the speed setting actually switches to a bunch of different speeds depending on the slicer settings.

it can go anywhere from 0 to 100%

https://github.com/prusa3d/Prusa-Firmware/issues/1300

this is a big bug that needs to be fixed.

I'm beyond shocked that anyone knows about it. It's been months and several versions of firmware and slicer since I first posted it.

Clearly it is something Prusa cares deeply about. It's a disaster for prints with TPU in them. There was a point where I was hoping to provide experience and data to Prusa but that's been beaten out of me. The level of commitment Prusa Research has to their MMU product makes the new SLA printer my LEAST recommended printer, after anything with an MMU on it.

Have you found anything out about how to cause/fix it? Other than selecting TPU, I've not seen a lot of influence.

I maintain an informal list of San Diego, CA 3D printing enthusiasts. PM me for details. If you include a contact email and I can add you to the informal mailing list.

Publié : 21/12/2018 7:17 pm
AbeFM
(@abefm)
Membre
Re: Firmware 1.0.3 for the MMU2 unit

In the newer firmware release, there's some talk of changing how the buttons are debounced.

I have experienced frequent misreads of the buttons, pressing the center will move left, pressing left will do a load.

Long presses and a little luck help.

Anyway, let me know if you care.

I maintain an informal list of San Diego, CA 3D printing enthusiasts. PM me for details. If you include a contact email and I can add you to the informal mailing list.

Publié : 21/12/2018 7:18 pm
Zaiden
(@zaiden)
Active Member
Re: Firmware 1.0.3 for the MMU2 unit

OK. So it seems there is some sort of "fix" for the speed settings, but I am not familiar with inserting GCODES and there are no examples on where to put this line of code. I ended up putting it all over in the Filament Settings GCODE, but it still doesn't work most of the time. The wipe tower still goes to 100%, sometimes it goes to my setting of 45%, but most of the time it resets to 100% and my prints are failing. I'm really tired of dealing with this so any help would be greatly appreciated.

Publié : 22/12/2018 2:29 am
Mirar
(@mirar)
Estimable Member
Re: Firmware 1.0.3 for the MMU2 unit

I would happily start fixing the code if I knew Prusa cared at all.

Publié : 22/12/2018 11:35 am
Page 1 / 3
Partager :