03 — Database, A2L Projects, and HEX Data Sets

INCAZ uses an INCA-style folder database. A database is a directory ending in .incazdb, containing an SQLite index and copies of imported project files. This gives each calibration effort a clear home for projects, data sets, hardware configuration, experiments, and saved ProF flash configurations.

Data model

Database (.incazdb)
  └── Project (imported A2L)
        ├── Dataset (imported Intel HEX)
        ├── Experiment (layers, windows, signals, rasters)
        ├── Hardware configuration (XCP transport/options)
        └── ProF flash configurations

Create a project

Create or open a database from the Database menu.
Choose Project → Import A2L….
Select the ECU A2L. INCAZ copies it into the database and builds an in-memory project model.
Review measurements, characteristics, axes, groups/functions, conversions, memory segments, XCP transport fields, and DAQ events in the Variables browser.

Add a data set

Right-click the project in the Database tree and choose Add dataset (HEX)…. A HEX data set is used for offline characteristic editing and as the source image for flashing. INCAZ copies the HEX into the database, preserving a self-contained project folder.

What INCAZ reads from A2L

Area	Why it matters
MEASUREMENT	Address, type, unit, limits, conversion, and access information for live acquisition.
CHARACTERISTIC / AXIS_PTS	Scalar, array, curve, map, ASCII, and axis definitions used by calibration editors.
COMPU_METHOD	Raw-to-physical conversion, including identical, linear, rational, table, verbal, and formula-based forms.
RECORD_LAYOUT	How characteristic values, dimensions, and axes are laid out in memory.
IF_DATA XCP	Suggested Ethernet transport settings and DAQ event channels when declared by the ECU.

Offline versus online work

With only a project and HEX data set, calibration writes modify the selected offline memory image. When connected to hardware, the same editor writes to the ECU working page through XCP. Keep this distinction clear in the experiment name and in operator procedure: offline edits change the data set on disk; online edits change live target memory until page/persistence actions are applied by the target workflow.

Good database practice

Create one database per ECU family, release, or controlled test campaign.
Use names that include software/EPK or release identifiers where available.
Import the exact A2L and HEX pair used by the target; do not mix files from unrelated builds.
Save experiments after choosing rasters and windows, so a measurement layout can be reproduced.
Back up the complete .incazdb folder before major calibration or flashing work.