Open Test Framework - Project Settings
- 1 Overview
- 2 General settings
- 3 External Applications settings
- 4 References settings
- 5 DiagCom (ODX Diagnostic Data) settings
- 6 Logging settings
- 7 i18n settings
- 8 Quantities settings
To run a test sequence, both the OTX documents and the settings related to the OTX extensions used in the test sequence are taken into account. The Project Settings are all the settings which supports the designtime and the runtime of the OTX test sequences within that project.
The Project Settings do not only specify the general settings such as backup files location, project version, used Meta-Data layout file, references to other projects etc. but they also specify the detail settings which are used for specific extensions such as HMI extension, Measure extension, DiagCom extension, Logging extension, i18n extension and Quantities extension.
You can access the Project Settings of a project by right-clicking on the corresponding project node in the solution explorer and select the "Properties" menu entry, the Project Settings dialog box will be displayed for users to configure the project settings. The Project Settings dialog box provides a centralized place for managing project properties and resources. It contains several pages that are accessed through tab entries on the left panel. By clicking on a tab entry on the left panel (e.g. "General", "External Applications" etc.), you can access the corresponding settings page on the right panel. You can adjust the settings in many pages and click OK button, and all the changes shall be applied.
The introduction and guidelines for each settings page are described in the following sections.
In this section, you can set the location path to store the backup OTX documents. Each time you start a sequence in the project or build the project, all the OTX documents including the contain OTX packages are copied to the storage folder. This helps to recover OTX documents in case the documents are unexpectedly changed, damaged or deleted at design-time. You can input the location path directly or browse for the folder via the "Browse" button.
Version Number section
For the purpose of sharing the project and tracing the modifications, you can set the version for the project manually by enter a number into each digit text box, or it can be done automatically by checking the "Bind last digit to SVN revision number" check box if the current project is under the version control (click here for more information).
Import Meta-Data Layout section
Here you can select a Meta-Data layout (*.xml) used in the project. You can then add the template Meta-Data for the documents, procedures or activites from the added layout. You can input the path of the Meta-Data layout file directly or browse for the folder via the "Browse" button. If you want to import the layout file into the project folder for exchanging the project purpose, you can check the "Import inside the project" check box.
After Build section
Here you can input the location path for the PTX storage folder directly or browse for the folder via the "Browse" button.
External Applications settings
This page allows to manage the OTX-Mapping of the current project (click here for more information). There can be many mapping files stored in the project but only one mapping file can be used at a time. Here you can select to use the OTX Mapping or HMI Mapping by checking on the corresponding radio button. After selecting OTX Mapping or HMI Mapping, you can select a mapping file which shall be used for the current project in runtime through the corresponding combo box.
All the available mapping files of the current project are displayed in the sub-panel (the old HMI Mapping files are not displayed here but they can be still selected in the HMI Mapping combo box). You can use the buttons below the sub-panel to manage the mapping files. Please note that you can only select and edit one mapping file at a time.
Normally, the OTX documents in the current project can only import documents within the same project (Cross-Document reference). To import and use the global elements from the documents in another project, you need to add reference to that project (Cross-Project reference). Click here for more information.
The referred projects can be classified into 2 types: the internal projects (the local projects in the current solution) and the external projects (the PTX libraries). Here in this page you can find the 2 sections with sub-panels corresponding to the 2 types of referred projects.
Internal Projects section
Here you can find all the available local projects of the current solution, each having a check box. You can add or delete a reference to a project by checking or unchecking the corresponding check box. When this settings page is loaded, the check boxes of the referred projects are already checked.
External Projects section
A PTX library is a zipped OTX project with access to all the public elements such as validities, signatures, global declarations and procedures to be used in another project (click here for more information of packing a project into a PTX library). In this section, you can see all the referred PTX libraries displayed in the sub-panel. Above the sub-panel, you can find the Add (+) button to add reference to more PTX libraries, or the Delete button (X) to delete the selected PTX references in the sub-panel , or the "Convert to relative Path" button to convert a PTX reference path into relative path (conversion to relative path only has effect on references with absolute path in the same disk partition with the current project). You can also import the referred PTX libraries from outside into the project folder by using the "The libraries are stored inside the project folder" check box under the sub-panel. When the check box is checked, a check box shall appear at the left of each PTX entries, the PTX libraries with the checked check box shall be imported into the project folder.
DiagCom (ODX Diagnostic Data) settings
In this page, you can determine whether the current project uses the Diagnostic Runtime System or not, change the used ODX Database or set the ECU Groups used in design time validation.
Diagnostic Runtime System (MVCI) section
You can use the switch button to turn ON/OFF using the Diagnostic Runtime System. When it is switched OFF, all the sections below this section shall be hidden. If a project does not use the Diagnostic Runtime System, it can be used and executed even in a machine with no Diagnostic Runtime System.
When the switch button is ON, the current Diagnostic Runtime System (MVCI) selected in the MVCI Configuration program shall be used and its ODX Databases shall be updated in the "Diagnostic Database (ODX)" section.
Diagnostic Database (ODX) section
In this section, you can access the database part of the current Diagnostic Runtime System (MVCI). To select and configure the MVCI Server, please open the MVCI Configuration program by clicking on the corresponding button in the Status Bar (or clicking on the "Open" Configuration Program button in the "Diagnostic Runtime System" tab of the OTF Options menu).
To set and use an ODX Database in the project, you must first select the database project through the "Project" combo box and then select the vehicle within the database project through the "Vehicle" combo box.
PDX Converter (DSA MVCI Server) section
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.
ECU Groups section
In variant identification, the actual ECU variant is known only at runtime. In order for the process to be validated at design time, all possible ECU variants can be specified in groups. This section allows you to define the ECU Groups and the ECU variants in each ECU Group.
The following rules are applied during validation:
This section contains a menu bar and a panel displaying the specified ECU groups. Please note that all the controls in this section are disabled if the ODX Database has not been selected yet i.e. "None".
Below are the buttons with their descriptions (according to their position in the bar from left to right):
ECU Variant List panel
This panel displays the specified ECU variant list existed in the DiagCom project settings file (*.otfDiag). Here you can only select one element at a time, this element can be modified with the menu bar above.
This page allows you to specify the behavior of the explicit logging i.e. using the WriteLog activities of the Logging extension or the behavior of the implicit logging which automatically saves runtime traces, exceptions or activity IDs etc.
Below are the controls in the Logging settings page with their descriptions (according to their position in the bar from left-to-right and top-to-bottom):
In this page, you can configure the Text Blocks Library for the i18n extension. The text library is an actual storage folder for the language files (*.ini). Each language file corresponds to a language and stores the data of that language.
Text Library Editor
This dialog box consists of a command bar above and a gridview displaying the data of all the language files below.
This command bar help you to edit the selected language data, below are the controls in the command bar with their descriptions (according to their position in the bar from left-to-right):
Language Data gridview
In the gridview, you can change the name of the categories and the translation keys, or the values of in each language by double-clicking on the corresponding cell and entering new texts (or you can select one entry and press F2 key). Here you can select one or many entries of the same type (i.e. same category type, or translation key type) by using the CTRL- or SHIFT-key and mouse click. The selected entries shall be edited with the controls in the command bar above or you can also manage them directly in the gridview such as moving selected entries with drag-and-drop, or copying keys from a category to the others with drag-and-drop and the CTRL key.
In this page, you can manage unit libraries (the ODX UNIT-SPEC containers) which support in calculating values with units in the current project (see Quantities extension).
Below are the elements in this page with their descriptions: