ASAM Standards for Calibration Data: A2L, XCP and CDF
An ASAM standard defines how tools in vehicle development talk to each other. Three of them matter most for calibration: MCD-2 MC for the ECU description, MCD-1 XCP for measurement, and CDF for data exchange.
What an ASAM Standard Governs in Calibration
A calibration tool chain rarely consists of one product. Instead, it combines test bench, measurement hardware, data management and release records. So for those parts to work together, they need shared formats.
That is exactly what ASAM e. V. develops its standards for. They describe file formats and protocols, not products. Therefore datasets stay readable across tool boundaries, and usable across project lifetimes.
ASAM MCD-2 MC: the A2L File
MCD-2 MC describes the contents of an ECU. The file usually carries the extension .a2l and is historically called ASAP2. Moreover, it names parameters, measurements, addresses, axes and conversion rules.
This ASAM standard is the basis for everything else. Without it, a memory image would not be interpretable. VersaCal therefore reads A2L files with its own parser and lays them over your HEX images.
ASAM MCD-1 XCP: Measure and Calibrate Online
XCP governs the link to a running ECU. The protocol transfers measurements and writes calibration values back while the software runs. Besides, it works independently of the transport layer, for example over CAN or Ethernet.
VersaCal uses XCP for live measurement and for applying values online. A simulator is included as well. Thus you can trial a procedure although no hardware is attached.
ASAM CDF: Exchanging Calibration Data
CDF stands for Calibration Data Format, and the files carry the extension .cdfx. Furthermore, the standard describes calibration datasets in XML, that is, independently of the tool that produced them.
Consequently CDFX suits hand-over into OEM processes. VersaCal exports datasets in this format. Likewise it produces delta DCM, HEX and S-Record when your chain expects those.
Formats Alongside the ASAM Standard
Not every established format comes from ASAM. In practice, further file types have settled in as de-facto standards in everyday ECU calibration. VersaCal therefore supports them too, although no ASAM standard covers them.
- Intel HEX and Motorola S-Record – memory images of the ECU
- DCM and delta DCM – full and differential parameter lists
- CSV and PDF – reports for review, release and records
What This Means for Your Process
Standards protect your data from the tool. Thus you can swap a product although the datasets stay. As a result, dependence on a single vendor drops.
VersaCal therefore commits to these formats instead of a proprietary container. Your calibration data stays readable outside the platform as well. In addition, operation runs entirely in your infrastructure.
Read the standards: ASAM e. V. · ASAM MCD-1 XCP · ASAM CDF
Frequently asked questions about ASAM standard
Which ASAM standard covers the A2L file?
ASAM MCD-2 MC. The standard is historically named ASAP2, and the files usually end in .a2l. It describes an ECU's calibration parameters, measurements, addresses, axes and conversion rules.
Is XCP the same as CCP?
No. CCP was the older predecessor and ran over CAN only. XCP stands for Universal Measurement and Calibration Protocol and separates protocol from transport. Therefore XCP also works over Ethernet, USB or SPI.
Why do I need CDFX if I already have DCM?
DCM is widespread but does not come from ASAM. CDFX is the standardised XML route for calibration data, and OEM processes frequently require it. VersaCal produces both, so you do not have to rebuild your existing chain.
Talk through the ASAM standard and your formats
Bring your format list along. In the demo we work out which files your chain delivers and expects — and where VersaCal fits between them.