1.1.0-RC10 hotbed thermal runaway during G29

[Angel996]

I've had this start up script for ages. Printer is working fine, both temp sensors are ok.

I flashed 1.1.0-RC10 and now I'm constantly getting a thermal runaway for bed exactly AFTER G29 is complete. Looks like the termal runaway routine is not aware of G29 running and thinks it's an emergency. I've set WATCH_BED_TEMP_PERIOD to 300, but it did not help. Hotbed is in bang-bang mode, using a relay.

Here is the error msg:

> Error:Thermal Runaway, system stopped! Heater_ID: bed
> [ERROR] Error:Thermal Runaway, system stopped! Heater_ID: bed
> 
> Error:Printer halted. kill() called!
> [ERROR] Error:Printer halted. kill() called!

Here is the script:

M80; on
M84 ; disable motors
M190 S105 ; set/wait for bed temperature
M104 S180 ; set extruder temperature
M190 S110 ; set/wait bed temperature
M104 S200 ; set extruder temperature and start calibrating right away
G21; metric
G91 ; relative
G1 F5000 Z5; raise Z
G90; absolute
G28
G29; run auto leveling
G1 Z0; // go to actual zero
G92 Z0.3; the bigger the value, the closer to the bed
G1 F200 Z10; raise Z
G1 F6000 X60 Y100; move to almost center
G1 F200 Z5; lower Z
M84; disable motors
M109 S230 ; set/wait extruder temperature (prevents bleeding)

Thanks.

[Anxles]

Just tested Bugfix version, STILL have problem with temperature jumps on the bed, huuge this time: a few thousand degrees, the difference is it's not stopping the print this time.

[Sebastianv650]

Then it might be a different problem. If you also get spikes with rc6, this means it has nothing to do with the interrupts because the change was applied later.

[thinkyhead]

It seems like something is interrupting the ADC sensor reading, causing bad values. I'm not sure why G29 is especially causing this. I would expect it to also be a problem during G28 (especially if Z needs to move far).

[Anxles]

I had the spikes at RC6, but a FEW degrees only and very rare. At RC8 the spikes are huge, often, and every few spikes temperature bars dissapears completly for some miliseconds also which didn,t happen at RC6.

I found another problem which didn't exist on other firmware. I am loosing control of different parts of printer lets say randomly (didn't happen yet during print) After finishing print I am trying to prepare next one and cannot heat the printer, I get wrong readings, cannot reconnect host to the printer (loosing COM connection) restearting host doesn't help. Restarting PC does. I happens only on RCbugfix. I'm not sure if its firmware problem, but it does'nt happen on Regular Marlin.

[Angel996]

Just a small update.

I am building a CO2 laser cutter, so I decided to use Marlin for control. My device does not have any heaters or temp sensors, the temp reading is -15. However, in idle state, sometimes I get the "Heating failed" error and Marlin is killed although I never sent any heater related G-Codes.

[Sebastianv650]

@Angel996 can you try if #5949 fixes your issue on the laser? Do you still have problems with normal printer since #5829?

[Sebastianv650]

Why you get a temperature reading when there is no temp. sensor - are you sure all sensors are set to 0 and no temperature protection is enabled?

[erikkallen]

I ran into the same issue with the runaway heater, the way I fixed it was to change

define THERMAL_PROTECTION_PERIOD 40 // Seconds

define THERMAL_PROTECTION_HYSTERESIS 4 // Degrees Celsius

in Configuration_adv.h the default settings where to strict for my slow heater (the problem in my case was that when both the extruder and the bed where heating up the bed probably reacted a bit slower) Maybe this helps someone

[mbauer599]

Don't know if this helps anybody, but I was having this same issue during print with my delta. Seemingly random thermal runaways in the middle of prints. Pounded my head against the wall for some time with this and eventually realized that my board was getting to hot (It was under the heat bed, too close I guess). Put a fan on the board and haven't had this issue since.

[gosewski]

I can confirm that the problem with bed sensor thermal runaway exists in Marlin 1.1 and it is strictly software related issue. I had a Marlin 1.0 previously loaded to my Teensy board and there was newer thermal runaway problem. After flashing Marlin 1.1 the problem arised. After several config adjustments there were still random error occurances. I decided to flash back Marlin 1.0 and problem dissapeared. Therefore, my conslusion is that there is saome bug in the Marlin 1.1 code. By the way, the sound (beep) function was much better in Marlin 1.0, at least the frequency of the beep was predictable, what I can not say about Marlin 1.1.

[thinkyhead]

@gosewski — I use heated beds on all my machines and so far I have not seen any thermal runaway with any version of Marlin. Please test with the latest bugfix-1.1.x (and/or bugfix-2.0.x) branch and if you get spurious thermal runaway errors then please post a new issue with all the information requested in the issue template.

The tone player in Marlin 1.1.x is now asynchronous where the tone player in 1.0 was a blocking function. This may have an effect on its frequency on some boards.

[gosewski]

I wrote my last message just to save time and money for all the Marlin users experiencing thermal runaway problems and trying to fix it by replacing thermistors, instaling/replacing fans and doing all other hardware related things. Regarding tone player, I can’t see any adventages of having not working or badly working asynchoronus one over a very well working synchronous.

[thinkyhead]

How about a well-working asynchronous?

With any luck someone will eventually come along to assist us in resolving your issues.

[gosewski]

Sure, every well-working function is welcome :) I keep my finger crossed for Marlin firmware. Now I am focused on printing but having more time I’ll try to debug this thermal runaway as I did with Bluetooth function for Teensy. Cheers, Greg

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.