ASAM has subdivided the standards into three groups, which are briefly described in the following tables:
- AE: Automotive Electronics
- CAT: Computer Aided Testing
- COMMON: Common standards shared between AE and CAT
ASAM AE standards (Automotive Electronics) are primarily applied during the design and implementation phases of ECU software development (left side of the V-Model). They focus on:
- design of functional and interface specifications for software components
- carrying out measurement, calibration and diagnostics tasks on an ECU
- automation of HIL tests
- description of engineering artifacts
- exchange of engineering issues
Automotive Test Exchange Format
Definition of an XML-based format for describing tests. Allows the reuse of test descriptions in different test automation systems. Covers activities such as test specification, test planning, test execution and test evaluation. Test specifications includes test cases, sequences, steps, actions and corresponding meta data. Format allows to store test values for inputs (stimuli values), outputs (expectation values) and execution conditions. Frequently used in conjunction with ASAM HIL.
Definition of an XML-based format for describing engineering objects such as source code, compiled objects or documentation files, and associated meta information about the objects, such as creator, name or version. Primarily used for exchanging information between OEM and supplier.
Calibration Data Format
Definition of an XML-based format for storing calibration values and associated meta data on acquisition and quality. Complements ASAM MCD-2 MC such that it provides the values of the calibration parameters described by ASAM MCD-2 MC.
Functional Specification Exchange Format
Definition of an XML-based format for describing the functional specification of software, primarily for the purpose of generating technical documentation. The format allows documentation via prose text in multiple languages, cross-referencing, linking and mentioning of requirements. Variations of the specification can be expressed. Is complementary to ASAM MDX, which contains the interface definitions of functions.
Definition of an API between test automation systems and ASAM HIL test-bench components. Provides access to the simulation model, ECU internal measurement and calibration data, diagnostics data and the electrical error simulation unit. API is described as a technology-independent UML model. Includes code examples for implementing the API in C# and Python.
ISSUE Exchange Format
Definition of an XML-based format for information exchange between different parties of a distributed development process. Covers change requests, clarification requests, problem reports and further use-cases. Furthermore, definition of a workflow for handling the requests.
Model Based Functions Specification
Definition of a block library for model-based design that contains typical functions needed in automotive control algorithm specifications. Includes the definition for 70 blocks with icons, pseudo code and test vectors. Also includes a description of a reference implementation in MATLAB/Simulink.
CAN Calibration Protocol
Definition of a communication protocol between master and slave controllers on a CAN 2.0B network. Includes transfer of calibration data to slave devices, continuous data acquisition from slave devices and carrying out of generic control functions. Standard is also known as "ASAP1". Standard has been replaced by ASAM MCD-1 XCP, but is still widely used in the industry.
The Universal Measurement and Calibration Protocol Family
Definition of a bus-independent communication protocol between master and slave controllers. Includes synchronous data acquisition and stimulation, read/write access on calibration data, memory page management, flash programming and further optional features. Transport layer specifications are defined for CAN, Ethernet (TCP/IP & UDP/IP), FlexRay, USB and SPI/SCI. Establishes an improved and generalized version of ASAM MCD-1 CCP.
Data Model Specification for ECU Diagnostics
Definition of an XML-based format for describing ECU diagnostic, programming and related vehicle interface data for data exchange between the ECU and external test equipment. If compliant to this standard, such equipment does not require special programming to process diagnostic data from an ECU. Standard is also known as "ODX".
ECU Measurement and Calibration Data Exchange Format
Definition of calibration parameters (CHARACTERISTIC) and measureable variables (MEASUREMENT) via a non-XML format. Such data resides inside the memory of the ECU. The definition format makes the data accessible through application systems. Furthermore, describes the HW interface of the ECU for device driver configuration of the application system. Standard is also known as "ASAP2".
Data Model for ECU Network Systems
Definition of an XML-based format for describing messages and their timing of automotive communication busses. Is the preferred description format for FlexRay and MOST, but also supports CAN, TTCAN, LIN and Ethernet. Is used for design, configuration, monitoring and simulation of communication on the bus. Standard is also known as "FIBEX" (Field Bus Exchange Format). Content is harmonized with the AUTOSAR System Template.
Automation / Optimization and ECU Calibration System Interface
Definition of an RS232 protocol between a test automation system and a measurement & calibration system connected to an ECU. Standard describes an obsolete technology. Standard has been replaced by ASAM MCD-3 MC and ASAM MCD-3 D.
Application Programming Interface for MVCI Diagnostic Server
Definition of an object-oriented API for a diagnostics server, which provides bus- and protocol-independent services for communication between client applications and ECUs. Includes a mapping of the OO API to C++, Java and COM-IDL with example code. Is complemented by ASAM MCD-2 D, which contains the actual diagnostic configuration for ECUs and vehicle networks.
Application Programming Interface for Measurement and Calibration server
Definition of an object-oriented API for a measurement and calibration server, which provides bus- and protocol-independent services for communication between client applications and ECUs. Includes a mapping of the OO API to COM-IDL with example code. Is complemented by ASAM MCD-2 MC, which contains the actual measurement and calibration data description for ECUs. Standard is also known as "MVCI D-Server API".
Model Data Exchange Format
Definition of an XML-based format for describing interfaces of functions, their data (variables and calibration parameters) and scheduling in ECU software. This allows the integration of such functions as object code into the overall ECU software without having access to the source code. Standard is complementary to FSX, which contains the functional description of functions. MDX is the predecessor of the AUTOSAR Software Component Template.
ASAM CAT standards (Computer Aided Testing) are primarily applied during the verification & validation phases of ECU software development (right side of the V-Model), and during automated calibration and system testing on engine and vehicle test beds. They focus on:
- automated calibration
- storage of testing data
- evaluation and analysis of testing data
Automatic Calibration Interface
Definition of a client-server, object-oriented API for an automatic calibration system (client) for remote-controlling a test bed automation system (server). Standard includes
Client and server may reside on different host systems, communicate via TCP/IP and are suitable for static tests execution. Includes a CORBA guide for middleware implementation, an interface definition file and a description for interface certification tests.
Components for Evaluation and Analysis
Definition of functional components for the evaluation and analysis of test measurement data. Most commonly used for the development of applications for processing and visualization of testing data. Defined components are: Input, Worker, Output, Consumer, Producer and Viewer. Services are available for graphic controls, logging & tracing, unit conversion, undo & redo, inter-component communication and help. Furthermore, defines a file format for CAE component description. Includes reference code files for Java and .NET.
Generic Device Interface
Standard focuses on the connection of measurement and control devices of a test bed with a test bed automation system via a 4-layer architecture. Includes the specification of
Standard specifies APIs for all layers and provides description formats for device functions and data structures. Includes companion standards for communication with chassis dyno test beds, crash test devices, multi-channel DAQ systems and mapping of MCD-3 to GDI. Includes files for schema definition, C-header, description format and implementation examples. Also available via ISO 20242 without the automotive-specific companion standards and code.
Open Data Services
Standard focuses on the persistent storage and retrieval of data independent of an IT architecture. Is primarily used in conjunction with test automation systems. Includes the specification of
Application models exist for vehicle geometry, NVH testing, test stand calibration data, bus data and testing workflows. Includes files for schema definition, interface definitions and description format examples.
ASAM COMMON standards are used in both areas, AE and CAT.
Layout Exchange Format
Definition of an XML-based format for describing layouts for graphical content used by data post-processing applications and automated document generators. Includes definitions for master layouts, canvases and graphic objects such as images, charts, shapes and curves. Can contain embedded formulas resolved during runtime. Used particularly in conjunction with CEA.
Measurement Data Format
Definition of a block-structured and channel-oriented binary format for storing measurement data including descriptive meta information. Allows for synchronization of data by time, angle, distance and index. Allows efficient storage of measurement data in real-time. MDF files can be referenced by an ODS database.
ASAM uses common description methods for the technology definitions in the standards:
- Format description: defines syntax and semantics of a file format for the purpose of data exchange.
- API: defines the interface and functional behavior of executable routines for the purpose of calling service routines or exchanging data between computer programs.
- Protocol definition: defines syntax, semantics and synchronization of the communication via a bus for the purpose of establishing a communication link between computer systems.
- Technology reference: specifies a technology-dependent interpretation of the technology-independent parts of the standard, typically via mapping rules or program code.
- Application area companion: defines an extension of a base standard for a specific application area or a specific type of device.
- Transport layer specification: defines how a generic protocol definition is to be interpreted using a concrete physical layer.
These methods are used throughout all ASAM standards.