ODX-parser

The ODX Parser Transform configures the UDS Request and UDS Response Transforms in MxTransit to send/receive diagnostic messages specified in the UDS spec and with the selected ODX file.

 

Note: This Transform was formerly called the UDS Transform.

Default UDS Supported Services (without ODX selected)

$10 Diagnostic Session Control Request

$14 Clear Diagnostic Information Request

$19 Read DTC Information Request

$22 Read Data By Identifier

$27 Security Access

$2E Write Data By Identifier

$31 Routine Control

How to use the Transform

1.Select the ODX Parser Transform from the Toolbox.

2.By default, the Transform uses ”DefaultECU” for the  Select ECU Name property and some default services and subservices to send/receive diagnostic messages specified in UDS spec.

 

uds2

 

 

3.Set the following properties to send and receive the diagnostic messages:

Functional ID (Functional diagnostic request CAN Id )

Physical ID (Physical diagnostics request CAN Id).

Response ID (Diagnostic Response CAN id).

(Optional) Browse and select the ODX file to send/receive diagnostic messages specified by the vendor in the selected ODX file.

 

uds3

 

4.Dll File for Security Key: Select the dll path to unlock the security service. See below for details of the security algorithm sample dll.

 

uds4

 

5.If the ODX is selected and parsed, you can select an ECU name from the drop-down list:

 

uds5

 

6.Message Format: Select the Message Format from the Format drop-down list . By default, the Message Format is Motorola.

 

uds6

 

7.Click on the Generate verb. The system generates Diagnostic Request, Transport Request, Transport Response, and Diagnostic Response Transforms in a subsystem (internal to the ODX Parser Transform) and automatically exports all the ports so they are visible on the ODX Parser Transform.

 

uds7

 

ODX-parser-populated

 

 

Notes:

Fill the Functional Id, Physical ID, and Response Id before clicking on the Generate verb.

If you use the DefaultECU (in the Select ECU Name property) and click Generate, all the configured Transforms generate which will support some default services and subservices .

 

 

8.Double-click on the ODX Parser Transform in the MxTransIt Harness window to open a new tab and display all the configured Transforms with connected and unconnected I/O ports automatically populated.

 

uds10

 

One response Transform is generated for each supported service.

 

9.The ODX Parser Transform configures 4 Transforms:

hmtoggle_plus1UDS Request Transform
hmtoggle_plus1UDS Response Transform
hmtoggle_plus1Transport Request Transform
hmtoggle_plus1Transport Response Transform

 

10.Connect to the CAN network through the Transforms.

 

uds10

 

11.Select Project -> Network Configuration from the main menu to change the Network Configuration. There can be zero or more Virtual Buses. Drag a device from the Devices onto bus name in the Virtual Communication Busses panel. For details, see Network Configuration.

 

uds13

 

12.Rename the CAN ports in the ODX Parser Transform or rename the CAN ports in both Transport Request Transform and Transport Response Transform to the name of the CAN bus defined in MxVDev.

13.Right-click on each Transform and select Export Ports.

14.Select the Signals to export and click OK.

15.Click (Save) to save your Harness.

 

NOTE: Configure Network configuration before you export the ports from the ODX Parser Transform.

hmtoggle_plus1Using the UDS Request Transform to Create Messages
hmtoggle_plus1Using UDS Response Transforms

 

hmtoggle_plus1SecurityKey DLL Sample

 

hmtoggle_plus1Sample Project with sample test cases

 

Notes:

Supported ODX file versions: v1.1.5 - v2.2.0

Tested with versions: v1.1.5, v2.1.0, v2.0.1, v2.2.0