Heater Fault Not Working Bang-Bang Mode RRF3.1.1
-
Hello,
I have set up M570 commands for fault protection for a Duet wifi using RRF 3.1.1. I would expect the code below to give me a fault if the temperature of the heaters is not rising, but nothing happens. Any help, please?
Thanks in advance!
; Configuration file for Duet WiFi (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v2.1.8 on Sun Feb 02 2020 20:27:48 GMT-0800 (Pacific Standard Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"BetaMVP" ; set printer name M564 H0 ; move without homing M555 P2 ; marlin compatibility ;M570 H0 P20 T20 ; set heater 0 fault to persist time of 10s, deviation of 10C, fault time to 120s ;M570 H1 P1 T25 ; set heater 1 fault to persist time of 10s, deviation of 10C, fault time to 120s ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Heaters ;M140 H-1 disable heated bed (overrides default heater mapping) M308 S0 P"e0temp" Y"thermistor" T100000 B3950 ; configure sensor 0 as thermistor on pin e0temp M950 H0 C"e0heat" T0 ; create nozzle heater output on e0heat and map it to sensor 0 M143 H0 S80 ; set temperature limit for heater 0 to 80C M307 H0 B1 D600 C600 S0.2 ; set PID parameters disable bang-bang mode for heater and set PWM limit M308 S1 P"e1temp" Y"thermistor" T100000 B3950 ; configure sensor 1 as thermistor on pin e1temp M950 H1 C"e1heat" T1 ; create nozzle heater output on e1heat and map it to sensor 1 M143 H1 S80 ; set temperature limit for heater 1 to 80C M307 H1 A180 B1 D300 C600 S1.0 ; enable bang-bang mode for heater and set PWM limit M308 S2 P"bedtemp" Y"thermistor" T100000 B3950; configure sensor 2 as PT1000 on pin bedtemp M950 H2 C"bedheat" T2 ; create bed heater output on bedheat and map it to sensor 2 M143 H2 S90 ; set temperature limit for heater 2 to 90C M307 H2 B1 D300 C600 S0.2 ; enable bang-bang mode for the bed heater and set PWM limit M140 H2 ; map heated bed to heater 2 M570 H0 P4 T5 ; set heater 0 fault detection to 10s persist, 10C excursion, 120s fault M570 H1 P4 T5 ; set heater 1 fault detection to 10s persist, 10C excursion, 120s fault M570 H2 P4 T5 ; set heater 2 fault detection to 10s persist, 10C excursion, 120s fault ; Tools M563 P0 S"Liquid" D0 H0 F0 ; define tool 0 G10 P0 Z0 U0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C M563 P1 S"Heating Block" D1 H1 F1 ; define tool 1 G10 P1 Z0 U0 ; set tool 1 axis offsets G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0C M563 P2 S"Reservoir" D2 H2 F2 ; define tool 2 G10 P2 Z0 U0 ; set tool 2 axis offsets G10 P2 R0 S0 ; set initial tool 2 active and standby temperatures to 0C ; Custom settings are not defined -
@dieguito said in Heater Fault Not Working Bang-Bang Mode RRF3.1.1:
RRF 3.1.1
Update your firmware to 3.4
https://github.com/Duet3D/RepRapFirmware/releases/tag/3.4.0
You should be able to upload the full zip file.
What kind of a heater is this? Is PID tuning not a viable option?
What was the situation you expected to fault but didnt?
-
@phaedrux I unplugged a wire in my heater. I was expecting the duet to show me a "temperature is rising much more slowly than x.xC", but nothing showed up after waiting for 20 mins with different testing from the one in the config.g file I included.
I couldn't get rid of random "temperature rising much more slowly" spurious fault messages using PID control on the same heater after playing much with the settings, hence I had to implement bang-bang.
-
@dieguito
If you were not running a print file, or doing a PID tune then I believe that RRF does not monitor all heater faults.
Someone might confirm which conditions this may affect if that is still the case. -
Upgrading to 3.4 and setting up event handling would be the best way to go I think.
https://docs.duet3d.com/en/User_manual/RepRapFirmware/Events
