Technical Brief · Architecture

VehicleLab Suite Technical Brief

Architecture, engineering interfaces, and local-first data containment across the integrated automotive engineering toolchain.

By Chayan Das, Founder & Lead Engineer

Download the PDF 8 pages, 561 KB · PDF

In short

The VehicleLab suite is an on-premise, local-first engineering ecosystem uniting seven specialized instruments: MDX for high-speed measurement analysis, CIE Pro for model-based calibration and DoE, HELIX for calibration lifecycle governance, Hexx for A2L-aware binary editing, DiagAI for protocol-level diagnostics, XHandbook for ECU function navigation, and Orbis for agentic engineering workflows. Built to replace fragmented desktop silos without imposing mandatory cloud telemetry, the suite operates directly on industry standards including ASAM MDF4, A2L (ASAP2), ISO 14229 UDS, SAE J1939, and the Model Context Protocol (MCP).

The automotive toolchain fragmentation problem

OEM calibration and software teams routinely manage fragmented toolchains across vehicle test campaigns. Separate proprietary desktop applications are deployed for bus logging, surrogate modelling, hex editing, and fault diagnosis, creating rigid data silos.

Legacy toolchains frequently impose restrictive node-locked license servers, require manual file format conversions, and lack open automation interfaces. The VehicleLab suite establishes a unified, local-first architecture where every instrument interoperates around open automotive standards without forcing telemetry egress.

Integrated suite instrument matrix

The suite comprises seven dedicated products spanning measurement to production release: MDX handles multi-gigabyte MDF4/BLF traces; CIE Pro optimizes dyno test envelopes using space-filling DoE; HELIX manages calibration datasets and semantic 3-way merges; Hexx edits binary images in engineering units; DiagAI isolates vehicle faults via 8 specialist agents; XHandbook navigates ECU function containers; and Orbis provides an agentic workspace with human approval gates.

Rather than enforcing an all-or-nothing migration, adoption is modular. Engineering teams can deploy individual instruments or integrate them into a continuous desktop and server pipeline.

Automotive data standards and interface bus

Interoperability is anchored in open standards: ASAM MDF v3/v4 for time-series measurement; ASAM MCD-2 MC (A2L) for ECU description; Intel HEX, Motorola S19, and raw binaries for flash images; DCM, CDFX, and PACO for parameter change packages; ISO 14229 (UDS) and SAE J1939 for diagnostics; and the Model Context Protocol (MCP) for AI agent integration.

Every instrument reads and writes native engineering artifacts directly, ensuring zero proprietary lock-in and seamless compatibility with established test equipment.

Data residency and air-gapped deployment architecture

All desktop instruments (MDX, Hexx, XHandbook, Orbis) operate locally via native Tauri wrappers on Windows, macOS, and Linux without calling external cloud servers. Server components (HELIX, CIE Pro, DiagAI) deploy fully on-premise inside corporate network boundaries.

AI agent integration relies on local loopback transports (stdio and 127.0.0.1 SSE) or self-hosted LLM endpoints via Ollama and LM Studio. Zero customer telemetry, calibration maps, or bus traces leave the engineering perimeter.

What we do not claim

VehicleLab is an independent software toolchain. We do not manufacture physical bus logger hardware, nor do we certify compliance with functional safety (ISO 26262) or legal type approvals without physical testing.

The suite does not perform live in-vehicle ECU flash flashing without verified hardware drivers, and AI agents operating within the suite do not execute autonomous calibration sign-offs without formal engineering review.

Questions

Frequently asked.

Can individual instruments be evaluated independently?

Yes. Every instrument in the VehicleLab suite functions as a standalone engineering tool. Teams can adopt MDX for telemetry, Hexx for binary editing, or CIE Pro for DoE without requiring the entire ecosystem.

Does the suite require an active internet connection or license server?

No. All desktop tools operate completely license-server-free and run in air-gapped dyno cells or secure test tracks. Server components deploy inside your private network.

Where can I download the complete suite PDF technical brief?

The complete technical brief is available for direct download at https://vehiclelab.in/resourses/market/vehiclelab-suite-brief.pdf.

Next step

Open one of your own files with us.

Send a measurement, an A2L or an EHANDBOOK container. We will open it in the instruments on a call, with your engineers in the room.

Book a technical demo Read the docs