Prusa-Firmware
Prusa-Firmware copied to clipboard
prusa3d
[BUG]3.13.0 Revo rapid change Thermal Anomaly
Printer type - MK3S+ Printer firmware version - 3.13.0-6873 SD card
Describe the bug Trying to perform first layer calibration but getting thermal anomaly.
To Reproduce Installed Revo rapid change with .8mm nozzle. Updated firmware to MK3S+ Revo 3.13.0-6873. Perform first layer calibration
Expected behavior Execute first layer calibration
Video Please attach a video. It usually helps to solve the problem.
https://github.com/prusa3d/Prusa-Firmware/assets/5809820/728af3f7-7623-43d2-b1c5-61119843cb1c
Can you try sending the command below before running the calibration (it works ok here)…
M310 (to check current values) M310 W1.00 E1.74
Hopefully someone who can explain / help with the issue permanently will also comment.
Is thermal calibration “Thermal Model cal.” If so the yes. It stops before completes the calibration.
Uploading 23-08-16 11-53-22 10562.mp4…
not sure if video is working. But it stops after “TM: initial c est.”. “Stopped” will flash. Then say “Print aborted”
Same issue here after upgrading to firmware 3.13.0 for mk3s with revo upgrade. Also tried a full factory reset without any better results.
The printer is an MK3 upgraded to MK3S. Just checked the revo model I have, it’s from the upgrade kit, I suppose it’s the 24V 40W heater block since the 60W seems to be sold for high flow purposes; the firmware has been flashed accordingly.
Having no filament loaded makes the TM test fail in seconds, while with filament loaded, the test does heat up to 230c, cool down, moves the extruder to a corner, and then fails with the « aborted » message.
For now, the printer is running with model disabled.
Can confirm, The issue with Revos still persist. I cannot perform an initial pid cal, cannot heat the nozzle. As soon as temp reaches 50-65 deg C any action is aborted and temp set to 0. Have installed 3.13.0 REVO version of FW. Appears to work fine on downgraded to 3.11 (so does not appear to be HW related).
M310 on 3.13.0 REVO version for MK3S/MK3S+ returns:
M310 P38.00 U0.0000 V1.00 C12.40 D0.0650 L2160 S1 B1 E1.74 W1.20 T-7.00
Also, turning off with M310 S0 I can complete a PID tuning just fine, but I cannot run a Thermal Model Cal (stops when heating at about 55degr. C)
@redzero36 You did use the Revo specific FW for your setup (there are four different ones in the revo.zip), correct?
@werkstrom Yes. Installed the MK3S+ revo version. Not the HF 60W one. Used the second of the four files.
FYI, I'm now back on 3.13.0.6873 REVO. Having disabled the temperature model functions (Using M310 S0 followed by M500 to save to EPROM) no issues. So a lot points to this being related to the temperature model functions and thus them not functioning correctly... still.... And since I'm under the assumption there are no such features in 3.11 and before, I assume there is no added "fire hazard risk" disabling this compared to reverting to 3.11. Unless, some other "legacy" safety feature has been removed in 3.12 and replaced by the temp mod stuff. Perhaps someone else knows and could clearify 🙂
Note: I'm on a non plus MK3S.
I also have this issue with the new REVO I purchased. I was able to roll back to 3.11 and it works now.
@werkstrom yup. I see an R after 3.13 so I guess thats the revo version. I just setup an mini pc for octoprint. Disabled TM. Still on 3.13. Things are up and running and just printed a first layer calibration.
IT SEEMS THE MK3S+ WORKS WELL WITH FW REVO 3.13.0, but you have to do an additional step.
I have upgraded my MK3S to MK3S+ and in this occasion I also installed the REVO. I installed the REVO 3.13.0 MK3S FW, and performed the wizard setup to recalibrate the printer. Unfortunately nothing worked.
- As soon as the printer tried to raise the hot-end temperature I always got strange THERMAL ANOMALY errors, or the printer just stuck, or reset the target temp to 0°.
- The PID test failed after few seconds and could not be set or completed.
I spent hours trying to make it work, until in order to solve another issue I had on the printer, I decided to FACTORY RESET & DELETE ALL DATA from the printer.
After the reset, the printer restarted, and the Configuration Wizard started. This time all the wizard tests were successfully passed, all the hot-end access worked, the PID tuning config either worked perfectly, and the successful message come from the printer on the LCD.
Now I have done also a couple of print, and all worked fine. And also the other issue I had automagically was gone.
So, the Prusa Firmware for some functions make really mess when it use values in conflict with the EEPROM values stored, so just clear all the EEPROM data, and restart, and then all should work fine.
Same issue here after upgrading to firmware 3.13.0 for mk3s with revo upgrade. Also tried a full factory reset without any better results.
The printer is an MK3 upgraded to MK3S. Just checked the revo model I have, it’s from the upgrade kit, I suppose it’s the 24V 40W heater block since the 60W seems to be sold for high flow purposes; the firmware has been flashed accordingly.
Having no filament loaded makes the TM test fail in seconds, while with filament loaded, the test does heat up to 230c, cool down, moves the extruder to a corner, and then fails with the « aborted » message.
For now, the printer is running with model disabled.
I am able to print with the 3.13.0. At the beginning it had your same behaviour, but then I got the idea to erase the EEPROM data that were probably confusing the FW, so I performed a FACTORY RESET (All Data) option, and then the printer restarted from scratch. Then I performed the Wizard, realigning the axes, and performing the PID thermal test, and all finished successfully, and I was able to print. I think that even if you have the REVO and try to perform the TM setup, the FW insist to use some old stored values for E3DV6.
@antimix
the FW insist to use some old stored values for E3DV6.
Yes flashing the FW3.12.0 will write E3D v6 Tjermal model and PID values to the EEPROm which aren't changed by flashing the E3DREVO_fw_*.hex file.
A Factory reset All data will delete the eeprom and write the default values (E3DREVO_*hex has the PID and TM values for the REVO).
E3D and we are working on a solution.
@everyone Please ensure that you flash the correct hex file. Make sure that you flash the E3DREVO_fw_*.hex file and flash it only with PrusaSlicer as OctoPrint Firmware updater doesn't flash the xflash correctly.
@redzero36 Just a side note when you change the nozzle size please don't forget to adjust the Settings -> HW Setup -> Nozzle. This will ensure that you get warnings if a 0.4 nozzle gcode is used while you have a different nozzle size installed. Also the first layer calibration will be adjusted for the different nozzle size.
Resetting my EEPROM worked, I am now able to run with the Revo 3.13.0 firmware :)
full factory reset didn't solve for me. using revo high flow hotside. had to upgrade fw to use mmu3. besides thermal anomaly, getting weird "filament unexpectedly detected" error since resetting.
I'm still getting Thermal Anomaly beeps with REVO 3.13.1 firmware. I've performed factory reset, pid tune, and successful thermal calibration on two MK3s+-R's. Both will occasionally beep with anomalies.
Some days they go without a sound. Last night one was beeping once every few minutes. After about 20 min of intermittent beeps and warnings it was fine and had no further warnings for another 5 hours when the print finished.
The only pattern that I've seen is that it generally occurs when the nozzle is at a lower Z height. Could the heated bed ambient temps affect nozzle temp monitoring? I'm printing exclusively in PETG. 235/85 - 240/90.
I'm backing down to 3.11, because these are farm machines with lots to do.
I too still get the occasional Thermal Anomaly or just the beeps with no message, never during a print however.
To be honest I don’t know how the E command in “M310 W1.00 E1.74” affects it and if it could help in fine tuning.
Ideally for me an option to turn off / disable checking during loading and unloading of filament would fix things.
Hope you manage to get it sorted to keep the farm running ok!
Thanks. Luckily, I've only added REVO to two machines. :) I also tried that M310 command from the start with no change in behavior.
Another observation I just made is that when on 3.13.1 the nozzle temp is somewhat erratic. It bounces +/- 2C around the set temp. Now that I have them downgraded to 3.11, the temp stays solid on the desired value.
Well, hell. It's possible this is a problem with the REVO extension cable connectors for both of these printers. One just refused to heat at all, even on 3.11. So, I messed with the wiring, reseated all connectors, and all is well again. So, everything above may be a false alarm. When I am able, I'll reupdate to 3.13.1 and see what happens.
I've found that the cable connector is not the cause of the anomalies. With my two REVO MK3S+ printers, I have one running 3.11 and one with 3.13.1. Both have been printing non-stop for the last 4 days. Just now the 3.13.1 machine beeped with an anomaly. Nothing has changed in those 3 days, not even the filament type. The print head is 2.3mm above the bed. So, there is still an issue with 3.13.1 tolerances.
I also have incessant beeping during the 2nd-4th layer of prints, seems to be during long extrusion moves. Newly installed revo on FW 1.13.1 MK3S with an 0.6mm obxidian nozzle, nozzle size set in FW and PID, TM calibration both run.
Today I installed my new REVO update, flashed the E3DREVO_fw_MK3S_MK3S+_3_13_1_6876.hex, and get the same errors. Even a factory reset didn't bring any improvement. Every time the temperature reaches approx. 60°, it stops. Even the setup wizard stopped at this point. I'm using a new MMU3 and I'm not sure whether it will also work with the MMU3 with the old firmware 3.11, which seems to work with the Revo. Does anyone have any experience with this? The hint from @werkstrom seams to work (Using M310 S0 followed by M500 to save to EPROM)
I'm not sure whether it will also work with the MMU3 with the old firmware 3.11
@klsc18 It won't work. The MMU3 firmware can't communicate with printers on FW 3.12 and older because the communication protocol is completely different. (Not backwards compatible)
The hint from @werkstrom seams to work (Using M310 S0 followed by M500 to save to EPROM) Now I can heat up
Today I installed my new REVO update, flashed the E3DREVO_fw_MK3S_MK3S+_3_13_1_6876.hex, and get the same errors. Even a factory reset didn't bring any improvement. Every time the temperature reaches approx. 60°, it stops. Even the setup wizard stopped at this point. I'm using a new MMU3 and I'm not sure whether it will also work with the MMU3 with the old firmware 3.11, which seems to work with the Revo. Does anyone have any experience with this? The hint from @werkstrom seams to work (Using M310 S0 followed by M500 to save to EPROM)
I use M310 W2.00 E2.00 as I was getting similar errors, had none since, the REVO warms up too quick for the stock settings and triggers warnings.
But since the "Thermal model calibration" aborts EVERY TIME, you cannot successfully complete the setup wizard. This means that every time the printer is switched on or reset, a message appears indicating that the setup has not yet been completed. I hope a bug-fixed firmware image will appear soon.