A calibration is the block of constants in an ECU's program memory that the control software reads but does not change while the engine runs. Bosch describes that memory as holding the program together with variant-specific data in three forms: individual values, characteristic curves and maps. Every curve or map is a short list of stored outputs plus one or two lists of axis breakpoints. The software finds where the current input sits between two breakpoints, interpolates linearly between the neighbouring cells, and holds the edge value when the input is beyond the end of the axis.
The stored numbers are raw integers. Their physical meaning (rpm, mg/stroke, degrees, per cent) exists only in a definition file that gives the address, data type, byte order, axis references and conversion rule for each object. Most mistakes in map editing come from one of those descriptive items being wrong, not from the arithmetic. The family-specific consequences are covered in ME7 map axes and torque-model consistency and EDC16 and EDC17 common tuning principles; the general mechanism is set out here.
Scalars, curves and maps
The ASAM MCD-2 MC standard (ASAP2, file extension A2L) is the description format used by manufacturer calibration tools, and its vocabulary is the most precise one available for these objects. The current release is 1.7.1, dated 30 January 2018.
| ASAM type | Common name | What is stored |
|---|---|---|
| VALUE | Scalar, constant, single value | One number with no axis: a threshold, a limit, a switch. |
| VAL_BLK | Value block | An array of numbers with no axis, indexed by position (for example per cylinder or per gear). |
| CURVE | Characteristic curve | One axis and one row of outputs. |
| MAP | Map | Two axes and a grid of outputs. |
| CUBOID, CUBE_4, CUBE_5 | Higher-dimension tables | Three to five axes. |
Axes and breakpoints
An axis is a list of breakpoints (ASAM calls them sample points) in ascending order of the input quantity. The AUTOSAR interpolation library requires the axis to be monotonic, because the search routine assumes it. ASAM distinguishes where the breakpoints live:
- Standard axis (STD_AXIS): belongs to one table and is stored with it.
- Common axis (COM_AXIS): stored once as a separate AXIS_PTS object, at its own address, and referenced by several curves or maps.
- Fixed axis (FIX_AXIS): not stored in ECU memory at all. The breakpoints are calculated, typically from an offset and a constant spacing, so they are fixed by the program and cannot be edited as data.
- Curve axis and rescale axis (CURVE_AXIS, RES_AXIS): shared axes that are themselves normalised through another curve or axis.
Two practical points follow. A table whose axis does not appear next to its data is not necessarily missing an axis: it may be shared or calculated. And editing a shared axis changes every table that references it. The AUTOSAR library makes the sharing explicit: one search routine returns an index and a ratio for the input on an axis, and that single result can be passed to any number of curve or map routines.
Interpolation
The AUTOSAR fixed-point interpolation specification defines the calculation used by software built on that standard. For a curve, the search finds the lower breakpoint index i and the ratio
ratio = (x − X[i]) / (X[i+1] − X[i])
and the result is V[i] + (V[i+1] − V[i]) × ratio. A map repeats this in both directions (bilinear interpolation): the two rows either side of the operating point are each interpolated along one axis, and the two results are interpolated along the other. The order makes no difference to the result.
Worked example (invented figures). A map has engine speed breakpoints 2000 and 3000 rpm and load breakpoints 40 and 60 per cent:
| 40 % | 60 % | |
|---|---|---|
| 2000 rpm | 10 | 14 |
| 3000 rpm | 12 | 20 |
At 2500 rpm and 45 per cent load the speed ratio is 0.5 and the load ratio is 0.25. Along the 2000 rpm row: 10 + (14 − 10) × 0.25 = 11. Along the 3000 rpm row: 12 + (20 − 12) × 0.25 = 14. Between the rows: 11 + (14 − 11) × 0.5 = 12.5. No cell contains 12.5, and all four cells contribute. Changing one cell therefore changes the output over the whole area between it and its neighbours, which is why a single raised cell produces a ramp and not a step.
Not every table is interpolated. The same specification defines "look-up" routines that return the stored value at the lower breakpoint without interpolating, and ASAM has a corresponding non-interpolating conversion table type. Whether a given table interpolates is a property of the program code that reads it and cannot be determined from the data alone.
In fixed-point software the result is also an integer in raw units. AUTOSAR specifies rounding towards zero for the ratio and intermediate results, so the interpolated output moves in the same steps as the stored data.
Clamping at the axis ends
The AUTOSAR specification states that an input below the first breakpoint uses the first value and an input above the last breakpoint uses the last value. There is no extrapolation: the output is flat beyond the axis. The MathWorks modelling guidelines used for production code generation require the same "clip" setting, on the grounds that extrapolating from an unexpected input can produce an impossible value or an overflow.
This matters when an engine is operated beyond the range the original calibration covered:
- If the last load breakpoint is 180 and the engine reaches 200, the table returns the 180 column. A higher value typed into a notional "200" position does nothing unless the axis itself reaches 200.
- Rescaling an axis without touching the cells moves every existing value to a different operating point. If the last three breakpoints 100, 140, 180 become 100, 160, 220, the value that applied at 140 now applies at 160 and the output at 140 becomes an interpolation between the 100 and 160 cells. The table must be re-derived for the new breakpoints, and so must every other table that shares the axis.
- The number of breakpoints is limited (an A2L axis description records the maximum). Extending the range spreads the same points more thinly and reduces resolution elsewhere.
- An axis can only reach as far as its raw data type and the input signal allow. An 8-bit axis scaled at 0.75 per count ends at 191.25 whatever the editor displays; see ME7 high load representation and map tracing.
Raw values and physical values
Each object has a record layout (data type, byte order, position in memory) and a conversion method. ASAM's common conversion methods are identity, a linear function with a slope and an offset, a six-coefficient rational function, interpolating and non-interpolating tables, and text tables for enumerations. In editor terms the linear case is physical = raw × factor + offset. ASAM notes one trap: most methods are written from the internal value to the physical value, but the rational function is defined in the opposite direction, from physical to internal.
Three properties of the raw number must be right before the factor means anything:
- Width. ASAM data types are 8, 16, 32 or 64 bits, plus IEEE floating point. An unsigned 8-bit cell holds 0 to 255 and an unsigned 16-bit cell 0 to 65535.
- Signedness. Signed integers are conventionally two's complement. The byte 0xF6 is 246 if unsigned and −10 if signed, so a signed correction table read as unsigned shows large positive values where small negative ones are stored.
- Byte order. The bytes 0x12 0x34 are 4660 if the most significant byte is first and 13330 if the least significant byte is first. A map read with the wrong byte order looks like noise.
Width and factor together set the resolution and the ceiling. With a factor of 0.75 an 8-bit cell can only hold multiples of 0.75 up to 191.25; a requested value of 100.3 is stored as 100.5 or 99.75. A value at the top of its raw range cannot be raised by editing data, only by a change to the program or the conversion.
Percentage edits behave differently on raw and physical values when the offset is not zero. With physical = 0.1 × raw − 10, raising raw 500 by 10 per cent gives a physical 45, whereas 10 per cent on the physical value of 40 is 44. The example is worked in the EDC16 and EDC17 principles page.
Definition formats
The binary contains only the raw data. EVC, the publisher of WinOLS, puts it this way for manufacturer description files: they carry the map names, addresses, scaling, sample points and labels, and the EPROM holds only the contents.
- A2L (ASAP2) and DAMOS are the manufacturer-side formats. An A2L file is structured text describing every calibration and measurement object for one software build. EVC states that the two formats are used by almost all German vehicle manufacturers and that a single file can describe 2,000 to 10,000 maps. EVC also states that it does not supply such files; their availability outside manufacturers is limited.
- XDF is the definition format of the free editor TunerPro, which requires a definition matching the ECU and supports scaling expressions for tables, scalars and axes. XDF files are usually community-written and cover a selection of maps.
- Map packs are tool-specific collections of map definitions for one software version, produced by third parties for editors such as WinOLS. Their accuracy is that of their author; an example of how they circulate is on the Sagem S2000 and S3000 files page.
A definition applies to one software version. Addresses in an A2L file are ECU memory addresses and generally differ from file offsets by a constant; EVC's guidance is that if no offset makes the description line up with the maps in the file, the two do not match and cannot be used together. Selecting and checking a definition is covered in Choosing ECU definition files, and the place of this step in the overall process in How an ECU is remapped. An edited calibration also needs its integrity checks recalculated before it is written; see ECU checksums and why they are corrected.
Not established
- The interpolation and clamping rules cited are those of the AUTOSAR Classic Platform library and of standard code-generation practice. ECU families that predate AUTOSAR, such as Bosch ME7 and EDC15/16, are consistently treated as behaving the same way in tuning literature, but no manufacturer document confirming it for those families has been identified. Boundary behaviour should be confirmed for the specific function.
- No primary specification for the XDF or map-pack formats has been identified; the descriptions above rest on vendor product pages.
Sources
- ASAM MCD-2 MC wiki, ASAM e.V., undated. Characteristic types, axis types, record layouts, conversion methods and data types. Accessed 2026-11-19.
- ASAM MCD-2 MC standard page, ASAM e.V., version 1.7.1, 30 January 2018. Scope of the A2L description and current release. Accessed 2026-11-19.
- Specification of Fixed Point Interpolation Routines, AUTOSAR, document 396, Classic Platform R22-11, 24 November 2022. Data point search, curve and map interpolation formulae, look-up variants, end-value behaviour (SWS_Ifx_00820), axis monotony and rounding. Accessed 2026-11-19.
- jc_0626: Usage of Lookup Table blocks, MathWorks modelling guidelines, undated. Requirement to clip instead of extrapolating, and its rationale. Accessed 2026-11-19.
- Electronic Diesel Control (EDC), Robert Bosch GmbH, 2001, independent PDF mirror, printed page 40. Program memory holding the program with individual data, characteristic curves and maps. Accessed 2026-11-19.
- Bilinear interpolation, Wikipedia, undated. Two-step linear interpolation and independence from the order of the steps. Accessed 2026-11-19.
- WinOLS option OLS521: DAMOS/A2L import, EVC electronic GmbH, undated. Vendor description of what DAMOS and A2L files contain, who uses them and their size. Accessed 2026-11-19.
- How do I find the offset for my Damos/A2L file?, EVC electronic GmbH FAQ, undated. Address offset between description and file, and the conclusion when none fits. Accessed 2026-11-19.
- TunerPro, Mark Mansur, undated. XDF definition requirement and scaling expressions for tables, scalars and axes. Accessed 2026-11-19.