Duet looses connection to sd card.
Hey, so i have a new problem with my Duet 3 Mini 5 Plus.
When i startup the printer it all works fine and without any problem. Then if i try to start a print it prints for like 10 minutes. Afterwards the printer just stops mid print. I can still access the DWC and the buttons work. If i refresh the page i get the following error:
"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 googled it and it seems that my board cant read the sd card anymore. Trying to remount the SD card over M21, returns in an error that the sd card is unreadable. If i then restart the printer everything works fine again.
Could it be that just the sd card died or something and is faulty. I would try another one but before that, there may be another issue.
I reformatted the sd card on my pc and resliced the gcode. After running it again the same error occured.
Error: Cannot read file, error code 1
Cancelled printing file 0:/gcodes/Rotation visualizer.gcode, print time was 0h 4m
Im just not sure why. I changed nothing at the electronics, the error accoured randomly.
@staticred M112 results
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.3RC3 (2021-05-26 13:44:42) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: N85PY-3096U-D65J0-40KMD-3J03Z-RHQAD
Used output buffers: 3 of 40 (13 max)
=== RTOS ===
Static ram: 102572
Dynamic ram: 106244 of which 52 recycled
Never used RAM 31980, free system stack 134 words
Tasks: NETWORK(ready,16.0%,234) HEAT(delaying,0.0%,320) Move(notifyWait,0.2%,276) CanReceiv(notifyWait,0.0%,943) CanSender(notifyWait,0.0%,358) CanClock(delaying,0.0%,339) TMC(notifyWait,0.7%,114) MAIN(running,81.9%,426) IDLE(ready,0.3%,29) AIN(delaying,0.8%,264), total 100.0%
Owned mutexes: WiFi(NETWORK) HTTP(MAIN)
=== Platform ===
Last reset 00:08:05 ago, cause: power up
Last software reset at 2021-06-20 14:23, reason: User, GCodes spinning, available RAM 34836, slot 2
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
MCU revision 3, ADC conversions started 486123, completed 486122, timed out 0, errs 0
Step timer max interval 1490
MCU temperature: min 26.4, current 42.0, max 43.1
Supply voltage: min 23.6, current 23.8, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/26/26, gc cycles 0
Driver 0: position 12580, standstill, SG min/max 0/418, read errors 0, write errors 0, ifcnt 12, reads 25520, writes 12, timeouts 0, DMA errors 0
Driver 1: position -125, standstill, SG min/max 0/116, read errors 0, write errors 0, ifcnt 12, reads 25520, writes 12, timeouts 0, DMA errors 0
Driver 2: position 21156, standstill, SG min/max 0/150, read errors 0, write errors 0, ifcnt 12, reads 25520, writes 12, timeouts 0, DMA errors 0
Driver 3: position 0, standstill, SG min/max 0/18, read errors 0, write errors 0, ifcnt 12, reads 25519, writes 12, timeouts 0, DMA errors 0
Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 25523, writes 9, timeouts 0, DMA errors 0
Driver 5: position 0, assumed not present
Driver 6: position 0, assumed not present
Date/time: 2021-06-20 17:02:58
Cache data hit count 908366785
Slowest loop: 2320.57ms; fastest: 0.10ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 101.3ms, write time 17.7ms, max retries 0
=== Move ===
DMs created 83, maxWait 168308ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 5179, completed moves 5179, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 2], 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 = 0 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is ready with "M122 " in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle 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 4378, send timeouts 4375, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17), ts 2430/0/0
Last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 1470.92ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.26
WiFi MAC address f0:08:d1:02:ef:56
WiFi Vcc 3.38, reset reason Power up
WiFi flash size 2097152, free heap 22192
WiFi IP address 192.168.178.106
WiFi signal strength -57dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
- WiFi -
@staticred updated now to full release of 3.3. Same issue still. I hope my duet didnt broke randomly.
@staticred unfortunately there is an issue with some early production Duet 3 Mini boards whereby the ESD protection chip loses a contact with the PCB, causing the SD card to become inaccessible. Please email email@example.com and cc your supplier. You will receive a reply with a link to a form to fill in.
StaticRed last edited by StaticRed
@dc42 oh wow that was the issue? Well thats nice then i did not ruin anything haha. Yes i will send a message to that email. I have a good contact to my supplier (i work there) so that hopefully will be a fast exchange. I btw tried to change my sdcard, which did actually work for one print, but now it seems like it stopped working aswell.
Thanks for the quick response, you saved my day
@staticred I'm sorry for the inconvenience this has caused you.
@dc42 thats no problem. I dont need the printer 24/7 i have other printers which can get the job done. I thank you for the advice.