Notifications
Clear all

Thermal anomaly on firmware 3.12.2  

Page 1 / 3
  RSS
Kent Sandhus
(@kent-sandhus)
New Member
Thermal anomaly on firmware 3.12.2

I have a problem with my brand new Prusa mk3s+ it sometimes beep and write thermal anormaly, but it prints perfectly

Posted : 23/03/2023 10:47 pm
Diem
 Diem
(@diem)
Illustrious Member

It's sensing transient events, perhaps a draft, and recovering before they become a problem.

If this persists try recalibrating.

Cheerio,

Posted : 24/03/2023 12:01 am
karl-herbert
(@karl-herbert)
Illustrious Member
RE: Thermal anomaly on firmware 3.12.2

A well-known and often discussed problem if you are running 3rd-party parts . Prusa writes on this matter:

"In case you are running 3rd-party parts like the Revo hotend, the thermal model will report errors because it needs to be trained on a large set of samples. We welcome anyone who’s willing to help us with testing. Please provide log files in GitHub issue. For now, you can disable the Thermal Model if you’re running the Revo and you’re certain that your printer is working fine. Connect to your Printer via Pronterface and send G-code M310 S0 followed by M500 - then you can continue using the firmware with third-party parts."

If nothing has been changed on the printer and the error still occurs, I would contact the Prusachat.

wbr,

Karl

Statt zu klagen, dass wir nicht alles haben, was wir wollen, sollten wir lieber dankbar sein, dass wir nicht alles bekommen, was wir verdienen.

Posted : 24/03/2023 12:33 am
barjammar
(@barjammar)
New Member
RE: Thermal anomaly on firmware 3.12.2

Hi Diem,

I just reassembled and then upgraded firmware to 3.12.2 on my Prusa I3 Mk3S but I'm getting a temperature calibration error.  Your discussion is way above my head and this error is just a time-waster as far as I can see.  Is there better information for me so I can stop it?  There is nothing special or new on my printer.

iPhone snap of error message and ambient temperature in cabinet

Meantime I'll see if they have time to chat at support.

Best Wishes

Barry Marshall (Perth Western Australia).

Posted : 24/03/2023 9:04 am
Diem
 Diem
(@diem)
Illustrious Member

Is this a kit or a preassembled machine?

If the problem persists when the printer is protected from ramdom breezes then it might be a loose connection between the thermocouples and the Einsy.

Prusa Chat should be able to help.

Cheerio,

Posted : 24/03/2023 5:48 pm
M.Lemley
(@m-lemley)
New Member
RE: Thermal anomaly on firmware 3.12.2

Hi Karl,  I just updated my 3.12.2 yesterday and I am running a REVO 6.   I am using Octoprint and I tried the M310 S0 then the M500.  No luck still has the same error.  I rolled back to 3.11.0 and back in operation.  I think I will stay at this revision for a while and just monitor my temp with other methods. 🙂  I assume the (0) in S0 is numeric?  That is what I used.

Posted : 28/03/2023 6:05 pm
karl-herbert
(@karl-herbert)
Illustrious Member
RE:

Thanks for the information! I would urgently forward the problem to Prusa or github. Probably several more people have the same problem.

Prusachat: Just log in with your Prusa account and select the eshop. After a few seconds the chat window should appear on the lower right corner. If the chat window does not open, disable a possibly activated adblocker or try another browser.

github: https://github.com/prusa3d/Prusa-Firmware-Buddy/issues

wbr,

Karl

Statt zu klagen, dass wir nicht alles haben, was wir wollen, sollten wir lieber dankbar sein, dass wir nicht alles bekommen, was wir verdienen.

Posted : 28/03/2023 6:48 pm
Chris Barnes
(@chris-barnes)
Eminent Member
RE: Thermal anomaly on firmware 3.12.2

I wanted to bring this back to the top.  The MK3S+ kit has been running well.  I upgraded to 3.12.2 and have a ton of "Thermal Anomaly" errors.  I run a standard V6 setup and all replacement parts either come from Prusa or from the Prusa Specific parts section on E3D-Online.  It is frustrating that even during the bed calibration it stops mid way and has the errors.  I chose the option for Thermal Calibration several times and yet I still have the anomaly.

Has anybody else seen this?

Posted : 02/07/2023 4:10 pm
EliwazMoonitz
(@eliwazmoonitz)
Member
RE: Thermal anomaly on firmware 3.12.2

Front fan fail upon test after update! May need to rollback to the update before this an see if the problem stops if it does its in the code an not a real problem with the printer itself. Try that first everyone an see if that fixes it since I had no issues with that until after this update.

Posted : 17/07/2023 7:01 am
mcad2000
(@mcad2000-2)
Member
RE: Thermal anomaly on firmware 3.12.2

Hi, i finished my 7 gcode files for MK4 Upgrade in my MK3S+ whitout any problem and ..., i change the PETG to ASA and try to print 2 small parts 2 hours, and the printer beginig to beepppppp, and Thermal anomaly coming, i will go in holidays tomorrow, i would re see in a week what is the solution...

Assembly my MK4 ?

Posted : 28/07/2023 6:08 pm
ga
 ga
(@ga)
Estimable Member
RE: Thermal anomaly on firmware 3.12.2

I just switched from printing nylon @ 245-260C to doing a PLA print @220 and am getting constant THERMAL ANAMOLY beeping.  The print looked like it was doing fine and the temp said a steady 220.  MK3S, fw 3.13.1, 0.6mm nozzle, all standard parts.  The nylon was printed without any enclosure; the PLA was being printed with a home-made enclosure that covers only the front part of the bed, i.e. from the print gantry out towards the screen.

1. Is there a way to silence the beep, especially mid-print?  I tried all values [LOUD, ONCE, SILENT, ASSIST] and it kept beeping.  I finally had to stop the print.  Occurred in the middle of the second layer of a 50 x 70 cm print.

2. I'm thinking this might be due to sometimes using an enclosure and sometimes not.  If that is the case, does that mean I need to re-calibrate every time I switch?  That would be a royal PITA, and a good reason to be able to store and recall different calibrations.  Or should I just keep the enclosure calibration, since that is likely the worst case?

I don't think I did a calibration when I upgraded to 3.13.1., but just did one and it seems to be printing ok now.

Posted : 05/10/2023 4:37 pm
Kent M.
(@kent-m)
Member
RE:

YES! @chris

I was having a similar issue with 3.13.0

Stock mk 3 s+ in prusa enclosure

It stemmed from a bad clog I got from installing a steel nozzle without adjusting the temperatures.  The fix for that was a rebuild of the hotend with a new block and break. NBD.

a few weeks after that halfway thru a 2 day print it failed due to a “thermal anomaly”. Further testing showed a temperature drift +/- 5 c with the print failing each time either right after z-scan or witching 5 minutes.

Thermal and PID calibration could not resolve this issue.

Last night I replaced the thermistor thinking that I may have pinched a wire during the rebuild and found it had the same +/- 5 c drift when set to preheat.

Temperature calibration did not fix it.

finally I flashed the firmware back to 3.12.2 and recalibrated temp and PID.  There is still a little bit of drift +/- 1 c but it’s quick enough not to trigger the “thermal anomaly.”

Hope this helps.

This post was modified 7 months ago 2 times by Kent M.
Posted : 11/10/2023 3:36 pm
Bent Derailleur
(@bent-derailleur)
Eminent Member
RE: Thermal anomaly on firmware 3.12.2

I have this problem also, have the Revo hot end, AND the special Revo firmware (3.13) but still problem. Yesterday I had a long print, it was sooooo many thermal anomalies and beeps, and then after a while it paused the print. It happened when I was away for a day. Came back and noticed the print was paused. I just had to resume the print and then it managed to finish.

But it would be great to tune this calibration so thermal anomaly works like it should. This is kind of frustrating.

Posted : 17/10/2023 7:55 am
Bent Derailleur
(@bent-derailleur)
Eminent Member
RE: Thermal anomaly on firmware 3.12.2

...this beep is driving me and my girlfriend nuts. I'm thinking of opening the case and put some cloth on the beeper, that should do it 😀

Posted : 21/10/2023 8:44 pm
guadalupecooper
(@guadalupecooper)
Member
RE: Thermal anomaly on firmware 3.12.2

Are you sure the thermistor is correctly positioned and secured on the hotend ? It should be in direct contact with the heater block, where the hotend's temperature is measured. If it's loose or misplaced, it might lead to inaccurate temperature readings.

pico park
Posted : 12/12/2023 3:36 am
Bruce Labitt
(@bruce-labitt)
Estimable Member
RE: Thermal anomaly on firmware 3.12.2

I want to report thermal anomolies on this new firmware as well.  Stock kit.  Never did it before the firmware update.  Haven't even changed the nozzle yet, so haven't been in there to disturb anything.  Happened to me in draft mode, less than 30 minutes into a 9 hour print.  Printer paused due to this.  Tried resuming, but paused less than two minutes later.  Had to abort the print.

Read that this is possibly due to excess current in the filament extruder motor.  It appears the default setting is around 538mA for draft and 430 otherwise. 

No enclosure, it's winter outside, inside is 21C or so.  Never had these events before the firmware change.  I am looking into downgrading the firmware unless I hear otherwise from this forum. 

But before doing that, I will edit the gcode and reduce the current for draft mode and see if it works any better.  If it would help, I could attach the 3mf file, it is 9.9MB.

Posted : 13/12/2023 2:55 pm
Bruce Labitt
(@bruce-labitt)
Estimable Member
RE: Thermal anomaly on firmware 3.12.2

Patching the gcode doesn't work.  I reduced the draft mode current by 5%.  Got a thermal error by layer 3 of the print.  I don't know what's wrong at this point, but not a happy camper.  Captured some of the thermal output and the error.

Recv: T:247.1 /250.0 B:90.6 /90.0 T0:247.1 /250.0 @:92 B@:37 P:0.0 A:34.6
Recv: ok
Send: N4514 G1 X127.468 Y36.833 E.02394*89
Recv: ok
Send: N4515 G1 X135.398 Y44.763 E.60933*95
Recv: ok
Send: N4516 G1 X135.662 Y44.411 E.02391*92
Recv: ok
Send: N4517 G1 X127.789 Y36.538 E.60495*82
Recv: ok
Send: N4518 G1 X128.069 Y36.202 E.02376*91
Recv: ok
Send: N4519 G1 X136.064 Y44.197 E.61432*80
Recv: ok
Send: N4520 G1 F8640*119
Recv: ok
Send: N4521 G1 X133.002 Y41.135 E-1*83
Recv: ok
Send: N4522 G1 Z1 F720*1
Recv: ok
Send: N4523 G1 X137.063 Y44.424 F10800*116
Recv: ok
Send: N4524 G1 Z.8 F720*32
Recv: ok
Send: N4525 G1 E1 F2100*47
Recv: ok
Send: N4526 G1 F4705.882*97
Recv: ok
Send: N4527 G1 X136.952 Y44.534 E.00663*93
Recv: ok
Send: N4528 G1 F4125.737*106
Recv: ok
Send: N4529 G1 X136.853 Y44.403 E.00794*95
Recv: ok
Send: N4530 G1 F3672.934*108
Recv: ok
Send: N4531 G1 X136.755 Y44.271 E.00893*84
Recv: ok
Send: N4532 G1 X128.322 Y35.838 E.64798*91
Recv: ok
Send: N4533 G1 F8640*117
Recv: ok
Send: N4534 G1 X131.384 Y38.9 E-1*88
Recv: ok
Send: N4535 G1 Z1 F720*7
Recv: TM: error |-1.260870|>1.200000
Recv: ok
Send: N4536 G1 X121.523 Y35.246 F10800*114
Recv: ok
Send: N4537 G1 Z.8 F720*34
Recv: TM: error |-1.260870|>1.200000
Recv: T:245.5 /250.0 B:90.4 /90.0 T0:245.5 /250.0 @:116 B@:69 P:0.0 A:34.6
Recv: ok
Send: N4538 G1 E1 F2100*35
Recv: ok
Send: N4539 G1 F4705.882*111
Recv: ok
Send: N4540 G1 X121.534 Y35.287 E.0018*101
Recv: ok
Send: N4541 G1 X121.463 Y35.306 E.00312*86
Recv: ok
Send: N4542 G1 X121.482 Y35.235 E.00312*91
Recv: ok
Send: N4543 G1 F4125.737*103
Recv: ok
Send: N4544 G1 X121.386 Y35.101 E.00797*83
Recv: ok
Recv: TM: error |-1.358177|>1.200000
Send: N4545 G1 F3672.934*110
Recv: ok
Send: N4546 G1 X121.29 Y34.968 E.00891*104
Recv: ok
Send: N4547 G1 X112.141 Y25.818 E.70303*87
Recv: ok
Send: N4548 G1 X111.973 Y25.51 E.01906*110
Recv: ok
Send: N4549 G1 F4705.882*104
Recv: ok
Send: N4550 G1 X111.72 Y25.207 E.01674*100
Recv: ok
Send: N4551 G1 X111.486 Y25.023 E.01262*93
Recv: ok
Send: N4552 G1 F4125.737*103
Recv: ok
Send: N4553 G1 X111.332 Y24.939 E.00848*87
Recv: ok
Send: N4554 G1 F3672.934*110
Recv: TM: error |-1.358177|>1.200000
Recv: ok
Send: N4555 G1 X111.178 Y24.855 E.00953*93
Recv: ok
Send: N4556 G1 X108.835 Y22.513 E.17999*95
Recv: TM: error |-1.246778|>1.200000
Recv: ok
Send: N4557 G1 X109.093 Y22.154 E.02402*87
Recv: ok
Send: N4558 G1 X121.152 Y34.213 E.92659*92
Recv: ok
Send: N4559 G1 X121.221 Y34.347 E.00819*91
Recv: TM: error |-1.337669|>1.200000
Recv: ok
Send: N4560 G1 F4125.737*102
Recv: ok
Send: N4561 G1 X121.291 Y34.48 E.00727*101
Recv: ok
Send: N4562 G1 F4705.882*97
Recv: ok
Send: N4563 G1 X121.272 Y34.551 E.00312*85
Recv: ok
Send: N4564 G1 X121.343 Y34.532 E.00312*84
Recv: ok
Send: N4565 G1 X121.332 Y34.491 E.0018*98
Recv: ok
Send: N4566 G1 X121.137 Y33.582 F10800*127
Recv: ok
Send: N4567 G1 F3672.934*110
Recv: ok
Send: N4568 G1 X109.356 Y21.801 E.90523*82
Recv: ok
Send: N4569 G1 X109.629 Y21.459 E.02378*92
Recv: TM: error |-1.597901|>1.200000
Recv: ok
Send: N4570 G1 X121.214 Y33.044 E.89017*86
Recv: ok
Send: N4571 G1 X121.348 Y32.561 E.02723*95
Recv: ok
Send: N4572 G1 X109.905 Y21.118 E.87926*91
Recv: ok
Send: N4573 G1 X110.193 Y20.791 E.02368*94
Recv: ok
Send: N4574 G1 X121.531 Y32.128 E.87115*85
Recv: ok
Send: N4575 G1 F8640*119
Recv: ok
Send: N4576 G1 X118.469 Y29.066 E-1*88
Recv: ok
Send: N4577 G1 Z1 F720*1
Recv: ok
Send: N4578 G1 X113.238 Y23.334 F10800*119
Recv: TM: error |-1.460425|>1.200000
Recv: T:243.5 /250.0 B:90.3 /90.0 T0:243.5 /250.0 @:127 B@:87 P:0.0 A:34.7
Recv: ok
Send: N4579 G1 Z.8 F720*40
Recv: ok
Send: N4580 G1 E1 F2100*32
Recv: ok
Send: N4581 G1 F4705.882*108
Recv: TM: error |-1.988392|>1.200000
Recv: TM: error triggered!
Recv: echo:enqueing "G1 E-1.000 F2700"
Recv: // action:paused
Printer signalled that it paused, switching state...
Changing monitoring state from "Printing" to "Pausing"
Recv: echo:Printer stopped due to errors. Supervision required.
Recv: Error:checksum mismatch, Last Line: 4580
Recv: Resend: 4581
Recv: ok
Send: N4581 G1 F4705.882*108
Recv: TM: error |-2.892131|>1.200000
Recv: TM: error |-2.892131|>1.200000
Recv: TM: error cleared
Recv: T:250.3 /0.0 B:90.1 /90.0 T0:250.3 /0.0 @:0 B@:109 P:0.0 A:34.5
Recv: echo:busy: paused for user
Recv: T:250.4 /0.0 B:90.1 /90.0 T0:250.4 /0.0 @:0 B@:96 P:0.0 A:34.7
Recv: echo:busy: paused for user
Recv: T:250.0 /0.0 B:89.9 /90.0 T0:250.0 /0.0 @:0 B@:117 P:0.0 A:34.6
Recv: echo:busy: paused for user
Recv: T:249.5 /0.0 B:90.0 /90.0 T0:249.5 /0.0 @:0 B@:87 P:0.0 A:34.8
Recv: echo:busy: paused for user
Recv: T:245.6 /0.0 B:89.8 /90.0 T0:245.6 /0.0 @:0 B@:117 P:0.0 A:34.7
Recv: echo:busy: paused for user
Recv: T:239.1 /0.0 B:89.8 /90.0 T0:239.1 /0.0 @:0 B@:115 P:0.0 A:34.6
Recv: echo:busy: paused for user
Recv: TM: error |-1.219507|>1.200000
Recv: TM: error |-1.219507|>1.200000
Recv: T:237.0 /0.0 B:89.8 /90.0 T0:237.0 /0.0 @:0 B@:104 P:0.0 A:34.7
Recv: TM: error |-1.321827|>1.200000
Recv: echo:busy: paused for user
Recv: TM: error |-1.321827|>1.200000
Recv: T:241.1 /0.0 B:89.8 /90.0 T0:241.1 /0.0 @:0 B@:97 P:0.0 A:34.9
Recv: echo:busy: paused for user
Recv: T:239.5 /0.0 B:89.9 /90.0 T0:239.5 /0.0 @:0 B@:74 P:0.0 A:34.5
Recv: echo:busy: paused for user
Recv: T:241.1 /0.0 B:90.0 /90.0 T0:241.1 /0.0 @:0 B@:58 P:0.0 A:34.9
Recv: echo:busy: paused for user
Recv: T:241.5 /0.0 B:90.0 /90.0 T0:241.5 /0.0 @:0 B@:60 P:0.0 A:34.7
Recv: echo:busy: paused for user
Recv: T:240.8 /0.0 B:90.1 /90.0 T0:240.8 /0.0 @:0 B@:40 P:0.0 A:34.6

Not sure what is happening here, but it doesn't take long to fail.  🙁

Posted : 13/12/2023 3:29 pm
Bruce Labitt
(@bruce-labitt)
Estimable Member
RE: Thermal anomaly on firmware 3.12.2

Found a loose left fan connector!  Hope that fixes it.  I did down grade the firmware, but it didn't fix it.  Trying again.  Probably should have checked the connectors, it's been a year.  The left fan connector was not latched, so it could have been intermittent, especially under some print conditions.  If it works, I will flash to the latest.

Posted : 13/12/2023 4:54 pm
Bruce Labitt
(@bruce-labitt)
Estimable Member
RE: Thermal anomaly on firmware 3.12.2

That didn't fix it.  Flashed to newest.  Think it is a pinched hot end thermistor cable, although the thermistor measures 110K statically.  Passes static tests, TM cal and PID cal, but fails during a print.  Can't print anything now.

Posted : 13/12/2023 11:03 pm
karl-herbert
(@karl-herbert)
Illustrious Member
RE: Thermal anomaly on firmware 3.12.2

Try to deactivate new thermo protection with "M310 S0".

Maybe it helps.

wbr,

Karl

Statt zu klagen, dass wir nicht alles haben, was wir wollen, sollten wir lieber dankbar sein, dass wir nicht alles bekommen, was wir verdienen.

Posted : 14/12/2023 12:04 am
Page 1 / 3
Share: