Driver 3 too hot error
-
I was getting a driver 3 too hot error from my duet, I removed the duex 5 board and that resolved the error long enough to have the driver 3 driver actually show signs of melting.
Here is the M122.
=== Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later Board ID: 0JD0M-9P6M2-NW4SN-6J9D4-3S46T-KVS3L Used output buffers: 3 of 24 (14 max) === RTOS === Static ram: 25712 Dynamic ram: 92880 of which 120 recycled Exception stack ram used: 304 Never used ram: 12056 Tasks: NETWORK(ready,676) HEAT(blocked,912) MAIN(running,3732) IDLE(ready,160) Owned mutexes: === Platform === Last reset 00:18:04 ago, cause: power up Last software reset at 2021-01-11 19:58, reason: User, spinning module GCodes, available RAM 10816 bytes (slot 3) Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d 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.5, current 35.8, max 36.1 Supply voltage: min 1.6, current 1.7, max 1.8, under voltage events: 0, over voltage events: 0, power good: no Driver 0: ok, SG min/max not available Driver 1: ok, SG min/max not available Driver 2: ok, SG min/max not available Driver 3: ok, SG min/max not available Driver 4: ok, SG min/max not available Date/time: 2021-01-27 20:03:26 Cache data hit count 4215967080 Slowest loop: 5.10ms; fastest: 0.05ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Move === Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms Bed compensation in use: none, comp offset 0.000 === DDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 Heater 1 is on, I-accum = 0.0 === 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: 200.42ms; fastest: 0.07ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0) HTTP sessions: 1 of 8 WiFi - Network state is running WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 20 WiFi firmware version 1.23 WiFi MAC address 84:0d:8e:b2:f4:96 WiFi Vcc 3.42, reset reason Turned on by main processor WiFi flash size 4194304, free heap 23000 WiFi IP address 192.168.1.177 WiFi signal strength -41dBm, reconnections 0, sleep mode modem Socket states: 0 0 0 0 0 0 0 0 -
Can you start from the top and try and explain what happened?
You have a Duet2Ethernet and a Duex5?
How was everything connected?
Were you in the web interface yet?
If you're unable to see the Duet via USB, try going through this document: https://duet3d.dozuki.com/Wiki/What_to_do_if_your_Duet_won't_respond
Photo of the board?
When and where was it purchased? -
Plugged it in like all my other builds, 2,5,6,7 to my z 0,1 to x and y 3 to my extruder. Was giving driver too hot error which I had read before that duex 5 board sometimes causes that error to show so I removed the duex 5 board while powered down and powered it back up and the driver 3 then started smoking and is now fried. Both boards at this point don't work. Was in the web interface with no issues. Can still see the duet no problem but driver 3 is toast. Bought first week of January for 8 custom builds I had for a customer just now getting into wiring all of them. Bought from filastruder. @Phaedrux
-
![alt text]!
PXL_20210128_030506341.jpg -
Top picture might indicate issues with the 3v3 regulator U2; but its clearly not the same board as shown with the scorched driver 3 (E0).
-
@bearer nope have another set with issues as well. Must have gotten them mixed up.
-
Yes it appears that U2 has exploded. Please contact Filastruder and initiate a warranty exchange for this Duet. Include a link to this thread as authorization.
-
@Phaedrux as well as the duex 5?
-
The Duex5 on this one also stopped working?
-
Is that Duex5 genuine? It would appear not to me.
