User Views

Generally ODX-LINK can open all ODX projects which comply with the ODX standard in Version 2.0.1 and 2.2.

These projects describe the diagnostic services, with their parameters, which can be queried via the ODX-LINK user views. In addition, the ODX project contains decoding information for responses from the ECU, i.e. information about how the data from the ECU is to be interpreted.

The ODX-LINK user views output this decoded information (or parts thereof) in the windows.

With the help of several ODX-LINK user views (e.g. the "Diagnostic Services" window), the user can select and parameterize any service – once the service request has been sent, the complete, decoded response is shown in the user view. In this case, the user must have detailed knowledge of the different services and of the data transported.

Other ODX-LINK user views, on the other hand, have been developed for very special requirements, such as the display of data for Service Inspector ("Service Inspector" window). In these cases, the user gets the required result at the simple push of a button.

The ODX-LINK user views do not depend on whether INCA measuring is taking place or not, i.e.:

even if there is no current INCA measuring, the windows for querying diagnostic data can be used,
the display of data in the ODX-LINK user views is not controlled via the starting or stopping of INCA measuring but exclusively via manual user operation (using the relevant Read ... buttons),
the displayed diagnostic data of the ODX-LINK windows is not recorded in an INCA measure file. To record diagnostic data, corresponding diagnostic signals must be configured for INCA measuring in the INCA variable selection.

Use ODX>User views to open the dialog windows for running your diagnostic tasks. The menu contains the following items:

Note
The configuration of most ODX-LINK user views (apart from "Diagnostic Services" and "Hex Services") must correspond to the ODX diagnostic database read in. ODX-LINK makes ODX configurations (ODX databases and the corresponding default window configurations) available to available standard diagnostic protocols (OBDonCAN and OBDonUDS) in the form of INCA export files (to be found in ETASData\INCA7.6\export\ODX). Please note, however, that these ODX configurations may not actually suit all diagnostic services of the ECU used, as the diagnostic services of many ECUs deviate from the relevant standard diagnostic protocol. ECU-specific fault memory entries and environment data in particular are thus not part of these sample configurations.

Note

The configuration of most ODX-LINK user views (apart from "Diagnostic Services" and "Hex Services") must correspond to the ODX diagnostic database read in.
ODX-LINK makes ODX configurations (ODX databases and the corresponding default window configurations) available to available standard diagnostic protocols (OBDonCAN and OBDonUDS) in the form of INCA export files (to be found in ETASData\INCA7.6\export\ODX).
Please note, however, that these ODX configurations may not actually suit all diagnostic services of the ECU used, as the diagnostic services of many ECUs deviate from the relevant standard diagnostic protocol. ECU-specific fault memory entries and environment data in particular are thus not part of these sample configurations.

The "OBD" User View

Unlike other diagnostic protocols, the OBD standard defines which services there are, how they are to be parameterized and which responses they supply.

This is why it is possible in the application case "OBD" to use a specific ODX project and preconfigure the "OBD" user view entirely for this project.

When the "OBD" user view is opened, a check is made to see whether all the necessary services and parameters etc. exist in the ODX project currently being used by ODX-LINK. If this is not the case, an error message is issued. In this case, the "OBD" user view is opened but cannot be used with the current database.

Note
The "OBD" User View can only be used with the ETAS OBD-ODX database ETASData\ODX7.6\Projects\OBDonCAN_ETAS_SAEJ1979<Version>.pdx and OBDonUDS_ETAS_SAEJ1979<Version>.pdx. The database is also contained in the INCA export file: ETASData\INCA7.6\export\ODX\OBDonCan.exp64 and ETASData\INCA7.6\Export\ODX\ODXTestDevice_OBDonUDS.exp64.

Default Configurations

The configuration of a user view can be saved as a default setting by selecting the Save as default button in the relevant window.

When you have made a configuration for the first time, you are prompted to specify whether you want to save these changes as the default setting when you close the user view. These settings are saved as part of the ODX configuration and are valid for all GUIs of one type.

This guarantees that ODX project-specific settings in the relevant GUIs do not have to be started from scratch every time.

Snapshots

All current results of the service requests which you define with user views, can be saved via a Snapshot function. You decide for each individual user view whether its result should be included in the snapshot file. The relevant information can be found in the configuration settings of the individual user views.

The snapshot icon – a small camera – at the very left of the title bar of each user view window shows that the results of this user view are recorded in the snapshot. For more details on the snapshot function, refer to the section Snapshots.

Names of User Views

If several user views of the same type but with different configurations are used in an experiment, they can be given different names (with the exception of "Hex Service").

To do this, select Configure and enter the desired name in the "Window Name"box.

Showing the Services in Function Classes

The services can either be displayed as a list (see left of the figure) or in functional classes (shown by a folder) in a user view window (e.g. Diagnostic Services):

To configure service display

Select Options>Users Options>Open from the INCA main menu.
The window for setting user options opens.
Select the "ODX" tab.
Select "Yes" or "No" with the option "Show Functional Classes".

A service is assigned to a functional group by the author of the ODX project data.