Error: short-to-ground or diy a replacement driver chip?
-
Hello, All! Finally completed dropping in recent Duet 2 WIFI replacement board. Installed motors are new, tested as well as the cables. For the 2nd time I'm hit with the "Error: short-to-ground reported by driver....". This board it is sensing that its Y axis driver is at fault. I break it down to isolate the reported problematic circuit; shut down, detach cabling, power. I begin to test for continuity throughout the component, primarily the driver chip soldering to the board. I compare my findings to results that are consistent across all other non-faulted components, driver chips. My multimeter detects a NON-transient grounding across the chip. This chip isn't holding anything to its own circuits. Every pin seems to connect with every other pin. I can honestly testify to DWC's reporting of a ground short on Driver 1, this "Y" axis driver. Oddly, when DWC is sent command M122 (included at bottom) the entire set of drivers report nothing unusual whatsoever. This Driver chip is the only one off. All others check out consistently.
Given this board has been returned twice already, thank you Filastruder for all your efforts and patience. I know this kind of attention and service is unique to you. I do not really want to sit idly by for another month while this issue is benched with suggestions and checklists, finally given an RMA, sent a shipping label after approvals, packed, sent, huge blank space filled with imagination and informational void, then surprises me at my door step some shiny day in the fortuitous distant future. Takes way to long.
So, I purpose that I order a replacement chip directly, to me, where I can desolder and replace the faulted driver myself, saving both time, energy. That said, how would the Duet's warranty become affected?
6/12/2022, 5:46:35 PM m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0 (2022-03-15 18:58:31) running on Duet WiFi 1.02 or later
Board ID: 0JD0M-9X6JA-JUNSN-6JKF0-3SJ6R-TVNBT
Used output buffers: 3 of 24 (12 max)
=== RTOS ===
Static ram: 23868
Dynamic ram: 78528 of which 0 recycled
Never used RAM 9684, free system stack 184 words
Tasks: NETWORK(ready,10.2%,243) HEAT(notifyWait,0.0%,332) Move(notifyWait,0.0%,364) MAIN(running,84.1%,466) IDLE(ready,5.7%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:16 ago, cause: reset button or watchdog
Last software reset at 2022-06-11 21:07, reason: User, GCodes spinning, available RAM 9536, 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
Step timer max interval 0
MCU temperature: min 20.2, current 21.7, max 22.0
Supply voltage: min 23.9, current 24.1, max 24.3, 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
Events: 0 queued, 0 completed
Driver 0: standstill, SG min n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 2022-06-12 17:46:31
Cache data hit count 590318053
Slowest loop: 4.95ms; fastest: 0.19ms
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.6ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.0
=== 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
=== Network ===
Slowest loop: 15.55ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8WiFi -
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:83:8a
WiFi Vcc 3.38, reset reason Power up
WiFi flash size 2097152, free heap 22336
WiFi IP address 192.168.137.2
WiFi signal strength -70dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0!
Thank you guys. All helps, totally green here. -
Sorry to hear you're still having problems.
Last time it was the X driver and this time it's the Y driver?
@crookid said in Error: short-to-ground or diy a replacement driver chip?:
Installed motors are new, tested as well as the cables.
New motors since the last problem? How and where were the verified as working?
@crookid said in Error: short-to-ground or diy a replacement driver chip?:
So, I purpose that I order a replacement chip directly, to me, where I can desolder and replace the faulted driver myself, saving both time, energy. That said, how would the Duet's warranty become affected?
We'll take that into consideration. I assume this means you have a reasonable skill level with hot air rework?
-
@phaedrux
Yes. I've been working with FPV drones... for some few years now. I can successfully swap out processors consistently. They're about the same exact size as TMC2660 drivers and have roughly 4 times the pins. I feel confident in my work and materials for success. As for the stepper motors, They're a Sanyo stepper, bipolar, 1.8 ohms at each phase. All specs check out and fall within the parameters of the Duet2 board. Hella bummer. Again... BUT-"... try, try, again." Thanks for your alls continued support. -
If you'd like to do the swap yourself we can arrange to send you the chip, but the warranty would be void.
-
@phaedrux
I see. I really feel like keeping the warranty active based on the various issues that have arisen in the past. However the time it has taken to resolve those issues has been a bit of another issue. Is there any middle ground we could take that solves the driver without voiding the warranty? I'm a big fan of resolution the 'smart' way, seems to serve better than any dumb way I've ever conceived. I appreciate having people smarter than mine in my corner. Thanks and I appreciate you. -
We could have been half way through a board exchange by now.
