Notifiche
Cancella tutti

3.12.0 Firmware for MK3, MK3S, MK3S+  

Pagina 1 / 2
  RSS
Same Old Shane
(@same-old-shane)
Utenti Admin
3.12.0 Firmware for MK3, MK3S, MK3S+

Greetings one and all;

We are happy to announce the release of our 3.12 final release for our MK3 series of printers (MK3, MK3S, and MK3S+). Please read the updates and you will find the download links at the bottom of the post. 

Summary

  • New thermal model protection
  • Nozzle change menu
  • NylonPA sheet profile added
  • Arc interpolation features G2/G3
  • UI improvements and fixes
  • New build environment
  • New language scripts
  • XYZ calibration updates
  • New language scripts
  • Updated translations
  • Farm mode
  • Bug fixes
  • Known issues

This is the final release of firmware 3.12.0. This changelog is a summary of the previous releases 3.12-beta13.12-RC1 and 3.12-RC2. The main focus is on the new thermal model feature for improved safety.

ATTENTION: Please note the thermal model requires calibration, which takes about 12 minutes to complete. It is recommended to perform the calibration in order for the feature to work properly.

New thermal model protection (MK3/MK3S/MK3S+)

History of development

For the past several months, we’ve been hard at work to bring all thermal-related safety features to a whole new level. The 3.12-BETA firmware was the first public release of the new Thermal model protection.

The firmware is now capable of detecting unexpected heating issues of any sort and stopping heating quickly (in 10-12 seconds) to avoid potential damage to your 3D printer. This encompasses cabling issues, an incorrectly working heater block, thermistor faults and external factors too (draft, blobs forming on the extruder, etc.).

Check our detailed dev diary blog article explaining all the details behind this new feature.

Protection is always active

The thermal model protection increases the overall security of the heating system and starting firmware 3.12.0, will be turned on by default. Since every printer is slightly different it is necessary to calibrate the printer first.

Calibrate the temp model on your printer

In case the printer is updated from any firmware prior to 3.12.0, or a factory reset is performed, the thermal calibration is considered invalid and must be executed again! If this process is skipped by the user, the printer will beep and possibly pause more often.

Temp model calibration is available in the LCD menu Calibration -> Temp model cal. as well in the initial setup Wizard.

  • The calibration takes approximately 12 minutes and for the duration, you can’t give the printer any other commands.
  • During the calibration the LCD status line shows which step it is going through at the moment.
  • As soon as you see ”Original Prusa MK3S” on LCD, it is finished.

Please re-run the temp model calibration to ensure the best performance and minimize the temp model warnings,

  • when you change:
    • the nozzle
    • heater block
    • the heater cartridge
    • the hotend thermistor
    • the print fan
    • fan shroud
    • complete hotend assembly
  • When you add a silicone sock
  • When you move the printer to a different environment (enclosure, etc.).

Printer behaviour

While preheating:
In case the algorithm detects any issue, the printer starts beeping. If the problem persists for about 10 seconds, the heating is stopped and the message “Thermal anomaly” is displayed. The printer continues beeping (calls for user attention).

While printing:
Similar to preheating, a discrepancy between the model and thermistor readings causes the printer to first beep and display “Thermal anomaly” and after about 10 seconds, the print is paused. The nozzle is turned off and the printer continues beeping.

Please note, that once a “Thermal anomaly” is detected the printer “locks” itself to prevent any possible damage and it is necessary to perform certain actions. See more information below.

Added Clear TM error

To “unlock” the printer in case a “Thermal anomaly” is detected, there is a new option in the menu LCD menu -> Clear TM error to temporarily clear/acknowledge the issue. As this is only a “temporary” solution proper calibration is recommended. In case the temp model calibration doesn't solve this, please contact Prusa support or open a GitHub issue.

Modded printers

In case your printer is equipped with third-party components (heating or cooling), the thermal model might not be working properly. The developers are trying to expand support, but a large amount of data is needed to calibrate the model properly. Internally we have tested and analyzed over 150 000 OEM heaters and thermistors.

We are aware that third-party nozzle E3D REVO is not working correctly and we have an active GitHub issue where users reported their values. At this moment we don’t have enough data to analyze these, so please if you are a REVO user share your log files there.

Turning the thermal model protection off is not recommended, however, at your own risk it can be disabled via the serial line by sending G-code M310 S0 followed by M500 to make it permanent.

Feedback report

Please report positive feedback on the thermal model (with an ✔️ at the end of the release notes). In case you run into issues, start a New issue

  • The report should contain at least following informations
    • Reproducible: Yes/No
    • Printer model: MK3/S/+ stock or modified
    • Modifications: Example E3D Revo or Copper block or different Fan shroud (with link)
    • If a specific print causes issues. Please attach the printed model
    • Try to add a serial log of the print failing.

Nozzle change menu

We added the necessary Nozzle change menu option under Settings -> HW Setup which disables the temp model temporarily. Please read Changing or replacing the nozzle (MK2.5S/MK3S/MK3S+) before you start. Please also keep in mind that changing the nozzle will need the first layer adjusted, as you will never be able to tighten the nozzle at exactly the same height as the previous one. We made this change thanks to the feedback from our community testers (see #3719).

NylonPA sheet profile added

The list of sheet profiles is now extended with the “NylonPA” option. Please note that this is just a name of the profile and there is no difference to other stock profiles (Smooth1, Texture1,...).

Since the list of profiles is limited, the “NylonPA” is replacing the current profile “Satin2”. In order to see this change, a Factory reset is required. Before you do so, please write down the “Live Adjust Z” values for all the calibrated sheets.

Once a Factory reset is performed, the default list is:

  • Smooth1
  • Smooth2
  • Texture1
  • Texture2
  • Satin
  • NylonPA
  • Custom1
  • Custom2

Arc interpolation features G2/G3

Until now, whenever the printer was supposed to “draw” the shape of an arc, the internal logic of the firmware interpreted and printed it as a segmented line. In most cases, this will be unnoticed and the line will look rounded, but in some scenarios, this algorithm wasn't working properly.

Community member @FormerLurker proposed a solution, which was tested internally by our testing department and they confirmed it works as expected. The printer is now capable of printing a smooth arc without any noticeable edges. This firmware release incorporates this pull request #2657 and we would like to thank FormerLurker for his amazing work.

In case you want to learn more about this feature, please visit #2657.

Additionally, this release also fixes long-standing issues regarding G2/G3 moves. The following things now work properly when executing G2/G3 commands:

  • Pause/resume from the LCD or G-code
  • Crash detection
  • Filament runout
  • Power Panic
  • Fan errors

UI improvements and fixes

There are multiple fixes and improvements across the user interface aiming to improve the overall experience.

Firmware flashing

While flashing the firmware with PrusaSlicer there are two parts. The first part is, flashing the firmware into the CPU memory, and the second part is flashing languages in the external (xflash) memory. Starting with this firmware the second part is now displaying an extra LCD message Upgrading xflash Do not disconnect!.

Status line (M117)

This firmware release improves behavior when the M117 message was in some scenarios permanently overwritten with system messages (for example when M117 was immediately followed by the M601 / G4).

Please note that your M117 message should be kept within 20 characters, any excess characters will be truncated. We would like to thank @RodKimmell @GWdd @daBernd for reporting the issue.

Firmware version on boot

The firmware version is now displayed on the startup screen

Fixes

  • The “back arrow” sign was added to the Preheat menu.

  • Don't prompt "New firmware version available:" if disabled in Settings. Until now a warning was always displayed when G-code M115 with the latest firmware version (e.g. M115 U3.11.0) was sent and this value was higher than the current firmware version installed. The Settings-> HW Setup -> Check -> Firmware [None] now suppresses the message below even if the M115 is included in the G-code.

  • Starting this release the UI ignores the knob long-press action if not allowed. Thanks to @Panayiotis-git for providing the solution.
  • In case the user stops the print, the remaining time is cleared. Thanks for reporting this issue @Stego72

New build environment

The build environment for all 8-bit firmware versions was updated from Arduino IDE 1.8.5 to 1.8.19 with GCC 7.3, which saved 1+ KB of resources. This is an important change. Older Arduino IDEs and/or GCC versions may not compile the code anymore from now on.

XYZ calibration updates

A message displayed on the screen has been updated from It will take up to 12 mins. to It will take up to 24 mins. as some users reported that their printer needed more time. We added some status information during the XYZ calibration to give visual feedback that the printer is still busy.

New language scripts

The new language scripts revealed missing translations hidden in the source code but also an obsolete one. The translation and post-processing process has not only improved for the developers but also for the translators.

Updated translations

We would like to thank the community members for updating translations with new texts. In case you want to join and help translate the firmware to your language, please visit the following article Community translations.

Based on the feedback from our translators:

  • The translation “.po” files can and should now contain diacritics which will be automatically replaced.
    • This should improve the spell checks in different languages and hopefully make it easier for the translators.
    • At this moment we are still limited by the LCD screen only to show [aA-zZ] and [äöüß] characters.

Farm mode

The Farm mode is used internally on the Prusa farm and will be from now available in a separate build and only in English. We have decided to remove it from the multi-language versions to save resources for other features.

Bug fixes

  • Parts of the firmware used “Extruder fan”, while the correct name is “Hotend fan”. This is now unified across the entire code base.
  • Some SD cards caused issues, the firmware should handle them correctly from now on.
  • The long button press wasn’t supposed to be active in some locations, this has been fixed now.
  • Minor SD card issue in FARM mode fixed. Sorting and long filenames have not been shown correctly.
  • Fixed µm being shown incorrectly in languages other than English.
  • M300 S0 pause like Marlin.

Known issues

A feature detecting the filament sensor hardware version is currently not working. Printing process isn't affected, however if the filament sensor is not working properly, the printer is unable to verify it. The devs are aware of this issue and a fix will be provided soon.

 

Please report any bug here:
https://github.com/prusa3d/Prusa-Firmware/issues

Download Link:
https://github.com/prusa3d/Prusa-Firmware/releases/tag/v3.12.0

How to flash the firmware:
https://help.prusa3d.com/en/article/firmware-updating-mk3s-mk3s-mk3_2227

Shane (AKA FromPrusa)

Postato : 11/01/2023 8:37 am
vhubbard hanno apprezzato
TheOldKenobi
(@theoldkenobi)
Active Member
RE: 3.12.0 Firmware for MK3, MK3S, MK3S+

Firmware is trash, im only getting error: Thermal Anomaly!!!!

Postato : 11/01/2023 11:16 pm
Tu hanno apprezzato
PlanetV3D
(@planetv3d)
New Member
RE: 3.12.0 Firmware for MK3, MK3S, MK3S+

Having the same issue. 

Postato : 12/01/2023 5:55 pm
Tu hanno apprezzato
Zbigniew Trzepizur
(@zbigniew-trzepizur)
Trusted Member
RE: 3.12.0 Firmware for MK3, MK3S, MK3S+

 

Posted by: @theoldkenobi

Firmware is trash, im only getting error: Thermal Anomaly!!!!

You won't fool me, you're not the real Obi-Wan. I remember him being respectful and considerate and you're not like that.

Postato : 13/01/2023 9:55 am
TheOldKenobi
(@theoldkenobi)
Active Member
RE: 3.12.0 Firmware for MK3, MK3S, MK3S+

Never said im the real Kenobi 😉

Postato : 13/01/2023 11:43 am
Zack
 Zack
(@zack)
New Member
RE: 3.12.0 Firmware for MK3, MK3S, MK3S+

Receiving a Thermal Anomaly statement and can't calibrate.

Postato : 13/01/2023 2:37 pm
Ian Harris
(@ian-harris)
Eminent Member
RE: 3.12.0 Firmware for MK3, MK3S, MK3S+

I have to say the reports of "Thermal Anomaly" problems don't inspire me to install the 3.12 firmware.

Would be interesting to hear from people who have no problems installing v3.12.

--

Ian

Postato : 13/01/2023 4:32 pm
TheOldKenobi
(@theoldkenobi)
Active Member
RE: 3.12.0 Firmware for MK3, MK3S, MK3S+

You only get this problem if you have moded your printer. My mod is a Revo 6, thats why I get this error. 

Postato : 13/01/2023 4:37 pm
Zack
 Zack
(@zack)
New Member
RE: 3.12.0 Firmware for MK3, MK3S, MK3S+

I have the same mod. Makes sense now.

Postato : 13/01/2023 4:43 pm
PlanetV3D
(@planetv3d)
New Member
RE: 3.12.0 Firmware for MK3, MK3S, MK3S+

Ahhhh yeah, thats makes sense. I kind of figured it was something like that. I also run a Revo 6. 

Postato : 13/01/2023 5:53 pm
cphoton
(@cphoton)
Eminent Member
RE:

No issues on my end so far - using 0.6mm DiamondBack nozzle with silicone sock. Also using ArcWelder plugin w/OctoPrint to try to leverage improved arcs support.

EDIT: I would suggest checking out GitHub issues as there are workarounds for folks using Revo nozzles and for folks upgrading from RC2.

Posted by: @ian-harris

I have to say the reports of "Thermal Anomaly" problems don't inspire me to install the 3.12 firmware.

Would be interesting to hear from people who have no problems installing v3.12.

--

Ian

 

Postato : 13/01/2023 6:10 pm
Ian Harris
(@ian-harris)
Eminent Member
RE: 3.12.0 Firmware for MK3, MK3S, MK3S+

Well, tried v3.12 and guess what? "Thermal Anomaly".

The printer is a standard Prusa assembled i3 Mk3S with no modifications.

The first part of the calibration seems to work:-

TM: initial C est. (looking for 230C ir looks like)

TM: cool down <50C (cooling down to <50C)

TM: refine C est. (target again seems to be 230C)

As the temperature reaches 224-224C the fan goes full speed and the temperature starts to fall: Thermal Anomaly.

Re-installed v3.11.

--

Ian

Postato : 14/01/2023 3:19 pm
TheOldKenobi
(@theoldkenobi)
Active Member
RE: 3.12.0 Firmware for MK3, MK3S, MK3S+

Thats why I said trash firmware. You have to wait a couple of months for new firmware and than you get this shit!!!! 

Postato : 14/01/2023 3:21 pm
uh
 uh
(@uh)
Eminent Member
RE:

It should be possible to turn of the thermal model protection by sending G-code M310 S0 followed by M500

That's not working for me.  I get the message that the calibration wasn't done on each power on.

Reverted back to version 3.11.0 

Questo post è stato modificato 1 year fa da uh
Postato : 15/01/2023 2:21 pm
Crab
 Crab
(@crab)
Reputable Member
RE: 3.12.0 Firmware for MK3, MK3S, MK3S+

Can 3.12.x  be installed totally by OctoPi/Print using the firmware update plug-in? (as I've done with past 2 firmware updates)

Although I don't plan to update to this until much more "test of time" has passed.

Postato : 15/01/2023 3:05 pm
tachijuan
(@tachijuan)
New Member
RE: 3.12.0 Firmware for MK3, MK3S, MK3S+

I upgraded as well. Stock MK3S running with OctoPrint. First attempt at a print, I got a thermal runaway error after heating but before bed calibration. The second time It was well into layer 4 or 5 of my print and same thing. OctoPrint graph shows no thermal issues. Downgraded and now my print is working again and honestly, looking cleaner than with 3.12.0. Running 3.11.0 now.

Postato : 15/01/2023 9:07 pm
Same Old Shane
(@same-old-shane)
Utenti Admin
Topic starter answered:
RE: 3.12.0 Firmware for MK3, MK3S, MK3S+

Hello all;

just a little bit from the release notes; 

Modded printers

In case your printer is equipped with third-party components (heating or cooling), the thermal model might not be working properly. The developers are trying to expand support, but a large amount of data is needed to calibrate the model properly. Internally we have tested and analyzed over 150 000 OEM heaters and thermistors.

We are aware that third-party nozzle E3D REVO is not working correctly and we have an active GitHub issue where users reported their values. At this moment we don’t have enough data to analyze these, so please if you are a REVO user share your log files there.

Turning the thermal model protection off is not recommended, however, at your own risk it can be disabled via the serial line by sending G-code 

You can go to that github site and submit your log files to help create a fix.

If you are having issues with the new firmware, you can either submit a ticket via github (link in the article) which goes to the devs, or you can contact our support department ([email protected] or use the chat opttion from the main site) to see what the issue might be. I understand people can get frustrated, but saying something is bad without any information doesn't help to fix and improve things. 

Shane (AKA FromPrusa)

Postato : 16/01/2023 8:59 am
Ian Harris
(@ian-harris)
Eminent Member
RE:

I can understand a lot of work has gone into the v3.12 firmware and a lot of testing as well, likely on many different versions of the hardware, but, my initial post was trying to find if there were people who had no problems installing v3.12 firmware (I don't know how big the beta test pool is), as it seems like the majority of posts were from people who encounter problems and there may have been many people who updated with no problem at all. 

I've opened an issue on the prusa3d/Prusa-Firmware github about the problem I've encountered.

The posts I have seen were from people with some sort of modification to the printer, whereas my printer is a standard Prusa assembled printer from 2020 with no mods.

Postato : 16/01/2023 10:51 am
Same Old Shane
(@same-old-shane)
Utenti Admin
Topic starter answered:
RE: 3.12.0 Firmware for MK3, MK3S, MK3S+

I can understand a lot of work has gone into the v3.12 firmware and a lot of testing as well, likely on many different versions of the hardware, but, my initial post was trying to find if there were people who had no problems installing v3.12 firmware (I don't know how big the beta test pool is), as it seems like the majority of posts were from people who encounter problems and there may have been many people who updated with no problem at all. 

I've opened an issue on the prusa3d/Prusa-Firmware github about the problem I've encountered.

The posts I have seen were from people with some sort of modification to the printer, whereas my printer is a standard Prusa assembled printer from 2020 with no mods.

Nope, your fine. Reporting it to the github issue system is the best way as that goes directly to the developers. What I said was a broad statement and not directed towards anyone. 🙂 

Shane (AKA FromPrusa)

Postato : 16/01/2023 2:54 pm
fuchsr
(@fuchsr)
Famed Member
RE: 3.12.0 Firmware for MK3, MK3S, MK3S+

I have Dragon hotends on my printers and have not experienced the thermal anomaly issue myself. Having said that, it does make me concerned that such a feature that has the potential to seriously affect many users has been rolled out without a proper way to disable it, if needed. I saw the M310/M500 procedure and was happy that Prusa supported that option but from recent reports it seems it still leads to requests for calibration on reboots. 

Postato : 16/01/2023 5:45 pm
Pagina 1 / 2
Condividi: