... Updates older versions

The CarSim connection has been revised and changed. Access now takes place via the Environment simulation tab. This means that the test steps and statistics already familiar from other connections can be used. This makes the test setup more flexible, since loading and starting a scenario are now carried out separately.

Depending on the time mode, there are tool jobs to be used instead of starting and stopping the simulation. These also enable special tasks, such as sending the model to Simulink or Scalexio.

The simulation interface OSI is a generic interface for the environment perception of automated driving functions in virtual scenarios. OSI defines variables that can be read by ECU-TEST. The inclusion of GroundTruth, SensorData and SensorView data allows comparison of virtual events in the scenarios and sensor data with the driving function response. With the new connection of ECU-TEST to OSI, the test case developer has the possibility to use environmental information such as GroundTruth or sensor data for test activities based on a standard. In the subsequent trace analysis, recorded OSI traces can be automatically evaluated with the recordings relating to the driving function.

Technical details:

• Connection via the ZeroMQ tool adapter
• Communication via the ZeroMQ network library
• Support of the standard in version 3.2.0
• Reading and evaluation of GroundTruth, SensoData, and SensoView data
• Automated recording and evaluation of OSI traces

In the course of a package or project preparation, it is worth performing a plausibility check and thus obtaining information about incorrect references or missing variables.

In addition to the already integrated check mechanisms, user-specific package checks and project checks can now be created in the form of scripts. These are stored in the UserPyModules folder as a .py file of the current workspace and are automatically applied when the Check package or Check project functions are executed.

Note: In order for changes to these scripts to take effect without an ECU-TEST restart, a reload can be initiated via Extras/Update user libraries.

Prior to the automated execution of a test order from an ALM system (*), numerous preparatory tasks must be completed, such as:

• Determining a suitable test bench for the underlying metadata of the test order
• Setting up the test station and test object: Configuring settings
• Selecting test implementations suitable for the job and configuring settings, if necessary

(*) supported ALM systems: Micro Focus ALM.NET and ALM Octane, Siemens Polarion, Rally / CA Agile Central

The new flexible test order import now makes it possible to automate these preparatory tasks. For this purpose, a Python script is stored in the workspace. When importing the test order via API or the Test management/Import project workspace context menu, the script is automatically executed and the metadata of the test order and the list of the required test cases are transferred. In this way, a completely suitable ECU-TEST project can be generated, which can be immediately executed fully automatically at the test station.

ECU-TEST can import specifications from ALM system (*) and use them to create the basic framework for a new test scenario package.

The new flexible import makes it possible to influence this creation in such a way that the test scenario package already meets certain requirements after creation. For this purpose, a Python script must be stored in the workspace.

When importing test cases from an ALM system, this script then receives the list of steps from the test scenario specification and the metadata associated with the test scenario.

Recurring manual implementation tasks that were previously required can be automated using this script. For example, the following tasks can be automated:

• Insertion of recurring test steps in the test scenario precondition
• Automatic insertion of predefined implementation steps for recurring specification steps
• Creation of mappings or variables that are required at all times

(*) supported ALM systems: Microfocus ALM.NET and ALM Octane, Siemens Polarion, Rally / CA Agile Central, Jama Connect

The connection to froglogic: Squish is now available for graphical user interface testing – in addition to JS Foundation: Appium. In the test scenario, this tool interacts via a Squish server with the user interface of applications on different platforms (desktop, mobile devices or embedded systems) and in a wide range of technologies. Besides stimulating the application with job test steps, the current screen content can be read and analyzed and evaluated with the image-reading test step and filters. This enables the automated testing of passive display elements, as well as complex control elements with touch functions, such as those widely used in infotainment systems.

The image port of ECU-TEST now offers the option to display the current image of the camera or the currently configured video stream live in a separate window. This gives you a constant view of the test object and makes troubleshooting much easier.

The ECU-TEST Diagnostics add-on now allows use of the Diagnostics over IP (DoIP) transport protocol.

• DOIP-SOCKET
• DOIP-PCAP

Connection settings are available for this purpose in the test configuration. DoIP offers the same range of functions as the already familiar UDS diagnostics via CAN. In this context, many improvements in the support of the ODX and CDD diagnostic databases have been added.

To ensure the testing of service-based communication, ECU-TEST grants access to structured data as defined in a service description in ARXML format. This structured data can now be used efficiently in signal recording and trace analysis. Events and methods from the Service tab can be dragged into the signal recording in order to record them. (This uses the well-known ECU-TEST mapping mechanism)

In the resulting PCAP traces of the Ethernet communication, these events and methods can then be evaluated using trace analysis. Input-supported attribute access to substructures is possible in trace analysis. Furthermore, index access to the individual components of a vector is also supported.

Teams and projects using the same bus and service databases can now increase their productivity. When a bus or service database is imported for the first time, the caches that can be stored encrypted in a shared cache directory are generated. Other team members can use them for their project and save the long waiting time it sometimes takes to incorporate the databases.

To this end, in the Workspace settings under the option Directories the new field Shared Cache Exchange Directory has been implemented.

The FMI connection for the FMUs simulation offers numerous new possibilities:

• Execution of SiL tests (FMI standard) tool-independent also on Linux
• Hierarchical representation of structured variables in the model tree
• Usage of vectors and matrices in test case and trace analysis
• Explicit selection of the Model Exchange or Co-Simulation simulation mode, especially for the FMUs that support both

Use-Cases

• ECU-TEST as a member in a co-simulation environment, which acts as the timing master

• Testing of virtual ECUs with direct access and indirect access via 3rd party tools

New continuous simulation mode

1. Test cases run in simulation time
2. Platform acting as time source and simulation control
3. Reporting of both simulation and real time

• Reset of parameters after simulation stop
• Manipulation of signals over a defined period
• New continuous simulation mode for testing in simulation time
• Support of physical units in trace analysis

• Stimulation of signals and parameters
• Reset of signals and parameters
• New continuous simulation mode for testing in simulation time
• Support for 32-Bit-FMUs

1. Support for FEP Metamodell 2
2. Demultiplexing of FEP-VU ObjectStates and VehicleAppearance

Linux compatible Tools

• Multimedia
• FEP
• ADTF
• VTD
• SSH
• User ToolAdapter

1. Tool server for Linux
2. REST-API for controlling ECU-TEST under Linux

1. Access complex return values of DID, RoutineCtrl and IoCtrl directly within the read test step
2. Autocompletion for sub elements and structures

1. AUTOSAR PDUs via Socket Adaptor
2. Full IPv6 support
3. AUTOSAR SOME/IP with optional structural elements
4. Recording, analysis, and replay of PCAPNG

Updated and new formats

• BLF-Traces for LIN and Raw Ethernet Analyses
• ASC: Performance Improvement
• PCAPNG

New Standards

• AUTOSAR-PDUs via Socket Adaptor

Updated Tools

• ATI VISION 6
• FEP 2.7.1
• NI LabView 2020
• NI VeriStand 2020
• OPAL RTLAB 2020.2
• Vires VTD 2019/2020
• VW ODIS 12.2

Motivation

• Analysis can be dependent upon variations in test object and test environment

„Solving this with parameterized generic analyses quickly gets very hard to maintain“

• Separation of roles and domain responsibilities can require separation of stimulation and analysis

New Feature “assign analyses to stimulations by global mapping“

Workflow

1. Teststep Request analysis defines label
2. Assign analysis packages via global mapping

Test step “request analysis”

• Defines a label (e.g. „CheckVelocity“)
• Acts as a placeholder for analysis
• Analysis results can be integrated into test case report
• Can be used to run analyses conditionally (e.g. within If-Then-Else Test step)
• “Request analysis” steps and actual analyses are linked within project reports and support quick jump via context menu

Package property “Stimulation package”

• Stimulation packages make their recordings available to associated analysis packages
• Stimulation packages are treated accordingly when inserted into a project
• Also read- and writeable via Object-API

1. Workspace filter for searching stimulation packages

1. Automatically created placeholders for every requested analysis
2. Assigning actual analysis package to these placeholders can be done locally via drag and drop from workspace explorer

1. Check project feature also shows requested analyses with no currently assigned analysis package
2. For currently unassinged by requestes analyses global mapping items can be generated

1. Assigning analysis packages via Drag & Drop to global mapping
2. Analysis mappings can also be drag into stimulation packages to create „request analysis“ test steps

1. Create new global mappings via Drag & Drop to mapping editor

1. Generates a parameter set for every trace in the specified directory
2. Generator source code is provided and can be enhanced or adapted to fit custom use cases

Generator for flexible and simple generation of signal comparison test cases such as reference or back to back tests

• Generation of packages or parameter sets
• Configurable signal association
• Individual signal comparison terms
• Configurable with GUI or as code

In ECU-TEST test case specifications can be edited and saved as “specification packages”: New package property “Specification”

Implementation packages can be derived from a specification package:

Implementation packages are linked to their specification package:

A comparison of both packages, e.g. to detect changes in specification compared to the implementation, is possible:

Test execution playbook overview

1) Preparation and implementation with ECU-TEST

• Project structuring: setup, tests, teardown
• Upload project as playbook to TEST-GUIDE

2) Parallelization and distribution with TEST-GUIDE

• Convert playbooks to one or more test execution jobs
• Distribute test execution orders to suitable, free test benches

3) Execution with ECU-TEST

• Execute test execution orders with ECU-TEST via the TEST-GUIDE ResourceAdapter
• The new ECU-TEST REST-API allows automated execution

Prepare playbook in ECU-TEST

Conventions

• Setup steps are executed before the first test
• Teardown steps are executed after all tests
• The tests are independent of each other and can be distributed and executed in any order

Workspace

• Stored in the source code management system: Git URL, Git Revision (commit hash)

Distributed test execution

TEST-GUIDE can distribute test execution orders to a variety of physical and virtual test benches

Basic approach: Simply outsource ECU-TEST report uploads to TEST-GUIDE so that ECU-TEST can continue testing immediately!

In ECU-TEST uploadThroughResourceAdapter must be configured.

TEST-GUIDE ResourceAdapter takes over.

Done. Time saved.

Details: https://www.test-guide.info/changelog/#_version_1_84_2_released_2020_09_30

1. Various gestures (tap, swipe) and device interactions
2. Capturing screenshots as images and video for further analysis
3. Support for iOS and Android
4. Platform, device and app settings can be set in TBC

CalculateBrightness

• Calculation of a brightness signal
• Mask support

FindImage

• Calculation of a logical signal ContainsImage
• Calculation of an object-value signal for API interaction with match objects
• Mask support

ReportFrameAtStartTrigger

• Add frames of a video at the start trigger of a parent trigger block to the report
• Optional input of a frame offset, e.g. to document the frame before the start trigger
• Optionally highlight the matches found by FindImage or a parameterized mask in the report

Numpy Trace step template ReduceVideo

• Acceleration of subsequent analysis steps
• Reduction of resolution
• Conversion to grayscale video
• Reduction of the frame rate (downsampling)

New API method FindImageByFeatures

• Use feature detection to find partial images in the frames of a video
• Independent of size, rotation, color or perspective

Create masks and reference images easily from videos

1. Make any internal data (e.g. frames) from the ECU available for test case and analysis
2. Example use case: Logging of the hardware load during the test

1. ECU-TEST records in the same *.dlt file format
2. Single DLT message

• AUTOSAR standardized interface for logging and tracing of ECUs
• Support of verbose mode (non-verbose with Fibex already since ECU-TEST 2020.1)
• Solution incorporating the GENIVI DLT Viewer

1. Specification in the test configuration gives access via object-value signals
2. Reuse of the filter files from the DLT viewer
3. API access to various attributes, such as applicationId or arguments

1. Identical data object in the Trace Analysis
2. Offline analysis of DLT and PCAP recordings

1. Storage of scenarios and attributes in the TEST-GUIDE artifact management
2. Filtering and downloading the scenarios in ECU-TEST
3. Direct simulation in VTD and CarMaker

1. Migration help for the switch to the new tool category "Environment Simulation”

Motivation

• Scenario database + test automation workflow in ECU-TEST
• Enables methodical development of specific features for environment simulation

Supported Tools

• VTD
• CarMaker

1. Generic stimulation, parameters
2. Analyses to check requirements or calculate KPIs
3. Independent reports for each run of an analysis package including return values

• Simulation and test environment for Functional Mock-up Units (FMU) without further proprietary tool dependency
• Read, write, record and analyze FMU parameters and signals

Diagnostics add-on

UDS-Service $2F "Input/Output Control by Identifier“

• Services "Return control to ECU", "Reset to default", "Freeze current state" and "Short term adjustment“ can be used as special DIDs
• Access via job InputOutputControlByIdentifier as well

Further Highlights

• CANdela Diagnostic Data (*.cdd) can be used as diagnostic description
• Support for ODX ECU variants

New and updated tools, standards and formats

New tools

• Appium
• FMI

New formats

• DLT
• FLAC
• MTS
• WAV

New standards

• CANdela Diagnostic Data (CDD) 6.5 bis 9.1
• FMI 1.0 und 2.0
• Probe Logging Protocol (PLP) for Ethernet
• AUTOSAR DLT verbose Mode

Updated tools

• dSPACE Release 2020-A
• ETAS INCA 7.3.1
• ETAS LABCAR 5.4.10
• FEP 2.7.1
• IPG CarMaker 9
• Lauterbach TRACE32 R.2019.09
• Softing DTS 9
• Vector CANape 18SP2
• Vector CANoe 13
• VW ODIS 11

Updated standards

• ASAM XIL STI/STZ 2.1 und 2.2

Features:

• Support of STI files in versions 2.1 and 2.2
• Segments can easily be converted into a value table
• Freely placeable cursor

Usability

• STI and STZ files can be opened directly from the editor
• Height and width of individual signal panels configurable
• All signals can be clearly displayed on a common time axis

1. Freely placeable cursor to read concrete data points from the signal
2. Performance improvements

• External Python editor also for UserPyModules
• Easier signal assignment in plot
• Configurable signal identifiers in the trace step signal export
• Performance optimization of the trace analysis, especially with many trigger ranges and large number of time stamps of the used signals

1. Move analogous to blocks: Strg + Shift + ↑
2. Assign multiple analysis packages to another stimulation via drag-and-drop

Enables:

• Search for suitable implementation depending on context (DUT, test environment) using attributes
• Fast navigation between Packages
• Better handling of specification changes (Diff)