...makes automation easy

With ECU-TEST you can intuitively create test cases for automotive software in every development phase and run them automatically – even without any prior knowledge of test automation and programming. We have designed the tool in such a way that the test quality is kept exceptionally high at all levels, although the effort it takes to use it is extremely low.


ECU-TEST allows for a consistent and effective automation of the entire test environment. It supports and connects so many different software tools, that it easily fits in numerous existing test and validation processes.

TraceTronic ECU-TEST Tools


The test automation tool ECU-TEST can be used in all phases of development up to the finished vehicle itself. It allows for a high reusability of the test cases in the various test areas MiL, SiL, HiL, PiL and ViL (vehicle), through generic test description and tool-access abstraction.


We have designed ECU-TEST to integrate perfectly into existing tool chains. For example, the software can be easily embedded in a continuous-integration platform by supporting standards and various interfaces. Customers can also include their own specific tools solutions. Using a number of extension capabilities, we tailor ECU-TEST to fit your exact problem definition.

TraceTronic ECU-TEST Tools
All interfaces, formats and tools at a glance


  • ASAM ACI 1.4
  • ASAM XiL API Version 2.0.1 und 2.1.0 (MA, EES, ECUC/M Port)
  • AUTOSAR Classic & Adaptive
  • AUTOSAR Time Synchronization (PTP)
  • FMI 1.0/2.0
  • PLP (Probe Logger Protocol)
  • ReqIF 1.2
  • SAE J2534 PassThru

Bus description:

  • ARXML (Classic Platform) 4.1.1 to R20-11
  • ARXML (Adaptive Platform) to R20-11
  • DBC
  • FIBEX to 4.1.1
  • FIBEX for Ethernet 4.1.2
  • FIBEX for Diagnostic Log and Trace (DLT): Analyse non-verbose Mode
  • LIN Description File (LDF)

ECU description:

  • ASAP2 Database (A2L)
  • Executable and Linkable Format (ELF) with DWARF 2-5
  • Intel HEX
  • Motorola S19

Supported trace formats:

Signal-based trace formats:

  • AS3TRACE (TraceTronic)
  • CSV
  • MAT (MATLAB/Simulink, ControlDesk)
  • MDF 3.0, 3.1, 3.2, 3.3, 4.0, 4.1
  • TDMS (National Instruments)
  • STI, STZ 2.0.1, 2.1, 2.2 ASAM XiL-API


  • ASC (Vector)
  • BLF (Vector)
  • MDF 4.0, 4.1
  • TTL (TTTech)


  • BLF (Vector)
  • DLT (TraceTronic, GENIVI DLT-Viewer)
  • PCAP, PCAPNG (TraceTronic, Wireshark)


  • ADTF2
  • eCAL 5.0, 5.1


  • ERD (CarSim)
  • ERG (CarMaker)
  • RDB (VTD)


  • Audio: FLAC, WAV
  • Video: AVI, MP4, MKV, MTS

Other formats supported on request.

Supported hard- and software

  • A&D: iTest
  • AKKA: Gigabox
  • AVSimulation: SCANeR
  • Beckhoff: TwinCAT
  • Digitalwerk: ADTF
  • dSPACE: ControlDesk
  • dSPACE: ModelDesk
  • dSPACE: MotionDesk
  • EA: UTA 12
  • ESI: SimulationX
  • FEP
  • FEP3
  • FEV: Morphée
  • froglogic: Squish
  • Göpel: Video Dragon
  • HORIBA FuelCon: TestWork
  • HMS: ACT - Restbussimulation
  • HMS: Bus interfaces
  • IPG: CarMaker
  • JS Foundation: Appium
  • KS Engineers: Tornado
  • Lauterbach: TRACE32
  • MAGNA: BluePiraT
  • Mathworks: MATLAB/Simulink
  • Mechanical Simulation Corporation: CarSim
  • MicroNova: NovaSim
  • Modelica Association: FMI
  • NI: LabVIEW
  • NI: VeriStand
  • NI: VISA
  • Opal-RT: RT-LAB
  • PLS: UDE
  • RA Consulting: DiagRA D
  • SAE: PassThru
  • Scienlab: CDS
  • Scienlab: ESD
  • Softing: CAN L2 API
  • Softing: DTS
  • Softing: EDIABAS
  • Speedgoat: Simulink RT
  • Synopsys: Silver
  • Synopsys: Virtualizer
  • Technica: BTS
  • The GNU Project: GDB
  • TraceTronic: cTestBed
  • TraceTronic: Ethernet
  • TraceTronic: Multimedia
  • TraceTronic: RemoteCommand
  • TraceTronic: Serial interface
  • TraceTronic: SSH
  • TTTech: TTXConnexion
  • Typhoon HIL: Typhoon HIL Control Center
  • Vector: CANalyzer
  • Vector: CANape
  • Vector: CANoe
  • Vector: DYNA4
  • Vector: XL API
  • ViGEM: CCA
  • Vires: VTD
  • VW: ODIS
  • X2E: Xoraya

Test management tools

  • Broadcom Rally Software
  • Micro Focus ALM / HP Quality Center
  • Micro Focus Octane
  • PTC Integrity LifeCycle Manager
  • SIEMENS Polarion ALM
  • Test42

Source code management tools

  • Apache Subversion
  • Git

On request we will gladly realize the linkage of your specific hardware or software.


Many of our clients and partners have a growing desire for smooth cooperation, even within their own ranks. The classical role division is reaching its limits and really inhibits both motivation and innovation. Being an agile organization, we strongly focus on this very aspect. With ECU-TEST, we support, for instance, version control (SVN, Git) and enable various users to use the same workspace. Upon request, different work statutes can be visualized and compared with each other rather effortlessly.

Latest Release 2021.3

Release video

We are constantly refining both ourselves and our software.

In the current release video, our product owner Martin Schopf shares his personal highlights of the latest ECU-TEST version.

Take a look!

Feel free to click through the features of past versions as well.
Older versions
Want more videos? Then take a look at our YouTube channel.
Would you like to see the latest features? Then browse through our product demos.

Top features at a glance

New trace synchronization method for AUTOSAR Time Synchronization/PTP

ECU-TEST 2021.3

With AUTOSAR Time Synchronization, it is possible for ECUs to continuously synchronize their clocks in the network. The synchronization takes into account the message delays of complex networks and can achieve accuracies in the nanosecond range.

With the current version of ECU-TEST, the correct implementation of this protocol can be tested in the trace analysis. In addition, the globally synchronized time can be used for trace synchronization of Ethernet, CAN(FD) and FlexRay recordings, so that they can be meaningfully tested with relation to each other.

Compared to existing synchronization methods, a significantly better accuracy is achieved and additional knowledge about the test process or modifications to the test system are not required.

Constant recording and analysis of audio signals and better support for diverse audio sources

With ECU-TEST 2021.3 it is possible to use and evaluate audio channels recorded in the test case directly in the trace analysis. For example, the signal data can be processed efficiently with NumPy trace step templates.

The current version also supports all audio sources available on the system.

Note: These improvements are not yet fully implemented due to their early stage. If you are interested in trying out audio recording and analysis in ECU-TEST, please contact our support.

ECU-TEST 2021.3

AutoSPY: Intuitively enlarge diagram view, value range axes and units for more context

ECU-TEST 2021.3

The diagram view of the interactive AutoSPY Viewer has been improved:

a) The size of the diagram can be changed intuitively by moving the lower range limit. This method of changing size applies to both individual signals and signal stacks.

b) Diagrams of analog signals include an axis with division and labeling. The enlarged context makes navigation easy in large diagrams. For signal stacks, the associated axis is highlighted when the signal is selected. In the context menu of the axis, the value range can be reset to actual values in the visible time range or in the entire document.

c) In addition to the measured values for the blue and red cursor, the physical unit for the signal values is displayed in a separate column. This makes it easier to identify signals and arrive at correct conclusions.

d) Finally, the possibilities for zooming and navigating in the diagrams have been extended:

  • Ctrl + Mouse wheel: Zoom in time range
  • Shift + Mouse wheel: Zoom in value range
  • Ctrl + Shift + Mouse wheel: Zoom in time and value range
  • Shift + Mouse wheel on axis: Zoom of all signals of the axis in the value range
  • Drag with middle mouse button: Time navigation
  • Shift + Drag with middle mouse button: Navigation in time and value range
  • Shift + Drag with middle mouse button on axis: Navigation of all signals of the axis in the value range

Central depository/deployment of bus, service and A2L caches by TEST-GUIDE

Importing the bus, service and A2L databases for the first time can be time-consuming due to the size of the files and the complexity of the formats.

Through the central depository/deployment of the read-in caches, this process is required much less frequently. Reuses in ECU-TEST therefore access a cache of these files.

After importing into the database, the associated cache is stored in encrypted form in a configured TEST-GUIDE depository. Other ECU-TEST instances can access the cache from there instead of creating separate caches.

ECU-TEST 2021.3

ASAM XIL: Prototype for extending XIL server to include job calls

ECU-TEST 2021.3

Thanks to a standardized interface, ASAM XIL enables applications to conveniently connect to ECU-TEST. The standard defines a wide range of functions that cover a variety of use cases.

Our interface extension makes it possible to publish methods on the server (test bench and ports) and make them available in ECU-TEST as tool and port jobs.

AUTOSAR: Support of Classic and Adaptive AUTOSAR releases R19-11 and R20-11 for bus and service communication

The AUTOSAR (AUTomotive Open System ARchitecture) methodology has established itself in many areas for describing modern E/E architectures, especially for on-board network communication.

ECU-TEST now also supports the latest versions of the AUTOSAR system description files (ARXML) for bus (CAN, LIN, FlexRay) and service communication (SOME/IP).

ECU-TEST 2021.3

Bus hardware: Mini residual bus simulation for FlexRay

ECU-TEST 2021.3

With the CAN mini rest bus simulation, it was possible in earlier versions of ECU-TEST itself to describe simple simulation (max. 20 messages, min. 10ms cycle times) in test cases.

The mini residual bus simulation now also works for all the supported FlexRay hardware bus connections. Similar to CAN, the signal values of the residual bus simulation can also be configured in three different ways on FlexRay:

  • Using fixed values in the test case
  • Using calculation classes
  • Integrating stimulus files

Diagnostics add-on: Support for FlexRay-TP

Access to diagnostic systems is an important component of many test cases in the automotive segment. With the ECU-TEST diagnostic add-on, there is an option to use UDS diagnostic functions in test cases.

In addition to support for diagnostics via CAN (ISO-TP) and Ethernet (DoIP), diagnostics is now also possible via FlexRay.

Ethernet recording with very high data rates and lower runtimes for trace analysis of SOME/IP service communication

The trends of autonomous driving and networking in automotive software development are leading to a significant increase of onboard network communication and huge increase in data rates, the complete processing of which poses a challenge for many tool manufacturers. The result is often data loss.

With the passive Ethernet service port, SOME/IP test parameters up to 100MBit/s* bandwidth can now be fully analyzed as part of the test case. In addition, there was a significant increase in performance during PCAP recording (tested up to 1.3 GBit/s). The analysis time of these traces could be significantly reduced.

*) pure SOME/IP communication via PLP, tested with Windows 10 21H1, Intel(R) Core(TM) i9-10885H CPU, 32GB RAM

I’ve got to have it!


You think ECU-TEST is a life-changing software? Then get in touch with our sales team and let us make you an offer.

We haven’t convinced you yet or you want to test the software? Contact us and give us a chance to do better.


You want to learn how to make the best use of ECU-TEST and how to integrate the tool into your own processes? Here, you can find out more about our product trainings.

Data sheet (PDF)

Too much useless information and you just need the hard facts? Then download our product data sheet.

Keep me posted!

ECU-TEST technology update to Python 3 and wxPython 4

Dear ECU-TEST users,
in order to keep the product ECU-TEST up to date, it is necessary to update important underlying software technologies and to switch therefor to Python 3. Unfortunately, this new version of the language is not completely backward-compatible. Thus, user with ECU-TEST version lower than 8.0 are also affected, if they want to update their workspaces. In the following migration guide we have summarized the main reasons for the switch to Python 3 and name the most important effects on our users.

Your ECU-TEST team

Python 3 guide