ECU-TEST Release 2022.2
Linux support
With the release of the new ECU-TEST version 2022.2, test cases can now also be executed at scale in Linux-based cloud systems. For ECU-TEST users who previously worked under Windows, it is thus quite easy to switch to an SiL test environment in the cloud.
The delivery contents of the ECU-TEST Runner include a DEB(debian) package, the user help and setting instructions. The instruction will support the user in setting a docker container which can then execute the runner. At this time the Ubuntu version 20.04. LTS is supported. The Linux version of ECU-TEST will not include a graphical user interface.
For more details about ECU-TEST under Linux have a look in the adjacent video.
Library workspace
In ECU-TEST there is a new library function – the library workspace. The packages, project generators and user Python modules (UserPyModules) of a workspace can be outsourced to this.
This is practical because the content created in the library workspaces can then be integrated into packages and projects in other workspaces as usual and reused there.
In ECU-TEST, the elements of the library workspaces are clearly distinguished from those of the main workspace by their blue color scheme.
A workspace can use any number of library workspaces. The integration of such libraries into another workspace is done by specifying the path in ECU-TEST settings. The creation of a library workspace is also done via the Manifest page in the Settings dialog.
MACsec
In modern E/E architectures, increasing security measures are being adopted to prevent known attack patterns on vehicle communication. One measure consists of cryptographic protection of parts or all of the onboard network communication.
In addition to IPsec and TLS, implementation of the MACsec protocol in the onboard network can also serve this purpose.
ECU-TEST now also allows for securing of cryptographically protected Ethernet networks. For this purpose, the built-in network solution offers establishment of and communication over MACsec-protected channels.
Session keys are negotiated using the MACsec Key Agreement (MKA) in conjunction with a static (pre-shared) Connectivity Association Key (CAK).
Currently, only integrity protection is supported. Encryption is not yet part of the range of functions.
Time synchronization via CAN and FlexRay with Vector hardware
With ECU-TEST it is now possible to specify a precise time on a bus system according to the following AUTOSAR protocol:
- Time Synchronization over CAN/FlexRay or IEEE 802.1AS
In addition to supporting the timing slave, ECU-TEST assumes the role of timing master.
Activation takes place on a manipulation port via the job:
- StartTimeSyncMaster
To ensure accuracy during implementation, hardware timestamps from the Vector measurement hardware are used. If there is a need for additional measurement hardware support, please feel free to contact us.
Efficient filtering of very high Ethernet data rates for multiple PLP data frames
In previous versions of ECU-TEST, improvements were implemented for the evaluation of passively received SOME/IP messages regarding performance. The efficient filtering of very high Ethernet data rates contributed to this.
These filtering mechanisms now also take effect in connection with CMP/PLP data streams. The BPF generator supports filtering of up to four PLP data frames in a PLP packet. The following job is available for this purpose:
- LearnBPFilter
Selenium
Value-added services, such as querying the vehicle's charging status, are already possible away from the vehicle via app and web interfaces.
In order to be able to test vehicle communication with the backend, as well as the functionality of actions via web interface, ECU-TEST now offers a connection to Selenium – a framework that simulates user interactions with the web browser.
For this connection, different jobs are available in ECU-TEST, which can be used to check the content of the web pages for different criteria (image, text).
More details are available in the adjacent video.
The prerequisite is a web driver for the browser in question, e.g.:
- Geckodriver.exe – Firefox
- Chromedriver.exe – Google Chrome
In the testbench configuration, paths are set to both the installed web browser and the web driver.
