Duet 3 Disconnects from SBC

mrenz999 · 4 Sept 2020, 01:44

During printing my SBC says randomly "Network error, not connected" Then shuts down the print I have running. Not sure what is causing this.

Phaedrux · 4 Sept 2020, 02:26

Please provide the results of M122 after this occurs.

And setup some debug monitoring to capture more information.

https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Monitoring_optional

mrenz999 · 4 Sept 2020, 03:55

@Phaedrux Warning: Lost connection to Duet (Board is not available (no data response))
Warning: Controller has been reset

Just happened. Will do M112 as well.

Phaedrux · 4 Sept 2020, 04:00

M122 is diagnostics

M112 is reset

mrenz999 · 4 Sept 2020, 04:17

@Phaedrux Opps typo lol
m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.01-RC9 running on Duet 3 MB6HC v1.01 or later
Board ID: 08DJM-956L2-G43S8-6J1FA-3SJ6P-1B06GUsed output buffers: 1 of 40 (10 max)
=== RTOS ===
Static ram: 154572
Dynamic ram: 162084 of which 20 recycled
Exception stack ram used: 216
Never used ram: 76324
Tasks: NETWORK(ready,2076) HEAT(blocked,1196) CanReceiv(suspended,3824) CanSender(suspended,1484) CanClock(blocked,1432) TMC(blocked,216) MAIN(running,4652) IDLE(ready,80)
Owned mutexes:
=== Platform ===
Last reset 00:17:17 ago, cause: software
Last software reset at 2020-09-04 04:59, reason: User, spinning module LinuxInterface, available RAM 75604 bytes (slot 1)
Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 42.0, current 42.3, max 43.7
Supply voltage: min 24.1, current 24.1, max 24.2, 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 28510, writes 14 timeouts 0, SG min/max 0/0
Driver 1: standstill, reads 28510, writes 14 timeouts 0, SG min/max 0/0
Driver 2: standstill, reads 28511, writes 14 timeouts 0, SG min/max 0/0
Driver 3: standstill, reads 28511, writes 14 timeouts 0, SG min/max 0/0
Driver 4: standstill, reads 28512, writes 14 timeouts 0, SG min/max 0/0
Driver 5: standstill, reads 28512, writes 14 timeouts 0, SG min/max 0/0
Date/time: 2020-09-04 05:16:59
Slowest loop: 3.68ms; fastest: 0.14ms
=== Move ===
Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, 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
Heater 1 is on, I-accum = 0.0
=== 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
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 2.08ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
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 53, longest wait 0ms for type 0
=== Linux interface ===
State: 0, failed transfers: 0
Last transfer: 16ms ago
RX/TX seq numbers: 436/438
SPI underruns 0, overruns 0
Number of disconnects: 1
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.1.1
Trigger:
Finishing macro config.g, started by system

Next stack level
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 30.67

mrenz999 · 4 Sept 2020, 04:26

@Phaedrux
Started the print again with same results. Then ran M122
again
9/3/2020, 9:23:58 PM Leadscrew adjustments made: 0.273 0.190 0.300, points used 3, (mean, deviation) before (0.254, 0.047) after (0.000, 0.000)
9/3/2020, 9:23:46 PM m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.01-RC9 running on Duet 3 MB6HC v1.01 or later
Board ID: 08DJM-956L2-G43S8-6J1FA-3SJ6P-1B06GUsed output buffers: 1 of 40 (13 max)
=== RTOS ===
Static ram: 154572
Dynamic ram: 162708 of which 20 recycled
Exception stack ram used: 424
Never used ram: 75492
Tasks: NETWORK(ready,2076) HEAT(blocked,1184) CanReceiv(suspended,3824) CanSender(suspended,1432) CanClock(blocked,1432) TMC(blocked,80) MAIN(running,4436) IDLE(ready,80)
Owned mutexes:
=== Platform ===
Last reset 00:24:07 ago, cause: software
Last software reset at 2020-09-04 04:59, reason: User, spinning module LinuxInterface, available RAM 75604 bytes (slot 1)
Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 42.3, current 42.8, max 42.9
Supply voltage: min 23.0, current 23.7, 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: ok, reads 62668, writes 3 timeouts 0, SG min/max 0/215
Driver 1: ok, reads 62668, writes 3 timeouts 0, SG min/max 0/142
Driver 2: standstill, reads 62668, writes 3 timeouts 0, SG min/max 0/88
Driver 3: standstill, reads 62669, writes 3 timeouts 0, SG min/max 0/90
Driver 4: standstill, reads 62668, writes 3 timeouts 0, SG min/max 0/93
Driver 5: standstill, reads 62672, writes 0 timeouts 0, SG min/max not available
Date/time: 2020-09-04 05:23:50
Slowest loop: 4.72ms; fastest: 0.14ms
=== Move ===
Hiccups: 0(0), FreeDm: 373, MinFreeDm: 373, MaxWait: 1426733ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 15, completed moves: 14, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: 3
=== 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
Heater 0 is on, I-accum = 0.4
Heater 1 is on, I-accum = 0.6
=== GCodes ===
Segments left: 0
Movement lock held by File
HTTP* is ready with "M122" in state(s) 0
Telnet is idle in state(s) 0
File* is idle in state(s) 40 0 0, running macro
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
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 1.92ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
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 1644, longest wait 0ms for type 0
=== Linux interface ===
State: 0, failed transfers: 0
Last transfer: 18ms ago
RX/TX seq numbers: 13844/13846
SPI underruns 0, overruns 0
Number of disconnects: 1
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.1.1
File:
Finishing macro deployprobe.g, started by G30 P1 X20 Y365 Z-99999 ; probe near an adjusting screw

Next stack level
Executing macro bed.g, started by G32 ; bed compensation
Suspended code: G30 P2 X430 Y240 Z-99999 S3 ; probe near an adjusting screw and calibrate 3 motors
Suspended code: ;G29
Suspended code: ;M402 ; retract probe
Next stack level
Executing macro start.g, started by system
Suspended code: G28 ; home XYZ
Suspended code: ;G29 S1 ; load heightmap
Suspended code: ;M400
Suspended code: ;G10 P0 R80 S235 ; Set extruder to 180 and release
Suspended code: ;M98 P"0:/sys/ZSpeedsPrint.g" ; Load Z speeds for printing
Suspended code: ;M98 P"0:/sys/CurrentsPrint.g" ; Load print motor currents
Suspended code: ; Slicer Start Gcode begins.
Next stack level
Suspended code: T0
Suspended code: M190 S70
Suspended code: M104 S245
Suspended code: M109 S245
Suspended code: M82 ;absolute extrusion mode
Suspended code: M83 ;relative extrusion mode
Suspended code: G1 F1500 E-6.5
Suspended code: ;LAYER_COUNT:51
Suspended code: ;LAYER:0
Suspended code: M107
Suspended code: G0 F3600 X86.205 Y144.27 Z0.3
Suspended code: ;TYPE:SKIRT
Suspended code: G1 F1500 E6.5
Suspended code: G1 F1800 X86.965 Y143.845 E0.03139
Suspended code: G1 X88.334 Y143.116 E0.05591
Suspended code: G1 X88.714 Y142.922 E0.01538
Suspended code: G1 X89.867 Y142.356 E0.0463
Suspended code: G1 X90.079 Y142.272 E0.00822
Suspended code: G1 X91.185 Y141.751 E0.04407
Suspended code: G1 X91.433 Y141.647 E0.00969
Suspended code: G1 X92.556 Y141.229 E0.04319
Suspended code: G1 X93.411 Y140.916 E0.03282
Suspended code: G1 X94.083 Y140.698 E0.02547
Suspended code: G1 X94.905 Y140.451 E0.03094
Suspended code: G1 X95.523 Y140.28 E0.02311
Suspended code: G1 X96.059 Y140.127 E0.02009
Suspended code: G1 X96.74 Y139.945 E0.02541
Suspended code: G1 X97.539 Y139.75 E0.02965
Suspended code: G1 X97.766 Y139.701 E0.00837
Suspended code: G1 X98.593 Y139.536 E0.0304
Suspended code: G1 X98.654 Y139.529 E0.00221
Suspended code: G1 X99.964 Y139.278 E0.04808
Trigger:
Finishing macro config.g, started by system
Next stack level
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 32.69
File /opt/dsf/sd/gcodes/petgtriple-moon.gcode is selected, processing
9/3/2020, 9:23:36 PM Connection to Duet established
9/3/2020, 9:23:36 PM Warning: Lost connection to Duet (Board is not available (no data response))

mrenz999 · 4 Sept 2020, 05:37

9/3/2020, 10:36:20 PM m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.01-RC9 running on Duet 3 MB6HC v1.01 or later
Board ID: 08DJM-956L2-G43S8-6J1FA-3SJ6P-1B06GUsed output buffers: 1 of 40 (10 max)
=== RTOS ===
Static ram: 154572
Dynamic ram: 162500 of which 20 recycled
Exception stack ram used: 528
Never used ram: 75596
Tasks: NETWORK(ready,2076) HEAT(blocked,1184) CanReceiv(suspended,3824) CanSender(suspended,1432) CanClock(blocked,1432) TMC(blocked,80) MAIN(running,2808) IDLE(ready,80)
Owned mutexes:
=== Platform ===
Last reset 00:57:28 ago, cause: software
Last software reset at 2020-09-04 05:38, reason: User, spinning module LinuxInterface, available RAM 75388 bytes (slot 2)
Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 43.7, current 43.8, max 46.6
Supply voltage: min 23.1, current 24.1, max 24.2, 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 55532, writes 19 timeouts 0, SG min/max 0/216
Driver 1: standstill, reads 55533, writes 19 timeouts 0, SG min/max 0/182
Driver 2: standstill, reads 55533, writes 19 timeouts 0, SG min/max 0/117
Driver 3: standstill, reads 55533, writes 19 timeouts 0, SG min/max 0/867
Driver 4: standstill, reads 55534, writes 19 timeouts 0, SG min/max 0/107
Driver 5: standstill, reads 55534, writes 19 timeouts 0, SG min/max 0/202
Date/time: 2020-09-04 06:36:24
Slowest loop: 4.66ms; fastest: 0.14ms
=== Move ===
Hiccups: 0(0), FreeDm: 375, MinFreeDm: 330, MaxWait: 29338ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 3, 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
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 1.92ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
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 13776, longest wait 0ms for type 0
=== Linux interface ===
State: 0, failed transfers: 96
Last transfer: 19ms ago
RX/TX seq numbers: 46307/46300
SPI underruns 40, overruns 40
Number of disconnects: 1
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.49

jay_s_uk · 4 Sept 2020, 06:10

I would first suggest updating your firmware. You're still running 3.01-RC9

Phaedrux · 4 Sept 2020, 06:11

You're still on an old release candidate firmware. Please update to 3.1.1 your issue may already be solved.

mrenz999 · 4 Sept 2020, 15:25

@Phaedrux So it should just require a sudo apt-get update ?

A Former User · 4 Sept 2020, 15:33

as of 3.0.0 apt should just-work(tm) for upgrades (but expansion- or tool-boards needs to be upgraded by M997 until the scripts from the reprapfirmware package takes care of that)

mrenz999 · 4 Sept 2020, 16:05

@bearer Hmmm. Well it updated the Pi but not the Duet 3. Is there something else I should be doing ?

mrenz999 · 4 Sept 2020, 17:41

Is there something else to do other than that sudo apt-get update and upgrade that needs to be done?

Phaedrux · 4 Sept 2020, 18:07

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.

https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Updating_Duet_3_main_board_firmware

A Former User · 9 Apr 2020, 19:47

@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/CodeConsole from 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)

mrenz999 · 9 May 2020, 01:52

@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.

Phaedrux · 5 Sept 2020, 01:57

Did you try uploading the Zip in DWC?

mrenz999 · 9 May 2020, 02:25

@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 ?

Phaedrux · 5 Sept 2020, 03:26

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.

mrenz999 · 5 Sept 2020, 03:28

@Phaedrux I have a laptop. Do I need to disconnect everything from the board or just plug in and do it ?