v2.3.0 — "Feedback Loop"

📅 2026-08-22 · Full changelog

✨ Features

• DWC 3.6 UI (Vuetify 2), full parity with the 3.7 page (39cbf7a)

🐛 Bug Fixes

• remove a dead-but-live M569.1 write at the riskiest point in auto-tune, and gate every PID write on M400 (64a0ff6)
• ui36: auto-tune card filled solid blue instead of outlined (661b0ce)
• correct update-check DWC requirement when a release ships both generations (880b909)

♻️ Refactoring

• share the tuning logic between both UIs via one composable (bfa001d)
• restructure into ui37/ shell, no behaviour change (e1e5ab0)
• extract HostAdapter seam ahead of DWC 3.6 support (4a55622)

📄 Documentation

• mark Phases 0-2 of the DWC 3.6 backport plan done (c6ff0ac)

🧪 Tests

• add a fast compile check for the untypechecked DWC 3.6 UI (33e2791)

🧹 Chores & CI

• add DWC 3.6 build/release machinery, no UI yet (62efa70)

---

📦 Install

1. Download the ZIP for your DuetWebControl from the Assets below — they are different builds, not alternatives:
   • DWC 3.7 and newer → ClosedLoopTuning-2.3.0.zip
   • DWC 3.6 → ClosedLoopTuning-2.3.0-dwc36.zip
2. In DuetWebControl, go to Settings → General → Plugins and click Install Plugin.
3. Select the downloaded ZIP and accept the third-party-plugin prompt.
4. Reload DWC, then open Plugins → Closed Loop Tuning.

🔧 The 3.7 package is built against DuetWebControl 3.7.0-beta.3 (4d47719, ref v3.7-dev); the 3.6 package against the DWC 3.6 branch.
DWC refuses a package whose dwcVersion doesn't match, so picking the wrong one is safe but won't install.
⚙️ Requires a Duet 3 board with closed-loop driver support (a Duet3D Expansion 1HCL / M23CL, or any other RRF board reporting closed-loop driver telemetry). Tuning moves a single driver — make sure the axis is in a safe position before recording.