Parameters, Maps & Curves - Calibration & XCP Protocol

Scalar CHARACTERISTIC: Single Value Parameter

Cscalar_cal.c

/* Scalar: one value at one fixed ECU address */
/* A2L type: VALUE */
volatile uint16 IDLE_RPM_TARGET __attribute__((section(".cal_data"))) = 800u;
volatile float32 LAMBDA_TARGET  __attribute__((section(".cal_data"))) = 1.0f;
volatile int8   IGN_TIMING_OFFSET __attribute__((section(".cal_data"))) = 0;

A2Lscalar.a2l

/begin CHARACTERISTIC
  IDLE_RPM_TARGET       /* name — must match linker symbol */
  "Target idle speed"   /* long identifier */
  VALUE                 /* type: scalar */
  0x20001000            /* ECU_ADDRESS from linker map */
  _UWORD_Z              /* RECORD_LAYOUT: unsigned 16-bit scalar */
  0.0                   /* max_diff (unused for VALUE) */
  CM_RPM                /* COMPU_METHOD reference */
  500.0                 /* LOWER_LIMIT */
  1200.0                /* UPPER_LIMIT */
/end CHARACTERISTIC

Curve: 1D Lookup Table

Ccurve_cal.c

/* Curve: array of Y values + separate axis array */
/* A2L type: CURVE */
#define THROTTLE_CURVE_SIZE 16

/* Axis breakpoints (X values) — stored separately, also calibratable */
volatile uint8 throttle_axis[THROTTLE_CURVE_SIZE]
    __attribute__((section(".cal_data"))) =
    {0, 7, 13, 20, 27, 33, 40, 47, 53, 60, 67, 73, 80, 87, 93, 100};

/* Y values indexed by throttle_axis */
volatile uint16 throttle_torque[THROTTLE_CURVE_SIZE]
    __attribute__((section(".cal_data"))) =
    {0, 22, 50, 85, 125, 168, 212, 256, 292, 325, 352, 370, 385, 393, 398, 400};

/* ECU lookup (with linear interpolation between breakpoints) */
uint16 Get_TorqueDemand(uint8 throttle_pct) {
    return Interp_1D(throttle_torque, throttle_axis, THROTTLE_CURVE_SIZE, throttle_pct);
}

Map: 2D Lookup Table

A2Lmap.a2l

/begin CHARACTERISTIC
  ign_timing_MAP
  "Ignition timing advance vs RPM and load"
  MAP                      /* 2D table */
  0x20002000               /* ECU_ADDRESS: start of 2D array in RAM */
  _SWORD_X_UWORD_Y_SWORD_Z /* RECORD_LAYOUT: int16 values, uint16 axes */
  0.0
  CM_DEG_CRANK
  -20.0                    /* LOWER_LIMIT: -20 degrees BTDC */
  45.0                     /* UPPER_LIMIT: 45 degrees BTDC */
  /begin AXIS_DESCR
    STD_AXIS                 /* standard axis type */
    engine_rpm_MEASUREMENT   /* input variable (MEASUREMENT reference) */
    CM_RPM                   /* conversion for axis display */
    16                       /* number of axis points */
    800.0                    /* lower axis limit */
    6500.0                   /* upper axis limit */
  /end AXIS_DESCR
  /begin AXIS_DESCR
    STD_AXIS
    engine_load_MEASUREMENT
    CM_PERCENT
    16
    10.0
    100.0
  /end AXIS_DESCR
/end CHARACTERISTIC

Map Dimension	Array Size	ROM Cost (uint16)	Interpolation Points per Lookup
8×8	64 cells	128 bytes	4 (bilinear)
16×16	256 cells	512 bytes	4 (bilinear)
32×32	1024 cells	2048 bytes	4 (bilinear)
32×64	2048 cells	4096 bytes	4 (bilinear)

Bilinear Interpolation in Map Lookups

Bilinear Interpolation in a 2D Map

  RPM axis:  ...  2000   3000  ...
  Load axis:
      40%   →   8°     12°
      60%   →  15°     20°

  Query: RPM=2500, Load=50%
  Step 1: interpolate along RPM axis at Load=40%:  8 + (12-8) × 0.5 = 10°
  Step 2: interpolate along RPM axis at Load=60%: 15 + (20-15) × 0.5 = 17.5°
  Step 3: interpolate along Load axis:            10 + (17.5-10) × 0.5 = 13.75°
  Result: ign_timing = 13.75° BTDC

⚠️ Axis Resolution vs ROM Trade-off

Doubling axis resolution from 16 to 32 points quadruples map size (16×16 = 256 cells vs 32×32 = 1024 cells). Finer resolution reduces interpolation error but costs Flash. The engineering decision is: how much interpolation error is acceptable for this parameter? For ignition timing, ±0.5° is typical tolerance — check whether a 16×16 axis covers the operating space sufficiently before requesting a 32×32 map.

Summary

Scalars, curves, and maps are the three fundamental calibration parameter types. Each is described in the A2L file with an ECU_ADDRESS matching the exact linker symbol address, a RECORD_LAYOUT defining the memory layout, and LOWER/UPPER limits enforcing safe ranges. The ECU uses bilinear interpolation between map cells at runtime — axis resolution directly determines interpolation accuracy and Flash cost.

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