CAN Calibration Protocol (CCP) Overview

The CAN Calibration Protocol is a CAN-based master-slave protocol for calibration and data acquisition. A single master device (host) can be connected to one or more slave devices. Before a slave device may accept commands from the host, the host has to establish a logical point-to-point connection to the slave device. After this connection has been established, the slave device has to acknowledge each command received from the host within a specified time.

CCP defines two function sets—one for control/memory transfer, and one for data acquisitions that are independent of each other and may run asynchronously. The control commands are used to carry out functions in the slave device, and may use the slave to perform tasks on other devices. The data acquisition commands are used for continuous data acquisition from a slave device. The devices continuously transmit internal data according to a list that has been configured by the host. Data acquisition is initiated by the host, then executed by the slave device, and may be based on a fixed sampling rate or be event-driven.

The communication of controllers with a master device through CCP is based on the CAN 2.0B standard (11-bit and 29-bit identifier), which includes 2.0A (11-bit identifier) for data acquisition from the controllers, memory transfers to the controllers, and control functions in the controllers for calibration.

The ECU M&C Toolkit abstracts the CCP communication layer so that it is transparent to the user. For most cases it is sufficient that the underlying CCP communication is handled by the toolkit kernel itself. Nevertheless, the ECU M&C Toolkit offers direct access to the low level CCP commands if a non-standard timing behavior or independent user defined command sequence is needed.

CCP Protocol Version

The ECU M&C Toolkit supports the CAN Calibration Protocol specification, version 2.1.