Duet Mini 5+ stuck in SBC mode
-
Ok, I just got my new board and when i connect with YAT and run m552 i get
Error: M552: Network-related commands are not supported when using an attached Single Board Computer<LF>ok<LF>. so i run M122 with SD card installed i get this.I have tried two different SD cards and still not luck. Here is m122 with out the SD card.
Do i have a bad board?
-
@moonman when and where did you purchase the board?
can you confirm that the sd card is formatted as fat32?
can you edit your YAT settings to follow this? https://docs.duet3d.com/en/How_to_guides/Getting_connected/Getting_connected_to_your_Duet#yat-settings so that your M122 outputs are more readable? -
this month on the 6th. SD card are Fat32.
here is the m122 again.With out card.
m122<CR>
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.6-rc.1 (2023-06-28 17:19:37) running on Duet 3 Mini5plus Ethernet (SBC mode)
Board ID: RD0JZ-HB67A-G65J0-401GW-KU82Z-ZMYUJ
Used output buffers: 1 of 40 (1 max)
=== RTOS ===
Static ram: 103712
Dynamic ram: 95292 of which 12 recycled
Never used RAM 42696, free system stack 150 words
Tasks: SBC(notifyWait,0.0%,972) HEAT(notifyWait,0.0%,374) Move(notifyWait,0.0%,363) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,335) CanClock(delaying,0.0%,342) TMC(notifyWait,0.0%,124) MAIN(running,98.9%,580) IDLE(ready,0.3%,30) AIN(delaying,0.8%,273), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:00:34 ago, cause: power up
Last software reset time unknown, reason: StuckInSpinLoop, GCodes spinning, available RAM 50164, slot 1
Software reset code 0x0083 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0000080f BFAR 0xe000ed38 SP 0x2002f0dc Task SBC Freestk 624 ok
Stack: 0004206f 00040ae0 61000000 a5a5a5a5 a5a5a5a5 00000000 0004206f a5a5a5a5 a5a5a5a5 a5a5a5a5 00000000 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5
Error status: 0x00
MCU revision 3, ADC conversions started 34531, completed 34531, timed out 0, errs 0
Step timer max interval 1490
MCU temperature: min 34.7, current 37.1, max 37.1
Supply voltage: min 0.2, current 0.5, max 0.5, 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 80045784
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 172, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 172/0/0
Tx timeouts 0,0,171,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 0x0f698
Buffer RX/TX: 0/0-0, open files: 0
okand with card
m122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.6-rc.1 (2023-06-28 17:19:37) running on Duet 3 Mini5plus Ethernet (SBC mode)
Board ID: RD0JZ-HB67A-G65J0-401GW-KU82Z-ZMYUJ
Used output buffers: 1 of 40 (16 max)
=== RTOS ===
Static ram: 103712
Dynamic ram: 95292 of which 12 recycled
Never used RAM 42696, free system stack 152 words
Tasks: SBC(notifyWait,0.0%,972) HEAT(notifyWait,0.0%,374) Move(notifyWait,0.0%,363) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,335) CanClock(delaying,0.0%,342) TMC(notifyWait,0.0%,124) MAIN(running,99.2%,374) IDLE(ready,0.0%,30) AIN(delaying,0.8%,272), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:05:34 ago, cause: power up
Last software reset time unknown, reason: StuckInSpinLoop, GCodes spinning, available RAM 50164, slot 1
Software reset code 0x0083 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0000080f BFAR 0xe000ed38 SP 0x2002f0dc Task SBC Freestk 624 ok
Stack: 0004206f 00040ae0 61000000 a5a5a5a5 a5a5a5a5 00000000 0004206f a5a5a5a5 a5a5a5a5 a5a5a5a5 00000000 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5
Error status: 0x00
MCU revision 3, ADC conversions started 334095, completed 334094, timed out 0, errs 0
Step timer max interval 1489
MCU temperature: min 32.6, current 35.9, max 36.3
Supply voltage: min 0.5, current 0.5, max 0.5, 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 781611031
Slowest loop: 0.23ms; fastest: 0.14ms
=== 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 1425, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 1425/0/0
Tx timeouts 0,0,1425,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 0x0f698
Buffer RX/TX: 0/0-0, open files: 0
ok -
@moonman thanks. one for @droftarts or @Phaedrux
-
@moonman Where did you buy that board?
-
I got it from Filastruder.com.
-
@moonman The boards is reverting to SBC mode because it can't find an SD card. Both your M122 reports show no SD card, so either the SD card is not pushed far enough into the socket, or there's a failure of the card or card socket.
If you have tried an alternative card (make sure it is formatted correctly, and has the right files on it, see https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card#formatting), and you're sure you have pushed it in far enough, can you post a good picture of the pins of the SD card holder? See https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card#sd-card-socket
Ian
-
Yes I have tried 3 cards now and I used that link to format and install the files. I am pretty sure the card is in all the way. Also I don't know if this matters but the network port has no lights on when I plug in the Cable I assume that's is because it is in SBC mode.
-
@moonman the socket soldering looks fine. Can you show a bit more of the area behind the SD card socket? On the Mini 5+, occasionally it’s be of the small components behind the socket that fails.
Ian
-
@droftarts Yes, I will after work.
-
@droftarts here is the picture.
-
@moonman said in Duet Mini 5+ stuck in SBC mode:
I got it from Filastruder.com.
When did you buy it?
-
@Phaedrux
@moonman said in Duet Mini 5+ stuck in SBC mode:this month on the 6th
Let's replace your board under warranty. Please send an email to warranty@duet3d.com and put Filastruder in CC. Also add a link to this forum thread and the details of your purchase. After that you'll receive a form to fill out.
-
@chrishamm will do thanks.