Features of past versions
To ensure the testing of service-based communication, ECU-TEST grants access to structured data as defined in a service description in ARXML format. This structured data can now be used efficiently in signal recording and trace analysis. Events and methods from the Service tab can be dragged into the signal recording in order to record them. (This uses the well-known ECU-TEST mapping mechanism)
In the resulting PCAP traces of the Ethernet communication, these events and methods can then be evaluated using trace analysis. Input-supported attribute access to substructures is possible in trace analysis. Furthermore, index access to the individual components of a vector is also supported.
TRACE-CHECK 2021.1 can be used to link an analysis package with all previous stimulation packages via a simple setting and to execute it for them.
This means that the configuration and maintenance effort can be significantly reduced, especially for the generic tests to be carried out on all test scenarios in a project.
The signal toolbox of the AutoSPY Viewer now supports the multiple selection of signals and provides access to additional functions via a context menu, for example, to invert the current selection. A new button allows you to control whether the signal selection between the toolbox and the views should be continuously synchronized. From now on, the diagram and table view synchronize their signal selection automatically at all times.
The Properties toolbox now also takes into account changes in the Signals toolbox and shows the common properties of the signals selected in it. The values of the properties can be copied to the clipboard via a newly introduced context menu.
In the course of a package or project preparation, it is worth performing a plausibility check and thus obtaining information about incorrect references or missing variables.
In addition to the already integrated check mechanisms, user-specific package checks and project checks can now be created in the form of scripts. These are stored in the UserPyModules folder as a .py file of the current workspace and are automatically applied when the Check package or Check project functions are executed.
Note: In order for changes to these scripts to take effect without an ECU-TEST restart, a reload can be initiated via Extras/Update user libraries.
Teams and projects using the same bus and service databases can now increase their productivity. When a bus or service database is imported for the first time, the caches that can be stored encrypted in a shared cache directory are generated. Other team members can use them for their project and save the long waiting time it sometimes takes to incorporate the databases.
To this end, in the Workspace settings under the option Directories the new field Shared Cache Exchange Directory has been implemented.
The new GetSomeIpServiceDiscovery trace step template provides an easy way to document the SOME/IP service discovery communication of an Ethernet stream for further use.
Only the UDP and SomeIpSd signals, as well as the ServiceId, are necessary to receive the binary signals of the Offer Service, Find Service, etc.
In addition, the CheckTriggerRange trace step template is introduced to evaluate the duration and the number of all trigger areas within a trigger block.
The new package generator delivered with ECU-TEST 2020.4 allows for flexible and easy generation of packages with trace analyses for the comparison of all signals of an existing and a new trace. Fields of application are for example back-to-back tests or neutrality tests.
- Filter for including and excluding signals
- Simple assignment of signals from different traces
- Generation of packages or parameter sets per signal pair
- Automatic visualization of signal differences
- Configuration either completely via GUI or alternatively as Python code for full flexibility
With this new parameter set generator, batch analyses can be easily realized, i.e. a trace analysis is executed on all similar traces of a defined directory. For this purpose a parameter set is created for each trace file. Since this generator including the source code is public, it can be easily extended or adapted to own requirements.
- Searches also subdirectories recursively
- Filters trace files by regular expressions using their names
- Supports CSV, MAT, MDF3/4 and PCAP formats
Among the newly added analysis modules are two templates from the multimedia domain:
- "FindColoredObject" allows for detection of objects in video frames based on their color and with tolerance. The effect of this step is similar to magic wand selection tools known from image processing programs. Here several found objects in configurable proximity are recognized as coherent (dilation). The template supports masks to limit the detection to certain parts of the video.
- In the annotated videos created by "AnnotateVideo", the locations of found objects from recognitions (like FindImage or FindColoredObject) are marked by configurable frames. In addition, masks that restrict the analysis to parts of a video can be visualized.
There are also other useful templates, such as "ExtractSignalsByRegEx" for extracting data components from text signals with regular expressions.
In the signal viewer AutoSPY delivered with ECU-TEST it is now possible to configure the drawing styles of signals in detail:
- Type, size and color of sample markers
- Line style, width and color of signal curves
- Filling and fill color of boolean signals
Settings already made in the static plots of the trace analysis are adopted when the interactive viewer is opened.
In order to be able to quickly implement frequent use cases for video analyses, new Numpy trace step templates are supplied
- Calculation of a brightness signal
- Mask support
- Calculation of a logical signal ContainsImage
- Calculation of an object-value signal for API interaction with match objects
- Mask support
- Add frames of a video at the start trigger of a parent trigger block to the report
- Optional input of a frame offset, e.g. to document the frame before the start trigger
- Optionally highlight the matches found by FindImage or a parameterized mask in the report
Numpy Trace step template ReduceVideo
- Acceleration of subsequent analysis steps
- Reduction of resolution
- Conversion to grayscale video
- Reduction of the frame rate (downsampling)
New API method FindImageByFeatures
- Use feature detection to find partial images in the frames of a video
- Independent of size, rotation, color or perspective
Furthermore, masks and reference images can be created directly in TRACE-CHECK from videos and used in these templates.
Diagnostic Log and Trace (DLT) provides a standardized component based on AUTOSAR 4.0 for logging and tracing ECUs. For the newly supported verbose mode reusable DLF filter files created with the GENIVI DLT-Viewer may be used to access only those messages that correspond to e.g. a certain ECU or application id. A unified object representation of these messages enables the automatic evaluation of received DLT messages in the trace analysis (from DLT or PCAP traces).
- Specification in the test configuration gives access via object-value signals
- Reuse of the filter files from the DLT viewer
- API access to various attributes, such as applicationId or arguments
- Identical data object in the Trace Analysis
- Offline analysis of DLT and PCAP recordings
A new OpenAPI based REST-API allows to execute test cases and upload test results to TEST-GUIDE. The REST-API is available for Windows and Linux and can be configured for remote access. This simplifies interaction with TRACE-CHECK, especially in container-based environments. After starting TRACE-CHECK the REST-API is available under http://127.0.0.1:5050/api/v1. An interactive swagger documentation can be viewed at http://127.0.0.1:5050/api/v1/ui.
The STI file editor included in TRACE-CHECK has been fundamentally revised. STI files in versions 2.1 and 2.2 can now be created and edited. In addition to several performance improvements, the following new features are available, among others:
- It is now possible to set a cursor to read concrete data points in the signal curve.
- STI and STZ files can be opened directly from the editor.
- The height and width of individual signal panels are configurable and can be automatically adjusted to the window size.
- Segments can be converted to a value table with a right click in the workspace.
- The time axis can be limited to the last signal to increase the display range of all signals.
- Freely placeable cursor to read concrete data points from the signal
- Performance improvements
Since several releases it is possible to implement stimulations modularly in a separate artifact (stimulation package). The new test step Request Analysis allows you to link associated analyses from analysis packages more closely to the stimulation. For example, the structure of a stimulation based on reusable subcycles can be formulated. This ensures that a requested analysis is actually implemented (project check and execution). The result of the analysis is optionally carried over into the test case of the requesting stimulation package. This feature is also suitable for users who are currently on the way to more global, reusable stimulations and can still outsource tests to analysis packages.
When calling the AutoSPY Viewer from the report, only those signals are displayed that were processed by the trace step currently selected in the report. Additionally, the AutoSPY Viewer offers a complete list of all signals of the trace analysis, grouped by episodes, and allows to show and hide them individually.
Further formerly event-based trace step templates were re-implemented as much more efficient array-based NumPy trace step templates (CalculateTriggerForDeltaY, CalculateUpsampledSignal, SavitzkyGolayFilter). Improved performance is also achieved for the processing of stimulus files (*.sti), as NumPy is now used here as well.
In the signal recording of a package, you can now add, delete, rearrange or move all elements to other groups by multi-selection. The latter simplifies the use of the Assign automatically signal group, which reassigns contained signals to the correct signal groups depending on the mapping. New configuration options of the recording group allow that an associated signal group depending can - depending on the loaded mapping - also be empty or contain only unmapped generic targets for the formulation of a synchronization, which is useful, when the signal group is not required or not applicable for certain variants.
For new packages the synchronization of recordings must be configured in the tab Signal recordings since several releases. With PRODUCTNAME 2020.2, an (often redundant) synchronization directly before the trace analysis is no longer possible and existing packages must be migrated. To automate this process wherever possible, a new migration helper is available at Help → Migration help → Trace synchronization. Only packages in which multiple, incompatible synchronizations are defined still require very little manual rework.