Settings¶

If the settings menu is opened, a window appears which is divided into two parts. On the left side there are the menu items which can be configured, on the right the corresponding settings.

Depending on their area of application settings in ecu.test are split into two categories:

• Workspace settings

• Local settings

Workspace settings are settings specific to projects and therefore also to the workspace. To allow the exchange of these settings via an version management system between different computers, settings are stored thematically separated.

Local settings are settings which are specific for the user or the computer. These settings are stored in the file localsettings.xml (in %appdata%/tracetronic/trace.check 2026.3/).

By means of the button OK the settings are accepted; Cancel closes the dialog without saving the settings.

Workspace settings¶

Directories¶

Here the ecu.test default directories for test configurations, packages, test reports, trace step templates, package/project templates and report generators are stored.

All directory paths should be relative to the path of the workspace if possible. This allows to move the complete workspace without additional modifications. If a given path is outside of the workspace it will be stored as absolute path.

These settings indicate in which directory ecu.test

• searches for configurations,

• searches for packages,

• stores test reports by default,

• searches for trace step templates,

• searches for package/project templates and report generators.

Directories which do not exist yet are highlighted in yellow and will be created upon confirmation by OK.

Protocol¶

Here it can be determined what kind of messages should be displayed in the message window . First of all, a level is selected:

• Off: no ecu.test messages are displayed

• Minimum: only failure messages are displayed

• Standard: failure messages and important information are displayed

• Maximum: all ecu.test messages are displayed

Messages are always displayed in the message window and written to the ecu.test log files. Under Additional targets you can specify whether messages should be logged to the standard output or the Windows Logging Api as well.

Additional log content can be activated in section Content. Generally, this is only necessary if demanded by the support.

Trace analysis¶

Here it can be determined how the trace analysis shall react in different situations.

Common

In this section you can make general settings for analysis execution.

Round timestamps

Timestamps of read-in and calculated signals are rounded to a defined number of decimal places to ensure comparability of the time axes.

Cache signals

If this option is active, signals are cached during the project execution. This speeds up access to signals when they are used in multiple episodes, trace analyses or packages and can have a positive effect on the execution speed of trace analyses. At the end of the project execution, the cache is emptied. For large projects that use a large number of signals, ecu.test may run out of memory. In such a case this setting should be deactivated. Alternatively, the cache can be cleared manually during project execution by calling the ClearSignalCache() method of the Internal API in a package.

ASC, BLF, GIN: Fix duplicate timestamps in files

Determines, how ecu.test shall deal with duplicating time stamps in a file, since theoretically several measured values are now available for one signal for one time. If this option not active ecu.test will about the analysis with a fault. If the option is active ecu.test will separate identical time stamps by inserting micro time steps of 0.0000001 seconds.

ETHERNET, DLT: Sort timestamps via moving window

Only PCAP, MDF4 and DLT: Due to internals of the network communication or the recording it can happen that messages in bus logging files are not sorted chronologically. With this option a moving window is maintained while reading the file, in which entries are sorted by time. The window size determines the count of subsequent packets after which a packet with an earlier timestamp can still be correctly sorted. Thus, a larger window provides more robustness.

The size of the window can influence the SOME/IP TP assembling and therefore the number of SOME/IP samples.

PCAP: Intelligent filtering of SOME/IP messages

If this setting is activated, an efficient filter is trained based on the SOME/IP communication over the parameterized duration. By using the filter the duration of reading in SOME/IP messages is reduced.

Typically, a duration of about 2 seconds is sufficient so that all relevant service providers can be detected and included in the filter. Services that are only provided after the learning phase may be filtered out.

PDU Update-bit ignoreren

The update bit of a PDU indicates whether the contained data has changed. If activated, PDUs will be read and evaluated independent of the update bit. By default, this will only happen if the bit is set to 1.

This setting is only used when message-based data is read in.

Fehlermeldung für fehlerhafte PDUs unterdrücken

By default, bad PDUs, e.g. due to invalid length, will result in an error. This setting indicates that instead of an error, only a warning should be printed to the log and the corresponding PDU will be ignored.

This setting is only used when message-based data is read in.

Fall back to raw values…

Specifies how to handle signals whose raw values cannot be converted into physical values. If the option is active, the raw value will be automatically used instead. Otherwise an ERROR with a corresponding error message is reported in the report. (Only PCAP, ASC, BLF, MDF 3/4, TTL)

Executing analysis jobs in parallel for projects

This section allows configuring the number of processes and their priority. The number of processes is limited to the number of available CPU cores of the system.

Reporting

In this category settings can be made that affect the resulting report of the trace analysis.

Round displayed timestamps to decimal places

This setting can be used to specify the number of decimal places displayed for timestamps in the report.

Caution

Only a newly created report will be affected!

Relevant locations in the report:

• Table of findings in report details

• Automatically generated titles in plots

The accuracy of the representation is limited by floating point arithmetic (more precisely by the number of significant digits).

Save used signals in trace.xplorer format

The signals used in the trace analysis are additionally saved in the *.astrace file format. This option is recommended if trace.xplorer basic or trace.xplorer is used as the signal viewer (see section Included programs in the local settings).

trace.xplorer format (*.astrace)

In this category, options can be set for the automatic conversion of data when writing *.astrace files. These settings are also effective when using the Signal export (signal recording) trace step.

• Save numerical signals that only contain the values 0 or 1 as Boolean signals

• Save floating-point signals that only contain integer values as integer signals

• Save string signals that only contain numerical values as integer or floating-point signals

• Save string signals

Version management¶

Here you can define different options for version control connection. In the first section you can select the version control system used (currently SVN and Git).

In order to use SVN respectively Git, TortoiseSVN respectively TortoiseGit must already be installed on the PC. Both programs are freely available on the Internet and can be downloaded there.

In the second setting field Automatic check the automatic comparison of working copy and repository for individual directories (currently only the package directory) can be activated or deactivated. If the automatic check for a directory is activated, e.g. for the package directory, ecu.test checks with each start if the files in the repository are newer than those in the local directory. Furthermore, ecu.test checks before exiting the program, if the working directory contains changed files, that have not yet been transferred to the repository. A dialog informs about available updates or changes and offers through a button the possibility to update or commit (update and commit are thus only executed upon user request).

The settings field Options offers the possibility to configure version control systems. When activating the field Add automatically new files and directories files and directories that are newly created, moved or copied in ecu.test are automatically added for the repository so that these files are taken over into the version control system with the next commit/push.

When working on a package at the same time by different people, conflicts can occur. These are marked by SVN respectively Git directly in the file. Due to these changes to the package, ecu.test can no longer open the package until the conflict is resolved and reports that the package is defective.

Report¶

Here it can be specified if test reports shall be checked for authenticity when being opened.

Here you can also set whether the new, JSON-based .prf format shall be used for project reports. It saves the results of all project steps and for each package refers to a .trf report with the results of the individual test steps. The new .prf format has advantages over the monolithic .trf reports previously used for projects, particularly in conjunction with test.guide, and is the standard format for project reports as of version ecu.test 2024.3.

System identifier¶

Here system identifiers can be configured for use in a test configuration (in the tab Bus access).

You can see all identifiers currently available for buses. In order to create a new identifier, delete existing ones or change their order, click on the lower right side on Edit name.

In the opening window on the upper right side you can find four buttons for editing identifiers:

• New item,

• Delete item,

• Move up,

• Move down.

Local settings¶

Workspaces¶

An overview of all configured workspaces is shown. It is possible to remove workspaces from the list. In addition, it is possible to decide whether the workspace selection dialog should be shown at the start of ecu.test or the last workspace should be used.

Language¶

Here the language of ecu.test can be set. Please note that this change (unlike any other) will not become effective until next restart of ecu.test.

Report filters¶

Here new filters and groups of filters can be set up to be used in a test configuration or a test report.

The window contains two columns:

Filter groups arranges several filters (from the right side) into one common filter. The individual filters are AND-connected.

Filter library sets up (elementary) filters. Filters can be assembled into groups on the left side. If they are used in test reports and several of them are selected, they are OR-connected, contrary to filter groups, which means that all steps are displayed in which filter1 or filter 2 or … are valid.

The first button (A, only filter library) serves to open settings. By means of the button New a new filter group or a new elementary filter can be created. The third button deletes the filter group or the filter selected.

In order to create a new filter click on the button New of the Filter library. Choose in the opening library which package element should correspond to which criterion.

For setting up a new filter group, click on the button New of Filter group. A new group will be created and marked. Now activate on the right side the filters to be assembled in that filter group. The selected filters are AND-connected, so all filters existing in the group must be valid in order to fulfill the condition of the filter group.

The selection of a filter contradicting another filter which is already marked will lead to the previously marked filter being deactivated.

Example: Evaluation == FAILED is already selected, and evaluation == ERROR is being chosen. Since both filters check the evaluation as to its identity, an AND-connection would result in an unsolvable condition. In order to prevent this, evaluation == FAILED is deselected.

To remove a filter group or a filter, mark the respective entry and click above the selection box on the Delete button.

Automatic Report Download from test.guide

Reports from test.guide are cached locally to expedite subsequent access. To prevent storage issues, the following settings are automatically checked with each report download:

• Maximum total size of all cached reports (GB): Once all cached reports exceed this size, the oldest reports will be deleted until the total size is below the limit (default: 20 GB). This also applies if the maximum duration has not been reached yet.

• Maximum duration for which reports should be retained (days): Downloaded reports that have not been opened for a specified number of days (default: 7 days) will be removed regardless of their file size.

Included programs¶

The default program for viewing traces can be selected in this section. The trace.xplorer offers the widest range of functions, but requires an additional license. The trace.xplorer basic and the Signal Viewer can be used without additional licenses.

For the best possible use of the trace.xplorer variants, it is recommended to activate the option to save the used signals in trace.xplorer format (*.astrace) in the workspace settings of the Trace analysis section.