Error: Heater 0 fault: heater monitor 0 was triggered
-
@dmbgo said in Error: Heater 0 fault: heater monitor 0 was triggered:
M303 H0 P0.4 S120
Why did you reduce the PWM factor so much?
-
@dmbgo said in Error: Heater 0 fault: heater monitor 0 was triggered:
Hmmm, I seem to have this error when doing the Autotune:
1/14/2021, 12:34:32 PM Auto tune cancelled because target temperature was not reached
1/14/2021, 12:04:32 PM Auto tune starting phase 1, heater on
1/14/2021, 12:04:26 PMAutotune didn't work, the second attempt at autotune led to the error above, however printing with the heatbed PID settings from an earlier firmware version that did successfully autotune, I have not experienced anymore heatbed errors.
Given that the errors were very constant, I think that it might be fixed.
Thanks! -
Oh and the reduction of the PWM factor was from the example at:
https://duet3d.dozuki.com/Wiki/Tuning_the_heater_temperature_control -
Yes the previous tuned values should still be valid.
I would try tuning again with full power to see if it has better luck hitting the commanded temp.
-
It's just an example of how the power factor can be used. Normally you'd want to tune at full power. I'm going to change that example. Actually I don't see that example at all in that tuning link, but I did find it in the M303 entry in the gcode wiki and have changed it to use 100%. The only times you'd want to use that is with an overpowered heater that is throwing "heating too fast" errors.
-
That makes sense Phaedrux. I was wondering why it was 40%. Given that the errors seem to have gone after the FW update, and the bed is stable, do you see any reason not to move on?
-
Nope, I think you're good to go.
-
Thanks for your help.
