ETAS INCA - Complete Walkthrough - Calibration & XCP Protocol

INCA Workspace Architecture: Three-Layer Hierarchy

INCA Project Hierarchy

  Workspace (.wsp)
  └── Experiment (.exp)
      ├── Hardware interface (ES592 USB-CAN, bit-rate 500kbps)
      ├── ECU Description (A2L file reference)
      │     ECU_Engine_v2.3.a2l
      └── Active Dataset (calibration parameter values)
            idle_v3_validated.cdf

  Rule: one Experiment per ECU software build.
  Changing software version (new ECU_ADDRESS assignments)?
  → Create new Experiment referencing new A2L.
  → Do NOT reuse old Experiment with new A2L — addresses may have shifted.

INCA Object	File Extension	Purpose
Database	`.db`	Stores A2L files + all calibration datasets for a project
Experiment	`.exp`	Links hardware interface + A2L + active dataset
Dataset	`.cdf`	A set of CHARACTERISTIC values — one per calibration variant
Recording	`.mf4`	MDF4 time-series measurement file from DAQ sessions
Workspace	`.wsp`	Collection of experiments for a project

Hardware Configuration: ES592 to XCP

Pythoninca_hw_config.py

# INCA COM API: configure hardware and verify XCP connection
import inca_com as inca

# Open INCA application (must already be running)
app = inca.GetApplication()

# Add ES592 USB-CAN interface
hw_catalog = app.GetHardwareCatalog()
es592 = hw_catalog.AddDevice("ES592")
es592.SetChannel(channel=1, baudrate=500000)
es592.SetXcpMasterId(0x600)
es592.SetXcpSlaveId(0x601)

# Assign A2L to hardware device
exp = app.GetCurrentExperiment()
exp.SetEcuDescription("C:/Projects/ECU_Engine/ECU_Engine_v2.3.a2l")
exp.SetHardwareInterface(es592)

# Test connection
result = exp.TestConnection()
if result.status == "CONNECT_OK":
    print(f"XCP connected: MAX_CTO={result.max_cto}, MAX_DTO={result.max_dto}")
else:
    print(f"Connection failed: {result.error_code} — {result.error_description}")
    # Common: 0x29 = ACCESS_LOCKED → load seed/key plugin

MDA: Measurement Data Analyzer Post-Processing

Pythoninca_mda_analysis.py

# INCA MDA: post-process .mf4 recording
import mdf4reader as mdf
import numpy as np, matplotlib.pyplot as plt

rec = mdf.load("bench_run_wltp_001.mf4")

# Load channels
rpm    = rec.get("engine_rpm")
lambda_= rec.get("lambda_actual")
hc_ppm = rec.get("HC_concentration_ppm")
time   = rpm.timestamps

# Find operating points: warm engine (coolant > 70C), RPM 1500-3000
coolant = rec.get("coolant_temp_degC").samples
warm_mask = (coolant > 70) & (rpm.samples > 1500) & (rpm.samples < 3000)

print(f"Warm operating window: {np.sum(warm_mask)/len(warm_mask)*100:.1f}% of recording")
print(f"Mean lambda in window: {np.mean(lambda_.samples[warm_mask]):.3f}")
print(f"Max HC in window: {np.max(hc_ppm.samples[warm_mask]):.0f} ppm")

# Plot lambda over time
plt.figure(figsize=(12, 4))
plt.plot(time, lambda_.samples, 'b-', linewidth=0.5, label='lambda_actual')
plt.axhline(1.0, color='r', linestyle='--', label='stoichiometric')
plt.xlabel('Time (s)'); plt.ylabel('Lambda')
plt.title('Lambda trace — WLTP cycle run 001')
plt.legend(); plt.tight_layout()
plt.savefig("lambda_wltp_001.png", dpi=150)

Dataset Management: Baseline, Variants, Diff

Dataset Operation	INCA Action	Purpose
Create baseline	Dataset → New → name it 'idle_baseline_v1'	Snapshot reference before any changes
Branch variant	Dataset → Clone → name 'idle_euro6_market'	Inherit all baseline values; modify only relevant parameters
Diff view	Dataset → Compare → select two datasets	Highlights only changed parameters — review before sign-off
Export	Dataset → Export → DCM / CDF / MCD-2 MC	Share with OEM, CDM system, or flash tool
Import from ECU	Device → Upload All from ECU → Save as dataset	Capture current ECU state as a new dataset

Shellinca_dataset_diff.sh

# INCA command-line dataset comparison (headless)
inca_cli.exe compare_datasets     --baseline  "idle_v2_released.cdf"     --new       "idle_v3_candidate.cdf"     --a2l       "ECU_Engine_v2.3.a2l"     --output    "dataset_diff_v2_vs_v3.xlsx"

# Output shows: parameter name | old value | new value | unit | delta
# Used by: calibration lead review, emissions engineer sign-off, safety engineer approval

Summary

INCA's three-layer architecture (Workspace → Experiment → Dataset) separates hardware, ECU description, and calibration data concerns. Always create a new Experiment when the ECU software build changes — reusing an old Experiment with a new A2L risks writing parameters to wrong addresses if the linker has moved symbols. The MDA post-processor and dataset diff view are the two most-used INCA features after the calibration editor itself.

🔬 Deep Dive — Core Concepts Expanded

This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.

Key principles to reinforce:

Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.

🏭 How This Topic Appears in Production Projects

Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.

⚠️ Common Mistakes and How to Avoid Them

Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.

📊 Industry Note

Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.