Diagnostics(DTS) tab¶

The Diagnostics(DTS) tab shows available diagnostic services including their request and response parameters for the control units defined in the test configuration. The tree-like display resembles the one used in the Windows explorer and can be browsed through accordingly. Via the context menu (by right click) diagnostic test steps, steps to allocate request parameters and to read and evaluate response parameters can be inserted.

The nodes of the first level in the tree display of the Diagnostics(DTS) tab correspond to the control units. A control unit possesses an entry if it has been assigned, in the test configuration, a diagnostic DTS port and a logical link in the corresponding ODX database. If there is no control unit with diagnostic port, the complete Diagnostics(DTS) tab remains faded out.

Below a control unit node the diagnostic services are shown which can be carried out through the corresponding logical link. Subordinated to every service are a request node and the corresponding response nodes. Names and numbers of response nodes vary as to diagnostic service (there are service nodes without response, too).

All request and response nodes comprise exactly two sub nodes: PDU and parameter. They represent the two different ways of displaying a request or response: technically as a ByteStream or logically as a data structure. Every parameter node contains sub nodes corresponding to its data structure.

Create a diagnostic test step

In order to insert a DTS diagnostic test step the diagnostic service to be executed is first marked in the Diagnostics(DTS) tab, and the command Execute is right-clicked in the context menu. A parameterization dialog appears. Now the user can modify the settings of request parameters in the section Parameterization. Confirmation by OK eventually inserts the new test step into the test case.

Diagnostic test steps are functional test steps. They possess an IN and an OUT block. The IN block contains test steps for writing which are attributed to the parameters or, alternatively, the PDU of the request. Those test steps for writing were already created automatically when the diagnostic step was installed. They can be edited directly (double click; context menu Edit) or indirectly via the input dialog of the containing diagnostic step. Writing steps can be deleted from or added to the Diagnostics(DTS) tab through the context menu of a request parameter.

The OUT block contains test steps for reading by which the parameters or - alternatively - the PDU of the responses delivered by the service call can be read and evaluated. The reading steps can be added to the Diagnostics(DTS) tab and parameterized through the context menu of the corresponding parameter node.