Duet 3D Seems to believe there's an SBC when there isn't
-
Hi, I'm extremely new to this, building my first 3d Printer using a Duet 3 6HC. I'm not planning on using an SBC, not have I ever plugged one into my Duet. I started with https://docs.duet3d.com/en/How_to_guides/Getting_connected/Getting_connected_to_your_Duet but didn't get very far because as soon as I tried to enter the m552 command into the terminal (Step 5) to check the status of the network, it gave me this error:
Error: M552: Network-related commands are not supported when using an attached Single Board Computer
okIt gives me that same error with any m552 command i put in, such as m552 s0
or M552 S1 P0.0.0.0My firmware is on version:
FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.3 ELECTRONICS: Duet 3 MB6HC v1.01 or later FIRMWARE_DATE: 2021-06-15 21:45:56
I really don't know much more than that and I couldn't find anything else about this issue on the internet or in the documentation. Again, this is literally the first time I've even turned the thing on, and it's never been connected to an SBC so I have no idea why it thinks it is. The only things plugged into it are the SD card it came with, the USB cable to connect it to my computer and the ethernet cable. Can someone help me to get it to stop recognizing an SBC that isn't there, so I can get back to setting the thing up? Thanks
-
There may be an issue with the board. Can you send M122 from the USB terminal and post the response?
Can you also try doing the same with the SD card removed?
When and where did you purchase the Duet board?
-
Thank you for replying,
When I send the M122 this is what I get:
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3 (2021-06-15 21:45:47) running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-9P63L-DJ3S0-7JKD4-3S46K-9UKR8
Used output buffers: 1 of 40 (13 max)
=== RTOS ===
Static ram: 150904
Dynamic ram: 59980 of which 0 recycled
Never used RAM 143308, free system stack 190 words
Tasks: SBC(ready,3.2%,606) HEAT(delaying,0.0%,412) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,342) TMC(notifyWait,0.0%,105) MAIN(running,96.7%,1147) IDLE(ready,0.0%,29), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:03:49 ago, cause: power up
Last software reset details not available
Error status: 0x00
Step timer max interval 521
MCU temperature: min 32.4, current 34.5, max 34.7
Supply voltage: min 0.1, current 0.1, max 0.2, under voltage events: 0, over voltage events: 0, power good: no
12V rail voltage: min 0.2, current 0.2, max 0.2, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max not available
Driver 1: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max not available
Driver 2: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max not available
Driver 3: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max not available
Driver 4: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max not available
Driver 5: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max not available
Date/time: 1970-01-01 00:00:00
Slowest loop: 0.10ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], 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 = -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== 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 695, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 49 (min 49), ts 695/0/0
Tx timeouts 0,0,695,0,0,0 last cancelled message type 30 dest 127=== SBC interface ===
State: 0, failed transfers: 0, checksum errors: 0
Last transfer: 229212ms ago
RX/TX seq numbers: 0/1
SPI underruns 0, overruns 0
Disconnects: 0, timeouts: 0, IAP RAM available 0x2c83c
Buffer RX/TX: 0/0-0
okWith the SD card removed I get
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3 (2021-06-15 21:45:47) running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-9P63L-DJ3S0-7JKD4-3S46K-9UKR8
Used output buffers: 1 of 40 (13 max)
=== RTOS ===
Static ram: 150904
Dynamic ram: 59980 of which 0 recycled
Never used RAM 143308, free system stack 190 words
Tasks: SBC(ready,3.2%,606) HEAT(delaying,0.0%,412) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,342) TMC(notifyWait,0.0%,105) MAIN(running,96.7%,1147) IDLE(ready,0.0%,29), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:04:35 ago, cause: power up
Last software reset details not available
Error status: 0x00
Step timer max interval 724
MCU temperature: min 34.5, current 35.1, max 35.1
Supply voltage: min 0.1, current 0.1, max 0.2, under voltage events: 0, over voltage events: 0, power good: no
12V rail voltage: min 0.2, current 0.2, max 0.2, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max not available
Driver 1: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max not available
Driver 2: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max not available
Driver 3: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max not available
Driver 4: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max not available
Driver 5: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max not available
Date/time: 1970-01-01 00:00:00
Slowest loop: 0.10ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], 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 = -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== 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 230, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 49 (min 49), ts 230/0/0
Tx timeouts 0,0,230,0,0,0 last cancelled message type 30 dest 127=== SBC interface ===
State: 0, failed transfers: 0, checksum errors: 0
Last transfer: 275335ms ago
RX/TX seq numbers: 0/1
SPI underruns 0, overruns 0
Disconnects: 0, timeouts: 0, IAP RAM available 0x2c83c
Buffer RX/TX: 0/0-0
okI bought it (along with a PanelDue that I haven't even tried turning on or plugging in yet) from Filastruder in March, 2022, but haven't really gotten around to actually turning it on until now (printer project was on hold for a while)
-
SD card 0 detected, interface speed: 37.5MBytes/sec
SD card 0 not detected, interface speed: 37.5MBytes/sec
Can you try putting the SD card into your PC and seeing what files you have on it?
Do you happen to have another SD card handy to test? If the original SD card has files visible on it, copy them all over to the new SD card and try that one.
It's possible that the SD card has an issue rather than the board itself. If that doesn't do it, then the board would be replaced. Sorry for the inconvenience.
-
One this to test as well. It shows the SD card detected in the M122 report. Can you duplicate that test and when it shows detected, press the reset button on the board itself. Then send M122 again. Does it still show SBC mode at the top?
-
Thank you so much. It does seem to have been the SD card. I got a new one, copied the files like you said and now it seems to be working, for reference, here is what I get now with the new SD card when I send m552 (with the IP adresses removed, not sure if that's wise to do or pointless):
Ethernet is enabled, configured IP address: ..., actual IP address: 0.0.0.0
ok
Ethernet running, IP address = ...And the other commands seem to be working correctly as well. Thank you so much for your help, and I have no idea how you came to that conclusion about the SD card being the issue, but if it's easy enough to explain I'd love to know what you saw in that data that pointed you to that. Either way though, thanks!
-
SBC mode requires removing the SD card from the Duet board, so if the SD card is physically there, but it still detects as being in SBC mode that indicates something may be wrong with the SD card slot, or the SD card itself.
When the Duet is in SBC mode the Pi does the networking, so network commands aren't accepted.
Sorry about the dud SD card. You might be able to do a full format of the card and get it working again.
Now that you're up and running again you can follow through the getting connected guide: https://docs.duet3d.com/en/How_to_guides/Getting_connected/Getting_connected_to_your_Duet
-
undefined Phaedrux marked this topic as a question
-
undefined Phaedrux has marked this topic as solved
