trace.check automates the analysis
Manual analysis is a thing of the past. trace.check handles the entire analysis of software test results in an automotive context. Fully automated, around the clock and for every commonly used automotive format. Many tests in the automotive industry generate records (traces). Logger data is written during on-board network communication, debugger logs are created by middlewares in the SiL context, or monitoring information is collected from the device-under-test on the HiL test bench. In addition to verifying that testing has been performed, these records are presently used mainly for manual error analysis.
They could revolutionize your testing process! Provided that the many other important information from the measurement data are also used. With trace.check this is very easy and even automated. The analysis itself can be performed offline and without any expensive prototypes, test benches or test systems. Offloaded to different systems (PC, virtual machine, cloud), trace.check helps to increase both test output and test coverage.
trace.check is flexible using standards
Standards make many things easier and are the yardstick for uniform quality, safety and interchangeability of data from different systems. We love standards and thus, we help you to concentrate completely on the analysis. The standardized system functions and interfaces in trace.check help you to easily process numerous description and configuration formats, to exchange them continuously regardless of the manufacturer, to reuse them and to use them over several product generations.
Did you immediately think of SOME/IP communication analysis? For example, we implemented this very easily based on an ARXML description file with associated PCAP traces. For more reports, description and data formats click the trace.check data sheet. In order to help develop the standards further in line with automation, we are also a member of AUTOSAR and ASAM.
trace.check makes signal analysis easy
A simple problem should also be easy to solve. Therefore, we have come up with a framework that allows you to map many analyses from requirements-based testing using simple expressions. Some sections in recorded measurement data are often more interesting than others. With so-called trigger blocks, these sections can be efficiently filtered out for subsequent analysis. Simple expressions and a variety of included functions, e.g. edge detection, help you to check and evaluate triggered sections effortlessly even without programming knowledge.
Does signal interpolation in measurement grids slow down your workflow? Our framework does it for you. This way you can fully concentrate on implementing your test conditions. Additional visual support is provided by integrable plots for your testing. This adds informative diagrams to the test report that visualize the result data with the signal curves and, in particular, provide a good starting point for error analysis.
trace.check analyzes synchronously with time
Each trace has its own timeline. Unfortunately. The good news: trace.check has suitable synchronization mechanisms to align different time axes. Often, comparing several recordings from different measurement data sources is not possible without restrictions. This is due to the delays between the clocks in the ECU and test network and latencies, such as those that occur when measurements are started in tools or loggers.
Interpolation is used to align the time axes of the different traces in the complex networks. Here, accuracies in the range of nanoseconds are achieved. Synchronization is performed according to the AUTOSAR protocol and is done for CAN, FlexRay, LIN and Ethernet recordings in pairs to each other. On top of that, it is even possible to merge any signal recordings into a common, synchronized MDF4 file.
trace.check visualizes results interactively
With the AutoSPY Viewer you have the option to interactively visualize the results of the trace analysis including all included and calculated signals. This makes them real and helps you identify the causes of errors. For us, interacting with signals means filtering, sorting, formatting, measuring or marking important time points in the trace. Zooming, moving, displaying and hiding or overlaying is also part of it for us.
In AutoSPY Viewer we have thought of everything needed for detailed graphical and value-based trace analysis. Even videos can be displayed alongside the analog or digital signals. And by the way, the AutoSPY Viewer is included with trace.check.
trace.check adapts to your requirements
Anyone can work with trace.check. Because it is so simple. A new trace analysis is generated in no time. Even complex analyses can be easily implemented using the analysis modules and templates provided. And the best part: Once generated, they can be universally used. Trace analysis is the core element of trace.check. Without it, automated analysis of recorded signal data and test report verification would not be possible.
The crucial factor for successful analysis is the analysis specification used. This is based on prefabricated analysis modules that are added in logical sequence via Drag&Drop or EasyInsert as a trace step and then specified. Also, a large pool of standard trace step templates for diverse tasks in different domains (check, calculation, ADAS, multimedia, and others) is already available.
Since everything is based on Python, it is easy to fine tune each analysis individually and, based on that, create your own modules and reusable generic analyses. You'll be surprised how easy it is. In order to adapt trace.check optimally to your use case, there are various APIs, e.g. also for your own report formats, for generators or for automating our analysis tool.
show less
Current Comments
10.12.2020 by tongmengli
Error linking to ...
28.05.2020 by Henning Femmer
26.02.2020 by Dirk O. Schweier
28.03.2018 by Daniel
09.12.2017 by Bert