ECU Service for measurement, calibration, bypassing, and ECU flash programming via XCP
- Support of transport layers for CAN, USB, and Ethernet
- Highly scalable service code according to functionality and ECU resource consumption
- Multiple service instances for measurement, calibration, and bypassing without interference
- Security and data consistency mechanisms for bypassing
The Universal Measurement and Calibration Protocol (XCP) is the successor to the well established CAN Calibration Protocol (CCP). XCP is standardized by the Association for Standardisation of Automation- and Measuring Systems (ASAM).
The dSPACE XCP service supports transport layers for CAN, USB and Ethernet (UPD/IP and TCP/IP). It is designed for various use cases during ECU development such as measuring ECU variables and calibration, and also for ECU flash programming in connection with CAN.
The dSPACE XCP on CAN and XCP on Ethernet service implementation is also dedicated to bypassing ECU functions using the dSPACE real-time prototyping platforms MicroAutoBox and AutoBox.
Depending on the transport layer, the dSPACE XCP service covers various aspects of XCP,, from measurement and ECU calibration to bypassing, and right through to ECU flash programming.
Flexible configuration options make it possible to tailor the service implementation with regard to functionality and resource consumption in the ECU.
For bypassing, dedicated mechanisms are provided to guarantee minimal latencies, data consistency, and automatic failure checking. In addition, you can run measurement, calibration, and bypassing tasks in parallel on the same ECU.
In addition, it is possible to configure the XCP service on the ECU in such a way that two separate systems, like a calibration tool and a bypass system, can access the ECU independently of each other.
dSPACE provides consulting and engineering services to help you integrate the dSPACE XCP service and flash kernels into your ECU.
Support of One and Two Service Instances
With function bypassing, the service is typically configured for two instances, allowing two different client systems, like a calibration tool and a dSPACE RCP system, to interface the ECU independently of each other. In other words, each client system can connect to or disconnect from the ECU, set up DAQ lists, and start or stop measurements regardless of the other client.