Lost connection to Duet3 SBC



  • I upgraded from Duet 2 Wifi and DueX2 to a Duet 3 with Raspberry Pi.
    Since I upgraded I will randomly get this error:

    Randomly I get this error and my machine will stop responding to the web interface:
    Warning: Lost connection to Duet (Timeout while waiting for transfer ready pin)

    Board: Duet 3 MB6HC (MB6HC)
    DSF Version: 3.1.1
    Firmware: RepRapFirmware for Duet 3 MB6HC 3.1.1 (2020-05-19b2)

    Before this happened I was loading the hotend using the interface to extrude the filament. Other times this has happened was when I was running bed leveling.

    Seems like when it does happen it's when I'm selecting a gcode file to print. It doesn't automatically reconnect unless I manually restart the board by hitting stop on the Panel Due or reset on the motherboard.

    8/13/2020, 2:34:16 PM	Connection established
    8/13/2020, 2:33:42 PM	Connection interrupted, attempting to reconnect...
    8/13/2020, 2:33:42 PM	Connection to Duet established
    8/13/2020, 2:33:41 PM	Warning: Firmware reset imminent
    8/13/2020, 2:33:41 PM	Emergency stop, attemping to reconnect...
    8/13/2020, 2:33:41 PM	Connection to Duet established
    8/13/2020, 2:33:29 PM	Warning: Firmware halted
    8/13/2020, 2:33:24 PM	Warning: Lost connection to Duet (Timeout while waiting for transfer ready pin)
    8/13/2020, 2:33:21 PM	M32 "0:/gcodes/2020 Dial Indicator X Carriage Mount.gcode"
    File 0:/gcodes/2020 Dial Indicator X Carriage Mount.gcode selected for printing
    8/13/2020, 2:33:07 PM	TELNET is disabled
    8/13/2020, 2:33:07 PM	FTP is disabled
    8/13/2020, 2:33:07 PM	HTTP is enabled on port 80
    8/13/2020, 2:33:07 PM	Warning: Controller has been reset
    8/13/2020, 2:33:07 PM	Connection to Duet established
    8/13/2020, 2:33:07 PM	Warning: Lost connection to Duet (Board is not available (no header))
    8/13/2020, 2:33:06 PM	M32 "0:/gcodes/2020 Dial Indicator X Carriage Mount.gcode"
    File 0:/gcodes/2020 Dial Indicator X Carriage Mount.gcode selected for 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-6J9D0-3S46T-9U2LF
    Used output buffers: 1 of 40 (11 max)
    === RTOS ===
    Static ram: 154604
    Dynamic ram: 163392 of which 64 recycled
    Exception stack ram used: 536
    Never used ram: 74620
    Tasks: ETHERNET(blocked,824) NETWORK(ready,1968) HEAT(blocked,1188) CanReceiv(suspended,3820) CanSender(suspended,1420) CanClock(blocked,1436) TMC(blocked,60) MAIN(running,2868) IDLE(ready,76)
    Owned mutexes:
    === Platform ===
    Last reset 00:10:35 ago, cause: power up
    Last software reset time unknown, reason: User, spinning module LinuxInterface, available RAM 77216 bytes (slot 2)
    Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task MAIN
    Error status: 0
    MCU temperature: min 33.5, current 37.5, max 37.7
    Supply voltage: min 24.2, current 24.6, max 24.7, 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: ok, reads 8566, writes 17 timeouts 0, SG min/max 0/191
    Driver 1: ok, reads 8563, writes 21 timeouts 0, SG min/max 0/1000
    Driver 2: ok, reads 8563, writes 21 timeouts 0, SG min/max 0/188
    Driver 3: ok, reads 8564, writes 21 timeouts 0, SG min/max 0/1023
    Driver 4: ok, reads 8564, writes 21 timeouts 0, SG min/max 0/1023
    Driver 5: ok, reads 8565, writes 21 timeouts 0, SG min/max 0/922
    Date/time: 2020-08-13 14:44:20
    Slowest loop: 9.24ms; 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: 362, MinFreeDm: 356, MaxWait: 288392ms
    Bed compensation in use: mesh, comp offset 0.000
    === MainDDARing ===
    Scheduled moves: 393, completed moves: 379, 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.0
    Heater 1 is on, I-accum = 0.3
    === GCodes ===
    Segments left: 1
    Movement lock held by null
    HTTP* is ready with "M122" in state(s) 0
    Telnet is idle in state(s) 0
    File* is doing "G1 E-0.100000 F5100" 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 2475, longest wait 0ms for type 0
    === Linux interface ===
    State: 0, failed transfers: 0
    Last transfer: 21ms ago
    RX/TX seq numbers: 19446/19447
    SPI underruns 0, overruns 0
    Number of disconnects: 0
    Buffer RX/TX: 3704/1080-4080
    === Duet Control Server ===
    Duet Control Server v3.1.1
    File:
    Buffered code: G1 E-0.1000 F5100
    Buffered code: G92 E0.0000
    Buffered code: G1 X142.453 Y151.100 E0.5814 F866
    Buffered code: G1 X148.447 Y151.100 E0.8227
    Buffered code: G1 X148.532 Y149.363 E0.8927
    Buffered code: G1 X148.626 Y148.732 E0.9183
    Buffered code: G1 X148.781 Y148.114 E0.9440
    Buffered code: G1 X148.996 Y147.513 E0.9697
    Buffered code: G1 X149.268 Y146.936 E0.9953
    Buffered code: G1 X149.596 Y146.389 E1.0210
    Buffered code: G1 X149.976 Y145.877 E1.0467
    Buffered code: G1 X150.404 Y145.404 E1.0723
    Buffered code: G1 X150.877 Y144.976 E1.0980
    Buffered code: G1 X151.389 Y144.596 E1.1237
    Buffered code: G1 X151.936 Y144.268 E1.1493
    Buffered code: G1 X152.513 Y143.996 E1.1750
    Buffered code: G1 X153.114 Y143.781 E1.2007
    Buffered code: G1 X153.732 Y143.626 E1.2263
    Buffered code: G1 X154.363 Y143.532 E1.2520
    Buffered code: G1 X155.000 Y143.501 E1.2777
    Buffered code: G1 X155.637 Y143.532 E1.3033
    Buffered code: G1 X156.268 Y143.626 E1.3290
    Buffered code: G1 X156.886 Y143.781 E1.3547
    Buffered code: G1 X157.487 Y143.996 E1.3803
    Buffered code: G1 X158.064 Y144.268 E1.4060
    Buffered code: G1 X158.611 Y144.596 E1.4317
    Buffered code: G1 X159.123 Y144.976 E1.4573
    Buffered code: G1 X159.596 Y145.404 E1.4830
    Buffered code: G1 X160.024 Y145.877 E1.5087
    Buffered code: G1 X160.404 Y146.389 E1.5343
    Buffered code: G1 X160.732 Y146.936 E1.5600
    Buffered code: G1 X161.004 Y147.513 E1.5857
    ==> 1508 bytes
    Code buffer space: 2576
    Configured SPI speed: 8000000 Hz
    Full transfers per second: 18.47
    File /opt/dsf/sd/gcodes/2020 Dial Indicator X Carriage Mount.gcode is selected, processing
    

  • Moderator

    Can you try putting it in debug mode to gather some additional info?

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


  • Moderator

    Will have to see what @chrishamm has to say about the error.

    Randomly I get this error and my machine will stop responding to the web interface:
    Warning: Lost connection to Duet (Timeout while waiting for transfer ready pin)



  • @Phaedrux Thanks. I will try that and see if I can get any more information. it's not consistent. I can go days without it happening.



  • @Phaedrux I’m still getting that error too. It usually happens after a print or two when I try to submit a new print. Any update on a fix for this?



  • I changed my hostname on the Pi not realizing i had invalid characters. I changed it to The_Demon where capital and "_" are not allowed. when i changed it to the-demon it seems my problems went away. at least it hasn't happened since


  • Moderator

    @baird1fa Have you started a thread for your issue and provide some debug info as linked above?



  • @dhusolo said in Lost connection to Duet3 SBC:

    where capital and "_" are not allowed.

    capitals isn't (shouldn't be?) a problem, it just isn't case sensitve. _ isn't a valid hostname character indeed, more details in link

    https://en.wikipedia.org/wiki/Hostname#Syntax



  • @bearer I know with Linux if you don't have the correct case it sometimes it'll say the command is invalid. So to eliminate any issues i made it all lowercase LOL



  • @dhusolo said in Lost connection to Duet3 SBC:

    @bearer I know with Linux if you don't have the correct case it sometimes it'll say the command is invalid. So to eliminate any issues i made it all lowercase LOL

    for commands and filenames yes, dns and hostnames doesn't matter. in general you'll have less issues avoiding mixed case and special characters (incl spaces) on linux indeed

    bearer@rama:~$ dig +noall +answer gatebear.lan
    gatebear.lan.           0       IN      A       10.10.0.1
    bearer@rama:~$ dig +noall +answer GATEBEAR.LAN
    GATEBEAR.LAN.           0       IN      A       10.10.0.1
    bearer@rama:~$ DIG +noall +answer gatebear.lan
    DIG: command not found
    

Log in to reply