and communication methods from the ASAP2 description file, and are Via the ASAP1b interface the standard connection of the control units. ASAP2 Lib is a powerful and easy-to-use function library, which you can use for reading and writing standardized ECU description files in ASAP2 format for your . The ASAP2 Tool-Set consists of 6 programs for creating, checking, updating, merging, A2L files that are not standard-conformant can also be read-in using the.

Author:	Samusida Kazijind
Country:	Oman
Language:	English (Spanish)
Genre:	Career
Published (Last):	7 January 2025
Pages:	16
PDF File Size:	14.81 Mb
ePub File Size:	3.3 Mb
ISBN:	328-4-92982-473-9
Downloads:	54785
Price:	Free* [*Free Regsitration Required]
Uploader:	Zulurg

The first version of the standard was developed before the foundation of ASAM e. This inclusion was a deliberate decision to keep all information to describe and access ECU data in saap2 location. Using XML would have otherwise increased the file size by approximately five times, which would have caused severe performance issues with tools that process such files. Furthermore, many tools in the Automotive industry relied already on the non-XML format and would have had to be re-written from scratch - an effort that was deemed to be unjustified.

Calibration tools can now show measurement variables and calibration parameters as part of a data structure. Furthermore, the standard introduced the definition of BLOB binary large object as a new object type to handle unstructured data blocks. A new transformer concept allows to convert complex, internal data structures into physical values by calling an external DLL.

Export ASAP2 File for Data Measurement and Calibration - MATLAB & Simulink

The calibration of parameters is an essential part of ECU software development. Calibration means the adaption aeap2 scalar constants, curves and maps to achieve an appropriate and optimized system behavior.

Once a new set of parameters has been determined, the next development step is to run tests in order to evaluate the effectiveness of the calibration.

For this purpose, internal variables are read from memory and transferred to a system that displays the data in a human-readable format.

In the early days of ECU development, the values of calibration parameters were directly modified in the source code. Variables had to be made assp2 for data logging in the source code as well. Every change to parameters or the list of measureable variables required modifications in the source code, re-compilation and flashing of the ECU.

As the control software grew stajdard complexity, the development of the software was split up into several groups xsap2 engineers function developers, software developers, calibration engineers, vehicle test engineers, etc. The side-effect of specializing the tasks however, was that this process became too cumbersome and slow. The MCD standard provided the way to abstract the calibration from the physical memory locations. Relevant information such as detailed descriptions of calibration and measurement variables is included.

Information that is not needed for calibration such as code details is excluded. Furthermore, the standard contains a description of the device interface to the ECU for read and write access. Such standatd description of calibration and measurement variables can easily extend to several thousand entries per ECU.

Today, software development is axap2 distributed. Without standardization, the creation and maintenance of such description files could easily become a major time and cost factor of the overall development process. Without standardization, the OEM or Tier 1 would be required to maintain several data description files in parallel or else continuously converting the files between different formats to ensure that everyone in the development process used the right format.

The variety of tools and description formats would quickly become a hindrance for development progress and a frequent source of errors in the MCD tool chain. ASAM MCD-2 MC was created to overcome those problems of wasting time and money stanxard deal with various description formats that more or less contain the same data.

The standard defines the syntax and semantics of the data descriptions. The standard was developed to consider the needs of all involved groups in the calibration process.

ASAM MCD-2 MC - Wiki

Each finds data elements and properties within the description format that they need for their work. Furthermore, they can work with the ECU data in a familiar representation without having to understand ECU-internal data formats such as scaled integers, bit-fields or ID-codes. Virtually all market-leading MC-systems for the Automotive industry know this format and are able to import, process and export a2l-files. The standard is also used in adjacent industries such as in train- and shipbuilding.

Another closely related field is the area of rapid control prototyping systems. The standard is also used by in-vehicle data loggers and diagnostic tools. Most of the production code generators for embedded software automatically generate a2l-files. If no encoding is specified in the a2l-file, then ISO Latin-1 is assumed.

The internal format of a2l-files is based upon a non-XML notation. The content of a2l-files consists of keywords, parameters, delimiters and comments.

Together, these items form a data model, which describe data semantics and data values. Keywords can contain parameters and other keywords. The parameters of a keyword contain the values of the data model.

Other keywords underneath a keyword create a hierarchical structure of keywords similar to an aggregation in XML. Parameters and aggregated keywords may be mandatory or optional and may have a multiplicity. The delimiters are applied to those keywords that contain optional standars or list standars parameters with variable length.

These delimiters prevent ambiguous interpretation. The standard clearly defines the list of parameters and aggregated keywords via prototype definitions. The prototype also specifies whether parameters and aggregated keywords are mandatory or optional, their multiplicity and use of delimiters. Single line comments start with a double forward-slash i. Multi-line comments are delimited with a forward-slash and asterisk i. These include statements are common practice in distributed development processes, where software originates from different suppliers and different tool chains.

Each a2l file provide partial data descriptions via a2l-file fragments, that have to be merged via include statements into a single file. Furthermore, it is common practice to place standatd interface description i.

This shall prevent ambiguous interpretation. At the beginning of an a2L-file, the version number keyword: The a2l-file consists of four structural levels:. An a2l-file contains one project PROJECTwhich describes all calibration and measurement data that belong to one adap2 project.

A header provides some general information about the project such as project number, version and a description HEADER. Each module represents one ECU. The following list contains the keywords of this level. This parameter can be aap2 scalar, string, array or look-up-table stadnard associated axes. The following types of tunable parameters are available:. The address, record layout, computation method, upper and lower calibration limits and further properties are defined.

Describes the methods and properties for converting values from an ECU-internal format, which is optimized for implementation, to a physical format, which is wsap2 understood by human beings. The majority of automotive ECU software still uses scaled integers for this data. This representation typically has an SI unit for signals, or may displays discrete data such as error codes as text strings.

Supported conversion methods are:. Other properties describe the display format in C-printf notation and the unit. Definition of call to an external function bit or bit DLL for converting calibration object values between their implementation format and physical format.

Bi-directional conversion is possible. Includes list of input and output objects. Input and output objects cannot contain measurement objects. Type definition of a axis object. Can be used for defining multiple axis objects of the same type.

Can be used to define axis standar, which are part ztandard a structure. Can be used to define BLOBs, which are part of a structure. Type definition of a measurement object. Can be used for defining multiple measurement objects of the standaard type. Can be used to define measurement objects, which are part of a structure.

ECU calibration with ASAP2Demo/ASAP2Library

Definition of structured data types similar to the “typedef” command in C. The fourth and lower levels of an a2l-file consist of secondary keywords. They are aggregated by primary keywords. The secondary keywords are a way to further structure the data and to provide further details. Specifies the properties of an axis that belongs to a tunable curve, map or cuboid. The following axis types are available:. The value changes automatically, once one of the referenced parameters has changed its value.

The standard does not explicitly state the signedness, bit-width and format of those data types. The following table provides a typical interpretation of the data types as used in the automotive industry.

The standard belongs to a group of tightly coupled standards that specify interfaces of meas-urement, calibration and diagnostic systems MCD. When all standards are jointly applied, then the MCD tool-chain achieves a high degree of interoperability, vendor- and technology-independence and allows easy exchange of data between customers and suppliers.

Calibration engineers can work independent from software engineers as soon as they get a flashable software version and a matching a2l-file. The advantages are even more significant when the development process is spread over several companies. Software sources do not have to be shared any longer to allow other parties to tune parameters or change the list of measurable.

Since a2l-files are standardized and vendor-independent, they do not have to be converted even though every partner in a development project may use different tools and different interfaces.

The standard allows to connect software development tools, calibration tools and ECU calibration interfaces with a neutral description format. All tools that support the description format are able to exchange and process the included information, hence there are no vendor-specific or technology-specific dependencies between tools of an ASAM-compliant calibration tool-chain.

Due to this comprehensive and complete coverage of data related to measurement and calibration, the standard has been globally accepted in the automotive industry and displaced most of the proprietary formats that were formerly used in the automotive industry.

Virtually all market-leading MC-systems know this format and are able to import and export a2l-files. The standard is used furthermore in other tools in the MCD area, such as data loggers, diagnostic tools, rapid control prototyping systems and automated calibration and testing systems.

Most of the production code generators for embedded software automatically generate a2l-files along with C-code sources.