|
|
|
| R2012a Documentation → xPC Target | |
Learn more about xPC Target |
|
| Contents | Index |
| On this page… |
|---|
The Universal Measurement and Calibration Protocol (XCP) interconnects engineering control units (ECUs) in a CAN network. The xPC Target software supports this capability with the XCP sublibrary. A model that contains the blocks from this library can act as an XCP master that communicates with CAN network slave or ECU devices. The xPC Target XCP blocks do not work with UDP networks. Using the XCP sublibrary, you can:
Use the XCP Protocol Stack block to synchronize one or more CAN network slave or ECU devices.
Initialize an XCP slave server running in an ECU on a CAN network.
Parse A2L (ASAP2 database) files.
Acquire real-time measurement data when specific events occur.
Support data stimulation.
When creating models to work as XCP masters with ECU slaves:
Use the FIFO mode of the Softing CAN hardware (CAN I/O Support for FIFO) with the XCP blocks. Do not use the object mode of the Softing CAN hardware with the XCP blocks.
Use one XCP Protocol Stack block for each CAN channel.
Provide two A2L format files:
One A2L (ASAP2) file that the model can load into the CAN software database. The generated file contains signal and parameter access information for the target application. It describes the slave ECUs.
One A2L (ASAP2) file that the model can load into the CAN software database. The generated file contains signal and parameter access information for the XCP specific elements of the network.
 | XCP Over CAN Support | Blocks — Alphabetical List |  |
Learn more about Simulink through this collection of videos, articles, technical literature and the Getting Started with Simulink Guide.
| © 1984-2012- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |
