Duet 3 + SBC Lost connection. No Header



  • I was mid job when the Duet 3 reported:
    "Lost connection to DUET board, board is not available (no header)"
    Then its connection established again and was immediately lost again and round we went in circles.

    As I have no idea what the message means or what header, I replaced the IDC header lead from the board to the Pi with one from my other board. No fix.

    The PanelDue reports "connecting" and doesn't get any further. If I power from USB, same issue and the Pi has a rock solid wifi connection.

    Any ideas?



  • This is what I have done so far:

    1. reflashed the firmware
    2. tried a different raspberry pi
    3. tried it in stand alone mode
    4. connected to the pi with putty and did the sudo apt update and sudo apt upgrade
    5. still the same issue with the board: "No data" "No header response"

  • Moderator

    Are you able to stay connected long enough to provide a M122 report?

    What firmware version specifically? 3.1.1 I assume?


  • Moderator

    Can you try in standalone mode to eliminate the pi and DSF from the equation?



  • @Phaedrux yes 3.1.1. I will try M122 tomorrow, not with the machine at the moment. thanks



  • @Phaedrux I thought I had tried it in stand alone but apparently it is not as simple as putting the SD card in the board instead of the pi. As it is a new board, purchased last week from OOznest I thought it was dual format and would work like that. It seems like I will need to swat up how to make a SD standalone card. I will get back to you.


  • Moderator

    If you can still access the configuration files from the Pi you can use those same config files on a separate SD card that will then go in the Duet. You'll also need the DWC files present in the www folder.

    Here's a breakdown of the SD card contents required.

    https://duet3d.dozuki.com/Wiki/SD_Card



  • Would most likely want to add M552 S1 to enable network for stand alone (if not already in there ofc, but it's not needed for the Pi)



  • @Phaedrux I managed to get a M122 report eventually, it was very difficult as you see the board is resetting every fraction of a second. I have checked continuity on the reset button and it is open so should be okay. :

    7/24/2020, 10:35:00 AM Connection to Duet established
    7/24/2020, 10:35:00 AM Warning: Lost connection to Duet (Board is not available (no header))
    7/24/2020, 10:35:00 AM M122
    === Diagnostics ===
    RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode)
    Board ID: 08DJM-956L2-G43S4-6J9F4-3SJ6R-TA6AG
    Used output buffers: 1 of 40 (10 max)
    === RTOS ===
    Static ram: 154604
    Dynamic ram: 161152 of which 52 recycled
    Exception stack ram used: 224
    Never used ram: 77184
    Tasks: NETWORK(ready,1980) HEAT(blocked,1464) CanReceiv(suspended,3820) CanSender(suspended,1488) CanClock(blocked,1468) TMC(blocked,204) MAIN(running,5216) IDLE(ready,76)
    Owned mutexes:
    === Platform ===
    Last reset 00:00:00 ago, cause: software
    Last software reset at 2020-07-24 10:35, reason: Terminate called, spinning module GCodes, available RAM 76840 bytes (slot 0)
    Software reset code 0x4183 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0x20417540 Task MAIN
    Stack: 0000002b 0046b487 00000000 2044d278 204178a0 0046b7ef 00000000 0046b175 20417590 004507ef 204175e0
    Error status: 0
    MCU temperature: min 25.9, current 26.0, max 26.0
    Supply voltage: min 23.2, current 23.2, max 23.3, under voltage events: 0, over voltage events: 0, power good: yes
    12V rail voltage: min 12.0, current 12.0, max 12.1, under voltage events: 0
    Driver 0: standstill, reads 1861, writes 12 timeouts 0, SG min/max 0/0
    Driver 1: standstill, reads 1862, writes 12 timeouts 0, SG min/max 0/0
    Driver 2: standstill, reads 1862, writes 12 timeouts 0, SG min/max 0/0
    Driver 3: standstill, reads 1863, writes 12 timeouts 0, SG min/max 0/0
    Driver 4: standstill, reads 1864, writes 11 timeouts 0, SG min/max 0/0
    Driver 5: standstill, reads 1865, writes 11 timeouts 0, SG min/max 0/0
    Date/time: 2020-07-24 10:35:00
    Slowest loop: 3.20ms; 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: 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 = -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 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 ready with "M201 X500.000000 Y500.000000 Z35.000000 E250.000000" in state(s) 0 0, running macro
    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.80ms; 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 0, longest wait 0ms for type 0
      === Linux interface ===
      State: 0, failed transfers: 0
      Last transfer: 19ms ago
      RX/TX seq numbers: 1464/12
      SPI underruns 0, overruns 0
      Number of disconnects: 0
      Buffer RX/TX: 584/804-0
      === Duet Control Server ===
      Duet Control Server v3.1.1
      Trigger:
      Buffered code: M208 X0 Y0 Z0 S1 ; set axis minima
      Buffered code: M208 X600 Y300 Z80 S0 ; set axis maxima
      Buffered code: ; Endstops
      Buffered code: M574 X1 S1 P"io3.in" ; configure active-high endstop for low end on X via pin io3.in
      Buffered code: M574 Y1 S1 P"io4.in" ; configure active-high endstop for low end on Y via pin io4.in
      Buffered code: M574 Z0 S1 ! P " i o 2 . i n "
      Buffered code: ; Z-Probe
      Buffered code: M558 P0 H0 F120 T4800 ; disable Z probe but set dive height, probe speed and travel speed
      Buffered code: M557 X15:215 Y15:195 S20 ; define mesh grid
      Buffered code: ; Heaters
      Buffered code: M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0
      Buffered code: M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0
      Buffered code: M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
      Buffered code: M140 H0 ; map heated bed to heater 0
      Buffered code: M143 H0 S120 ; set temperature limit for heater 0 to 120C
      Buffered code: M308 S1 P"temp1" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin temp1
      ==> 920 bytes
      Executing macro config.g, started by system

    Next stack level
    Code buffer space: 2428
    Configured SPI speed: 8000000 Hz
    Full transfers per second: 0.02
    7/24/2020, 10:34:59 AM Warning: Controller has been reset
    7/24/2020, 10:34:59 AM Connection to Duet established
    7/24/2020, 10:34:59 AM Warning: Lost connection to Duet (Board is not available (no header))
    7/24/2020, 10:34:59 AM Warning: Controller has been reset
    7/24/2020, 10:34:59 AM Connection to Duet established
    7/24/2020, 10:34:59 AM Warning: Lost connection to Duet (Board is not available (no header))
    7/24/2020, 10:34:58 AM Warning: Controller has been reset



  • Looks like it was the SD card. I made a new one (for the PI, not standalone) and now it all works.
    Not sure how to mark the post as solved, thanks for all your help!
    Chris




  • Moderator

    Glad you figured it out. I wouldn't have immediately thought of the SD card.


  • administrators

    Do you still have the SD card that didn't work? My suspicion is that you had a bad command in config.g and the firmware was failing to catch the resulting exception. I'd like to fix that.



  • You are absolutely right, it was an error in config.g, I was setting up an end stop and the software advised me I had to reverse the pin, or something like that. I looked up how to do it and needed to put a "!" in front of the pin number. From memory it was something like
    M587 Z0 S1 P"Io_2"
    so I stuck the ! before the P like:
    M587 Z0 S1 !P"I0_2"

    this totally trashed the setup, how do I know? I did it again!

    It should have been
    M587 Z0 S1 P"!Io2"

    Forgive me if the syntax is wrong but I am not a programmer, anyway it worked this way round!



  • @chrishornby ...and sorry, not got the card, I re-flashed it, but didn't need to do so as deleting one character in the config file would have fixed it!



  • @dc42 I am wondering whether you received my first board and whether you need a AOZ1284 as I have one in my possession


  • Moderator

    @chrishornby said in Duet 3 + SBC Lost connection. No Header:

    @dc42 I am wondering whether you received my first board and whether you need a AOZ1284 as I have one in my possession

    I think DC42 is on vacation until next week.



  • thanks very much


Log in to reply