Suspected SD card slot issues with a Duet 3 Mini 5+

Z4c_Sm1th

Hi all, it was suggested to me that I write a detailed account of some bizarre issues I'm having with my Mini5+ at the moment here, to see if there are any suggestions!

So I'm running a Mini5+ on my Mod0 which brendonbuilds very generously donated & built for me at SMRRF23, and it had been working great for a while. However, I was keen to try the new Input Shaping on 3.6.0 B3, so decided to backup the SD Card (was running 3.5.4 stably) to my computer, before then moving to the beta. However, when reinserting the SD card after backing it up, the printer was no longer responsive. I'm certain I had safely ejected it from my laptop, although it is possible it was prematurely removed from the printer (although power was off, theres a chance a capacitor was still holding charge maybe?)

Following this I've run through several troubleshooting steps, that ill list in as best of an order as I can below:

Attempt to connect via DWC - printer wasn't connecting to my Wifi
Used the original SD card contents that Brendon used, after reformatting the card, but was still unresponsive on DWC and the LCD wasn't showing a UI, like before.
Tried Fallback Procedure to flash firmware, made sure that I was flashing the 3.5.4 .uf2 file for a firmware built on 3.5.4 - the board acted as the documentation suggested it would, however once I reconnected over YAT, it wasn't automatically connecting to Wifi, and even after using M587 to make a connection to Wifi, the error of "your duet denied access, check /www in sd card" showed up, and after a power cycle the printer hadn't stored the SSID / Password, so everytime I tried to test this it would need a new M587 command.
Tried about 6 different SD cards in the slot, following the documentation's advice on formatting, size etc.
Ran M20, M21 and M122 over YAT. This was the most interesting step, as M122 says that SD card 0 is detected, however the transfer rate is 0.2 MB/sec, which documentation suggests would be an error with the socket / processor. Also ran M20 and M21s, both of which couldn't detect the SD Card, which I find confusing if M122 could?

I might've forgotten some other steps, sorry if so, but hopefully I can answer any questions people have about what I have / haven't tried. Thank you in advance for the help, its greatly appreciated!! Have to warn I'm on a trip for the next 2 days so can't be next to the printer, but can still answer questions ASAP

droftarts

@Z4c_Sm1th Please connect via USB, and run the tests here https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card#troubleshooting-sd-card-issues, and look at the SD card socket as shown here https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card#sd-card-socket.

Please report back with the full M122 report, and any photos of the SD card pins, if it looks like it's been poorly soldered.

@Z4c_Sm1th said in Suspected SD card slot issues with a Duet 3 Mini 5+:

M122 says that SD card 0 is detected, however the transfer rate is 0.2 MB/sec, which documentation suggests would be an error with the socket / processor.

Most likely that is the issue. Check if the SD card socket gets unexpectedly warm to the touch when the board is powered.

Ian

droftarts

@Z4c_Sm1th We're happy to offer you a warranty replacement board, as you've been through the troubleshooting with Brendon, and it looks to be the SD card slot. Please send an email to warranty@duet3d.com. Include a link to this forum thread and mention that it's the Mod0 machine that Brendon built. You'll receive a reply with a form to fill out.

Ian

Z4c_Sm1th

@droftarts Hi Ian, sorry for the delayed response, only just got back from my trip

Thank you very much for offering a replacement board, its incredibly generous of you!

I've attached a full copy of the M122 report and some photos of the SD slot just incase there is anything that would suggest another issue (would prefer not to cause a bother with a replacement if it can be avoided)

Thanks again,
Zac

=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.5.4 (2024-11-24 10:44:24) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: 35ZY3-SN6KL-K65J0-409N8-JFW1Z-ZF6NL
Used output buffers: 1 of 40 (1 max)
=== RTOS ===
Static ram: 103496
Dynamic ram: 119484 of which 0 recycled
Never used RAM 18768, free system stack 156 words
Tasks: NETWORK(1,ready,6.5%,505) HEAT(3,nWait 6,0.0%,369) Move(4,nWait 6,0.0%,355) CanReceiv(6,nWait 1,0.0%,939) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,334) TMC(4,nWait 6,0.0%,121) MAIN(1,running,90.4%,876) IDLE(0,ready,2.2%,29) AIN(4,delaying,0.8%,264), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:02:22 ago, cause: power up
Last software reset at 2025-01-19 15:31, reason: User, Gcodes spinning, available RAM 6088, 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
MCU revision 3, ADC conversions started 107312, completed 107312, timed out 0, errs 0
MCU temperature: min 23.8, current 25.8, max 26.2
Supply voltage: min 0.3, current 0.8, max 0.9, under voltage events: 0, over voltage events: 0, power good: no
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: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 1: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 2: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 3: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 4: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 5: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 6: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 302689886
Slowest loop: 0.28ms; fastest: 0.15ms
=== Storage ===
Free file entries: 20
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, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== DDARing 1 ===
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, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks held by null, 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
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
Q0 segments left 0, axes/extruders owned 0x0000000
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== CAN ===
Messages queued 715, received 0, lost 0, errs 689203, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 26 (min 26), ts 715/0/0
Tx timeouts 0,0,714,0,0,0 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 0.25ms; fastest: 0.00ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 0 of 8
=== WiFi ===
Interface state: disabled
Module is disabled
Failed messages: pending 0, notrdy 0, noresp 0
Socket states: 0 0 0 0 0 0 0 0
ok