DAMOS and A2L: how ECU data is described

Anyone getting into chip tuning sooner or later comes across the terms DAMOS and A2L. On forums they sometimes sound like a secret key: whoever has "the DAMOS" can supposedly do anything. Reality is more sober. Both terms refer to descriptions that ECU manufacturers use to make their own software understandable. They are a development tool, not a substitute for calibration experience. This article explains what's behind them without going into the details of their content.

The basic problem: data without labels

In an engine control unit's memory, program and data sit as a long sequence of numbers. They contain hundreds to thousands of parameters: single constants, curves and maps for injection, ignition, boost, torque limits, protection functions and diagnostics. The ECU itself knows where each value is and how to interpret it. For a person looking at the data, it's just numbers at first.

For engineers to work with this data, they need a description: what does each value mean, in which unit, with which axes? That's exactly what A2L and DAMOS provide.

A2L: the ASAM standard

A2L is the file format of the ASAM MCD-2 MC standard, formerly called ASAP2. ASAM is an association in which car makers, suppliers and tool vendors define common standards for vehicle development. The idea: an ECU from manufacturer A should be workable with a measurement and calibration tool from manufacturer B without the two having to agree on every detail.

An A2L file is a text file. Put simply, it describes:

• which quantities exist in the ECU: measured values the ECU calculates while running, and parameters it uses as targets,
• how they are stored: data type, size, structure of a table,
• how to convert them: from the stored raw value into a physical quantity such as degrees, bar, newton metres or per cent,
• which axes belong to a curve or map.

The standard allows multi-dimensional tables and is continuously developed. The format is read by common measurement, calibration and development tools and can also be generated directly from development environments.

Measured values and parameters

One distinction that's fundamental in ECU development helps here:

• Measured values are values the ECU continuously calculates while running or takes from sensors: engine speed, air mass, lambda, boost, calculated torque. They change every millisecond and are recorded during development.
• Parameters are the targets the software works with: single constants, one-dimensional curves and multi-dimensional maps. They are fixed in memory and only changed during calibration.

Tuning changes parameters. Measured values are the result. They show whether a change works and whether the protection functions operate cleanly.

DAMOS: a term from the manufacturers' world

DAMOS isn't an ASAM standard but a term originating from the Bosch and ETAS world. It is used for data descriptions and data storage around ECU software. In the tuning scene, "DAMOS" has become a catch-all term for the manufacturer's description of a software version. It's often used almost synonymously with A2L.

As a customer, the distinction doesn't really matter. What matters is the shared principle: both describe what a particular software version contains and how to read it.

Why manufacturers need such descriptions

When an engine is developed, calibration engineers spend months adapting the software to engine, vehicle and emissions standard. They drive on test benches, in heat and cold, at altitude and towing trailers. All the while they measure what happens inside the ECU and adjust parameters to balance fuel consumption, emissions, driveability and durability.

Without a description, that would be impossible. The A2L ensures that the calibration tool displays the right values, in the right unit, with the right label. So it is first and foremost a working tool of series development. These documents are manufacturers' development documents and are not public.

A description applies to one software version

One point that's often overlooked: an A2L describes exactly one software version. If the manufacturer changes the software, the data layout can shift, new functions can be added and old ones removed. The description of another version then no longer fits as is.

That's the same reason a tuning file must always match the vehicle's exact software version. More in Same car, different software.

What a description can't do

As helpful as a data description is, it has clear limits:

• It says what a value means, not which value is right. The description explains that a table is, for example, a torque limit. How far you can raise it for a particular engine without overloading turbocharger, clutch or gearbox isn't written anywhere in it.
• It doesn't replace understanding the function. Parameters work together. Anyone who raises a limit without understanding the associated protection and monitoring functions quickly ends up in limp mode or, worse, disables protection meant to save the engine.
• It contains no calibration. A description is a map, not a destination.

That's why the statement "we have the DAMOS, so our tune is good" isn't a mark of quality. The quality of a modification comes from experience with the engine, careful calibration of the protection functions and honest limits.

How tuners work without a manufacturer description

For most software versions in the field, there's no description outside the manufacturer. Professional tuners then work with experience and careful analysis: they know the ECU families, know which functions an engine management system typically has and check every change for plausibility. In the end the result has to prove itself on the road: running cleanly, without fault codes and with active protection functions.

How the main map families are structured in principle is explained in Map optimisation: what are these 80+ maps?. How parameters interact in the torque model is described in The torque model.

Common questions from the workshop

Do I as a customer need a DAMOS or an A2L? No. What matters for you is that the modification matches your software version, is calibrated cleanly and the protection functions stay active.

Is a modification without a manufacturer description worse? Not automatically. Experience, careful work and healthy restraint at the limits are what count. A description makes the work easier; it doesn't guarantee a good result.

Does an A2L say how to write to the ECU? No. A data description explains the content of the data, not the route into the ECU. How ECUs are read and written in principle is covered in OBD, bench and boot compared.

Conclusion

DAMOS and A2L are descriptions that manufacturers use to make their ECUs' data readable. A2L is the open standard ASAM MCD-2 MC; DAMOS is a term from the Bosch and ETAS world that serves as a catch-all in the tuning scene. Both apply to exactly one software version, and both say what a value means, not which value is the right one. What makes a good tune is decided in the calibration. The configurator shows which options are possible for your car.