Book a demo

06 / 07 — XHandbookAvailable

ECU documentation software with deep A2L integration.

Every label resolved to address, record layout, conversion and units.

Open, search, and navigate EHANDBOOK containers and interactive function models — then follow any label straight to its A2L calibration data. Local-first, no license server. The EHANDBOOK‑NAVIGATOR workflow you know, modernized.

Request a desktop build Read the docs

In pilot with Tier-1 powertrain teams

XHandbookMED_function_docs.ehb Live

ZWGRU — base ignition angle

The base angle is read from over engine speed and relative load , then limited to before the correction path.

.ehb · .ehbcrypt · .ehbp · label → A2L object → ECU address
Containers
.ehb, .ehbcrypt, .ehbp
Model navigation
Interactive KAOM function graphs
Core
Native Rust engine, no Electron
Calibration link
Bi-directional A2L resolution

Capabilities

One explorer, whole workflow.

  1. F1

    Document & Model Explorer

    Browse the full table of contents, read function documentation, and open interactive function models with automatic graph layout. Follow breadcrumbs and cross-links between docs and models without losing your place.

  2. F2

    Instant Global Search

    Search across topics, labels, components, and calibration objects in one query — with source-container provenance so you always know which container a hit came from. Find-in-tab narrows results inside the current view.

  3. F3

    Deep A2L Integration

    Convert A2L into a container, then resolve any label to its CHARACTERISTIC, MEASUREMENT, or AXIS_PTS — complete with ECU address, record layout, conversion method, units, and limits. Reverse lookup goes from an ECU parameter back to every topic that documents it.

  4. F4

    Label Intelligence

    Click any label for a popup of its metadata and the functions that import, export, and define it. Curves and maps render as calibrated 2D and 3D visualizations right where you need them — pin it, or copy it straight to search.

  5. F5

    Library, Comments & Attachments

    Organize bookmarks and model views into folders, leave comments in document and model contexts, and attach supporting files to topics. Import and export your annotations to share knowledge across the team.

  6. F6

    Export & Extract

    Export functional components to PDF for review, extract a subset of content into a new container, and bundle support logs in a click. Share exactly what a colleague or supplier needs — nothing more.

CONTAINER ANATOMY

It understands the whole container.

An EHANDBOOK container is far more than a PDF. XHandbook parses every layer — documentation, interactive models, structured metadata, and the search index — and normalizes them into one navigable model with stable, resolvable links.

Container layer Underlying format What XHandbook does with it
Documentation Structured DITA topics & generated HTML Function descriptions and parameter tables, browsable through the full table of contents with breadcrumbs and cross-links.
Interactive models KAOM function graphs Blocks, ports, connections, and annotations — laid out automatically so signal paths stay readable.
Metadata metadata.db (SQLite) Component and element relationships with access type, category, data type, units, and limits.
Search index Lucene index Ingested when present, with a fast fallback so any container stays searchable.

Resolving a label across the container

One label, followed from the topic that documents it, through the model block that uses it, down to the calibration object in the ECU:

Label in the documentationAccPedEv_tqWhlNorm_M

  1. Documented inPedal Map
  2. Used by model blockTrqMod / Subsystem

A2L object · CHARACTERISTIC · MAP

Address
0x80299464
Record layout
RB_Map_S16S16_S16
Unit
Nm
Axes
AccPed_rPrp %, VehV_vSign km/h
Show the resolution as text
VC1CP091…_HVR100.ehb
<span class="c-com"># resolving a label across the container</span>
<span class="c-key">label</span>   AccPedEv_tqWhlNorm_M
  <span class="c-arw">&rarr;</span> <span class="c-key">doc topic</span>     Pedal Map
  <span class="c-arw">&rarr;</span> <span class="c-key">model block</span>   TrqMod / Subsystem
  <span class="c-arw">&rarr;</span> <span class="c-key">a2l</span>           CHARACTERISTIC &middot; MAP
       <span class="c-key">addr</span>     <span class="c-val">0x80299464</span>
       <span class="c-key">layout</span>   <span class="c-val">RB_Map_S16S16_S16</span>
       <span class="c-key">unit</span>     <span class="c-val">Nm</span>
       <span class="c-key">axes</span>     <span class="c-val">[AccPed_rPrp %, VehV_vSign km/h]</span>

Workflow

From input to decision.

  1. 01

    Open the container

    Load an EHANDBOOK container or convert an A2L on the spot. XHandbook indexes the table of contents, labels, and calibration objects first, then streams heavy content only when you open it.

  2. 02

    Navigate & search

    Move through documentation and interactive models, or jump anywhere with global search. Multi-container projects keep clear source provenance so cross-references always resolve to the right place.

  3. 03

    Resolve to the ECU

    Click a label to bridge documentation and calibration data — its A2L object, ECU address, conversion, and value. Bookmark, comment, and export what matters for the next review.

Why it exists

Documentation that behaves like live engineering context.

XHandbook turns a static documentation drop into a living, queryable knowledge base. Built for calibration and validation engineers who live between ECU function documentation, interactive models, and calibration data — and who need every label to resolve, every time.

Validated against real Bosch and ETAS golden containers — including the HVR100 and FlexECU demo sets — and shipped as a local Tauri desktop application on Windows, macOS, and Linux.

Positioning

XHandbook vs legacy EHANDBOOK tooling.

The familiar EHANDBOOK‑NAVIGATOR workflow, rebuilt local-first and calibration-aware.

CapabilityLegacy doc toolingXHandbook Navigator
DeploymentLicense-server dependentLocal-first, no license server
PlatformWindows-only legacy buildModern desktop — Windows, macOS, Linux
Runtime & footprintHeavy legacy runtimeLightweight native Rust core, small install
Calibration linkLimited / separate toolsDeep native A2L resolution & reverse lookup
Container authoringSeparate toolchainBuilt-in A2L → container builder
InterfaceLegacy desktop widgetsModern, responsive UI

Questions

Asked by engineers, answered plainly.

Is XHandbook Navigator a replacement for ETAS EHANDBOOK-NAVIGATOR?

XHandbook Navigator reads the same EHANDBOOK container formats (.ehb, .ehbcrypt, .ehbp) and provides equivalent Document Explorer, Model Explorer, global search, and label popup capabilities. The key differences are that XHandbook runs entirely local-first with no license server required, and adds deep A2L integration — resolving documentation labels directly to ECU calibration objects (address, record layout, conversion method, units, live HEX) — which is not available in ETAS EHANDBOOK-NAVIGATOR.

What EHANDBOOK container formats does XHandbook support?

XHandbook Navigator supports .ehb (standard containers), .ehbcrypt (encrypted containers), and .ehbp (partial containers). These are ZIP-based archives containing DITA documentation, KAOM function models, a metadata.db SQLite database, and a Lucene search index. XHandbook has been validated against real Bosch and ETAS golden containers including HVR100 and FlexECU demo sets.

Does XHandbook Navigator require a license server?

No. XHandbook is fully license-server-free. It runs as a local Tauri desktop application on Windows, macOS, and Linux with no network dependency for core operation. This eliminates the floating license overhead that ETAS EHANDBOOK-NAVIGATOR requires.

What is A2L integration in XHandbook and how does it work?

XHandbook's A2L integration resolves any documentation label (CHARACTERISTIC, MEASUREMENT, AXIS_PTS) to its full ECU definition — memory address, record layout, conversion method, units, and live HEX value — directly from within the document or model view. You can also import an A2L file and convert it into a standalone EHANDBOOK container using the bundled build-ehb tool.

Next step

Bring your ECU documentation to life.

Give your calibration and validation teams a single, local-first explorer for documentation, models, and calibration data — part of the VehicleLab desktop suite alongside MDX. No license server, no data leaving the building.

Request a desktop build Talk to an engineer

By task

Where XHandbook is used.

Go deeper

Guides and comparisons for XHandbook.

Works with