Vehicle & ECU identity
Review VIN evidence and detected modules. Vehicle identification is subject to adapter support and ECU responses; missing information is not filled with guesses.
Information with
purpose.
A desktop diagnostics workspace and a complementary web dashboard. Each feature has a defined role—and an honest status.
Fault investigation
Inspect diagnostic findings with their source modules. Guided scanning and before/after repair snapshots help preserve context across a repair.
Live data
View supported measurements received from the connected vehicle. Signal availability depends on the module, protocol and validated definitions.
Definition Browser
Import ODX/PDX metadata through the engineering converter. Search services, parameters and units; export CSV. This is reference inspection, not live parameter editing.
Workshop records
Search received account-scoped diagnostic summaries and export matching records as JSON. Connected Windows builds upload after activation; real Windows synchronization acceptance testing remains required.
Software delivery
CORE has a signed release workflow. This website will expose installer downloads only after the release file and its verification metadata are connected.
Regeneration and programming
These remain development targets. Reading a truck does not establish safe support for active routines or ECU writes. Each ECU family needs an implemented procedure, compatibility checks and vehicle validation.
See the development roadmap →