BLUEPRINT DIAGNOSTICS • P59-FIRST DEVELOPMENT
Log. Compare. Calibrate.
Protect the controller.
Release 0.2 adds guarded live OBD logging through compatible Windows J2534 drivers, a definition-driven calibration workspace, complete change history, and a bench write/recovery gate. Programming traffic stays locked until the exact controller path passes recovery testing.EXACT VEHICLE
VIN-locked project
A VIN snapshot stays attached to every exported log. Later profile edits do not rewrite old records.
ACTUAL CONFIGURATION
Modified build sheet
The VIN only describes the factory vehicle. Record the engine, transmission, converter, injectors, fuel pressure, intake, exhaust, gearing, tires, sensors and controller changes actually installed.
BLUEPRINT LOGGER
Record, replay and export evidence
0 samples
No events recorded.
DEFINITION-DRIVEN EDITOR
Calibration workspace
Blueprint edits named parameters only when a matching definition supplies the address, data type, scaling, unit and safe range. It never guesses table locations.
Load a calibration and its matching Blueprint definition package.
No defined parameters loaded.
AUDIT TRAIL
Pending changes
Every edit will appear here with its original and new value.
Binary export requires a cryptographically verified production definition and a validated checksum provider. The included demo can never be flashed.
ORIGINAL FILE
Stock-backup fingerprint
Select an original controller read. Blueprint calculates a SHA-256 fingerprint locally so the project can prove which untouched backup it references.
- File
- Not selected
- Size
- —
- SHA-256
- —
SAFETY BOUNDARY
What remains locked
- Live mode permits only standard OBD data and vehicle-information requests.
- No security-access, erase, download or transfer-data request is exposed.
- No P59 binary definition or checksum provider is bundled.
- ECU erase, write and recovery remain disabled until spare-module bench validation.
WINDOWS PASS-THROUGH
J2534 live connection
Select the bus that matches the vehicle, then connect through an installed J2534 driver. The GM J1850 VPW profile is intended for older Class 2 vehicles such as the 2003 P59 truck; CAN is for compatible newer vehicles. MPVI3 is not treated as available unless HP Tuners provides an authorized integration.
No compatible driver information loaded.
CONTROLLER PROGRAMMING
Bench write gate
WRITE ECUUnavailable in 0.2.0
A real write release must identify the exact VIN, controller and operating system; verify stable protected voltage; compare two original reads; validate the definition signature and controller checksum; and pass an intentional power-loss recovery test on a spare PCM.
Two identical controller readsRead path is the next P59 bench milestone
NEEDEDSigned OS-specific definitionNo guessed addresses or unverified files
NEEDEDIndependent checksum validationMust agree before and after every change
NEEDEDPower-loss recoveryIntentional interruption test on spare hardware
NEEDEDEmission-system protections retainedNo defeat-device or safety-system presets
REQUIREDBLUEPRINT LINK
Our own USB-C OBD interface
Blueprint Link is the planned companion device—not a copy of HP Tuners hardware. It uses an open Blueprint USB protocol and a Windows J2534 driver, with a separate physical safety state for read-only vehicle use and protected bench programming.
The downloadable package includes the Blueprint Link architecture, first prototype bill of materials, USB command protocol and firmware safety-state header. A production device still needs schematic/PCB review, EMC/ESD testing, enclosure work, driver signing and real bench validation.
0%BENCH READINESS
Setup incomplete
This score measures project preparation only. It never unlocks ECU writing in the developer preview.