Burnt Driver
-
While running some tests with my Duet Wifi A jumper cable on the Y-Axis motor came loose and caused a short. I can tell the Y motor Driver is bad, after disconnecting everything for the night and coming back today I can't move the Z or X axis motors. No motion what so ever. Is there an SMD fuse I need to replace as well? Please tell me I'm not out another $150.
Thanks in advance!
-
Are you saying that none of the X, Y and Z motors move, or was there a typo in your message?
If none of the motors move, check that you still have 12V or 24V at the VIN terminals. If the Y driver has failed, it's possible that it is shorting out the 12V/24V power.
If you are in the USA, there is a forum user (W3DRK) who can probably replace the driver chip for you. If you are in or near the UK, I intend to offer a repair service in the near future.
PS - M122 will show you the VIN voltage it measures too.
-
Just tested the board again, no movement on any axis whatsoever. I can, however trick the board into thinking the axes are homed by pressing the switches. I'm reading 24.11V across the Vin terminal. Accourding to the M122 command it's reading 24.6V. I am in the U.S. should I just search by username?
Memory usage:
Program static ram used: 13132
Dynamic ram used: 82180
Recycled dynamic ram: 2992
Current stack ram used: 2768
Maximum stack ram used: 3868
Never used ram: 28900
Last reset 00:06:37 ago, cause: power up
Error status: 1
Bed probe heights: 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 38.8, current 40.5, max 44.4
Supply voltage: min 24.5, current 24.6, max 24.8, under voltage events: 0, over voltage events: 0
Slowest main loop (seconds): 0.013702; fastest: 0.000031
Move Diagnostics:
MaxReps: 0, StepErrors: 0. Underruns: 0
Heat Diagnostics:
Bed heater = 0, chamber heater = -1
Heater 1 is on, I-accum = 0.0
GCodes Diagnostics:
Move available? no
Stack pointer: 0 of 5
macro is idle
http is ready with "M122"
telnet is idle
serial is idle
aux is idle
file is idle
Network Diagnostics:
WiFiServer is running
SPI underruns 0, overruns 0
Webserver Diagnostics:
HTTP sessions: 1 of 8 -
I'm the user David was referring to. Just send me a PM and I'll give you my contact info.
If all the axis are dead I wonder if something happened to the digital potentiometer or even the MCU itself, since I doubt all of the motor drivers were damaged simultaneously.
EDIT: I just realized this is a DuetWIFI, so no Digi-pot. So it sounds like the maybe the drivers aren't being initialized over SPI. In fact I'd bet it's the damaged driver hanging up the SPI bus which is why the other drivers were working until after a power-cycle.
-
So I'm only out a single IC? From what I've seen they're about $7 USD a piece. I have access to micro soldering equipment on campus, If I decide I don't feel comfortable doing it, I have friends who do work on micro satellites/Cubesats. I would really like your opinion and advice more than anything. So If you tell me just to replace a single driver that's what I'll do. Thanks for your input!
-
I'm not sure if the firmware expects a driver to be there or not, perhaps David could chime in… If not, I'd remove the dead driver and see if the others begin to work again. If that does it, I suspect a new driver would do the trick.
-
I removed the burnt Y-axis driver, your assumption was correct, the other axes moved upon command looks like I'm only out $7!
-
Glad to hear it!
-
Not as glad as I am!
