-
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
[BUG] Thermal Anomoly errors in 3.14.0 #4721
Comments
It's clear from the forums that this thermal model code has never worked well. What is really needed is a way to disable it. |
I'm sorry to hear that, and I understand the problem may look like a direct consequence of the firmware upgrade but there haven't been similar reports since 3.14.0 was released - not that I know, so far - so it may be an unfortunate coincidence, or you may come from an old/custom firmware without Thermal Model. We may be missing something but so far this seems to be an unfortunate coincidence, so please contact our Customer Support to check the hardware, and I strongly recommend not to take the thermal anomaly lightly! Other than this, there is a way to disable it via codes of course - #3552 - but that is definitely not advisable. Some users may have decided to ignore the thermal anomalies, and we respect their opinion on forums, but there haven't really been comments and evidence to prove the thermal model wrong. If you say that it has never worked well, it may seem to imply you have been ignoring an even mildly potentially hazardous condition for a long time, or you may have been using an underperforming printer (to some extent). Except for multiple new reports over the next few days/weeks, this issue should be closed as we are probably looking at the correct firmware behavior caused by more or less concerning - yet real - hardware issues, or assembly inconsistencies. Michele Moramarco |
+1 for the thermal anomaly here. |
Same for me. I don't know if it comes from there, but I launch my prints from Pronterface. |
I have replicated the issue on my MK3S+. However I have a Revo Six Hotend My last working "native" version of Firmware is 3.11.0. The issue was introduced with 3.12.0 with the addition of the "New thermal model protection" feature. There is a discussion #4451 that goes into detail and has allowed me to move to 3.14.0 🤞🏻 |
Same problem here. |
i did buy my machine second hand had no issue does have a nozzle upgrade. soon as i upgraded to 3.14.0 i've had the thermal anomaly. and wont calibrate. im now running back on 3.10.0 |
I did a factory reset after and before flashing 3.14 and then the thermal anomaly error appeared immediately. |
Same here on mk3s+ with revo and bondtech extruder, sometimes thermal error persist but hotend warms up without issues, sometimes with same error on display warm up stops and I have to clear error. |
@GaborTheHutt, @dingo1984 and @cpuks - Are you using the standard 3.14 image or the special Revo 3.14 image? The discussion in #4451 goes into detail on how to install it. |
Since I've got bondtech extruder I'm using their version and it's special one for revo - and it's displayed on the screen. So well I think I'll have to go back to 3.11 as turning off thermal model does not work in my case. |
You can connect via USB and open a serial monitor and look which TM errors you get. I get sometime TM warnings when heating up after a print has finished and I start a new print, BUT never got a TM error that I had to clear. On the other hand I have the stock E3Dv6. Try to change your I can understand some user being frustrated that TM triggers on some REVO to sensitive and what to disable it. But there have been more than one case I know off where a broken wire was detected and so prevented a way bigger issue. |
i not sure as i didnt ask when i bought it i have flashed again to 3.14 still getting the anomaly i clear tm fault and retry first layer calibration. i do this several time until i reach around 160c alarms but keep going to right temp but now filament sensor not working |
filament my fault sort but still getting thermal anomaly. managed to get it to do the first layer cal, but thats with constantly clearly thats thermal fault until i get to about 160c |
The thermal model is completely broken. |
You can disable the TM using the M310 gcode command and to make it permanent use
I am aware of at least one REVO user who has found a broken wire at some specific position as the connector rubbed off the isolation. I would argue that it shows that the connectors of the REVO can cause issues and the hardware isn't "perfectly fine".
The TM works well for the E3D v6 stock nozzle. The REVO values have been provided by a small community group and E3D and so these values may not work for every one.
Did you try the TM calibration to fine tune the TM values to your specific printer?
The REVO is a 3rd party solution and issues should be reported to E3D.
There will be no menu to enable or disable this feature. E3D is responsible for the support of the REVO! As E3D is a long partner of Prusa we agreed to compile and release the firmware here for E3D. Reading these kind of comments let me think that we may have to stop compiling and releasing the firmware for the REVO and let the community / E3D to do it themself. |
i made an update on #4451 (comment) the gist of it is we're reverting back to fw3.11 |
that may be but there should be no reason to run the V6 nozzle with revo available considering how V6 is to prone to leaking and maintenance is time consuming and much more difficult compared to revo |
The original MK3S comes with an E3Dv6. There might be some advantages to use the REVO but Prusa doesn't sell these. |
Printer type - MK3S+
Printer firmware version - 3.14.0
MMU upgrade - none
MMU upgrade firmware version - none
SD card or USB/Octoprint
sd card
Describe the bug
After updating to firmware 3.14.0 I am getting thermal anomaly errors during calibration.
Previously the printer was working without issue.
All stock parts no upgrades
To Reproduce
Walk through calibration wizard
anomoly happens on first layer calibration
Expected behavior
No thermal anomaly errors
The text was updated successfully, but these errors were encountered: