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 message 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.
 

VIDEO TUTORIALS

Tips & Tricks Directly from Our CANoe Diagnostics Expert

You get a detailed introduction into working with diagnostics in CANoe and CANalyzer. It presents the basic technical aspects and possibilities with the Diagnostic Feature Set, complements the help file of CANoe and may be used as a tutorial.

>> Open "CANoe and CANalyzer as Diagnostic Tools"

Overview of CANoe features regarding DoIP as of CANoe 14 SP2. Step by step it explains how to use CANoe as DoIP tester, gateway and simulated ECU. Additionally, instructions are given how to configure CANoe for different use cases. 
Scope of this document is neither to explain the DoIP protocol, nor to explain the diagnostics features of CANoe.

>> Open "Diagnostics over Internet Protocol (DoIP) in CANoe"

Learn about the concept of a diagnostics gateway between CAN and any other bus system or transport protocol to make CANoe's diagnostics features available when direct access ist not yet possible.

>> Open "Diagnostics via CANoe Gateways"

You can test and analyze a System Under Tests (SUT) with a CANoe simulation. By transferring real components to a simulation under laboratory conditions, the SUT is operated under defined, controlled and, above all, reproducible situations. This makes it possible to analyze limit and exceptional situations without risk. All development phases are supported with this residual bus simulation. 

The SUT can be hardware as well as software.

During stimulation, events are applied to a System Under Test (SUT) to produce a desired response. These stimuli can be of the character of a planned control or of a scheduled system disturbance for further investigation. The goals of a stimulus are:

• Controlled, reproducible excitation of your SUT
• Various test scenarios for your analyses
• Determine optimal control parameters

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

The free extension "Connectivity Feature Set" for CANoe allows you to easily connect your System Under Test (SUT) via a back end (CANoe Connectivity Hub) or directly via an interface hardware (VH4110 "IoT Enabler"). Your SUT can be a real device or pure software, e.g. in a virtual environment.

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 is required when using the Connectivity Hub, as the connection is made via websockets or HTTPS
• A wide range of protocols is supported when using the VH4110 hardware - also called "IoT Enabler"
   

The Connectivity Feature Set provides access with a low barrier to entry  and easy operation:

• 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.
• CANoe provides all the necessary artifacts of a complete system environment for your System Under Test (SUT).

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 also CANalyzer, CANape, vFlash, Indigo and CANoe.DiVa use the Security Manager.

This free CANoe extension allows you to easily test ADAS functions. Such functions can be, for example, brake assistants, traffic sign recognition or lane keeping assistants. The basic concepts of CANoe are of course available. 

For stimulating ADAS algorithms, various ADAS objects are exchanged between simulation environments, sensors or development environments. Specific windows are available for analysis. The use of Test Units enables complete testing of the algorithm. CANoe provides the necessary remaining system. Depending on the application, data from simulated environments can also be used here, such as those provided by DYNA4.

Highlights:

• Stimulation of ADAS algorithms with simple or complex scenarios
• Test of ADAS algorithms
• Analysis of sensor data via network communication
• Stimulation of ADAS algorithms via network communication
• Analysis of logging files
• Analysis of scenarios

The mapping of object lists is done internally via the ASAM OSI® standard (Open Simulation Interface). This standard is also supported by other Vector tools, ensuring interoperability between different tools.

"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

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.

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 modify signals
• Model Generator to generate a complete CANoe environment

Available extensions resp. "OEM packages":

The professional variant is intended for users who want to take advantage of the full range of CANoe functions. Simulation models can be created with CAPL and .NET. Test cases are easy to model with the Test Feature Set.

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

The runtime variant is suitable for users who want to quickly and easily test their ECU in interaction with a specified remaining bus simulation. Configurations cannot be changed, analysis functions are fully available and network nodes can be easily connected and disconnected.

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

The project execution variant provides a graphical user interface exclusively. Simulation, test cases and results are easily controlled without the need to specifically evaluate the underlying messages.

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