v2.6.0 — "Overshoot Yourself"

📅 2026-09-06 · Full changelog

✨ Features

• measure vibration with an accelerometer alongside tuning captures (982b522)
• raise M569.1 error thresholds for the duration of every tuning run (5adbdce)
• surface sample rate and M569.1 E threshold on the tuning page (62dee4b)
• cap the auto-tune capture sample rate, with a lower ceiling for RP2350 boards (8f76f46)

🐛 Bug Fixes

• wire up the accelerometer, and fix a cost bug behind inconsistent auto-tunes (0325aae)
• auto-tune now stops automatically on an emergency stop or a lost connection (9808f86)

📄 Documentation

• add an implementer handoff block to the accelerometer plan (864e74a)
• make accelerometer plan phases 1+3 implementation-ready (87a858f)
• plan for accelerometer-based vibration measurement during tuning (77c2389)

🧹 Chores & CI

• point build36.bat at the correct local DWC 3.6 checkout (b246650)

---

📦 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.6.0.zip
   • DWC 3.6 → ClosedLoopTuning-2.6.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-rc.1 (cf54b5a, 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.