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

    After update, DWC is out of Sync with board.

    Scheduled Pinned Locked Moved Solved
    Firmware installation
    2
    3
    105
    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.
    • BlueDustundefined
      BlueDust
      last edited by

      I am running a Duet3 connected to an SBC. I completed the update from the Pi console using apt-get update/upgrade like I have done in the past, but DWC apparently didn't update.
      What is the best way to update the DWC out of band (hopefully without having to redo everything)?

      Thanks!

      d3fdfb0f-0447-442e-9d72-cd40e9f20dfc-image.png

      M122
      === Diagnostics ===
      RepRapFirmware for Duet 3 MB6HC version 3.5.4 (2024-11-24 10:47:10) running on Duet 3 MB6HC v1.02 or 1.02a (SBC mode)
      Board ID: 08DJM-9P63L-DJ3T8-6J9D6-3SN6S-1U7ZB
      Used output buffers: 2 of 40 (40 max)
      === RTOS ===
      Static ram: 155464
      Dynamic ram: 89560 of which 5272 recycled
      Never used RAM 91928, free system stack 112 words
      Tasks: SBC(2,ready,0.9%,807) HEAT(3,nWait 6,0.0%,321) Move(4,nWait 6,0.6%,211) CanReceiv(6,nWait 1,0.0%,771) CanSender(5,nWait 7,0.0%,325) CanClock(7,delaying,0.0%,346) TMC(4,nWait 6,9.3%,53) MAIN(2,running,89.1%,101) IDLE(0,ready,0.0%,29), total 100.0%
      Owned mutexes: HTTP(MAIN)
      === Platform ===
      Last reset 113:05:29 ago, cause: software
      Last software reset at 2025-01-28 21:32, reason: User, Gcodes spinning, available RAM 91928, slot 2
      Software reset code 0x6003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0043c000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
      Error status: 0x04
      Aux0 errors 0,2,0
      MCU temperature: min 32.6, current 36.9, max 40.9
      Supply voltage: min 23.8, current 24.0, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
      12V rail voltage: min 12.0, current 12.3, max 12.6, under voltage events: 0
      Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/568/568, gc cycles 0
      Events: 1 queued, 1 completed
      Driver 0: standstill, SG min 0, mspos 136, reads 25594, writes 75 timeouts 0
      Driver 1: standstill, SG min 0, mspos 760, reads 25595, writes 75 timeouts 0
      Driver 2: standstill, SG min 0, mspos 744, reads 25595, writes 75 timeouts 0
      Driver 3: standstill, SG min 0, mspos 104, reads 25445, writes 225 timeouts 0
      Driver 4: standstill, SG min 0, mspos 232, reads 25465, writes 205 timeouts 0
      Driver 5: standstill, SG min n/a, mspos 8, reads 25659, writes 11 timeouts 0
      Date/time: 2025-02-02 14:38:08
      Slowest loop: 1001.02ms; fastest: 0.04ms
      === Storage ===
      Free file entries: 20
      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, segments created 38, maxWait 78056668ms, bed compensation in use: mesh, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
      no step interrupt scheduled
      Moves shaped first try 115883, on retry 37828, too short 221420, wrong shape 1257363, maybepossible 63368
      === DDARing 0 ===
      Scheduled moves 615600, completed 615600, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === DDARing 1 ===
      Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === Heat ===
      Bed heaters 2 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
      Heater 0 is on, I-accum = 0.0
      Heater 2 is on, I-accum = 0.1
      === GCodes ===
      Movement locks held by null, 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
      File2 is idle in state(s) 0
      Queue2 is idle in state(s) 0
      Q0 segments left 0, axes/extruders owned 0x80000003
      Code queue 0 is empty
      Q1 segments left 0, axes/extruders owned 0x0000000
      Code queue 1 is empty
      === CAN ===
      Messages queued 5265641, received 8143332, lost 0, errs 16, boc 0
      Longest wait 3ms for reply type 6013, peak Tx sync delay 280, free buffers 50 (min 49), ts 2035646/2035645/0
      Tx timeouts 0,0,0,0,0,0
      === SBC interface ===
      Transfer state: 5, failed transfers: 0, checksum errors: 0
      RX/TX seq numbers: 11810/11810
      SPI underruns 0, overruns 0
      State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x24c68
      Buffer RX/TX: 0/0-0, open files: 0
      === Duet Control Server ===
      Duet Control Server version 3.5.4 (2024-11-25 17:29:06, 32-bit)
      HTTP+Executed:
      > Executing M122
      Code buffer space: 4096
      Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
      Full transfers per second: 39.15, max time between full transfers: 303.0ms, max pin wait times: 186.1ms/22.8ms
      Codes per second: 4.69
      Maximum length of RX/TX data transfers: 4520/1664
      

      I would also like to thank you for this update as it fixed an odd problem that just recently started. I wasn't having any issues with my printer to really speak of until about 3 weeks ago. I figured it may be a hardware issue because the problem just started without having made any changes to the printer in a long time, but wanted to update before I posted the issue here asking for help. Its hard to explain but generally noticed it when the PanelDue failed to run specific touch screen commands like "resume" after pausing a print. I guess its possible the MicroSD card is starting to die and the update replaced the corrupt files (still being a hw issue) but wanted to share incase it helps someone else and stating just updating the Duet Software may help. (I didn't replace my MicroSD card, only updated via SBC)
      Copied one of the errors here from event logs.

      Error: Pop(): stack underflow on Aux
      

      Fun, that 3 letter word with "u" in the middle.

      jay_s_ukundefined 1 Reply Last reply Reply Quote 0
      • jay_s_ukundefined
        jay_s_uk @BlueDust
        last edited by

        @BlueDust clear your browser cache.

        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

        BlueDustundefined 1 Reply Last reply Reply Quote 1
        • BlueDustundefined
          BlueDust @jay_s_uk
          last edited by

          @jay_s_uk

          LMAO!

          That's a fun ending to this story!
          Thanks!

          Fun, that 3 letter word with "u" in the middle.

          1 Reply Last reply Reply Quote 1
          • BlueDustundefined BlueDust marked this topic as a question
          • BlueDustundefined BlueDust has marked this topic as solved
          • First post
            Last post
          Unless otherwise noted, all forum content is licensed under CC-BY-SA