3.2beta3 times out reading config.g



  • I run a Duet3 0.6 with preproduction 1LC on a tool distribution board in SBC mode with a Pi3 powered from the Duet3 board

    During the upgrade the Pi3 crashed once, but since it only crashed during download of packages, I was able to do the upgrade after a power cycle.

    Now it seems like during bootup config.g is not being read fast enough. DuetControlServer logs note:

    -- Support: https://www.debian.org/support
    --
    -- A stop job for unit duetcontrolserver.service has finished.
    --
    -- The job identifier is 528 and the job result is done.
    Nov 07 18:07:12 vcore-pro systemd[1]: Started Duet Control Server.
    -- Subject: A start job for unit duetcontrolserver.service has finished successfully
    -- Defined-By: systemd
    -- Support: https://www.debian.org/support
    --
    -- A start job for unit duetcontrolserver.service has finished successfully.
    --
    -- The job identifier is 528.
    Nov 07 18:07:12 vcore-pro DuetControlServer[646]: Duet Control Server v3.2.0-beta3
    Nov 07 18:07:12 vcore-pro DuetControlServer[646]: Written by Christian Hammacher for Duet3D
    Nov 07 18:07:12 vcore-pro DuetControlServer[646]: Licensed under the terms of the GNU Public License Version 3
    Nov 07 18:07:13 vcore-pro DuetControlServer[646]: [info] Settings loaded
    Nov 07 18:07:13 vcore-pro DuetControlServer[646]: [info] Environment initialized
    Nov 07 18:07:13 vcore-pro DuetControlServer[646]: [info] Connection to Duet established
    Nov 07 18:07:14 vcore-pro DuetControlServer[646]: [info] IPC socket created at /var/run/dsf/dcs.sock
    Nov 07 18:07:14 vcore-pro DuetControlServer[646]: [info] Starting macro file config.g on channel Trigger
    Nov 07 18:07:15 vcore-pro DuetControlServer[646]: [error] Failed to get macro response within 8000ms from SBC (channel Trigger)
    Nov 07 18:07:15 vcore-pro DuetControlServer[646]: [warn] Trigger: System macro config.g.bak is requested but the stack is not empty. Discarding request.
    

    After that, no tools are configured. Running M98 P"config.g" manually makes the fans on the toolboard stop running (as expected), and DCS logs the following:

    Nov 07 18:07:42 vcore-pro DuetControlServer[646]: [info] Starting macro file config.g on channel HTTP
    Nov 07 18:07:42 vcore-pro DuetControlServer[646]: [info] Starting macro file config-override.g on channel HTTP
    Nov 07 18:07:43 vcore-pro DuetControlServer[646]: [info] Finished macro file config-override.g
    Nov 07 18:07:43 vcore-pro DuetControlServer[646]: [info] Finished macro file config.g
    

    M122 (after manually loading config.g):

    	M122
    === Diagnostics ===
    RepRapFirmware for Duet 3 MB6HC version 3.2-beta3 running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode)
    Board ID: 08DGM-9T66A-G63SJ-6J1D6-3SD6R-9U0BA
    Used output buffers: 3 of 40 (15 max)
    === RTOS ===
    Static ram: 122124
    Dynamic ram: 138980 of which 20 recycled
    Never used RAM 131068, free system stack 176 words
    Tasks: Linux(ready,101) HEAT(blocked,296) CanReceiv(blocked,901) CanSender(blocked,371) CanClock(blocked,352) TMC(blocked,51) MAIN(running,1149) IDLE(ready,19)
    Owned mutexes: HTTP(MAIN)
    === Platform ===
    Last reset 00:05:15 ago, cause: software
    Last software reset at 2020-11-07 18:07, reason: User, GCodes spinning, available RAM 132476, slot 0
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0xffffffff Task Linu
    Error status: 0x00
    MCU temperature: min 31.6, current 32.6, max 32.7
    Supply voltage: min 24.0, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
    12V rail voltage: min 12.2, current 12.3, max 12.3, under voltage events: 0
    Driver 0: position 0, standstill, reads 49178, writes 14 timeouts 0, SG min/max 0/0
    Driver 1: position 0, standstill, reads 49179, writes 14 timeouts 0, SG min/max 0/0
    Driver 2: position 0, standstill, reads 49183, writes 11 timeouts 0, SG min/max 0/0
    Driver 3: position 0, standstill, reads 49181, writes 14 timeouts 0, SG min/max 0/0
    Driver 4: position 0, standstill, reads 49181, writes 14 timeouts 0, SG min/max 0/0
    Driver 5: position 0, standstill, reads 49182, writes 14 timeouts 0, SG min/max 0/0
    Date/time: 1970-01-01 00:00:00
    Slowest loop: 206.83ms; fastest: 0.00ms
    === 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, 0], CDDA state -1
    === AuxDDARing ===
    Scheduled moves 0, completed moves 0, StepErrors 0, LaErrors 0, Underruns [0, 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 doing "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 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.
    === CAN ===
    Messages sent 1134, send timeouts 1134, longest wait 2ms for type 6011, free CAN buffers 47
    === SBC interface ===
    State: 0, failed transfers: 0
    Last transfer: 19ms ago
    RX/TX seq numbers: 9831/9833
    SPI underruns 0, overruns 0
    Number of disconnects: 0, IAP RAM available 0x20aa0
    Buffer RX/TX: 0/0-0
    === Duet Control Server ===
    Duet Control Server v3.2.0-beta3
    Trigger:
    Buffered code: G90 ; send absolute coordinates...
    Buffered code: M83 ; ...but relative extruder moves
    ==> 48 bytes
    Executing macro config.g, started by system
    Number of flush requests: 1
    > Next stack level
    Code buffer space: 4096
    Configured SPI speed: 8000000 Hz
    Full transfers per second: 31.91
    


  • Here is an M122 after a reboot when the machine is not configured fully:

    	M122
    === Diagnostics ===
    RepRapFirmware for Duet 3 MB6HC version 3.2-beta3 running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode)
    Board ID: 08DGM-9T66A-G63SJ-6J1D6-3SD6R-9U0BA
    Used output buffers: 1 of 40 (10 max)
    === RTOS ===
    Static ram: 122124
    Dynamic ram: 137340 of which 0 recycled
    Never used RAM 132728, free system stack 200 words
    Tasks: Linux(ready,97) HEAT(blocked,362) CanReceiv(blocked,869) CanSender(blocked,371) CanClock(blocked,352) TMC(blocked,54) MAIN(running,1311) IDLE(ready,19)
    Owned mutexes: HTTP(MAIN)
    === Platform ===
    Last reset 00:01:03 ago, cause: power up
    Last software reset at 2020-11-07 18:07, reason: User, GCodes spinning, available RAM 132476, slot 0
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0xffffffff Task Linu
    Error status: 0x00
    MCU temperature: min 28.9, current 32.2, max 32.3
    Supply voltage: min 24.0, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
    12V rail voltage: min 12.2, current 12.3, max 12.3, under voltage events: 0
    Driver 0: position 0, standstill, reads 54395, writes 11 timeouts 0, SG min/max 0/0
    Driver 1: position 0, standstill, reads 54396, writes 11 timeouts 0, SG min/max 0/0
    Driver 2: position 0, standstill, reads 54397, writes 11 timeouts 0, SG min/max 0/0
    Driver 3: position 0, standstill, reads 54398, writes 11 timeouts 0, SG min/max 0/0
    Driver 4: position 0, standstill, reads 54399, writes 11 timeouts 0, SG min/max 0/0
    Driver 5: position 0, standstill, reads 54399, writes 11 timeouts 0, SG min/max 0/0
    Date/time: 2020-11-07 18:15:56
    Slowest loop: 454.28ms; fastest: 0.23ms
    === 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, 0], CDDA state -1
    === AuxDDARing ===
    Scheduled moves 0, completed moves 0, StepErrors 0, LaErrors 0, Underruns [0, 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 doing "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.
    === CAN ===
    Messages sent 1, send timeouts 1, longest wait 0ms for type 0, free CAN buffers 47
    === SBC interface ===
    State: 0, failed transfers: 0
    Last transfer: 19ms ago
    RX/TX seq numbers: 1357/1358
    SPI underruns 0, overruns 0
    Number of disconnects: 0, IAP RAM available 0x20aa0
    Buffer RX/TX: 0/0-0
    === Duet Control Server ===
    Duet Control Server v3.2.0-beta3
    Code buffer space: 4096
    Configured SPI speed: 8000000 Hz
    Full transfers per second: 8.33
    

  • administrators

    Did you update the tool board firmware as well?



  • yes, I did update the tool board firmware as well

    11/7/2020, 10:32:49 PM	M115
    FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.2-beta3 ELECTRONICS: Duet 3 MB6HC v0.6 or 1.0 FIRMWARE_DATE: 2020-11-07
    11/7/2020, 10:32:46 PM	M115 B10
    Duet TOOL1LC firmware version 3.2beta3 (2020-11-07)
    

Log in to reply