Heater fault on heated bed because it's rising to slow.
-
@arnold_r_clark
I'm also seeing similar behavior since updating to 3.4.0b6 (from 3.3.0)
My bed heater faults very often while initially warming up. And I can also clear the fault and continue heating, but very annoying.
Re-running PID tuning did not improve the situation.
-
Hi,
Try to use the half of the computed R value from the PID Tuning, This is how it works with my printer
https://forum.duet3d.com/topic/25321/bed-heater-fault-3-4-b5
-
@pfn There are quite a few fixes post beta6: https://github.com/Duet3D/RepRapFirmware/commits/3.4-dev
Some of these may impact the problem you are seeing...
https://github.com/Duet3D/RepRapFirmware/commit/37b4e02726993763b477181b6aa918089e2210b4
https://github.com/Duet3D/RepRapFirmware/commit/1e0e6c99252dee6aa20194f212aca3be6e68415a -
@gloomyandy thanks for digging! looks like known issues that will be resolved in the next beta/rc
-
Well there you go, just have to adjust the heating rate until b7 / RC1 sees day then
-
@gloomyandy Thanks for the info.
I thought that my Nevermore carbon recirculation filter with fans was responisble for the heater errors.
Looking forward to the next beta release then
-
@gixxerfast Just to be clear, I'm not saying that the above changes will fix the problem, just that some things have been changed! Will need to be tested with the next release I guess?
-
@gloomyandy said in Heater fault on heated bed because it's rising to slow.:
@gixxerfast Just to be clear, I'm not saying that the above changes will fix the problem, just that some things have been changed! Will need to be tested with the next release I guess?
@dc42 Guess this is something you could either confirm or deny?
-
Heater 0 fault: temperature rising too slowly: expected 0.44°C/sec measured 0.21°C/sec
Build the new source code after Beta6, the same.
Heater 0 fault: temperature rising too slowly: expected 0.44°C/sec measured 0.21°C/sec
-
@hestiahuang did you run M303 heater tuning on the bed heater, and save the M307 result?
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42
yes, I did. Ran Auto PID and saved, also restarted. But still failed, even I used bangbang mode, full speed, I mean.
After above, I got this too
Then I changed the code and built Beta7 version, everything looks good now.
I adjusted the factor 0.5 to small value simplely => RepRapFirmware\src\Heating\LocalHeater.cpp => Line#317 => if (actualTemperatureRise < expectedTemperatureRise * 0.5)
-
@dc42 I guess this should be new good feature, it will be perfect if it is better to enlarge the limitation. Or can have parameter to set expected rate.
-
Need to resume my printer can print first, so I call it simple way...
-
@dc42
Read from change history, issue is involved from Beta3 and keeping improving.
-
-
@hestiahuang we have made changes in 3.4.0beta 7 that we believe resolve the majority of these cases.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 You did great! Thank you so much!
-
now with beta7 i also get this error. with rrf 3.3 all was fine
-
undefined joeko referenced this topic
-
@joeko
Have you re tuned the heater after upgrading to b7? I haven't gotten around to test mine btw, so just asking out of curiosity
-
@exerqtor said in Heater fault on heated bed because it's rising to slow.:
@joeko
Have you re tuned the heater after upgrading to b7? I haven't gotten around to test mine btw, so just asking out of curiosityyes after update from 3.3 to this beta7 i did an pid tuning for bed and hotend with m500. with 3.3 there was no problem. i reduced the r in 307 to 0.19 and was able to heat the bed and print
