XCP UDP Configuration

Configure XCP UDP slave connection

• Library:

• Simulink Real-Time / XCP / UDP

  Vehicle Network Toolbox / XCP Communication / UDP

• 

Description

The XCP UDP Configuration block uses the parameters specified in the A2L file and the ASAP2 database to establish an XCP slave connection.

Before you acquire or stimulate data, specify the A2L file to use in your XCP UDP Configuration. Use one XCP UDP Configuration to configure one slave connection for data acquisition or stimulation. If you add XCP UDP Data Acquisition and XCP UDP Data Stimulation blocks, your model checks to see if there is a corresponding XCP UDP Configuration block. If there is no corresponding XCP CAN Configuration block, the model prompts you to add one.

The XCP UDP communication blocks support Simulink^® accelerator mode and rapid accelerator mode. You can speed up the execution of Simulink models by using these modes. For more information about these simulation modes, see Design Your Model for Effective Acceleration.

The XCP communication blocks support code generation with limited deployment capabilities. Code generation requires a C++ compiler that is compatible with the code generation target. For more information, see Supported and Compatible Compilers.

Parameters

Config name — Specify XCP UDP session name

'UDP_Config1' (default)

Specify a unique name for your XCP session.

Programmatic Use

SlaveName

A2L File — Select an A2L file

file name

Click Browse to select an A2L file for your XCP session.

Programmatic Use

A2LFile

Enable seed/key security — Select that key required to establish connection

'off'

Select this option if your slave requires a secure key to establish connection. Select a file that contains the seed/key definition to enable security.

Programmatic Use

EnableSecurity

File (*.DLL) — Select file for seed and key security

file name

If you select Enable seed/key security, this field is enabled. Click Browse to select the file that contains the seed and key security algorithm that unlocks an XCP slave module. This parameter is available in Windows Desktop Simulation for Vehicle Network Toolbox.

Programmatic Use

SeedKeyLib

Output connection status — Display connection status

'off'

Select this option to display the status of the connection to the slave module. Selecting this option adds a new output port.

Programmatic Use

EnableStatus

Disable CTR error detection — Disable CTR error detection scheme

'on' (default) | 'off'

To detect missing packets, the block can check the counter value in each XCP packet header. When 'on', counter error detection for packet headers is disabled. When 'off', the counter Error detection scheme is enabled.

Programmatic Use

HeaderErrDet

Error detection scheme — Select CTR error detection scheme

One counter for all CTOs and DTOs (default) | Separate counters for (RES,ERR,EV,SERV) and (DAQ) | Separate counters for (RES,ERR), (EV,SERV) and (DAQ)

To detect missing packets, the block can check the counter value in each XCP packet header and apply an error-detection scheme.

Programmatic Use

CTRScheme

Sample time — Sample time of block

-1 (default) | numeric

Enter the base sample time or a multiple of the base sample time. -1 means that sample time is inherited.

Programmatic Use

Block Parameter: SampleTime

Local IP Address — Maser IP address

x.x.x.x

Enter the IP address to which you want to connect.

Programmatic Use

LocalAddress

Local Port — Master IP port

1–65535

The combination of Local IP address and Local port must be unique.

Ports in the range 5500 through 5560 are reserved for Simulink Real-Time communications.

Programmatic Use

LocalPort