Data Description
User-friendly display and edit description files

Data Description for ECU Calibration

Three types of description files play a key role in ECU calibration. They describe:


  • Internal ECU variables
  • Different communication networks
  • Diagnostic services and data as well as the flash process

Description Files for Internal ECU Parameters

Description files let the user access internal ECU parameters by symbolic names. A2L files are elementary components of every measurement and calibration operation, and it should be noted that the CCP and XCP protocols are address-oriented in their operation. The user selects objects by symbolic name, while CANape takes the associated addresses from the A2L and uses them in communication with the ECU.


Contents of the A2L database

An ASAP2 description file (also called A2L) contains all information on the relevant data objects in the ECU such as characteristics (parameters, characteristic curves and maps), real and virtual measurement variables and variant dependencies. Information is needed for each of these objects, such as memory address, storage structure, data type and conversion rules for converting them into physical units. In addition, an A2L also contains the parameters for communication between CANape and the ECU.

Supporting you in data description of internal ECU variables

CANape contains an editor (ASAP2 Studio) so that you can easily edit ECU description files in A2L format. The following tools, which are available separately, support you in working with ECU description files:

Easily create and edit ECU description files
Functional library for reading and writing ASAP2 files

Generating A2L Files

Manual generation

You can generate A2L files from CANape at any time with the information from the Linker Map file. To define communication-specific data in the A2L, you just need to create a suitable new driver in CANape (XCP-on-FlexRay, CCP-on-CAN, etc.) and save the settings. The measurement and calibration parameters from the ECU can be selected from the Linker Map file using object names. You can use the editor to conveniently input and manage all other settings, such as entry of minimum and maximum values, groupings, definition of conversion rules and storage schemes.

Automatic generation by C Code Parser

Special comments in C code are parsed with the A2L Creator, which is supplied as a component of the ASAP2 Tool-Set. Software developers do not need to define the objects a second time in a parallel database, rather they define them in the form of comments in the C code. This minimizes the risk of inconsistencies between the code and a separate database.

The software developer makes a change to the code directly at the relevant point. That is also precisely where the comments are located; so the developer can make all changes at one point, without having to update the changes in another tool.

The parser searches the C code for the comments and generates a partial A2L from them, which represents the measurement and calibration parameters. The communication section of the A2L, or other partial A2L files containing the complex conversion rules, can be merged into a complete A2L in another step and be updated with current address information from the Linker Map file.

Graphic automatic ASAP2 generation process with ASAP2 Tool-Set
Automatic ASAP2 generation process with ASAP2 Creator, Updater and Merger. Comparison of ASAP2 files and specific modification results using the ASAP2 Comparer and Modifier. The ASAP2 Checker checks these files for syntactic and semantic errors.