[Sticky] 3.13.2 Firmware for MK2.5 and MK2.5S
3.13.2 Firmware for MK2.5 and MK2.5S
- Power Panic improvements
- MMU firmware improvements
- Submitted by the Prusa community
- User interface improvements
- Other Improvements
- Bug fixes
This is the stable release of firmware version 3.13.2, with a primary focus on Power Panic, Multi-material, and several other improvements. While most of the features and fixes mentioned below were already included in the 3.13.2-RC1 release, we recommend updating to this firmware version.
Power Panic improvements
The primary focus of this release is to improve the Power Panic behavior, especially after the introduction of the new MMU3 firmware and the error states reported on the LCD of the printer.
Multi-material prints tend to be very long, so any sort of power failure can put the quality of the print at stake.
Any function that needs user interaction will pause the printer and move the hotend away from the print itself. This action prevents the hotend from "scorching" the print and creating blobs. It also creates space to investigate the reported issue or perform the requested action. Previously, the positions were saved to RAM, but these were lost during a power failure or a reset of the printer. This means the printer would try to continue with the print, but at the wrong height and wrong position. This caused mid-air extrusions, the creation of blobs, and sometimes missing extrusions.
This issue has now been resolved. All values in RAM (volatile) are saved to EEPROM (permanent) during a power panic which ensures a better power panic recovery during the MMU prints.
Power Panic recovery was tested for:
- Paused print ✔️
- MMU Error codes ✔️
- After a crash ✔️
- Filament runout ✔️
- Filament change ✔️
Note: Power panic works only with SD card prints!
MMU firmware improvements
Based on the feedback from the community, this release brings new features allowing you to adjust parameters like idler sensitivity or bowden length.
Added Tune menu for IDLER|SELECTOR CANNOT HOME
MMU2S users have reported that, despite careful hardware inspection, some units struggle to home the Idler reliably. Although MMU Firmware 3.0.0 has already offered an option to adjust the Idler's homing sensitivity by modifying the StallGuard threshold, some users have encountered difficulties changing this value.
Therefore, in case the MMU reports any of the “Idler and/or Selector cannot home” errors, there is a new option displayed on the screen called "Tune" which allows to set the threshold value in a user-friendly way. Please note that the allowed range of values has been limited to prevent users from accidentally setting extreme values.
Bowden length register added
With the MMU FW 3.0.1, it is possible to set a custom front PTFE tube length (default length: 360 mm). This has been implemented at the request of our community members who pointed out that there are various configurations for the filament setup and there's a need to set a longer PTFE tube length. We limited the length to 1000 mm since longer tubes might introduce additional issues - we strongly recommend keeping the tube shorter rather than at the maximum allowable length.
This new register can be used to tweak the fast loading and unloading distance in case of non-standard installations. The register is persistent in the MMU's EEPROM. Unlike the previous generation of FW 1.0.x, the register now reflects the actual real length of the tube, not including any additional distances to the pulley or drive gears.
Note: If you choose to increase the PTFE length for your custom setup, you must verify whether the unloaded filaments fit inside the provided buffer. If they do not, you will need to construct your own buffer with sufficient space.
MMU USB product string updated
In the new firmware version 3.0.0 or later, which now supports both MMU2S and MMU3, the USB product string has been updated to "Original Prusa MMU unit 🐑." This change does not impact any of the MMU's functions.
Submitted by the Prusa community
We have implemented several improvements submitted by the active users from the Prusa Community. Many thanks to everyone involved.
Enable/Disable FSensor using G-codes
This release brings support for enabling and disabling filament sensor (FSensor) using G-codes
M405/M406 submitted by @Commod0re
Support for M118 G-code
M118 G-code was submitted by @RoboMagus see here. The M118 G-code allows the sending of a message (Serial print) to hosts like OctoPrint and PrusaLink to trigger actions, etc. See the pull request for more information.
Improved G-code M914 & M915 control (stealth mode)
In addition to enabling M914 and 915 by default, these codes have been expanded to allow for more flexible control of the current printing mode via G-code (such as enabling crash detection selectively during portions of a print).
By default, changes issued are temporary (lost on printer reset), but by supplying the 'P' parameter, the change can be saved to EEPROM and made persistent. Alternatively, supplying the
R parameter will revert any current temporary changes in favor of the saved value. Finally, the menu has been updated to provide visual feedback when a temporary override is in place via G-code
User interface improvements
Jump to 200°C/50°C in Temperature menu
This release brings a new behavior when users manually set the temperature in the LCD Menu -> Settings -> Temperature menu. Previously, both nozzle (hotend) and heatbed temperatures started at 0 °C, and users had to rotate the knob clockwise to increase the temperature incrementally by 1 °C until the target temperature was reached.
However, since most filaments require printing temperatures above 200/50 °C (nozzle/heatbed), we have made an adjustment. Now, starting at 0 °C, a single clockwise rotation will increase the nozzle temperature to 200°C instead of just 1 °C. The same change applies to setting the heatbed temperature (0 °C to 50 °C). This modification allows users to reach their target temperature more quickly.
Similar behavior is applied to the print fan; when turning the knob clockwise from 0, the speed is set to 127, which corresponds to 50% of the RPM range.
If you prefer to revert to the original behavior, simply rotate the knob counterclockwise first, and then you can use it in the same way as before.
Language Update information shown in the first row
Simplified variant names
In the source code, we shortened the variant names to the minimum needed, as all Original Prusa MK2.5/S and MK3/S/+
- use 1.75mm filament
- use E3d v6 style hotends
- All MK3/S/+ use the same controller board
- Exceptions are
- MK2.5/S may have a RAMbo10a or a RAMbo13a board which have different pinouts
- 3rd party modification
We optimized the source code and freed up some space for future features.
Update development tools
- Fixed a false FINDA runout event at the start of an MMU print on MK3S printers #4332 (Kudos goes to @mmoraes80, @sruggier and @Braddg for helping us narrow down the problem and verify the fix)
- Fixed an issue with Preheat heating for longer than intended #4338 (Kudos to @linzwatt for reporting the issue and to @sarusani for fixing it)
- Fixed an issue where some users could not run first layer calibration because the LCD was stuck rendering the same fullscreen message repeatedly (Kudos to @sarusani for helping us test and fix this)
- Fixed an issue where a print could be started while the printer is still loading or unloading filament, triggering a firmware crash. #3564
- Previously in FW 3.13.2-RC1 reported FAN check issue has been fixed.
When downloading, please pay attention to the files and make sure you download the correct version for your machine.
Please report any bug here:
How to flash the firmware:
Shane (AKA FromPrusa)
RE: 3.13.2 Firmware for MK2.5 and MK2.5S
It seems this firmware is not compatible with the MMU2S?
MMU2S unit with firmware 3.0.0 and up - The main concern is different system voltage compared to the MK3S+ (12 vs. 24 V). The firmware is not optimized for this configuration.
"Not optimized"? I tested the firmware and it reports the MMU2S needs to be on 3.x firmware. Is the 3.x firmware for MMU2S on the MK2.5S supported or not? Or is the 3.12.2 firmware + 1.0.6 the latest supported combination?
RE: 3.13.2 Firmware for MK2.5 and MK2.5S
Is the 3.x firmware for MMU2S on the MK2.5S supported or not? Or is the 3.12.2 firmware + 1.0.6 the latest supported combination?
I'm also trying to find out exactly this. Anyone?