Heater fault on heated bed because it's rising to slow.
-
@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
-
@joeko said in Heater fault on heated bed because it's rising to slow.:
@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
Well in that case it looks like the heater tuning needs more work @dc42
-
@exerqtor said in Heater fault on heated bed because it's rising to slow.:
Well in that case it looks like the heater tuning needs more work
Actually, I have more heater problems as well with the b7 than I had with the b6. Instead of one error while heating up that just could be restarted I now have to restart it three times. And I have done the heater tuning (pid calibration).
Thing is a have a active carbon filter under the bed where the fans kicks in at 65C. Although it's a very low airflow it seems to disturb the heating process.
I would like an option to just turn all this control off. Max temp supervision is enough for me as far as I can understand it now.
Sorry to hog in in this thread.
-
Short feedback from my side, the problem is not solved
The Result from the pid tuning with RFF 3.4.b6:
M307 H0 R0.460 C286.278:286.278 D0.90 S1.00 V24.3 B0 I0and the result from PID tuning with RRF 3.4.b7:
M307 H0 R0.484 K0.438:0.000 D0.85 E1.35 S1.00 B0and the error:
Error: Heater 0 fault: temperature rising too slowly: expected 0.43°C/sec measured 0.19°C/secHypercube-Evolution-Hybrid, Piezo Orion, Orbiter
Duet WiFi 1.02 or later + DueX5
RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.0beta4 (2021-09-27 11:30:36)
Duet WiFi Server: 1.26
Duet Web Control 3.4.0beta4 (2021-09-27) -
-
@hestiahuang said in Heater fault on heated bed because it's rising to slow.:
@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)
Quoted here.
However I don't have dropbox, and can't share my firmware here. Good Luck! -
@hestiahuang said in Heater fault on heated bed because it's rising to slow.:
@hestiahuang said in Heater fault on heated bed because it's rising to slow.:
@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 tooThen 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)
Quoted here.
However I don't have dropbox, and can't share my firmware here. Good Luck!Highlight the code for you all again.
I adjusted the factor 0.5 to small value simplely =>
[RepRapFirmware\src\Heating\LocalHeater.cpp] => Line#317 => if (actualTemperatureRise < expectedTemperatureRise * 0.5) -
@hestiahuang your workaround is not for everybody to make, so the easier way is to half the R value and the bed is heating without error
-
@siam I want to say even I use bangbang mode the issue is still, bangbang is using the full power(24V) already. So code change is the only way to me.
-
@siam said in Heater fault on heated bed because it's rising to slow.:
Short feedback from my side, the problem is not solved
The Result from the pid tuning with RFF 3.4.b6:
M307 H0 R0.460 C286.278:286.278 D0.90 S1.00 V24.3 B0 I0and the result from PID tuning with RRF 3.4.b7:
M307 H0 R0.484 K0.438:0.000 D0.85 E1.35 S1.00 B0and the error:
Error: Heater 0 fault: temperature rising too slowly: expected 0.43°C/sec measured 0.19°C/secPlease post the temperature plot while heating up the bed, to help me diagnose this.
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 here you can download a short video:
Hypercube-Evolution-Hybrid, Piezo Orion, Orbiter
Duet WiFi 1.02 or later + DueX5
RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.0beta4 (2021-09-27 11:30:36)
Duet WiFi Server: 1.26
Duet Web Control 3.4.0beta4 (2021-09-27) -
@dc42 said in Heater fault on heated bed because it's rising to slow.:
@siam said in Heater fault on heated bed because it's rising to slow.:
Short feedback from my side, the problem is not solved
The Result from the pid tuning with RFF 3.4.b6:
M307 H0 R0.460 C286.278:286.278 D0.90 S1.00 V24.3 B0 I0and the result from PID tuning with RRF 3.4.b7:
M307 H0 R0.484 K0.438:0.000 D0.85 E1.35 S1.00 B0and the error:
Error: Heater 0 fault: temperature rising too slowly: expected 0.43°C/sec measured 0.19°C/secPlease post the temperature plot while heating up the bed, to help me diagnose this.
yes, the same issue, I mean too.
-
@dc42 said in Heater fault on heated bed because it's rising to slow.:
@siam said in Heater fault on heated bed because it's rising to slow.:
Short feedback from my side, the problem is not solved
The Result from the pid tuning with RFF 3.4.b6:
M307 H0 R0.460 C286.278:286.278 D0.90 S1.00 V24.3 B0 I0and the result from PID tuning with RRF 3.4.b7:
M307 H0 R0.484 K0.438:0.000 D0.85 E1.35 S1.00 B0and the error:
Error: Heater 0 fault: temperature rising too slowly: expected 0.43°C/sec measured 0.19°C/secPlease post the temperature plot while heating up the bed, to help me diagnose this.
Want to confirm that, the same printer with different firmware, such as rrf and klipper, no issue on klipper
-
@dc42 said in Heater fault on heated bed because it's rising to slow.:
@siam said in Heater fault on heated bed because it's rising to slow.:
Short feedback from my side, the problem is not solved
The Result from the pid tuning with RFF 3.4.b6:
M307 H0 R0.460 C286.278:286.278 D0.90 S1.00 V24.3 B0 I0and the result from PID tuning with RRF 3.4.b7:
M307 H0 R0.484 K0.438:0.000 D0.85 E1.35 S1.00 B0and the error:
Error: Heater 0 fault: temperature rising too slowly: expected 0.43°C/sec measured 0.19°C/secPlease post the temperature plot while heating up the bed, to help me diagnose this.
For the bed heater case above, it is very normal that take 5~10mins to heat the bed from around 20°C to around 80°C, (80°C-20°C) / 0.19°C/sec /60sec/min=5.26min. So I think 'the quick factor' is good to apply to tools heater but not for bed heater.
