Duet2 wifi + Duex5 board thermistor issue
-
I recently got a Duet2 Wifi and Duex5 expansion board for use with the e3d tool changer, but the two thermistors on the Deux expansion board are showing the wrong temp readings. The thermistors on the Duet2 show room temp(22C), but the ones on the Duex show 7C. swapping thermistor connections shows correct temperatures on any connection to the Duet2. Am I missing something here? Should I start a warranty claim or something?
In configuration file:
M308 S1 P"e0temp" Y"thermistor" A"T0" T100000 B4725 C7.06e-8 ; Set thermistor
M950 H1 C"e0heat" T1 ; Extruder 0 heater
M143 H1 S305 ; Set temperature limit for heater 1 to 300CM308 S2 P"e1temp" Y"thermistor" A"T1" T100000 B4725 C7.06e-8 ; Set thermistor
M950 H2 C"e1heat" T2 ; Extruder 0 heater
M143 H2 S305 ; Set temperature limit for heater 2 to 300CM308 S3 P"e2temp" Y"thermistor" A"T2" T100000 B4725 C7.06e-8 ; Set thermistor
M950 H3 C"duex.e2heat" T3 ; Extruder 0 heater
M143 H3 S305 ; Set temperature limit for heater 3 to 300CM308 S4 P"e3temp" Y"thermistor" A"T3" T100000 B4725 C7.06e-8 ; Set thermistor
M950 H4 C"duex.e3heat" T4 ; Extruder 0 heater
M143 H4 S305 ; Set temperature limit for heater 4 to 300C
-
Firmware version?
-
@phaedrux firmware is 3.3 (2021-06-15)
diagnostic stuff
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later + DueX5
Board ID: 0JD0M-9X6JA-JUNSN-6J9FA-3S86T-KURZV
Used output buffers: 3 of 24 (16 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 77736 of which 0 recycled
Never used RAM 12804, free system stack 184 words
Tasks: NETWORK(ready,42.1%,237) HEAT(delaying,0.1%,330) Move(notifyWait,0.2%,319) DUEX(notifyWait,0.0%,24) MAIN(running,57.5%,417) IDLE(ready,0.1%,29), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 01:57:21 ago, cause: power up
Last software reset at 2021-12-19 14:24, reason: User, GCodes spinning, available RAM 12388, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 40.9, current 43.2, max 44.3
Supply voltage: min 22.4, current 23.4, max 23.8, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, standstill, SG min/max not available
Driver 1: position 0, standstill, SG min/max not available
Driver 2: position 0, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0, standstill, SG min/max not available
Driver 6: position 0, standstill, SG min/max not available
Driver 7: position 0, standstill, SG min/max not available
Driver 8: position 0, standstill, SG min/max not available
Driver 9: position 0, standstill, SG min/max not available
Driver 10: position 0
Driver 11: position 0
Date/time: 2021-12-20 23:24:44
Cache data hit count 4294967295
Slowest loop: 12.73ms; fastest: 0.17ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 4.4ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== DueX ===
Read count 1, 0.01 reads/min
=== Network ===
Slowest loop: 27.31ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8- WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.26
WiFi MAC address 48:3f:da:a6:dd:3b
WiFi Vcc 3.40, reset reason Power up
WiFi flash size 2097152, free heap 24880
WiFi IP address 192.168.1.91
WiFi signal strength -40dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
- WiFi -
-
@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 -
undefined Szalek referenced this topic
-
@szalek Awesome, Thank you so much!
-
@waffle there is now a 3.4.0beta7+1 build of RRF available, which auto detects the DueX version and sets the default series resistor value.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 said in Duet2 wifi + Duex5 board thermistor issue:
version
yeah, I saw the beta version, I just went with the latest stable release. I'll have to remember that for when I upgrade.
