-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Thermal Anomaly 3_13_1 MK3S+ #4431
Comments
The github for the Mk3 firmware is located here https://github.com/prusa3d/Prusa-Firmware/issues This section is for Prusa Slicer issues. |
I've had a similar problem with a Revo hot-end but I also can't run the terminal model calibration |
Just turn it off with gcode M310 S0 and M500 for save. |
I noticed that a Thermal Cal. When using a housing (Prusa Enclosure, etc.), different values are written into the EEPROM (Cold Enclosure, warm Enclosure), which then leads to the THERMAL ANOMALY error. This means that values from the HOTEND and the surrounding area are taken into EEPROM. I'm not sure whether this can be updated with future firmware updates or at least that external factors such as ambient temperature don't play a role. PS. Another thing I noticed is when you use Thermal Cal. in the warm housing, the ambient temperature values are then saved in the EEPROM. When starting a new print in the cold housing, the THERMAL ANOMALY error will occur again until the temperature reaches the previous Thermal cal. measured value again. The same thing happens the other way around (Cold Housing -> Thermal Cal.) For the moment the best option to users that are using a Enclosure with the Revo Six is like @cqeta1564 say to turn off the termal model calibration with M310 S0 and M500 |
@acothebraco As the EINSY Ambient thermistor is used as a base for the Thermal model cold and warm TM cal may cause your reported issues. Can you please measure the reported ambient temperature and place an additional thermistor near the einsy box/ in enclosure?
It would be also great if you could provide detailed Thermal Model calibration data when executed in cold and in warm enclosure.
We suspect that the Another potential issue is that the cold air while part cooling causes the TM errors (when TM cal was done when warm) as it draws more thermal heat from the heat block (thermistor) than calculated during TM calibration. And vice versa. |
Hello @3d-gussner Thank you for the Mail. I tired the steps that you asked for and now I provide the information to you in hope that we can found a solution for the problem. Just for your information, since I deactivated the Thermal Protection I don´t have any error messages. The Prints are also very fine. The pictures attached below are in the same order like the output from Terminal. Cold Printer: T:31.9 /0.0 B:30.2 /0.0 T0:31.9 /0.0 @:0 B@:0 P:0.0 A:37.3 Preheating for Print Prusament PETG Recv: T:240.2 /240.0 B:84.7 /85.0 T0:240.2 /240.0 @:28 B@:52 P:0.0 A:42.2 Printing Calibration Cube Prusament PETG Recv: T:249.8 /250.0 B:90.1 /90.0 T0:249.8 /250.0 @:58 B@:73 P:0.0 A:45.4 Printing Calibration Cube Prusament PETG after 15min. Recv: T:249.8 /250.0 B:90.0 /90.0 T0:249.8 /250.0 @:55 B@:79 P:0.0 A:49.7 End of the Print Recv: T:249.2 /250.0 B:89.9 /90.0 T0:249.2 /250.0 @:66 B@:84 P:0.0 A:52.9 Thermal Model calibration Data attached in the .txt File |
@acothebraco Thanks for the detailed testing, very appreciated. Your Enclosure thermistor temp vs Einsy Ambient temp values:
As we can see the |
Thank you for the Information. I will wait for a solution or ist it maybe better to put the Einsy board outside of the Prusa enclosure? |
Putting the EINSY outside the enclosure will not fix the issue as the TM relays on the EINSY Ambient temperature as a basis to compare the TM calculated values. |
Ok than I leave temporary the TM off and when a fix in the future firmware will be ready that will fix the problem. Thank you |
@acothebraco I understand that you disable the TM, but glad you said "temporary". 🤞 We find a good solution for the TM in an enclosure. |
Thank you again. I´m proud and happy every time with the Prusa Support. keep the good work. Best Regards Aleksandar |
@3d-gussner any news about a fix? I’m now on the way to upgrade my MK3S+ to the MK3.5. Maybe the THERMAL ANOMALY problem will be solved with the upgrade with the new xBuddy Board? |
@acothebraco The MK3.5 and all other buddy firmware based printer don't have the Thermal protection thermal model yet. |
Thank you for your contribution to our project. This issue has not received any updates for 60 days and may be considered "stale." If this issue is still important to you, please add an update within the next 7 days to keep it open. Administrators can manually reopen the issue if necessary. |
This issue has been closed due to lack of recent activity. Please consider opening a new one if needed. |
I have a stock Mk3 for 7 years. Since 3.14 upgrade I have been getting THERMAL ANOMALY message regularly but intermittently. In looking at the temps, the Nozzle and Bed temps are rock solid at the expected values. I have never had this message before. How do I diagnose the source? |
@brucec87 What was the previous firmware you were using? Did you run the Calibration -> Thermal model cal.? User have found
|
Description of the bug
With Firmaware 3_13_1 the Nozzle get "Thermal Anomaly" on my MK3S+
It's not possible to do a PID-calibration.
Works fine with firmware 3_11_0 but now newer that that.
I use original Prusa Parts so no mods.
Project file & How to reproduce
no file
Checklist of files included above
Version of PrusaSlicer
2.6.1
Operating system
Windows 10
Printer model
Prusa i3 MK3S+
The text was updated successfully, but these errors were encountered: