E3D REVO Thermal Model #4451
Comments
|
Hello, I have the same issute that my MK3S+ beeps three times with Thermal Anomaly and at the next time it stops with Thermal Error. I use the Revo Six Hotend and have never a problem with THERMAL ANOMALY. But since I put the MK3S+ in the Original Prusa Enclosure it shows up after 1-2 hours printing. I did also PID and Thermal Cal. on the 3.13.2 and the older 3.13.0 and I also tired to do a Revo_Reset G-Code without scuccess. Only when I put the Printer outside of the Enclosure the Error will not apear.
|
|
same problem for me. I updated from 3.13.0 to 3.13.2, set the printer to factory settings, I can't even do the first layer of calibration. without the printer screaming, revo six for mk3 |
|
Adding my voice to this. I went through each step carefully. I reset TM and PID multiple times. I ran the gcode. And when I finally decided to factory reset, I was unable to finish the wizard due to the thermal errors I was continuing to get. I've downgraded back to 3.11, and I'll try again with the next REVO firmware update. |
|
Two printers, did all the steps here. All had the same issue. One seems to actually finish the model but still fails later, the other can't even calibrate the model. Going to downgrade back to 3.11 this feature seems half baked and not suited for revo hotends. |
I am selling this printer and it need to "just work". Disabling until next restart isn't an option. |
|
M500 safe it and it will remain disable afer restart |
|
@3d-gussner , In the step 4 of your first post, isn't it "if step 3 fails" rather than "step 2" ? because it appends to me : changing the firmware went fine, reboot OK with the new firmware but PID calibration fails and TM calibration fails too. The gcode saved me. |
|
@LoakAudio Thanks for the feedback I will check again. |
|
I'm in the same boat as others here. I have opened a ticket with E3D and will post back with any findings that might help others. Update - I still have not heard back from E3D but I checked the Thermistor extension cable and it seems the wire has come lose from the housing. Here are the docs if anyone is wondering. |
|
@3d-gussner I happen to do a factory reset and after the calibration this happened IMG_1961.movShould I open a different Github issue? Please advise. |
|
@jamesdehart Which calibration caused this screen? |
|
After much head scratching, finally got it working, used the E3DREVO_fw version and everything worked first time. Thanks to @3d-gussner for laying out the procedures very much appreciated. |
So it turned out my entire issue was because the thermal cable connector from the Hot-end to the cable that goes to the motherboard failed. The image shows the failed cable & connecor. One of the two wires were connected. 
For others who are running in to issues related to this hotend. It would be good to check there cable to see if there are any issues like I had. When contacting E3D it took them about a week to respond to the support tickets. They are really backed up. I hope this helps. |
|
@jamesdehart Thanks for sharing! This is an example why we implemented the Thermal model to detect issues like this and other. Side note: Try to add some more strain relief so all motions of the cable loom are possible without "pulling" cables at the connectors. |
|
Thanos for sharing. I checked my printer six times and I don’t have any cable or hardware issues. The point is that like I wrote in a other post that TM have problems when the printer is in a enclosure. Also I’d explained in this post how the problem occur in my setup #4431 (comment) |
|
I'm chasing down the same
The PID and TA calibrations finished properly. Upon the next PLA preheat, |
|
@ndemarco Thanks for the update. |
|
I'm also experiencing the issue described by users in this thread. Installed the Revo variant of 3.13.2 on two MK3S+ and now encounter consistent thermal anomaly errors. Things I've tried:
After these steps I still encounter frequent thermal anomaly errors. Sometimes these occur right after initiating a preheat, sometimes right before a print begins, sometimes during a print. (I'm not using an enclosure). Going to try rolling back to 3.11 as other have suggested. |
|
had the same issue. it works now, maybe change the order of your steps 2 and 3 @stevenbennett :)
seems to work, step 3 was the magic sauce for me though! ;) |
After the factory reset you don't need to run any gcode as it set identical values as are used in the E3D . hex files https://github.com/prusa3d/Prusa-Firmware/blob/v3.13.2/Firmware/thermal_model/e3d_REVO.h The gcode files are for users that don't want to factory reset or got "bad" values at some point. |
3.14 is tagged but there are no hex files included so I cant use it yet. https://github.com/prusa3d/Prusa-Firmware/releases/tag/v3.14.0 |
|
Sounds close |
|
new firmware is ready, i will test this on July 4th and report back, looking forward to getting this resolved and especially the new reprint menu feature; it will really help with running the farm of 100's of files. |
So far its working great on the 3 printers I updated a week ago; fw3.14 for mk3s and mk3s+ with revo. I think the main difference was running the reset_revo.gcode , I didnt have to factory reset any printer. I tried this on printers as old as 2019 with 982days of print time and new printer built in late 2023 with 40days of print time. The older printer starts thermal model cal right away after firmware update, newer one didnt. printer number 49 was stuck at PID cal 0/5 but I just restarted the printer and tried again. Details: We'll start updating the rest of the printers and report back if issues. |
|
awesome I haven't been having trouble with mine either on this version but I was waiting because when I had a previous version I didn't have trouble until I did and I don't really know what had changed so I wanted to hear it from someone else before saying anything. |
|
@mhouse1 Thanks for sharing the information 🤗 . Always nice to see that kind of feedback. 🤞 The rest of the printers updates are also going that "smoothly" |
|
Been running 3.14.0 firmware for the Mk3S with Revo for a couple of days now. Seems to be working so far without errors! Though, the option to load filament when autoload is turned off seems to have disappeared. Should I open an issue for this? |
|
@capsulecorplab Thanks for the positive feedback. The "Load filament" and "Unload filament" menus are shown depending on the state of the filament sensor.
Hope that it makes clear. If you have an question or issue with it, then please open a new Issue to keep this one "clear" to one topic. |
|
So far I have 4 printers running new fw3.14 successfully |
|
so far 2 out of 9 printers can't be updated to fw3.14 due to PID cal and thermal model failing right away even though both printers are functional on fw3.11 and is used everyday . Some inconsistencies, some printers starts thermal model cal right away after flashing fw3.14, some doesn't, printer number 10 built 12/16/19 I reverted back to fw3.11 because it kept failing to calibrate on fw3.14 even after factory reset and reset_revo.gcode, when I tried flashing fw3.14 again a few days later it starts self test after flashing. for now any printer that accepts fw3.14 I'm updating to that otherwise they get updated to fw3.11 Details: |
I spoke too soon. I forgot I had disabled thermal model protection while running v3.13.2 before updating to v3.14.0. Factory resetting the printer brought back the thermal anomaly error until I reran the gcode to disable thermal model protection. |
|
@capsulecorplab Thanks for the feedback. Did the TM cal after the factory reset work? |
I tried running TM cal after the reset, but couldn't get the thermal anomaly error to go away, so I ended up just disabling the TM protection |
which one is safer, disabling TM protection and using fw3.14 or using fw3.11 ? |
I don't recall TM issues with fw3.11, but I also haven't printed on that fw enough to tell. I think I've had the best experience with fw3.13.2 (with TM protection disabled) so far - in part due to the fact that fw3.11 lacks filament runout sensing and fw3.14's "load filament" option seems to disappear for me when autoload is disabled, granted that's a separate issue. |
|
no TM issues with fw3.11 but I thought the TM that was added after 3.11 improves on detecting TM anomalies, I wonder if disabling the new TM means we still have whatever safety feature that was in 3.11. Theres definitely lots of improvements in 3.14 that I'd like to use but if disabling the TM model means its less safe than 3.11 then I won't risk it. With TM model disabled in 3.14 can it still detect extruder thermal runaway events? 3.11 has been great in detecting thermal runaways which I've see happen 8 times so far in the last 4 years on a print farm of 50+ mk3s printers. |
|
@mhouse1 Sorry for the late answer.
Yes the default thermal protection is always active. Did you contact E3D support as they should be able to help you with REVO and TM issues, |
|
As you might imagine, E3D ran out of ideas, and directed me to contact Prusa for support. E3D as a supplier of retrofit parts is ultimately responsible for making their parts are compatible. I have offered to assist by providing logged data if properly instructed.
|
I think the confusion from the community is fw3.11 was such a stable fw (no thermal issues in our years of use) why mess with it when it introduces complexity such as having to manage multiple fw builds. And the fact that a printer that prints completely fine on fw3.11 might experience odd thermal anomalies when using fw3.14: in some cases, a "PAUSED thermal anomaly" will appear on the LCD and prevent the print from starting but a reboot fixes it, in other cases "thermal anomaly" appears during print start with audible alarm but does not prevent print. Although a majority of the printers running fw3.14 are running good, it will take me a few more months of runtime to conclude whether updating from 3.11 to 3.14 was worth it. I will try disabling thermal protection on fw3.14 just for those printers (2 out of 12) that are completely functional on fw3.11 but errors out ASAP on fw3.14 preventing the printer from being used. |
@mhouse1 Thanks for the feedback and sorry to hear that 2 of your 12 printers keep be difficult with TM enabled. The thermal model already proved that it is useful as some users had broken or semi broken thermistor or heater cables and found the issue. It reacts to issues way faster that the regular thermal protection but is also way more "sensitive" which can cause false positive warnings and errors. For the stock E3D V6 we had tons of data and test machines internally and I think that the values are working great. For the REVO we had just few community members submitting their values and E3D provided some other values for the REVO within their performance tolerances. @mhouse1 Did you try to raise the |
Hi, sorry to hear that E3D couldn't help you. My time on this 3rd party issue is very limited but please try #4105 and provide there your results? |
thank you for all the work put into this , I do believe I have some bias towards changing from fw3.11 We have some printers on fw3.14 that throws thermal anomally errors during startup, perhaps the firmware response is a sign that the printer wires or revo is wearing out, or its caused by a draft at that corner of the room and moving printer location will improve it, time will tell. |
|
Draft can cause some TM issues. I expected the REVO having less issues with draft because of the design of it. Or are these printers next to an walk-in freezer with -40°C? 😉 If I remember correctly testing the TM on REVO wasn't as easy to trigger as with the E3D v6 see as an example #4105 (comment) |
|
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. |
|
I ended up updating all printers to fw3.14 and disabled thermal model on more than half of the printers (12+ printers); due to thermal model either being annoying or preventing prints. No issues so far operating this way. For most printers with thermal model disabled they on average had 30000 meters of filament and 500 to 600 total print time days (from printer's LCD statistics page). |
If your printer displays a firmware version prior to 3.13.0 or it does not start with E3DREVO_fw_ or E3DREVO_HF_60W_ we would advise that you install the latest Revo supported firmware release via the following link and proceed with the next steps: https://github.com/prusa3d/Prusa-Firmware/releases
If you are using a E3D Revo firmware, please check that this matches the Revo Hotend you have installed as there are different versions.
If you do have an E3D Revo Firmware installed and it matches the Revo HotEnd you have please go to step 4.
If you are unsure as to how to update your printers firmware with the .HEX file please refer to the Flashing procedure within the following guide: https://help.prusa3d.com/article/firmware-updating-mk3s-mk3s-mk3_2227
reset_revo.gcode.txttoreset_revo.gcodereset_revo_hf_60W.gcode.txttoreset_revo_hf_60W.gcodeThese files will need to be copied to an SD card and installed , to Install the G-code select it from the print from the SD menu on your printer and follow the on-screen instructions.
Optional step: If the above steps fail you may wish to factory reset the machine and run the setup wizard. Please note that as the process suggests this will reset the printer and its firmware to a factory state and any setting will be lost.
Link to E3D ticket
The text was updated successfully, but these errors were encountered: