Skip to content

3.12.1-RC1 Firmware for MK3, MK3S, MK3S+, MK2.5 and MK2.5S

Pre-release
Pre-release
Compare
Choose a tag to compare
@3d-gussner 3d-gussner released this 17 Jan 16:56
· 2226 commits to MK3 since this release
54a3c83

Summary

  • Restore correct RPM for fans
  • Set the calibration state when running M310 A
  • Non responding MMU2S fixed
  • Max Z-coordinate during Nozzle Change
  • MK2.5 beeping after Factory reset

This is the first release candidate of firmware 3.12.1 focused on bug fixes and small improvements.

Restore correct RPM for fans

In case of a Temp model error both fans spin at full speed to cool down the nozzle as fast as possible. In firmware 3.12.0 the fans kept spinning at 100 % RPM even after the TM error was cleared. This has been fixed now and the fan speeds are regulated based on the current temperatures.

Thanks to our community members @gregsaun, @Aldebaran91, @arekm, @matthew-humphrey reporting the issue.

Set the calibration state when running M310 A

Calibrating the Thermal model using the G-code command M310 A F0 didn’t set the TM calibration state correctly. This is now fixed and calibration stored as expected.

Kudos to our community members @arekm, @FrHePo and @gregsaun for reporting this issue.

Non responding MMU2S fixed

Firmware 3.12.0 accidentally introduced a bug, where the MMU2S unit might stop responding in case of an error. For more details, see issue #3742. This is now fixed and the unit will work as expected.

We would like to thank our community members @RPospisil, @ursius2020, @E-Extrude, @Hauzman, @Mirarkitty and @3dprintandpaint for reporting this bug and retesting the fix.

Max Z-coordinate during Nozzle Change

In case the “Nozzle Change” feature is used, the printer will raise the extruder to its max Z-coordinate value making the nozzle exchange easier.

This change was done based on the request from our community member @laskr1999.

MK2.5 beeping after Factory reset

Some users have reported that MK2.5 and MK2.5S printers keep on beeping after the Factory reset is performed. This release fixes the issue.

Kudos @cjshaker for reporting this issue.