Testing ECUs and Networks with CANoe

CANoe users can analyse the multi-bus communication of ECUs and entire systems at their desk as well as in the vehicle. Theses smart windows support your analysis:

1. Trace Window (1) for listing all bus activities such as messages or error frames. For each massages there is the possibility of displaying the individual signal values.
2. Graphics Window (2) for graphical online display for values transmitted in messages and diagnostic requests, such as rpm or temperature values, over a time axis.
3. Statistics Window (3) for displaying useful network and node statistics, e.g. bus load on node and frame levels, burst counter/duration, counter/rate for frames and errors, controller states.
4. Data Window (4) for displaying preselected data, e.g. numeric or bar graph data.
5. State Tracker (5) for displaying states and bit signals.

... further analysis windows and blocks are:

• Measurement Setup for graphical display and parameterization of function blocks and evaluation functions
• Scope Window for offline display of bit level measurements recorded with the Option .Scope
• Interactive Generator for stimulating the buses and for easy sending of modified signals
• Signal Generator for generating signal waveforms (sine, ramp, pulse, value list, etc.)
• Logging/Replay for logging and later analysis or replay of measurements
• Trigger and Filter for specific reactions to bus events and to reduce the amount of data that is displayed or logged
• Write Window for system messages and user-specific outputs from CAPL programs

The Diagnostic Feature Set included with CANoe supports you in analyzing diagnostic communication via the KWP2000 and UDS standards. CANoe may be used both as a diagnostic tester and to simulate ECU diagnostics; it is parameterized via ODX or CANdelaStudio description files. In addition a complete OBD-II Tester is integrated in CANoe.

With CANoe.DiVa you can perform automated testing of diagnostic software implementations in ECUs. Reproducible test cases are generated based on an ECU diagnostic description in CANdela or ODX format. CANoe automatically executes these test cases and generates a conclusive test report.

With CANoe, you can also implement the diagnostic simulation of ECUs. In addition, the included Test Feature Set allows you to perform automated tests programmed in CAPL, XML,. NET, or with the help of vTESTstudio. CANoe can also automatically generate a test report in XML and HTML format on request.
 

Tips & tricks directly from our CANoe diagnostics expert

A simulation can be generated manually or automatically from the underlying communication data base. This remaining bus simulation of communication behavior of complete networks or individual ECUs is the basis for the subsequent analysis and testing phases.

Via specific OEM Packages the CANoe simulation can be adjusted to the requirements of the respective OEM. Such an OEM-specific remaining bus simulation is the basis for the function development. The developer may implement different test scenarios along the development process.

• SIL (Software-in-the-Loop) – Execution of ECU code with vVITRUALtarget
• MIL (Model-in-the-Loop) – Integration of MATLAB/Simulink models
• HIL (Hardware-in-the-Loop) – Execute the simulation in real time with real hardware like VT System

CANoe RT Rack is an industrial PC with optimized real-time operating system

CANoe offers in combination with the hardware CANoe RT Rack options for executing real-time relevant simulation and test functions on a dedicated platform, i.e. separate from the graphic user interface. CANoe RT Rack is an industrial PC with a real-time operating system that is optimized for CANoe RT operation. This simply involves increasing total system performance as necessary, and it is possible to implement shorter latency times and more precise timers.

More Information:

• Fact Sheet CANoe RT Rack (PDF)

In stimulation with CANoe, you intentionally send out individual messages or signals to elicit reactions from ECUs in the network in a simple and quick way. The ECUs‘ responses give an indication abour their correct functionality. CANoe offers many different ways to stimulate ECUs in the network. The bandwidth ranges from pre-defined user interfaces to different programming options:

• CAPL or .NET programs for setting signal and variable values.
• Visual Sequencer to create command sequences easily
• Signal Generator and Signal Replay for generating signal responses (sinusoidal, ramp, pulse, value list, etc.)
• Interactive Generator or Frame Panel for stimulating the buses and conveniently sending modified signals
• Panels for users to create customized graphic user interfaces.

CANoe represents the state-of-the-art test environment. It is the ideal testing tool as well for the entire system as for efficient ECU testing. CANoe supports you with impressive performance on:

• ECU tests
• Module tests
• Integration tests
• Conformance tests
• Regression tests
• Testing of ECU prototypes

For your convenience the Test Feature Set (TFS) is integrated in CANoe. It performs both application-specific tests and standardized conformance tests.

On increased real-time requirements, you may also operate CANoe as a HIL (Hardware-in-the-Loop) system.

In the CANoe RT (Real Time) mode, real-time relevant simulation and test functions are executed on a dedicated computer, i.e. separate from the graphic user interface. This offers you an easy way to increase the overall system performance if necessary. Additionally it results in shorter latency times and more precise timers.

Application examples

CANoe’s many open interfaces make it easy to adapt it in your testing environment:

• Integrating hardware for stimulation, measurement and injecting errors:
  VT System, digital and analog I/Os, automated measuring devices, controllable power supplies
• Interfacing simulation and test models: MATLAB/Simulink models
• Controlling test systems from third parties: via program calls, script calls
• Integration in higher-level test controllers: via the CANoe COM server, e.g. from Python or .NET
• Linking to external software tools: e.g. to DOORS for traceability requirements

This free extension for CANoe allows you to easily connect your System Under Test (SUT) via a back-end or local broker. Your SUT can be a real device or pure software, e.g. in a virtual environment. Initially MQTT is supported as protocol, but more protocols are planned.

Highlights:

• For functional tests of your software or your smart device.
• Use the familiar CANoe features, such as analysis windows, automated testing or integration of additional models to provide the system environment
• No special IT policy necessary, since the connection is established via web sockets or HTTPS

Benefit from a low entry barrier and simple operation:

• You start immediately after receiving and configuring the certificates required for authentication.
• Protocol-specific aspects are handled implicitly by CANoe. You can concentrate fully on your application data.
• If you are already working with CANoe, you will remain within your usual workflows for simulation and testing.

The system to be tested is a room temperature control:

• Multiple temperature sensors provide measured values
• The “business logic” is running in the back-end
• The back-end software calculates the ventilator speed based on the provided temperature values
• The speed is transmitted to the ventilator
• The ventilator device software adds some own logic, e.g. emergency stop
• The communication between the ventilator, the sensor and the back-end is based on MQTT

"Service-orientation in E/E designs" (26 min.). Part 1/2 about SOA fundamentals and CANoe´s support for SOA testing of vehicle networks.

The classic signal-based communication is increasingly supplemented by service-oriented communication patterns. The AUTOSAR Adaptive platform, for example consistently uses service-oriented approach. Service-oriented communication is often based on the TCP/IP protocol stack and uses communication middleware, for example SOME/IP. The transmitted network message, i.e. the Ethernet frame, and the actual application view drift here much more apart than in case of signal based communication via CAN. In addition, the service interfaces and the associated data structures are defined in a way which is detached from a specific network transmission or network topology.

Communication model of CANoe

CANoe supports this new design paradigm. To do so, databases are imported into the CANoe communication model. Via a built-in communication object editor you can define your own communication objects and edit the existing ones.

Communication Setup Window

In the CANoe communication concept the Communication Setup Window is the central starting point for communication configuration of the:

1.  Application layer (application models)
2.  Communication layer (communication, bindings)
3.  Transmission medium (hardware, bindings)

Workflow of CANoe .AMD/XCP

The CANoe option .AMD/XCP (AUTOSAR Monitoring and Debugging) supports access to internal parameters in the ECU. It gives you extensive test options and shortens your debug times substantially.

Especially with complex ECUs or distributed functions, a pure blackbox test is no longer adequate. Access to internal information in ECUs opens up new and comprehensive test options for your application or ECU stack. AUTOSAR ECUs, in particular, offer defined interfaces for measuring and stimulating test parameters due to their structured layout consisting of basic software (BSW), a runtime environment (RTE) and software components (SWCs).

Highlights:

• Easy access to internal ECU parameters over XCP/CCP
• Extensive measurement of the MICROSAR stack (supports all monitoring features, including generic measurement)
• Update of A2L files with new addresses from the linker-map files (via the included ASAP2 Updater)

Application Areas:

• Extended test options through access to ECU internal values
• Analyzing and automated testing of ECU internal values, bus signals and I/O signals
• Analysis of distributed functions with parallel access to several ECUs
• Debugging in BSW and SWCs
• Automatic configuration via ASAM A2L file

Further information:

• Webinar recording "Testing and debugging of ECUs using MICROSAR.AMD and CANoe .AMD" (47 min.)
• CANoe option .AMD/XCP
• Web page AUTOSAR technologies

Performance diagram with and without using the Vector Tool Platform

The “Vector Tool Platform” is a free system extension, which is available for CANoe as well as other products. The “Extended Real Time” (ERT) component is part of the Vector Tool Platform and has been supported since CANoe 9.0.

Extended Real Time improves the latency and determinism (see figure) of CANoe in connection with the VT System. You will benefit by:

• predefined functions can be executed under real-time conditions
• higher sampling rates, i.e. additional transfer rates of 200 µs and 500 µs are achievable in connection with the VT system modules VT1004, VT7001, and VT2816

The “Vector Tool Platform” is a free system extension, which is available for CANoe as well as other products.

The Vector Tool Platform is a free system extension for PC-based Vector network interfaces.  It consists of the following  components:

1. Platform Manager
   This programm simplifies system configuration of the PC-based network interfaces VN8800, VN8900 and VT6000 as well as CANoe RT (Real Time) racks. It allows to configure system settings, install device updates and controll installed applications.
2. Extended Real Time
   It improves the latency and determinism of CANoe and CANape. In order to achieve this, the PC-based network interfaces VN8912A and VT6051A are divided logically into two areas. The interface works just as before in one area. “Extended Real Time” is available in a different area in which the predefined functions are executed under real-time conditions.
3. Smart Device Access
   This component allows the user to select and control diagnostic scripts with a smartphone or a tablet on the VN8810 diagnostic hardware.

CANoe supports simulation of complex ECU models with various modeling tools, here for example MATLAB

CANoe has interfaces to these modeling tools, which can be used to integrate complex models of individual ECUs into a simulation:

• MATLAB®
• Simulink®
• Stateflow®

The interface provides a blockset for reading/writing system variables and bus signals. It provides 2 operation modes:

1. Online/HIL for executing generated code in the CANoe real time environment
2. Offline/Synchronized for simulated systems

CANoe provides the interaction layer and a signal API which can directly be used in the MATLAB/Simulink model. All communication aspects are handled inside CANoe.

The principle of the Security Manager - with and without access to OEM-specific backends

Security mechanisms in the ECU secure the vehicle and its functions against manipulation and unauthorized access. However, for testing and diagnostic purposes, it must be possible for an authorized individual to participate in vehicle communication during development and later operation.

With the Security Manager, Vector offers a uniform solution that is used identically for many Vector tools. In addition to CANoe, CANalyzer, CANape, Indigo and CANoe.DiVa also use the Security Manager.

Vector offers free of charge OEM specific function extensions for CANoe. These simulation extensions are composed of several components. The components are typically based on a standard and are extended with OEM specific add-ons.
 

Content:

• Interaction Layer
• Transport Protocol
• Network Management
• Panels to display and modificate signals
• Model Generator to generate a complete CANoe environment

Available extensions resp. "OEM packages":

The "professional" variant supports the full range of functional features. Simulation models are created with CAPL, test cases are easy to model with the Test Feature Set. This variant is intended for advanced users who want to use CANoe’s full functionality.

Detailed information on the scope of functions in the "CANoe/CANalyzer Feature Matrix" (PDF).

The "runtime" variant supports unchangeable configurations, full analysis functions and simple connection and disconnection of network nodes. This variant is intended for users who wish to test their ECU quickly and easily in interaction with a prescribed remaining bus simulation.

Detailed information on the scope of functions in the "CANoe/CANalyzer Feature Matrix" (PDF).

The "project execution" variant supports an exclusively graphic user interface. Simulation, test cases and results are easy to control without requiring special evaluation of the underlying messages.

Detailed information on the scope of functions in the "CANoe/CANalyzer Feature Matrix" (PDF).