DWC Temperature Chart goes upto 2000?

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?