Duet 3 Mini 5+ SD card issue
-
All,
I have a Mini 5+ that I believe is having SD socket issues. When I first purchased the Mini5+ back in April I built a basic config with firmware version 3.2.2 to be able to build a basic cnc laser. This appeared to go well and everything appeared to be good with the Mini 5+ powered over USB on the bench.
Forward a few months and I am about ready to install the card into the machine, I figured I would fire it up over USB one more time before dropping it in to update to 3.3. When I attempted to do this I noticed the card did not join my wifi network. I thought this was odd as it had been working and the appropriate commands are contained in the config file (M552 S1). I noticed the wifi LED was not illuminated.
So I connected over USB and manually send basic commands and I was able to communicate over serial.
M115 response:
SENT: M115 READ: FIRMWARE_NAME: RepRapFirmware for Duet 3 Mini 5+ FIRMWARE_VERSION: 3.2.2 ELECTRONICS: Duet 3 Mini5plus WiFi FIRMWARE_DATE: 2021-02-11M122 response:
SENT: M122 READ: === Diagnostics === READ: RepRapFirmware for Duet 3 Mini 5+ version 3.2.2 running on Duet 3 Mini5plus WiFi (standalone mode) READ: Board ID: 1NYYQ-H396U-D65J0-40KMA-MJ03Z-ZN9QP READ: Used output buffers: 1 of 40 (1 max) READ: === RTOS === READ: Static ram: 98732 READ: Dynamic ram: 106368 of which 552 recycled READ: Never used RAM 39564, free system stack 136 words READ: Tasks: NETWORK(ready,518) HEAT(blocked,362) CanReceiv(blocked,947) CanSender(blocked,372) CanClock(blocked,362) TMC(blocked,123) MAIN(running,656) IDLE(ready,20) AIN(blocked,269) READ: Owned mutexes: USB(MAIN) READ: === Platform === READ: Last reset 00:08:43 ago, cause: software READ: Last software reset time unknown, reason: User, GCodes spinning, available RAM 39564, slot 2 READ: Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a READ: Error status: 0x00 READ: Aux0 errors 0,0,0 READ: Aux1 errors 0,0,0 READ: Supply voltage: min 0.0, current 1.3, max 1.3, under voltage events: 0, over voltage events: 0, power good: no READ: 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 READ: 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 READ: 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 READ: 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 READ: 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 READ: 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 READ: 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 READ: Date/time: 1970-01-01 00:00:00 READ: Cache data hit count 1206845107 READ: Slowest loop: 0.38ms; fastest: 0.11ms READ: === Storage === READ: Free file entries: 10 READ: SD card 0 detected, interface speed: 0.2MBytes/sec READ: SD card longest read time 0.0ms, write time 0.0ms, max retries 0 READ: === Move === READ: DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000 READ: === MainDDARing === READ: Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 READ: === AuxDDARing === READ: Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 READ: === Heat === READ: Bed heaters = -1 -1, chamberHeaters = -1 -1 READ: === GCodes === READ: Segments left: 0 READ: Movement lock held by null READ: HTTP is idle in state(s) 0 READ: Telnet is idle in state(s) 0 READ: File is idle in state(s) 0 READ: USB is ready with "M122" in state(s) 0 READ: Aux is idle in state(s) 0 READ: Trigger is idle in state(s) 0 READ: Queue is idle in state(s) 0 READ: LCD is idle in state(s) 0 READ: SBC is idle in state(s) 0 READ: Daemon is idle in state(s) 0 READ: Aux2 is idle in state(s) 0 READ: Autopause is idle in state(s) 0 READ: Code queue is empty. READ: === Network === READ: Slowest loop: 0.19ms; fastest: 0.00ms READ: Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions READ: HTTP sessions: 0 of 8 READ: - WiFi - READ: Network state is disabled READ: WiFi module is disabled READ: Failed messages: pending 2779096485, notready 2779096485, noresp 2779096485 READ: Socket states: 0 0 0 0 0 0 0 0 READ: === CAN === READ: Messages queued 2616, send timeouts 2615, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 16 READ: okIf I send M552 S1 over serial the wifi card will turn on. But my response from the web browser says, "Your Duet rejected the HTTP request: page not found
Check that the SD card is mounted and has the correct files in its /www folder".I verified the SD card had all the necessary files to start DWC.
I then built a new SD card, and SANDISK ultra SDXC and that had no change in response.
I tried following the guide to test SD card speed using:
M122 P104 S[file size in MB]And received the following:
SENT: M122 P104 S1 READ: Error: Failed to create folder 0:/gcodes in path 0:/gcodes/test.tst READ: Error: M122: Failed to create fileHow should I continue? Is there anything else I can try to do to get this card working? I have never plugged anything into the card besides a USB cable, SD cards, and the WIFI u.fl connector
Thanks,
Alex -
That does sound like an SD card reader issue.
When and where did you purchase your product?
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.
Sorry for the inconvenience.
-
I ordered it from Filastruder to a US address on April 7th 2021.
Not a problem I will send them email.
