Open Test Framework  
Solution Settings

Solution Settings are valid for the scope of a solution. In other words they are valid for all projects inside a solution. Solution Settings will be stored with the solution. To adjust the Solution Settings right click at the solution node (root node) in the Solution Explorer and select the Properties menu entry.

Inside the Solution Settings the following settings can be managed:

  1. Startup Project
  2. DiagCom (ODX Diagnostic Data) settings

Related Topics:

Startup Project

Inside this dialog one project can be set as the startup project of the current solution. The Startup Project will be executed if the user start the solution.

The change the startup project select the radio button of the related project.

Note: The startup project can be also selected by right clicking at the related project inside the Solution Explorer.

DiagCom (ODX Diagnostic Data) settings

The OTF uses the OTX-DiagManager API for diagnostic communication. The general settings for the DiagManager are made in the Runtime Environment Settings. However, there are also settings that only apply to one solution. These settings are described below.

  1. Usage of Diagnostic Runtime System
  2. Diagnostic Database (ODX)
  3. PDX Converter (DSA MVCI Server)
  4. Diag Validation Groups Settings

Usage of Diagnostic Runtime System

In principle, OTX sequences can also be created without vehicle diagnostics. The use of the diagnostic runtime system can be switched on and off via the switch button.

Note: If the use of the diagnosis runtime system is switched off, all diagnosis-relevant extensions are hidden in the OTF.

Diagnostic Database (ODX)

To use the diagnostic runtime system, ODX diagnostic data is required, which can be set here:

  1. ODX Project
    All available diagnostic databases (ODX) are listed in the ComboBox. One database must be selected.
  2. ODX Vehicle
    All available vehicles in the selected database are listed in the ComboBox. One vehicle must be selected.
  3. DoIP Support active
    In the CheckBox you can select whether communication should take place via DoIP. If the vehicle name contains the string "doip", the CheckBox is automatically selected.

Note: The ODX tree is only available in the toolbox once an existing database and vehicle have been selected.

PDX Converter (DSA MVCI Server)

In case the DSA MVCI Server is used, all the PDX files (ODX data) can not be used directly and they have to be converted via the button "Convert...". The result of the PDX file conversion shall be displayed in the Output panel. The "Additional Optional Arguments" text box allows you to add the arguments used in PDX conversion, its default value is "-consoletrace 1 -ignoreerror 0" which means "write console trace = yes, ignore error = no ". After the conversion, you can select the newly converted ODX Database in the "Diagnostic Database (ODX) section" to use.

Diag Validation Groups Settings

A Diag Validation Groups (DVG) enable the validation of links to ODX if the access path is unknown at design time. The DVG will be stored inside a file with extension .dvg inside the DVG folder. The DVG folder can be adjusted inside global OTF settings. Here a DVG file, which is valid for the current solution can be selected.

  1. DVG file used
    All the DVG files in the DVG folder are listed in the ComboBox. The selected DVG file is valid for the solution.
  2. List of existing DVG files
    All DVG files in the DVG folder are listed in the ListBox. The selected DVG file is valid for the solution.
  3. Rename Button
    The DVG file selected in the ListBox can be renamed.
  4. Import Button
    A DVG file can be copied to the DVG folder.
  5. New Button
    A new DVG file can be created in the DVG folder.
  6. Edit Button
    The DVG file selected in the ListBox can be edited, see Editing. Double-clicking the file does the same.
  7. Copy Button
    The DVG file selected in the ListBox is copied.
  8. Delete Button
    The DVG file selected in the ListBox is deleted.