@phaedrux Sent. Thank you again for all your help!
Latest posts made by LevelFun
-
RE: Duet 2 Wifi & Duet 3 Mini 5+ SD Card Slot Faulty
-
RE: Duet 2 Wifi & Duet 3 Mini 5+ SD Card Slot Faulty
@phaedrux I found my Duet 2 Wifi receipt from Printed Solid on March 2, 2020. Any way I can still send this in for repair since the SD card solder points are faulty? Thank you for your help!
-
RE: Duet 2 Wifi & Duet 3 Mini 5+ SD Card Slot Faulty
@phaedrux Will do. Thanks a bunch. I'll also post once I also find my Duet 2 Wifi receipt.
-
RE: Duet 2 Wifi & Duet 3 Mini 5+ SD Card Slot Faulty
@phaedrux After searching through my old e-mails I actually purchased the Duet 3 Mini 5+ from Filastruder on January 6th, 2021 (my first Duet 3 Mini 5+ from Filastruder was RMA'd immediately after it arrived because it was faulty. The return was approved back then here on the forum and exchanged for a new one after more came in stock after a month.)
My Duet 2 Wifi I am still trying to find where I purchased it from, but I know it was in 2020. I just can't catch a break with these board I love the support and RepRap over Marlin etc, but I don't know what to do now. Advice?
-
Duet 2 Wifi & Duet 3 Mini 5+ SD Card Slot Faulty
I purchased my Duet 2 Wifi in 2019 and my Duet 3 Mini 5+ Ethernet in January of 2020 (it was RMA'd under warranty the day after receiving and I received a fresh new one via Filatruder). Life happened and I wasn't able to use them, so I kept them in their boxes and set them to the side. Fast-forward to today - finally excited to have free time and build my dream delta printers. Set everything up with my Duet 2 Wifi (which I tested back in the day) and YAT informs me of the following:
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.2 (2022-09-13 15:11:16) running on Duet WiFi 1.02 or later
Board ID: 08DGM-9T6BU-FG3SJ-6JKFD-3SJ6T-TBYBH
Used output buffers: 1 of 26 (11 max)
=== RTOS ===
Static ram: 23860
Dynamic ram: 73376 of which 12 recycled
Never used RAM 14832, free system stack 193 words
Tasks: NETWORK(ready,7.7%,517) HEAT(notifyWait,0.0%,388) Move(notifyWait,0.0%,363) MAIN(running,92.3%,428) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:02:01 ago, cause: power up
Last software reset at 2021-10-05 15:42, reason: User, GCodes spinning, available RAM 12656, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Step timer max interval 0
MCU temperature: min 21.6, current 22.9, max 23.3
Supply voltage: min 1.5, current 1.7, max 1.8, 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
Driver 1: ok, SG min n/a
Driver 2: ok, SG min n/a
Driver 3: ok, SG min n/a
Driver 4: ok, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 1970-01-01 00:00:00
Cache data hit count 4294967295
Slowest loop: 0.23ms; fastest: 0.14ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 30.0MBytes/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, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
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 ===
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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== Network ===
Slowest loop: 0.20ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 0 of 8
= WiFi =
Network state is disabled
WiFi module is disabled
Failed messages: pending 2779096485, notready 2779096485, noresp 2779096485
Socket states: 0 0 0 0 0 0 0 0
ok(Yes I disabled the network after testing with it on, too)
I figured, based off of reading up on the Duet3d forums, that the sd card socket is faulty per the images shown (that match my sd card solder points) and the response from YAT.
I set it aside and pull out the Duet 3 Mini 5+ and give it a whirl, hoping I can at least start building the printer and use this board instead, choosing to deal with the Duet 2 Wifi at a later date. I somehow update the firmware then try to connect to the Duet Web Server and I am rejected. I open YAT and run M122 and get the following:
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.2 (2022-09-13 15:14:33) running on Duet 3 Mini5plus Ethernet (standalone mode)
Board ID: ZTVJA-K396U-D65J0-40KMG-JN03Z-76KJK
Used output buffers: 1 of 40 (1 max)
=== RTOS ===
Static ram: 103684
Dynamic ram: 103264 of which 0 recycled
Never used RAM 34764, free system stack 160 words
Tasks: NETWORK(ready,6.8%,547) HEAT(notifyWait,0.0%,374) Move(notifyWait,0.0%,363) CanReceiv(notifyWait,0.0%,942) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.0%,341) TMC(notifyWait,0.0%,124) MAIN(running,57.7%,613) IDLE(ready,34.6%,30) AIN(delaying,0.9%,271), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:00:21 ago, cause: power up
Last software reset details not available
Error status: 0x00
MCU revision 3, ADC conversions started 22036, completed 22035, timed out 0, errs 0
Step timer max interval 660
MCU temperature: min 23.1, current 24.0, max 24.2
Supply voltage: min 0.4, current 0.9, 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 29809916
Slowest loop: 0.20ms; 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, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
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 ===
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
=== CAN ===
Messages queued 108, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 108/0/0
Tx timeouts 0,0,107,0,0,0 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 0.18ms; 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 0
Socket states: 0 0 0 0 0 0 0 0
ok(Yes, I disabled the network after testing with it on, too)
Am I cursed with the worst luck when it comes to Duet3d Boards? I tried multiple SD cards. All of them formatted with SD Card Formatter that I downloaded per the Duet3d instructions. All the SD cards are between 8-32gb. All formatted correctly.
Seeing as I purchased these boards over 2 years ago, they're clearly out of warranty, yet brand new Please help. I've been troubleshooting trying everything I can for 2 days.
I'm attaching 2 images of each board's SD solder points.
-
RE: Duet 3 Mini 5+ unable to connect via browser
@timcurtis67 Were that an option to begin with, I would have, but the only option provided was to return for a replacement.
-
RE: Duet 3 Mini 5+ unable to connect via browser
@Phaedrux Any updates on when stock is being sent out? Still awaiting the replacement for my faulty board. Thanks in advance.
-
RE: Duet 3 Mini 5+ unable to connect via browser
@dc42 well, I returned the faulty board per your instruction. Filastruder (my supplier) was quick to respond and send me a prepaid label. Sadly, they say there is no current stock. Is there a time frame as to when the Duet 3 Mini 5+ will be back in stock for US retailers? I feel like I'm getting the crap end of the stick in this situation (ie - buying a new board, having the new board be faulty, having an offline printer until I receive a replacement, having no current replacement available). Isn't there anything else that can be done by the Duet3D team to help make this right?
-
RE: Duet 3 Mini 5+ unable to connect via browser
@dc42 No worries. I purchased it from Filastruder here in the US. I'll message them this evening pointing them to this thread per your instructions. Thank you for your help!
-
RE: Duet 3 Mini 5+ unable to connect via browser
@dc42 Yat reports the following:
M115
FIRMWARE_NAME: RepRapFirmware for Duet 3 Mini 5+ FIRMWARE_VERSION: 3.2 ELECTRONICS: Duet 3 Mini5plus Ethernet FIRMWARE_DATE: 2021-01-05
okM20 P"/www"
Begin file list
NONE
End file list
ok
M21Error: M21: Cannot initialise SD card 0: Card is unusable
ok
M20 P"/"
Begin file list
NONE
End file list
okI've tried multiple SD cards all within spec. I know I must be doing something wrong, I just don't know what