Duet 3 Disconnects from SBC
-
Some of the older firmware didn't update properly with the normal apr-get update method. In these cases you'd need to update the board firmware separately. Once you're at 3.1.1 it should "just work" going forward.
You should be able to update the board firmware by uploading the firmware zip file to the /sys folder in DWC just as you would normally with any other Duet.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.1.1/Duet2and3Firmware-3.1.1.zip
If that doesn't work, then you have the option of using Bossa to flash the firmware to the board over USB with a PC.
-
@mrenz999 said in Duet 3 Disconnects from SBC:
@bearer Hmmm. Well it updated the Pi but not the Duet 3. Is there something else I should be doing ?
not really, but it'd be helpfull to see the output from apt as it would allude to why the firmware failed.
should be as simple as doing
echo S997 | sudo /opt/dsf/bin/CodeConsolefrom ssh if the duet is communicating with the pi (if its not then thats why the upgrade failed, but afaik not been an issue after 3.0) -
@bearer pi@duet3:~ $ echo S997 | sudo /opt/dsf/bin/CodeConsole
Unhandled exception. System.Net.Internals.SocketExceptionFactory+ExtendedSocketException (99): Cannot assign requested address /var/run/dsf/dcs.sock
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at DuetAPIClient.BaseConnection.Connect(ClientInitMessage initMessage, String socketPath, CancellationToken cancellationToken) in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetAPIClient/BaseConnection.cs:line 98
at CodeConsole.Program.Main(String[] args) in /home/christian/Duet3D/DuetSoftwareFramework/src/CodeConsole/Program.cs:line 44
at CodeConsole.Program.<Main>(String[] args)
Aborted
This is the result of it. -
Did you try uploading the Zip in DWC?
-
@Phaedrux I did download it. However, I am unable to connect to DWC now for some reason. It says Failed to connect to Duet3.local DCS not started. I hard power reset both, unplugged and left off for a few mins and replugged them in. Is there a way to do it through the pi ?
-
If the pi is connected to the duet via usb you can use bossa to flash the duet. That may be a better option if it's too much hassle getting everything disconnected to get it to a PC to flash. But if you have a laptop or PC nearby that might be easier if you're not comfortable with the pi environment.
-
@Phaedrux I have a laptop. Do I need to disconnect everything from the board or just plug in and do it ?
-
@Phaedrux Verify failed
Page errors: 1115
Byte errors: 564485
This was the response when I used BOSSA through the pi -
@mrenz999 said in Duet 3 Disconnects from SBC:
Unhandled exception. System.Net.Internals.SocketExceptionFactory+ExtendedSocketException (99): Cannot assign requested address /var/run/dsf/dcs.sock
...
Aborted
This is the result of it.so that could be why it didn't upgrade with apt, as pi and duet aren't communicating over the spi link and that also prevent duet web control working.
seeing as bossac failed, maybe try different usb cable or from a computer instead (or disconnect any power hungry peripherals to eliminate usb power supply issues)
-
@Phaedrux Ok I got it updated using BOSSA through the pi. 2 failed prints later.
m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956L2-G43S8-6J1FA-3SJ6P-1B06G
Used output buffers: 1 of 40 (13 max)
=== RTOS ===
Static ram: 154604
Dynamic ram: 163364 of which 20 recycled
Exception stack ram used: 536
Never used ram: 74692
Tasks: NETWORK(ready,1972) HEAT(blocked,1188) CanReceiv(suspended,3820) CanSender(suspended,1420) CanClock(blocked,1436) TMC(blocked,68) MAIN(running,2868) IDLE(ready,76)
Owned mutexes:
=== Platform ===
Last reset 10:16:20 ago, cause: software
Last software reset at 2020-09-05 05:11, reason: User, spinning module LinuxInterface, available RAM 75124 bytes (slot 3)
Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 40.5, current 40.8, max 43.9
Supply voltage: min 23.9, current 24.1, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.1, max 12.1, under voltage events: 0
Driver 0: standstill, reads 56301, writes 8 timeouts 0, SG min/max 0/591
Driver 1: standstill, reads 56300, writes 8 timeouts 0, SG min/max 0/646
Driver 2: standstill, reads 56301, writes 8 timeouts 0, SG min/max 0/99
Driver 3: standstill, reads 56300, writes 8 timeouts 0, SG min/max 0/97
Driver 4: standstill, reads 56300, writes 8 timeouts 0, SG min/max 0/78
Driver 5: standstill, reads 56304, writes 4 timeouts 0, SG min/max 0/847
Date/time: 2020-09-05 15:27:29
Slowest loop: 5.84ms; fastest: 0.15ms
=== 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 ===
Hiccups: 0(0), FreeDm: 375, MinFreeDm: 292, MaxWait: 9557402ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 41108, completed moves: 41108, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== Heat ===
Bed heaters = 0 -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 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 assembling a command 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 0, running macro
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 2.13ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 0 of 8- Ethernet -
State: disabled
Error counts: 0 0 0 0 0
Socket states: 0 0 0 0 0 0 0 0
=== CAN ===
Messages sent 91415, longest wait 0ms for type 0
=== Linux interface ===
State: 0, failed transfers: 309
Last transfer: 16ms ago
RX/TX seq numbers: 20337/20313
SPI underruns 118, overruns 118
Number of disconnects: 0
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.1.1
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 32.45
- Ethernet -
-
Does it fail on every print now?
Can you share the gcode file you're printing?
Can you setup debugging info?
https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Monitoring_optional
-
@Phaedrux Yes every print. I have tried mulitple prints. I will setup debugging and share the Gcode this evening when I get back from work. Every print it just stops about 10% or so in. It has rebooted but on the status page it says it has completed the print.
-
@Phaedrux
Where can I upload the file I was printing ?
m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956L2-G43S8-6J1FA-3SJ6P-1B06G
Used output buffers: 1 of 40 (10 max)
=== RTOS ===
Static ram: 154604
Dynamic ram: 163156 of which 20 recycled
Exception stack ram used: 528
Never used ram: 74908
Tasks: NETWORK(ready,1972) HEAT(blocked,1188) CanReceiv(suspended,3820) CanSender(suspended,1420) CanClock(blocked,1436) TMC(blocked,68) MAIN(running,2672) IDLE(ready,76)
Owned mutexes:
=== Platform ===
Last reset 00:28:11 ago, cause: power up
Last software reset at 2020-09-05 17:15, reason: User, spinning module LinuxInterface, available RAM 74692 bytes (slot 0)
Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 36.1, current 41.6, max 41.7
Supply voltage: min 23.9, current 24.1, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.1, max 12.1, under voltage events: 0
Driver 0: standstill, reads 53593, writes 17 timeouts 0, SG min/max 0/216
Driver 1: standstill, reads 53594, writes 17 timeouts 0, SG min/max 0/165
Driver 2: standstill, reads 53594, writes 17 timeouts 0, SG min/max 0/104
Driver 3: standstill, reads 53594, writes 17 timeouts 0, SG min/max 0/98
Driver 4: standstill, reads 53595, writes 17 timeouts 0, SG min/max 0/103
Driver 5: standstill, reads 53595, writes 17 timeouts 0, SG min/max 0/210
Date/time: 2020-09-06 03:21:15
Slowest loop: 5.23ms; fastest: 0.14ms
=== 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 ===
Hiccups: 0(0), FreeDm: 375, MinFreeDm: 340, MaxWait: 1539522ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 1396, completed moves: 1396, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== Heat ===
Bed heaters = 0 -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 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 assembling a command 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.
=== Network ===
Slowest loop: 2.14ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 0 of 8- Ethernet -
State: disabled
Error counts: 0 0 0 0 0
Socket states: 0 0 0 0 0 0 0 0
=== CAN ===
Messages sent 6679, longest wait 0ms for type 0
=== Linux interface ===
State: 0, failed transfers: 2
Last transfer: 22ms ago
RX/TX seq numbers: 54222/54222
SPI underruns 3, overruns 3
Number of disconnects: 0
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.1.1
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 14.09
- Ethernet -
-
@Phaedrux
Duet Control Server v3.1.1
Written by Christian Hammacher for Duet3D
Licensed under the terms of the GNU Public License Version 3[info] Settings loaded
[info] Environment initialized
[fatal] Could not connect to Duet (Board is not available (no header))
[debug] System.OperationCanceledException: Board is not available (no header)
at DuetControlServer.SPI.DataTransfer.ExchangeHeader() in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetControlServer/SPI/DataTransfer.cs:line 1093
at DuetControlServer.SPI.DataTransfer.PerformFullTransfer(Boolean connecting) in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetControlServer/SPI/DataTransfer.cs:line 162
at DuetControlServer.SPI.DataTransfer.Init() in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetControlServer/SPI/DataTransfer.cs:line 102
at DuetControlServer.Program.Main(String[] args) in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetControlServer/Program.cs:line 10This is what i get when I try to run debug
-
@mrenz999 said in Duet 3 Disconnects from SBC:
Where can I upload the file I was printing ?
If it's small enough you can upload it here. If it's too large try zipping it and use dropbox or something like that to share it.
-
@Phaedrux
https://www.dropbox.com/s/c1a8ve3eq0kahxr/CFFFP_lotus_nightlight.gcode?dl=0
Constant G28 network errors pop up. -
@mrenz999 said in Duet 3 Disconnects from SBC:
Constant G28 network errors pop up.
What does this mean?
-
@Phaedrux It means everything I do pops that up on the bottom right of the screen. However, I completely redid the SBC and this morning everything seems to be working.
-
It says G28 network error?
Well glad to hear that it seems to be working now.
