The Open Diagnostic Framework (ODF) is a development environment for ODX / OTX-based applications with these features:

ODF - Highlights & Design Features

• Data-driven solution for the entire diagnostic process chain

  Only with OTX is liaison with ODX a complete, data-driven solution for the entire diagnostic process chain can be obtained. The diagnostic development process becomes more reliable, easier and more productive.

• Specification, design, validation, documentation, testing and implementation of OTX sequences

  From the specification to the generic production of diagnostic tests, the entire development process are illustrated.

• Independent of the diagnostic run-time system

  Through an internal layer of abstraction any standard but also proprietary diagnostic runtime systems can be integrated.

• Complete new development

  The ODF has been developped for the OTX standard and is entirely new. The design is based on more than 10 years experience in vehicle diagnostic tools. There are no historically related compromises. Therefore, the architecture is slim, of high-performance and robust. The user feels an extremely short startup time of the application of less than 4 seconds, or in the relatively small space requirement on the hard disk.

• Links and generate GUI / HMI (Surface)

  For the production of generic diagnostic testers, the OTX sequences can be bound to graphical interfaces. We have an abstraction layer that allows to support various so-called screen implementations. The ODF will include a screen implementation for the Windows Presentation Foundation (WPF). Without implementation, the screen input and output are displayed in an unformatted way in a grid control.

• OTX-performance processing and very large databases

  Since OTX projects can be quite large, we have put much effort in the processing of large databases. With approximately 10,000 sequences, the OTX database is about 1 GB large. Our XML database is at these specs still far from their limits. Several TB of data can be processed at high performance and maximum protection of resources. Only those parts are held in memory which are currently in use. For the user it is almost irrelevant whether he is working with a large or a small OTX project.

• Natives and direct work on data-OTX (No import / export!)

  An OTX import and export may be implemented quickly for existing systems. However,experience shows that such systems encounter problems in practise, as the data models of OTX and existing proprietary solutions are not 1:1 compatible. Unfortunately, these problems are rarely detected early and may only be found in a later stage of the project. Since you can not draw back from there, the result is usually a workaround with all its consequences. Again, we make no compromises! The ODF is working directly on the XML data. There is no transformation, and no import or export.

• On-the-fly Code Generation

  The runtime system generates program code. At this time we have C#, but it is also possible later to generate other code (Java, Python, VB, etc.). The code is simple, slim and corresponds to the code of an expert for diagnostic procedures. The code can be generated on-the-Fly, translated and executed. Compared to a conventional drain interpreter, this has three advantages:

  1. Code offers the best performance and is therefore suitable for control and regulation tasks.
  2. Precompiled processes can spread extremely compact and thus have minimal resource requirements. needed for the above-described 1 GB OTX data yield about 1 MB binary data.
  3. In addition to the normal PC any target systems such as Pocket PC, browser, and tablet PC may be used.

• Flexible deployment as a stand-alone application or SDK

  We try to be flexible to adapt to the often hetrogenen customer requirements. Therefore, we not only the ODF as a stand-alone application with a modern user interface available, but also offer our own use SDK (API SDK OTX, OTX OTX SDK and Runtime Design SDK) for integration in their own projects .

• User group adaptation and Concepts for complexity reduction
  

  Due to the usually heterogeneous landscapes in the different areas of development, production and service and the different perspectives and requirements, we use several effective approaches to adaptation to the user group and to reducing and managing the complexity.

• User-specifically extendible at almost each layer

  In addition, the Open Diagnostic Framework adaptable to almost any level, to the different requirements. The open interfaces allow a virtually unlimited extension of functionality through code.

In addition,

• Pre-coding

  To create variables you don\'t have to go back but you can add variables where ever needed.

• References adjustment
  

  With the change of names, all these references are automatically adjusted project wide.

• Object search

  The object search refers, for example, all the places in which the variable is "abc" is used.

• Undo/Redo

  Operations can in any depth in both the designer and in the Solution Explorer.

• Development environment in German and English
  

  Other languages ​​can easily be integrated.