Multi CANoe - Vector · Multi CANoe instances. 3.2 Vector Network HW The Vector network interfaces are configured on each Multi CANoe computer independently of each other. However,

Multi CANoe Version 1.1

2019-08-28

Application Note AN-IND-1-024

Author Vector Informatik GmbH

Restrictions Public Document

Abstract Introduction to the Multi CANoe concepts, getting started and troubleshooting

Table of Contents

1 Overview ........................................................................................................................................ 2 1.1 Introduction .......................................................................................................................... 2

2 Technical Background .................................................................................................................. 2 2.1 Time Synchronization .......................................................................................................... 2 2.2 Data Exchange..................................................................................................................... 2 2.3 Measurement Start .............................................................................................................. 3

3 Configuration ................................................................................................................................. 3 3.1 IP Configuration ................................................................................................................... 3 3.2 Vector Network HW ............................................................................................................. 4 3.3 Version and Licensing .......................................................................................................... 6

4 Best Practice .................................................................................................................................. 6 4.1 Operation ............................................................................................................................. 6 4.2 Information exchange .......................................................................................................... 7 4.3 Conflict Free Channel Mapping ........................................................................................... 8 4.4 Offline Analysis ..................................................................................................................11

5 Troubleshooting ..........................................................................................................................12 5.1 Measurement does not start ..............................................................................................12 5.2 Invalid Multi CANoe Configuration .....................................................................................12

6 Contacts .......................................................................................................................................12

Multi CANoe

Copyright © 2019 - Vector Informatik GmbH 2 Contact Information: www.vector.com or +49-711-80 670-0

1 Overview

This application note covers the technical concepts behind the Multi CANoe operation mode. It gives

usage recommendations and contains tips for troubleshooting.

1.1 Introduction

Multi CANoe is a special operation mode of CANoe. It allows coupling multiple instances of CANoe

running on different computers. In Multi CANoe operation, the measurement starts synchronously in

all connected instances. Network interfaces of all instances of CANoe are time synchronized via

Vector HW sync. Each CANoe has its own user interface and real-time part.

Figure 1: Schematic view of a Multi CANoe system

This setup allows scaling the performance of CANoe to meet the requirements of very large systems

under test. For example, an integration breadboard containing all ECUs of all networks of an upper-

class vehicle is such a large SUT and the perfect use case for Multi CANoe.

2 Technical Background

2.1 Time Synchronization

Almost all Vector VN interfaces can be time synchronized via a party line. One interface

sends out a pulse on this line which is detected by all connected interfaces at almost the

same time. However, the more interfaces are connected, the longer it takes to send out the

pulse and the quality of the pulse’s edge gets weaker. To compensate this, use a Multi

SYNCbox active which amplifies an incoming sync pulse by driving 10 active outputs. While

there is almost no time offset between the 10 outputs, there is an offset to the incoming

pulse. This delay is constant and can be compensated. It should be measured and entered in

the can.ini of that instance of CANoe that is configured to send out the pulse.

2.2 Data Exchange

In principle, configurations running on Multi CANoe instances are completely independent

from each other. However, for time synchronization the time of the reference channel of the

master CANoe producing the sync pulse is distributed to the other instances of CANoe. Also,

System Variables can be exchanged between the CANoe instances. For this purpose, a

hidden FDX connection (Ethernet) is automatically established when CANoe is configured to

run in Multi CANoe mode.

Multi CANoe


2.3 Measurement Start

To start CANoe on all computers at the exact same time, the following mechanism is used:

When the measurement is started on any of the Multi CANoe instances, a start request is

sent to the master. The master sends a start command to all CANoe instances. Every

instance starts its current configuration and report this status back to the master. In this

phase, all drivers are running but no event is processed by CANoe yet. When the master

detects that all CANoe instances have reached this state, it sends a sync pulse via the HW

sync. This pulse is the time stamp 0 for all instances. At this moment, all CANoe instances

begin processing the driver events.

3 Configuration

3.1 IP Configuration

Multi CANoe uses the Windows IP stack for data exchange. Make sure that all computers

are in the same IPv4 subnet:

Figure 2: IPv4 settings of a Windows network adapter

After configuring the Windows network adapters properly, you can use the IP addresses in

the Multi CANoe configuration dialog. If you enter IP addresses that are not available from

the current Windows IP configuration, the icons will have a red x meaning the CANoe

instances are not reachable.

Multi CANoe


Figure 3: Multi CANoe settings in CANoe Options dialog

Important notes: The list of Multi CANoe instances needs to be identical on all machine.

Therefore, there is an Import and Export functionality. Configure the Multi CANoe setup on

one computer and put the configuration file on a shared folder. Import the file in all instances.

Every CANoe needs to know all other instances. Dynamic IP addresses are not supported.

Only enter the IP addresses of computers in the list that will run a CANoe, i.e. don’t enter the

IP address of a gateway computer that is used to remote desktop on the computers running

CANoe. The alias name is used for the (optional) system variable exchange between the

Multi CANoe instances.

3.2 Vector Network HW

The Vector network interfaces are configured on each Multi CANoe computer independently

of each other. However, for the physical connection of the HW sync it is important to decide

which interface of the Multi CANoe master computer will send out the pulse. This device

needs to be connected to the input of the Multi SYNCbox active (VN7570 in the graphic

below):

Multi CANoe


Figure 4: Synchronization of VN interfaces using a Multi SYNCbox active

In the hardware configuration dialog of CANoe, you can verify which application channel is

used for the “Sync source” (i.e. an application channel on a VN interface sending out the

pulse):

Figure 5: Hardware synchronization settings of CANoe

In this example, CANoe application channel “CAN 1” is used for the Synch source. Using the

Vector Hardware Configuration dialog in the Windows Control Panel, you can find out, on

which interface this channel is mapped (here: VN1640 with serial number 001240):

Multi CANoe


Figure 6: Channel assignment in Vector Hardware Configuration

3.3 Version and Licensing

For Multi CANoe operation, the CANoe versions installed on all computers must be the

same. In particular, main version, SP version and hotfix version must be identical.

Multi CANoe requires one CANoe pro or run license and one pro / run license for every

option that is required for the SUT. For every additional computer you need a CANoe slave

license which basically mirrors those licenses.

Example:

A SUT has CAN, LIN and Ethernet networks. Three computers are necessary to handle all

channels. This would require the following licenses:

License License Alternative

1x CANoe pro

1x CANoe run

1x CANoe pro Option .LIN 1x CANoe run Option .LIN

1x CANoe pro Option .Ethernet 1x CANoe run Option .Ethernet

2x CANoe Slave 2x CANoe Slave

4 Best Practice

4.1 Operation

Every Multi CANoe instance has the full CANoe GUI which must be operated for example to

analyze the communication on the channels connected to this instance. Technically you

could use a separate keyboard, monitor, and mouse on every computer. Usually the

simultaneous operation of all CANoe instances is not necessary, though. From practical

experience, a KVM switch has proven to be a good solution. Another option is a very large

Multi CANoe


monitor and simultaneous remote desktop connections to all Multi CANoe computers. This

allows a seamless operation of all CANoe instances.

4.2 Information exchange

The big advantage of the Multi CANoe solution is that it scales without any limitations. All

computation is done on the individual computer, there’s no central coordinator that must

handle the data of all instances. If more computation power or more channels are required,

just add another computer.

However, for some use cases it is important to share information between the CANoe

simulations. For example, the simulated ignition status may need to be changed on several

networks at the same time, but some networks may be handled by different computers. Or a

test may be distributed on multiple instance of CANoe and they need to coordinate which test

step they should execute next.

For this purpose, system variables can be configured to be exchanged between the Multi

CANoe instances. You can configure the “Multi CANoe Write access” for any user-defined

system variable:

Figure 7: Multi CANoe settings for a system variable

Save such a system variable definition into a file and reference this file from all Multi CANoe

instances. Every instance of CANoe, which does not have the write access, will see the

value as soon as the instance with the write access changes the variable. Always take in

mind that this may impact the overall performance significantly. For example, do not try

mapping lots of bus signals to such system variables as this may cause more load as if the

CANoe instances would have direct access to this bus.

Multi CANoe


Due to the underlying communication techniques, there is a delay between when the

instance with the write access sets a new value and when the other instances see the

update. In fact, you can see it in the Trace Window comparing the time stamp of the system

variable update on the different PCs (usually below 1ms). If you need to trigger a

simultaneous action on several instances of CANoe, you can schedule this event ahead.

Since the simulation time is the same on all instances, use a system variable to transmit a

time in the future of when you want to trigger an action. Use a second system variable or a

system variable struct to pass the desired action to the other CANoe instances. In CAPL, set

up a timer with the difference of the desired time in the future and the current simulation time

retrieved by the CAPL function timeNowNS(). By doing so, you can eliminate the

transmission delay of the system variable values.

The distributed system variables work as any other system variable. I.e. you can use them in

the Graphics Window or even on a panel to show information coming from different CANoe

instances.

4.3 Conflict Free Channel Mapping

At the time of writing, a single CANoe instance is limited to 32 channels of each bus system

except for LIN and A429, which are limited to 64 channels. If the overall system does not

exceed these limits, it is worth setting up the channel numbers conflict free on all computers.

This simplifies the combined offline analysis of log files created by the Multi CANoe instances

(see 4.4).

Example:

A Multi CANoe setup consisting of 2 computers handling 4 CAN channels with 2 CAN

channels handled by each computer.

Setup on Computer #1

Figure 8: Channel mapping on computer #1

Multi CANoe


Figure 9: CANoe Simulation Setup on computer #1

Setup on Computer #2

Figure 10: Channel mapping on computer #2

Multi CANoe


Figure 11: CANoe Simulation Setup on computer #2

Add the channels 1 and 2 just like on computer #1 but deactivate them in the Simulation

Setup. Now add the channels that you want to use on computer #2 and use the conflict free

application channel number. The result is that computer #1 write log files with CAN channel

number 1 and 2, computer #2 will write log files with CAN channel number 3 and 4. For

offline analysis you can merge these files together without any pre-processing or conflicts.

Note: If the driver does not show all required channels, increase the number of available

channels for the application:

Figure 12: Application channel settings for CANoe

Multi CANoe


4.4 Offline Analysis

Multi CANoe allows real-time simulation and logging of all channels of large systems under

test by distributing the load between multiple computers. For some use case, an offline

evaluation of the combined traffic of all channels is required. Since all Multi CANoe instances

are time synchronized, the time stamps in all log files of the same measurement can be

merged together. There is no need to compensate an offset or a drift between the time

stamps of the log files. If you use CANoe or CANalyzer, you can use the Offline Mode to

perform an offline analysis. Configure the log files from the required Multi CANoe PCs:

Figure 13: Configuration window for Offline Mode of CANoe

If the channels are conflict free (see 4.3), you can directly start the analysis. If this is not the

case, you must define a channel mapping for the desired analysis. For example, if both log

files contain a CAN channel 1 and 2, you can create a mapping for the log file of computer #2

and map channel 1 to 3 and 2 to 4:

Figure 14: Channel mapping definition

Multi CANoe


Afterwards, assign this channel mapping to the second log file:

Figure 15: Offline Mode configuration with channel mapping

Now you can start the analysis with a conflict free channel mapping. Please note that the

maximum number of channels in CANoe and CANalyzer is restricted (see 4.3). Therefore,

you may have to reconfigure the Offline Mode to analyze those channels together that you

need to focus on.

5 Troubleshooting

5.1 Measurement does not start

Usually there are two reasons why Multi CANoe does not start the measurement: IP

configuration / firewall settings in Windows or wiring of the HW sync. If you get an error that a

CANoe on a certain IP address does not answer, switch your monitor to this CANoe and

check if there is a window or message box shown. If so, resolve the problem. If there’s no

problem, check if you can ping this IP address from the command line. If this does not work,

correct the Windows IP settings. In all other cases, carefully check the channel mapping in

the Vector Hardware Configuration and check the wiring of the sync cables.

If you can’t find the problem, start with a reduced setup: Use only two computers for Multi

CANoe and use a CANoe configuration with just one CAN channel on both computers. Be

careful that CANoe starts by default with a configuration with one channel of each bus

system that you have a license for. Create a new configuration using the CAN template with

1 CAN channel. Connect the CAN channels of the two computers using a terminated cable

and start the measurement. Try sending a CAN frame from one instance to the other using

the IG block. If this works (check the Write Window for warnings and errors), expand your

setup to more computers and channels. If it does not work, it is very likely the problem is

either the wiring of the sync cable or the application channel is mapped to a different VN

interface as expected. Use the Vector Hardware Configuration and do compare the serial

number of the interface.

5.2 Invalid Multi CANoe Configuration

If you set up IP addresses that are not available with the current Windows IP configuration,

you will get a warning when starting CANoe. Resolve the issues but either correcting the

Windows IP settings or the Multi CANoe settings (see 3.1).

6 Contacts

For a full list with all Vector locations and addresses worldwide, please visit http://vector.com/contact/.

http://vector.com/contact/

Documents

Multi CANoe - Vector · Multi CANoe instances. 3.2 Vector Network HW The Vector network interfaces are configured on each Multi CANoe computer independently of each other. However,