Enables you to create, execute and test diagnostic data and sequences based on the latest international automotive standards. Helps you to ensure that the diagnostic communication as well as the actual vehicle diagnostics work reliably in engineering, manufacturing and service.
All the major vehicle manufacturers worldwide, together with their suppliers, worked on specifying and implementing a range of international standards. A standardized diagnostic runtime system is a central element in vehicle diagnostics. This ISO MVCI server makes it possible to use vehicle interfaces (VCIs) from different manufacturers and exchange them at will. The standardized data format for specifying and exchanging diagnostic data is ODX. It is independent of the bus protocols used and comprises not only the vehicle- and ECU-specific diagnostic functions ("services") but also configuration and flash data. All ECU variants, based on a standard variant, are included. Redundancies are avoided with the use of libraries, inheritance and references. The actual applications use the methods made available at the application interface. This means that they can be created without there being any need for users to have special knowledge of communication protocols or services and that they are independent of VCI and the protocols used. ECU and vehicle information is accessed using the conversion methods, service and data type descriptions contained in the ODX database. It is also possible to address a request to all ECUs of a functional group with comprehensive functionality, such as for example OBD.
| || |
But in vehicle diagnostics, not only individual services but also a large number of diagnostic and test sequences are required over and over again throughout the entire life cycle. These more complex sequences including possible user interaction cannot be described using ODX. This gap in vehicle diagnostics was closed by OTX, another standardized data format which can be run directly over an additional OTX runtime directly based on the diagnostic runtime system. The Diagnostic Tool Set comprehensively covers the vehicle diagnostics by merging ODX with OTX.
DTS Tool Family
Softing DTS - Base System
The base system comprises a full diagnostic runtime system based on the latest international Automotive standards as well as an OTX runtime environment.
Delivery Scope and Packages
For ISO MVCI Server and OTX Runtime System
Access to the programming interface of the ISO MVCI Server for individual applications
Softing OTX API RT
Enables to access the API of the des OTX runtime system as well as to execute scripts via the command prompt.
Simple access to diagnostic communication for manufacturing and test bench applications
All-in-one Engineering Tester: Enables to ensure that diagnostic communication and vehicle diagnostics work reliably.
An easy-to-use tool based on the ODX standard for flash programming of ECUs.
A PC-based tool for validating and releasing the self-diagnosis of individual ECUs or an entire vehicle in vehicle engineering.
Powerful Authoring System for ODX 2.2 and 2.0.1 for Diagnostic Experts and Developers of Vehicle ECUs
Development of Complex Diagnostic Sequences According to the Standard ISO 13209
|Standard compliance, e.g.||ISO 22901-1/ASAM MCD-2D, ODX V2.2.0 and 2.0.1 (Open Diagnostic Data Exchange),|
ISO 22900-3/ASAM MCD-3D V3.0.0 programming interface,
ISO 22900-2/D-PDU API via CAN, K-line and Ethernet (ISO 13400 DoIP/Tester - Gateway),
ISO 13209/OTX V1.0.0 (Open Test Sequence Exchange)
|VCI support||All VCIs according to the corresponding revision of the data sheet Softing D-PDU API,|
Other VCIs: All with ISO standard compliant D-PDU API software (release test required possibly),
Parallel communication: depending on type and combination ≤ 4 diagnostic interfaces (more on request)
|Simulated Interface||Enables the diagnostic functions to be tested even without an ECU|
|Protocol templates within scope of delivery||As base for protocol tests and the creation of ECU data in accordance with ISO 22900-2/D-PDU API:|
ISO_14230_3_on_ISO_15765_2, ISO_14230_3_on_ISO_14230_2, ISO_OBD for K-line and CAN,
SAE_J1939_73_on_SAE_J1939_21, WWHOBD_on_CAN (ISO_27145_3_on_ISO_15765_2)
|Databases within scope of delivery||OBD database in accordance with ISO 15031-5/SAE J1979:2012-02 for gasoline/diesel vehicles,|
J1939 database in accordance with SAE J1939,
Sample database with three ECU and detailed documentation as well as tutorial
|Runtime data formats||SOD: editable runtime format, which can be exported back to ODX|
SRD: „monolithic“ ultra-compact runtime format with closed database as with ODX/SOD,
SMR: Modular* ultra-compact runtime format (* .. for ODX categories/single ECU),
Ultra-compact runtime formats: Vehicle and flash data are 60 to 180 times more compact in comparison to ODX data (depending on OEM/data structure); optional OEM specific encryption
|Operating systems||Windows 7 SP 1 and 8.1 (both 32+64 Bit)|
|General PC requirements||Processor: type and clock (≥ 1.5 GHz) depending on the system configuration and complexity of ODX data,|
RAM: ≥ 2 GB– depending on ODX data,
For hardware interfaces: PCI-/PCMCIA slot, USB-/LAN port, wireless LAN or Bluetooth for HW interface,
For optional USB Dongle: USB port,
Screen resolution: see detailed data sheets on the relevant products
|Softing DTS.cos||ISO MVCI server incl. API access – see data sheet DTS 8 COS|
|Softing DTS.automation||Automation API access for manufacturing & test bench applications - see data sheet DTS 8 Automation|
|Softing DTS.monaco||All-in-one engineering tester - see data sheet DTS 8 Monaco|
|Softing DTS.venice||Authoring system for ODX 2.2 and 2.0.1 – see data sheet DTS 8 Venice|
|Softing OTX.studio||Development environment for OTX– see data sheet OTX Studio|
|Softing OTX.runtime||OTX runtime system incl. API access – see data sheet OTX Runtime System|
Supplementary Products and Services for the Entire Product Family
Micro USB license dongle, as an alternative to licensing on a hardware interface
Softing’s ISO 22900-2/D-PDU API compliant VCI software for selected CAN and SAE J2534/PassThru VCI as well as ISO 13400/DoIP without VCI – see data sheet D-PDU API
Parallel use of more than four VCIs (evaluation and approval required for the actually used VCI types and their combination)
Optional extension for DTS COS, Automation, Monaco, Venice or OTX Studio: Generating the modular ultra-compact runtime data format SMR (requires one-time DTS8S-SMR-SETUP)
Initial process consulting regarding the usage of the modular, ultra-compact runtime data format SMR and its creation
Reading and writing of OEM-specific encrypted, ultra-compact runtime data (requires one-time DTS8S-CRYPT-SETUP)
Initial setup for OEM-specific encryption of ultra-compact runtime data (one-off costs per OEM)
|Universal Vehicle Diagnostics in spite of OEM-Specific ODX Data|
|Standardized Runtime System with ODX and OTX|
|All-in-one Tester for the Vehicle Diagnostics|
|Diagnostics: Communication Server for all Standards|
|Advantages of Using Current International Standards in Vehicle Diagnostics|
|Vehicle Diagnostics - From Nuisance to Necessity (Part 1+2)|