@waffle I think that the reason is change in serial resistors on Duex v0.11 from 4k7 to 2k2 as mentioned here:
https://duet3d.dozuki.com/Wiki/Duex2_and_Duex5_Features#Section_PCB_revision_v0_Num_11
I encountered the same on Duex I received recently, the thermistors (and PT1000) are working as expected on Duex v0.10, but on v0.11 they behave the same as on your hardware (thermistor ~7 degree in room temperature, PT1000 ~360 degree), modification in M308 (or M305 for RRF2) gcode is required as mentioned in the link

Recently I received Duex5 v0.11 with changed serial resistors for temperature sensors and connected it do Duet2 Ethernet v1.04c. According to revision changelog from here:

"From RRF3.4 the Duex 5 version will be detected and the correct R values set in M308"

Although after installing RRF 3.4.0beta7 temperature readings from Duex v0.11 are wrong (thermistor shows 7°C and PT1000 shows 360°C in room temperature) until I add R2200 parameter to M308 commands in config.g. The readings of thermistor are similar to those discribed in thread:
https://forum.duet3d.com/topic/26480/duet2-wifi-duex5-board-thermistor-issue

Is there anything that I'm missing with Duex version detection mechanism? Is there a way to make Duet work with both Duex versions v0.10 and v0.11 out-of-the-box without changing M308?

Here are the commands used in config.g to configure sensors on Duex board:

M308 S3 P"duex.e2temp" Y"pt1000"                                                  ; configure sensor 3 as pt1000 on pin duex.e3temp
M950 H3 C"duex.e2heat" T3                                                         ; create heater output on duex.e3heat and map it to sensor 3

M308 S4 P"duex.e3temp" Y"thermistor"

@phaedrux
This exact board behaved like that from the very beginning while another daughetboard works fine with the same configuration and the rest of hardware.

Bought directly from Duet3D.

Hello!
I was trying to configure PT100 sensors on Duet2 (running RRF 2.05) with PT100 Daughterboard. I configured 2 virtual heaters for those 2 sensors:

M305 P100 X200 S"RTD1"
M305 P101 X201 S"RTD2"

Duet only returns "ok" for those commands, so I think that communication with MAX31865 chips is fine.

I can read the temperature from RTD2, but RTD1 always shows open circuit (2000.0 C). I tested with working PT100 sensors and with ~100 Ohm resistors - for both RTD2 works fine, RTD1 does not.

Hello!
I suspect I received a broken PT100 Daughterboard. It was bought directly from Duet3D about a month ago.

When I connect it to Duet2, connect PT100 sensors and try to configure the sensors with M305 command it returns:
Error: Failed to initialise RTD: bad response from sensor

I also have second PT100 Daughterboard working with second Duet2. The same Duet, sensors and configuration with only switched daughterboard works like a charm, so it looks like Daughterboard is a problem.

Recently I received Duex5 v0.11 with changed serial resistors for temperature sensors and connected it do Duet2 Ethernet v1.04c. According to revision changelog from here:

"From RRF3.4 the Duex 5 version will be detected and the correct R values set in M308"

Although after installing RRF 3.4.0beta7 temperature readings from Duex v0.11 are wrong (thermistor shows 7°C and PT1000 shows 360°C in room temperature) until I add R2200 parameter to M308 commands in config.g. The readings of thermistor are similar to those discribed in thread:
https://forum.duet3d.com/topic/26480/duet2-wifi-duex5-board-thermistor-issue

Is there anything that I'm missing with Duex version detection mechanism? Is there a way to make Duet work with both Duex versions v0.10 and v0.11 out-of-the-box without changing M308?

Here are the commands used in config.g to configure sensors on Duex board:

M308 S3 P"duex.e2temp" Y"pt1000"                                                  ; configure sensor 3 as pt1000 on pin duex.e3temp
M950 H3 C"duex.e2heat" T3                                                         ; create heater output on duex.e3heat and map it to sensor 3

M308 S4 P"duex.e3temp" Y"thermistor"

@waffle I think that the reason is change in serial resistors on Duex v0.11 from 4k7 to 2k2 as mentioned here:
https://duet3d.dozuki.com/Wiki/Duex2_and_Duex5_Features#Section_PCB_revision_v0_Num_11
I encountered the same on Duex I received recently, the thermistors (and PT1000) are working as expected on Duex v0.10, but on v0.11 they behave the same as on your hardware (thermistor ~7 degree in room temperature, PT1000 ~360 degree), modification in M308 (or M305 for RRF2) gcode is required as mentioned in the link

After config.g modifications result for M98 P"config.g":

ok

M122 results after boot and after sending fan control command (i.e. M106 P8 S255) in attached file, I2C errors start to show up after trying to control the fans:
M122_result.txt

DueX board was bought about a month ago from Duet3D with label number 1220X290, Duet board is a little older (also bought from Duet3D) and works fine with other DueX boards so I assume it's DueX board problem.

Re: External triggers don't work on Duex5

Hello!

I have a problem similar to one described in the thread linked above. Duex5 doesn't recognize signal on endstops (all of them) on Duex5. Tested with config.g and trigger6.g files included in linked thread.

When trying to enable FAN/LED 8 output, I2C errors occour and are listed in response for M122 command. Other Duex5 boards connected to the same Duet board work fine.

I also suspect SX1509 soldering, close-up photos attached

RRF 2.05.1
Duex5 v0.10
SD card with files rom factory, modified config.g and trigger6.g

config.g with added line: M581 E0:1:2:3:4:5:6 T6 S1 C0

; Configuration file for factory testing Duet Ethernet and Wifi with V2.05.1 firmware

*******************************************************************************************************************
FOR TESTING ONLY! USE https://configurator.reprapfirmware.org/ to generate configuration files for your printer!
*******************************************************************************************************************

 
; Communication and general
M111 S0                         ; Debug off
M550 PDuetTest					; Machine name and Netbios name (can be anything you like)
M551 Preprap                   	; Machine password (used for FTP)
 
*** Ethernet networking: The following lines are used for factory testing - PLEASE REMOVE THEM
 
M552 P192.168.1.34				; IP address
M554 P192.168.1.255				; Gateway
M553 P255.255.255.0				; Netmask
 
;*** End of factory test lines to be removed
 
;*** Networking
M552 S1					; Turn network on
 
M555 P2					; Set output to look like Marlin
G21						; Work in millimetres
G90						; Send absolute coordinates...
M83						; ...but relative extruder moves
 
; Axis and motor configuration
M569 P0 S1
M569 P1 S1
M569 P2 S1
M569 P3 S1
M569 P4 S1
M574 X2 Y2 Z2 S1
 
M665 R105.6 L215.0 B85 H250
M666 X0 Y0 Z0
M350 X16 Y16 Z16 E16:16 I1
M92 X80 Y80 Z80
M906 X1000 Y1000 Z1000 E800 I60
M201 X1000 Y1000 Z1000 E1000
M203 X20000 Y20000 Z20000 E3600
M566 X1200 Y1200 Z1200 E1200
 
; Thermistors
 
M305 P0 T100000 B3950 R4700 H30 L0
M305 P1 T100000 B3974 R4700 H30 L0
M305 P2 T100000 B3974 R4700 H30 L0
 
M570 S180
 
; Adjustments for dummy heaters on test rig
 
M307 H0 A250 C140 D5.5 B1
M307 H1 A250 C140 D5.5 B0
M307 H2 A250 C140 D5.5 B0
 
; Disable Fan 1 thermostatic mode
 
M106 P1 H-1
 
; Tool definitions
M563 P0 D0 H1
G10 P0 S0 R0
M563 P1 D1 H2
G10 P1 S0 R0
M92 E80:80
 
; Z probe and compensation definition
 
M558 P5 F100 T6000 X0 Y0 Z0 H3
G31 P100 X0 Y0 Z-0.25
 
 
M208 S1 Z-0.2
 
T0
 
;********************************************************************************
; M117 Use https://configurator.reprapfirmware.org/ to set up your printer config
;********************************************************************************
 
M581 E2:3:4:5:6 T6 S1 C0

trigger6.g

M291 R"Hello 6" P"World"