MAP DEFINITIONS FOR WORKSHOPS & TUNERS

Your original file.WinOLS MapPack & DAMOS.Created automatically.

MapPacks and DAMOS for your software version. Upload your BIN or ORI, review the included maps and receive a CSV for WinOLS.

ECU / MAP DEFINITIONSDEFINITIONS, NOT TUNING VALUES
No registrationPreview before purchaseDownload after paymentFiles deleted after 14 days
ECU MAPPACK / ACTIVITYExample data
BMWMG1CS003/generated 6 min ago in GeorgiaVolkswagenEDC17C74/generated 3 min ago in AustriaAudiMD1CP004/generated 16 min ago in GermanyVolkswagenEDC17C64/generated 12 min ago in Great BritainAudiMG1CS008/generated 21 min ago in Poland
01 / HOW IT WORKS

From BIN to MapPack.

  1. Upload your original file

    Upload a complete, unencrypted original read from your ECU.

  2. Review the preview

    Check which maps are included and choose a MapPack, DAMOS or both.

  3. Pay & download

    Pay without an account. Once payment is confirmed, receive your download and invoice by email.

02 / WHAT YOU RECEIVE

Two scopes. One solid starting point.

Map definitions as a CSV for WinOLS. No modified calibration values. This is not a tuning file. Need a finished Stage 1 or Stage 2 file? Find that service at ECU-Tuningfiles.com.

MAP DEFINITIONS

MapPack

Relevant maps for your calibration work in WinOLS, with clear names and folders organised by function.

  • German map names and folders by default
  • Optional English names with the exact same selection
  • Definitions only, no calibration values
Example scope779 maps
01 | Driver wish and torque
Driver wish 0116 × 12
Torque limiter 0116 × 12
Torque model 0116 × 16

Illustrative names and scope. The actual scope depends on your file.

ORIGINAL NAMES

DAMOS

DAMOS usually contains significantly more maps than a MapPack, covering additional functions while retaining the original names.

  • A broader set of identified definitions
  • Original names and folders
  • Review the actual scope before purchase
Example scope51,325 maps
Original names · multiple function groups
AccPed_trqDes16 × 12
TrqLim_nEng16 × 12
TrqMdl_rAir16 × 16
PCR_pDesVal16 × 12
Rail_pSet16 × 16
InjCrv_tiBas20 × 16

Illustrative names and scope. The actual scope depends on your file.

Import the CSV into WinOLS

Open a WinOLS project using the same original BIN. Use the map description / CSV import, select the supplied file and check the native column mapping in the import dialog. Then review the maps and axes in your project. Menu names vary by WinOLS version. The supported minimum version will be specified following import testing.

“English map names and folders” changes names and folders only. Selection, addresses, axes and scaling remain identical. DAMOS keeps its original names.

03 / DAMOS INVENTORY

Start with your ECU.

Search our inventory by manufacturer, vehicle, ECU or software version.

Inventory is not a fixed compatibility list.This list shows our DAMOS inventory. The portal works automatically: upload your original file and we will create a MapPack for your software version, even if it is not individually listed here.
Loading catalog …BIN / ORI → CSV
04 / PRICING

Buy once. Get back to work.

ProductStandardMD1 / MG1 / MDG1
MapPack€40€50
DAMOS€60€75
MapPack + DAMOS Bundle: save 10%€90 €100€112.50 €125

All prices are net plus applicable VAT. Business customers only.

Prices may vary for individual controllers. The binding price is the price displayed after uploading your original file.

Controllers of the Bosch MDG1 generation (MD1/MG1/MDG1) are considerably more complex to define. This work carries a 25% surcharge for MapPack and DAMOS. The preview shows the identified definition scope. MG1CS221 / ASG1 available on request via WhatsApp only.

05 / QUESTIONS & ANSWERS

Before your first upload.

Have a specific software version or a technical question? Contact us directly.

Contact ↗
Is there a MapPack for my software version?
Upload your original BIN or ORI. The preview shows the matching identified scope. A missing catalogue entry does not automatically mean your file cannot be processed.
What is the difference between DAMOS, A2L and MapPack?
MapPack and DAMOS are two definition scopes supplied as CSV for WinOLS here. MapPack uses clear names; DAMOS retains original names and generally offers broader coverage. A2L is a different description format; a native A2L file is not promised here.
Does this work with Slave tools or encrypted files?
Analysis requires a complete, unencrypted BIN or ORI. An encrypted Slave file cannot be processed directly. Arrange an original export with your Master.
How do I identify my software version?
Check the software number, part number and, where available, hardware number in your reading tool identification screen. Compare them with the catalogue. Matching is based on the analysis of your original file.
How does the bundle discount work?
Bundle: save 10%. MapPack + DAMOS costs 10% less than the sum of both individual prices, rounded down in €0.50 steps. Standard: €90 instead of €100; MD1 / MG1 / MDG1: €112.50 instead of €125. The offer shown after upload is binding. Special controllers remain available by enquiry only.
Which original file do I need?
A complete, unencrypted Full Read as a BIN or ORI file. A Virtual Read may differ from the software actually installed. Use an original read from the vehicle. Encrypted slave files cannot be analysed here.
Which WinOLS version is supported?
Delivery uses the native WinOLS CSV format. The minimum version and precise import steps will be checked with actual exports before launch. This prototype does not promise untested version compatibility.
How do I import the CSV?
Create a WinOLS project with the same original BIN and use the map description / CSV import. Check column mapping, maps and axes. Exact menu steps will follow the WinOLS import test.
What if a map is missing?
Review the preview before purchase. Scope depends on the software version and reliably identified definitions. If delivery differs from the purchased scope, contact us with your order number. Statutory rights for defective products remain unaffected.
What happens to my original file?
It is used for analysis and order fulfilment. Uploads and generated outputs are deleted after 14 days. Your download link is valid for 3 days and 3 downloads. Use for improving the program requires your separate, optional consent.
Is this a tuning file?
No. MapPacks and DAMOS contain map definitions for WinOLS. They contain no modified calibration values and do not alter your original file. Need a finished Stage 1 or Stage 2 file? Find that service at ECU-Tuningfiles.com.
Can I get a refund?
No voluntary refund is offered for conforming delivered digital definitions. The portal sells exclusively to businesses. Statutory remedies for defects or non-delivery remain unaffected.
Why do MD1 / MG1 / MDG1 cost more?
Controllers of the Bosch MDG1 generation (MD1/MG1/MDG1) are considerably more complex to define. This work carries a 25% surcharge for MapPack and DAMOS. The preview shows the identified definition scope.
Which payment methods are available?
Payments are processed by Mollie, including PayPal. Eligible methods are shown in Mollie Checkout. Currently enabled: PayPal, cards, Apple Pay and pay by bank. Delivery follows confirmed payment only.

Questions about MapPack or DAMOS?

Contact us directly via WhatsApp or email.

WinOLS MapPack and ECU MapPack: what you receive

A MapPack helps you locate and understand maps in an ECU file. It describes functions through their names, dimensions and axes. You receive these map definitions as a CSV for import into WinOLS. The calibration values in your original file remain unchanged; the definitions give you a more organised starting point for reviewing and editing the project.

Your vehicle's software version is the starting point. Two vehicles with the same engine can use different files, so choosing a MapPack by model, year or power output alone is not enough. Upload your BIN or ORI and inspect the preview generated for that file before deciding which product suits the work you intend to carry out.

To import the definitions, open a WinOLS project containing exactly the original file you uploaded for analysis. Import the supplied CSV as map descriptions and check the column assignment in the import dialogue. Then review the maps and axes in the project before editing calibration data. The precise menu names and import steps depend on your WinOLS version.

This service is intended for workshops and tuners developing their own calibrations. An ECU MapPack does not contain a completed tune or replace your assessment of the functions involved. If you need a finished Stage 1 or Stage 2 file, that service is available at ECU-Tuningfiles.com. For your own calibration work, start here with the original file.

DAMOS Files and A2L definitions

People searching for DAMOS Files often need a wider view than a selection of maps assembled for one task. Our DAMOS product provides the reliably detected definitions with their original names and folders. Its scope can therefore be substantially larger than the MapPack. The preview for your uploaded file shows which definitions are actually included in the offer.

A2L is a separate description format defined by the ASAM MCD-2 MC standard. It can describe calibration parameters, measurement variables, memory assignments and conversions, among other information. DAMOS, A2L and MapPack are often searched together, although the terms do not simply name the same file format. What matters is the information you need and the format your workflow can import.

This portal supplies the offered map definitions as CSV for WinOLS import. It does not promise a native A2L file download or a complete ECU development description. If an A2L search brought you here, first check whether the CSV definitions and the displayed scope meet your actual purpose in WinOLS. The preview lets you make that comparison before purchasing.

You can choose MapPack and DAMOS separately or together. MapPack prioritises understandable names and a functional folder structure, while DAMOS retains the original naming. The English map names option changes only MapPack names and folders. It does not change the selection, addresses, axes or scaling. Compare both previews against the functions required for the vehicle and the job you are working on.

A Tuning MapPack for Stage 1 work

Stage 1 calibration work calls for a clear understanding of how functions interact. A Tuning MapPack helps organise relevant maps within your project, but it does not contain a completed Stage 1 tune. Suitable changes depend on the vehicle's equipment and condition, together with your assessment of the software. The definitions support that work without deciding the calibration for you.

Typical groups include driver wish, the torque model and torque limiters. These describe different parts of the request and limitation strategy, so similar names can have different purposes. Check the axes and how each function participates in control. A MapPack assists with finding and organising definitions; understanding the function and checking it against the vehicle remain part of your work.

For turbocharged engines, boost pressure and air path definitions may also be relevant. Fuel-related areas can include injection, injection duration and fuel pressure, depending on the system. Rail pressure is one possible area for applicable injection systems. The actual selection depends on the ECU and software version. This general description therefore does not establish a fixed scope for every uploaded file.

The MapPack is a general working resource rather than a product restricted to Stage 1. Included definitions may also be useful for more extensive calibration work. Check the preview against the functions needed for different hardware or your particular investigation. A larger total map count does not, by itself, tell you whether the definitions required for that purpose are present.

MapPacks for Bosch, Siemens/Continental, Delphi, Denso, Marelli, Temic and ZF

For Bosch, different ECU families lead to different collections of software versions. The EDC17, MD1, MG1 and MED17 family pages help you identify a known ECU and find recorded software entries. A family name is an entry point into the catalogue. Analysis of your actual original file determines whether definitions can be generated for the software you are using.

For Siemens/Continental, the catalogue includes entries from areas such as SIMOS. Compare the complete ECU designation with the available software identifiers, even when the vehicle model is familiar. Projects within one family can differ considerably. A matching vehicle description or a similar version name is therefore not enough to justify transferring definitions to another BIN without checking that file.

For Delphi, families such as CRD and DCM provide a starting point for browsing. For Denso and Marelli, use the relevant ECU and vehicle pages alongside the identifier search. The tables show the associations available in the catalogue. A listed engine helps narrow the search; it does not establish compatibility with every software version used for that engine.

Temic and ZF entries can also be explored through their associated control units and vehicles wherever corresponding records are available. Pay particular attention to whether a project concerns an engine ECU or a transmission TCU. These projects serve different purposes. The unit designation, vehicle information, transmission details and software identifiers help you select the entry relevant to the task you are carrying out.

Popular ECUs

Popular vehicle brands