Hands-On: First Calibration Session - Calibration & XCP Protocol

Setup: Connect ETAS INCA to Bench ECU

Step	INCA Action	Expected Result
1. New experiment	File → New Experiment → select A2L file	A2L loads; signals appear in variable browser
2. Hardware config	Hardware → Hardware Configuration → Add ES592 USB-CAN	ES592 appears; assign CAN channel + bit-rate 500 kbps
3. XCP IDs	Edit XCP channel → CAN ID Master 0x600, Slave 0x601	Matches A2L IF_DATA XCP_ON_CAN section
4. Connect	Device → Connect (F5)	CONNECT response 0xFF in XCP monitor; status: CALIBRATION PROCESSOR READY
5. Verify	XCP Monitor → GET_STATUS	Response shows CAL_PAGE_MODE, SEGMENT_INFO available

Hexxcp_connect_trace.txt

/* INCA XCP monitor — successful connection sequence */
Master→ECU: FE 00 00 00 00 00 00 00   /* CMD=0xFE CONNECT, mode=0x00 (normal) */
ECU→Master: FF 00 00 00 01 01 08 08   /* Positive response:
                                          byte4: COMM_MODE_BASIC (block transfer available)
                                          byte5: MAX_CTO = 8 bytes
                                          byte6: MAX_DTO = 8 bytes
                                          byte7: XCP protocol version 1.0 */

Master→ECU: FB 00 00 00 00 00 00 00   /* CMD=0xFB GET_STATUS */
ECU→Master: FF 00 00 00 00 00 00 00   /* session_status: DAQ+CAL processor ready */

Building a Measurement List in INCA

Pythoninca_measurement_setup.py

# INCA COM API equivalent — automate measurement list creation
import inca_com as inca

inca.Connect("ECU_Engine_v2.3.a2l", channel="ES592_CAN1")

# Add MEASUREMENT signals to DAQ list
inca.AddMeasurement("engine_rpm",      event="event_10ms",  unit="rpm")
inca.AddMeasurement("coolant_temp",    event="event_100ms", unit="degC")
inca.AddMeasurement("lambda_actual",   event="event_10ms",  unit="")
inca.AddMeasurement("boost_pressure",  event="event_10ms",  unit="mbar")
inca.AddMeasurement("injection_pw_us", event="event_10ms",  unit="us")

# Start DAQ recording
inca.StartRecording(filename="bench_run_001.mf4")
inca.StartMeasurement()
# ... test execution ...
inca.StopMeasurement()
inca.StopRecording()

Modify IDLE_RPM_TARGET and Observe Response

Pythoninca_cal_change.py

import inca_com as inca

# Read current value (XCP UPLOAD)
current = inca.GetCharacteristic("IDLE_RPM_TARGET")
print(f"Current IDLE_RPM_TARGET = {current} rpm")  # → 800 rpm

# Write new value (XCP DOWNLOAD to RAM working page)
inca.SetCharacteristic("IDLE_RPM_TARGET", 850.0)

# Verify write (XCP UPLOAD readback)
verified = inca.GetCharacteristic("IDLE_RPM_TARGET")
assert verified == 850.0, f"Write failed! Got {verified}"

# Observe: measure actual_idle_speed MEASUREMENT
# ECU PID controller will bring idle to 850 rpm within ~500ms
import time; time.sleep(2.0)
actual = inca.GetMeasurement("actual_idle_speed")
print(f"Actual idle speed = {actual:.0f} rpm")  # → ~850 rpm

💡 PID Settling Time

After writing a new setpoint, wait for the ECU's PID controller to settle before evaluating the result. An idle speed controller typically has a settling time of 0.5–3 seconds depending on integral gain. Evaluate steady-state measurements only — transient overshoot is not a calibration issue.

Session Close: RAM-Only Change Demonstration

Pythonsession_close_demo.py

import inca_com as inca

# During session: IDLE_RPM_TARGET was set to 850 in RAM
print(inca.GetCharacteristic("IDLE_RPM_TARGET"))  # → 850

# Close session WITHOUT COPY_CAL_PAGE
inca.Disconnect()

# Power-cycle ECU (reset)
bench_power_cycle()  # ECU reloads Flash reference

# Reconnect and read
inca.Connect("ECU_Engine_v2.3.a2l", channel="ES592_CAN1")
print(inca.GetCharacteristic("IDLE_RPM_TARGET"))  # → 800 (original!)
# RAM working page was re-initialised from Flash reference on reset

# To persist the change:
# inca.CopyCalPage(source=WORKING, dest=REFERENCE)
# Then disconnect — ECU reloads 850 on next start

Summary

A first calibration session validates the entire toolchain in order: hardware connection (XCP CONNECT), A2L address correctness (verified by UPLOAD readback), parameter writability (DOWNLOAD + UPLOAD verify), and ECU response (MEASUREMENT tracking the new setpoint). The RAM-only nature of working-page writes is the key insight: always issue COPY_CAL_PAGE before resetting the ECU when results need to be retained.

🔬 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.