Fried Duet 3 io
-
Yesterday I was trying to set up a sensor that detects pellets, when i turned the duet on one of the IO pins smoked and burnt out, I was meant get power of the duet board but I also wired in a 24v power source to the electronics board of the sensor i didn't realise it was either or. My duet still seems to be working but my bl touch dose not seem to have power and more, have i fried it the IO section of the board? is the only fix a replacement board. Also would this cause damage to my external boards like the xd board and the thermocouple boards or even the bl touch. Thanks using duet 3 6hc
m122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.4.0 (2022-03-15 18:57:24) running on Duet 3 MB6HC v1.01 or later (standalone mode) Board ID: 08DJM-956L2-G43S8-6JTD8-3SS6K-9B1AH Used output buffers: 3 of 40 (15 max) === RTOS === Static ram: 151000 Dynamic ram: 97404 of which 0 recycled Never used RAM 102268, free system stack 206 words Tasks: NETWORK(ready,25.9%,219) ETHERNET(notifyWait,0.1%,175) HEAT(notifyWait,0.1%,321) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,8.0%,92) MAIN(running,65.3%,1101) IDLE(ready,0.7%,30), total 100.0% Owned mutexes: === Platform === Last reset 00:12:09 ago, cause: power up Last software reset at 2022-11-17 09:17, reason: User, GCodes spinning, available RAM 102196, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Step timer max interval 130 MCU temperature: min 16.4, current 25.7, max 26.1 Supply voltage: min 28.3, current 28.3, max 28.4, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0 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 0, mspos 8, reads 62587, writes 14 timeouts 0 Driver 1: standstill, SG min 0, mspos 8, reads 62588, writes 14 timeouts 0 Driver 2: standstill, SG min 0, mspos 8, reads 62588, writes 14 timeouts 0 Driver 3: standstill, SG min 0, mspos 8, reads 62588, writes 14 timeouts 0 Driver 4: standstill, SG min 0, mspos 8, reads 62591, writes 11 timeouts 0 Driver 5: standstill, SG min 0, mspos 8, reads 62591, writes 11 timeouts 0 Date/time: 2022-11-17 09:46:28 Slowest loop: 5.91ms; fastest: 0.05ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 25.0MBytes/sec SD card longest read time 1.2ms, write time 0.0ms, max retries 0 === Move === DMs created 125, 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 1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 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 SBC is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === CAN === Messages queued 6542, received 0, lost 0, boc 10232 Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 49), ts 3648/0/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 5.96ms; fastest: 0.02ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions HTTP sessions: 1 of 8 - Ethernet - State: active Error counts: 0 0 0 0 0 Socket states: 5 2 2 2 2 0 0 0
-
Can you show some photos of your board? Maybe we can spot a damaged component.
Can you share a diagram of what you had connected where?
-
@Phaedrux I had the OUTPUT and the 24v supply plugging at the same time by mistake like an idiot. It started sparking and smoking. it seemed like it took the io ports out as my bl touch was not lighting up red and a few of the fans were not running,the endstops were still triggering though. Is there a way to check how badly its damaged see if i could use it for something else in the future, i ordered a replacement as i would not have the skills to fix it anyway.I had it wired to 3.3v ,ground and io out. There was no visual damage on the rest of the board. image url)
-
That looks like it shorted 24v to ground through the ground pin. If the BLTouch and some fans are not working it sounds like it took out some regulators as well. If you got a clear shot of the top of the board we might be able to tell.
-
This post is deleted! -
@Phaedrux ![alt text]( image url)
-
-
The photos aren't quite bright or clear enough to make out enough detail, but with your own eye are you able to see any chips that look damaged?
-
@Phaedrux i dont see any chips that are broken but i have replaced the duet now maybe ill get another use out of it , i also had to replace the bl touch as that got fried anyway thanks for your help.
-
@cj19944 where in the world are you?
-
@cj19944 if there was a short between +24V and the +5V_EXT rail, the Duet 3 is designed to withstand that, however anything else powered from 5V such as BLTouch or PanelDue will have been fried. Also the output pin feeding the BLTouch may have been damaged.
-
@jay_s_uk I am in the uk.
-
@dc42 Thank you.
-
@cj19944 might be recoverable then. feel free to drop me a PM