Updating Duet3 via DWC even when using SBC

[BlueDust]

Hello,
I tried to update my Duet3 6HC with SBC and it appears to not work.
DWC says version 3.4.6, DSF says version 3.4.6, but Firmware says 3.4.5.
I am trying to install the Input Shaping Plugin, and it fails because Plugin service has not started.
I am guessing its failing because the firmware is wrong, or at least its low hanging fruit to fix....
I tried to update the Duet3 via DWC but it stated only update if support tells you to do so, otherwise only update via SBC.
2 problems

1. How do I update The Duet3?
2. If updating the Duet3 doesn't fix the plugin service, how do I start it?

Thanks!

[BlueDust]

Kept looking for info on the 1st problem...
Found this and fixed it.
https://forum.duet3d.com/topic/34638/sudo-apt-dist-upgrade-doesn-t-update-main-board

I am still getting the error about the plug in service not running....
But again will keep looking for a fix for this.

[BlueDust]

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.5 (2022-11-30 19:35:23) running on Duet 3 MB6HC v1.01 (SBC mode)
Board ID: 08DJM-956L2-G43S4-6JTDJ-3SD6S-9S5YD
Used output buffers: 4 of 40 (18 max)
=== RTOS ===
Static ram: 152760
Dynamic ram: 67164 of which 16 recycled
Never used RAM 130732, free system stack 194 words
Tasks: SBC(resourceWait:,0.5%,476) HEAT(notifyWait,0.0%,322) Move(notifyWait,0.0%,351) CanReceiv(notifyWait,0.0%,740) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.0%,333) TMC(notifyWait,7.7%,91) MAIN(running,90.0%,1227) IDLE(ready,1.8%,30), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:20:22 ago, cause: power up
Last software reset at 2024-01-26 15:09, reason: User, Platform spinning, available RAM 125540, slot 1
Software reset code 0x0000 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 134
MCU temperature: min 19.7, current 35.4, max 35.5
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.1, current 12.2, max 12.2, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, mspos 8, reads 13784, writes 14 timeouts 0
Driver 1: standstill, SG min 0, mspos 8, reads 13784, writes 14 timeouts 0
Driver 2: standstill, SG min 0, mspos 8, reads 13787, writes 11 timeouts 0
Driver 3: standstill, SG min 0, mspos 8, reads 13787, writes 11 timeouts 0
Driver 4: standstill, SG min 0, mspos 8, reads 13784, writes 14 timeouts 0
Driver 5: standstill, SG min 0, mspos 8, reads 13784, writes 14 timeouts 0
Date/time: 2024-01-29 18:14:27
Slowest loop: 24.21ms; fastest: 0.03ms
=== 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, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
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
=== 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 13233, received 268, lost 0, boc 0
Longest wait 2ms for reply type 2010, peak Tx sync delay 61138, free buffers 50 (min 49), ts 6112/6098/0
Tx timeouts 0,0,13,0,0,7 last cancelled message type 30 dest 127
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 47168/47168
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x2ad1c
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4.6
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 27.49, max time between full transfers: 1723.4ms, max pin wait times: 1760.6ms/9.3ms
Codes per second: 0.04
Maximum length of RX/TX data transfers: 3487/876

[BlueDust]

[BlueDust]

Kept looking for info on the 1st problem...
Found this and fixed it.
https://forum.duet3d.com/topic/34638/sudo-apt-dist-upgrade-doesn-t-update-main-board

I am still getting the error about the plug in service not running....
But again will keep looking for a fix for this.