 |
Open Test Framework
|
|
|
Open Test Framework
|
|
The OTF Settings enable you to configure the default settings for the working environment of the OTF. You can configure the general settings such as establishing the default location for your OTX solutions, or enabling the function to restore the last opened solution and procedures, or changing the development platform ect.
You can access the OTF Settings by selecting the File tab of the Ribbon and then selecting the Options entry, the OTF Options dialog box will be displayed to configure the OTF settings. The OTF Options dialog box contains several pages that are accessed through tabs on the left-hand side. By clicking a tab on the left pane (e.g. General, OTX Runtime System ect.) you can access the corresponding settings page on the right pane. You can adjust the settings in many pages and click OK button, and all the changes will be saved.
The introduction and guidelines for each settings page are described in the following sections.
Related Topics:
This page contains the following sections which allows you to customize the general settings for the working environment of the OTF:
In this section, you can select the display language in the OTF. The default is English. At present, the OTF only allows you to switch between English and Deustch (German).
The OTF must be restarted for the changes to take effect completely!
This section allows you to configure the behavior when starting OTF and when switching between the designer and the OTL editor.
Below are the options in this section:
In this section, you can set the default storage location for the OTX solutions. You can also enable or disable creating copy backups of the OTX documents, see the "General" settings page of the Project Settings. The check box "Export old PTX-1 format" allows you to export a project into the old version PTX library to use with the older version of OTF.
Note that if you check the "Export old PTX-1 format" check box, the "Security - PTX" section below shall be disabled, also the "Security" section of the Export Manager.
This section allows you to configure the settings for exporting PTX/PPX libraries.
Below are the controls in this section with their descriptions (according to their positions from top to bottom):
| Control | Description |
|---|---|
OTX files check box  | Enables to include the OTX folder containing all OTX files in the PTX library (checked) or not (unchecked) when exporting a project. |
| Runtime settings check box | Enables to include all emotive specific project settings in the PTX library (checked) or not (unchecked) when exporting a project. |
| Runtime-optimized binaries for DotNet check box | Enables to include the Output folder containing the compiled and executable binaries for DotNet runtime in the PTX library (checked) or not (unchecked) when exporting a project. |
| Runtime-optimized binaries for Java check box | Enables to include the Output folder containing the compiled and executable binaries for Java runtime in the PTX library (checked) or not (unchecked) when exporting a project. |
| Referenced projects combo box | Allows to select a behavior with the externally referred PTX files. |
| Store APPs inside project check box | Enables to copy all the referred external applications (from the central application folder) into the PTX/PPX library (checked) or not (unchecked) when exporting a project. |
| Open dialog when exporting check box | Enables to display the "PTX Export Manager" dialog (checked) or not (unchecked) when exporting a project into a PTX/PPX file. |
This section allows you to configure the settings for PTX/PPX library encryption.
Below are the controls in this section with their descriptions (according to their positions from left to right and top to bottom):
| Control | Description |
|---|---|
| Private key text box | Allows to specify a password to encrypt and/or sign the exported PTX/PPX library. |
| Encryption check box | Enables to encrypt the entire PTX/PPX file (checked) or not (unchecked) when exporting a project. The encrypted PTX/PPX file can only be opened by the OTX-Runtime API (DotNet/Java). |
| Protect ... with a checksum check box | Enables to protect the PTX/PPX file against an encrypted checksum (checked) or not (unchecked). The protected PTX/PPX file can be opened with the OTF or the OTX-Runtime API (DotNet/Java). |
| Has Algorithm combo box | Allows to select the hash algorithm. |
During the design time and run time, the OTF has to create some temporary files. This section allows you to clean up these temporary files from your computer free up lost space by using the "Clean up temporary files" button. You can also enable the function to automatically clean up these files after the OTF is closed by checking the corresponding check box below the clean up button.
This page allows you to set up some settings related to the run time environment. Below are the sections in this page.
Within this section the Diagnostic Runtime System used by the OTF must be selected and adjusted.
Note: Without a correctly configured diagnostic runtime system, diagnostic communication with the vehicle cannot be carried out. The OTF supports standardized diagnostic runtime systems (MVCI) from various manufacturers, see Related Standards. For more information, please contact EMOTIVE Support.
Note: In order to install and configure the diagnostic runtime system and the drivers for the VCI used (D-PDU API), expert knowledge is required, which cannot be conveyed here. Please contact the supplier of the diagnostic runtime system or VCI.
| Control | Type | Description |
|---|---|---|
| Binaries (Kernal Path) | ComboBox | Absolute path to the binaries directory of the related diagnostic runtime system. Note: This setting selects the corresponding diagnostic runtime system. Note: The OTF knows all supported diagnostic runtime systems. Therefore only the directory is necessary. Note: The "..." Button opens a file or folder selection dialog.Note: The ComboBox lists all previous used values. |
| Kernal Type | ComboBox | Type of the selected diagnostic runtime system. Note: The available values depend on the selected diagnostic runtime system. Note: If the selected diagnostic runtime system is licensed via EMOTIVE, then the license status is displayed to the right of the ComboBox. |
| Configuration (Config Path) | ComboBox | Absolute path to the configuration directory of the related diagnostic runtime system. Note: The OTF knows all supported diagnostic runtime systems. Therefore only the directory is necessary. Note: The "..." Button opens a file or folder selection dialog.Note: The ComboBox lists all previous used values. |
| Project Directory | TextBox | Diagnostic runtime system specific directory where the converted ODX projects are stored. Note: The "..." Button opens a file or folder selection dialog.Note: The "Open..." Button opens the selected directory. |
| Java VM (JavaVMPath) | TextBox | Path to the Java VM. Note: For the execution of OdxJavaJobs inside diagnostic runtime system this path can adjusted, if multiple Java VMs are installed at the system.Note: The "..." Button opens a file or folder selection dialog. |
| VCI (D-PDU-API) | ComboBox | Lists all available D-PDU APIs installed at this system to select one of it. |
| PDU length check | CheckBox | The property can be used to control whether or not a length check against the Response in the ODX data is carried out when a response PDU is evaluated. If the length check is switched on, the response PDU must fit exactly. If the length check is switched off, the response PDU can actually be longer. This supports unclean ODX data where only the response parameters of interest are data, even if a control unit sends more response parameters. |
| MVIC server logging level | ComboBox | Set the log level for diagnostic runtime system internal for error detection. |
| Diagnostic connection via | CheckBox | Select the CheckBox if the communication to the diagnostic runtime system should be established automatically.Note: Deselect it only in special cases (for experts only!). If the CheckBox is not selected:- ComboBox IPC: Selects the IPC (Inter Process Communication) to SOCKET or PIPE.- TextBox Port number or Pipe name: Sets the number of a free SOCKET port or a unique name of the PIPE. |
| Polling Time | TextBox | The time in milliseconds between the next check of the connection state during the procedure execution (Polling). The default value is 500 ms. |
| Battery Voltage Threshold | TextBox | The voltage threshold in millivolt from which the battery voltage is enough for CL30 = ON. The default value is 6000 mV. |
| DiagService Handle Mapping | CheckBox | DiagService handle mapping is needed to restore DiagService objects of closed and re-opend ComChannels when the ComChannels limit is exceeded. The mapping takes time and can be switched off, if it is not needed. |
| Trace Level | CheckBox | Trace level of the DiagManager Tracing for internal error detection. |
| DiagLogging Level | CheckBox | Level for the DiagLogging to log the diagnostic communication. |
| DiagLogging Folder | TextBox | Folder where the files of the DiagLogging are stored (ReadOnly).Note: The "Open..." Button opens the folder. |
| Kernel Logging Folder | TextBox | Folder where the log files of the diagnostic runtime system are stored (ReadOnly).Note: The "Open..." Button opens the folder. |
The OTX-Home (OTX search path) determines the base directory to which all relative path specifications refer. In this section, you can enter the search path in the text box.
The OTX search path can contain several directories separated by semicolons ";" and the placeholders "?" and "*" . You can also use the placeholder "[ProjectDir]" (e.g. "[ProjectDir]/*"). When reading, the runtime environment takes each directory starting from the left as a base for relative paths. If the file is found, the search is cancelled.
| Placeholder | Description |
|---|---|
* | Zero, one or multiple arbitrary characters |
? | Zero or one arbitrary character |
[ProjectDir] | Inside OTF: Directory of the current project. Inside OTX Runtime API: Directory in which the PTX or PPX file is located. |
Note: If no OTX search path is specified, the default value is
"[ProjectDir];[ProjectDir]/..".
Note: The first directory which is used for writing, shall not contain wildcards.
In this page, you can find all the supported OTX extensions with their licensing status. Only the full version license enables to show all of the extensions supported by the OTF.
The extensions are classified into 2 groups: the standard compliant extensions and the non-standard compliant extension (user defined extensions).
The extension settings help you hide the unused extensions in design time. To turn on or turn off an extension, please use the switch button at the left most of the corresponding extension. If an extension is turned off, the category related to that extension in the Toolbox window shall be hidden, and the related data types of the turned off extension shall not be displayed when creating or modifying a declaration, and all the entries related to that extension shall not be display in the OTL IntelliSense.
The OTF still supports loading and running the OTX documents containing elements of turned off extensions. It only prevent to create new elements related to the turned off extensions.
An add-in expands the OTF with additional functionality. The only current add-in is the Builder Checker, see picture below. The Add-In Manager can manage different versions of the Builder Checker.
| Button | Description |
|---|---|
| Add... | Opens a dialog to browse and add a new addin. |
| Select as default | Sets the selected addin as the default addin. The default addin shall be displayed in the default addin combo box in the "Runtime Environment" tab of the Ribbon (Menu Bar) menu. |
| Delete | Deletes the selected addin. |
| Open selected Addin... | Opens the selected addin in the Builder Checker program. |
The OTP Themes settings allows for configuring the typical display settings of the player monitor in design time of the OTF and in run time of the OTP, and saving the settings as theme files (*.playTheme) which can be selected and used later, or transferred to another computer.
Using so-called themes, the typical look of the OtpReference (OTP) can be adapted to the corporate identity of the company. Company-specific colors, fonts, icons and a logo can be set. Optionally, different icons can be defined for the switchable day and night design in the player.
This settings page consists of the header section, the theme content view section and the preview section.
This section contains controls to manage the themes and some elements of the themes.
Below are the controls in this section with their descriptions (according to their positions from left to right and from top to bottom):
| Control | Description |
|---|---|
| Current Design combo box | Allows to select the current theme for the player in design time of the OTF. |
| Import... button | Imports a new theme file to use. |
| Save as... button | Saves the current theme (along with the current modifications, if any) as a new theme. |
| Add icon button | Adds a new icon line into the Icon panel of the theme content view. |
| Delete button | Deletes the selected icon lines in the Icon panel of the theme content view. |
| Reset to default values... button | Resets all the current settings in the theme content view back to the default settings (defaultSilver theme). |
This section displays all the settings of the current theme. There are 4 panels inside the content view: Colors panel, Fonts panel, Logo panel and Icons panel.
You can find color pickers for each elements of a monitor (this also used for the OtpStartPage and the background of the OTP application). Each element has 2 color pickers corresponding to the Day view mode and Night view mode.
This panel allows to configure the font settings used in the monitor design time and the OTP application.
Here you can customize the OTP application with your own company logo. It allows to set logos for the Day view mode and Night view mode. If you only input a logo for a view mode, the logo shall be used for the both view mode.
Note that only the shape of the logo can be taken and used. You should save an PNG file with shape only and with transparent background; other wise, the displayed logo shall be unexpected shape e.g only a rectangle shape if you input here a rectangle image with details inside.
The logo shall not be displayed with the original color but it shall be displayed with the "Base" color in the Colors panel.
This panel displays all the including default icons in the current theme file which can be applied for the "Symbol" controls used in the players. Here you can delete the existing ones and add your new icon sets. It allows to set icons for the Enabled/Disabled Day view mode and Enabled/Disabled Night view mode. If you only input an icon for a view mode, the icon shall be used for the all other view modes.
Here you can see the general preview of the current theme settings. This helps you to observe how the modification looks in the player designer and in the OTP application immediately. However, to check the detail changes of font size, icons etc., you still have to go back to the player designer or you have to save the current theme and load it in the OTP application.
In this section the ConfigFile can be managed. A ConfigFile contains all target system-specific settings for a ControlFile. A ConfigFile can be edited in the ConfigFile Editor.
Note: All available
ConfigFilesare located in a central directory, which can be set in OtpControlFileSettings.
| Control | Type | Description |
|---|---|---|
| Directory | TextBox | Central directory where all ConfigFiles stored. |
| List | ListBox | List all ConfigFiles of the central directory.Note: Double click at a ConfigFile opens it in the ConfigFile Editor. |
| Rename | Button | Renames the selected ConfigFile. |
| Import... | Button | Imports an existing ConfigFile from outside into the central directory. |
| New... | Button | Creates a new ConfigFile. |
| Edit... | Button | Opens the selected ConfigFile in the ConfigFile Editor for editing. |
| Copy | Button | Copies the selected ConfigFile. |
| Delete | Button | Deletes the selected ConfigFile. |
The Error Reporting settings help the emotive to improve the OTF product quality. Some OTF bugs may be difficult to reproduce but the OTF has its own traces for the activities in OTF. After the OTF has been closed unexpectedly (crashes), when you start the OTF again, it shall automatically gather all the old OTF traces files and the related Windows XML Event Log (*.evtx) in a zipped file, an error report file, which is ready to be sent to emotive. With the error report from the customers, the emotive can simplified the troubleshooting.
Note that when the OTF is restarted after the crash and the Error Reporting is enabled, the current trace files shall be cut and pasted in the in the error report zipped file. The new empty trace file shall be created for the new working sessions of the OTF.
Below are the controls in the page with their descriptions (according to their positions from left to right and from top to bottom):
| Control | Description |
|---|---|
| Trace Level combo box | Allows to set the level for tracing the activities in the OTF. |
| Open Trace file folder... button | Opens the storage folder of the trace files in a new window. |
| Active Error Reporting switch button | Enables to create the zipped error report file with the OTF trace files and related Windows XML Event Log (*.evtx), when the OTF is closed unexpectedly (please refer the note above). |
| Send e-mail... button | Opens new email message window with the default mail client, already input the necessary texts such as receiver (support@emotive.de), mail title and draft content. You then need to attached all the report files and trace files, and write a brief description of the error, and send the e-mail. We recommend deleting the error report files after sending. |
| Open Folder... button | Opens the storage folder of the error report files in a new window. You can take these files to attach to the report e-mail. |
| Reload button | Updates the list of the error report files from the storage folder in the gridview (see gridview description below). |
| Delete button | Deletes the selected error report files in the gridview (see gridview description below). |
| Include trace files check box | Enables to include the trace files in the zipped error report file (checked) or not (unchecked). |
| Error Report gridview | Displays all the error report files in the storage folder with file name, created date and size. Here you can select one or more error report files (using CTRL key, or SHIFT, or mouse drag or CTRL+A) to use with the Delete button above or with the DEL key. You can also sort the error report by date by clicking on the header of the "Date" column. |
This page contains the following sections which allows you to customize the specialized settings for the working environment of the OTF:
Here you can determine to store the ADMIN MetaData of an OTX document as a seperated file in the same package folder or store within the OTX document by checking or unchecking the related check box. Its default state is unchecked.
The name of the activities (OTX nodes) in the OtfWorkflowDesigner are optional. This section allows you to enable or disable the function of automatically creating unique names for the new activities in the OtfWorkflowDesigner by using the corresponding check box.
Normally, the OTF validates the current project (and all the referred projects) before executing a workflow. If there are critical errors, the execution shall not run.
In this section, you can find the check box "No Validation before execution", this check box allows to turn off the validation (ignore the critical errors) in run time. However, critical errors signal that the OTX sequences are incomplete or ill-designed so turning off the validation may result in unexpected behavior in run time.
Here in this section, you can also add the additional schema for the OTX-Extensions which are not supported by the OTF to validate documents/projects while they are being imported into the OTF. You can manually input the path for the schema file in the related text box or use the "Browse" button to browse to the schema location.
This section related to the OTX-Viewer project of emotive which supports to view PTX libraries or OTX documents in the internet browser by adapting XSL Stylesheet for the OTX documents (click [here]OtxViewerUserDoc for more information). This section allows to adapt or clean the XSL Stylesheet in all the available documents in the current solution with the "Adapt all documents" button and the "Clean all documents" button.
This section allows to configure some settings related to the DoIP support in runtime.
This section allows to configure the global settings for the ODX Database. Below are the check boxes in this section with their descriptions:
This section allows for configure the global settings for the OTX Mapping. Belows are the setting controls in this section:
The dialog consists of a command bar and an application gridview (see the image above). The gridview displays all the available external applications in the central folder with the detailed information such as name, version, changed data and size. Here in the gridview, you can select one or many applications (using CTRL key or SHIFT key) which can be handled with the buttons in the command bar.
Below are the buttons in this the command bar with their descriptions (according to their positions from left to right):
| Button | Description |
|---|---|
| Add application... | Opens a dialog to browse and add a new application (*.dll or *.exe) into the central folder. |
| Open | Opens the global central folder in a new window explorer. |
| Delete | Deletes the selected applications. |
| Create application container... | Creates an zipped and encrypted container file (*.apc) which contains all the selected applications. The container can not be unzipped normally, it can only be decrypted and unzipped by the OTF. |
| Load application container... | Opens a dialog to browse for a container file (*.apc), and then extracts all its applications into the global central folder. |
Each execution of a UnitTest, see Test Explorer can create a TestProtocol. The TestProtocol will be stored inside a central directory which path can be adjusted here.
With this setting the path to the Web-Server for the HTML-Screen Implementation, see Web Server which should be used by the OTF can be configured.
Note: The OTF delivers its own Web-Server. This path should be only changed, if not the Web-Server of the OTF should be used.
This section allows to specify the prefix for copying and for the OTX-ID through the following text boxes: