Release Archive

Legacy README Changelog Archive

This page preserves technical notes from the former rolling changelog model in root `README.md`, prior to structured per-version release pages.

Why this archive exists

OpenHaldex development originally tracked engineering progress under a single rolling section in root README. That model worked during rapid bring-up, but once users needed version-selectable firmware installs and formal release notes, changelog structure needed to evolve.

This archive keeps historical signal intact while new releases move to version-specific notes pages. It is not a replacement for release tags; it is continuity context.

Archived categories from rolling changelog

Platform and build system pinning (PlatformIO, package versions, flash/fs layout).
Project architecture refactor into modular `src/functions/*` and `include/functions/*` layers.
CAN stack bus-role mapping (TWAI + MCP2515 split and abstraction stabilization).
Controller/map logic evolution (bilinear map interpolation and runtime gates).
Map storage and LittleFS persistence hardening.
Web API expansion and endpoint contract normalization.
Filesystem-backed logging and runtime debug controls.
CAN viewer diagnostics overhaul and capture workflows.
OTA update subsystem and release deployment automation.

Condensed historical notes

Platform and build stabilization

Historical notes document migration to pinned PlatformIO + ESP32 Arduino toolchain settings, explicit 16MB flash configuration, partition pinning, and LittleFS workflow stabilization. This laid the reproducibility foundation required for reliable release packaging.

CAN and control-path maturation

Legacy notes track the transition to dual-bus role handling with ESP32-S3 internal TWAI and MCP2515 split behavior, plus controller logic consolidation around map/curve calculations, gating behavior, and generation-specific frame mutation.

API and diagnostics expansion

The rolling changelog captured major endpoint additions (`status`, `settings`, map/curve CRUD, Wi-Fi/network, OTA, CAN viewer, logs) and corresponding UI surfaces. It also logged diagnostics upgrades for frame tagging, capture mode, and file-backed evidence trails.

How this maps to modern release pages

Going forward, each release page should answer:

What changed in this version only.
What users must do differently after flashing.
What known risks or migration notes exist.
Which binaries/manifests are required for installer integrity.

Legacy notes stay valuable for architectural history and root-cause research, while per-version pages give operational clarity to users in the field.

Reference links

Try the OpenHaldex Firmware Demo

Preview the real OpenHaldex firmware UI in your browser with simulated live CAN traffic and interactive pages for tuning, diagnostics, logs, setup, and OTA workflows.

Open firmware demo