XCP DAQSTIM block (not recommended)
Simulink® Real-Time™ Library of Drivers No Longer Recommended for Use
The XCP DAQSTIM block manages the synchronous data communication with an XCP slave running on the CAN network. This block supports:
Data acquisition — Data flows from the ECU that supports the XCP slave to the master.
Data stimulation — Data flows from the master to the ECU that supports the XCP slave.
The block dialog box supports configuration of the dynamic data acquisition list with a selection tool. As you configure the block, the block inputs and outputs change correspondingly.
Specify an ECU configuration A2L file (ASAP2 database) in the Main A2L File parameter.
Specify an XCP slave configuration A2L file (ASAP2 database) in the XCP A2L File parameter.
Observe that the block populates the Events and Signals parameters with the contents of the two A2L files.
Use the add and remove buttons on the selection tool to move event channels into a configuration. Assign signals to those channels for the configuration.
The software populates this field with event channels based on the contents of the files you specify in Main A2L File and XCP A2L File. Select the event channel to associate with the periodic data acquisition and stimulation of signals. You can configure multiple event channels to obtain different rates of triggering for the provided signal acquisition or stimulation events.
The event channel names clearly indicate:
Data flow direction (data acquisition or data stimulation)
Slave-side event type, such as the data flow rate
The software populates this field based on the contents of the files you specify in Main A2L File and XCP A2L File.
Use the add and remove buttons to move signals and events into configurations for the slave ECU.
Specify the A2L file that describes the available measurement and characteristics. The block maps the selected measurements as signals.
Specify the A2L file that describes a slave that supports XCP.
The file contains the
IF_DATA settings of the A2L
Enter the identifier for the slave ECU you are configuring.
Enter the stack identifier for the slave ECU you are configuring. This value must match the value of the Protocol Stack ID parameter in the corresponding XCP Protocol Stack block.