Duet3 Pi4b 3.2b1 error



  • Hi,

    After updating to latest version which did not update web control from 3.1.1 initially
    I get the following every minute or so from power on no g-code loaded hope this helps.
    Done a fresh install this morning as showing 3.2b1 on Pi screen and 3.1.1 on desktop ?
    (after clearing history)This came about after update/upgrade?

    9/18/2020, 1:09:42 PM Connection interrupted, attempting to reconnect...
    Network error
    9/18/2020, 1:07:33 PM Connection to Duet established
    9/18/2020, 1:07:33 PM Warning: Lost connection to Duet (Board is not available (no data response))
    9/18/2020, 1:06:55 PM Connection to Duet established
    9/18/2020, 1:06:55 PM Warning: Lost connection to Duet (Board is not available (no data response))
    9/18/2020, 1:05:19 PM Upload of config.g successful after 0s
    9/18/2020, 1:04:56 PM M122
    === Diagnostics ===
    RepRapFirmware for Duet 3 MB6HC version 3.2-beta1 running on Duet 3 MB6HC v1.01 or later (SBC mode)
    Board ID: 08DJM-956L2-G43S8-6J1DJ-3SJ6P-980QG
    Used output buffers: 1 of 40 (10 max)
    === RTOS ===
    Static ram: 154820
    Dynamic ram: 132612 of which 44 recycled
    Exception stack ram used: 416
    Never used ram: 105324
    Tasks: HEAT(blocked,296) CanReceiv(blocked,948) CanSender(blocked,349) CanClock(blocked,352) TMC(blocked,52) MAIN(running,1230) IDLE(ready,19)
    Owned mutexes:
    === Platform ===
    Last reset 00:01:20 ago, cause: software
    Last software reset at 2020-09-18 13:03, reason: User, LinuxInterface spinning, available RAM 105100, slot 0
    Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task MAIN
    Error status: 0x020
    MCU temperature: min 29.0, current 29.1, max 31.0
    Supply voltage: min 24.1, current 24.2, max 24.3, 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: position 125308, standstill, reads 1962, writes 19 timeouts 0, SG min/max 0/143
    Driver 1: position 125308, standstill, reads 1962, writes 19 timeouts 0, SG min/max 0/143
    Driver 2: position 125308, standstill, reads 1963, writes 19 timeouts 0, SG min/max 0/145
    Driver 3: position 0, standstill, reads 1968, writes 14 timeouts 0, SG min/max 0/0
    Driver 4: position 0, standstill, reads 1972, writes 11 timeouts 0, SG min/max 0/0
    Driver 5: position 0, standstill, reads 1972, writes 11 timeouts 0, SG min/max 0/0
    Date/time: 2020-09-18 13:04:58
    Slowest loop: 3.67ms; 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: 372, MaxWait: 17250ms
    Bed compensation in use: none, comp offset 0.000
    === MainDDARing ===
    Scheduled moves: 4, completed moves: 4, 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 0 is on, I-accum = 0.5
    Heater 1 is on, I-accum = 0.3
    === 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.00ms; fastest: 5726623.00ms
    Responder states:
    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 291, send timeouts 291, longest wait 0ms for type 0, free CAN buffers 48
      === SBC interface ===
      State: 0, failed transfers: 10
      Last transfer: 18ms ago
      RX/TX seq numbers: 2383/2384
      SPI underruns 4, overruns 3
      Number of disconnects: 0
      Buffer RX/TX: 0/0-0
      === Duet Control Server ===
      Duet Control Server v3.2.0-beta1+1
      Code buffer space: 4096
      Configured SPI speed: 8000000 Hz
      Full transfers per second: 32.24
      pi@duet3:~ $ journalctl -u duetcontrolserver.service -f
      -- Logs begin at Fri 2020-09-18 12:34:25 BST. --
      Sep 18 13:06:53 duet3 DuetControlServer[2685]: [warn] Restarting transfer becaus e a bad data response was received (0xffffff7d)
      Sep 18 13:06:55 duet3 DuetControlServer[2685]: [warn] Restarting transfer becaus e a bad data response was received (0x00000022)
      Sep 18 13:06:55 duet3 DuetControlServer[2685]: [warn] Restarting transfer becaus e a bad data response was received (0xffffff7d)
      Sep 18 13:06:55 duet3 DuetControlServer[2685]: [warn] Restarting transfer becaus e a bad header response was received (0x0000002c)
      Sep 18 13:06:57 duet3 DuetControlServer[2685]: [warn] Lost connection to Duet (B oard is not available (no data response))
      Sep 18 13:06:57 duet3 DuetControlServer[2685]: [warn] Bad header checksum (expec ted 0x0000, got 0xc221)
      Sep 18 13:06:57 duet3 DuetControlServer[2685]: [warn] Restarting transfer becaus e the Duet received a bad response (header response)
      Sep 18 13:06:57 duet3 DuetControlServer[2685]: [info] Connection to Duet establi shed
      Sep 18 13:07:03 duet3 DuetControlServer[2685]: [warn] Restarting transfer becaus e a bad data response was received (0xffffff7d)
      Sep 18 13:07:03 duet3 DuetControlServer[2685]: [warn] Restarting transfer becaus e a bad data response was received (0x00000003)
      Sep 18 13:07:09 duet3 DuetControlServer[2685]: [warn] Restarting transfer becaus e a bad data response was received (0xffffff67)
      Sep 18 13:07:15 duet3 DuetControlServer[2685]: [warn] Bad data checksum (expecte d 0x0406, got 0xb167)
      Sep 18 13:07:15 duet3 DuetControlServer[2685]: [warn] Restarting transfer becaus e a bad data response was received (0xffffff67)
      Sep 18 13:07:15 duet3 DuetControlServer[2685]: [warn] Bad data checksum (expecte d 0x2024, got 0x0a96)
      Sep 18 13:07:16 duet3 DuetControlServer[2685]: [warn] Bad data checksum (expecte d 0xdd2d, got 0xf17d)
      Sep 18 13:07:22 duet3 DuetControlServer[2685]: [warn] Bad data checksum (expecte d 0x727d, got 0x033c)
      Sep 18 13:07:22 duet3 DuetControlServer[2685]: [warn] Bad data checksum (expecte d 0x727d, got 0xc323)
      Sep 18 13:07:27 duet3 DuetControlServer[2685]: [warn] Bad data checksum (expected 0x2566, got 0xd18f)
      Sep 18 13:07:35 duet3 DuetControlServer[2685]: [warn] Bad data checksum (expected 0x41a4, got 0xd0f7)
      Sep 18 13:07:36 duet3 DuetControlServer[2685]: [warn] Restarting transfer because a bad data response was received (0xffffff7d)
      Sep 18 13:07:36 duet3 DuetControlServer[2685]: [warn] Lost connection to Duet (Board is not available (no data response))
      Sep 18 13:07:36 duet3 DuetControlServer[2685]: [warn] Bad header checksum (expected 0x0000, got 0x41c0)
      Sep 18 13:07:36 duet3 DuetControlServer[2685]: [warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000006)
      Sep 18 13:07:36 duet3 DuetControlServer[2685]: [warn] Bad header checksum (expected 0x0000, got 0x41c0)
      Sep 18 13:07:36 duet3 DuetControlServer[2685]: [warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000006)
      Sep 18 13:07:36 duet3 DuetControlServer[2685]: [warn] Bad header checksum (expected 0x0000, got 0x41c0)
      Sep 18 13:07:36 duet3 DuetControlServer[2685]: [warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000006)
      Sep 18 13:07:36 duet3 DuetControlServer[2685]: [warn] Restarting transfer because the number of maximum retries has been exceeded
      Sep 18 13:07:36 duet3 DuetControlServer[2685]: [info] Connection to Duet established
      Sep 18 13:07:36 duet3 DuetControlServer[2685]: [warn] Restarting transfer because a bad data response was received (0xffffff7d)
      Sep 18 13:07:37 duet3 DuetControlServer[2685]: [warn] Bad data checksum (expected 0x4877, got 0x1859)
      Sep 18 13:07:37 duet3 DuetControlServer[2685]: [warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000006)
      Sep 18 13:07:37 duet3 DuetControlServer[2685]: [warn] Restarting transfer because a bad data response was received (0xffffff7d)
      Sep 18 13:07:37 duet3 DuetControlServer[2685]: [warn] Restarting transfer because a bad data response was received (0x00f40100)
      Sep 18 13:07:37 duet3 DuetControlServer[2685]: [warn] Restarting transfer because the Duet received a bad response (header)
      Sep 18 13:07:42 duet3 DuetControlServer[2685]: [warn] Restarting transfer because a bad data response was received (0xffffff7d)
      Sep 18 13:07:43 duet3 DuetControlServer[2685]: [warn] Restarting transfer because a bad data response was received (0xffffff7d)
      Sep 18 13:07:50 duet3 DuetControlServer[2685]: [warn] Restarting transfer because a bad data response was received (0xffffff7d)
      Sep 18 13:08:09 duet3 DuetControlServer[2685]: [warn] Restarting transfer because a bad data response was received (0xffffff67)
      Sep 18 13:08:09 duet3 DuetControlServer[2685]: [warn] Bad data checksum (expected 0xddc1, got 0x600e)
      Sep 18 13:08:09 duet3 DuetControlServer[2685]: [warn] Bad data checksum (expected 0x5d5a, got 0x4846)
      Sep 18 13:08:14 duet3 DuetControlServer[2685]: [warn] Restarting transfer because a bad data response was received (0xffffff7d)
      Sep 18 13:08:20 duet3 DuetControlServer[2685]: [warn] Restarting transfer because a bad data response was received (0xffffff7d)
      Sep 18 13:08:22 duet3 DuetControlServer[2685]: [warn] Bad data checksum (expected 0x0a38, got 0xd390)
      Sep 18 13:08:26 duet3 DuetControlServer[2685]: [warn] Bad data checksum (expected 0xe543, got 0x0777)
      Sep 18 13:08:26 duet3 DuetControlServer[2685]: [warn] Bad data checksum (expected 0xe543, got 0x5e40)
      Sep 18 13:08:26 duet3 DuetControlServer[2685]: [warn] Restarting transfer because a bad data response was received (

    Cheers
    C



  • @Carlo

    I've been playing around a bit ......bored... and the above happens if I change from stable to unstable packages including "sudo rm /etc/apt/sources.list.d/duet3d.list" before updating to the unstable packages. but if I start on unstable it appears to install all files correctly including DWC 3.21b as previously it hadn't been ...maybe there is some permission issue with that aspect ? dunno because I have no idea what I'm doing.
    So I did a fresh install duetpi then changed to unstable above post errors etc happens
    installed Pi Os and install duet directly to unstable all appears to works fine ..done this a few times now with the same results not sure this is relevant to anyone but helped me ease the boredom.

    and of course fix my install I can now see the plugins...now what else can I break?

    Cheers
    C



  • @Carlo

    After delta calibration got this,

    9/18/2020, 5:19:14 PM M122
    === Diagnostics ===
    RepRapFirmware for Duet 3 MB6HC version 3.2-beta1 running on Duet 3 MB6HC v1.01 or later (SBC mode)
    Board ID: 08DJM-956L2-G43S8-6J1DJ-3SJ6P-980QG
    Used output buffers: 1 of 40 (10 max)
    === RTOS ===
    Static ram: 154820
    Dynamic ram: 132820 of which 44 recycled
    Exception stack ram used: 528
    Never used ram: 105004
    Tasks: HEAT(blocked,296) CanReceiv(blocked,948) CanSender(blocked,351) CanClock(blocked,352) TMC(blocked,18) MAIN(running,276) IDLE(ready,19)
    Owned mutexes:
    === Platform ===
    Last reset 00:15:15 ago, cause: software
    Last software reset at 2058-01-24 11:14, reason: HardFault imprec, none spinning, available RAM 192284, slot 1
    Software reset code 0x4071 HFSR 0x40000000 CFSR 0x00000400 ICSR 0x0440f803 BFAR 0x00000000 SP 0x204179a8 Task MAIN
    Stack: 20430b4c 00000000 20417aa4 20430b40 3f800000 00416401 00416010 81000000 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5
    Error status: 0x020
    MCU temperature: min 28.8, current 29.4, max 30.7
    Supply voltage: min 24.1, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
    12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0
    Driver 0: position 76427, standstill, reads 34458, writes 25 timeouts 0, SG min/max 0/185
    Driver 1: position 76427, standstill, reads 34458, writes 25 timeouts 0, SG min/max 0/214
    Driver 2: position 76427, standstill, reads 34459, writes 25 timeouts 0, SG min/max 0/156
    Driver 3: position 0, standstill, reads 34470, writes 14 timeouts 0, SG min/max 0/0
    Driver 4: position 0, standstill, reads 34474, writes 11 timeouts 0, SG min/max 0/0
    Driver 5: position 0, standstill, reads 34474, writes 11 timeouts 0, SG min/max 0/0
    Date/time: 2020-09-18 17:19:13
    Slowest loop: 6.67ms; 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: 372, MaxWait: 403819ms
    Bed compensation in use: none, comp offset 0.000
    === MainDDARing ===
    Scheduled moves: 62, completed moves: 62, 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 0 is on, I-accum = 0.3
    Heater 1 is on, I-accum = 0.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.00ms; fastest: 5726623.00ms
    Responder states:
    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 3676, send timeouts 3676, longest wait 0ms for type 0, free CAN buffers 48
      === SBC interface ===
      State: 0, failed transfers: 13
      Last transfer: 17ms ago
      RX/TX seq numbers: 25629/28169
      SPI underruns 105, overruns 15
      Number of disconnects: 1
      Buffer RX/TX: 0/0-0
      === Duet Control Server ===
      Duet Control Server v3.2.0-beta1+1
      Code buffer space: 4096
      Configured SPI speed: 8000000 Hz
      Full transfers per second: 31.00
      9/18/2020, 5:18:18 PM G32
      Calibrated 8 factors using 17 points, (mean, deviation) before (0.079, 0.039) after (-0.000, 0.021)
      9/18/2020, 5:18:17 PM Connection to Duet established
      9/18/2020, 5:18:17 PM Warning: Lost connection to Duet (Board is not available (no header))


  • @Carlo

    Fixed all errors by installing 3.2b1 via bossa after resetting the board and then apt get for DSF DWC, had to reset the firmware as updating to the stable feed and going back to 3.1.1 was still giving the lost connection no data error every couple of seconds.

    Now done a few small prints printer on for a few hours now with not a blip.
    Again not sure if relevant to anything or anyone.

    Cheers
    C


Log in to reply