ECU-TEST

...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.

Independent.

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

Versatile.

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.

Expandable.

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

Standards:

  • ASAM ACI 1.4
  • ASAM iLinkRT 3
  • ASAM XiL API Version 2.0.1 und 2.1.0 (MA, EES, ECUC/M Port)
  • ASAM ATX
  • AUTOSAR Classic & Adaptive
  • AUTOSAR SOME/IP
  • AUTOSAR Time Synchronization (PTP)
  • FMI 1.0/2.0
  • IEEE1722 ACF (for CAN)
  • OpenSCENARIO
  • 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 (Version 2-5)
  • Intel HEX
  • Motorola S19

Supported trace formats:

Signal-based trace formats:

  • ASTRACE, AS3TRACE (AutoSPY)
  • 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

Buslogging:

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

Ethernet

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

Middleware/Cosimulation

  • ADTF2
  • AS3TRACE (FEP)
  • eCAL 5.0, 5.1

ADAS

  • ERD (CarSim)
  • ERG (CarMaker)
  • OSI/TXT (ASAM OSI)
  • RDB (VTD)
  • ROSBAG2 (ROS2)

Multimedia

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

Other formats supported on request.

Supported hard- and software

  • A&D: iTest
  • AKKA: Gigabox
  • ASAM: ACI
  • ASAM: XIL
  • ASAP: STEP
  • ATI: VISION
  • AVL: LYNX
  • AVL: PUMA
  • AVSimulation: SCANeR
  • Beckhoff: TwinCAT
  • CARLA Team: CARLA
  • Digitalwerk: ADTF
  • dSPACE: ControlDesk
  • dSPACE: ModelDesk
  • dSPACE: MotionDesk
  • EA: UTA 12
  • ESI: SimulationX
  • ETAS: BOA
  • ETAS: INCA
  • ETAS: LABCAR
  • ETAS: LABCAR-PINCONTROL
  • 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
  • PEAK: PCAN
  • PLS: UDE
  • QUANCOM: QLIB
  • RA Consulting: DiagRA D
  • ROS2
  • 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
  • IBM RQM
  • 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.

Collaborative.

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 2022.1

Release video

We are constantly refining both ourselves and our software.

In the current release video, our product owner Lukas Vierhaus 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.
YouTube
Would you like to see the latest features? Then browse through our product demos.
PRODUCT DEMOS

Top features at a glance

Initial ROS2 connection for recording and analysis of rosbag files

In the ADAS/AD field, digital twins are being used increasingly in the development of sensor-based driver assistance systems. These virtual images of physical systems can be set up as co-simulation platforms using ROS (Robot Operating System), or even as virtual environments for a test object (Device Under Test).

This can then be used to run various simulations based on different scenarios in order to test the (sensor) software which is to be tested right in the early stages of the development process. To test the software, the communication in the ROS network has to be analyzed. However, the manual evaluation of these ROS messages is very time-consuming.

For this reason, a ROS2 connection to ECU-TEST was created. This can be used to automate systems based on ROS2 Foxy Fitzroy.

Via this interface, it is possible for ECU-TEST to record and analyze so-called ROS topics (from rosbag files). In addition to this, the ROS system itself can also be tested in depth and in an automated manner in this way.

Easy exporting of the workspace when uploading playbooks

Formerly, the underlying workspace of a playbook had to be extracted from a version control system (Git, SVN). In order to be able to run playbooks, even without access to these systems, the export of playbooks from ECU-TEST has been extended.

It is now possible to export the current workspace as an artifact to TEST-GUIDE.

The export wizard allows referencing to workspaces that have already been stored in the artifact management, or direct uploading of the current workspace.

ECU-TEST 2022.1

New tool connection to ASAM: iLink RT 3.0

The tool connection to the ASAM standard iLinkRT 3.0 enables communication with measurement and calibration tools. This is an Ethernet standard that supports multi-client and multi-server connections.

Currently it supports the reading and recording of measured quantities.

Acceleration A2L parser

By optimizing the read and write process and parallelization when reading multiple A2L files in the test configuration, memory consumption has been reduced, in addition to a significant acceleration of the processes.

Active IPsec communication

In modern E/E architectures, security measures are being adopted to increasing extents to prevent known attack patterns on vehicle communication. One such measure is to use cryptographic protection on parts of the on-board network communication or on all of it. One possible application can be the implementation of the IPsec protocol in the on-board network.

Now ECU-TEST can also be used for securing or verification in cryptographically protected Ethernet networks. For this purpose, the built-in network solution allows for set up and communication in the networks with IPsec switching (for IPv4).

The current implementation supports the transport mode and the key exchange according to IKEv2. Active connections can thus be protected using the Authentication Header (AH).

Encryption (ESP) is not yet part of the scope of function.

New trigger mode: Define range by event and time offset

ECU-TEST 2022.1

A new trigger mode was introduced in Release 2022.1:

  • with time offset if the start trigger is fulfilled

This can be used to create time-defined trigger ranges that extend around a start trigger event.

Beispiel:

  • Start trigger: Edge(Signal, 0, 1)
  • Start offset: -2s (start of trigger)
  • Stop offset: 5s (end of trigger)

The trigger range in this example is opened 2 seconds before a 0-1 edge and ends 5 seconds after that. Thus, with this new mode, it is possible for more trigger ranges of the same trigger block to overlap.

Truncated trigger ranges at the beginning and end of the trace or of the parent range can be explicitly evaluated (e.g. with FAILED). The corresponding setting can be found under 'Extended options' of the trigger block.

AutoSPY: Improvements in signal identification

In the interactive signal viewer AutoSPY it is now much easier to identify the correct signals:

  • The support for number-to-text mappings (enumerations of status signals on a bus, for instance) not only facilitates the signal identification, but also the interpretation of the signal values. The associated numerical raw value can still continue to be displayed.
  • When opening the AutoSPY Viewer from a static plot of the TRF report, signal color and line style are carried over: this has been a feature since several releases. With the ECU-TEST 2022.1 onwards, the signal curves are also automatically formatted if an astrace file is opened directly with the viewer.
  • Pressing F11 will minimize all docking windows. In this way, more space is created quickly for the table view or chart view. Shift + F11 restores all minimized toolboxes.

ECU-TEST 2022.1

ECU-TEST 2022.1

Also, the mouse zoom (Z) has been improved:

  • Left click: Increases the time range
  • Shift + left click: Increases the value range
  • Shift + Ctrl + left click: Increases the time range and value range
  • Right click: leads to the corresponding reduction in each case
  • Pressing and holding down the left mouse button: Pulls up a zoom window that sets new visible time range and value range

Offline filtering of PCAP traces

In the online case, ECU-TEST has been using an efficient and intelligent filter mechanism since release 2021.4 to handle very high data rates with high performance. In this process, parts of the service-based communication that are not relevant for the test case and the analysis will be recognized as part of a learning phase and filtered out at the operating system level in a resource-optimized manner. This results in reduced PCAP traces that contain only the data that is relevant to the test case and to the analysis.

Now ECU-TEST 2022.1 also supports the offline filtering of service based communication from PCAP traces. Here, the traces are created away from ECU-TEST, e.g. by loggers. This enables significant performance gains in the trace analysis of this data.

The length of the learning phase can be configured in the ECU-TEST settings in the 'Trace analysis' area.

ECU-TEST 2022.1

Signal-based trace merge

ECU-TEST 2022.1

The new signal-based merging of traces generates synchronized and interpreted MDF4 traces based on arbitrary recordings of a package.

Specifically, all signals of the signal groups used are transferred to a common MDF4 file by means of the trace merge, with due consideration for the respective synchronization.

This is done with due consideration for the following:

  • Signals in the signal groups
  • Signals of the special signal group 'Assign automatically’
  • Signals of the 'Record all test variables' option
  • Signals from analysis packages

Package links with target version for better traceability

If an implementation package is derived from a specification package with a version number, the link to the specification package and to the associated version number will also be displayed automatically for the implementation package.

If the version number in the specification changes, it will also affect the implemented or derived package. It recognizes that the version numbers are not matching anymore and will display the new version number of the specification in brackets, highlighted in color, next to the version number that is valid to date.

The context menu can be used to update the link to the specification package and hence the version number as well.

ECU-TEST Neuerungen 2022.1

Support for the IEEE 1722a protocol for bus communication via Ethernet

ECU-TEST 2022.1

With the support, it is possible to use all known bus test steps by accessing the IEEE 1722 (CAN) Ethernet protocol as well.

For this purpose, new ports for bus access and J1939 are available on the Ethernet tool adapter.

Bus access: Support of time options and the selection of representation in the "Check initial value" test step

With the test step 'Check initial value', it is possible to access the first value of a signal since the start of the measurement (port start) or since the last call of 'Reset initial value'.

What is new is that now time options for the evaluation can also be configured in this test step. In addition, the representation of a signal value (physical value, text value, raw value, implementation value) can also be selected. The behavior is analogous to the test step 'Read'.

New option for handling INCONCLUSIVE evaluations

In the precondition block of ECU-TEST it is possible to overwrite the evaluation of the contained test steps with NONE and ERROR using checkboxes. As a result, SUCCES will be mapped to NONE, while INCONCLUSIVE and FAILED to ERROR. Thus, each test case was aborted with ERROR, if it was evaluated with INCONCLUSIVE in the precondition block.

The precondition block has been extended to enable a more flexible handling of evaluation INCONCLUSIVE. Specifically, it is now possible to keep INCONCLUSIVE as the evaluation for a test case without canceling the test.

ECU-TEST 2022.1

There are two new options for this:

1) Overwrite result: The selection list can be used to define whether the INCONCLUSIVE evaluation should be excluded when overwriting the evaluation or not.

2) Variable abort information: This option can be used to set whether the test case should be aborted or should continue to run in the event of an evaluation as INCONCLUSIVE.

I’ve got to have it!

Contact

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.

PRODUCT TRAININGS

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.