Heatbed issue - Heater 0 fault (...)

esobreiro

Here we go...

Heater 0 fault: temperature rising much more slowly than the expected 1.6°C/sec - Heatebed.

Its a big heatbed originally from Tronxy X55 printer (30cmx30cm).

Following my config.g heater commands:

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.0 ; disable bang-bang mode for heater and set PWM limit era B0
M143 H1 S280

Its a 600w 24v power source.
Board: Duet 2 WiFi (2WiFi)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.2.2 (2021-02-11)
Duet WiFi Server Version: 1.25

Thank you very much!

Regards,

Erick

fcwilt

@esobreiro

You need to run heater tuning - see M303.

Frederick

esobreiro

Thank you!

Warning: heater behaviour was not consistent during tuning
Auto tuning heater 0 completed after 4 idle and 25 tuning cycles in 4186 seconds. This heater needs the following M307 command:
M307 H0 R0.326 C543.4 D9.46 S1.00 V23.6
Send M500 to save this command in config-override.g

Despite the error, the results seems ok:

Phaedrux

It means that the temperatures expected were consistent over the course of the tuning. Depending on how off it was it might or might not be a problem. The algorithm is new and may have some room for improvement, so thanks for the report. If it's working well though and maintains a steady temp you should be fine to use it.