Control Module Maps

What is a Control Module Map?

VCDS supports "Control Module Maps", this function rapidly scans through all possible measuring block groups and/or adaptation channels on any ECU and writes a "map" file. These "map" files are useful for creating new label files or taking a "snapshot" of all available data from an ECU.

• *.PLA files are Adaptation Maps.
• *.PLB files are Meas. Block Maps

VCDS Manual: Control Module Maps

Special Notes

• Control modules using the newest UDS/ODX protocol require a special .ROD file for VCDS to interpret data and they do not support traditional Measuring Blocks or Adaptation channel numbers. Since no data is readable without a .ROD file, there is no way for VCDS to interrogate all possible Measuring Blocks or Adaptation Values if those aren't already documented. In other words, the Controller Channels Map function does not work with control modules using the UDS/ODX protocol if no ROD file is present. If you run a Debug Level: 2 as described below, any control modules using UDS will be skipped and PLA/PLB files will not be retrieved if no ROD file is present. Current interfaces are able to create channel maps of Adaptation and Advanced Measuring Values, again only if an appropriate ROD file is present.

How can I help?

We are continuously working on improving this wiki and the VCDS label files, therefore it's very helpful to have maps from modules which are either new, undocumented or incomplete yet. You can help us by providing such maps from your car(s). After creating the "map" files (file type/ending PLB, PLA and CSV), you can find them in the /VCDS/Logs/ folder - please send them to us via email. If you are sending files, please attach an Auto-Scan from the car(s) you obtained the maps from too.

There are two ways how you can create such maps, if you are unsure about this procedure we recommend the first variant.

Type #1: To create a map from all undocumented control modules in the car, please perform the following procedure:

[Options]
Debug Level: 2
[Apply]
[Auto-Scan]
Select Chassis Type
[Start]

VCDS will now automatically create pre-label files from all undocumented control modules, once it's finished you will find these "map" files (file type/ending PLB, PLA and CSV) in the /VCDS/Logs/ folder. Please send these to us via email and make sure to attach an Auto-Scan from the car(s) you obtained the maps from as well. Please note that do to the amount of requests coming in we cannot respond to all emails (and sent out confirmations or status updates) but your files will added to the queue and we'll try to get the relating label files done as soon as possible.

Type #2: To create map files from individual control modules, please perform the following procedure:

[Applications]
[Controller Channels Map]
Address: XX (Enter the address of the control module in question, e.g. 01 for engine)
Function: Meas. Blocks/Adaptation
Output: Pre-Label File
[Start]

VCDS will now create pre-label files from the module you chose, once it's finished you will find this "map" file (file type/ending PLB, PLA and CSV) in the /VCDS/Logs/ folder. Please send these to us via email and make sure to attach an Auto-Scan from the car(s) you obtained the maps from as well.Please note that do to the amount of requests coming in we cannot respond to all emails (and sent out confirmations or status updates) but your files will added to the queue and we'll try to get the relating label files done as soon as possible.

How do I find out if the control modules in my car are documented?

Start VC and perform a standard Auto-Scan:

[Auto-Scan]
Select your model.
[Start]

After the Auto-Scan is finished, you will see outputs like this:

Address 01: Engine       Labels: 06A-906-033-BGU.LBL
  Part No: 06A 906 033 CM
  Component: SIMOS71 1.6l 2VG    6395
  Coding: 0000075
  Shop #: WSC 12345

OR

Address 76: Park Assist       Labels: None
  Part No: 1Z0 919 283 B
  Component: Parkhilfe 4-Kan H04 0020
  Coding: 0001001
  Shop #: WSC 12345

When you see Labels: None or Labels: Redir. Failed", there is no Label File for this control module.