Skip to main content
EVCore versions its firmware, host protocol, report schema, board definitions, knowledge packages, calibration formats, and EVCore Studio independently. Data from another version must be validated, and migrations must be explicit.

Version identifiers

Rules

  • Every report carries the firmware, build, protocol, and board identifiers, so any result can be traced to what produced it.
  • Studio refuses a device whose protocol version it does not support. It does not guess at compatibility.
  • A version bump belongs in the same commit as the change that requires it, with a CHANGELOG.md entry.
  • Stored data (Studio records, calibration, and knowledge files) carries its own schema version. Loading an unknown version fails safely instead of reinterpreting it.

Recent changes

The CHANGELOG.md records notable changes to the firmware and EVCore Studio. No hardware release has been made yet; everything runs on the host simulator.
  • Studio 0.3.2 (2026-09-26): Help link opens the feedback page at csharness.com/pages/feedback.
  • Studio 0.3.1 (2026-09-26): Pre-order with beta access; sign-in screens explain account creation with the order email.
  • Studio 0.3.0 (2026-09-25): Two editions in one download (Studio and Studio Pro), new Diagnoses screen with PDF reports, redesigned UI with dark theme, email confirmation and password reset, Windows installer with auto-update.
  • Firmware 0.1.0 (unreleased): Safety requirements SR-01 to SR-19 with traced tests, draft hazard analysis with 16 hazards, generated fault-injection matrix, seeded fuzz tests, strict build gates, local screen menus, on-device diagnostic codes, structured fault records, host protocol 2 with request tags, and version reporting in INFO and REPORT JSON.
For the full history, see CHANGELOG.md in the repository.