ECU-TEST supports active and passive network communication for many protocols used in the automotive field. These include service-based communication via SOME/IP, DLT, AUTOSAR Socket Adaptor and many more.
A new feature is the ability to use all of these protocols directly with Ethernet-capable measurement hardware from Vector in a network-based mode. This eliminates the need to connect the measurement hardware to the network card via mirroring mode.
ECU-TEST Release 2021.2
Top features at a glance
Use of all supported network protocols with Vector Ethernet measurement hardware
Improved support of service-based communication
In order to extend the usage possibilities of the service-based communication, several new enhancements have been implemented:
Furthermoore, there is access to services even if only the service-consumer relationship is mapped in the (ARXML) description file (ECU extract)
- Configurable behavior for handling SOME/IP protocol errors and informative reporting
- Selectable source ports for active SOME/IP service communication: communication even in firewall-protected networks
- Manual control of the ECU-TEST service discovery mechanism for recording and analysis during the startup phase
Furthermoore, there is access to services even if only the service-consumer relationship is mapped in the (ARXML) description file (ECU extract)
Playbook creation for the Automotive DevOps Platform
Playbooks are the central element in the Automotive DevOps Platform for the execution of test orders distributed on multiple test benches. Playbooks describe the workspace to be used – including test cases as well as the test bench setup and test bench teardown. Additionally, the three sections Setup, Tests and Teardown can be parametrized using global constants.
With the new feature Generate Playbooks from ECU-TEST, playbooks can be created in the already familiar project editor GUI. By using the already existing TEST-GUIDE connection, they can be uploaded to TEST-GUIDE directly from ECU-TEST.
An included Template project with the given folders Setup, Test and Teardown simplifies the creation of playbooks. More information on this can be found in the user documentation.
With the new feature Generate Playbooks from ECU-TEST, playbooks can be created in the already familiar project editor GUI. By using the already existing TEST-GUIDE connection, they can be uploaded to TEST-GUIDE directly from ECU-TEST.
An included Template project with the given folders Setup, Test and Teardown simplifies the creation of playbooks. More information on this can be found in the user documentation.
Access to structured signal data for ASAM Open Simulation Interfaces (OSI)
OSI data streams contain complex and also structured signals. For the creation of test cases and analyses, ECU-TEST offers the possibility of using complex structures in the test case and trace analysis in addition to leaf elements. Structures can be read and recorded in the test case, as well as used in trace analysis. Access to the elements of a structure is simplified by an auto-completion mechanism.
The feature can be activated on request. If you are interested, please contact our support.
The feature can be activated on request. If you are interested, please contact our support.
ASAM XIL: Dummy-Server and TestSuite as support to connect your own tools to ECU-TEST
ECU-TEST contains a tool connector called ASAM XIL which enables you to connect a variety of tools which implement a server interface according to the ASAM XIL-API.
This standard defines the interfaces for model, measurement, calibration and error simulation ports. Using these ports, you can read, write, record and play back stimulation sequences on variables.
The interface is also often used by users of ECU-TEST to connect tools they develop themselves to ECU-TEST.
This standard defines the interfaces for model, measurement, calibration and error simulation ports. Using these ports, you can read, write, record and play back stimulation sequences on variables.
The interface is also often used by users of ECU-TEST to connect tools they develop themselves to ECU-TEST.
To support this, we have created a starter package which is available on demand from our customer support. It contains a working dummy server – including source code – which could be a good foundation for implementing your own server.
To test the compatibility of your server with ECU-TEST, we also provide a TestSuite.
This TestSuite contains a generator to help you to create the configurations and mappings, as well as select the suitable test cases for your server. After executing the generator you will receive a project in ECU-TEST which tests all the core functionality of the ASAM XIL interface and which creates a report document as reference for your level of compatibility.
To test the compatibility of your server with ECU-TEST, we also provide a TestSuite.
This TestSuite contains a generator to help you to create the configurations and mappings, as well as select the suitable test cases for your server. After executing the generator you will receive a project in ECU-TEST which tests all the core functionality of the ASAM XIL interface and which creates a report document as reference for your level of compatibility.
More flexible test cases using generic job/Image mappings and parameterized library Packages
In many use cases, it is useful to separate the read or write access of a test quantity together with necessary pre- and post-processing in a library Package. If the test quantity is not fixed, but you would like to use the pre- and post-processing for different test quantities, you need to alter the used mapping.
This can be done using global mappings or parameter sets in a project, but is limited to one test quantity per test case as these mechanisms cannot change the mapping within a Package run.
But there is another, more flexible mechanism – parameterized mapping on Package calls. Using parameterized mapping, you can manipulate the mapping to be used within the Package called up.
This can be done using global mappings or parameter sets in a project, but is limited to one test quantity per test case as these mechanisms cannot change the mapping within a Package run.
But there is another, more flexible mechanism – parameterized mapping on Package calls. Using parameterized mapping, you can manipulate the mapping to be used within the Package called up.
This mechanism is available only for those mappings in the library Package which are of a generic type. This means that they do not point to a real target path.
Therefore, the mechanism was not available for jobs and image mappings. This has been changed with ECU-TEST 2021.2. Now you can create a library Package that reads an image mask, preprocesses the read image and applies text recognition. This Package can be used subsequently at any point of the test case. This approach improves the structure of your test cases and prevents redundant implementations of the same logic which lead to unnecessary maintenance work in the long run.
Therefore, the mechanism was not available for jobs and image mappings. This has been changed with ECU-TEST 2021.2. Now you can create a library Package that reads an image mask, preprocesses the read image and applies text recognition. This Package can be used subsequently at any point of the test case. This approach improves the structure of your test cases and prevents redundant implementations of the same logic which lead to unnecessary maintenance work in the long run.
Downstream analysis execution distributed by TEST-GUIDE
By performing trace analysis downstream, you can release valuable test resources sooner and significantly increase the test throughput of your HiLs/prototypes.
For projects or packages that are executed with downstream analysis, only the test case is initially taken into consideration. The resulting recordings and analysis jobs are passed on to a configured TEST-GUIDE, which distributes the analyses to available infrastructure.The TEST-GUIDE ResourceAdapter simplifies making ECU-TEST available on physical or virtual machines or in containerized environments. After completion, the results of the analyses are automatically collected in TEST-GUIDE.
In addition to this application scenario, downstream analysis distribution is also available in the Automotive DevOps Platform workflows with playbooks.
For projects or packages that are executed with downstream analysis, only the test case is initially taken into consideration. The resulting recordings and analysis jobs are passed on to a configured TEST-GUIDE, which distributes the analyses to available infrastructure.
In addition to this application scenario, downstream analysis distribution is also available in the Automotive DevOps Platform workflows with playbooks.
New tool connectors for scenario-based testing: DYNA4 and SCANeR
For scenario-based testing, ECU-TEST offers two new tool connectors: DYNA4 from Vector Informatik GmbH and SCANeR from AVSimulation.
DYNA4 is an open simulation environment for virtual test driving. The DYNA4 connector offers the possibility of loading, parameterizing and starting tasks by using tool jobs.
SCANeR provides a simulation platform for creating and executing test scenarios in a virtual environment. The resulting recordings can be fetched and used in trace analysis. For SCANeR, it is possible to control and parameterize the simulation.
DYNA4 is an open simulation environment for virtual test driving. The DYNA4 connector offers the possibility of loading, parameterizing and starting tasks by using tool jobs.
SCANeR provides a simulation platform for creating and executing test scenarios in a virtual environment. The resulting recordings can be fetched and used in trace analysis. For SCANeR, it is possible to control and parameterize the simulation.
