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

    3.2Beta 4.1 reset - duet 3 mini5+ with SBC

    Scheduled Pinned Locked Moved
    Beta Firmware
    2
    2
    148
    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.
    • jay_s_ukundefined
      jay_s_uk
      last edited by

      I've been rebuilding my printer and during running the first test print the board reset.
      Here's an output of M122

      m122
      === Diagnostics ===
      RepRapFirmware for Duet 3 Mini 5+ version 3.2-beta4.1 running on Duet 3 Mini5plus Ethernet (SBC mode)
      Board ID: P2P4H-PA67A-G65J0-40TFU-L2D0Z-ZTS4L
      Used output buffers: 1 of 40 (10 max)
      === RTOS ===
      Static ram: 98728
      Dynamic ram: 119596 of which 24 recycled
      Never used RAM 42772, free system stack 200 words
      Tasks: Linux(blocked,101) HEAT(blocked,315) CanReceiv(blocked,967) CanSender(blocked,372) CanClock(blocked,363) TMC(blocked,105) MAIN(running,488) IDLE(ready,20) AIN(blocked,258)
      Owned mutexes: HTTP(MAIN)
      === Platform ===
      Last reset 00:02:55 ago, cause: software
      Last software reset at 2020-12-17 11:14, reason: HeatTaskStuck, GCodes spinning, available RAM 42320, slot 1
      Software reset code 0x4143 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0000080f BFAR 0xe000ed38 SP 0x2000ab84 Task MAIN
      Stack: 2001dfbc 0003035e 81000800 3f800000 40180000 4d8e8180 00000000 3e7f1f3e 3ddc9cf1 4530c6d4 4530c6d4 00000000 44b0c6d4 4301f53f 430aa7f0 00000000 3f800000 3f800000 3f800000 20000010 2001e530 200095b4 2001fe30 00000000 2001e530 00000080 a5a5a5a5
      Error status: 0x00
      Supply voltage: min 0.0, current 12.3, max 12.3, under voltage events: 0, over voltage events: 0, power good: yes
      Driver 0: position 0, standstill, SG min/max 38/38, read errors 0, write errors 1, ifcnt 76, reads 25058, writes 12, timeouts 0, DMA errors 0
      Driver 1: position 0, standstill, SG min/max 2/2, read errors 0, write errors 1, ifcnt 101, reads 25058, writes 12, timeouts 0, DMA errors 0
      Driver 2: position 0, standstill, SG min/max 2/2, read errors 0, write errors 1, ifcnt 101, reads 25057, writes 12, timeouts 0, DMA errors 0
      Driver 3: position 0, standstill, SG min/max 158/158, read errors 0, write errors 1, ifcnt 103, reads 25057, writes 12, timeouts 0, DMA errors 0
      Driver 4: position 0, standstill, SG min/max 154/154, read errors 0, write errors 1, ifcnt 107, reads 25058, writes 12, timeouts 0, DMA errors 0
      Driver 5: position 0, assumed not present
      Driver 6: position 0, assumed not present
      Date/time: 2020-12-17 11:17:42
      Slowest loop: 1.69ms; fastest: 0.08ms
      === Storage ===
      Free file entries: 10
      SD card 0 not detected, interface speed: 11.2MBytes/sec
      SD card longest read time 0.0ms, write time 0.0ms, max retries 0
      === Move ===
      FreeDm 169 (min 169), maxWait 0ms, bed compensation in use: none, comp offset 0.000
      === MainDDARing ===
      Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === 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, chamberHeaters = -1 -1
      Heater 1 is on, I-accum = 0.0
      === 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 queued 1581, send timeouts 1579, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 15
      === SBC interface ===
      State: 4, failed transfers: 0
      Last transfer: 8ms ago
      RX/TX seq numbers: 41417/6275
      SPI underruns 0, overruns 0
      Number of disconnects: 0, IAP RAM available 0x0b13c
      Buffer RX/TX: 0/0-0
      === Duet Control Server ===
      Duet Control Server v3.2.0-beta4
      Code buffer space: 4096
      Configured SPI speed: 8000000 Hz
      Full transfers per second: 35.00
      

      Info from the pi syslog

      Dec 17 11:14:27 duet3 DuetControlServer[1098]: [info] Job has been paused at byte 11404, reason User
      Dec 17 11:14:27 duet3 DuetControlServer[1098]: [warn] Lost connection to Duet (Timeout while waiting for transfer ready pin)
      Dec 17 11:14:27 duet3 DuetControlServer[1098]: [warn] Bad header checksum (expected 0xd0ff, got 0x2953)
      Dec 17 11:14:31 duet3 DuetControlServer[1098]: [warn] IPC#202: Client with outdated protocol version connected (got 8, want 10)
      Dec 17 11:14:31 duet3 DuetControlServer[1098]: [warn] IPC#203: Client with outdated protocol version connected (got 8, want 10)
      Dec 17 11:14:31 duet3 DuetControlServer[1098]: [warn] IPC#204: Client with outdated protocol version connected (got 8, want 10)
      Dec 17 11:14:47 duet3 DuetControlServer[1098]: [info] Connection to Duet established
      Dec 17 11:14:47 duet3 DuetControlServer[1098]: [info] Aborted job file
      Dec 17 11:14:47 duet3 DuetControlServer[1098]: [warn] Controller has been reset
      
      

      Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

      1 Reply Last reply Reply Quote 0
      • chrishammundefined
        chrishamm administrators
        last edited by

        Please upgrade to RC1 and check if the problem persists.

        Duet software engineer

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