Test configuration editor¶
The test configuration editor allows to create and to modify test configuration files (.tcf files). Many tools need specific files, which describe the test objects. ecu.test can read some of these data types and displays their contents in the action window, based on which the user can create test cases.
Import and export¶
A test configuration and its related artifacts can be imported from an archive or exported to an archive via the menu or .
When a test configuration is exported to an archive, the test configuration is packed into a file together with the selected referenced artifact files. These files include databases, diagnostic, A2L, HEX, model, and simulation files, for example. Mapping files and global constants are not included in the archive. This also applies to files on the tool host and files referenced by artifacts.
When such a test configuration archive is imported again, the test configuration is added to the
configuration directory defined in the settings. The contained artifacts are stored in the workspace
under DataBases/<name of the test configuration>. The references in the imported test
configuration are adjusted to the new storage locations. If the files already exist, the user is
asked whether the import should be canceled or parts of the workspace should be overwritten.
Supported file formats¶
The following table shows the file formats that can be used by ecu.test within test configurations.
Format |
Extension |
Version |
Vendor |
Usage |
Note |
|---|---|---|---|---|---|
CAN bus database |
.dbc |
Bus Tools |
|||
Field Bus Exchange Format (FIBEX) |
.xml, .fbx |
1.1.5a, 1.2.0a, 2.0.1, 3.0.0, 3.1.0, 3.1.1, 4.0.0, 4.0.2, 4.1.0, 4.1.1, 4.1.2 (for services only) |
ASAM MCD 2NET |
Bus Tools |
|
AUTOSAR System Description (Classic Platform) |
.arxml |
3.0.2, 3.1.4, 3.1.5, 3.2.1, 3.2.2, 4.1.1 [1], 4.2.2 [2], 4.3.0 [2], 4.3.1 [3], 4.4.0 [3], 19.11 [3], 20.11 [3], 21.11 [3] |
AUTOSAR |
Bus Tools, Ethernet (SERVICE: 4.3.0 or later, SOCKET-ADAPTOR: 4.2.2 or later) [4] |
Starting with version 4 the following bus systems are supported: CAN/CAN FD, FlexRay, LIN |
AUTOSAR System Description (Adaptive Platform) |
.arxml |
17.10, 18.03, 18.10, 19.11, 20.11 |
AUTOSAR |
Ethernet |
Implemented as prototype |
LIN Description File |
.ldf |
Bus Tools |
|||
ASAP2 Datenbank (A2L) |
.a2l |
ASAM MCD 2 MC |
Application Tools |
||
Executable and Linkable Format |
.elf |
DWARF 2, 3, 4, 5 |
Debugger Tools |
||
Model description file |
.sdf, .trc |
dSPACE |
ControlDesk Tool |
||
SUT Mapping File |
.smf |
3.1 |
Vehinfo |
LABCAR |
|
XiL configuration file |
.xml |
ASAM |
XiL access (EES, MA) |
||
Intel HEX |
.hex |
Application Tools |
|||
Motorola S19 |
.s19 |
Application Tools |
|||
Open Diagnostic Data Exchange Format (ODX) |
.odx, .odx-d, .pdx |
2.2.0 |
ASAM MCD 2 D |
||
Global Diagnostic Data Export (GDX) |
.gdx, .mdx |
4.1, 4.2, 5.0 |
|||
CANdela Diagnostic Data (CDD) |
.cdd |
from 6.5, testet up to 9.1EC |
Vector Informatik GmbH |
||
Zip Archive |
.zip |
Bus-Tools |
Bus databases can be specified as Zip archives. An archive should only include a single file of an arbitrary bus database format [5] |