Recording control¶
This category contains test steps for trace recording control. By means of the test steps in this group it is possible to record signal variations and process them with the help of our trace analysis tool.
Start trace¶
The test step Start trace provides the opportunity to start a recording for one or all (available) recording group(s). In a recording group, several signals are defined, which have to be read from a tool.
Info
Signal recordings read signals from a tool and permit further processing by means of the trace analysis tool. The configuration of the trace analysis takes place in the working area via trace analysis
To start a recording, it is necessary to select either an existing recording group or the option All recording groups. The fields of the control are adjusted according to the current selection and display data source, file path and description (of the signal group). The field name allows the user to reference the start of the recording by a unique name.
Add trace¶
Info
An overview of supported file formats and specific information about when and how to use the device name and the format details can be found in the section Supported file formats.
Info
If the documentation of the formats does not fully reveal the correct parameterization, it is recommended to create a recording using ecu.test and check in the report, which device identifier and which format details are automatically used by ecu.test. Therefore, select the item “Recordings” in the overview tree of the report. In the table of all recordings, which is then displayed, you can search for the file in question. In the column Recording, the device identifier is shown before the parentheses and the format details are shown within.
With the test step Add trace it is possible to add a recording to a recording group. First of all, an existing recording source (e.g. an MDF-File) has to be selected. The “Open” button can select trace files (default) or directories as traces (available through the context menu). The recording path can be absolute or relative to the used workspace.
Recordings contain one or more signal groups, each of which usually corresponds to a recorded device (e.g. A-CAN, DME1_DDE1). Therefore, the device can be specified in the input field underneath. The value can optionally be written as a regular expression (see https://docs.python.org/3/library/re.html). At execution time, the regular expression is checked against the available device identifiers and must then uniquely match an identifier.
As a second option a format details string can be entered. The structure of the format details is format-dependent and can be looked up under Supported file formats for the respective format.
The Filter option is currently only relevant for the PCAP format. Based on the filter, entries of the file are discarded if they do not meet the filter condition. For more information about the filter, see PCAP/PCAPNG.
The recording trace can be copied to the report directory before the trace analysis by activating the option Copy trace into report directory. If a name template is defined in the corresponding recording group of the test step, it will be applied to the trace name of the copied file or directory. A name template defined in the recording group will be displayed in the dialog of the Add Trace test step under Target name.
Stop trace¶
The test step Stop trace stops one or all recording(s). It is necessary to either select the respective recording group or the option All recording groups. The field name offers the user the opportunity to reference the end of the recording by a unique name.
The option Condition for recording usage may be used to specify a condition that a recording must fulfill in order to not be discarded.
Set trace comment¶
The test step Set Trace Comment adds a comment to created recordings. The test step must be called only once within the test case. A repeated call will overwrite the previous comment. The comment is written into the recordings at the end of the test case.
Currently, this functionality is only supported for MDF4 files.