Duex5 shown as Duex2
-
Hi, I am trying to wire a Duex5 but it shows as Duex2 in the M115 command when connected over USB.
Is there any configuration to change the board type? or is this a bug? -
@miguel it is automatically detected based on some resistors on the port expander on the Duex5. can you send a picture of the board, especially around this area:
-
@T3P3Tony This is what I am able to capture right now. Let me know if you need different or better quality images.
-
@miguel that looks correct - the board ID resistor is populated which should indicate Duex5.
Can you paste the M122 report.
-
@T3P3Tony
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.01(RTOS) running on Duet Ethernet 1.02 or later + DueX2
Board ID: 08DGM-956GU-DJMSN-6J9D6-3S46L-9VQRH
Used output buffers: 1 of 20 (12 max)
=== RTOS ===
Static ram: 28476
Dynamic ram: 95552 of which 0 recycled
Exception stack ram used: 276
Never used ram: 6768
Tasks: NETWORK(ready,464) HEAT(blocked,1248) MAIN(running,4324)
Owned mutexes:
=== Platform ===
Last reset 00:00:24 ago, cause: reset button or watchdog
Last software reset at 2018-08-22 16:05, reason: Heat task stuck, spinning module Platform, available RAM 6376 bytes (slot 3)
Software reset code 0x40a0 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x20005344 Task 0x4e49414d
Stack: 00403181 00441a40 81000000 460ca000 3ff00000 00000000 00000000 3e178897 3e1cd04f 41880000 3e3a3fd4 3e639b49 3e9250f0 3c942078 3eccd653 be09b238 397d66d2 80000000 00007530 20000010 0043a809 00000000 004393ef
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 34.2, current 36.9, max 37.1
Supply voltage: min 24.4, current 24.5, max 24.5, under voltage events: 0, over voltage events: 0
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
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
Expansion motor(s) stall indication: no
Date/time: 2018-08-22 16:14:58
Slowest loop: 4.25ms; fastest: 0.07ms
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
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
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: 5.09ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
Interface state: 5
=== Expansion ===
DueX I2C errors 0
.
.
.
.
.Sometimes I manage to get the board correctly identified by power cycling or resetting the board. Here is a M122 with the Duex5 correctly identified:
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.01(RTOS) running on Duet Ethernet 1.02 or later + DueX5
Board ID: 08DGM-956GU-DJMSN-6J9D6-3S46L-9VQRH
Used output buffers: 3 of 20 (17 max)
=== RTOS ===
Static ram: 28476
Dynamic ram: 95660 of which 0 recycled
Exception stack ram used: 356
Never used ram: 6580
Tasks: NETWORK(ready,328) HEAT(blocked,1248) MAIN(running,3912)
Owned mutexes:
=== Platform ===
Last reset 00:04:10 ago, cause: reset button or watchdog
Last software reset at 2018-08-22 16:05, reason: Heat task stuck, spinning module Platform, available RAM 6376 bytes (slot 3)
Software reset code 0x40a0 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x20005344 Task 0x4e49414d
Stack: 00403181 00441a40 81000000 460ca000 3ff00000 00000000 00000000 3e178897 3e1cd04f 41880000 3e3a3fd4 3e639b49 3e9250f0 3c942078 3eccd653 be09b238 397d66d2 80000000 00007530 20000010 0043a809 00000000 004393ef
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 35.7, current 37.5, max 37.6
Supply voltage: min 24.4, current 24.4, max 24.6, under voltage events: 0, over voltage events: 0
Driver 0: standstill, SG min/max 0/227
Driver 1: standstill, SG min/max 0/205
Driver 2: standstill, SG min/max 0/1023
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
Expansion motor(s) stall indication: no
Date/time: 2018-08-22 16:13:05
Slowest loop: 3.40ms; fastest: 0.08ms
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 239, MaxWait: 238706ms, Underruns: 0, 0
Scheduled moves: 8, completed moves: 8
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 4 allocated, 0 in use
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
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: 5.22ms; fastest: 0.03ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
Interface state: 5
=== Expansion ===
DueX I2C errors 0 -
-
I agree, intermittent issue with U8 is the most likely cause. Please ask for your DueX5 to be replaced under warranty. https://www.duet3d.com/warranty
