New Duet 3 Mini 5+ not working
-
Hi guys
We have the following issue with our new board - https://forum.duet3d.com/topic/19447/new-duet-2-wifi-not-reading-sd-card
Please can someone get back to me regarding a replacement or solution? It has cost us ALOT of time and frustration to get to this point.
M122 returns the following:
m122<CR>
=== Diagnostics ===<LF>RepRapFirmware for Duet 3 Mini 5+ version 3.4.1 (2022-06-01
21:06:56) running on Duet 3 Mini5plus Ethernet (standalone mode)<LF>Board ID: LK9YK
-4396U-D65J0-40KMW-JK03Z-7MDAH<LF>Used output buffers: 1 of 40 (1 max)<LF>=== RTOS ===
<LF>Static ram: 103684<LF>Dynamic ram: 103220 of which 0 recycled<LF>Never used RAM 34808
, free system stack 156 words<LF>Tasks: NETWORK(ready,8.7%,548) HEAT(notifyWait,0.0
%,374) Move(notifyWait,0.0%,363) CanReceiv(notifyWait,0.0%,942) CanSender(notify
Wait,0.0%,372) CanClock(delaying,0.0%,339) TMC(notifyWait,0.6%,114) MAIN(running
,84.4%,617) IDLE(ready,5.4%,29) AIN(delaying,0.8%,274), total 100.0%<LF>Owned mutex
es: USB(MAIN)<LF>=== Platform ===<LF>Last reset 00:01:07 ago, cause: power up<LF>Last sof
tware reset at 2022-08-31 15:28, reason: User, GCodes spinning, available RAM 32
792, slot 1<LF>Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00
000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a<LF>Error status: 0x00<LF>
MCU revision 3, ADC conversions started 67869, completed 67869, timed out 0, err
s 0<LF>Step timer max interval 719<LF>MCU temperature: min 30.2, current 31.2, max 31.
5<LF>Supply voltage: min 24.2, current 24.2, max 24.2, under voltage events: 0, ove
r voltage events: 0, power good: yes<LF>Heap OK, handles allocated/used 0/0, heap m
emory allocated/used/recyclable 0/0/0, gc cycles 0<LF>Events: 0 queued, 0 completed
<LF>Driver 0: standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 3
130, writes 9, timeouts 0, DMA errors 0, CC errors 0<LF>Driver 1: standstill, SG mi
n 0, read errors 0, write errors 0, ifcnt 9, reads 3129, writes 9, timeouts 0, D
MA errors 0, CC errors 0<LF>Driver 2: standstill, SG min 0, read errors 0, write er
rors 0, ifcnt 9, reads 3129, writes 9, timeouts 0, DMA errors 0, CC errors 0<LF>Dri
ver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 3129,
writes 9, timeouts 0, DMA errors 0, CC errors 0<LF>Driver 4: standstill, SG min 0,
read errors 0, write errors 0, ifcnt 9, reads 3129, writes 9, timeouts 0, DMA e
rrors 0, CC errors 0<LF>Driver 5: not present<LF>Driver 6: not present<LF>Date/time: 1970
-01-01 00:00:00<LF>Cache data hit count 149525687<LF>Slowest loop: 0.25ms; fastest: 0.
12ms<LF>=== Storage ===<LF>Free file entries: 10<LF>SD card 0 detected, interface speed:
0.2MBytes/sec<LF>SD card longest read time 0.0ms, write time 0.0ms, max retries 0<LF>=
== Move ===<LF>DMs created 83, segments created 0, maxWait 0ms, bed compensation in
use: none, comp offset 0.000<LF>=== MainDDARing ===<LF>Scheduled moves 0, completed 0
, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1<LF>=== Au
xDDARing ===<LF>Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0
, Underruns [0, 0, 0], CDDA state -1<LF>=== Heat ===<LF>Bed heaters -1 -1 -1 -1, chamb
er heaters -1 -1 -1 -1, ordering errs 0<LF>=== GCodes ===<LF>Segments left: 0<LF>Movement
lock held by null<LF>HTTP is idle in state(s) 0<LF>Telnet is idle in state(s) 0<LF>File
is idle in state(s) 0<LF>USB is ready with "m122" in state(s) 0<LF>Aux is idle in stat
e(s) 0<LF>Trigger is idle in state(s) 0<LF>Queue is idle in state(s) 0<LF>LCD is idle in
state(s) 0<LF>SBC is idle in state(s) 0<LF>Daemon is idle in state(s) 0<LF>Aux2 is idle i
n state(s) 0<LF>Autopause is idle in state(s) 0<LF>Code queue is empty<LF>=== CAN ===<LF>Mes
sages queued 339, received 0, lost 0, boc 0<LF>Longest wait 0ms for reply type 0, p
eak Tx sync delay 0, free buffers 18 (min 18), ts 339/0/0<LF>Tx timeouts 0,0,338,0,
0,0 last cancelled message type 30 dest 127<LF>=== Network ===<LF>Slowest loop: 0.20ms
; fastest: 0.01ms<LF>Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telne
t(0), 0 sessions<LF>HTTP sessions: 0 of 8<LF>- Ethernet -<LF>State: disabled<LF>Error counts
: 0 0 0 0 0<LF>Socket states: 0 0 0 0 0 0 0 0<LF>ok<LF>
m122 p104 s10
Error: Failed to create folder 0:/gcodes in path 0:/gcodes/test.tst<LF>Error: M122:
Failed to create file<LF>ok<LF> -
@davidleigh said in New Duet 3 Mini 5+ not working:
SD card 0 detected, interface speed:
0.2MBytes/seclooks like the card is detected, which is more than duet3 mini's with dodgy SD card slots can do.
What SD card are you using?
Can you also fix the output of YAT to make sure its more readable? https://docs.duet3d.com/en/User_manual/Troubleshooting/Terminal_Emulators#line-endings -
@davidleigh said in New Duet 3 Mini 5+ not working:
interface speed:
0.2MBytes/secSomething is definitely not right with the SD card interface.
When and where did you purchase the Duet?
-
@phaedrux I bought it recently from Filastruder - 12 July 2022.
Please can someone from Duet help me with a claim for a new one? Ive had to buy a new one in order tog et prints going. Quite frustrating.
-
@phaedrux I emailed Duet and was advised to go to the forums for a support staff to review fault and authorise a warranty claim.
-
@davidleigh Sorry for the inconvenience, it would appear that your board is faulty. For reference, there is a section in the documentation about these kinds of faults: https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card#troubleshooting-sd-card-issues
The interface speed ... gives an indication of whether the processor is able to communicate with the SD card at all. It should be ... 22.5MB/sec on a Duet 3 Mini in standalone mode. Other numbers, eg 12MBs/sec, are odd and suggest an issue with the SD card. If the socket or processor is faulty but the card is detected, it usually drops to 0.2MB/sec.
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.
Ian
