CANoe Matlab en

CANoe
AddOn
MATLAB

Interface

User Guide

Version 1.7

Vector Informatik GmbH, Ingersheimer Str. 24, D-70499 Stuttgart
Tel. +49 711 80670-0, Fax +49 711 80670 555,
Email can@vector-informatik.de, Internet http://www.vector-informatik.de
i
Subsidiaries
France
Vector France SAS
168, Boulevard Camlinat
F-92240 Malakoff
Tel.: +33 (1) 4231 4000
Fax: +33 (1) 4231 4009
information@vector-france.com
http://www.vector-france.com
Japan
Vector Japan Co., Ltd.
Seafort Square Center Bld. 18F
2-3-12, Higashi-shinagawa, Shinagawa-ku
J-140-0002 Tokyo
Tel.: +81 3 5769 6970
Fax: +81 3 5769 6975
info@vector-japan.co.jp
http://www.vector-japan.co.jp
Sweden
VecScan AB
Lindholmspiren 5
SE-417 56 Gteborg
Tel.: +46 (31) 76476 00
Fax: +46 (31) 76476 19
info@vecscan.com
http://www.vecscan.com/
USA
Vector CANtech, Inc.
Suite 550
39500 Orchard Hill Place
USA-Novi, Mi 48375
Tel.: +1 (248) 449 9290
Fax: +1 (248) 449 9704
info@vector-cantech.com
http://www.vector-cantech.com

For Distributor Addresses please have a look on our website:
www.vector-informatik.com
Vector Informatik GmbH CANoe AddOn MATLAB Interface User Guide Version 1.7
ii
International Quality Standard Certificate
The Quality/Process Management of Vector Informatik GmbH is being certified
according to DIN EN ISO 9001:2000-12 (formerly DIN EN ISO 9001:1994-08)
throughout since 1998-08-19.
Typographic Conventions
Note:

Identifies important notes
Identifies enumerations (bullet items)
'1.0 Introduction' Identifies references to further chapters of this manual
[OK] Notation for buttons in dialogs
<TAB> Notation for keys on the computer keyboard
<Ctrl>+<Z> Notation for keys of the computer keyboard which should be
pressed simultaneously
Add
FileFile open
Notation for menu, command and dialog names
on message 0x100 Notation for MS-DOS syntax or program code

iii
Contents
1 Introduction..........................................................................................................1
2 Execution Modes .................................................................................................2
2.1 Offline Mode..................................................................................................2
2.2 Hardware-In-The-Loop (HIL) Mode...............................................................3
3 Modeling Concepts..............................................................................................4
3.1 Software Layers of an ECU...........................................................................4
3.2 Interaction Layer ...........................................................................................5
3.3 CANoe Interaction Layer ...............................................................................5
3.4 Application.....................................................................................................6
3.5 Definition of Concepts ...................................................................................6
3.5.1 Middleware .......................................................................................6
3.5.2 Interaction Layer...............................................................................6
3.5.3 Transport Layer ................................................................................6
3.5.4 Network Management Layer.............................................................7
4 Setup.....................................................................................................................8
4.1 General .........................................................................................................8
4.2 Matlab ...........................................................................................................8
4.3 Verification.....................................................................................................8
4.4 CANoe...........................................................................................................9
4.5 CANoe Interaction Layer .............................................................................10
4.5.1 Database preparation .....................................................................10
4.5.2 Configuration Setup from scratch ................................................... 11
4.6 Customize a Matlab Simulink
Model for Interaction with CANoe...............12

4.6.1 Simulink
Settings ..........................................................................12
Model for Parameterization from

CANoe...................................................................................................14
4.7.1 Simulink
Settings ..........................................................................14
4.7.2 CANoe Settings..............................................................................16
4.8 Configuration and Test of CANoe Simulink
Blocks ....................................20
4.8.1 Signal Block Configuration..............................................................20
4.8.2 Test of CANoe Blocks.....................................................................22
iv
5 Sample Configurations .....................................................................................24
5.1 Sine Sample Configuration..........................................................................24
5.1.1 Offline Mode ...................................................................................24
5.1.2 Hardware-In-The-Loop (HIL) Mode ................................................24
5.2 Sine Parameterization Configuration...........................................................25
5.3 Signal Access Sample Configuration ..........................................................25
5.4 SF_Auto_SignalAccess Sample Configuration ...........................................26
5.5 Automot Sample Configuration ...................................................................28
5.6 Trigger Sample Configuration......................................................................29
5.6.1 Triggering by Environment Input.....................................................29
5.6.2 Triggering by Environment Event....................................................29
5.6.3 Using Different Targets ...................................................................30
6 CANoe I/O Library..............................................................................................31
6.1 Signal Input .................................................................................................32
6.2 Signal Output ..............................................................................................32
6.3 Signal Block ................................................................................................32
6.4 Message Input.............................................................................................34
6.5 Message Output ..........................................................................................34
6.6 Simulation Step ...........................................................................................35
6.7 CAPL Call....................................................................................................35
6.8 CAPL Handler .............................................................................................36
6.8.1 Environment Event .........................................................................37
6.9 Environment Input .......................................................................................37
6.10 Data Environment Input...............................................................................38
6.11 Environment Output ....................................................................................38
6.12 Data Environment Output ............................................................................38
6.13 Environment Step........................................................................................38
6.14 Environment Trigger ....................................................................................39
6.15 System Variable Input .................................................................................40
6.16 System Variable Output...............................................................................41
7 CAPL Functions.................................................................................................42
7.1 General .......................................................................................................42
7.2 MODEL_init .................................................................................................42
v
7.3 MODEL_step...............................................................................................43
7.4 Parameterization Functions.........................................................................43
7.4.1 MODEL_getParameter ...................................................................44
7.4.2 MODEL_setParameter ...................................................................44
7.4.3 MODEL_setScalarParameter .........................................................44
8 Utilities................................................................................................................45
8.1 Setup of environment blocks.......................................................................45
8.2 Setup of signal and environment blocks......................................................46
9 Troubleshooting.................................................................................................48
9.1 Unusable CANoe GUI during offline simulation...........................................48
9.2 Unable to compile the nlapml.cpp source file. .............................................48
9.3 Spaces in MATLAB
installation path ..........................................................48

9.4 Model Advisor Checks not available............................................................49
10 Index ...................................................................................................................50

1
1 Introduction
This document describes the CANoe/MATLAB
interface. The CANoe/MATLAB

interface was designed to combine the strengths of both simulation tools.
CANoe is a total network simulation tool designed to both model nodes on a network
and the network that binds them. Traditionally the functionality of these network
nodes are modeled using the CAPL language provided with CANoe. The purpose of
this interface is to extend CANoes node modeling capability by adding the strength
of the MATLAB
/ Simulink
environment.
Now models can be used to describe the functionality of a network node in CANoe.
This allows CANoe to simulate nodes which are impossible or difficult to model using
CAPL alone. Another feature would be to use a Simulink

model to generate an
outside stimulus to an existing CAPL node.
2
2 Execution Modes
Simulations utilizing this interface can be operated in two different modes:
Running a simulation in MATLAB
/ Simulink
.
This is an offline simulation mode.

Running a simulation in the CANoe execution environment.
This is a real-time or Hardware-In-The-Loop (HIL) simulation mode.

2.1 Offline Mode
In this mode the simulation is run in the MATLAB

Simulink

environment. CANoe is
operated in Slave mode whereas MATLAB
Simulink
is the simulation Master. This

is the mode for non-real-time simulation. The simulation is controlled from the
MATLAB
Simulink
environment.
CANoe's Slave mode is a special simulation mode whereby CANoe is simulating the
(CAN) bus and takes its measurement time base from outside (here: from Simulink
).
This is especially useful in early design stages. Debugging features of the MATLAB

environment can be used. Communication between MATLAB
Simulink
and CANoe
takes place over Microsoft
DCOM.
You cannot perform real-time simulation with this kind of simulation.
3
2.2 Hardware-In-The-Loop (HIL) Mode
In this mode the simulation is run in the CANoe execution environment. With the
Simulink

Real-Time Workshop
you can target CANoe and produce a Windows

DLL which can be loaded in CANoe's simulation environment. One DLL must be
generated per node. With this approach it is possible to test and verify your design
with real (CAN) hardware in a networked environment. The simulation can be used
as a simulation of the remainder of the bus in a real-time environment. Several ECUs
can be simulated simultaneously within a single CANoe environment. This mode
must be used if it is necessary to simulate the remaining bus in real time.
Requirements: Simulink

Real-Time Workshop
.
4
3 Modeling Concepts
It is important to understand how this interface communicates with CANoe in order to
easily design a model.
It is easiest to think of the CANoe/MATLAB

interface an extension or a complete
replacement of existing CAPL code. The application of a CAPL node can be
completely implemented with Simulink

.
It is possible to design an entire ECU in Simulink
. Examples of this can be found in

Chapter 5 Sample configurations.
For definition of concepts see "Definition of Concepts" in chapter 3.5.
Please continue with chapter 4 if you are familiar with Software Layers of an ECU.
3.1 Software Layers of an ECU
CANoe's Simulation Setup lets you define the network nodes for a given (CAN)
network. The functional behavior of these nodes can be described in CAPL
(Communication Access Programming Language) which is a C style programming
language. CAPL was designed to facilitate the modeling of a network node's basic
logic (behavior). CAPL allows you to directly integrate the specification of the CAN
communication matrix into the programming syntax.
Application Behavior
CAPL lets you define the basic application behavior of an ECU with special emphasis
on its functional bus behavior.
Middleware
Apart from the application behavior of an ECU, there are parts of the software which
are identical for each network node, such as interaction layers (IL), network
management services (NM), diagnostic services and transport protocols (TP).
These layers are available as CANoe modeling libraries for all major OEMs.
NM and TP layers are available as CANoe DLLs; the IL is generated automatically as
CAPL code. The IL and the modeling of the application are described in more detail
in subsequent chapters.
5

Figure 1: Software Layers
3.2 Interaction Layer
An important part of the software located between an ECU's application layer and
lower-level functions is the Interaction Layer (IL) with its Signal Interface. It is
important because applications deal with named signals (bus signals) instead of their
networked representation in bits and bytes of the data stream. This Interaction Layer
performs mapping between the signals and their network representations.
3.3 CANoe Interaction Layer
The Vector CANoe Interaction Layer (in short CANoeIL) provides a signal-oriented
means of accessing the bus. The CANoeIL also performs mapping of signals to their
send messages and controls the sending of these send messages as a function of
the Send Model. Different Send Models are defined depending on the network type
(OEM), and a special CANoeIL is provided to each of these Send Models.
It is possible to map model outputs and inputs directly to signals. This mapping
causes the changed value of the model to be routed directly to the specific CANoeIL
responsible for sending the value out and also the models input is stimulated with the
changed value.
6
3.4 Application
The application of an ECU has two major interfaces:
The interface to bus signals
The interface to peripheral I/Os like sensor and actuators. In CANoe the
interface to I/Os is modeled using environment variables.
ECUs with simple application logic (e.g. some truth tables, simple conditional
behavior, simple calculations) are usually modeled directly in CAPL.
ECUs with complex application behavior may be modeled with tools like MATLAB

Simulink

and Stateflow
using the signal input and output blocks as interfaces

between the application and interaction layers. Environment variable input and output
blocks are used as interfaces to the sensors and actuators. An additional advantage
of this approach is that application models can be used to generate code for the real
target, too.
3.5 Definition of Concepts
The following definitions and explanations are intended to describe the functionality
of various components and their coordination with other modules/components.
3.5.1 Middleware
Software that functions as a conversion or translation layer. It is also a consolidator
and integrator. For decades custom-programmed middleware solutions have been
developed to enable one application to communicate with another application that
either runs on a different platform or comes from a different vendor or both. Today, a
diverse group of products exists offering packaged middleware solutions.
3.5.2 Interaction Layer
The Interaction Layer is a communication module responsible for separation of the
low-level driver (a CAN Driver for example) which is dependent on the Data Link
Layer and the application task which is independent of the underlying bus system.

Specifically the following items are handled by the Interaction Layer:
Signal-based interface
Sending of bus messages according to specified transmission types
Monitoring of receiving messages
Different notification types
The Interaction Layer is also responsible for transmitting and receiving all node-
specific messages. Messages are sent according to predefined transmission types
such as cyclic, event-triggered or a mixed mode specified in the network database.
3.5.3 Transport Layer
Some information to be transmitted over the CAN bus does not fit into a single data
frame because the data length exceeds 8 bytes. In such cases the sender has to split
up the data into several CAN messages with the same identifier. Additional
7
information is necessary to re-assemble the data in the receiver.
This is performed by the Transport Layer:
Segmentation and reassembly of data that are larger than the underlying Data
Link Layer
Flow control for single messages
Error recognition
A Transport Layer is not only needed for diagnosis purposes but also for any large
data which must be exchanged between different nodes, e.g. text information to be
displayed on a dashboard.
3.5.4 Network Management Layer
The availability of the CAN bus is handled by Network Management. Typical features
include:
Identifies the network configuration at start-up
Monitors the network configuration while the bus system is running
Synchronizes transition of all network nodes to bus sleep mode
(power saving mode if CAN network is not needed)
Controls peripheral hardware (CAN Controller and Bus Transceiver)
Provides network-relevant status information
Error recovery after bus-off
Each ECU is identified by a unique station number and has a special CAN message
identifier for exchanging network-relevant information. This message contains
identification of the transmitting node (encoded in the CAN identifier), the address of
the receiving node as well as the message type and additional sleep flags.
8
4 Setup
This chapter describes the installation/setup process.
4.1 General
The CANoe/MATLAB
Interface requires the following minimum product versions:

CANoe 3.0.43 (CANoe 5.1 SP3 for signal access)
MATLAB
R12
Visual C++
6.0

CANoe/MATLAB
Interface files (canoe\*.*) are located in the following directory:

$(MATLABROOT)\rtw\c
Note: After installation you should find the following path in your MATLAB
environment:
$(MATLABROOT)\rtw\c\canoe\devices
The sample files (CANoe configurations and Simulink

models) are located in the
following directory:
$(MY DOCUMENTS)\Matlab\CANoe\Samples
4.2 Matlab
MATLAB
needs to be associated with your C compiler in order to generate the dll

files for the HIL mode.
See your MATLAB
/RTW
documentation for a correct setup of the compiler

environment. The following compilers are currently supported:
Compiler Supported since Matlab Version
Microsoft Visual C++
6.0 R12
.NET (7.1) R14

2005 (8.0) R2006a

4.3 Verification
To verify proper installation open the Simulink

library browser. You should see an
additional library: Vector CANoe.
When you open a model (or create a new one) select "RTW Options" from the
Tools menu. Under "Code generation" select the "Browse" button to open the
"System Target File Browser". In this list you should see the following line:
cn.tlc Vector CANoe Real-Time Target DLL (Visual C++ Project Makefile)
9
4.4 CANoe
If you simulate your models from within Simulink

CANoe is switched to Slave mode.
In this mode CANoe takes its time base from an external source (here: Simulink
).
Note: This note applies to CANoe versions lower than CANoe 3.1.15.
These CANoe versions need the DEMO driver to switch to Slave mode.
You have to install CANoe with the Custom Setup option to install the
DEMO driver.
To set CANoe to the Slave mode do the following:
Exit CANoe if it is running.
Install the DEMO driver:
$(CANOEROOT)\Exec32\Batch\CANdem32.BAT.
Open the CAN.INI configuration file.
Under the [System] section edit the following entry (i.e. set it to 1):
ExternalDemoSimulationTime=1.
Append the following entry (this will increase the performance in Slave mode
operation):
SingleStepSimulationTime=1.
(Re)start CANoe and open the configuration with which you want to work.
Select the "Simulation" item from the "Configure" menu.
Set the Working mode to Simulated bus and select an Animation factor of
"1.0000".
Save your changes.
10
4.5 CANoe Interaction Layer
The CANoe Interaction Layer is used to access signals from Simulink
directly.
Several preliminary steps have to be taken before the CANoe Interaction Layer can
be utilized.
Note: The signal access blocks of the CANoe I/O library can only be used with
CANoe versions 5.1. SP3 or later.
4.5.1 Database preparation
The database must contain several attributes to use it with the Vector Interaction
Layer. You can import these attribute definitions from the Vector_IL_Basic template
dbc file.

Database attributes to use the Vector Interaction Layer:
Object type Database attribute Description
BusType Defines the bus type, here CAN Network
NmBaseAddress OSEK NM attribute
Node NmStationAddress OSEK NM attribute
NmMessage Identifies a NM message Message
GenMsgStartDelayTime Delay of cyclic sendings after the start of the Vector IL
GenMsgSendType Send type of the message
GenMsgNrOfRepetition Number of repetitions for send types OnWriteWithRepetition,
OnChangeWithRepetition and IfActiveWithRepetition
GenMsgILSupport Defines the support of the Vector IL for this message
GenMsgFastOnStart Fast cyclic sending on start of the Vector IL
GenMsgDelayTime Minimum delay time between two sendings of the message
GenMsgCycleTimeFast Cycle time used by send types IfActive and for messages
using attribute GenMsgFastOnStart
GenMsgCycleTime Cycle time for send type cyclic
NWM-WakeupAllowed Allows a signal to wake up the network Signal
GenSigStartValue Start value of the signal
GenSigSendType Send type of the signal
GenSigInactiveValue Inactive value of the signal used by the send types
IfActive

You can find more information about the Vector IL send types in the CANoe Online
Help (CAPL Generator Interaction Layer Vector Interaction Layer)

Network management:
11
The communication between the network management and the Vector Interaction
Layer doesnt need any CAPL code. If you dont want to use the OSEK NM please
remove the entry dmoseknm.dll within the database attribute NodeLayerModules.
All the greyed database attributes in the overview above can be removed from the
database if there is no need to use the OSEK NM.
4.5.2 Configuration Setup from scratch
Starting from a pre-configured dbc file you can automatically generate a CANoe
configuration. Please take the following steps:
1. Prepare a new directory that shall contain the simulation configuration. There,
create the folder candb and copy your network database into this folder.
The nodes will be generated to the folder <Database-folder>/../Nodes.
The panels will be generated to the folder <Database-folder>/../Panels.
2. The exec32\ModelGeneration folder of your CANoe installation contains a
Model Generation Wizard. A link can also be found in the CANoe start menu in
the Tools folder. Start the wizard and select your network database. The output
folder for the new configuration is set automatically. Choose [Generate] to
create the configuration.

Figure 2: Model Generation Wizard
3. CANoe is started automatically. The Simulation creation runs about up to 2
minutes, depending on your hardware configuration and the complexity of the
model. You can track the status of the generation within the write window of
CANoe.
Note: Please do not operate CANoe before the message
Vector Simulation creation finished. has occurred there.
12
Additional information for the automatic generation
The original database will be saved as *.bak file before the creation of the
simulation model.
The run of the automatic simulation creation requires the confirmation of the
disclaimer of CANoe.
Trouble-shooting of the automatic generation
If the automatic simulation creation fails, then please check the following topics:
Start CANoe manually. Is it possible to start CANoe without the confirmation of
dialogs, maybe error-dialogs?
In this case please start CANoe manually, load a demo-configuration, and
close CANoe.
Is CANoe currently running? If yes, is the currently active configuration already
saved?
If the currently running configuration is not yet saved, then save it.
Do you have multiple installations of CANoe onto your system?
The generation must use the CANoe you have installed at last.
Model for Interaction with CANoe

This chapter describes the steps which are necessary to run a Matlab model together
with a CANoe configuration. It is recommendable to start CANoe and open the
desired configuration at first. If a new configuration should be created consider using
the Model Generation Wizard ( '4.5.2 Configuration Setup from scratch'). The
reason is that CAN signals or environment variables can be selected easily in the
Simulink model if a CANdb is present.
It may be helpful to copy the Simulink model file (*.mdl) into the same folder as the
CANoe configuration (*.cfg). If you want to use the generated DLL, create a subfolder
named Exec32 for example. The Real-Time Workshop
can be configured to copy

the DLL into this folder.
4.6.1 Simulink
Settings
The CANoe interface for Matlab needs some settings of the Simulink model which
are described here. Choose Simulation | Configuration Parameters to open the
settings dialog.

Real-Time Workshop Settings
The Real-Time Workshop must be configured with the correct target for CANoe
(cn.tlc). Otherwise the CANoe Matlab interface blocks cant be used.
13

Figure 3: Target Selection
Interface
If you want to parameterize the model from CANoe activate the C-API Interface for
parameters. Please note that this setting is available with Matlab R14 and newer:

Figure 4: C-API Interface Settings
CN code generation options
The CN target has some specific options for the code generation process. First of all
the output directory can be set. If nothing is specified the DLL will be generated in the
..\MODEL_cn_rtw\release\ folder relative to the folder containing the Simulink

model. You can specify a subfolder of your configuration like Exec32 for example to
generate the DLL here.
Export CAPL-Function: With this option activated two special CAPL functions
are exported by the generated DLL. Refer to '7.0 CAPL-Functions' for more
details.
Enable Parameterization from CANoe: If this option is activated, values of
model parameters will be accessible from CANoe. This option requires Export
CAPL Functions and activation of the C-API for parameters.
Enable Simulink Signal Analysis: Enables analysis of all named Simulink

signals. With CANoe 7.0 or newer system variables are created for each signal
below the namespace MODEL::Signals. This option requires the activation of
the C-API for signals.
14
Generate Visual C++ project file: The build process first builds a makefile. If
this option is selected Visual Studio is opened. The compilation process now
must be finished within Visual Studio. This is useful to generate a DLL with
debug info. If this option is not selected, the DLL is built directly by a command
line call. This applies only to Visual Studio 6.0.
Perform Simulation Step at t(0) : If the model does not contain blocks with
states (e.g. the model contains only algebraic blocks) this option can be
selected to get a value for the simulation step at t=0.
Use full signal qualification for compilation: CANoe signal blocks can use
unique signal names. This option ensures compatibility of the compiled model to
older versions of CANoe by using full signal name qualification (see 4.8.1).
Check CANoe block configuration at compilation: Uses the Model Advisor
to check settings of all CANoe blocks (see 4.8.2).

Figure 5: CN Code Generation Settings
Note: Only non-complex scalar or vector parameters are supported by the
parameterization and signal analysis feature. Both make use of the C-API
interface which is available since Matlab R14. Therefore these features
are only available with R14 and newer.
Model for Parameterization from CANoe

In this chapter all steps are described which are necessary for parameterization of a
compiled model from CANoe. It is assumed that the model uses the CANoe target
(cn.tlc).
4.7.1 Simulink
Settings
The CANoe interface for Matlab needs some settings of the Simulink model which
are described here. Choose Simulation | Configuration Parameters to open the
settings dialog.
15
Optimization
The Inline Parameters option on the Optimization page defines which model
parameters are accessible. If the option is deactivated, all parameters of every
Simulink

block will be accessible. The number of parameters and their names might
differ from the ones configurable in Simulink
. In most cases it wont be necessary to

access all model parameters. Use workspace variables and assign them to block
parameters. Activate the Inline parameters option and choose the Configure
button. Add all workspace variables which should be configurable after compilation.
This is the recommended setting for optimal speed of the compiled model.

Figure 6: Model Parameter Configuration
Real-Time Workshop Settings

Select the C-API interface for data exchange on the Interface page:

Figure 7: C-API Interface Settings
Enable the options Export CAPL Functions and Enable Parameterization from
CANoe on the CN code generation page:
16

Figure 8: CN Code Generation Settings for Parameterization
Build the model with the new settings. The output folder will contain the model DLL
and the parameterization files (named model_M.csv and model_V.csv).
Note: Only non-complex scalar or vector parameters are supported by the
parameterization and signal analysis feature. Both make use of the C-API
interface which is available since Matlab R14. Therefore these features
are only available with R14 and newer.
4.7.2 CANoe Settings
CANoe 7.0 and newer
Since CANoe 7.0 the model can be parameterized easily using system variables. The
model DLL creates a system variable for each parameter as soon as it is added to
the CANoe configuration. If you choose Configuration | System Variables you
will get an overview of all variables.
17

Figure 9: CANoe system variables dialog
The model can be parameterized by setting the values of these system variables. In
the following sample CAPL code the amplitude of a sine block in the Sine
Parameterization configuration will be changed:
@sysvar::sine::Parameters::Sine_Wave::Amplitude = 3;
In addition there is a .NET panel included to the Matlab Interface located in
$(MATLABROOT)\rtw\bin\canoe\parameterization\Parameterization.
dll. It allows modifications of all system variables belonging to a model DLL. You
can add the panel to your CANoe configuration using the dialog Panel Configuration
from the Configuration menu.

18
The panel searches for system variables used for model parameterization if it is
opened in CANoe or if the [Refresh] button is pressed. It is possible to update the
currently loaded parameters with values of a value file (*_V.csv) by pressing
[Open]. The button [Save] allows writing parameter values back to into a value
file. If you press [Parameterize] all system variable values are written and the model
uses the new values if possible.
Note: Some parameters might not be configurable during measurement. This
depends on the implementation of a Simulink block. Therefore it is

recommended to change the system variables in the On PreStart section
of a CAPL program or to restart the measurement after using the
[Parameterize] button of the parameterization panel in order to make sure
that all parameters are taken over completely.
You can also customize any other .NET project to read a value file and create the
system variables. The parameterization panel uses the assembly
ParamAccess.dll (also located in $(MATLABROOT)\rtw\bin\canoe\
parameterization) which must be included as reference. It contains the following
classes:
Class name Description
CANoeOperations Get name space names of all models which are currently
loaded in CANoe:
static string[] GetModelNames()
Get and set parameters from CANoe:
static void GetParametersFromCANoe(string
namespaceName, ModelParameters params,
ParamChangeNotification changeNotification)
static void ParameterizeCANoe(ModelParameters
params)
FileOperations Reads and writes the parameterization files:
static void ReadParameters(string
valueFilePath, ModelParameters params)
staic void WriteValueFile(string
Please note that the model parameters must be loaded via
GetParametersFromCANoe at first.
ModelParameters Contains all parameter values of a model. Note that the
property LastError returns a string if any of the methods
above failed. The property is null if the method succeeded.
ParamData Contains the name and values of a single parameter.
ParamChangeNoti
fication
Delegate for a function called whenever a parameter changes
its value:
void ParamChangeNotification(ParamData
19
changedParam)
CANoe 6.0 and 6.1
Up to CANoe 6.1 CAPL functions must be used for parameterization of the model.
There is an include file named Params.cin in the
$(MATLABROOT)\rtw\bin\canoe\parameterization_6x folder. It contains a
CAPL function named ParameterizeModel which uses the values of system
variables for parameterization. It is recommended to use this function in the PreStart
section of a CAPL program. Note that you must implement a Callback function
named SetModelParameter which calls the CAPL function MODEL_setParameter
which is exported by the model DLL ( '7.0 CAPL-Functions'). Please see also the
sample configuration Sine Parameterization for an example CAPL program using
the include file.
The system variables are created by the parameterization panel located in
$(MATLABROOT)\rtw\bin\canoe\parameterization_6x\Parameterizati
on.dll. You can add the panel to your CANoe configuration using the dialog Panel
Configuration from the Configuration menu.

Figure 10: Parameterization Panel
Choose the value file (model_V.csv) which is created during compilation of the
model. It contains all parameter values and the path of the map file. The map file
contains the parameter name to index mapping. The contents of both files is merged
and presented in the panel. You can also edit the parameter values. Choose the
[Save] button to write the new values back to the value file. The [Parameterize]
button will create the following system variables:
20
Namespace: MODEL_NAME
Variables:
Name Type Contents
NumberOfParameters Integer Number of model parameters
ParameterDimensions Array of Integer Number of values of each parameter
ParameterIndexes Array of Integer Internal index of each parameter. This
index is used by the CAPL functions.
Parameters Array of Float Values of all parameters. Note that
ParameterDimensions must be used to
determine the correct position of the
values belonging to a parameter.

You can also customize any other .NET project to read a value file and create the
system variables. The parameterization panel uses the assembly
ParamAccess.dll (also located in $(MATLABROOT)\rtw\bin\canoe\
parameterization_6x) which must be included as reference. It contains the
following classes:
Class name Description
CANoeOperations Parameterizes CANoe:
static void ParameterizeCANoe(ModelParameters
params)
FileOperations Reads and writes the parameterization files:
static void ReadParameters(string
staic void WriteValueFile(string
ModelParameters Contains all parameter values of a model. Note that the
property LastError returns a string if any of the methods
above failed. The property is null if the method succeeded.
ParamData Contains the name, index and values of a single parameter.
4.8 Configuration and Test of CANoe Simulink
Blocks
Note: This chapter only applies to Matlab R14 and newer. CANoe 7.0 SP3 and
newer must be used.
4.8.1 Signal Block Configuration
CANoe signals can normally be identified by four parameters:
1. Database name
2. Node name (the node which sends the message)
21
3. Message name (the message containing the signal)
4. Signal name
By double clicking CANoe signal blocks a selection dialog appears containing all
signals of the current CANoe configuration. The dialog also sets the parameters of
the signal block so that it uses the currently selected signal.
Since version 1.7 of the Matlab Interface the parameters 1. to 3. are optional. If the
signal name is unique, database, node and message name are set to a space
character ( ). If two messages contain signals with the same name, an additional
message name will be set to resolve the ambiguity. This also applies to the node and
database name. The use of unique signal names simplifies the development of
models in early development stages where database and node name might change
frequently.

Figure 11: Full signal qualification Figure 12: Unique signal name
Note: The use of unique signal names is not compatible with older versions of
CANoe and of the CANoe Matlab Interface. Therefore the following

functions are provided to change the signal block settings to full signal
qualification and back.
VSignalQualification.m
This m-function allows switching signal blocks or a whole model to full signal
qualification. Please make sure that CANoe has opened a configuration containing all
databases used by the model. You can manually call the function from the Matlab

prompt:
VSignalQualification(model_name, 1); %full qualification
VSignalQualification(model_name, 0); %use unique names
22

Code Generation
Signal names must be fully qualified if the complied model should work with versions
of CANoe older than 7.0 SP3. This can easily be achieved by using the m-function
described above or by checking the CN code generation option Use full signal
qualification for compilation:

Figure 13: Signal Qualification Option
The VSignalQualification function is called twice during the compilation process if the
option is enabled. It automatically switches to full signal qualification before the code
is generated and sets back the unique names at the end.
4.8.2 Test of CANoe Blocks

Interface provides custom checks for the Simulink The CANoe Matlab Model
Advisor. Please make sure that CANoe has opened a configuration containing all
databases used by the model before running these checks. The Model Advisor will
report all CANoe blocks which are not configured correctly.
By following the links of erroneous blocks in the Model Advisor report, Simulink

opens the correct sub system and highlights the block. Using the Model Advisor it is
very easy to find all CANoe blocks that wont work properly with the current CANoe
configuration.
The Model Advisor checks can be run automatically during compilation if the CN
code generation option Check CANoe block configuration at compilation is enabled.
Note: With Matlab
R14 this option just opens the Model Advisor and doesnt
interrupt the compilation process if errors are detected. Using R2006a and
newer the compilation process is stopped if the Model Advisor detects any
erroneous CANoe block and opens the report. If all blocks are configured
correctly the compilation is resumed.
23

Figure 14: Model Advisor Report
24
5 Sample Configurations
The actual chapter describes some sample configurations as examples for different
purposes.
5.1 Sine Sample Configuration
This simple configuration shows the minimum settings for a CANoe configuration and
database necessary to load and execute a Simulink

model.
5.1.1 Offline Mode
Notice the Environment Out, and Simulation Step blocks. The Environment Out block
specifies that the sines output will be associated with EnvFloat environment variable.
The Simulation Step block is required when running in slave mode. It is used to
control CANoes timing from Simulink
. This block may be left in models intended for

HIL mode but has no function; RTW will not generate any code for it.
Open the CANoe configuration
$(MATLABROOT)\work\samples\Sine\matlab.cfg
Start the measurement by clicking on the Start Simulation button in the sine
Simulink

model
A sine wave should display in the graphics window. Notice that it runs for 100
seconds before stopping on its own. This stop time is defined in the Simulink

model
under simulation parameters | solver | stop time. In HIL mode, since control is in
CANoe, this time is ignored and any model is run indefinitely. Offline mode does not
run in real time and this configuration should run much faster since it is so basic.
5.1.2 Hardware-In-The-Loop (HIL) Mode
Now convert this into a real time simulation. The sine.mdl will be compiled in RTW
into a DLL that CANoe can run.

model Open the Simulink
$(MATLABROOT)\work\samples\Sine\sine.mdl
in MATLAB
, specify the Output Directory and build the DLL.

To execute the DLL within CANoe you must add it to the configuration. Since CANoe
5.1 you can add the DLL to a network node:
Right click a network node in simulation setup and select Configuration.
Open the Modules tab and choose Add.
Select the DLL and choose OK.
Alternatively you can add the DLL via CANdb.
To do so, open the database of your configuration within the CANdb Editor.
The DLL will be attached to a node in the Simulation Setup.
Select the list of nodes in the CANdb Editor.
Here you can attach the DLL to an existing node or create a new one if desired.
Select the node in the list and choose Edit Node in its context menu.
25
Select the Attributes tab.
A dialog appears which lists all attributes defined for the selected node. Verify
that there is a NodeLayerModules entry in the list. If there is no entry you must
first define this kind of attribute in your database. This requires closing all
opened dialogs and selecting Attribute Definitions from the View main menu.
Select Edit | New and define the following:
Name: NodeLayerModules
Object Type: Node
Value type: String
Leave the "Default" editing box empty.
Close the dialog.
Now you can edit this (node) attribute as described above.
Select the NodeLayerModules attribute in the attribute list of the desired node
and edit its value.
Type the name of the generated DLL.
If the name of your Simulink model is "mymodel.mdl" you would type
"mymodel.dll".
Close all dialogs and save your database changes.
5.2 Sine Parameterization Configuration
Note: This sample configuration will only work with CANoe 6.0 SP2, Matlab R14
and newer.
This configuration shows how Simulink models can be parameterized after

compilation with the Real-Time Workshop
. It is similar to the Sine configuration. The

difference is that you can manipulate the parameters of the Sine Wave block in the
Hardware-In-The-Loop (HIL) Mode. To do so, the following options must be set in
Simulink Simulation Parameters | Real-Time Workshop.
Choose the Interface page and select C-API for data exchange interface.
Activate the Parameters in C API option.
Choose the CN code generation options page and activate the options
Export CAPL Functions and Enable Parameterization from CANoe.
The DLL will provide system variables and CAPL functions for accessing the
parameters of the model ( '7 CAPL Functions'). See the configuration comment of
the sample for usage of these functions. Use the configuration sine.cfg for CANoe
7.0 and newer or sine_6x.cfg for CANoe 6.0 and 6.1.
5.3 Signal Access Sample Configuration
Note: This sample configuration will only work with CANoe 5.1 SP3 and newer.
This sample configuration shows how to use the signal input and output blocks for
directly accessing signals. The CANdb of this configuration simply contains two
messages with signals for stimulating the model and receiving results.
26
You will find this model in:
$(MATLABROOT)\work\samples\signalaccess.mdl
Open the CANoe configuration
$(MATLABROOT)\work\samples\signalaccess.cfg
Start the measurement by clicking on the Start Simulation button in the
signalaccess Simulink
model

A sine wave should be displayed in the graphics window. Enter a value for signal
SigModelInput into the simulink panel in CANoe. This value is used as a multiplier
for the amplitude of sine wave 2 in the model. The output of sine wave 2 is mapped
to the signal SigResult and should now also be displayed in the graphics window.
5.4 SF_Auto_SignalAccess Sample Configuration
Note: This sample configuration will only work with CANoe 5.1 SP3 and newer.
For earlier CANoe versions there is an alternative model available
(SF_Car) which interfaces to CANoe via environment variables.
This sample only applies to MATLAB
version 6.0 R.12 or later

This CANoe configuration derived from the Automot demo configuration that is
supplied with CANoe. In addition to the original configuration the generated code of
the Simulink
demo model SF_Car.mdl has been added to the Simulation Setup.

The original Automot demo models the behavior of a car engine with CAPL. This part
was replaced by the Automatic Transmission Control demo that comes with
Simulink
.
You will find this model in:
$(MATLABROOT)\work\samples\
SF_Auto_SignalAccess\Models\sf_car.mdl
It contains seven CANoe specific signal input/output blocks:
BreakForce
EngineRunning
PedalPosition
EngSpeed
Gear
CarSpeed

The Simulation step block is only relevant to the Simulink Simulation. It will be
discussed later
When you build the model a folder (sf_car_cn_rtw) containing several files generated
during the code building process is made in the current MATLAB
working directory.
To specify a destination for the DLL file generated you must first specify the
27
compiler's output directory. Select the RTW Options item from the Tools menu
and click the [Options] button. In the editing box labeled Output Directory specify
your directory:
$(CANOEROOT)\Exec32
Note: If the $(CANOEROOT) directory path contains spaces
C:\Program files\CANoe (e.g.: ) you must specify the MS-DOS name
C:\Progra~1\CANoe (usually: ).
Use the Explorer to find the MS-DOS name.
If nothing is specified the DLL will be generated in the
..\sf_car_cn_rtw\release\ directory and must be copied manually to
$(CANOEROOT)\Exec32.
Note: This note applies to MATLAB R12.
To specify the Output Directory open the Category combo box and select
the CN code generation options.
Additional settings in the Simulation Parameters dialog:
1. Export CAPL-Function: With this option activated two special CAPL functions
are exported by the generated DLL. Refer to '7.0 CAPL-Functions' for more
details.
2. Enable Parameterization from CANoe: If this option is activated values of all
model parameters are accessible from CANoe. Refer to '5.2 Sine
Parameterization Configuration' for an example.
3. Enable Simulink Signal Analysis: Enables analysis of all named Simulink

signals. With CANoe 7.0 or newer system variables are created for each
signal below the namespace MODEL::Signals. This option requires the
activation of the C-API for signals.
4. Generate Visual C++ project file: The build process first builds a makefile. If
this option is selected Visual Studio is opened. The compilation process now
must be finished within Visual Studio. This is useful to generate a DLL with
debug info. If this option is not selected, the DLL is built directly by a command
line call.
5. Perform Simulation Step at t(0) : If the model does not contain blocks with
states (e.g. the model contains only algebraic blocks) this option can be
selected to get a value for the simulation step at t=0.
After all settings are done
Close all dialogs and save your changes.
Select RTW Build from the Tools menu.
$(CANOEROOT)\Exec32 The DLL will be linked into your directory.
Start CANoe and open the configuration:
$(MATLABROOT)\work\samples\Auto\automot4.cfg
28
Select Compile all nodes from the Configure menu.
(Configure | Compile all nodes)
To verify that CANoe has detected the DLL select View | Simulation Setup to
have the Simulation Setup window pop up.
The Engine node should display a RTW string in its second description line
although this depends on the order the nodelayer modules are defined in the
CANdb.
Start the measurement to view the models in action
There is a replay block that controls the measurement. 20 seconds after
measurement start, the pedal position moves to 100%. Now you can see the
models behavior.
You can also stimulate the model manually: Deactivate the replay block in the
Simulation Setup.
Select the Gateway panel, set the Ignition switch to 3 (right mouse click) and
press the Starter panel.
Select the Control panel and press the Powertrain Bus button to open the
Engine panel.
Play with the accelerator position and watch how the gear is shifting up and
down
Play with the break force

5.5 Automot Sample Configuration
This CANoe configuration is derived from the Automot demo configuration that is
supplied with CANoe. In addition to the original configuration the generated code of
two Simulink
models have been added to the Simulation Setup. Before you open
this configuration you should first build the actual DLLs for these models. If you open
it beforehand you will get two warning messages indicating that CANoe cannot find
them you can safely ignore these messages at this time but you will not be able to
start the measurement.
The first model engine.mdl implements a simple vehicle speed control system.
Vehicle and engine speed are the input variables and the speed is controlled as a
function of the pedal position and gear. You will find this model in:
$(MATLABROOT)\work\samples\Auto\Models\engine\engine.mdl
Open the model in MATLAB
. The model contains 5 CANoe specific blocks:

Simulation step
Actual speed
Engine speed
Pedal position
Gear
The first block Simulation step is only relevant to the Simulink Simulation. It will
be discussed later. The others are two Environment Input and Output blocks
respectively. They read and write directly to the corresponding CANoe environment
29
variables. Double click on the Environment blocks to see the actual controlled
variable names.
The second model door_ri.mdl lowers the window of the right door automatically
to the lowest position when the user presses the window down button longer than a
specified time. You will find the model in:
$(MATLABROOT)\work\samples\Auto\Models\door_ri\door_ri.mdl
Generate code for the models as described in the SF_Car_SignalAccess example
above. For your convenience you will find all prebuilt DLLs in:
$(MATLABROOT)\work\samples\Auto\DLL
After you have generated code
Start CANoe and open the configuration:
$(MATLABROOT)\work\samples\Auto\automot.cfg
Note: If youre using CANoe 4.0 or newer open the configuration:
$(MATLABROOT)\work\samples\Auto\automot4.cfg
Select Compile all nodes from the Configure menu.
(Configure | Compile all nodes)
To verify that CANoe has detected the two DLLs select View | Simulation
Setup to have the Simulation Setup window pop up.
The Engine node should display a RTW string in its second description line.
The DOOR_ri node should display RTW,nm28:2.
Start the measurement to view the models in action.
Select the Gateway panel and set the Ignition switch to 3 (right mouse click)
and press the [Starter] button.
Select the Control panel and press the [Powertrain Bus] button to open the
Engine panel.
View the pedal position controlled by the engine model.
Try the [Brake] button.
Play with the window up and down buttons of the right-side doors on the
Console panel and watch the effects on the Door right panel.
5.6 Trigger Sample Configuration

This example shows how to use CANoe events to trigger Simulink subsystems.
Furthermore it introduces the concept of using a Simulink

library for the actual model
and targeting of different hardware and/or software environments.
5.6.1 Triggering by Environment Input

The Simulink model trigsub1.mdl uses an Environment Input block to trigger the
subsystem. The subsystem trigger is configured as an either edge trigger.
5.6.2 Triggering by Environment Event

The Simulink model trigsub2.mdl uses an Environment Event block to trigger the
subsystem. The subsystem trigger is configured as a function-call trigger. In this
30
simple example the actual value of the Environment Event block variable is not used
and it is therefore connected to a terminator.
5.6.3 Using Different Targets

The Simulink models trigsub3.mdl and trigsub4.mdl use a subsystem which is
defined in the trigsub.mdl Simulink

library. The trigsub3.mdl model targets CANoe
whereas the trigsub4.mdl model targets a VxWorks environment. Using a Simulink

library for the actual model (here: Triggered Subsystem) makes it easy for you to
target different environments while providing a single point of maintenance for your
application model.
31
6 CANoe I/O Library
The CANoe I/O library is a collection of S-Functions blocks.

Figure 15: CANoe I/O library
The library provides the following features:
Data I/O
Trigger sources
Event sinks
Model execution control
CANoe simulation control
32
6.1 Signal Input
The Signal Input block is the basic input block for a database signal. It is configured
with the signal name, message name, node name and database name. It contains
the additional parameter Sample Time. According to Simulink
semantics:

0 = continuous sample time
-1 = inherited sample time

Continuous sample time is set as default. If the Signal Input block is used in a
triggered subsystem for example, the sample time must be set to inherited because
only constant blocks or blocks with an inherited sample time are allowed in triggered
subsystems.

The access to signals is provided through the Vector Interaction Layer. Please refer
to 4.5 CANoe Interaction Layer for information about preliminary steps.

For further information on the CANoe Interaction Layer see CANoe online help.
Compatibility: RTW Offline CANoe 5.1 SP3 and later
X X
6.2 Signal Output
The Signal Output block is the basic output block for a database signal. It is
configured with the signal name, message name, node name and database name.

The access to signals is provided through the Vector CANoe Interaction Layer.
Please refer to 4.5 CANoe Interaction Layer for information about preliminary steps.

X X
6.3 Signal Block
This block allows the user to collect a number of Signal Input and Signal Output block
into one subsystem and configure them by one step. This block consists of an empty
subsystem which can be configured by a Matlab
GUI.
Add Signal Output Adds Signal Output blocks to the subsystem
Add Signal Input Adds Signal Input blocks to the subsystem
Delete Removes the selected signal
33

Figure 16: Configuration of the Signal Block
The example above results in the following Signal Block:

Figure 17: Configured Signal Block
Under the hood Signal Input and Signal Output blocks are created and configured
with database name, node name, message name and signal name.
34

X X Matlab R14 and later
6.4 Message Input
The Message Input block serves as input block for all signals of a database
message. The values of the signals are output as a vector from the block. Double
click the block to select a message. The block will be configured with the message
name, node name and database name. It contains the additional parameter Sample
Time accessible from the dialog Mask Parameters. According to Simulink

semantics:


Continuous sample time is set as default. If the Message Input block is used in a
subsystems.

The access to the signals of a message is provided through the Vector Interaction
Layer. Please refer to 4.5 CANoe Interaction Layer for information about preliminary
steps.

6.5 Message Output
The Message Output block serves as output block for all signals of a database
message. It receives the values of the signals as a vector. Double click the block to
select a message. The block will be configured with the message name, node name
and database name.

The access to signals of the message is provided through the Vector Interaction
Layer. Please refer to 4.5 CANoe Interaction Layer for information about preliminary
steps.

35
6.6 Simulation Step
The Simulation Step block is used to control the CANoe simulation from within
Simulink
. You must place this block in your model if you wish to run CANoe in Slave
mode during a simulation within Simulink
. When used within RTW
this block
performs nothing.
Compatibility: RTW Offline
X
6.7 CAPL Call
The CAPL Call block can be used to trigger a Simulink
subsystem from CAPL.

Figure 18: CAPL Call block
The CAPL Call block is configured with a function name which is exported by the
RTW
generated CANoe DLL. Function parameters are not supported.

X
36
6.8 CAPL Handler
The CAPL Handler block can be used to handle a Simulink event in CAPL.

Figure 19: CAPL Handler block
The CAPL Handler block is configured with a function name. If the attached CAPL file
implements this function it will be called whenever the Simulink
event fires. Function

parameters are not supported.
X X

37
6.8.1 Environment Event
The Environment Event block is a combination of an Environment Input block and a
function-call trigger source. You can use this block to trigger Simulink
subsystems.

Figure 20: Environment Event block
The Environment Event block is configured with an environment variable name. The
trigger port fires whenever the input variable changes.
X X
6.9 Environment Input
The Environment Input block is the basic input block for a CANoe environment
variable. It is configured with an environment variable name. It contains the additional
parameter Sample Time. According to Simulink
semantics:


38
Continuous sample time is set as default. If the Environment Input block is used in a
subsystems.
X X
6.10 Data Environment Input
The Data Environment Input block is used for an environment variable of type data.
The bytes of the environment variable are output as a vector from the block.
6.11 Environment Output
The Environment Output block is the basic output block for a CANoe environment
variable. It is configured with an environment variable name.
X X
6.12 Data Environment Output
The Data Environment Output block is used for an environment variable of type data.
It receives the bytes of the environment variable as a vector.
6.13 Environment Step

The Environment Step block is used to designate a Simulink model that is executed
only when one of its CANoe environment inputs changes. This is particularly useful
for a model whose outputs are a direct function of its inputs and only need to be
updated when the inputs are changed.
39

Figure 21: Environment Step block
Note: The Environment Step block should only be used if the Simulink model
does not contain any continuous or discrete blocks.
X
6.14 Environment Trigger
The Environment Trigger block can be used to trigger Simulink subsystems on

environment input variable changes.
40

Figure 22: Environment Trigger block
The Environment Trigger block fires a function call trigger whenever one of the
environment input variables changes.
X
6.15 System Variable Input
The System Variable Input block is the basic input block for CANoe system variables.
It is configured with the name space name, system variable name and an array index
for accessing only one value of an array system variable. It contains the additional
parameter Sample Time. According to Simulink
semantics:


Continuous sample time is set as default. If the System Variable Input block is used
in a triggered subsystem for example, the sample time must be set to inherited
because only constant blocks or blocks with an inherited sample time are allowed in
triggered subsystems.

41
Compatibility: RTW Offline CANoe 7.0 and later
6.16 System Variable Output
The System Variable Output block is the basic output block for a CANoe system
variable. It is configured with the name space name, system variable name and an
array index for accessing only one value of an array system variable.

Compatibility: RTW Offline CANoe 7.0 and later
42
7 CAPL Functions
7.1 General
The RTW generated DLL contains two additional functions which can be called by
CAPL. These functions may be used to control the behavior of the generated
CANoe/MATLAB

Interface and the execution of the Simulink model. The function
names are in the form
MODEL_fct where MODEL is the name of the Simulink

model.
Note: The CANoe/MATLAB Interface uses meaningful default values to set up
and control Simulink model execution. These defaults are determined
during the generation process by the RTW. If you use the CAPL
functions described herein you can override these defaults and take
control of model execution.
Build option Export CAPL Functions:
The CAPL functions described herein are only exported if this option is on.
Default value is off.
Long model filenames (> 44 characters) are only supported if this option is
off.
7.2 MODEL_init
Function:
LONG MODEL_init( DWORD enableTimer, DWORD enableEvents);
Parameters:
DWORD enableTimer
Enables or disables the internal model execution timer
DWORD enableEvents
Enables or disables the event triggered model execution
Description:
MODEL_init The function is used to initialize the CANoe runtime environment for
the generated MODEL DLL. This effectively overrides the default execution settings
which were compiled into the MODEL DLL.
DWORD enableTimer
Per default the generated MODEL is executed by the CANoe runtime environment
according to its fixed simulation step size. If the user sets the fixed step size to
"auto", Simulink

calculates the required minimum fixed step size based on the model
contents. However, if the user specifies a fixed step size Simulink

checks this value
against the model contents during simulation startup and generates an error
message if the step size violates any timing restrictions. If the MODEL is built into a
43
DLL with the RTW, the fixed step size is written into the generated C source code
(See generated "MdlInitializeSampleTimes" function in MODEL.c). The
CANoe/ MATLAB
Interface reads this generated fixed step size value during

measurement startup to set up a timer used to execute the MODEL at the specified
sample time, thus providing exactly the same execution environment as in Simulink
.
If the user wants to execute the MODEL non-cyclically at arbitrary sample times (for
example with the MODEL_step function) the user must disable the CANoe/
MATLAB
Interface timer. This is done by setting this parameter to zero.

DWORD enableEvents
In addition (or instead) of using the MODEL_step function to execute the MODEL a
simulation step may be performed on each environment variable change. To activate
this feature this parameter must be set to a nonzero value.
Return:
Zero on success, nonzero otherwise.
7.3 MODEL_step
Function:
LONG MODEL_step();
Description:
MODEL_step The function is used to execute a simulation step.
Return:
Zero on success, nonzero otherwise.
7.4 Parameterization Functions
If the options Export CAPL Functions and Enable Parameterization from CANoe
are activated the RTW
generated DLL will contain the following three functions for

accessing parameter values. The return values of all functions are listed in the table
below:

Return value Meaning
0 Success
3 No model data available (internal error)
4 nrOfValues Wrong parameter type: does not match or
unsupported parameter value type (complex numbers for
example).
5 Wrong index: No parameter exists with the given index.
44
Note: Some parameters might not be configurable during measurement. This
depends on the implementation of a Simulink block. If the MODEL_set

functions are used in the PreStart section of a CAPL program, all
parameters will be configurable and will use the new values during
measurement.
Parameterization requires the C-API for data exchange which is available
since Matlab R14.
7.4.1 MODEL_getParameter
Function:
LONG MODEL_getParameter( DWORD index, FLOAT values[],
DWORD nrOfValues)
Description:
MODEL_getParameter The function retrieves the values of a model parameter
specified by index values and copies them into the array. nrOfValues must
match the number of values the parameter has. The size of the values array must
not be smaller than nrOfValues.
7.4.2 MODEL_setParameter
Function:
LONG MODEL_setParameter( DWORD index, FLOAT values[],
DWORD nrOfValues)
Description:
MODEL_setParameter The function copies the values from the values array to a
model parameter specified by index nrOfValues . must match the number of
values the parameter has. The size of the values array must not be smaller than
nrOfValues.
7.4.3 MODEL_setScalarParameter
Function:
LONG MODEL_setScalarParameter( DWORD index, FLOAT value)
Description:
MODEL_setScalarParameter The function sets a scalar model parameter
specified by index to the given value.

45
8 Utilities
8.1 Setup of environment blocks
Note: The setup procedure described here only applies to CANoe 3.1.15. Later
CANoe versions already provide this or a more modern dialog. In addition
only MATLAB
R12 or later is supported.

To specify an environment variable name for a block you can choose from a list of
available variables rather than typing the name into the block mask parameters.

Figure 23: Environment Information dialog
To enable this feature you need to setup the ActiveX Control located in:
$(MATLABROOT)\rtw\c\canoe\devices\misc\CANutil.dll
$(CANOEROOT)\Exec32 Copy the DLL into your directory, open a console window
and type:
C:\WINNT\system32\regsvr32 $(CANOEROOT)\Exec32\CANutil.dll
or:
C:\WINDOWS\system\regsvr32 $(CANOEROOT)\Exec32\CANutil.dll
if you are running Windows 9x. Copy the CANoe I/O library located in:
$(MATLABROOT)\rtw\c\canoe\devices\misc\canoelib.mdl
to the directory:
$(MATLABROOT)\rtw\c\canoe\devices\
46
A double-click on the environment block will bring up the dialog.
You can still edit the name by choosing Mask parameters from the context menu.
If you use a later version of CANoe 3.1.15 and you dont want to use this feature,
copy the CANoe I/O library located in:
$(MATLABROOT)\rtw\c\canoe\devices\misc\canoelib_nodlg.mdl
to
$(MATLABROOT)\rtw\c\canoe\devices\
and rename the model file to canoelib.mdl.
8.2 Setup of signal and environment blocks
Note: The setup procedure described here only applies to Matlab 7.0 R14 or
later
To specify database name, node name, message name and signal name of the
signal input and signal output block you can choose from a list rather than typing the
names into the block mask parameters. To specify an environment variable name for
a block you can also choose from a list of available variables.

47
Figure 24: Symbol Selection dialog
A double-click on the signal input / signal output block will bring up the dialog.
You can still edit the names by choosing Mask parameters from the context
menu.
48
9 Troubleshooting
9.1 Unusable CANoe GUI during offline simulation
It can happen that the CANoe user interface doesnt update correctly or isnt usable
at all when operation in offline mode. If so, open the CAN.INI configuration file and
verify that the following entry is set to zero:
[System]
GUIThreadPriority=0
The default setting for this entry is 3 which lowers the priority of the CANoe GUI.
9.2 Unable to compile the nlapml.cpp source file.
If the compilation of the source file fails with the following error:

error C2117: 'test_for_long_filename_init' : array bounds overflow

youve activated the export of CAPL functions in the code generation options and the
file name of your model is longer than 44 characters. If you really need the CAPL
functions save your model under a shorter name. If you dont need the additional
CAPL functions deactivate the export in the CN code generation options.

9.3 Spaces in MATLAB installation path

Due to problems with spaces in the MATLAB

installation path Mathworks issued a
patch for the code generation process which applies to MATLAB
7.0 R14 SP2. If

you are using MATLAB
7.0 R14 SP2 and have installed it in a directory which

contains spaces you cannot generate code unless you modify your target makefile. In
this case please add the following lines to your target makefile.
( $(MATLABROOT)\rtw\c\canoe\cn_msdll.tmf):

line 99:

ALT_MATLAB_ROOT = |>ALT_MATLAB_ROOT<|
ALT_MATLAB_BIN = |>ALT_MATLAB_BIN<|

!if "$(MATLAB_ROOT)" != "$(ALT_MATLAB_ROOT)"
MATLAB_ROOT = $(ALT_MATLAB_ROOT)
!endif
!if "$(MATLAB_BIN)" != "$(ALT_MATLAB_BIN)"
MATLAB_BIN = $(ALT_MATLAB_BIN)
!endif

49
9.4 Model Advisor Checks not available

After installation of the CANoe Matlab Interface 1.7 or newer the Simulink Model
Advisor should contain a new folder named CANoe Matlab Interface Checks below
the By Product section. The CANoe checks are created by a file named
sl_customization.m located in the folder $(My Documents)\Matlab\CANoe.
Please make sure that this folder is included in the Matlab
path list (menu File

Set Path). Matlab
slcustomize updates all customizations if the command is

called. Please make sure that your version of Simulink
supports custom checks for

the Model Advisor.
50
10 Index
A I
actuator............................................................6 Interacion Layer .............................................. 6
Attributes..................................................10, 25 Interaction Layer ............................................. 5
Automot .........................................................28
M
C
Message Input .............................................. 34
Message Output............................................ 34 CAN.INI............................................................9
Middleware.................................................. 4, 6 CANdb attributes ........................................... 11
Model Generation Wizard..............................11 CANoe ...................................................1, 3, 48
MODEL_getParameter ................................. 44 CANoe I/O Library .........................................31
MODEL_init................................................... 42 CANoe Interaction Layer ...............5, 10, 32, 34
MODEL_setParameter ................................. 44 CANoeIL..........................................................5
MODEL_setScalarParameter ....................... 44 CAPL Call ......................................................35
MODEL_step ................................................ 43 CAPL Handler................................................36
D N
Data Environment Input.................................38 Network management................................... 10
Data Environment Output ..............................38 Network Management Layer........................... 7
NodeLayerModules....................................... 25
E
O
ECU.........................................................4, 6, 7
Enable Parameterization from CANoe ....13, 27 Offline............................................................ 24
Environment Event ........................................37 Offline Mode.................................................... 2
Environment Information dialog.....................45 OSEK.............................................................11
Environment Input .........................................37
P
Environment Output.......................................38
Environment Step ..........................................38
Parameterization........................................... 14
Environment Trigger ......................................39
Perfom Simulation Step at t(0)................ 14, 27
Export CAPL-Function.............................13, 27
R
G
RTW Options ................................................ 27
Generate Visual C++ project file..............14, 27
S
H
sensor ............................................................. 6
HIL .................................................................24
Setup............................................................... 8
HIL Mode .........................................................3
Signal Input ................................................... 32
Signal Output ................................................ 32
51
Simulation Setup ...........................................28 System Variable Input ................................... 40
Simulation Step..............................................24 System Variable Output ................................ 41
Sine................................................................24
T
Sine Parameterization .............................25, 27
Slave Mode......................................................9
Transport Layer............................................... 6
Symbol Selection dialog ................................47
System Target File Browser.............................8


CANoe Matlab en

Uploaded by

Document Informationclick to expand document informationmatlab

Document Informationclick to expand document information

Copyright:

Available Formats

CANoe Matlab en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CANoe Matlab en

Uploaded by

Copyright:

Available Formats

CANoe

Model for Interaction with CANoe...............12

Model for Parameterization from

installation path ..........................................................48

interface. The CANoe/MATLAB

is the simulation Master. This

you can target CANoe and produce a Windows

. Examples of this can be found in

using the signal input and output blocks as interfaces

Interface requires the following minimum product versions:

Interface files (canoe\*.*) are located in the following directory:

needs to be associated with your C compiler in order to generate the dll

documentation for a correct setup of the compiler

.NET (7.1) R14

2005 (8.0) R2006a

Model for Interaction with CANoe

can be configured to copy

Real-Time Workshop Settings

..\MODEL_cn_rtw\release\ folder relative to the folder containing the Simulink

Enable Simulink Signal Analysis: Enables analysis of all named Simulink

Model for Parameterization from CANoe

. In most cases it wont be necessary to

Real-Time Workshop Settings

depends on the implementation of a Simulink block. Therefore it is

CANoe and of the CANoe Matlab Interface. Therefore the following

. This block may be left in models intended for

, specify the Output Directory and build the DLL.

This configuration shows how Simulink models can be parameterized after

. It is similar to the Sine configuration. The

version 6.0 R.12 or later

demo model SF_Car.mdl has been added to the Simulation Setup.

3. Enable Simulink Signal Analysis: Enables analysis of all named Simulink

. The model contains 5 CANoe specific blocks:

. When used within RTW

subsystem from CAPL.

generated CANoe DLL. Function parameters are not supported.

event fires. Function

The Environment Trigger block can be used to trigger Simulink subsystems on

MODEL_fct where MODEL is the name of the Simulink

Interface reads this generated fixed step size value during

Interface timer. This is done by setting this parameter to zero.

generated DLL will contain the following three functions for

depends on the implementation of a Simulink block. If the MODEL_set

R12 or later is supported.

9.3 Spaces in MATLAB installation path

7.0 R14 SP2. If

7.0 R14 SP2 and have installed it in a directory which

path list (menu File

slcustomize updates all customizations if the command is

supports custom checks for

You might also like

Interface files (canoe\.) are located in the following directory: