MK3S+ 3.12+ Firmware + Revo = Massive Headache w/ “Thermal Anomaly Detected” BS
 
Notifications
Clear all

MK3S+ 3.12+ Firmware + Revo = Massive Headache w/ “Thermal Anomaly Detected” BS  

  RSS
oriddlero
(@oriddlero)
Eminent Member
MK3S+ 3.12+ Firmware + Revo = Massive Headache w/ “Thermal Anomaly Detected” BS

I finally got around to updating my firmware on multiple printers like I have many times in the past thou Octoprint, and because I use REVOS.....  kaboom thermal anomaly town.  Fun times.  After scratching my head and cursing for a while trying to recalibrate, I got around to reading the full release notes and found this most interesting tidbit AT THE BOTTOM that probably should have been in bold red letters next to the release:

"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."

Riiight... Cool story.  I ran Pronterface and send G-code M310 S0 followed by M500... Rebooted printer same shit.

TLDNR: If you are running Revo's just downgrade your firmware to FIRMWARE 3.11.0 before they release this half-baked crap. All be well again.

Couple of hours of my life I will never get back again. 

 

If my post helps you please consider downloading & making one of my most popular Prusa-Printables 3D models below:1. Ultimate Printer Knob Upgrade - The Best Knob of Both Worlds 2. Prusa MK3S Right…

Posted : 23/02/2023 7:11 pm
You liked
R&D
 R&D
(@rd)
Estimable Member
RE:

That was announced a month or so ago, apparently what should have been in bold type was, READ THE RELEASE NOTES. 😉

 

Also Prusa is looking for feedback  so they can try to help resolve the issue.

 

This post was modified 1 year ago 2 times by R&D
Posted : 23/02/2023 8:45 pm
oriddlero
(@oriddlero)
Eminent Member
Topic starter answered:
RE:

Well Kemosabe, that’s a cool sentiment and all….  Thanks for the insightful tidbit.

I always read the release bullet points.  Usually, it’s just blah like known issues, bug fixes, etc…This time there was actually a few interesting-sounding things… but not enough for me to read the “FULL release log”

As you can see from my screenshot it reads “thermal model – important info” it probably should have read something like thermal model – IF YOU HAVE A REVO U R BEAT – SKIP THIS ONE”

Better yet, maybe they could release an alternative firmware version for stock printers and one that excludes this thermal functionality for those of us with alternative hot ends until they get it sorted. At the very minimum it should have some kind of notice in the bullet points not deep in the full release notes.

FUN

This post was modified 1 year ago by oriddlero

If my post helps you please consider downloading & making one of my most popular Prusa-Printables 3D models below:1. Ultimate Printer Knob Upgrade - The Best Knob of Both Worlds 2. Prusa MK3S Right…

Posted : 23/02/2023 9:02 pm
darksharpie
(@darksharpie)
Trusted Member
RE: MK3S+ 3.12+ Firmware + Revo = Massive Headache w/ “Thermal Anomaly Detected” BS

FWIW...  I installed the Revo.. Got the thermal issue.  Ran the Pronterface gcode, restarted, and haven't had a problem since.  Maybe the setting didn't get saved properly on your end?

Posted : 23/02/2023 9:43 pm
Extra Fox
(@extra-fox)
Estimable Member
RE: MK3S+ 3.12+ Firmware + Revo = Massive Headache w/ “Thermal Anomaly Detected” BS

Contributing here would help: https://github.com/prusa3d/Prusa-Firmware/issues

Aaron

Posted : 23/02/2023 9:49 pm
oriddlero
(@oriddlero)
Eminent Member
Topic starter answered:
RE: MK3S+ 3.12+ Firmware + Revo = Massive Headache w/ “Thermal Anomaly Detected” BS

 

Posted by: @darksharpie

FWIW...  I installed the Revo.. Got the thermal issue.  Ran the Pronterface gcode, restarted, and haven't had a problem since.  Maybe the setting didn't get saved properly on your end?

Interesting, I followed the procedure applied the G code restarted and it did not stick or work for some reason. I have several printers and can't really afford the downtime to play games with them right now.

When I have some downtime maybe I will try again.

I still stand by my above suggestion: If they know it doesn't work with aftermarket parts they should have had two versions of the firmware one for aftermarket parts (feature disabled), one for stock parts.

If my post helps you please consider downloading & making one of my most popular Prusa-Printables 3D models below:1. Ultimate Printer Knob Upgrade - The Best Knob of Both Worlds 2. Prusa MK3S Right…

Posted : 23/02/2023 10:01 pm
vincele liked
RU's nephew
(@rus-nephew)
Eminent Member
RE:

I would like to contribute, but I'm not sure how to proceed. They ask for log files, but how do I generate & retrieve them? I saw a vague reference to getting them from OctoPrint but, when I upgraded via OctoPrint, I got zero log files. I have been unable to locate a guide; can you point me to one by any chance?

 

Posted : 25/02/2023 10:30 pm
Extra Fox
(@extra-fox)
Estimable Member
RE: MK3S+ 3.12+ Firmware + Revo = Massive Headache w/ “Thermal Anomaly Detected” BS

This will give you the documentation you need. What they'll want is your serial log. Keep in mind that this logs a TON of information so you probably only want it on long enough to capture the data they want. Then turn it back off.

https://community.octoprint.org/t/where-can-i-find-octoprints-and-octopis-log-files/299

Logging documentation: https://docs.octoprint.org/en/master/bundledplugins/logging.html

Aaron

Posted : 26/02/2023 12:54 am
RU's nephew
(@rus-nephew)
Eminent Member
RE: MK3S+ 3.12+ Firmware + Revo = Massive Headache w/ “Thermal Anomaly Detected” BS

Thanks very much. That helped. Of course, first I had to figure out how to enable Serial Logging. Go figure, it's not in with the rest of the logs. Noooo, you have to go under Serial Connection. Oh well, found it. Now, I guess, I need to redo the upgrade again and let it log. But, do I need to try the PID Tuning and let that log too?

Posted : 26/02/2023 1:09 am
RU's nephew
(@rus-nephew)
Eminent Member
RE: MK3S+ 3.12+ Firmware + Revo = Massive Headache w/ “Thermal Anomaly Detected” BS

Well, at least for now, I'm reverting to 3.11. I haven't figured out how to get the log files Prusa wants. It's just taking too long. If I can get a concise guide I'll try again.

Posted : 26/02/2023 1:42 am
RU's nephew
(@rus-nephew)
Eminent Member
RE: MK3S+ 3.12+ Firmware + Revo = Massive Headache w/ “Thermal Anomaly Detected” BS

Today I tried

prusa3d_fw_MK3S_MK3S+_3_13_2_7080

Nope. Got thermal runaway while the printer was trying to do the bed mesh. Back to 3.11.

Posted : 21/11/2023 9:25 pm
RU's nephew
(@rus-nephew)
Eminent Member
RE:

Apologies. I posted the wrong file name: I loaded

E3DREVO_fw_MK3S_MK3S+_3_13_2_7080

And, yes, it stopped with thermal anomaly during the bed mesh.

So, back to

prusa3d_fw_MK3S_MK3S+_3_11_0_4955
This post was modified 3 months ago by RU's nephew
Posted : 21/11/2023 9:42 pm
mpeill
(@mpeill)
Eminent Member
RE: MK3S+ 3.12+ Firmware + Revo = Massive Headache w/ “Thermal Anomaly Detected” BS

Just another symptom with the E3DREVO_fw_MK3S_MK3S+_3_13_2_7080 firmware.

The thermal calibration works, but then when I print, it continues as if all is ok, but I haven't loaded any filament!

The extruder refuses to feed in filament even when offered, although the filament sensor does recognise that it's present at the input end.

What's going on!?!? Back to 3.11.0 again, and all is well.

Posted : 29/11/2023 5:07 pm
James DeHart
(@james-dehart)
Member
RE: MK3S+ 3.12+ Firmware + Revo = Massive Headache w/ “Thermal Anomaly Detected” BS

There are some who have found success following this Github issue. I have opened a ticket with E3D and waiting to get something back from them.

Posted : 30/11/2023 3:39 pm
Share: