Vector CANoe

Parent Previous Next

Table of Contents

1        Introduction        1

1.1        Prerequisites        1

2        iSystem.Connect in Test Environment        2

2.1        CANoe setup        2

3        iSystem.Connect and vTESTstudio        11

3.1        CANoe setup        18

3.2        vTESTstudio setup        11


1Introduction

The iSystem.connect interface allows driving iSYSTEM blue boxes from almost any external application being used in the development labs. These external applications are typically test environments controlling the target microcontroller and acquiring specific data (memory content, register values, trace, profiler, code coverage) from the target microcontroller.

This document describes how to remotely drive iSystem blue box from Vector CANoe Test Automation Module. As an alternative, the vTESTstudio integration is described as well.

.NET for C# test automation scenario is described.

1.1Prerequisites

Vector CANoe

Vector vTESTstudio (optionally for test units)

iSystem winIDEA

isystem.connect SDK for C# (http://isystem.com/download/winidea-testidea-apis)


2iSystem.Connect in Test Environment

2.1CANoe setup

1.Run “Test Environments for Test Modules”  under View/Test setup/


2.Right-click on “Test Setup” and select “New Test Environment”


3.Rename the test environment and save it to disk

4.Right – click the test environment and select “Insert .NET test module”


5.Under “Common” tab rename the .NET Test Module and select the test script file (extension .cs for C#).


6.Under “Components” tab register the iSystem .NET library (IConnectCSLib.dll).  This library is valid for C# .NET scripts and could be downloaded from iSystem home page under :     http://isystem.com/download/winidea-testidea-apis


Note: iConnectCSLib.dll and native isystemConnect.dll must be copied to CANoe executables folder location (%CANoe_home%\Exec32) or to Windows system folder.


7.Edit and prepare .cs script. Refer to a downloadable Canoe configuration package iSystem.Connect.Canoe.TestModulesExample.zip. Advanced CS sample (file name testModules\AdvancedExample.cs), could be a good starting point for the script implementation.

8.Run the simulation and test


Test results are visible in “Write Window”



3iSystem.Connect and vTESTstudio

In vTESTstudio, you can implement tests with the help of CAPL and C# files as well as in tabular and graphic forms. In so doing, the different test languages can be easily combined. The executable entity programmed in vTESTstudio is called a test unit. It comprises all files required for the test. A test unit created in vTESTstudio has the file extension *.VTUEXE. This can be configured and executed in CANoe.

3.1vTESTstudio setup

1.Create a new vTESTstudio project



2.Create a new test unit



3.Add a C# file to the test unit


4.Copy the .NET assembly iConnectCSLib.dll either to the vTESTstudio test unit folder next to the C# file or to one of its libraries.


5.Add the .NET assembly iConnectCSLib.dll to the test unit.



Now the the functionality of the iConnectCSLib.dll is available within the C# file.


6.Define test cases, test functions or functions within the C# file accessing the API of the iConnectCSLib.dll. Use the attribute [Export] to be able to call these functions in other test design languages as well, e.g. in the Test Table Editor.



7.Use the C# methods to define your test sequence - either in C# editor or in the Test Table Editor or in the Test Diagram Editor.



8.Build the executable test unit *.VTUEXE.



Note: Vector CANoe with vTESTstudio integration sample is provided in the compressed archive iSystem.Connect.Canoe.Example.Testunit.zip



3.2CANoe setup

1.Run “Test Configurations for Test Units”  under View/Test setup/


Test  Configurations for Test Units Window opens:


2.Add new test configuration


3.Add test unit (previously created in vTESTstudio)


Note: The .NET assembly iConnectCSLib.dll must be copied to the vTESTstudio test unit folder. The native library isystemConnect.dll must be copied to the CANoe executables folder location (%CANoe_home%\Exec32) or to Windows system folder.



4.Start the simulation and run the test