Intermittent SD-card funtionality on Duet 3 mini 5+
-
Hi,
I recently purchased a Duet 3 mini 5+ from one the official resellers. I've noticed problems with intermittet function of the SD-card and found this thread:
https://forum.duet3d.com/topic/21004/duet-3-mini-5-unable-to-connect-via-browser/23
I also get the error "Cannot initialise SD card 0: Card is unusable"
I also saw @dc42 mentioning that it could be fixed with a no-clean flux pen and a hot-air station. Something I have and know how to use...
I was thinking that I will give it a go to fix it instead of sending it back to Germany from Sweden. Is the chip that had the QA-ussues the SD-card ESD-protector denoted U20 in the schematic? Would it be suficient applying flux and reheat it with hot air or should I de-solder it, clean, apply new paste and flux and solder it back? The 0.4 mm pin pitch of the CM1624 is not impossible, but a bit smaller than I'm used with.
-
What hardware revision is the board? Check the silk screen.
When and where did you purchase?
-
@phaedrux It's v 1.0 ordered from Dold Mechatronik in Germany end of May.
Resoldering the SD-card holder seems to have solved the issue though. Fingers crossed, but now it detects the card every time. I did not have to do anything to the ESD-suppressor.
-
Well that is good to hear. Please keep us updated on if it keeps working.
Did you ever happen to notice config.g going missing on you?
-
Now it's back to not detecting the SD-card again
The sticker on the back of the board says:
Mini 5+ V1.0
202101-0374A boot followed by a M122 gives the following output over the USB connection:
RepRapFirmware for Duet 3 Mini 5+ version 3.2.2 Warning: Cannot initialise SD card 0: Card is unusable Ethernet is disabled. RepRapFirmware for Duet 3 Mini 5+ is up and running. === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.2.2 running on Duet 3 Mini5plus Ethernet (standalone mode) Board ID: AVUXR-A196U-D65J0-40KMG-1N03Z-7ZJ7D Used output buffers: 1 of 40 (1 max) === RTOS === Static ram: 98732 Dynamic ram: 100904 of which 612 recycled Never used RAM 44968, free system stack 152 words Tasks: NETWORK(ready,544) HEAT(blocked,367) CanReceiv(blocked,947) CanSender(blocked,372) CanClock(blocked,363) TMC(blocked,123) MAIN(running,666) IDLE(ready,20) AIN(blocked,272) Owned mutexes: USB(MAIN) === Platform === Last reset 00:00:12 ago, cause: power up Last software reset at 2021-06-05 20:33, reason: User, GCodes spinning, available RAM 44196, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 Aux1 errors 0,0,0 Supply voltage: min 0.0, current 0.9, max 0.9, under voltage events: 0, over voltage events: 0, power good: no 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 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 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 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 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 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 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 Date/time: 1970-01-01 00:00:00 Cache data hit count 34743441 Slowest loop: 0.18ms; fastest: 0.12ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 0.2MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters = -1 -1, chamberHeaters = -1 -1 === 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 ready with "M122" 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. === Network === Slowest loop: 0.17ms; fastest: 0.01ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 0 of 8 - Ethernet - State: disabled Error counts: 0 0 0 0 0 Socket states: 0 0 0 0 0 0 0 0 === CAN === Messages queued 65, send timeouts 64, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 16 okBTW. config.g is still present in the sys-directory
-
Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.
-
@lhelge
Hi Linus, when I get that error message I just open the config.g to edit and save = OK -
@lhelge said in Intermittent SD-card funtionality on Duet 3 mini 5+:
SD card 0 detected, interface speed: 0.2MBytes/sec
That’s a sign that the interface isn’t working correctly, should be 25MBytes/sec. See https://duet3d.dozuki.com/Wiki/SD_Card#Section_Troubleshooting_SD_Card_issues
If the socket or processor is faulty but the card is detected, it usually drops to 0.2Mbytes/sec.
I’d recommend replacement.
Ian
