Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    Duet3 resets mid print on RRF 3.2

    Scheduled Pinned Locked Moved Unsolved
    Beta Firmware
    2
    4
    289
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • evomotorsundefined
      evomotors
      last edited by

      My setup:
      RPi4, Duet3 6CH and 3CH Expansion board latest stable RRF 3.2 installed yesterday.

      Already had 2 instances of board reset mid-print, print status reported as completed. Diagnostic reporting

      Last reset 00:48:00 ago, cause: watchdog
      

      Also getting constant disconnects

      Warning: Lost connection to Duet (Board is not available (no header))
      

      Duet3 diagnostics

      M122
      === Diagnostics ===
      RepRapFirmware for Duet 3 MB6HC version 3.2 running on Duet 3 MB6HC v1.01 or later (SBC mode)
      Board ID: 08DJM-956L2-G43S8-6JKDL-3SJ6L-1802G
      Used output buffers: 1 of 40 (10 max)
      === RTOS ===
      Static ram: 149788
      Dynamic ram: 63136 of which 68 recycled
      Never used RAM 145840, free system stack 124 words
      Tasks: Linux(ready,95) HEAT(blocked,296) CanReceiv(blocked,927) CanSender(blocked,344) CanClock(blocked,352) TMC(blocked,19) MAIN(running,717) IDLE(ready,19)
      Owned mutexes: HTTP(MAIN)
      === Platform ===
      Last reset 00:48:00 ago, cause: watchdog
      Last software reset at 2021-01-06 15:10, reason: User, none spinning, available RAM 145840, slot 0
      Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task Linu Freestk 0 n/a
      Error status: 0x00
      Aux0 errors 0,0,0
      Aux1 errors 0,0,0
      MCU temperature: min 35.0, current 37.4, max 37.6
      Supply voltage: min 24.0, 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 81124, standstill, reads 27916, writes 22 timeouts 0, SG min/max 0/247
      Driver 1: position 3042, standstill, reads 27917, writes 22 timeouts 0, SG min/max 0/244
      Driver 2: position 705, standstill, reads 27917, writes 22 timeouts 0, SG min/max 0/255
      Driver 3: position 0, standstill, reads 27917, writes 22 timeouts 0, SG min/max 0/266
      Driver 4: position 0, ok, reads 27917, writes 22 timeouts 0, SG min/max 0/1023
      Driver 5: position 0, ok, reads 27917, writes 22 timeouts 0, SG min/max 0/851
      Date/time: 2021-01-06 15:58:16
      Slowest loop: 181.89ms; fastest: 0.04ms
      === 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 ===
      DMs created 125, maxWait 887437ms, bed compensation in use: mesh, comp offset 0.000
      === MainDDARing ===
      Scheduled moves 30838, completed moves 30809, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 2], CDDA state 3
      === AuxDDARing ===
      Scheduled moves 0, completed moves 0, hiccups 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
      Heater 0 is on, I-accum = 0.3
      Heater 1 is on, I-accum = 0.3
      === GCodes ===
      Segments left: 1
      Movement lock held by null
      HTTP* is doing "M122" in state(s) 0
      Telnet is idle in state(s) 0
      File* is doing "G1 X249.156006 Y219.667999 E0.013370" 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 queued 37418, send timeouts 0, received 7, lost 0, longest wait 1ms for reply type 6042, free buffers 48
      === SBC interface ===
      State: 0, failed transfers: 0
      Last transfer: 1ms ago
      RX/TX seq numbers: 50811/50812
      SPI underruns 0, overruns 0
      Number of disconnects: 0, IAP RAM available 0x2c8a8
      Buffer RX/TX: 48/1560-0
      === Duet Control Server ===
      Duet Control Server v3.2.0
      File:
      Buffered code: G1 X249.156 Y219.668 E0.01337
      Buffered code: G1 X249.383 Y219.895 E0.01068
      Buffered code: G1 X249.472 Y220.287 E0.01337
      Buffered code: G1 X249.472 Y222.095 E0.06013
      Buffered code: G1 X249.492 Y222.913 E0.02721
      Buffered code: G1 X249.557 Y223.75 E0.02792
      Buffered code: G1 X249.664 Y224.582 E0.0279
      Buffered code: G1 X249.813 Y225.406 E0.02785
      Buffered code: G1 X250.005 Y226.223 E0.02791
      Buffered code: G1 X250.238 Y227.029 E0.02791
      Buffered code: G1 X250.511 Y227.819 E0.0278
      Buffered code: G1 X250.745 Y228.402 E0.02089
      Buffered code: G1 X250.829 Y228.604 E0.00728
      Buffered code: G1 X251.179 Y229.359 E0.02768
      Buffered code: G1 X251.57 Y230.099 E0.02784
      Buffered code: G1 X251.998 Y230.819 E0.02786
      Buffered code: G1 X252.463 Y231.515 E0.02784
      Buffered code: G1 X252.967 Y232.194 E0.02813
      Buffered code: G1 X253.498 Y232.837 E0.02774
      Buffered code: G1 X254.064 Y233.455 E0.02787
      Buffered code: G1 X254.661 Y234.042 E0.02785
      Buffered code: G1 X255.288 Y234.6 E0.02792
      Buffered code: G1 X255.942 Y235.124 E0.02787
      Buffered code: G1 X256.621 Y235.613 E0.02783
      Buffered code: G1 X257.328 Y236.07 E0.028
      Buffered code: G1 X258.053 Y236.487 E0.02782
      Buffered code: G1 X258.798 Y236.866 E0.0278
      Buffered code: G1 X259.372 Y237.125 E0.02094
      Buffered code: G1 X259.572 Y237.211 E0.00724
      Buffered code: G1 X260.285 Y237.489 E0.02545
      Buffered code: G1 X260.822 Y237.671 E0.01886
      Buffered code: G1 X261.025 Y237.737 E0.0071
      ==> 1528 bytes
      Code buffer space: 2540
      Configured SPI speed: 8000000 Hz
      Full transfers per second: 40.41
      Maximum length of RX/TX data transfers: 3176/1684
      File /opt/dsf/sd/gcodes/ZR_BearingTopMount_FR.gcode is selected, processing
      

      3CH ecpansion diagnostics

      M122 B1
      Diagnostics for board 1:
      Duet EXP3HC firmware version 3.2 (2021-01-05)
      Bootloader ID: not available
      Never used RAM 154848, free system stack 154 words
      HEAT 90 CanAsync 94 CanRecv 83 TMC 30 MAIN 293 AIN 257
      Last reset 22:54:23 ago, cause: power up
      Last software reset data not available
      Driver 0: position 0, 80.0 steps/mm,  standstill, reads 40773, writes 0 timeouts 0, SG min/max not available
      Driver 1: position 4730738, 172.0 steps/mm,  ok, reads 40750, writes 22 timeouts 0, SG min/max 0/723
      Driver 2: position 0, 80.0 steps/mm,  standstill, reads 40772, writes 0 timeouts 0, SG min/max not available
      Moves scheduled 619649, completed 619599, in progress 1, hiccups 1556
      Next step interrupt due in 2509 ticks, enabled
      VIN: 24.6V, V12: 12.3V
      MCU temperature: min 43.8C, current 44.0C, max 44.2C
      Ticks since heat task active 5, ADC conversions started 82463996, completed 82463996, timed out 0
      Last sensors broadcast 0x00000000 found 0 9 ticks ago, loop time 0
      CAN messages queued 36, send timeouts 0, received 859805, lost 0, free buffers 32
      
      1 Reply Last reply Reply Quote 0
      • Phaedruxundefined
        Phaedrux Moderator
        last edited by

        Is this a recent setup of DuetPi or the version that came on the SD card with the board?

        A quick test would be to setup a new SD card with a fresh DuetPi image and then doing an apt update.

        https://pkg.duet3d.com/DuetPi-lite.zip

        https://pkg.duet3d.com/DuetPi.zip

        How is the Pi4 powered?

        Z-Bot CoreXY Build | Thingiverse Profile

        evomotorsundefined 1 Reply Last reply Reply Quote 0
        • evomotorsundefined
          evomotors @Phaedrux
          last edited by

          @Phaedrux said in Duet3 resets mid print on RRF 3.2:

          Is this a recent setup of DuetPi or the version that came on the SD card with the board?

          A quick test would be to setup a new SD card with a fresh DuetPi image and then doing an apt update.

          https://pkg.duet3d.com/DuetPi-lite.zip

          https://pkg.duet3d.com/DuetPi.zip

          How is the Pi4 powered?

          SD card (Pre imaged) that came with Duet3 board
          RPi 4 powered from it's own power supply (MEAN WELL 323282 RS-25-5 )

          Phaedruxundefined 1 Reply Last reply Reply Quote 0
          • Phaedruxundefined
            Phaedrux Moderator @evomotors
            last edited by

            @evomotors said in Duet3 resets mid print on RRF 3.2:

            SD card (Pre imaged) that came with Duet3 board

            Definitely try a fresh one.

            Z-Bot CoreXY Build | Thingiverse Profile

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Unless otherwise noted, all forum content is licensed under CC-BY-SA