DIALOGREBEL CTREBEL LTSoftware

DIALOG: log ECU data over CCP or XCP from an A2L file

Updated

Configure a REBEL to read internal ECU measurements over CCP or XCP on CAN, using the ECU's A2L file for the addresses. This guide also explains how CCP or XCP takes priority over diagnostic polling.

Before you start

  • A REBEL LT or REBEL CT connected to the ECU's CAN bus, and its USB cable.
  • The ECU's A2L file (ASAM MCD-2 MC), which describes its measurements, their addresses and its DAQ lists.
  • The bit rate of the bus the ECU's CCP or XCP traffic runs on.
  • DIALOG Standard or Plus for XCP and CCP measurement. A2L import needs DIALOG Plus.

New to the protocols? Read understanding CCP and XCP.

Create the configuration and the bus

  1. Create a configuration. Select New Configuration, enter a name and select OK.
  2. Check the sleep mode. On the Sleep Mode tab, choose the mode you need. Clear Limit Module Wakeup so the logger does not drain the vehicle battery. Select OK.
  3. Add the bus. Select New Bus, choose CAN 0 (HS) and select OK.
  4. Set the bit rate. Choose the rate of the ECU's network and select OK.

For the sleep settings and the rest of the configuration window, see DIALOG: create projects and configurations and send them to a REBEL.

Add the protocol and import the A2L file

  1. Add a protocol. Select New Protocol, choose CCP Protocol and select OK. For an XCP ECU, choose XCP Protocol from the same list. This guide shows the CCP route only.
  2. Import the A2L file. In the CCP Protocol Presets window, select Import From A2L File at the bottom left.
  3. Choose the file. Select the A2L file on your PC, then select Open. DIALOG takes the protocol settings from the file.
The CCP Protocol Presets window with the Bosch_CCP_001 preset selected, its CCP settings listed and the Import From A2L File button at the bottom left
Import From A2L File reads the settings from your ECU's file instead of a supplier preset.

The import fills in the same fields the presets show:

  • The protocol version (CCP 2.1)
  • The Command Receive Object (CRO) and Data Transmission Object (DTO) identifiers
  • The station address
  • The byte order
  • The DAQ lists with their identifiers and prescalers

Choose the measurements

The A2L panel lists everything in the file. To find what you need, filter by label, address, units or data type. The Show Only Measurements, Show Only Characteristics and Show Both options narrow the list further. Leave Byte Order on Use A2L Settings.

  • One parameter: select it, choose a sampling rate from the Rate list and select Copy Items.
  • Several parameters: hold Ctrl and select them, choose the Rate, then select Copy Items or drag them to the items list.

The rates come from the DAQ lists in the A2L file, for example segment synchronous, 10 ms time synchronous and 100 ms time synchronous.

The A2L panel listing measurements from a demo A2L file, with the Rate list open showing segment synchronous, 10ms time synchronous and 100ms time synchronous
Choose the DAQ rate before you copy.
Selected A2L measurements copied into the configuration's items list, which shows each item's rate, label, units, address, size and data type
Copied items appear in the configuration with their addresses.

Watch: How to log data using an A2L file (2:59)

Send the configuration and check the data

Send the configuration to the logger over USB. See DIALOG: create projects and configurations and send them to a REBEL.

To watch the measurements arrive, use the live data viewer. See DIALOG: view live data, copy recordings and export them.

When CCP and diagnostics share a configuration

A configuration can hold a CCP or XCP protocol and a diagnostic protocol at the same time. On its own, either one runs without conditions. Together, CCP or XCP has priority:

  1. CCP or XCP connects first. When the logger powers up it tries to connect over CCP or XCP.
  2. Diagnostics follow. Once that connection is established, the logger also polls the module over the diagnostic protocol.
  3. No connection, no diagnostics. If no CCP or XCP connection can be established, the logger does not poll diagnostics at all.

This stops diagnostic polling from waking modules on a sleeping vehicle. The logger only polls when the vehicle is awake enough to answer CCP or XCP. If you add a CCP protocol, check that the logger can connect over it, or the diagnostic items stay empty.

CCP or XCP comes first, diagnostics follow DIALOG · PROTOCOL PRIORITY CCP or XCP comes first, diagnostics follow Logger powers up CCP or XCP Can the logger connect to the ECU over CCP or XCP? Both run CCP or XCP measurement, and diagnostic polling of the module once the connection is up No diagnostic polling the logger does not poll the module; the diagnostic items stay empty Yes No This rule applies only when one configuration holds both a CCP or XCP protocol and a diagnostic protocol; on its own, either one runs without conditions. It keeps diagnostic polling from waking modules on a sleeping vehicle: the logger polls only when the vehicle is awake enough to answer CCP or XCP.
CCP or XCP connects first, and diagnostic polling runs only after it.

To set up the diagnostic side, see DIALOG: log UDS and OBD diagnostic data.

Next: DIALOG: view live data, copy recordings and export them.

Products in this guide

DIALOG

CAN analysis & diagnostics

View DIALOG Ask an engineer

REBEL CT

Automotive engineering logger

View REBEL CT Ask an engineer

REBEL LT

Vehicle diagnostics logger

View REBEL LT Ask an engineer

Still stuck?

Our engineers answer support questions on every Influx Technology product.