Simulation of ECUs


Configurable simulation of ECU diagnostics.

The ECU simulation TestCUBE2 can be used for all cases when an ECU is not available.
TestCUBE2 is a configurable hardware and software solution for simulating ECU diagnostics with real bus communication. With just one device, you can simulate several ECUs or even an entire vehicle at the same time.

Areas of Application

  • Preparation of tests in Engineering, Testing, Manufacturing
  • Tester or production system release tests
  • Tester regression tests


  • Tests can be started before the ECU is available
  • Clear management of variants with archiving of simulation files
  • Easy to use
  • API interface enables automatic tester regression tests
  • High test quality with various configurations
  • Best-case and worst-case tests
  • Complex sequences can be run
  • Can run without a PC


  • Simulation of several ECUs (CAN or K-line) with one device
  • Reliable response time behavior due to protocols being run directly on the interface
  • Automatic creation of the simulation from a CAN bus trace (*.asc/*.trc)
  • Residual bus simulation with import of CANdb file and database at symbolic level
  • High-performance interface with 32-bit PowerPC core (384MHz)
  • Supported buses: CAN, K-line
  • Supported protocols: UDS, KWP2000, TP2.0, J1939
  • Three analog inputs and three digital inputs/outputs
  • Adapter interface with banana jacks

More information

Creating Simulation Files

Usually, simulation files are created by manually editing the request and response messages in a convenient dialog. You thus have all the necessary freedom for the required test depth and scope in your application case. Alternatively, the simulation file can be generated automatically from an existing trace file – an incredible increase in efficiency particularly for regression tests. The simulation files of the original TestCUBE can be imported.

Regression Tests

The challenge in regression testing is the availability of the test environment – in the case of service testers, all vehicles in all variants. With TestCUBE2, you simply archive simulation files for all vehicle variants. In the regression test, you exchange the simulation files as required – in the case of automated tests via the programming interface. It really couldn’t be simpler!

Technical Data
Interface 32-bit embedded controller with PowerPC core 384MHz

  • Supply voltage 8 to 28V
  • Dimensions (housing) 143mm x 113mm x 84mm
  • 2 CAN interfaces (high-speed, low-speed, single-wire)
  • 2 K-line interfaces
  • 3 analog inputs / 3 digital inputs/outputs
  • Can be extended with additional boards

Signals to banana jacks and 26-pin MDR jack

PC interfaces
  • USB 2.0
  • Ethernet
  • ISO-TP
  • VW TP2.0
  • J1939
  • On request
Operating systems
  • Windows 10
  • Windows 7
Delivery scope
  • High-performance interface with integrated adapter area (banana jacks)
  • Software and documentation on CD


Softing DTS.monaco

Universal development test – Ensure that diagnostic communication and vehicle diagnostics work reliably.

Softing DTS.monaco enables the comprehensive testing of diagnostic communication, diagnostic data and diagnostic sequences in the areas of engineering, testing and preparation of manufacturing tests. It can be adapted for a whole range of different test tasks and for different user groups.


Areas of Application

  • Development of diagnostic and control functions for ECUs
  • Function test and validation
  • Integration and system test
  • Preparation of test sequences for Manufacturing and Service
  • Analysis of returns and Quality Assurance


  • Reduced costs and familiarization time as DTS Monaco covers the functionality of several tools, previously separate: OBD scan tool, data and bus monitor
  • Intuitive operation and preconfigured templates
  • Early detection and remedy of communication problems and function errors
  • Flexible adaptability to various tasks
  • Communication data and test results can be fully documented

Flexibly Adaptable to the Relevant Task

DTS Monaco is part of the Diagnostic Tool Set product family and is based on the DTS Base System. Monaco stands for Modular Analyzer for Vehicle Communication. A clearly laid out start page enables simple and fast access to the functions required most frequently. The actual workspace is divided into two: one area with a fixed layout and the second with layouts that you can toggle between. A status display below shows communication server messages. The various functions are realized using special, configurable interface elements. These “HMI Controls” can be arranged freely in the layouts in configuration mode and comprehensively configured.

Early Detection of Problems and Errors

In execution mode, a configured workspace can be “started”. In doing so individual functions can be started automatically and communication can be established in advance if so required. Self-generated test sequences enable both simple and very complex function tests. This makes it possible to detect, and remedy, communication problems and function errors at an early stage. Communication data and test results can be documented in entirety in the process.

Fast Results

For typical use scenarios predefined templates including a universal database for the OBD self-diagnosis as well as various protocol templates (WWH-OBD, J1939-73 among others) are supplied. In Demonstration mode, all functions can be tested, even without an interface and a license, using a detailed example including simulation. Furthermore, the tool has a completely integrated OTX runtime for running complex test sequences in accordance with ISO 13209. An authoring tool for creating such OTX sequences can be started directly from DTS Monaco.

Separately Available Solutions


  • Testing communication
  • Analyzing data on bus
  • Examining ODX data vs. ECU
  • Reading/deleting error memory
  • Programming flash memory
  • Displaying measuring values
  • Parameterizing ECUs
  • Coding variants
  • Executing ECU routines
  • Testing OBD functions
  • Creating/executing test sequences
  • Identifying built-in ECUs


  • Communication server: ISO MVCI-Server/ASAM MCD runtime system (COS)
  • ODX data interface: ISO 22901-1/ASAM MCD-2D
  • Programming interface: ISO 22900-3/ASAM MCD-3D
  • VCI access interface: ISO 22900-2 (D-PDU API) via CAN/-FD, K-line, Ethernet
  • ISO 13400 (DoIP)
  • ISO13209 (OTX)
  • ISO 14229 (UDS)
  • ISO 14230 (KWP2000)
  • ISO 15031 (OBD)
  • ISO 15765
  • ISO 27145 (WWH-OBD)
  • SAE J2534
  • SAE J1939
  • and many more

Click for Video

Download trial version of DTS Monaco


    Development of Complex Diagnostic Sequences According to the Standard ISO 13209.

    OTX Studio is a development environment for creating, implementing and debugging of complex diagnostic sequences. You can conveniently create graphical user interfaces and link them to the sequences created.

    Areas of Application

    • Graphic specification of diagnostic sequences
    • Creation of test sequences in ECU development
    • Creation of test sequences for EOL tester in Manufacturing
    • Guided fault diagnosis for repair shop testers


    • Easy exchange of sequences between ECU, system and vehicle manufacturers
    • Diagnostic data is supported in compliance with ODX 2.0.1 as well as 2.2.0
    • User oriented editor concepts: Line oriented, Flow Chart or modular “Comfort Mode”
    • Can be implemented universally as maximum OTX function scope available
    • Long-term protection of investments due to use of an international standard
    • Expertise protection and prevention of unauthorized changes by saving OTX scripts in binary format
    Softing DTS.venice

    Powerful authoring system for ODX 2.2 and 2.0.1 for
    diagnostic experts and developers of vehicle ECUs.

    Softing DTS.venice enables the convenient creation, testing, management and maintenance of diagnostic specifications over the entire process chain for OEMs as well as system and ECU suppliers.

    Areas of Application

    • Description and validation of diagnostic functions and ECU communication
    • Data interoperability test
    • Provision of test data for integration and system test
    • Data adaptation in production preparation and for use in repair shop testers


    • Efficient creation of the diagnostic specification with assistant support
    • Greater data quality thanks to testing of both syntax and semantics
    • Data consistency over the entire process chain based on standard tool with central database (single source)
    • Considerable cost saving because of the ability to import existing data descriptions and early error detection
    • Shorter approval process as suppliers can test conformity with the OEM regulations themselves

    Simple Creation of ODX Databases

    DTS Venice is part of the Diagnostic Tool Set product family and is based on the DTS Base System. Venice stands for Vehicle Communication Database Editor. New databases can be created both on the basis of existing ODX/PDX files and on the basis of protocol templates. In the scope of delivery is a sample database containing three ECUs including detailed documentation and a tutorial.

    Convenient Editing of ODX Data

    A start page enables simple and fast access to the functions required most frequently. The entire ODX data model can be processed in the editor’s Expert view. The ECU view enables a simplified view of the most important data of an individual ECU as well as of its variants. Diagnostic description inheritance is visualized graphically. Integrated assistants support data input. It is possible both to work with ECU shared data and to process several databases simultaneously. For documentation purposes, the diagnostic specifications created can be output as RTF files. In Demonstration mode, ODX databases can be viewed without a license.

    Top Data Quality from the Outset

    The ODX databases of modern vehicles are highly complex and become even more so during their lifetime due to additional variants, maintenance measures and function extensions. DTS Venice ensures the consistency and completeness of the database at all times. Formal checks ensure the basic compliance with the ODX standard and optionally with the ASAM ODX Recommended Style. Extensions by user-specific authoring guidelines are possible.