Skip to content

3.12.2 Firmware for MK3, MK3S, MK3S+, MK2.5 and MK2.5S
Compare
Choose a tag to compare
@DRracer DRracer released this 02 Mar 10:51
v3.12.2
a6eeb55
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Summary

  • Thermal model updates
  • Update on E3D Revo
  • Self Test message fixed
  • FLC procedure updated
  • List of pull requests

This is the final release of firmware 3.12.2 focused mainly on thermal model-related improvements.

Thermal model updates (MK3/MK3S/MK3S+)

Autotune/Calibration temperature

Fixed the thermal model autotune/calibration temperature value to allow real print temperatures.
Before the G-code M310 A215 F1 failed.

Check Power and Capacitance values

Power and Capacitance parameters are now checked whether they are greater than zero.

Fixed incorrect sending of ERROR: via serial

In the previous firmware release, OctoPrint would send an M112 emergency G-code and “kill” the print during a thermal model anomaly. This is now fixed. Thanks to our OctoPrint community for reporting this issue.

Consistent TM wording

During the thermal model development, the terminology shifted in meaning. We decided to use this term to have clear and consistent wording for the thermal model.

  • The LCD calibration menu Temp model cal. is now Thermal model cal.
  • Messages related to the thermal model have also changed
    We added a page at prusa.io/tm-cal (also shown during the TM calibration step in the wizard). Please read this Prusa help article for more information.

Update on E3D Revo (MK3/MK3S/MK3S+)

We would like to thank all of the community members who provided their TM calibration logs with the E3D REVO! This really helped to improve the TM development for PTC/REVO hotends.

E3D and Prusa Research have also started a task force to work on the Thermal Model for PTC/Revo hotends.

Self test message fixed

The Self test OK message was incorrectly set as an “alert” message and blocked actual alerts from being shown correctly. This has been solved.

FLC procedure updated

The message Is filament loaded? during the Wizard doesn’t timeout anymore and has to be confirmed to prevent First Layer Calibration (FLC) to continue without filament loaded.

List of pull requests

See here for more information

Assets 8
Loading