← System records

Vehicle diagnostics · Hardware · Provenance

OBD2Tech Capture + Journal

A local vehicle-diagnostic workflow: an iPhone recorder captures read-only signals from the owner's Jeep, and a journal turns signed recordings into traceable findings without losing where a reading came from.

State
Field-validated private system
Form
Private product
Updated
2026-09-24
  1. Vehicle signal
  2. iPhone capture
  3. Signed bundle
  4. Journal

Screens

All screens in the gallery →
OBD2Tech Journal Diagnostic Garage: scan findings such as a power transfer unit warning and lamp faults beside a 3D model of a black Jeep Cherokee and an evidence inspector.
The Diagnostic Garage maps real fault codes from the owner's 2014 Jeep Cherokee to vehicle zones on a source-calibrated model, not an exact CAD model. Captured 24 September 2026.
OBD2Tech Journal briefing: a Bank 2 oxygen-sensor activity difference repeated in qualifying evidence, with the measured figures, what the evidence supports, and the next inspection to run.
The Journal's briefing, built from real recordings of the owner's Jeep. Captured 24 September 2026.
OBD2Tech Journal diagnostic findings: 11 grouped findings in the latest complete scan, with 20 of 36 routes responding.
Findings grouped from the newest complete scan. Captured 24 September 2026.
OBD2Tech Journal Drive Coach, marked read-only research: a coach recording produced 4 of 4 descriptive analysis groups, while matched comparisons are not yet established.
Drive Coach research keeps measurement separate from advice. Captured 24 September 2026.
Four OBD2Tech Capture screens on an iPhone: the vehicle page with a 3D illustration of a 2014 Jeep Cherokee Limited, the field plan ready to collect, a live Drive Coach recording showing speed, gear, and RPM, and the evidence custody ledger.
The iPhone recorder in a simulator build with its built-in fixture values; the adapter, receipt, and hash values are fake. Captured 24 September 2026.
01

Problem

Vehicle data is difficult to trust when transport state, capture identity, and later interpretation are mixed together.

02

Actual state

The Journal holds 149 accepted sessions and 546 immutable analysis results, and it adopted Vehicle Evidence on 22 September 2026. The iPhone recorder, version 1.1.13, is installed and signs its field evidence but is not yet the accepted primary recorder; the Android recorder passed real-vehicle acceptance and remains the backup.

03

System architecture

The iPhone app reads a Bluetooth OBD adapter through a read-only, exclusive lease and seals each run into a signed bundle. Bundles travel through CloudKit to a Mac relay and ingest app. The Journal, a Python engine with a read-only local dashboard, records provenance, runs immutable analyses, and maps findings onto a 3D vehicle and transmission model.

04

Christian's role

Designed the hardware-facing capture flow, transport controls, evidence receipts, journal model, and recovery procedures; directed the implementation and validated it against the owner's vehicle and simulator paths.

05

Verified evidence

physicalAndroid real-vehicle acceptance: 36 of 36 routes
physicalAttended hardware capture and device workflow
runtimeVehicle Evidence adopted: 546 analysis results across 149 sessions
releaseiPhone recorder 1.1.13 recovered all 57 signed field plans
06

Safety, privacy, and authority boundary

  • The VIN stays private, and no GPS or route data is collected
  • Diagnostic support is not a repair guarantee
  • Capture and journal authorities remain distinct
  • The Journal dashboard is read-only
07

Current limitation

  • The iPhone recorder is not yet the accepted primary recorder; one real Drive Coach V2 drive and odometer qualification remain open.
  • The 3D garage is a source-calibrated blockout, not an exact CAD model, and the system is built around one owner's vehicle.
08

Next milestone

Record one real Drive Coach V2 acceptance drive.