CANoe DENoe - KEMT FEI TUKE

156
not send them on the bus. Since the data flow is directed from left to right, these
messages are only passed to the function blocks to the right of the CAPL program.
Only messages generated by CAPL programs located in CANoe's simulation setup
can be sent out on the bus. This completely logical behavior - which may at first
seem surprising - applies equally to the generator block, which - when it is located in
the measurement setup - similarly generates messages without affecting the bus.
Therefore, in general those CAPL program blocks that exclusively serve analysis
purposes should be inserted on the right side of the measurement setup, while program
blocks for transmitting CAN messages should be inserted in CANoe's simulation
setup.
6.1.3 Use of the Symbolic Database in CAPL
Just like other function blocks in the measurement setup, from CAPL you also have
access to the symbolic information in the database. For example, instead of using the
identifier 100 in your CAPL program you could use the symbolic name EngineData at
all locations, provided that you have assigned this name to the identifier 100 in your
database.
Use of the symbolic database makes your programs essentially independent of information
that only relates to the CAN protocol, but has no meaning for the applications.
Let us assume, for example, that during the development phase you determine
that certain CAN identifiers in your system should be reassigned to change message
priorities, and that in your system the message EngineData should now get the higher
priority identifier 10 instead of the identifier 100.
In this case, let us assume that you have already developed test configurations and
CAPL programs for your system which are exclusively based on the symbolic information
(which do not use the identifier 100 anywhere, but rather always refer to the
name EngineData). After modifying the identifiers in the database, you can incorporate
the new information in the configuration by recompiling the CAPL programs. It is
not necessary to adapt the CAPL programs to the new identifiers, since you only used
symbolic names (e.g. EngineData), and not CAN identifiers (previously ID 100,
now ID 10).
Therefore, it is advisable to manage all information relating only to the CAN bus in
the database, and to use application-relevant symbolic information in CANoe exclusively.
6.1.4 Introduction to CAPL
CAPL is a procedural language whereby the execution of program blocks is controlled
by events. These program blocks are known as event procedures.
The program code that you define in event procedures is executed when the event
occurs. For example, you can send a message on the bus in response to a key press
(on key), track the occurrence of messages on the bus (on message), or execute
certain actions cyclically (on timer).
© Vector Informatik GmbH CANoe/DENoe Manual Version 4.1.1