WinOLS Mastery: Map Identification & Editing: DAMOS A2L Files and Description Files
Watch This Course
$299 USD
-OR-
Or
8 easy payments of only $37.38
Instant access. Easy checkout. No fees.
DAMOS A2L Files and Description Files
06.59
| 00:00 | - It's virtually impossible to spend time on a chip tuning forum without seeing multiple references to DAMOS files, A2L files, description files or map packs and these are terms that are often thrown around with limited understanding of what they mean. |
| 00:15 | Many of those fresh to WinOLS also have formed the impression that tuning a factory ECU without this information is impossible which fortunately isn't always the case. |
| 00:26 | So what are these files and what do they do for us? Well in essence these are documents that tell us exactly how a particular controller or ECU works. |
| 00:36 | There are levels to these files but in general, they'll provide the address for a particular map as well as the axis locations and conversion factors or scaling so that we can view real values rather than the raw data. |
| 00:50 | Better still, these maps will typically be named too so that we know what they do. |
| 00:55 | There'll also be information about the logic flow of the controller. |
| 00:59 | In other words, how the data is used and how the different maps interact with each other to actually make the engine run. |
| 01:06 | On face value this sounds like the dream scenario, instantly taking all of the hard work of finding and defining the maps out of our hands and we can just settle down to the task of tuning. |
| 01:18 | The reality however may be quite different to this theory. |
| 01:22 | For a start, not all of these files are created equal. |
| 01:26 | You can probably understand that when Bosch or Siemens for example create their latest and greatest controller for a particular manufacturer, they're not going to rush to the tuning aftermarket and freely provide detailed data on the inner workings of said controller. |
| 01:42 | This information is typically closely guarded and getting access to it, particularly for brand new controllers, really comes down to companies having relationships with those writing the code in the first place. |
| 01:55 | This is usually how the larger chip tuning companies seem to have tuning support for a brand new vehicle a matter of months after the vehicle first hits the showroom floor. |
| 02:06 | Unless you're very well connected with those on the inside of Bosch or Siemens, this is unlikely to be a viable path for you. |
| 02:13 | No problem though as you'll likely be able to find various DAMOS files for older generation controllers available for a fee or sometimes for free on various chip tuning forums. |
| 02:25 | Some of these may well be the real deal but more often than not you can find yourself paying good money for a description file that's incomplete or inaccurate with MAP or axis data that doesn't properly match the controller that you're tuning. |
| 02:40 | We also need to understand exactly what these files actually show us. |
| 02:45 | You're probably thinking right now that you're going to be suddenly shown the ignition table, cam target tables, target lambda tables and more all in plain English so that you can understand exactly what's going on and tune the engine just like you would on an aftermarket standalone or commercial reflashing package. |
| 03:04 | Unfortunately these files will often be written in technical German with a wide range of bizarre acronyms which on face value may mean nothing to us. |
| 03:14 | Who would have thought that the acronym KFLBTS for example, refers to the lambda for component protection table. |
| 03:22 | All is not lost however and these files can still be useful to us. |
| 03:27 | Particularly with OLS' ability to translate German to English this can put us one step ahead, however we'll also find that technical German often includes words that have no English equivalent so proper translation may actually be impossible. |
| 03:43 | To help with navigating map packs and finding the tables you're interested in, we've attached a list of the common Bosch acronyms as a PDF. |
| 03:51 | These will help you identify the maps required for reliable tuning and it'll also let you associate the map name to the map shape. |
| 03:59 | The bigger issue is that modern ECUs are incredibly complex with 100s or more likely 1000s of individual tables and parameters. |
| 04:08 | Those new to this style of tuning would rightly think that having a full description of every map and parameter is what we need but the reality is that in 99% of instances, less is more and we may only need somewhere in the order of 20 to 30 maps defined in order to perform a proper tune on a basic stage one car. |
| 04:29 | Granted if you want to start making more serious modifications like adding forced induction to a naturally aspirated vehicle then the number of required maps we'll need access to does increase but for the majority of tunes, and the ones we focus on within this course, this won't be necessary and this is much less likely to confuse you. |
| 04:50 | So the bottom line is do we actually need a description file or map pack in order to tune a vehicle using WinOLS? And the answer is, it depends. |
| 05:00 | For older and simpler controllers and particularly for basic modifications to suit a bolt on car, the answer's no. |
| 05:08 | Understanding the logic flow of the ECU and what maps you'll need to find, along with pattern recognition, all aspects that you will learn within this course, will let you get by without a description file. |
| 05:21 | For newer controllers, a description file can be a help and can certainly fast track locating maps. |
| 05:28 | The information provided in this course will still be vital so that you can understand what the description file is telling you and how to ensure that the maps that are defined are in fact accurate. |
| 05:39 | Sometimes the best way to start is with a map pack which is an OLS project that has all of the key maps you'll need identified and defined. |
| 05:50 | This gives you a great starting point and allows you to focus primarily on the tuning process. |
| 05:54 | Once you have a good base map pack for let's say the Bosch MED9 ECU, it's also possible to transfer the map data to another MED9 based tuning project. |
| 06:05 | This allows you to create your own map packs for different vehicles quickly and easily. |
| 06:10 | This will save you time and money in the long run. |
| 06:13 | Creating map packs can be relatively boring and repetitive work but it's also a great way to train yourself and gain confidence in the identification process. |
| 06:24 | Let's just quickly recap before we move on. |
| 06:26 | Despite popular believe, a description file is not essential in order to perform a basic stage one tune, particularly on older controllers. |
| 06:35 | While a full description file for your ECU might sound ideal, the reality is that you don't need every map or parameter defined for the majority of tunes and hence this can actually become confusing if you've got access to every map available. |
| 06:50 | A good place to start can be a basic map pack with just the maps you need to access defined. |
