Reverse input polarity Duet 3 Mini
-
The motor drivers will between them have taken the short circuit output current of the PSU for as long as it too for the fuse to blow. So if the short circuit current of the PSU was 20A, then the drivers will have taken 4A each. Given that each driver has two H-bridges rated 2A each, I think there is a reasonable chance that they will have survived. If the fuse doesn't blow when you connect VIN the right way round, that's a good sign.
You are not the only person to have done this - I did it once with a Duet WiFi, before we fitted fuses to that board. The board survived.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 Thanks! However, I cannot open up a serial connection the board anymore. I connect it via USB to my PC and it seems to connect and reconnect every 10s or so and I'm not able to communicate. If I connect the USB, the 3.3V and 5V LED are on and the status LED is off. It only blinks shortly everytime Windows detects a new USB device.
-
@weeky said in Reverse input polarity Duet 3 Mini:
@dc42 Thanks! However, I cannot open up a serial connection the board anymore. I connect it via USB to my PC and it seems to connect and reconnect every 10s or so and I'm not able to communicate. If I connect the USB, the 3.3V and 5V LED are on and the status LED is off. It only blinks shortly everytime Windows detects a new USB device.
It sounds to me that it is in a reboot loop. Try booting up with the SD card removed. If you are then able to get a serial connection, run M122 and post the output here.
If you are not able to get a serial connection, see if you can put the board into bootloader mode, by pressing the reset button twice quickly in succession. In bootloader mode, it presents a storage device to USB. See https://duet3d.dozuki.com/Wiki/Duet_3_Mini_5plus_Firmware#Section_Updating_firmware_via_USB.
-
By updating the firmware I got it running again. Here is the output:
=== Diagnostics ===<\n>
RepRapFirmware for Duet 3 Mini 5+ version 3.2.2 running on Duet 3 Mini5plus Ethernet (standalone mode)<\n>
Board ID: KZUH1-9296U-D65J0-40KMD-2A03Z-H6X90<\n>
Used output buffers: 1 of 40 (1 max)<\n>
=== RTOS ===<\n>
Static ram: 98732<\n>
Dynamic ram: 100904 of which 612 recycled<\n>
Never used RAM 44968, free system stack 152 words<\n>
Tasks: NETWORK(ready,544) HEAT(blocked,367) CanReceiv(blocked,947) CanSender(blocked,372) CanClock(blocked,363) TMC(blocked,123) MAIN(running,652) IDLE(ready,20) AIN(blocked,272)<\n>
Owned mutexes: USB(MAIN)<\n>
=== Platform ===<\n>
Last reset 00:00:32 ago, cause: power up<\n>
Last software reset time unknown, reason: StuckInSpinLoop, none spinning, available RAM 63548, slot 2<\n>
Software reset code 0x0092 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0046080f BFAR 0xe000ed38 SP 0x2000a6e4 Task MAIN Freestk 4294967295 ok<\n>
Stack: 000309c5 000726aa 410a0000 00000000 00000000 42340094 2c048011 00ea0922 100208b2 c1100101 09060088 12213062 c0c28588 0c251008 00000000 00000000 3f800000 00000000 42a00000 20000000 00000000 00000000 00000001 00000000 000309c5 00000000 00000000<\n>
Error status: 0x00<\n>
Aux0 errors 0,0,0<\n>
Aux1 errors 0,0,0<\n>
Supply voltage: min 0.0, current 0.6, max 0.6, under voltage events: 0, over voltage events: 0, power good: no<\n>
Driver 0: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0<\n>
Driver 1: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0<\n>
Driver 2: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0<\n>
Driver 3: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0<\n>
Driver 4: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0<\n>
Driver 5: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0<\n>
Driver 6: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0<\n>
Date/time: 1970-01-01 00:00:00<\n>
Cache data hit count 81325300<\n>
Slowest loop: 0.23ms; fastest: 0.12ms<\n>
=== Storage ===<\n>
Free file entries: 10<\n>
SD card 0 detected, interface speed: 0.2MBytes/sec<\n>
SD card longest read time 0.0ms, write time 0.0ms, max retries 0<\n>
=== Move ===<\n>
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000<\n>
=== MainDDARing ===<\n>
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1<\n>
=== AuxDDARing ===<\n>
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1<\n>
=== Heat ===<\n>
Bed heaters = -1 -1, chamberHeaters = -1 -1<\n>
=== GCodes ===<\n>
Segments left: 0<\n>
Movement lock held by null<\n>
HTTP is idle in state(s) 0<\n>
Telnet is idle in state(s) 0<\n>
File is idle in state(s) 0<\n>
USB is ready with "M122" in state(s) 0<\n>
Aux is idle in state(s) 0<\n>
Trigger is idle in state(s) 0<\n>
Queue is idle in state(s) 0<\n>
LCD is idle in state(s) 0<\n>
SBC is idle in state(s) 0<\n>
Daemon is idle in state(s) 0<\n>
Aux2 is idle in state(s) 0<\n>
Autopause is idle in state(s) 0<\n>
Code queue is empty.<\n>
=== Network ===<\n>
Slowest loop: 0.20ms; fastest: 0.01ms<\n>
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions<\n>
HTTP sessions: 0 of 8<\n>- Ethernet -<\n>
State: disabled<\n>
Error counts: 0 0 0 0 0<\n>
Socket states: 0 0 0 0 0 0 0 0<\n>
=== CAN ===<\n>
Messages queued 163, send timeouts 162, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 16<\n>
However, I cannot manage to get the SD card to work. It didn't work with the supplied one and also not after reformatting it and putting the files back on. M39 reports:
Error: M39: No SD card mounted in slot 0<\n>
and M21:
Error: M21: Cannot initialise SD card 0: Card is unusable
- Ethernet -<\n>
-
Does the SD card read OK in a PC? Have you another SD card you can try?
Which country are you in?
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 The SD card reads fine under windows. I tried a different one, formatted to FAT32, copied the contents and got the same behavior. Are the SD card contents not compatible with the new firmware or should this be independent on the issue of a M21 command? I'm from Germany.
-
I understand this is a new build, but were you at a point yet where you had previously been able to access the SD card?
-
@Phaedrux No, I was just installing the board in the printer when the mishap took place. I never was at a point where I turned the Duet on before. Now I tested everything and was able to verify that its still working. However, the SD card does not work the way I'm trying right now. I cannot say if it worked before.
-
I was shortly able to get it running:
SD card in slot 0: capacity 7.95Gb, free space 7.94Gb, speed 22.50MBytes/sec, cluster size 32kb<\n>
ok<\n>
<\n>
SDHC card mounted in slot 0, capacity 7.95Gb<\n>
ok<\n>
Error: Cannot read file, error code 1<\n>However, after I tried to access DWC, I got the error message "Error: Cannot read file, error code 1" and after that I wasn't able to mount it again. I was not able to see the DWC from my Browser.
-
Okay after another hour of testing: No SD card works, only that one time it worked for a couple of seconds. I've read that a couple of other users of the Mini had the same issue. However, after my input voltage reversal I can't be sure if it wasn't working from the beginning or only after that. Seems like I got an expensive piece of junk now without a working SD-card interface. Very disappointing
-
It could be an unrelated SD card issue. Where and when did you purchase the Duet?
Please contact your vendor and initiate a warranty exchange. Include a link to think thread as authorization.
-
@Phaedrux I bought it on the 6th of January from E3D-Online. I think it could be a problem with the SD card socket itself, since I was able to very shortly mount the SD card it, maybe some contact problems?
-
Please contact E3D and initiate a warranty exchange for the SD card issue. Include a link to this thread as authorization.
-
@Phaedrux Thanks! I did this and my return package is already on its way. Thanks for the great service and help.
