hero image
What's new?


ecu.test meets XCP - for best ECU performance

A new extension for ecu.test is now available. It allows access to measurement and calibration quantities of ECU functions without external tools – ecu.test calibration.

For measurement, calibration and evaluation, you need access to the internal variables and signals of the control units. In the automotive sector, special measurement and calibration protocols such as XCP, CCP or iLink RT are used for this purpose. In the past, ecu.test did not support these directly, but outsourced the task to various 3rd party tools that were only controlled by ecu.test.

With ecu.test calibration, a dedicated XCP interface is being established for the first time. XCP is short for "Universal Measurement and Calibration Protocol" and is an ASAM-standardized protocol that allows the exchange of data between different development tools and ECUs. This exchange currently includes reading measurement data in real time and writing calibration parameters. It is also possible to record and evaluate variables in MDF4 file format.

XCP can be used for different communication interfaces (CAN, CAN-FD, LIN, FlexRay, Ethernet). Currently, ecu.test calibration offers Ethernet access via TCP and UDP.

In future, the range of functions will be expanded to include other communication interfaces like CAN and FlexRay.

You want to see ecu.test calibration in action? Then take a look at our video. And if you're interested in ecu.test calibration, just get in touch with us.


Merry Christmas and a happy new year 2024

Christmas is just around the corner. We wish you all happy holidays and a great start to 2024. May the upcoming year be as exciting and successful as the one that is now ending – with many new opportunities to take advantage of.

We're looking forward to it!Merry Christmas


tracetronic turns 20 and we're already celebrating!

In 2024 we will be 20 years old, it's crazy. We're celebrating - for the whole next year! And because Christmas is coming soon, we're starting now and giving ourselves a new corporate design for our birthday.

New logo, new colors, new spelling. TraceTronic becomes tracetronic (also in the body text, not just in the logo), ECU-TEST becomes ecu.test, TRACE-CHECK becomes trace.check and TEST-GUIDE becomes test.guide (and so on).

Our website has also been given a completely new look. In addition to the new design, the main focus of the relaunch is on improving usability and increasing the visibility of our products and solutions. We will continue to work hard on this over the next few months - continuously, as with all our tools. Have fun discovering everything!


scenario.architect Release 2023.3

Create typical scenarios for any traffic situation? It's easy with scenario.architect. With the user-friendly scenario editor, typical or even safety-critical traffic situations can be developed according to specific requirements and adapted iteratively. A new release is now available for this tool.

With the version 2023.3, numerous new features, such as event-based annotations or improvements in graphic performance, are waiting to be tested. We show you everything that is new in the video.

Are you curious to test scenario.architect and develop your own scenarios? Then get in touch with our sales-team .


Easily manage test executions with playbooks

Playbooks belong to test.guide like test case packages to ecu.test. How to work with playbooks and how to distribute them to executable test tasks, we will show you in our latest video.

First, a few sentences explaining what it's all about: In general, playbooks describe a test scope for the fully automated execution of test jobs via test.guide.

In detail, playbooks contain an ecu.test workspace, the required test resource, necessary steps for the preparation and post-processing of the test execution and the actual test cases to be executed. With this information, test.guide can manage the entire test process. Even the upload of the test reports generated after the test execution is done automatically. Sounds good, doesn't it?

With Playbooks, you can minimize many manual steps and at the same time, you only execute those parts of the ecu.test Workspace that are necessary for the planned test scope. The creation is very easy, because test.guide already offers a comprehensive playbook editor for all necessary steps. Just select files, save them and get started. And if multiple test resources are available, you can also split the playbook when starting the execution to distribute the test execution to multiple test resources. Another additional time saving.

Are test.guide playbooks your last missing puzzle piece in the continuous testing process? Feel free to ask us for more details - we'd be happy to hear from you.


Highly automated test execution with test.guide

Starting software tests manually? That was once. With test.guide, you can execute all open test tasks in the correct order on the correct test resource automatically – even in a continuous loop.

In our latest video, we show you exactly how this works. If you prefer reading instead of watching, we also have a short explanation for you here:
The workflow for automated test execution is based on our tools test.guide and ecu.test, which which perfectly match each other. We use test.guide to plan test executions, manage test results and monitor test resources. While ecu.test is used to implement and execute the test jobs.

The test execution is controlled by the test.guide ResourceAdapter, which is installed on the test resource just like ecu.test. From there, it controls the local execution of the tests. After completion, the ResourceAdapter sends the results back to test.guide for analysis and then releases the resource for further tests. Fully automated. According to the test volume, this infrastructure can also be scaled and test executions can be distributed to different resources.

Would you like to reduce the many manual and time-consuming steps and optimize your continuous testing process? We are pleased to help you with the setup and also with any questions about our tools. Just get in touch with our support.


From 0 to 100 - our booth becomes interactive

Many times a year, we are on the road at recruiting fairs. Since this April, we can no longer just tell you how versatile our tools are - we can also show it: with our ecu.test Playstation demonstration. We got the idea for this from our student Ben Margott. He connected ecu.test with Gran Turismo 7 and analyzed the driven laps in detail.

Now this idea has become a highlight at our booth. When racing live on the Playstation, skill and sensitivity are required not only in the curves. Because while you are really going for it, a test case developed especially for the race is started in ecu.test, which tracks the driven lap with regard to different measured quantities.

For this purpose, the transmitted signals of the car racing simulator are recorded and saved into a file. After finishing the race, the data is automatically analyzed with trace.check. At the end, you get an individual report of the lap you were fastest on. This overview contains details about the speed you drove, your own acceleration behavior and how often you hit the brakes.

It's a lot of fun - for us and for the students. Come and visit us.


The results of the Stellantis Hackathon are in: We are ready for the cloud!

In the beginning of March, we participated in the Stellantis and Amazon Web Service (AWS) Hackathon in Rüsselsheim, Germany and proved that we are capable on every level!
In collaboration with about 70 other software experts, we spent a whole week focusing on Stellantis’ cloud-based product development environment "Virtual Engineering Workbench" (VEW). This virtual platform is designed to enable continuous integration, testing and validation of vehicle software within a global partner network. The project was defined by seven different use cases.

Our use case had the working title "End-to-end Testing". A topic tailored to our skillset, as we already use end-to-end workflows to validating software-defined vehicles. Our experience enabled us to optimize and adapt the processes from automated startup to execution and termination of tests for Stellantis. The result? The time we invested in the last weeks and months to make our tools compatible with cloud environments was worth all of the effort and everything worked exactly as we had imagined. Specifically, we were able to complete the following tasks:
  • Analysis and optimization of continuous integration workflows
  • Support for dynamic provisioning of virtual test resources
  • Fully automated test execution planning in test.guide for commit-triggered functional validation in ecu.test
  • Aggregation of test results from all test stages – from health checks and sanity checks to functional validation – to establish overall traceability for assessing the quality of functional adaptation
  • Upload of all test results to test.guide for fast and timely feedback
  • Integration of the utilized test management and defect tracker tools into test.guide
Hackathon Stellantis

This was a successful and educational week for us, which Michael Mausbach of Stellantis summarized as follows: "We also had the tracetronic team there so that they could reprogram and adapt their software to our needs on-the-fly, but then quickly realized that everything was already working. A configuration change or a script here and there and it was up and running - we were very impressed with how easy it was!"
We could hardly have received better praise, thank you very much! We are looking forward to continuing our work with Team Stallantis in the future!


Artifact synchronization with test.guide

With the test.guide artifact management we are currently building a central depository where all software and software artifacts can be managed in separate test.guide depositories. Artifacts not only refer to work results of software development, but also documents, description files, test data or configurations. Centralization ensures that all those involved always have access to this relevant information.

In parallel, the ecu.test requirements to configure various test.guide depositories and access their artifacts, were also met. The focus of this first prototype synchronization between ecu.test and test.guide is on providing A2L and HEX files. These are referenced by an ID in a test.guide depository instead of a (local) file path. Only the configuration and the test case are necessary in ecu.test for running the test itself. The required artifacts are automatically retrieved from the depository when the configuration is started. In this way, not only can the actual workspace be kept lean, but the test data organization also runs independently in the background.

In our latest YouTube video, we show how easy it is to use this feature. Only four steps, a few clicks and inputs are required to meet all test requirements.

But see for yourself! We are also happy to help you with the setup and with any questions about our tools.