Error: M552: Network-related cmds r not supported using SBC

[foesi]

I purchased a new Duet 3 mini 5+ from 'cr3d.de' a few weeks ago.
Now I wanted to setup the duet with YAT but somehow this error occurs when I type in M552

-> Error: M552: Network-related commands are not supported when using an attached Single Board Computer

When I type in M115 it tells me this

->FIRMWARE_NAME: RepRapFirmware for Duet 3 Mini 5+ FIRMWARE_VERSION: 3.4.1 ELECTRONICS: Duet 3 Mini5plus WiFi FIRMWARE_DATE: 2022-06-01 21:07:06

I also have tried to reformat the SD-card like explained but there is still no difference. By searching for a dead SD-card reader I found out to check the M122 which tells me this

->=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 0.0MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0

Is the problem with the M552 connected with a dead SD-card reader? Or is there another problem?
Any guesses appreciated!

[jay_s_uk]

@foesi looks like it. I take it you aren't using an SBC and the SD card is formatted as FAT32?

[foesi]

@jay_s_uk that is correct.
The SD-card is FAT32 and I have no SBC connected.

[jay_s_uk]

@foesi one for @Phaedrux
can you confirm when a few weeks ago was?

[foesi]

@jay_s_uk yes sure I can send you the details per Mail.
A few weeks ago means I purchased it at 03.07.2022

[Phaedrux]

Can you share the entire results of M122?

What do the contents of the SD card look like?

[foesi]

@phaedrux here are the results of M122 and the contents of the SD-card.

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.1 (2022-06-01 21:06:56) running on Duet 3 Mini5plus WiFi (SBC mode)
Board ID: KS8ZD-NT8LU-F65J0-409NL-1513Z-7LQYL
Used output buffers: 1 of 40 (1 max)
=== RTOS ===
Static ram: 103684
Dynamic ram: 96528 of which 0 recycled
Never used RAM 41500, free system stack 170 words
Tasks: SBC(notifyWait,0.0%,972) HEAT(notifyWait,0.0%,374) Move(notifyWait,0.0%,363) CanReceiv(notifyWait,0.0%,942) CanSender(notifyWait,0.0%,372) CanClock(delaying,0.0%,339) TMC(notifyWait,0.0%,123) MAIN(running,98.4%,583) IDLE(ready,0.8%,29) AIN(delaying,0.8%,274), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:00:12 ago, cause: power up
Last software reset details not available
Error status: 0x00
MCU revision 3, ADC conversions started 12868, completed 12868, timed out 0, errs 0
Step timer max interval 1490
MCU temperature: min 10.4, current 13.5, max 13.5
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 31761453
Slowest loop: 0.23ms; fastest: 0.00ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 0.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
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 64, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 64/0/0
Tx timeouts 0,0,63,0,0,0 last cancelled message type 30 dest 127
=== SBC interface ===
Transfer state: 0, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 0/1
SPI underruns 0, overruns 0
State: 0, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x0f1ec
Buffer RX/TX: 0/0-0, open files: 0
ok

[droftarts]

@foesi It looks like the Duet isn't seeing the SD card socket at all, so likely a soldering fault on the socket or one of the components nearby. Unfortunately these faults happen from time to time, despite factory testing. We are happy to offer you a warranty replacement, and sorry for the inconvenience.

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

[foesi]

I recently got the new duet board and - it works fine now! Thanks for your help!
It must have been the SD-card socket. Now I can get on with my project - which is to make the Duet 3 mini 5+ my controller for a Tronxy X5SA-600.
Thanks again and all in all it was surprisingly convenient to get the new board.