BLUEPRINT STUDIO 0.2.0
A real Windows logger and calibration workspace—built toward safe ECU programming
Blueprint Studio now has a native Windows J2534 bridge for guarded standard OBD logging, exact VIN and modified-build snapshots, a definition-driven calibration workspace, complete change history, original-file fingerprints, and a hard bench write/recovery gate.BLUEPRINT LINK DEVICE
How we build our own OBD tuning interface
Read-only J2534 logging
Probe a registered Windows pass-through and log whitelisted Mode 01 data through GM J1850 VPW or 11-bit 500 kbit CAN. Security, erase and programming services are not exposed.
Definition-driven calibration
Blueprint edits only parameters whose definition supplies an exact address, data type, scaling, unit and safe range. The included synthetic demo cannot map or flash a real ECU.
Auditable vehicle projects
Every log and change manifest preserves the VIN, controller, operating system, modified build sheet, original-file fingerprint and before/after values.
Blueprint Link device plan
The download includes the hardware architecture, first prototype bill of materials, USB command protocol and firmware safety states for our planned USB-C OBD interface.
HOW IT WORKS
From symptom to measured proof
- Download and extract Blueprint Studio on a Windows computer with Node.js 22 or newer.
- Run start-blueprint-studio.cmd; the first launch installs the pinned native bridge dependency.
- Install the official driver for a compatible J2534 device, probe it, and test read-only logging on a protected bench before a vehicle.
- Use the safe demo to test calibration editing and change manifests while the real P59 definition, checksum and write/recovery path remain locked.
BLUEPRINT DIAGNOSTICS