Damos, Mappacks & A2L Files: The Key to Professional Tuning

The Three Pillars of Professional Map Identification

When you open a raw ECU binary file in a hex editor, you see thousands of bytes of data with no labels, no descriptions, and no obvious structure. Identifying which bytes correspond to which engine maps — and what those maps do — is one of the core skills of ECU tuning.

Three types of definition files make this process dramatically easier: Damos files, Mappacks, and A2L files. Understanding the differences between them is essential for efficient tuning work.

Damos Files — The Full Picture

What They Are

A Damos (short for Daten und Meßordnungssystem — Data and Measurement Organisation System) is a complete ECU description file created by Bosch during the ECU development process. It contains the full engineering documentation for every parameter, map, constant, and measurement value in the ECU software.

Damos files are OEM development documents — they were never intended for public distribution. They originate from the ECU manufacturer’s (Bosch, Siemens, etc.) development environment and contain the kind of information that engineers use during calibration development.

What They Contain

A complete Damos file includes:

• Map definitions: Name, description, address in flash memory, data type, scaling factors
• Axis definitions: X and Y axis labels, units, breakpoints, scaling
• Physical units: Nm, bar, °C, mg/stroke, °BTDC — what the raw hex values actually represent in engineering terms
• Parameter descriptions: German-language descriptions of what each map does
• Constants and scalars: Single-value parameters (not just multi-dimensional maps)
• Measurement definitions: Live data channels for datalogging, with addresses, scaling, and descriptions
• Function groups: Maps organised by functional area (boost control, injection, torque model, etc.)

Why Damos Files Are Valuable

With a Damos file loaded into WinOLS, every map in the ECU is automatically identified, labelled, and displayed with correct units. Instead of looking at a hex dump and guessing which bytes represent boost pressure, you see a map titled “LDRXN — Requested boost pressure normalized” with axes labelled in RPM and relative charge, and values displayed in mbar.

This transforms the tuning process from guesswork to engineering.

Limitations

• Software version specific: A Damos file is created for a specific software version. If the ECU has been updated by the dealer (new software version), the map addresses may have shifted, and the Damos no longer matches exactly.
• Availability: Damos files are proprietary. They’re not freely available — they’re obtained through various channels and traded within the tuning community.
• Format: Damos files come in several formats (.damos, .kp, .dcm) depending on the development tool used to create them.

Mappacks — Tuning-Focused Definitions

What They Are

A mappack (also called a map pack or WinOLS map pack) is a simplified version of a Damos file, containing only the maps relevant for tuning. It’s designed specifically for use with WinOLS and strips away the engineering detail that tuners don’t need.

What They Contain

• Map addresses: Where each tuning-relevant map starts in the binary file
• Map dimensions: Size of the map (rows × columns)
• Axis definitions: Basic axis labelling and breakpoints
• Map names: Descriptive names (often in English, unlike Damos which use German abbreviations)
• Data type: 8-bit, 16-bit, signed/unsigned

What They Don’t Contain

• Measurement definitions: No live data channel information
• Full descriptions: Less documentation than a Damos file
• Complete parameter set: Only tuning-relevant maps, not engineering/diagnostic parameters
• Physical unit scaling: May or may not include unit conversion formulas

Advantages of Mappacks

• More widely available: Mappacks are more commonly shared and sold than full Damos files
• Curated for tuning: Only the maps you actually need to modify are included, reducing clutter
• WinOLS native format: Import directly into WinOLS with one click
• Often version-flexible: Some mappacks work across multiple software versions of the same ECU variant (though addresses may need minor adjustment)

Sources

Mappacks are available from:

• WinOLS community forums
• Commercial map pack providers (EVC, various forum sellers)
• Created manually by experienced tuners who identify maps through analysis

A2L Files — The Industry Standard

What They Are

An A2L file is a standardised ECU description file defined by the ASAM MCD-2MC (Association for Standardisation of Automation and Measuring Systems) standard. It serves a similar purpose to a Damos file but uses an open, documented format.

A2L is the automotive industry standard for ECU calibration and measurement. Tools like INCA (Bosch), CANape (Vector), and ATI Vision all use A2L files as their primary ECU description format.

What They Contain

A2L files contain essentially the same information as Damos files, but in a standardised format:

• CHARACTERISTIC blocks: Define maps, curves, and constants with addresses, dimensions, data types, and conversion formulas
• MEASUREMENT blocks: Define live data channels for datalogging
• COMPU_METHOD: Conversion methods between raw hex values and physical units
• AXIS_DESCR: Axis definitions including breakpoints and units
• MODULE: Organises parameters into functional groups
• MOD_PAR: Module parameters including memory layout information

Key Differences from Damos

Using A2L Files

WinOLS can import A2L files and use them in the same way as Damos files — maps are automatically identified, labelled, and scaled. Some tuners prefer A2L files because the English descriptions are more accessible than the German abbreviations in Damos files.

How to Use These Files in WinOLS

Importing a Damos or Mappack

1. Open your ECU binary file in WinOLS
2. Go to File → Import → Map Pack / Damos
3. Select the definition file that matches your ECU variant
4. WinOLS will identify and label all defined maps in your binary
5. Navigate maps using the map list panel — they’re now organised by name and function

Importing an A2L File

1. Open your ECU binary file in WinOLS
2. Go to File → Import → A2L
3. Select the A2L file for your ECU variant
4. WinOLS processes the A2L and creates map definitions
5. Maps appear with their full descriptions and physical units

What If You Don’t Have Any Definition Files?

If no Damos, mappack, or A2L file exists for your specific ECU variant, you’ll need to find maps manually. This involves:

• Comparing original and tuned files to identify modified areas
• Using WinOLS’s 2D/3D view to identify map-like structures in the hex data
• Recognising common patterns (axis lengths, data types, typical value ranges)
• Using Damos from a similar ECU variant as a starting point and adjusting addresses

For more on this technique, see our guide on how to find maps in WinOLS.

Practical Recommendations

1. Always try to find a Damos or A2L first. The time investment in searching is far less than manually identifying maps.
2. A mappack is better than nothing. Even a partial mappack saves significant time.
3. Verify the definition file matches your software version. Load it and spot-check a few maps — do the axis values look reasonable? Do the map values make engineering sense?
4. Build your own collection. Over time, accumulate Damos/A2L files for the ECU types you commonly work with.
5. Use file services for unfamiliar ECUs. If you don’t have definition files for an ECU and can’t find them, using a professional file service is more efficient than spending hours on manual map identification.

Where to Find Definition Files

• WinOLS community: The WinOLS user community shares mappacks for many ECU types
• Tuning forums: ECUEdit, MHH Auto, Digital Kaos, and others have map pack sections
• Commercial providers: Some companies sell comprehensive map pack collections
• Nefmoto: For ME7 specifically, Nefmoto has the most complete Damos collection available