Mappack WinOLS and XDF for professional tuning

What is a mappack and what is it used for?

A mappack is a set of definition files that lets a calibration engineer view and modify the internal maps of a specific ECU. Without a mappack, an ECU binary is an opaque sequence of bytes — you don't know which maps it contains, where they are or what units they use. With a mappack, the file becomes a collection of organised, named tables with the correct units, ready to work on.

Formats we supply

• DAMOS (.dam, .damos): native WinOLS format, common for Bosch EDC/MED/MG/MD families.
• A2L (.a2l): ASAM standard format used by OEM and professional tools (INCA, CANape, ATI Vision). It can be converted to other formats.
• OLS (.ols): complete WinOLS project already organized with folders and annotations.
• XDF (.xdf): TunerPro format, widely used in the US community and for Denso, Delphi and some Bosch families.
• Original BIN: we include the original binary the mappack is built on, for verification.

What each mappack includes

Depending on the ECU family and the availability of OEM data:

• Main injection maps (duration, rail pressure, post-injections).
• Ignition advance maps (petrol) / injection timing maps (diesel).
• Turbo maps (boost target, wastegate/VNT duty cycle).
• Target lambda and enrichment maps.
• Torque limiters, RPM limiters, speed limiters.
• Electronic throttle maps (pedal map).
• EGR, DPF, AdBlue/SCR strategy.
• Multi-map configuration where applicable.
• OBD diagnostic tables.
• Checksum location and calculation method.

Who is this service for?

Mappacks are a working tool for professional workshops and file service companies who do their own calibration. If you are the one calibrating files for other workshops, you need accurate mappacks. If your workshop prefers to send us the files and get the modified ones back, this service isn't for you — what you need is Stage 1 or similar services.

ECU family compatibility

What information we need

• Original binary file read from the reference vehicle.
• Make, model, year, engine and exact software version.
• Requested formats (DAMOS, A2L, XDF — more than one can be requested).
• Whether the mappack will be used on a single vehicle or on a range of similar vehicles.

Typical use cases

• Workshop setting up its own tuning service and needs mappacks for its most common ECU (example: 2.0 TDI EDC17CP44).
• File service company which expands coverage to new families.
• Freelance calibration engineer who works for several file services and needs up-to-date definitions.
• R&D centre for specific builds that need proprietary calibration.
• Motorsport workshop with its own calibration for customers' cars.

If you need the reference factory file to start a project, see original software restoration. To add specific changes later and make them permanent, see DTC management and adaptations.

Service terms

Mappacks are supplied under license for internal use by the requesting workshop. They may not be redistributed or sold to third parties. Each mappack is delivered with a unique workshop identifier for traceability. The price, in MYC, depends on the complexity and coverage of the requested ECU family.