OTX Runtime

Runtime Environment for Integration into any Target System

Simple and high-performance execution of OTX in any target system with optimal integration for most application scenarios. Stable and proven with thousands of installations in production, and as an on-board tester in vehicles since 2018.

Request a demo version

User documentation

With APIs for:

CPP

JAVA

Supported platforms 32/64 bit:

Windows

Linux

Android

Embedded

Supported file formats:

PTX file

OTP Player-Datei

Run OTX Efficiently Everywhere

Product overview

The OTX Runtime is a programming interface (API) for the simple, fast, and reliable execution of OTX procedures (PTX files) in custom applications, outside of the OTX development environment. It runs on Windows and Linux. Communication with the ECU takes place either via an MVCI diagnostic runtime system (ISO 22900-3) or via an SOVD server (ISO 17987). The OTX Runtime offers extensive options for seamless integration into existing systems and infrastructures.

Designed for use in any target system

The OTX runtime is written in native C++ and can therefore be integrated into virtually any target system. APIs in C++, DotNet, and Java are available for integration. Interfaces are also provided that allow users to override the default implementation for accessing external systems (for example, via the OTX extensions HMI, Measure, ExternalServiceProvider, and Logging). For example, OTX can be used to call any method in a test bench DLL or display a GUI screen in a test system.

1st generation

Code generation
Runner in native Java

2nd generation

E-SUV, embedded
Code generation
Runner in native C++

3rd generation

Optimized code generation for maximum embedded performance
SOVD and JSON support

2018

2023

2026

The OTX runtime is continuously optimized for performance and memory consumption, especially for use in embedded systems. The graphic shows the successful use of the OTX runtime as an on-board tester in vehicles.

Main Functions at a Glance

Load OTX Projects

PTX/PPX files, signed or encrypted

Performance Optimized

Suitable for embedded systems

Long-term stable

Continuous operation without restart

SOVD Diagnostic Communication

Service-oriented vehicle diagnostics

Browsing the Project Structure

Determining the executable elements

Multiple Thread-Safe and Multi-Instance Capable

Parallel and scalable processing

Isolated and Scalable

Execution in a separate process

Highly Integrable

Connection to External Systems

Code Example

The following simplified example code shows how to load a PTX file and execute an OTX procedure in a DotNet application:

using OpenTestSystem.Otx.Runtime.Api ;

// Declare runtime manager

IRuntimeManager rtm = null ;

// Create runtime manager instance

rtm = CreateSocketRuntimeManager ( 0 , 8888 );

// Load PTX file

IProject proj = rtm. LoadPtx ( "C:\\HelloWorld.ptx" );

// Get the main procedure of the startup document

IProcedure proc = proj.MainProcedure ;

// Executes the procedure synchronously

IRuntimeContext rtc = rtm.Execute ( proc );

Request a demo version or price indication

Main functions

The OTX Runtime offers you numerous tried-and-tested features that effectively support you in your daily work. We are continuously developing the OTX Runtime – with a focus on quality and user benefits.

Do you have ideas or requests for new features? We look forward to hearing from you!

Load OTX Projects

PTX/PPX files, signed or encrypted

The OTX runtime can load and process standardized, executable PTX files and PPX files. For sensitive information, the files can be signed or encrypted. A file can only be executed if the signature is correct.

Browsing the Project Structure

Determining the executable elements

The project structure can be used to select the procedure to be executed, to determine and set the procedure parameters, and to read and write status and context variables.

Configuring the Settings

Configuring project properties

The project properties for the various extensions, such as the ODX data to be used, the logging settings, or the translation libraries, can be edited in the OTX runtime. Existing default settings from the PTX file are overwritten.

Performance Optimized

Suitable for embedded systems

The OTX runtime is written in native C++ and was developed for maximum performance and optimal integration. To further increase performance, the OTX code is compiled for execution.

Synchronous and Asynchronous

Procedure execution

Procedures can be started synchronously and asynchronously. With synchronous execution, the current thread waits until the procedure has completed. With asynchronous execution, the end of procedure execution can be determined via registered events. With asynchronous execution, multiple procedures can also be started simultaneously.

Multiple Thread-Safe and Multi-Instance Capable

Parallel and scalable processing

Multiple instances of the runtime manager can be created. The runtime manager is responsible for synchronous and asynchronous execution, as well as monitoring the started procedures. Each instance is independent and thread-safe.

Long-term stable

Continuous operation without restart

The OTX Runtime API is designed and tested to operate reliably over long periods of time—both technically and in terms of its interface. It has been running stably and robustly in production and in vehicles for many years.

Isolated and Scalable

Execution in a separate process

Each procedure launched via the OTX Runtime API runs isolated in its own process, which communicates with the API via interprocess communication (IPC). This enables a clear separation between the integrating application and the API, makes the OTX Runtime easily scalable, and improves application stability. If starting new processes by the application is not possible for security reasons, the procedure can also run in an application thread.

MVCI Diagnostic Communication

Standardized diagnostic runtime system according to ISO 22900-3 (MVCI, ODX)

Communication with the control units is handled via the DiagManager, which is also available as a standalone solution. This enables multi-client access to a standardized diagnostic runtime system according to ISO 22900-3 (MVCI, ODX). All communication types, such as physical or functional addressing and DoIP, are supported. Integrations for diagnostic runtime systems from five different manufacturers are currently available. Users can also integrate their own diagnostic runtime system via published interfaces.

SOVD Diagnostic Communication

Service-oriented vehicle diagnostics

The OTX runtime supports the new SOVD standard according to ISO 17978 for service-oriented vehicle diagnostics. A web-based REST API provides direct access to any user-defined SOVD server. This server is typically located in an HPC control unit within the vehicle.

Highly Integrable

Connection to External Systems

The API provides interfaces for accessing any functions in the environment, such as methods of a test bench DLL or GUI windows (screens) in a production system. These external systems can be accessed from OTX via the OTX mapping.

Conditional Execution

Depending on battery or ignition status

The MVCI diagnostic runtime system can query the status of the vehicle's battery and ignition (clamp 30 and clamp 15). When starting a procedure, the expected status can be set, for example, to "ignition ON." Execution of the procedure will then wait until the ignition is turned on.

Controlled Execution

Pause or Stop Execution

A RuntimeContext object is created each time the program is executed. This object can be used to retrieve runtime information and to pause or prematurely terminate a running process.

Execution with Timeout

For predictable performance and resource conservation

When starting a procedure, a timeout can be set. If this timeout is reached, execution is terminated and the procedure returns with a timeout error.

Creating Profiler Files

To optimize runtime performance

Profiler files can be generated to identify and optimize performance hotspots. These contain the timestamp, average CPU load, and average memory usage of each executed OTX activity. This slows overall performance on a standard PC by approximately 10%. The files can be evaluated in the Open Test Framework.

Compatibility Handling

Make sure everything fits

Using built-in compatibility management, the OTX Runtime API ensures that only compatible versions can be processed. It checks whether the loaded PTX/PPX file is executable with the OTX Runtime version.

Tracing

Logging of execution for troubleshooting

For troubleshooting, the OTX Runtime API offers extensive logging capabilities at all levels. These can be configured based on the level of detail, file size, and number of files.

Delivery

Windows and Linux in 32 and 64-bit

The OTX Runtime API is delivered in four configurations: Windows 32-bit and 64-bit, and Linux 32-bit and 64-bit (Ubuntu, gcc). Other configurations are available upon request.

Reference Application

Using the OTX Runtime API without integration

All properties, methods and events of the API can be tried out and tested using the included reference application, which is also available in the source code.

User Documentation

For beginners and experts

The extensive user documentation with many practical examples helps both when working with the OTX Runtime API for the first time and as a reference for experts.

OTX Extensions

OTX consists of a core and OTX extensions. The core describes all the elements necessary for a programming language. OTX extensions extend the core with general or domain-specific functions.

Alphabetical List of Supported, Standardized OTX Extensions

The following overview lists all supported, standardized OTX extensions alphabetically. Detailed information on the individual extensions can be found in the User Documentation.

Assertion

Assertions can be used to ensure the correct implementation of OTX test sequences. An assertion states that a specific condition is met during OTX execution. For detailed validation of the OTX test logic, the significantly more comprehensive Unit Test Extension is recommended.

BusMonitoring

With the BusMonitoring extension, communication data (frames) of the diagnostic bus system used can be recorded and processed.

CommonDialogs

The Common Dialogs extension provides common, frequently used dialogs, for example "File Open Dialog".

DataType

The DataType extension provides the user-defined data types "Enumeration" and "Structure" as well as the data type "ResourceLocation" for resource management.

DiagConfiguration

Allows you to change the diagnostic runtime system (ODX) data during runtime.

EcuConfiguration

To support ECU configuration or variant coding (ECU CONFIG container in ODX). Variant coding describes the data elements and configuration process of an ECU.

EventHandling & EventPlus

Extension for processing events. Event sources can be defined and events can be waited for.

File

Read and write access to any binary or text files.

HMI

Actions and terms for interacting with a graphical user interface (GUI). Basic dialogs and free screens are supported, which can be bound to any implementation (WPF, HTML, etc.) via OTX mapping.

Job

Access to the job API of an ISO 22900 standardized diagnostic runtime system (MVCI).

Math

The Math extension adds mathematical operations such as sin, cos or log to OTX.

Persistence

The Persistence extension is used to store and restore runtime information. The OTX runtime is responsible for storing the value of a variable and ensuring that the stored value can be restored to the same variable later.

Range

The Range extension introduces a new data type for describing validity intervals.

SQL

Read and write access to SQL databases.

StringUtil

The extension provides a collection of operations for string processing.

Util

The Util extension extends OTX with general convenience functions.

XML

The extension enables reading and interpreting XML documents from the file system or other sources. It enables editing existing documents and creating new ones.

i18n

For translating strings, units and values for language and regional adaptation (internationalization).

BlackBox

The BlackBox extension defines a container data type for transporting objects with a data type unknown within OTX. This is typically required for communication with any external system.

ComInterface

The OTX ComInterface Extension enables access to a vehicle interface (VCI) at runtime, for example for selecting a DoIP interface.

DataTime

Basic functions for working with dates or millisecond-accurate time.

DiagCom & DiagComPlus

Basic diagnostic communication via a standardized diagnostic runtime system (MVCI) according to ISO 22900-3.

DiagDataBrowsing & DiagDataBrowsingPlus

The extension enables detailed browsing of diagnostic data at runtime. It uses the database interface of a diagnostic runtime system standardized according to ISO 22900-3.

EcuStateChart

Access to information from diagnostic sessions and their representation in a state machine.

ExternalServiceProvider

Universal interface for accessing any external systems, such as a DLL for test bench control or a Lua script. The interfaces can be mapped to real systems using OTX mapping.

Flash & FlashPlus

The extension enables reading hex data blocks from a flash session within an ODX configuration. The data is transferred to the control unit via diagnostic services; see DiagCom extension.

JSON

The JSON extension enables reading and interpreting JSON data (defined in RFC-8259) from files or directly from strings. It allows modifying existing data and creating new data.

Logging

The logging extension provides functions for writing log messages to log files.

Measure

The Measure extension provides general access to any measurement and control systems (devices) that can be linked to real systems via OTX mapping.

Quantities

The extension extends OTX with the new data types Quantity and Unit. Quantity is derived from Float. These contain information about the physical unit of a value and thus enable the description of actual measured values and their conversions.

SOVD

Extension for accessing an ISO 17978-standardized SOVD server for service-oriented vehicle diagnostics. Using a modern REST API, SOVD offers, among other things, browsing and executing diagnostic operations on an HPC in the vehicle.

StateMachineProcedure

The extension extends OTX to describe a state machine as an alternative to a sequence.

TestResultHandling

The TestResultHandling extension provides functions for the structured capture, evaluation, and persistent storage of test results, e.g., measured values.

VehicleInfo

The extension provides access to information about the vehicle network architecture (VEHICLE-INFO-SPEC container in ODX).

ZipHandling

The ZipHandling extension enables the packing and unpacking of ZIP containers.

Alphabetical List of Supported Proprietary OTX Extensions

The following overview lists all supported proprietary OTX extensions alphabetically. Proprietary OTX extensions were developed by EMOTIVE and not by the OTX working group. Detailed information on the individual extensions can be found in the user documentation.

Can't find the feature you need? Talk to us!

PduSimulation

The PduSimulation extension extends OTX to simulate diagnostic communication at the PDU level. PDU stands for ProtocolDataUnit and expresses the HexByteField of a request or response. This makes it possible to individually influence diagnostic communication for each test case or to explicitly generate errors. See also the UnitTest extension.

UnitTest

With the UnitTest extension, OTX procedures can be validated for their expected behavior using test procedures and their test cases.

Supported Standards

The following ISO standards are supported:

ISO 13209-3:2012
The OTX Core data model is fully supported
ISO 13209-3:2012
All standardized OTX extensions are supported
ISO 13209-4:2021
All included OTX extensions are supported
ISO 13209-2:2022 2nd. ed.
Die zweite Edition des Standards wird vollständig unterstützt.
ISO 13209-3:2022 2nd. ed.
The second edition of the standard is fully supported
ISO 13209-4:2024 2nd. ed.
The second edition of the standard is fully supported
ASAM OTX Extensions 3.3.0
The third edition of the standard is fully supported with version 9 of the OTF. Until the ISO standard is published, version 3.3.0 of the "ASAM OTX-Extensions" standard, which has the same content, will be used.

Indirectly Supported Standards

The following ISO standards are indirectly supported by the respective OTX extensions:

ISO 22900-3
MVCI - Diagnostic server application programming interface (D-Server API)
ISO 22901-1
Open diagnostic data exchange (ODX)
ISO 22900-2
MVCI - Diagnostic protocol data unit (D-PDU API)
ISO 17978-3
Service-oriented vehicle diagnostics (SOVD) - Application programming interface (API)

APIs for:

CPP

JAVA

Windows

The OTX runtime is fully compatible with Windows 7, Windows 8/8.1, Windows 10, and Windows 11. The application is delivered in 64-bit and 32-bit versions.

Requirements

Installed Microsoft Visual C++ Redistributable 2015 or higher
For communication with the ECUs, the standardized diagnostic runtime system of a third-party manufacturer (MVCI and/or SOVD) must be installed.

Recommended configuration

Intel I7 class CPU - 2.8 GHz or better
16 GB RAM
Windows 11

API for:

CPP

Linux

The OTX runtime is compiled and tested on Ubuntu Linux with a gcc compiler and cmake, and is delivered in 64-bit and 32-bit versions.

Please contact us if other configurations are required.

Requirements

For communication with the ECUs, the standardized diagnostic runtime system of a third-party manufacturer (MVCI and/or SOVD) must be installed.

Minimum system requirements

CPU with 2 cores and 1.5 GHz
1 GB RAM
Free ROM memory approx. 150 MB

Learn more ...

Licensing

The OTX Runtime API is licensed using a key provided in the application's source code; see Licensing . Without a valid key, the OTX Runtime cannot run. No additional activation is required.

LicenseManager . SetLicenseKey ( "XXXXX-XXXXX-XXXXX-XXXXX-XXXXX" );

Learn more

Request a demo version or price indication

Single-user license

A single-user license allows unlimited use of the software on one piece of hardware. The license is personal. The OTF development environment includes a runtime license.

Additional product support & maintenance 20% of the list price per year
Outside Europe, the first year of support and maintenance is mandatory
Time-limited trial license available

Volume license

For the use of the license on a specific target system.

Target system bound
Minimum 100 licenses
Separate support and maintenance contract required

Framework agreement

The framework agreement allows the temporary use of the software on multiple hardware systems.

From 100 licenses for at least 1 year
35% of the individual list price
Support and maintenance included
During the contract period, the number of licenses used may be exceeded by up to 50%. For the next service period, the number will be calculated based on actual usage.

OTX Runtime

Runtime Environment for Integration into any Target System

Run OTX Efficiently Everywhere

Product overview

Designed for use in any target system

1st generation

Code generation

Runner in native Java

2nd generation

E-SUV, embedded

Code generation

Runner in native C++

3rd generation

Optimized code generation for maximum embedded performance

SOVD and JSON support

2018

2023

2026

Main Functions at a Glance​

Load OTX Projects

Performance Optimized

Long-term stable

SOVD Diagnostic Communication

Browsing the Project Structure

Multiple Thread-Safe and Multi-Instance Capable

Isolated and Scalable

Highly Integrable

Code Example

Main Functions at a Glance