Heating failed errors occur when changing target temps after a preheat #1065
Comments
|
I go through that process almost daily. Ive never seen this issue.
…On Thu, Jun 24, 2021 at 8:15 PM Mike Pfeffer ***@***.***> wrote:
Description
Heating failures occur when adjusting temps after preheating bed
Steps to Reproduce
1. Preheat PLA or ABS
2. Let the bed temperature increase to its preheat value
3. Change the hot end temp to any value higher than the current hot
end target temp, or change the bed temp to any value lower than the current
bed target temp
4. Wait approximately 30 seconds
*Expected behavior:* The printer should adjust the temps to the specified
targets
*Actual behavior:* Printer gives a heating failure error, beeps loudly,
and requires a physical power off/on, regardless of temp
Additional Information
- I'm using the stock 1.3.4 release from
E3V2-ManualMesh-5x5-v4.2.2-v1.3.4.bin
- The issue occurred on 1.3.3 as well - it doesn't happen on Creality
official firmware
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1065>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIPE4Q7CBOELY62I43YGD6LTUPKCNANCNFSM47I5YIXA>
.
|
|
Yes, I do. Exactly the same problem. |
I didn't see it with stok firmware |
|
I had the same problem, and did what @mosheas suggested but no luck. So I reinstalled the firmware and installed the stock firmware for the screen and did the PID one more time. Now everything is ok. I will try to upgrade the screen software ones more but i'm printing now so. Thanks for the tips and thank you Jyers for a great update ;) |
|
Screen firmware is... for the screen. Obviously, that has zero connection
to the heating process
…On Sat, Jun 26, 2021 at 11:16 AM Taffse ***@***.***> wrote:
I had the same problem, and did what @mosheas <https://github.com/mosheas>
suggested but no luck. So I reinstalled the firmware and installed the
stock firmware for the screen and did the PID one more time. Now everything
is ok. I will try to upgrade the screen software ones more but i'm printing
now so. Thanks for the tips and thank you Jyers for a great update ;)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1065 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIPE4Q6DKDLX3XT75TJJOKTTUX4OLANCNFSM47I5YIXA>
.
|
|
Just telling what i did to get it to work smooreace.... So, the solution for me was to reinstall the firmware. Thanks for pointing that out :) |
|
@MohnJadden In the meantime I'll try to recreate this as I feel like I've heard of this issue before. |
|
Fresh user of this great Marlin fork. Thanks for all your efforts! I'm able to reproduce this issue on my machine as well. Did not occur everytime but most of them. I'm still trying to figure out if it only happens in case I change the temperature due the display, as I can not remember that this happen when I change temperature through Octoprint. Installed latest releases of Jyers Marlin FW and the gotcha icon DWIN_SET. |
|
And again... did you do a PID auto-tune after clearing the EEPROM after
installing the new FW?
…On Mon, Jun 28, 2021 at 11:34 AM agarthand ***@***.***> wrote:
Fresh user of this great Marlin fork. Thanks for all your efforts!
I'm able to reproduce this issue on my machine as well. Did not occur
everytime but most of them. I'm still trying to figure out if it only
happens in case I change the temperature due the display, as I can not
remember that this happen when I change temperature through Octoprint.
Installed latest releases of Jyers Marlin FW and the gotcha icon DWIN_SET.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1065 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIPE4Q5LTUD3LI7ONFS5PNDTVCQADANCNFSM47I5YIXA>
.
|
|
Not yet, but it's on my list to be done next and be assured I'll provide an update if it fix the situation for me or it reamins unchainged.
|
|
Update, I performed a PID auto-tune for hotend and bed but the kill exception still occurs from time to time. |
|
I have exactly the same problem. My steps to recreate:
I am using OctoPrint 1.6.1, Python 3.7.3, OctoPi 0.18.0 and Marlin Jyer v1.34 |
yes, we talked to you about this problem before, the same problem happened to this friend and a friend on facebook had the same problem and returned to stock software, it gives a heating error while heating and says start again when it starts to heat, it gives the same error only when the device is cold, there is no error |
|
I don't understand, what is the cause and the solution? |
|
I have this when the print temp is lower than the current temp. IE if the hotend/bed are at say PETG temps of 235/70 and then the sliced file is for PLA 195/60, when the GCode changes to the lower temp it crashes with the error. Provided the pre-heated temp is at or below the desired print temp no error. |
|
Hmmm interesting I will try to verify tomorrow.
On Fri, Jul 2, 2021 at 3:30 AM Tw0bit ***@***.***> wrote:
I have this when the print temp is lower than the current temp.
IE if the hotend/bed are at say PETG temps of 235/70 and then the sliced
file is for PLA 195/60, when the GCode changes to the lower temp it crashes
with the error.
Provided the pre-heated temp is at or below the desired print temp no
error.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1065 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEJTDDN5D5WKPX4W2KV3YXLTVVTJTANCNFSM47I5YIXA>
.
--
Paul Hodara
|
|
That seems to work. Provided I only prewarm to a lower temperature than what I print at, no crashes. Probably a minor bug in the firmware. As long as there is a work around it's fine with me. |
|
I don't know if it's actually a bug. My best guess is that resetting the temp to make it cooler is messing with marlins thermal runaway safety system. As cooling the heaters would cause the temp to change to slowly and therefore trip the runaway protection. I could make the runaway values even more lenient but obviously I don't want to overdo it and compromise the safety of the machine. |
|
Once I preheat the heaters I then turn them off before I run the print job. I don’t
know the thermal runaway logic, but once a print job starts and the gcode
sets up the temps for the job shouldn't PID kick in and if the temp are too high
keep the heaters off and monitor temp rates until preset temps are reached?
My understanding is that the thermal runaway logic triggers only when temps go above
a preconfigured maximum temperature. Again I don’t know anything about
the logic I am just speculating.
I really do like this firmware and find the screen layout very intuitive everything
seems very stable and the features are great. Thank you!
On Fri, Jul 2, 2021 at 10:47 PM Jyers ***@***.***> wrote:
I don't know if it's actually a bug. My best guess is that resetting the
temp to make it cooler is messing with marlins thermal runaway safety
system. As cooling the heaters would cause the temp to change to slowly and
therefore trip the runaway protection. I could make the runaway values even
more lenient but obviously I don't want to overdo it and compromise the
safety of the machine.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1065 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEJTDDMEFLTNHA3RAOXPGCTTVZ22ZANCNFSM47I5YIXA>
.
--
Paul Hodara
|
|
Is someone able to check / reproduce the following behaviour, I just recognized? Running into Thermal runaway kill when I initiate a print with a 10° higher temperature for the first layer(s), once it changes down to the regular temperature. Configured values 245°C for initial 2 layers, then continue with 235°C. As far as I see the kill occurs once it changes set temperature to 245°C but is not yet cooled down to this value (showing actual of about 239°C). I mean yes actual temp is higher then the (new) set value, but does this mean it is not possible to have a 10° higher temp for initial layers? Or need the runaway protection to be a bit more patient is such situations? |
|
I just had another thermal runaway and the hotend temp was 5 degs cooler than what the print job called for. Once again a reboot fixed the problem. I will test agarthand issue ,an increased temp for initial layer, within the next day or two. Update - I tested again and did not start the print job until the hotend temp was over 10 degs below print job temp and still had a thermal runaway. It seems I don't have the issue when there is at least a 40+ deg temp difference. I am going to try to narrow down. |
|
I am also facing the same issue. The error occurs if the target temperature is close to current temperature. Suppose I preheated PLA then clicked on cooldown and after 1 min if I preheat PLA again I get the error. Sometimes it also occurs before printing. |
|
Only solution I have found is to reboot printer then let print job bring up temperature |
But that is not exactly a solution right? You have to wait for your printer to cool down at least 10°C on the bed and heat up again. |
|
Yes not a fix, It is a workaround. I am not familiar with Mriscoc. It appears to give you a lot of control of the colors in the GUI. What I really like about the Marlin Jyers build is all the advanced options such as PID autotune and many others see: https://github.com/Jyers/Marlin/wiki/Update-Notes |
|
The reason Mriscoc doesn't have this problem is his fork still uses the stock thermal runaway settings, which are very loose and not the safest. However I believe all of this can be fixed by tuning them slightly without putting them all the way back to stock. I'll give it a try and anyone here compiling their own version can weigh in. |
|
I've tuned the settings a bit now. Let me know if anyone compiling their own can still manage to recreate the issue with these new settings. |
|
@Jyers These are the settings I use and have no thermal error. |
|
I also use those numbers for the temps, except for the bed. No more thermal
runaway ever since.
Op za 10 jul. 2021 om 01:15 schreef Cal-LF ***@***.***>
… @Jyers <https://github.com/Jyers> These are the settings I use and have
no thermal error.
225 #define THERMAL_PROTECTION_PERIOD 30 // Seconds
245 #define WATCH_TEMP_PERIOD 30 // Seconds
246 #define WATCH_TEMP_INCREASE 3 // Degrees Celsius
253 #define THERMAL_PROTECTION_BED_PERIOD 180 // Seconds
259 #define WATCH_BED_TEMP_PERIOD 180 // Seconds
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1065 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGXIODJAP2F26F5C2MX4FX3TW57JRANCNFSM47I5YIXA>
.
|
Thank you so much! I think the issue is solved. |
|
I am not sure this is the appropriate place to ask for help, if not please let me know. To confirm I have everything installed correctly I downloaded the marlin nightly bugfix code base and when I go to build I have two environment options: If I use STM321F103RET6_creality this fails but if I use STM321F103RET6_creality_maple the build is successful. |
Uninstall everything install VSCode then install platformIO extension then install Auto Build Marlin Extension. Open the folder in VSCode. Copy the appropriate config.h and config_adv.h files. then go to Auto Build Marlin tab and press build. It will compile a bin file. |
|
K will try now. Thanks |
|
I am copying the header/config files from /configuration files/jyers's Config to /Marlin and getting the same errors: In file included from Marlin\src\HAL\STM32F1../../inc/MarlinConfig.h:49:0, Environment Status Duration STM32F103RET6_creality FAILED 00:00:13.578 |
|
Atom extension is not used. Compiling steps for Jyres FW. |
|
You can not use Jyres config files. They are for his particular setup. The E3V2 templates are the correct config files to use. |
|
Hmm the one I downloaded was Marlin-Temperature-Issue-Testing.zip. I just downloaded Marlin-Ender_3_V2_JyersUI.zip is this the correct one? |
|
Yes, the default on the top of the list. |
|
@phodara It may be better to open a discussion topic rather than be off topic in this thread. |
|
Thank you @Cal-LF it worked! :-) |
|
@phodara Just as a reference, these are my changes from Jyres default for my configs. They are not all required for my printer but set some different defaults and temps for safety. |
|
Thnx |
|
Is there a new build with this fixed? Or does one have to manually compile? I was experiencing this daily which is really annoying as I moved temps between preheat and ideal quite often. Thanks |
|
@jiriteach There is no new release but it should be soon. Mr. Myers has done a lot of merge cleanup and adjusted the temp settings for heating failure. |
|
I did a manual compile and It worked flawlessly. I no longer have temperature issues. |
|
@jiriteach Yes, there should be a release soon. I've had my hands a bit full with MarlinFirmware#22422 but I'll try to get a new release out today or tomorrow. @phodara Glad to here it's working well! Seems like we've finally got it tuned for max safety with little to no false trips. |
|
Thank you! |
|
Awesome! Thanks all and to @Jyers for the excellent work on this. Looking forward to the new release. |
|
Just installed the new release and for it seems to fix the problem. After several tries I was not able to reproduce my issues any more. Thanks for the adjustments. Will monitor behavior closely for the next prints and let you know if anything similar occurs. |
|
Great! I'll mark this as closed for now. Hopefully we've got it sorted 🥳 |
and others
Description
Heating failures occur when adjusting temps after preheating bed
Steps to Reproduce
Expected behavior: The printer should adjust the temps to the specified targets
Actual behavior: Printer gives a heating failure error, beeps loudly, and requires a physical power off/on, regardless of temp
Additional Information
The text was updated successfully, but these errors were encountered: