Tailored CCP/XCP solutions for unique customer implementations

30/05/2016 by Kvaser

The CAN Calibration Protocol (CCP) and Universal Measurement and Calibration Protocol (XCP) protocols for reading measurement data and writing parameters to electronic control units (ECUs) are now commonly used during development, testing and in-vehicle calibration. Developed by the Association for Standardization of Automation and Measuring Systems (ASAM), CCP was designed purely for CAN networking applications, whilst its successor, XCP – introduced in the early 2000s – caters for a variety of transport layers, including LIN, FlexRay, Ethernet and, of course, CAN.  As with any standard, it is impossible to specify every detail for every application, so experienced, trustworthy suppliers are essential to delivering robust solutions.

Whilst the CCP and XCP higher layer protocols were intended as universal standards, many vehicle OEMs have implemented them in slightly different ways. A notable example is ECU security, where proprietary usage is not standard and yet is increasingly necessary. For software tool providers, a tailor-made approach – demanding considerable cooperation between the software vendor and the customer – is usually required to optimise the calibration toolchain.

Maintaining a secure toolchain

Martin Sventén, Business Manager at Accurate Technologies (ATI) Sweden AB, a Kvaser technical associate, notes: “Whilst some development ECUs are unprotected, most are secured by a proprietary SEEDnKEY mechanism that the development tools need to verify or implement. Access to these security mechanisms demands considerable trust between tool supplier and end customer.” He adds: “ATI’s VISION Calibration and Data Acquisition software has been capable of running CCP/XCP for many years and ATI provides the calibration toolchain for some of the world’s largest automotive manufacturers. Our engineers are highly experienced when it comes to working with customers to enhance their calibration and measurement process, whilst safeguarding the NDAs and legal protection rightly attributed to modern ECUs.”

Accurate Technologies often specifies Kvaser Memorator or Kvaser Eagle as the hardware interface between the ECUs and ATI VISION. Kvaser’s single and multichannel products provide the reliability and bandwidth necessary for all CAN-based CCP and XCP applications. In particular, Kvaser’s multichannel interfaces facilitate the handling of data channels from multiple ECUs by time synchronising the data transmitted and received across different buses.

Encrypted t programs

Kvaser’s Memorator product platform is programmable via Kvaser’s t programming language, facilitating a ‘tailor-made’ approach to CCP/XCP. Kvaser Memorator customers have the option of implementing an encryption program to protect their intellectual property, in addition to locking the execution of a t program to the Memorator device’s serial number. This is how ATI protects customers’ CCP/XCP solutions, including the Seed and Key parameters.

A calibration toolchain needs to be secure, efficient and flexible to meet the increasing complexity of the job. Confirms Sventén: “ATI VISION was designed from the outset to adapt to the needs of individual calibrators, making the most common tasks as efficient as possible. Whether it is data acquisition, calibration, rapid prototyping or flashing that customers are doing over CCP or XCP, the combination of ATI’s deep calibration expertise and Kvaser’s trusted CAN interfaces make for a unique partnership that our automotive customers can rely on.”

For more information on CCP/XCP, please visit www.kvaser.com/ccpxcp/

For a detailed explanation of the difference between CCP and XCP, please visit ‘The Move from ASAM CCP to XCP Communication Protocolwhitepaper.

Link CCP/XCP page

For more information on CCP/XCP, please visit www.kvaser.com/about-can/higher-layer-protocols/ccpxcp/

Difference between CCP and XCP from ATI

For a detailed explanation of the difference between CCP and XCP, please visit ‘The Move from ASAM CCP to XCP Communication Protocol’ whitepaper.