CANoe - Guide Me!
Play the Easy Ball

Tips for Using CANoe in 3 Typical Applications

CANoe offers an extremely high number of features. It´s not easy to get an overview of this. Here you will receive simple yet effective tips on:

  • Typical pitfalls & how to avoid them
  • What your optimal CANoe tool environment might look like

Let´s start: What is your task?

  1. Developing ECUs
  2. Automated ECU testing
  3. System validation

1. Developing ECUs

When developing an ECU, you often need the signals of other ECUs in the network.  CANoe provides this in the form of the remaining bus simulation.  Real and simulated data alike can be analyzed with the Trace and Graphics window and stored using CANoe’s logging function.  You may stimulate the network or specifically manipulate the remaining bus simulation.

 

Avoid these pitfalls:

A remaining bus simulation in the form of handwritten code is error-prone and very maintenance-intensive.

Changes in the communication matrix lead to inconsistencies of the remaining bus simulation.

What your Vector solution looks like:

Use the appropriate OEM specific Interaction Layer to configure CANoe to automatically send the simulated messages according to their timing definitions in the database.

 

2. Automated ECU Testing

You develop ECUs and want to test their functions using automated testing. In doing so, you bring your system to its limits. You stimulate ECU functions, selectively inject errors, and monitor the ECU reactions on your network.

 

Avoid these pitfalls:

The tests are not reproducible or not reproducible at all if they are performed interactively and manually.

The non-automated test execution ties up scarce resources or important staff.

Manually generated test protocols may be incomplete or difficult to process.

What your Vector solution looks like:

Create your tests with vTESTstudio. With this tool, you can either select predefined test primitives or develop your own.  CANoe hereby performs as a tool for automatic test execution and generates an extensive test protocol. The tests can be reproduced at any time and test reports can be further processed automated.

3. System Validation

You want to assure the complete system functionality. It is necessary here to provide the corresponding system environment for your System Under Test (SUT) and to incorporate analog and digital inputs and outputs in the test.

 

Avoid these pitfalls:

Missing time synchronization between network events and stimulation or measurement of the inputs and outputs.

The specific signal conditioning of the inputs and outputs of the SUT is not only time-consuming but can also be error-prone.

What your Vector solution looks like:

Make use of the openness of CANoe and integrate it into a group of various run-time environments into a co-simulation. The VT System ensures that events for the stimulation of inputs and outputs of the SUT as well as network  events are synchronized. The VT System modules are specifically developed for the ECU test – a special signal conditioning is therefore not necessary.
 

Play the Easy Ball !