An INCAZ experiment is the reusable measurement/calibration workspace for a project. It records layout and operational choices so a user can return to the same engineering view instead of rebuilding windows and signal lists every session.
Layers
An experiment can contain multiple layers, shown as tabs. Create a layer with Ctrl+T. Each layer can hold its own Measure Tables, oscilloscopes, and calibration editors. This is useful for separating a system into meaningful views—for example powertrain, thermal, diagnostics, or a specific calibration task.
Measurement covers every layer
Layers organise the GUI; they do not isolate acquisition. When measurement starts, INCAZ collects variables used across all layers. Plan raster assignments and signal counts with the complete experiment in mind, especially when a hidden layer contains fast DAQ signals.
Save the workspace
Use Ctrl+S to save the experiment. The database stores the layer structure, MDI window geometry, signal lists, and raster assignments. Use an experiment name that identifies the ECU release, purpose, and test condition.
MF4 recording
Press F12 to start recording measurement data to an MF4 file. INCAZ writes ASAM MDF 4.10 using asammdf. One acquisition group is stored for each DAQ list/raster or polling group, preserving the different sample grids instead of forcing unrelated signals onto one artificial time base.
What a recording contains
- Physical numeric samples where available.
- Timestamp arrays aligned to the acquisition group.
- Signal name, unit, and A2L-derived comment metadata.
- Recording start time and an automatically unique filename when a name already exists.
Recording workflow
- Build a small, intentional experiment and choose rasters.
- Start measurement; verify live values and status rate.
- Start MF4 recording with F12 or the Measurement menu.
- Perform the manoeuvre/test sequence.
- Stop recording and confirm the saved MF4 path in the log.
- Archive the recording together with the A2L/HEX/ECU version and test notes.
Recording quality tips
- Use DAQ for signals whose ECU timing matters.
- Do not mix builds: record with the A2L that matches the ECU.
- Capture a small set of context signals alongside the primary signals, such as state, enable, temperature, and fault status.
- Document changes to calibration, hardware, and target software around each recording.
- Check disk space and recording directory before long or high-rate tests.