Issue with Duet3d 2 Ethernet Board
-
Hi, we are currently running into an issue with our Duet 2 Ethernet board where it claims there is a short to ground on driver 0 even though there are no stepper motors plugged in. What could be the cause of this issue and how can it be rectified?
-
Driver 0 may be damaged.
Can you send M122 and M98 P"config.g" in the Gcode console in DWC and post the results? Also post your config.g please.
When did it start giving that error? Was there ever a motor plugged into the driver?
Can you post some photos of the driver0 chip area?
-
This is the response to both commands from DWC.
8/10/2021, 2:53:00 PM: Connected to 192.168.137.11
8/10/2021, 2:53:04 PM: M122: === Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet Ethernet 1.02 or later
Board ID: 0JD0M-9P6B2-NJ4S8-6J9D0-3S86Q-TA7QL
Used output buffers: 1 of 24 (10 max)
=== RTOS ===
Static ram: 27988
Dynamic ram: 92084 of which 196 recycled
Exception stack ram used: 320
Never used ram: 10484
Tasks: NETWORK(ready,700) HEAT(blocked,1456) MAIN(running,2096) IDLE(ready,80)
Owned mutexes:
=== Platform ===
Last reset 00:01:26 ago, cause: software
Last software reset at 2021-08-10 14:51, reason: User, spinning module GCodes, available RAM 10668 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 24.8, current 25.6, max 26.1
Supply voltage: min 24.0, current 24.1, max 24.1, 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 not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2021-08-10 14:53:02
Cache data hit count 154921930
Slowest loop: 55.64ms; fastest: 0.12ms
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 3.8ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== Heat ===
Bed heaters = -1 -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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 6.42ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
Interface state active, link 100Mbps full duplex
8/10/2021, 2:53:34 PM: M98 P"config.g": HTTP is enabled on port 80
FTP is enabled on port 21
TELNET is enabled on port 23The config.g is as follows
; Default config.g template for Duet 2
; Replace this with a proper configuration file (e.g from https://configtool.reprapfirmware.org)
; enable UART for testing
M575 P1 B57600 S1
; test network enable
M550 P"DuetCraitor"
M551 P"craitor"
; M554 P192.168.96.1
; M553 P255.255.255.0
M552 P0.0.0.0 S1
M586 P0 S1
M586 P1 S1
M586 P2 S1 T0
; M552 P192.168.96.150; Display initial welcome message
M291 P"Please go to <a href=""https://www.duet3d.com/StartHere"" target=""_blank"">this</a> page for further instructions on how to set it up." R"Welcome to your new Duet 2!" S1 T0The error started immediately, we attempted to move a motor with it to test the board and the motor did not move at all. We then noticed this error in the console and after removing the motor the error still remained. The motor was tested with a different control board and functioned properly.
-
You need a proper config. Create one with the online tool linked in your current config.g
