Loading reference vehicle0%
Book a demo
Model-based calibration, multi-agent diagnostics, MDF4 analysis and ECU documentation, built local-first for OEM and Tier-1 teams. No licence server; your data stays on your bench.
Use the arrow keys to turn and tilt the car. Enter steps through front, side, rear and top views. Home resets.
Reference vehicle
1989 V10 Formula car · 3.5 L
01 / 05 — Aerodynamics
Front wing, nose and the stacked rear wing. Downforce is a chain of small surfaces working together, tuned by the millimetre and proven in the data.
MDX Ride heights, pressures and loads arrive as MDF4 channels. MDX opens the run, aligns every signal and finds the moment the balance moved.02 / 05 — Bodywork
Engine cover, sidepods, mirrors and screen. Underneath, every system the bodywork was hiding. Your ECU documentation should open the same way.
XHandbook Browse ECU documentation containers offline, with every label resolved against the A2L: address, conversion, units.03 / 05 — Power unit
The 3.5-litre V10 rises out of the chassis with its intake trumpets, radiators, exhausts, gearbox and floor. This is where most of the calibration lives.
CIE Pro Build response models from test data and explore calibration trade-offs before the next dyno slot. Hexx Open the flash image and see each map by name, not by address, with checksums recomputed on save.04 / 05 — Running gear
Wheels, tyres, brakes, driveshafts and wishbones, separated corner by corner. When something goes wrong here you need evidence, not a guess.
DiagAI Ask the measurement a question. Diagnostic agents work through your data privately, on your own machine.05 / 05 — The whole system
Every part has an owner, a calibration and a history. Nothing should reach the car without review.
HELIX Change packages, variant compare, validation gates and one ECU-ready release, with the audit trail intact. Orbis An agent workspace that understands calibration files, and asks before it changes anything.Reassembly
Shakedown
Every lap becomes a measurement. Every measurement becomes a decision about the next one.
The suite
Each tool owns one part of the job. Start with the one you need; they share the same files, the same A2L and the same local-first rules.
MDF / MF4 data lab. Import a run, index every signal, compare cursors, map GPS offline.
Natural-language questions over your measurements, answered by diagnostic agents that run privately.
ECU documentation navigator with deep A2L integration. Labels resolve to address, record layout and units.
Model-based calibration from test data: design experiments, fit responses, explore the trade-offs.
A2L-aware hex and binary editor. Intel HEX, S-record or BIN in; named maps out; checksums handled.
Calibration data management. DCM and CDFX change packages, reviewed, gated and released.
The agent workspace for calibration and measurement. Every change arrives as a diff you approve.
The loop
The same car goes round the same loop, run after run. Together they form ECU calibration software that follows the work from signal to release, handing it to each other so nothing is retyped and nothing is lost between steps.
Record and open the run.
MDXTrace signals to their documentation.
XHandbook · DiagAIModel the response, choose the change.
CIE ProSee the change in the binary.
HexxReview, gate and sign off.
HELIXBy task
Most engineers arrive with a problem rather than a product in mind. These pages start from the work and end at the tool that does it — powertrain calibration software, diagnostics and measurement analysis, built in India for OEM and Tier-1 engineering teams.
Pedal tip-in, torque delivery and shift feel — and why a rating alone will not tell you what moved.
Engine and aftertreatment control against a certification cycle, where the margin has to survive the run-to-run scatter.
Thresholds, debounce and in-use performance ratios: the settings that decide when a monitor actually reports.
Getting from a fault code or a customer complaint to a cause you can point at in the data.
Measurement files, bus traffic and fault memory turned into an answer about one control unit.
The same question asked across many vehicles, where the pattern matters more than any single run.
Holding the evidence a type-approval submission rests on, so the file you send is the file you tested.
How an A2L describes the maps inside a HEX image, and what breaks when the two drift apart.
Install it and use it. There is no license server to check in with and no seat to release, so the calibration software keeps working on a bench that has never seen the internet. How we handle your data.
Measurements, maps and documentation open on the machine they live on, in the lab or at the track.
AI features can run against a local model when the data cannot leave the building.
Questions
An engineering suite for automotive teams: MDX for MDF4 measurement data, CIE Pro for model-based calibration, Hexx for A2L-aware HEX editing, HELIX for calibration release management, DiagAI for multi-agent diagnostics, XHandbook for ECU documentation and Orbis for agent-driven workflows.
The desktop instruments (MDX, Hexx and XHandbook) run on your own machine and need no licence server. DiagAI and HELIX can be deployed on-premise when confidential data cannot leave the building.
It builds surrogate models such as Gaussian processes from a designed set of test points, then uses constrained Bayesian and multi-objective optimisation to spend the next dyno runs where they matter, instead of sweeping the full design space.
DiagAI works over MDF/MF4 measurement data and fault memory, with support for UDS (ISO 14229), OBD-II, J1939, CAN and LIN. Specialist agents cover misfire, DFC, IUPR, gear, drivability, fuel and WLTP analysis.
Yes. MDX ships an MCP server and a local REST API with a Python SDK, so assistants such as Claude, ChatGPT, Codex or Gemini can open files, extract channels and run analyses. Orbis adds a reviewed, logged workflow on top.
Next step
Show us a real file and a real problem. We will walk through it with the tools that fit.