![]() |
Open Test System
|
|
The frequently ask questions (FAQ) provide immediate answers to common questions without requiring users to search extensively.
The list of supported OTX extensions and the supported standard versions can be found here: Supported OTX Standards.
The software can be downloaded either from the EMOTIVE License Portal or from EMOTIVE Issue Tracking System (Redmine). The license portal contains the latest released version. In Redmine all versions can be found, including beta versions.
No, the software is based on, see ISO standards. A standardized diagnostic runtime system is necessary for diagnostic communication. EMOTIVE currently does not deliver a diagnostic runtime system. The diagnostic runtime system must be installed separately. Diagnostic runtime systems from various manufacturers are supported. For more information, please contact EMOTIVE Support.
OTX is an ISO standard and therefore freely available. However, the ISO standard is written more for a tool manufacturer than for the user. The user's view is described in the OTX Reference. But, if you want to be on the safe side or if you want to implement your own tools for OTX, then we recommend buying the latest version of the standard from ISO, see Related Standards.
Note: The application of OTX in an automobile manufacturer's processes can become very complex. This user documentation attempts to answer many questions, but cannot replace individual OTX training. We therefore recommend a 2-day OTX training course to start with OTX or to deepen it. For more information, please contact EMOTIVE Support.
We would like to provide you with the best possible support in the effective use of OTX. For details please see Support, Maintenance and FAQ.
Here you can find details about Logging and Tracing.
If the execution of OTX in the OTF is too slow, you can deactivate output windows. In particular, the output window for the Variable Trace.
Note: Please note that the OTF is an OTX development environment. The execution of OTX is therefore not runtime optimized. A lot of additional data is processed that is not processed in the OTX-Runtime API. For a runtime optimized execution, the OTX-Runtime API or the Open Test Player must be used.