DWC Temperature Chart goes upto 2000?

SIam

Check the cable and the thermistor when the thermistor port input shows to 2000C° then is the Thermistor disconnected or you have the wrong Thermistor port in your config.g defined

DocTrucker

Temperature sensors are behaving fine. Been doing a autotune on bed and hotend this morning.

It's like the web control remembered the first start with the RRF 2 config where the sensor readings were screwed. That was many machine re-starts ago.

jay_s_uk

@doctrucker can you check you have an M143 command for whichever heater is showing the 2000 degrees? this sets the upper limit for the chart I think

DocTrucker

@jay_s_uk Neither heater is showing 2000.

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T10000 B3988 ; 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 B0 S1.00                               ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0                                        ; map heated bed to heater 0
;M308 S1 P"spi.cs1" Y"rtd-max31865"             ; configure sensor 1 as pt100 via CS pin spi.cs1
;M305 P1 B4725 C7.060000e-8 R4700 ; https://e3d-online.dozuki.com/Guide/V6+RepRap+Firmware+Configuration/26

;e0temp
M308 S1 P"e0temp" Y"thermistor" B4725 C7.060000e-8 ; configure sensor 1 as thermistor via pin e0temp
M950 H1 C"e0heat" T1                           ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00                               ; disable bang-bang mode for heater  and set PWM limit

; Heater fault detection & handling.
M143 H0 S120 A0 C0    ; Raise a heater fault if heatbed exceeds 120C.
M143 H1 S255  A0 C0   ; Raise a heater fault if hotend exceeds 255C.
M143 H0 S10 A0 C1      ; Raise a heater fault if heatbed falls below 10C.
M143 H1 S5  A0 C1     ; Raise a heater fault if hotend falls below 5C.
M570 H0 P10 T10 S1    ; Allow a heat bed anomaly to persist for 10 seconds (P10) 
                      ; on the before raising a heater fault. Allow a 10C deviation 
                      ; from set point (T10) After 0.17 minutes of heater  fault
                      ; cancel the build (S0.17).
M570 H1 P10 T10 S1    ; Allow a hot end anomaly to persist for 10 seconds (P10)
                      ; on the before raising a heater fault. Allow a 
                      ; 10C deviation from set point (T10 - default) After 0  
                      ; minutes of heater fault cancel the build (S0.17).

; Fans
;M106 P0 S0 I0 F500 H-1         ; (Part cooling fan) Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off

; Fans
M950 F0 C"fan0" Q500                           ; create fan 0 on pin fan0 and set its frequency

; Tools
M563 P0 S"E3D V6 Hotend" D0 H1 F0              ; define tool 0
G10 P0 X0 Y0 Z0                                ; set tool 0 axis offsets
G10 P0 R100 S245                               ; set initial tool 0 active and standby temperatures to 0C

jay_s_uk

@doctrucker can you set a maximum in your config for each heater? I know you have the fault handling, but try something along the lines of

M143 H0 S120
M143 H1 S275

obviously adjust them to the maximum for your bed and tool.
Place the bed one after the M140 H0 and the other one after the M307 H1

droftarts

@doctrucker as @jay_s_uk says use M143, but set it for both heaters.

Ian

DocTrucker

@jay_s_uk @droftarts

You mean like I already have in the config file clip above?

@doctrucker said in DWC Temperature Chart goes upto 2000?:

[...clipped...]
M143 H0 S120 A0 C0    ; Raise a heater fault if heatbed exceeds 120C.
M143 H1 S255  A0 C0   ; Raise a heater fault if hotend exceeds 255C.
[...clipped...]

jay_s_uk

@doctrucker it might be cause you're not setting a P value for each one so the S value is being overwritten by the lines below?
I've not used the monitoring function but thats the way the wiki reads
https://duet3d.dozuki.com/Wiki/Gcode#Section_M143_in_RRF_3_01RC2_and_later

maybe something like

M143 H0 S120 P0 A0 C0
M143 H0 S10 P1 A0 C1

edit: I meant P1 on the second line. updated to reflect

DocTrucker

@jay_s_uk Running the M143 H[0/1] commands on the terminal sheds a little more light. Looks like the high and low need to be asigned to unique P numbers? Will try and see if the following improves...

14/04/2021, 09:33:17 	M143 H1
Heater 1 monitor 0 uses sensor 1 to generate a heater fault if the reading falls below 5.0°C
Heater 1 monitor 1 is disabled
Heater 1 monitor 2 is disabled
14/04/2021, 09:33:03 	M143 H0
Heater 0 monitor 0 uses sensor 0 to generate a heater fault if the reading falls below 10.0°C
Heater 0 monitor 1 is disabled
Heater 0 monitor 2 is disabled

DocTrucker

@jay_s_uk yup, "P" was the problem. Bit dodgy that as I had specifically set the upper and lower limits and had no idea they weren't being respected. Will read the release notes again to make sure that is clearly stated.

So the old code that did not work:

M143 H0 S120 A0 C0    ; Raise a heater fault if heatbed exceeds 120C.
M143 H1 S255  A0 C0   ; Raise a heater fault if hotend exceeds 255C.
M143 H0 S10 A0 C1     ; Raise a heater fault if heatbed falls below 10C.
M143 H1 S5  A0 C1     ; Raise a heater fault if hotend falls below 5C.

This needed to be:

M143 H0 S120 A0 C0 P0  ; Raise a heater fault if heatbed exceeds 120C.
M143 H1 S255  A0 C0 P0 ; Raise a heater fault if hotend exceeds 255C.
M143 H0 S10 A0 C1 P1   ; Raise a heater fault if heatbed falls below 10C.
M143 H1 S5  A0 C1 P1   ; Raise a heater fault if hotend falls below 5C.

Setting the lower limits after the upper caused the upper limits to be overwritten.

Gives the following console feedback:

14/04/2021, 09:36:38 	M143 H1
Heater 1 monitor 0 uses sensor 1 to generate a heater fault if the reading exceeds 255.0°C
Heater 1 monitor 1 uses sensor 1 to generate a heater fault if the reading falls below 5.0°C
Heater 1 monitor 2 is disabled
14/04/2021, 09:36:29 	M143 H0
Heater 0 monitor 0 uses sensor 0 to generate a heater fault if the reading exceeds 120.0°C
Heater 0 monitor 1 uses sensor 0 to generate a heater fault if the reading falls below 10.0°C
Heater 0 monitor 2 is disabled

jay_s_uk

@doctrucker looks like it was changed in RRF 1.20?

DocTrucker

@jay_s_uk I've skipped from RRF1 to RRF3. It was working when I did a full heater interlock test on RRF1 which I shared many months ago. Need to repeat that!

dc42

The meaning of the M143 P parameter was changed in RRF3. See https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M143_Maximum_heater_temperature.

DocTrucker

@dc42 perhaps flag a warning if no P parameter is used so it is harder to accidentally overwrite alarm conditions like I did?