ecu.test calibration

ecu.test calibration enables direct access to measurement and calibration variables without additional 3rd party software tools. Using the XCP protocol, variables can be measured, calibrated, and evaluated during test execution. XCP is supported for all hardware-related bus interfaces for CAN, CAN-FD, and Ethernet.

To use ecu.test calibration an additional license is required. For more information, please visit tracetronic.com

Key features

The extension provides access to calibration variables for both reading and writing. Calibration variables can be read from the ECU via upload and written back to the ECU via download.

In addition, the extension supports access to measurement variables which can be read cyclically via DAQ or polling. A suitable task can be configured for each variable, while the available measurement tasks are polled live from the ECU. Both static and dynamic measurement lists are supported. Writing measurement variables via download is also possible.

For recording calibration and measurement variables, ecu.test calibration offers symbolic recording via the signal recording functionality integrated into ecu.test. To record a large number of variables, a global Mapping file can be added for signal recording. Recordings are stored in the ASAM MDF4 format and are compatible with trace analysis. If supported, the slave timestamp can also be used.

ecu.test calibration also provides general features such as page switching, as well as security access via Seed & Key.

Configuration

In the tool connections, the following ports are available for ecu.test calibration:

  • APPLICATION-XCP-ETH

  • APPLICATION-XCP-CAN

  • APPLICATION-XCP-CAN-FD

  • APPLICATION-XCP-CAN-FD-TOLERANT

These ports are generally available for tools that support direct CAN-bus access respectively Ethernet access, for instance tracetronic Ethernet and Vector XL API.

If the connection is configured in the test bench configuration via one of these ports, the port must then be assigned to an ECU under “Application” in the control-units tab of the test configuration. Additional application-level settings, such as the A2L file and the used transport layer, are also required there.

Considerations for certain XCP-Slaves

ETAS XETK/FETK

XETK devices natively support XCP-on-Etherrnet. While FETK devices use a proprietary Ethernet protocol, an ES89x interface module can be used to translate to and from XCP-on-Etherrnet. So both device types can be used with ecu.test calibration. However, they require some special considerations: First, the XETK or FETK needs to be set up as an ASAM-MCD1 compliant XCP device, and an appropriate A2L file must be generated. The proprietary NON-ASAM XCP dialect that offers some additional features when working with INCA is not supported by ecu.test calibration. Refer to the document ETAS Access Devices Operation as ASAM XCP on Ethernet Device for details. Also, make sure your PC’s network interface is configured as described in the document How can I avoid that my measurement stops due to an XETK measure overflow. Second, XETK and FETK modules have a feature called “advanced code check” (ACC), which, if enabled, requires the calibration system to “prove” it has an A2L file and/or dataset (hex/srec file) matching the software in the ECU flash memory before enabling calibration access. ecu.test calibration has no direct built-in support for ACC, but it offers building blocks for implementing ACC as a utility package. Contact support@tracetronic.com for examples and assistance.