ecu.test Release 2023.4

ecu.test 2023.4 presents the new package mapping! Package call meets mapping concept. All calls from packages to packages are now realized via mappings.

All basic workflows are still the same as before: 

• Drag 'n drop from the workspace explorer inserts a familiar test step
• The target is changed by over-mapping the entry with another package - as already used
• The adaptation of package usages is realized via global mapping - as already used

What is new?

• When inserting a test step, it no longer has an address line, but a mapping reference. The file path of the package is now part of the (automatically created) mapping. This also applies to library packages.
• When opening existing packages, all existing references are updated and suitable local mappings are created
• Package references are hereby discontinued - see the Note

The ASAM standard Open Diagnostic Data eXchange (ODX) is the basic format for describing vehicle and ECU diagnostics.

With ecu.test 2023.4, ODX-based diagnostics havs been completely reworked. This results in a large number of improvements:

• Support of almost all diagnostic services described in ODX in form of a generic test step with improved reporting
• Support of variants and inheritance
• Better identification of correct connection settings
• Better overview of the services in the Diagnostics tab

ecu.test calibration is our new extra for measurement and calibration access. With this add-on, application access to ECUs can be automated without additional software.

The functional scope currently includes the basic reading and writing of calibration and measurement quantities as well as the recording and downstream analysis of these quantities as part of the trace analysis. Access is currently possible via Ethernet using a TCP/IP network connection and can be used in conjunction with the following tool connections:

• tracetronic: Ethernet
• Vector: XL API

ecu.test calibration is continuously being developed. We intend to provide some functions in later versions:

• In general
  • Page Switching
  • Security Access
• Transport Layer
  • XCP on CAN
  • Transport Layer Commands (Slave Detection, Clock Multicast)
• Measurement access (DAQ)
  • ODT optimization
  • Special features for XETK are not taken into account yet
  • Configuration Storing/Resume Mode
• Recording
  • Non-linear conversion functions
  • Sparse write operations
  • Timestamp from slave

The functional scope can be purchased as an extension for ecu.test. If you are interested in ecu.test calibration or have questions about extensions, please contact sales@tracetronic.de.

This new concept can be used directly in the entire workspace.

Note: Package references with reference to global constants are not transferred to the mapping. Support for global constants in package references is hereby discontinued. The test cases are all still executable. However, we recommend switching to a solution using mappings as soon as possible.

The interaction between test cases and scenarios is one of the biggest challenges in scenario-based testing.

With ecu.test 2023.4, we offer for the first time an integrated workflow to create, adapt and execute both scenarios and test cases in your test environment.
The graphic on the right illustrates the interaction between our scenario.architect and ecu.test:

You can now create new scenarios and adapt existing ones in ecu.test.

The scenario tree in the environment simulation tab offers new context menu entries for this purpose.
When creating or changing a scenario, scenario.architect opens. In this tool, the user can make adjustments or create completely new scenarios. After completion, ecu.test manages the artifact handling and ensures that the necessary scenarios are sent directly to the environment simulation. The corresponding scenarios are loaded, parameterized and executed via the test cases. 

The advantage is in the coupling of the tools. As a result of the integration, scenarios, test cases and analyses can be developed and executed very quickly, intuitively and iteratively. 

You can find more details in the new tutorial in the user documentation.

Note: The workflow is developed for the use of OpenSCENARIO files. The functions are currently available for the VTD and CARLA environment simulations. Please contact us if you are interested in supporting other simulation tools.

When testing in the SiL area, it is often necessary for all communication participants to synchronize to an alternative time axis, the so-called model time. With the possibilities of time control, ecu.test in conjunction with some tools (e.g. XiL-API) has already supported test case synchronization in this mode for some time. 

Until now, the limitation was that the network and diagnostic stack built into ecu.test could not take model time into account. Timing tests and trace analyses or timing-sensitive protocol implementations did not work as expected in this environment because they were based on the system time of the test host.

In the current version of ecu.test, all built-in communication and diagnostic stacks (e.g. Bus-RBS, UDS, SOME/IP, ...) have been enabled to handle an alternative model time. In this version, this function is enabled for the Vector SiL-Kit tool. In the future, it is planned to activate this feature for other tools (bus hardware connections, Ethernet).

We will be celebrating our 20th birthday next year.

We are taking this anniversary as an opportunity to refresh our corporate design.

TraceTronic changes to tracetronic and in addition to minor adjustments to the company logo and the spelling, product logos and icons will also change in order to create a uniform overall appearance.

ECU-TEST changes to ecu.test, TRACE-CHECK to trace.check and TEST-GUIDE to test.guide.

The most important thing for you: Apart from visual aspects, nothing changes. 
Your workspaces and automations remain unaffected.