3.13.0 Firmware for MK3, MK3S, MK3S+, MK2.5 and MK2.5S

Summary

• MMU3 firmware support
• Features by the Prusa community
  • E3D Revo support
  • Meatpack support
  • Do not preheat the heatbed on load/unload
  • Features and translations
• Support for G-Code M850
• First Layer Calibration - nozzle diameter
• PrusaLink improvements
• Build environment with cmake
• Known issues

This is the final release of the firmware 3.13.0 focused on adding support for MMU3, extending the thermal model with support for Revo nozzle and several other improvements.

MMU3 firmware support (MK3S+)

The firmware for the MMU3 unit is completely new (rewritten from scratch). A detailed description of the architecture, automatic procedures, registers and many more will be described in the upcoming dev diary.

MMU3 firmware compatibility

It is important to distinguish between two types of firmware. One firmware is designed for the MMU (2S or 3) unit, the other one is for the printer. Due to major changes, both firmwares must be updated and can't be combined with any previous releases.

Compatibility:

• 3.12.2 + 1.0.6 (firmware combination valid until this release)
• 3.13.0 + 3.0.0 (firmware combination starting this release)

Running a combination of older 3.12.2 with newer 3.0.0 or newer 3.13.0 with older 1.0.6 will not work correctly due to major changes in both firmwares for the MMU (2S or 3) unit and the printer.

Combinations of older hardware like MMU2S with MK3S or MK2.5S with the latest firmware (3.13.0 and 3.0.0) should work and will be soon explained in the article about MMU3 firmware compatibility at help.prusa3d.com.

Features and improvements

The MMU3 firmware brings multiple improvements across the board. In case of an issue the firmware will try to solve the problem on its own before pausing the print and waiting for user interaction. The auto-retry feature solves a lot of minor issues with filament sensors.

All issues/errors are shown on the LCD screen. A short title shows the issue and a web link prusa.io/04xxx code for more information. Showing the FINDA, Filament sensor, tool operation and temperature helps to identify issues. Last line shows actions the user can select and selecting the double downward arrow shows more detailed offline information about the issue.

There is a continuous two-way serial communication between the printer and MMU which improves the printer “knowing” what state the MMU is. Since the printer firmware and MMU firmware need to be able to communicate, the firmware versions are checked and need to be in a compatible combination.

The MMU is by default disabled and has to be enabled in LCD menu Settings -> MMU [ON|OFF]. After a Factory reset the Wizard will run without the MMU. If you want the Wizard to test the MMU as well:

• don't start the Wizard after the Factory reset
• activate the MMU in Settings -> MMU first
• run the LCD `Calibration -> Wizard

Features by the Prusa community

We would like to thank the community for their support and additions to the code base. Thanks to their effort, this release adds more new features. Please note, that these features are maintained by its creators, therefore any suggestion for an improvement or bug should be reported directly to them.

The same should be done for languages translated by the community. Only in case the person responsible for translating the given language does not respond for a longer period, contact Prusa.

We would like to apologize for the delay in adding the community pull requests to the main firmware branch. We had reached the capacity of the resources on the Einsy board and needed first to create space for new lines of code.

Community E3D Revo support (MK3/MK3S/MK3S+)

Thanks to community members and E3D, we were able to provide a source code base for the community and other 3rd party hotends. As a result, if your printer is modified with E3D Revo hotend, it should be now capable of passing the thermal model calibration process and react correctly to any thermal related issues.

Kudos to users @alexiri, @kromeninja, @ulab, @JWvP, @snafu1282, @matthiazzz, @sdh2, @davejhilton, @D-an-W, @MaroonOut09 and others helping to solve the issues #4105 and #3636.

Please flash the E3DREVO_.hex files on your modified printer. You can find these in the e3d_REVO_.zip file. Read the instructions how to add a new 3rd party hotend.

Community Meatpack support

Thanks to @scottmudge providing this well prepared and detailed pull request. For more information and questions, please see here and here.

Community Do not heat bed on load/unload

Thanks to @Panayiotis-git for this pull request. It speeds up some operations where the heating of the bed isn't needed. For more information and questions, see here. By default this feature is disabled with the Bed being heated as in previous firmware. It can be changed in LCD menu Settings -> Hbed on load [YES|NO]

Support for G-code M850

A support for G-code M850 to read and modify sheet labels and offsets. For more information see the pull request.

First Layer Calibration - nozzle diameters

Thanks to @GilesBathgate, the Prusa firmware built-in First layer calibration (FLC) now works for multiple nozzle sizes. Please ensure that you have the correct nozzle size selected in LCD menu Settings -> HW setup -> Nozzle d. [0.25|0.40|0.60|0.80] with 0.40 as default.

PrusaLink improvements

PrusaLink was improved for this release. To learn how to use PrusaLink on your Prusa i3 MK2.5/S and MK3/S/+ please checkout here. For more information about the project visit its GitHub repository.

Build environment with cmake

With the next release we will switch completely to build the firmware using cmake. The build is already prepared and can be used. It can be used in FW 3.13.0. For more information visit.

The build with Arduino IDE is still possible but no longer supported and it will be removed in a future firmware release.

Known issues

During final testing of the FW 3.13.0 and MMU3 3.0.0 developers discovered a rare issue, which we will address in a future release. In case the MMU print stops with an error and needs user interaction a power panic will cause issues to recover from the power panic.