Duet 3 SBC DCS has stopped



  • Recently my printer has been stopping midprint. I've re-sliced the models but it happens with multiple models.

    The strange thing is when it resets it just stops printing. It doesn't reset the position or the heaters.

    Duet 3 SBC DCS has stopped.PNG This is what shows in the console after I started a print

    11/3/2020, 7:02:44 PM	Connection established
    11/3/2020, 7:02:28 PM	Connection interrupted, attempting to reconnect...
    DCS has been stopped
    11/3/2020, 4:22:40 PM	Connection to Duet established
    11/3/2020, 4:22:40 PM	Warning: Lost connection to Duet (Board is not available (no data response))
    11/3/2020, 3:43:50 PM	Connection to Duet established
    11/3/2020, 3:43:50 PM	Warning: Lost connection to Duet (Board is not available (no data response))
    11/3/2020, 1:59:36 PM	Height map saved to file heightmap.csv
    11/3/2020, 1:59:36 PM	16 points probed, min error -0.006, max error 0.010, mean 0.010, deviation 0.010
    

    M122

    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-6J9D0-3S46T-9U2LF
    Used output buffers: 1 of 40 (13 max)
    === RTOS ===
    Static ram: 154604
    Dynamic ram: 163392 of which 64 recycled
    Exception stack ram used: 568
    Never used ram: 74588
    Tasks: ETHERNET(blocked,824) NETWORK(ready,1968) HEAT(blocked,1188) CanReceiv(suspended,3820) CanSender(suspended,1412) CanClock(blocked,1436) TMC(blocked,60) MAIN(running,2672) IDLE(ready,76)
    Owned mutexes:
    === Platform ===
    Last reset 06:01:59 ago, cause: power up
    Last software reset at 2020-10-24 12:13, reason: User, spinning module LinuxInterface, available RAM 74836 bytes (slot 1)
    Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task MAIN
    Error status: 0
    MCU temperature: min 22.2, current 39.6, max 41.3
    Supply voltage: min 24.3, current 24.5, max 24.8, under voltage events: 0, over voltage events: 0, power good: yes
    12V rail voltage: min 12.0, current 12.1, max 12.2, under voltage events: 0
    Driver 0: standstill, reads 57080, writes 17 timeouts 0, SG min/max 0/226
    Driver 1: standstill, reads 57076, writes 21 timeouts 0, SG min/max 0/1023
    Driver 2: standstill, reads 57077, writes 21 timeouts 0, SG min/max 0/1023
    Driver 3: standstill, reads 57078, writes 21 timeouts 0, SG min/max 0/1023
    Driver 4: standstill, reads 57078, writes 21 timeouts 0, SG min/max 0/1023
    Driver 5: standstill, reads 57079, writes 21 timeouts 0, SG min/max 0/1023
    Date/time: 2020-11-03 19:03:24
    Slowest loop: 9.33ms; fastest: 0.13ms
    === 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: 321, MaxWait: 3040502ms
    Bed compensation in use: mesh, comp offset 0.000
    === MainDDARing ===
    Scheduled moves: 442248, completed moves: 442248, 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 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.
    === Network ===
    Slowest loop: 1.02ms; 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: establishingLink
    Error counts: 0 0 0 0 0
    Socket states: 0 0 0 0 0 0 0 0
    === Filament sensors ===
    Extruder 0 sensor: ok
    === CAN ===
    Messages sent 86669, longest wait 0ms for type 0
    === Linux interface ===
    State: 0, failed transfers: 10
    Last transfer: 21ms ago
    RX/TX seq numbers: 1187/35131
    SPI underruns 38, overruns 4
    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: 26.42
    

  • Moderator

    Can you enable extended monitoring and try to capture one of the freezes?

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

    Can you also provide some more details about your printer and your config?



  • This is similar symptoms I encountered with a dying Rpi.

    I tested by running the same file with the Duet-3 in standalone mode to confirm.



  • @Phaedrux
    CoreXY with 3 independent Z steppers
    24v PSU
    110 AC bed
    Anything else you need to know?

    ; Configuration file for Duet 3 (firmware version 3)
    ; executed by the firmware on start-up
    ;
    ; generated by RepRapFirmware Configuration Tool v3.1.3 on Sat Jul 11 2020 20:25:37 GMT-0500 (Central Daylight Time)
    
    ; General preferences
    M80													; Turns on the ATX power supply
    G90                                                ; send absolute coordinates...
    M83                                                ; but relative extruder moves
    M669 K1                                            ; select CoreXY mode
    
    ;Network
    M552 S1                                            ; Enable network
    M552 P192.168.1.52					;
    M553 P255.255.255.0					;
    M554 P192.168.1.1					;
    M586 P0 S1                                         ; Enable HTTP
    M586 P1 S0                                         ; Disable FTP
    M586 P2 S0                                         ; Disable Telnet
    
    ; Drives
    M569 P0.0 S1                                       ; physical drive 0.0 goes backwards
    M569 P0.1 S0                                       ; physical drive 0.1 goes backwards
    M569 P0.2 S0                                       ; physical drive 0.2 goes backwards
    M569 P0.3 S0                                       ; physical drive 0.3 goes backwards
    M569 P0.4 S0                                       ; physical drive 0.4 goes backwards
    M569 P0.5 S0                                       ; physical drive 0.5 goes backwards
    
    M671 X-36:345:346 Y157:301:17 S10	   ; leadscrews at Front left, right Front and right rear -65:363:363 Y166:304:25
    
    M584 X0.1 Y0.2 Z0.3:0.4:0.5 E0.0                           ; set drive mapping Z3=Left Front, Z4= Right Rear, Z5=Right Front
    M350 X32 Y32 Z16 E16 I1                            ; configure microstepping with interpolation
    M92 X200.00 Y200.00 Z400.00 E406.56                ; set steps per mm 406.56 409.85
    M566 X700.00 Y700.00 Z24.00 E2000.00                ; set maximum instantaneous speed changes (mm/min)
    M203 X18000 Y18000 Z800 E20000                   ; Set maximum speeds (mm/min) mm per minute/60=mm per second
    M201 X3000 Y3000 Z100 E4000			   				; Set accelerations (mm/s^2)
    M906 X1600 Y1600 Z1600 E800 I30                   ; Set motor currents (mA) and motor idle factor in per cent
    M84 S120                                             ; Disable motor idle current reduction
    
    ; Axis Limits
    M208 X0 Y1 Z0 S1                                   ; set axis minima
    M208 X330 Y319 Z445 S0                             ; set axis maxima
    
    ; Endstops
    M574 X2 S1 P"io1.in"                              ; configure active-high endstop for high end on X via pin i01.in
    M574 Y2 S1 P"io2.in"                              ; configure active-high endstop for high end on Y via pin i02.in
    M574 Z1 S2                                         ; configure Z-probe endstop for low end on Z
    M591 D0 P1 C"io3.in" S1							  ; configure filament runout sensor for high end on extruder drive 0 via pin i03.in
    
    ; Z-Probe
    M950 S0 C"io7.out"                                 ; create servo pin 0 for BLTouch
    M558 P9 C"^io7.in" H10 F300 T9000                   ; set Z probe type to bltouch and the dive height + speeds
    G31 P500 X0 Y0 Z1.230                               ; set Z probe trigger value, offset and trigger height
    M557 X65:328 Y21:291 S67.5                           ; define mesh grid
    
    ; Heaters
    M308 S0 P"temp0" Y"thermistor" A"Bed Temp" T100000 B4700 C0.0000000706                   ; configure sensor 0 as thermistor on pin temp0
    M308 S1 P"temp1" Y"thermistor" A"Extruder Temp" T100000 B4725 C0.0000000706               ; configure sensor 1 as thermistor on pin temp1
    M950 H0 C"out1" T0                                 ; create bed heater output on out0 and map it to sensor 0
    M950 H1 C"out2" T1                                 ; create nozzle heater output on out1 and map it to sensor 1
    M307 H0 A326.4 C1281.8 D11.0 V24.5 B0              ; Set PID for bed heater
    M140 H0                                            ; map heated bed to heater 0
    M143 H0 S100                                       ; set temperature limit for heater 0 to 100C
    M307 H1 A319.6 C112.6 D2.2 V24.5 S1.0 B0			; Set PID for Hotend .4Bmm nozzle
    M143 H1 S260                         				; Set temperature limit for heater 1 to 260C
    M308 S2 P"mcu-temp" Y"mcu-temp" A"Duet Board" ; Configure MCU sensor
    
    ; Fans
    M950 F0 C"out9" Q500                               ; create fan 0 on pin out9 and set its frequency
    M106 P0 C"Layer Fan" S0 H-1                                     ; set fan 0 value. Thermostatic control is turned off
    M950 F2 C"out7" Q500                               ; create fan 1 on pin out7 and set its frequency
    M106 P2 C"MB Fan" T40:55 H2                                  ; set fan 1 value. Thermostatic control is turned on
    M950 F1 C"out8" Q500                               ; create fan 1 on pin out8 and set its frequency
    M106 P1 S255 H1 T30                                  ; set fan 1 value. Thermostatic control is turned on
    M950 F3 C"out6" Q500                               ; create fan 1 on pin out8 and set its frequency
    M106 P3 S255 H1 T30                                  ; set fan 1 value. Thermostatic control is turned on
    
    
    ; Tools
    M563 P0 D0 H1 F0                                   ; define tool 0
    G10 P0 X0 Y0 Z0                                    ; set tool 0 axis offsets
    G10 P0 R0 S0                                       ; set initial tool 0 active and standby temperatures to 0C
    
    ; Custom settings are not defined
    M564 H0                                   	   ; Let the Jog buttons work blv: added to allow jog buttons
    
    ; Miscellaneous
    M575 P1 S1 B57600                                  ; enable support for PanelDue


  • Started a print a few hours ago. This time got I got these error's but the heater wasn't in a fault state.

    11/4/2020, 10:04:23 PM	Warning: Tool 0 was not driven because its heater temperatures were not high enough or it has a heater fault
    11/4/2020, 10:04:21 PM	Warning: Tool 0 was not driven because its heater temperatures were not high enough or it has a heater fault
    11/4/2020, 10:04:21 PM	Warning: Tool 0 was not driven because its heater temperatures were not high enough or it has a heater fault
    11/4/2020, 10:04:21 PM	Warning: Tool 0 was not driven because its heater temperatures were not high enough or it has a heater fault
    11/4/2020, 10:04:07 PM	Warning: Tool 0 was not driven because its heater temperatures were not high enough or it has a heater fault
    11/4/2020, 10:04:03 PM	Warning: Tool 0 was not driven because its heater temperatures were not high enough or it has a heater fault
    11/4/2020, 10:03:59 PM	Warning: Tool 0 was not driven because its heater temperatures were not high enough or it has a heater fault
    11/4/2020, 10:03:55 PM	Warning: Tool 0 was not driven because its heater temperatures were not high enough or it has a heater fault
    11/4/2020, 10:03:52 PM	Warning: Tool 0 was not driven because its heater temperatures were not high enough or it has a heater fault
    11/4/2020, 7:56:35 PM	Height map saved to file heightmap.csv
    

    The PI became unresponsive before I could get the logs for DWC
    This is from DWS

    DWS.txt


  • Moderator

    Is it possible there was an extrusion command issued while the heater wasn't at the min temp?



  • @Phaedrux I highly doubt it. That was in the middle of a print. I had to restart the printer to get it to respond so I couldn't take a screenshot but the temp was stable until those errors started showing and it wasn't in a fault state.



  • Capture.PNG

    I tried with a different raspberry pi but same outcome. I was able to connect a monitor but was unable to copy the full output. This was the best I could get



  • So it happened again. I swapped to a Raspberry Pi 4 with new firmware.

    11/6/2020, 12:04:08 AM	Cancelled printing file 0:/gcodes/a1.gcode, print time was 0h 20m
    11/6/2020, 12:04:08 AM	Warning: Controller has been reset
    11/5/2020, 11:48:41 PM	Height map saved to file heightmap.csv
    11/5/2020, 11:48:41 PM	16 points probed, min error -0.018, max error 0.070, mean 0.034, deviation 0.027
    11/5/2020, 11:48:41 PM	Leadscrew adjustments made: -0.027 -0.025 -0.033, points used 3, (mean, deviation) before (-0.028, 0.003) after (-0.000, 0.000)
    11/5/2020, 11:48:41 PM	Leadscrew adjustments made: -0.059 -0.023 -0.016, points used 3, (mean, deviation) before (-0.031, 0.014) after (0.000, 0.000)
    11/5/2020, 11:48:41 PM	Leadscrew adjustments made: -0.022 -0.039 -0.054, points used 3, (mean, deviation) before (-0.039, 0.010) after (0.000, 0.000)
    11/5/2020, 11:46:07 PM	Height map loaded from file heightmap.csv
    11/5/2020, 11:44:01 PM	M32 "0:/gcodes/a1.gcode"
    File 0:/gcodes/a1.gcode selected for printing
    
    11/6/2020, 12:12:01 AM	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-6J9D0-3S46T-9U2LF
    Used output buffers: 1 of 40 (13 max)
    === RTOS ===
    Static ram: 154604
    Dynamic ram: 163392 of which 64 recycled
    Exception stack ram used: 544
    Never used ram: 74612
    Tasks: ETHERNET(blocked,824) NETWORK(ready,1960) HEAT(blocked,1188) CanReceiv(suspended,3820) CanSender(suspended,1420) CanClock(blocked,1436) TMC(blocked,60) MAIN(running,2672) IDLE(ready,76)
    Owned mutexes:
    === Platform ===
    Last reset 03:23:27 ago, cause: power up
    Last software reset at 2020-11-05 20:48, reason: User, spinning module LinuxInterface, available RAM 74612 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 39.7, current 39.9, max 41.4
    Supply voltage: min 24.3, current 24.6, max 24.7, under voltage events: 0, over voltage events: 0, power good: yes
    12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0
    Driver 0: standstill, reads 17162, writes 4 timeouts 0, SG min/max 0/160
    Driver 1: standstill, reads 17162, writes 4 timeouts 0, SG min/max 0/400
    Driver 2: standstill, reads 17162, writes 4 timeouts 0, SG min/max 0/384
    Driver 3: standstill, reads 17162, writes 4 timeouts 0, SG min/max 0/1023
    Driver 4: standstill, reads 17162, writes 4 timeouts 0, SG min/max 0/1023
    Driver 5: standstill, reads 17162, writes 4 timeouts 0, SG min/max 0/1019
    Date/time: 2020-11-06 00:12:00
    Slowest loop: 9.38ms; fastest: 0.21ms
    === 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: 322, MaxWait: 302820ms
    Bed compensation in use: mesh, comp offset 0.000
    === MainDDARing ===
    Scheduled moves: 3599, completed moves: 3599, 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 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.
    === Network ===
    Slowest loop: 0.77ms; fastest: 0.03ms
    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: establishingLink
    Error counts: 0 0 0 0 0
    Socket states: 0 0 0 0 0 0 0 0
    === Filament sensors ===
    Extruder 0 sensor: ok
    === CAN ===
    Messages sent 7459, longest wait 0ms for type 0
    === Linux interface ===
    State: 0, failed transfers: 8
    Last transfer: 19ms ago
    RX/TX seq numbers: 2795/56430
    SPI underruns 13, overruns 11
    Number of disconnects: 3
    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.12
    

    DWS2.txt
    DCS.txt


  • Moderator

    Hi, please keep an eye out for RRF 3.2 Beta 3 which may have a fix for you. Not sure on the ETA other than.. soon.



  • This is mostly to maintain tracking

    Errored out a few times during printing but it didn't stop printing until 4:54:48

    11/6/2020, 4:59:19 PM	Connection established
    11/6/2020, 4:58:54 PM	Connection interrupted, attempting to reconnect...
    Network error
    11/6/2020, 4:54:57 PM	Connection established
    11/6/2020, 4:54:48 PM	Connection interrupted, attempting to reconnect...
    DCS has been stopped
    11/6/2020, 4:19:04 PM	Connection to Duet established
    11/6/2020, 4:19:04 PM	Warning: Lost connection to Duet (Board is not available (no data response))
    11/6/2020, 4:08:08 PM	Connection to Duet established
    11/6/2020, 4:08:08 PM	Warning: Lost connection to Duet (Board is not available (no data response))
    11/6/2020, 3:50:15 PM	Connection to Duet established
    11/6/2020, 3:50:15 PM	Warning: Lost connection to Duet (Board is not available (no data response))
    11/6/2020, 2:44:36 PM	Connection to Duet established
    11/6/2020, 2:44:36 PM	Warning: Lost connection to Duet (Board is not available (no data response))
    11/6/2020, 1:39:53 PM	Height map saved to file heightmap.csv
    
    	M98 P"config.g"
    HTTP is enabled on port 80
    FTP is disabled
    TELNET is disabled
    Warning: M307: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 351C
    
    11/6/2020, 5:01:05 PM	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-6J9D0-3S46T-9U2LF
    Used output buffers: 1 of 40 (10 max)
    === RTOS ===
    Static ram: 154604
    Dynamic ram: 163184 of which 64 recycled
    Exception stack ram used: 528
    Never used ram: 74836
    Tasks: ETHERNET(blocked,832) NETWORK(ready,1968) 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 03:27:54 ago, cause: power up
    Last software reset at 2020-11-05 20:48, reason: User, spinning module LinuxInterface, available RAM 74612 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 36.5, current 40.1, max 40.9
    Supply voltage: min 24.3, current 24.6, max 24.8, under voltage events: 0, over voltage events: 0, power good: yes
    12V rail voltage: min 12.0, current 12.1, max 12.2, under voltage events: 0
    Driver 0: standstill, reads 30653, writes 19 timeouts 0, SG min/max 0/227
    Driver 1: standstill, reads 30649, writes 23 timeouts 0, SG min/max 0/1023
    Driver 2: standstill, reads 30650, writes 23 timeouts 0, SG min/max 0/1023
    Driver 3: standstill, reads 30650, writes 23 timeouts 0, SG min/max 0/1023
    Driver 4: standstill, reads 30651, writes 23 timeouts 0, SG min/max 0/1023
    Driver 5: standstill, reads 30651, writes 23 timeouts 0, SG min/max 0/708
    Date/time: 2020-11-06 17:01:05
    Slowest loop: 9.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: 317, MaxWait: 187934ms
    Bed compensation in use: mesh, comp offset 0.000
    === MainDDARing ===
    Scheduled moves: 270437, completed moves: 270437, 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 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.
    === Network ===
    Slowest loop: 0.94ms; 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: establishingLink
    Error counts: 0 0 0 0 0
    Socket states: 0 0 0 0 0 0 0 0
    === Filament sensors ===
    Extruder 0 sensor: ok
    === CAN ===
    Messages sent 49847, longest wait 0ms for type 0
    === Linux interface ===
    State: 0, failed transfers: 22
    Last transfer: 20ms ago
    RX/TX seq numbers: 3664/7222
    SPI underruns 35, overruns 14
    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.07
    


  • Disconnected panel due

    11/6/2020, 5:23:22 PM	Connection established
    11/6/2020, 5:21:46 PM	Connection interrupted, attempting to reconnect...
    DCS has been stopped
    11/6/2020, 5:21:16 PM	Cancelled printing file 0:/gcodes/a1.gcode, print time was 0h 19m
    11/6/2020, 5:21:15 PM	Warning: Controller has been reset
    11/6/2020, 5:06:52 PM	Height map saved to file heightmap.csv
    
    11/6/2020, 5:23:59 PM	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-6J9D0-3S46T-9U2LF
    Used output buffers: 1 of 40 (13 max)
    === RTOS ===
    Static ram: 154604
    Dynamic ram: 163392 of which 140 recycled
    Exception stack ram used: 544
    Never used ram: 74536
    Tasks: ETHERNET(blocked,832) NETWORK(ready,1968) HEAT(blocked,1188) CanReceiv(suspended,3820) CanSender(suspended,1384) CanClock(blocked,1436) TMC(blocked,68) MAIN(running,2672) IDLE(ready,76)
    Owned mutexes:
    === Platform ===
    Last reset 03:50:47 ago, cause: power up
    Last software reset at 2020-11-05 20:48, reason: User, spinning module LinuxInterface, available RAM 74612 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 39.5, current 39.8, max 40.3
    Supply voltage: min 24.3, current 24.6, max 24.8, 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 32788, writes 7 timeouts 0, SG min/max 0/1023
    Driver 1: standstill, reads 32787, writes 8 timeouts 0, SG min/max 0/226
    Driver 2: standstill, reads 32788, writes 7 timeouts 0, SG min/max 0/1023
    Driver 3: standstill, reads 32788, writes 7 timeouts 0, SG min/max 0/179
    Driver 4: standstill, reads 32788, writes 7 timeouts 0, SG min/max 0/175
    Driver 5: standstill, reads 32788, writes 7 timeouts 0, SG min/max 0/127
    Date/time: 2020-11-06 17:23:58
    Slowest loop: 9.29ms; fastest: 0.21ms
    === 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: 323, MaxWait: 541330ms
    Bed compensation in use: mesh, comp offset 0.000
    === MainDDARing ===
    Scheduled moves: 3364, completed moves: 3364, 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 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.
    === Network ===
    Slowest loop: 0.76ms; fastest: 0.03ms
    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: establishingLink
    Error counts: 0 0 0 0 0
    Socket states: 0 0 0 0 0 0 0 0
    === Filament sensors ===
    Extruder 0 sensor: ok
    === CAN ===
    Messages sent 5531, longest wait 0ms for type 0
    === Linux interface ===
    State: 0, failed transfers: 22
    Last transfer: 20ms ago
    RX/TX seq numbers: 1766/48405
    SPI underruns 38, overruns 14
    Number of disconnects: 2
    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.03
    
    11/6/2020, 5:24:21 PM	M98 P"config.g"
    HTTP is enabled on port 80
    FTP is disabled
    TELNET is disabled
    Warning: M307: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 351C
    

    DWS3.txt
    DCS3.txt



  • So last night I swapped to standalone mode completely disconnecting the pi. I was able to print the same file I had issues with. So sounds like the issue is with the communication between the Pi and the Duet 3.

    I'm going to try the beta 3.2.3 with SBC and try again.


  • administrators

    @dhusolo said in Duet 3 SBC DCS has stopped:

    So last night I swapped to standalone mode completely disconnecting the pi. I was able to print the same file I had issues with. So sounds like the issue is with the communication between the Pi and the Duet 3.

    I'm going to try the beta 3.2.3 with SBC and try again.

    Sounds like a good plan to me. As with any beta, exercise caution - I suggest you baby-sit the print, at least for a while.



  • @dhusolo said in Duet 3 SBC DCS has stopped:

    So last night I swapped to standalone mode completely disconnecting the pi. I was able to print the same file I had issues with. So sounds like the issue is with the communication between the Pi and the Duet 3.

    I'm going to try the beta 3.2.3 with SBC and try again.

    I did try to tell you a few days ago.....

    Nice to be proven correct again....

    It must be noted that I had the same problem on 3.1.1 firmware too



  • @CaLviNx Yea you're correct but why did you feel the need to say it like that? I was troubleshooting. I started focusing on the firmware side. When all options were exhausted i eliminated the Pi



  • After upgrading to the latest beta 3.2.3 I get the error Could not connect to duet (Board is not available (no header))

    The error exists even after swapping back to the original 3.1.1 pi.

    3a65705c-3346-4f96-b84d-536c57fff93e-image.png


  • Moderator

    What version is on the Duet itself?

    See this thread for downgrading instructions.

    https://forum.duet3d.com/topic/19257/downgrade-from-3-2beta2-to-3-1-1/



  • @Phaedrux thanks. I ran

    sudo wget -O /opt/dsf/sd/sys/Duet3Firmware_MB6HC.bin https://github.com/Duet3D/RepRapFirmware/releases/download/3.1.1/Duet3Firmware_MB6HC.bin
    
    sudo apt -y --allow-downgrades install duetsoftwareframework=3.1.1 duetcontrolserver=3.1.1 duetruntime=3.1.1 duetsd=1.0.6 duettools=3.1.1 duetwebcontrol=3.1.1 duetwebserver=3.1.0 reprapfirmware=3.1.1-1
    
    Unpacking duetruntime (3.1.1) over (3.2.0-beta3) ...
    Setting up duetruntime (3.1.1) ...
    Setting up duetwebcontrol (3.1.1) ...
    Setting up duetcontrolserver (3.1.1) ...
    Installing new version of config file /opt/dsf/conf/config.json ...
    Setting up duettools (3.1.1) ...
    Setting up duetwebserver (3.1.0) ...
    Setting up duetsd (1.0.6) ...
    Setting up reprapfirmware (3.1.1-1) ...
    [fatal] Could not connect to Duet (Board is not available (no header))
    Setting up duetsoftwareframework (3.1.1) ...
    
    


  • The cable is good. I used a continuity tester to check each pin from the duet board to the pi. Every pin had a connection to it's corresponding one. I'm starting to suspect there's an issue with the board



  • @dc42 any ideas? everything i've tried has failed. The board will work in standalone but the reason I bought it is for the benefits of with the SBC



  • @dhusolo said in Duet 3 SBC DCS has stopped:

    @CaLviNx Yea you're correct but why did you feel the need to say it like that? I was troubleshooting. I started focusing on the firmware side. When all options were exhausted i eliminated the Pi

    I was trying to help you and save you time, instead of listening to reason you blew it off and acted like I was speaking out of my ass


  • Moderator

    @CaLviNx said in Duet 3 SBC DCS has stopped:

    @dhusolo said in Duet 3 SBC DCS has stopped:

    @CaLviNx Yea you're correct but why did you feel the need to say it like that? I was troubleshooting. I started focusing on the firmware side. When all options were exhausted i eliminated the Pi

    I was trying to help you and save you time, instead of listening to reason you blew it off and acted like I was speaking out of my ass

    How bout you save us all some time and just exit the thread please.


  • Moderator

    @dhusolo said in Duet 3 SBC DCS has stopped:

    After upgrading to the latest beta 3.2.3 I get the error Could not connect to duet (Board is not available (no header))

    The error exists even after swapping back to the original 3.1.1 pi.

    3a65705c-3346-4f96-b84d-536c57fff93e-image.png

    Can you try beta 3 again? It seems like something might have gone wrong on the update.



  • @Phaedrux said in Duet 3 SBC DCS has stopped

    How bout you save us all some time and just exit the thread please.

    What why? Don't you don't like the fact that I pointed out the problem days ago, a problem that has been proven to be true, just because you don't like the fact its still a fact none the less.


Log in to reply