Diagnostic Services

The Diagnostic Services function allows you to send a service request to the ECU. The service request must be defined in the diagnostic database. The service request and its result can be shown both in clear text and in hexadecimal notation. All clear text must be defined in the diagnostic database. The display of the service request and the results can be configured.

The request can be executed either just once or recur periodically. The recurrence rate can be configured.

If the cyclical send timeframe you defined cannot be adhered to, for example because the bandwidth of the interface is not sufficient, it is adjusted automatically. In this case, the adjusted cycle time is shown with a red background.

To configure a diagnostic service

Select ODX>User views>Diagnostic Services.
The dialog box for selecting a service is displayed.
Click Configure..
Select "General" in the left-hand window.
Activate the check box "Snapshot relevant" if the results of the service request are to be recorded in the snapshot (see the section Snapshots).
Activate the check box "Show service ID in tree view" if you want the ID of the Diagnostic Service to be displayed next to the name.
Activate the option "Create Measurement Signals from Response Parameters" if you want to add the signal measured subsequently to the signals available in the INCA variable selection (seeDiagnostic Signals in the INCA Variable Selection).
Pressing the Save as default button makes any changes you have made become the default setting.
Select "Output Configuration" in the left-hand window.
Activate the required options.
Click OK.
Refer to the following table for details of the significance of the options.

Option	Meaning
Show tester data	Service request and relevant parameters which were sent to the ECU
Show response status	Type of response of the ECU, response status
Show message bytes	Response of the ECU in hexadecimal notation
Show response parameter	ASAM MCD2D-interpreted response of the ECU
Show only last response	Shows only the data of the last service request. The data of previous service requests is deleted
Update during cyclic execution	If the cyclic repetation of the service request is activated, the display is updated in every cycle

To execute a diagnostic service

Choose ODX>User views>Diagnostic Services.
The dialog window for selecting the service will be displayed.
Select the service you want to execute from the top left section of the window.
The top right section of the window will show the parameters for the service you selected.
In the "Values" column, select the parameter values for the service.
If the service is to be repeated on a regular basis, select the "Cyclic" check box and enter the cycle intervals.
Click Send.
The service request is sent to the control unit and the response from the ECU will show up in the bottom section of the window.

The data (PDU, Protocol Data Units) sent to the ECU after the service ID has been entered, can be modified manually. To do this, use hexadecimal notation to enter the data in the "PDU" field. Please note that afterward, you can no longer select the parameters for this service.

Java Jobs

The ODX data model makes it possible to run Java code. These Java jobs are handled like diagnostic services - in particular, intermediate results can be issued while they are run.

Java jobs are indicated with a Java icon in the list of services - when selected in the list, both job parameters and diagnostic service parameters are shown on the right in the window and can also be edited there.

Java jobs are started using the Send button - depending on how complex they are these may take several seconds or even minutes to run.

Although not permissible in the ODX data model, working with Java GUIs is technically possible (see the example "JobDemo_JavaGUIs").

Note
The first time they are run, the Java windows may remain in the background! The windows are only in the foreground when they are run again.