XCP (or) “Universal Measurement and Calibration Protocol” is a network protocol originating In , the protocol was standardized as “ASAM MCD-1 XCP”. Refer to transport layer specific command 68 .. ASAM MCD 2MC AML for XCP (Common_Parameters). Like CCP, the “Universal Measurement and Calibration Protocol” (XCP) originated from the . Learn about the capabilities of the ASAM MCD-1 XCP standard.
|Published (Last):||24 February 2017|
|PDF File Size:||7.63 Mb|
|ePub File Size:||12.88 Mb|
|Price:||Free* [*Free Regsitration Required]|
As a central improvement, an XCP master is now able to obtain a detailed view of the clock system related to an XCP slave, i. The initiation of the event is thereby carried out periodically by an XCP master. XCP always uses the same protocol layer independent of the transport layer. In addition to supporting other transport layers, aszm successor to the CCP protocol contains many functional improvements such as: XCP data is exchanged between the master and slave in a message-based way.
The standard is mainly used during development and does not cover the more complex process steps that are necessary in end-of-line flashing. The initial value 0.
For example, the master initiates contact in this direction. Two typical customer-supplier collaboration scenarios are supported:. In other words, the ECU contains only a generic XCP slave protocol stack, which responds to memory access service requests from the calibration system. This access enables modifications of large parameters e.
The following asynchronous events are defined: XCP was designed with these main objectives: The flash process with XCP is roughly subdivided into three areas: The first letter X in XCP expresses the fact that the protocol is designed for a variety of bus systems.
The standard consists of a base standard, which describes memory-oriented protocol services without direct dependencies on specific bus systems. The calibration tool uses this information to establish communication, visualize the implemented XCP features and informs the calibration engineer about ECU resource limitations.
Participating slaves have to sample their timestamps instantaneously with the mcc of the event.
This enables the calibration tool to correlate measurement data from different ECUs when displaying them together in one graphical chart. Some of the standard commands are: Today, there is a strong need for reliable synchronization accuracy in the single-digit microsecond range or even below that.
Furthermore, specific event channels are required, which control the bypassing process. The frame consists of three parts: An event does not have to be cyclic and time-equidistant. Due to limitations in the implementation of the XCP master and XCP slaves as well as limitations of the communication infrastructure, the achievable accuracy using the above mentioned legacy time correlation technique is limited.
The adaption of the ECU code to support a bypass is called a bypass hook. Addition of the transport layer for FlexRay.
This page was last edited on 20 Septemberat A slave may ,cd communicate with one master at any given time. The standard includes the following deliverables: Minimal resource usage in the ECU Efficient communication Simple Slave implementation Plug-and-play configuration with just a small number of parameters Scalability: The programming commands are: Flashing means writing data into an area of flash memory. These MMUs offer the possibility to adjust parameters located in a flash memory segment by remapping mcf an address translation to a physical RAM area.
Entire datasets can be acquired or stimulated synchronous to events triggered by timers or operating conditions. XCP introduces the concept of pages which make the implemented address translations accessible for the XCP Page Switching service commands.
The mechanism to enable a bypass hook is implementation-specific and not part of the XCP standard. From the perspective of the calibration tool, the RAM area in which the parameters are located is referred to as calibration RAM memory that can be calibrated.
Therefore, each clock known to the XCP slave features a unique identifier. The information about the flash sectors is also part of the A2L file. The generation of the XCP master initiated event that has to occur simultaneously at the XCP slaves requires broadcast-like mechanism. Aswm safety reasons, a bypass hook may need to be activated before it is functional.
XCP (protocol) – Wikipedia
The third technique addresses the requirements of resource limited XCP slaves that do aszm offer the possibility to synchronize clocks. Once the bypassing tool receives the DAQ data triggers, it starts the execution of the bypass function. Views Read Edit View history. Essentially, the protocol supports all typical calibration tasks without the need to recompile to ECU application.
Standard Authors Accurate Technologies Inc. Don’t have an account? In addition, XCP also supports programming of flash memory. The primary purpose of XCP is to adjust internal parameters and acquire the current values of internal variables of an ECU.
This information is required to handle systems with more than one grandmaster clock. The XCP packet is independent of the used transport protocol. To overcome these disadvantages of the polling mode, XCP offers the synchronous data acquisition mode.
It enables the slave to report a disturbance, such as the failure of a specific functionality.