Do you know at what temperature they will give the warning? and without a thermistor is this something the board is reading through the motor wires or is it the connection at the board that is getting hot?

We keep getting a warning over and over
Warning High Temperature reported by driver(s) 2
But we are not showing any faults and temperatures are good
Is driver(s) 2, heater 2? or is this not the driver 2 but 2 drivers? and if so is there way to find out which drivers and how to fix the warning?
MCU is running at 36C

Duet WiFi 1.02 or later + DueX5 Firmware Version: 2.05 (2019-12-13b1)

Thank You

Everything was working fine yesterday, but today we went to start a job and the print never starts, just processing

we have tried sending a different job, and even the old turn off and back on

we ran a m122 but really don't know what it might dhow as the problem that we are missing

8:11:34 AM=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05 running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DLM-996RU-N85T0-6J1D4-3SJ6K-TAVZR
Used output buffers: 1 of 24 (11 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 94196 of which 0 recycled
Exception stack ram used: 424
Never used ram: 10740
Tasks: NETWORK(ready,628) HEAT(blocked,1176) DUEX(suspended,160) MAIN(running,3728) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:07:25 ago, cause: software
Last software reset at 2020-10-14 08:04, reason: User, spinning module GCodes, available RAM 10764 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 20.1ms, max retries 0
MCU temperature: min 32.1, current 32.4, max 33.2
Supply voltage: min 23.3, current 24.1, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max 0/538
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Driver 5: standstill, SG min/max not available
Driver 6: standstill, SG min/max not available
Driver 7: standstill, SG min/max not available
Driver 8: standstill, SG min/max not available
Driver 9: standstill, SG min/max not available
Date/time: 2020-10-14 08:11:33
Cache data hit count 1339471581
Slowest loop: 55.31ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 158, MaxWait: 101266ms
Bed compensation in use: mesh, comp offset 0.273
=== DDARing ===
Scheduled moves: 6, completed moves: 6, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = 5 -1
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.2
Heater 5 is on, I-accum = 0.7
=== GCodes ===
Segments left: 0
Stack records: 2 allocated, 0 in use
Movement lock held by file
http is idle in state(s) 0
telnet is idle in state(s) 0
file is doing "M116 " in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 30.55ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 2 of 8

• WiFi -
  Network state is running
  WiFi module is connected to access point
  Failed messages: pending 0, notready 0, noresp 0
  WiFi firmware version 1.23
  WiFi MAC address ec:fa:bc:5b:41:b9
  WiFi Vcc 3.38, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 26184
  WiFi IP address 192.168.5.248
  WiFi signal strength -56dBm, reconnections 0, sleep mode modem
  Socket states: 0 0 0 0 0 0 0 0
  === Filament sensors ===
  Extruder 0 sensor: ok
  Extruder 1 sensor: ok

Duet WiFi 1.02 or later + DueX5 Firmware Version: 2.05 (2019-12-13b1)
Thank You

Alright after a lot of trial and error I have figured out what my problem was in case anyone else runs into it this seems to be working

;E4:
M141 H5 ; Heater H4 is the Chamber Heater
M143 H5 S100 ; Set max chamber temp to 100c
M305 S"Chamber temp" P5 T100000 B3988 C0 ; heater 5 is monitored by a 100K
thermistor with B=3988
;M307 H5 ; report the process parameters for heater 5

That fixed that issue but I still have a heater fault after doing calibration, I calibrated to 50 and after everything was done, I tried just running to 45 and getting the rising to slowly fault?

9:24:07 AM
Error: Heating fault on heater 5, temperature rising much more slowly than the expected 0.4°C/sec
9:23:51 AM
M141 S45
9:23:45 AM
M141 P0 S0
9:21:34 AM
Connection established!
9:21:16 AM
Disconnected.
9:20:42 AM
M307 H5
Heater 5 model: gain 340.0, time constant 140.0, dead time 5.5, max PWM 1.00, calibration voltage 0.0, mode PID, inverted no, frequency default
Computed PID parameters for setpoint change: P13.4, I0.482, D51.4
Computed PID parameters for load change: P13.4
9:20:09 AM
M500
9:18:38 AM
Auto tune phase 3, peak temperature was 50.6
9:18:28 AM
Auto tune phase 2, heater off
9:16:35 AM
Auto tune phase 1, heater on
9:16:30 AM
M303 H5 S50
Auto tuning heater 5 using target temperature 50.0°C and PWM 1.00 - do not leave printer unattended

Alright, everything seems to be working except M500?

7:42:59 AM M500
Warning: No M501 command was executed in config.g
7:40:49 AM Auto tune heater 5 completed in 1137 sec
Use M307 H5 to see the result, or M500 to save the result in config-override.g
7:33:05 AM Auto tune phase 3, peak temperature was 55.2
7:33:02 AM Auto tune phase 2, heater off
7:21:57 AM Auto tune phase 1, heater on
7:21:52 AM M303 H5 S55
Auto tuning heater 5 using target temperature 55.0°C and PWM 1.00 - do not leave printer unattended

Does this mean the M500 didn't save and I need to do something else?

So I See what the problem was, we had the same code in twice but now working with

;E4:
"M141 H5" ; Heater H4 is the Chamber Heater
"M143 H5 S100" ; Set max chamber temp to 100c
"M305 S"Chamber temp" P5 T100000 B3988 C0" ; heater 5 is monitored by a 100K
thermistor with B=3988
"M307 H5" ; report the process parameters for heater 5

The only problem we have now is
Error: Heating fault on heater 5, temperature rising much more slowly than the expected 1.8°C/sec

are we missing something, or need to do the PID calibration for our M307 command?
Thank You

We are now connecting a relay to E4 to run a relay for chamber heater so do I change the thermistor from
"M305 S"Chamber temp" P103 T100000 B3988 C0 X5"
to
"M305 S"Chamber temp" P5 T100000 B3988 C0"
and use
"M141 H5" ; Heater H5 is the Chamber Heater
"M305 P103 T100000 B3950" ; heater 4 is monitored by a 100K thermistor with
B=3950
to turn the chamber heater on?
The dash board will show it turning on but the LED on the duex5 E4 does not turn on

We are running a high temp bed heater for our printer so I used a fan output off the Duex5 board
"M106 P3 S1; Set fan 3 value for bed relay to on"
and it turns on
Will I be able to put
"M106 P3 S0" in the slicer end of print, to turn the relay off, or do I need to add something he else to the Config G?

Duet WiFi 1.02 or later + DueX5 Firmware Version: 2.05 (2019-12-13b1)

Thank You

Worked Perfect, Thank You