CANoe DENoe - KEMT FEI TUKE

48
tribute DBName, then its value is used as the name. If the attribute does not exist,
the name is derived from the file name. The user can overwrite the name. Database
names must begin with a character and may not contain any blank or special characters.
The database name must be unique. If a name that is automatically determined already
exists, it is assigned a unique name according to the sequence of names
CANdb1, CANdb2, etc.
You can assign both CAN controllers (CAN1 and CAN2) to exactly one database. All
other databases are assigned to the two controllers jointly. This assignment defines
the default selector for message definitions in CAPL.
2.3.4 Use of Multiple Databases
For large systems it may be sensible to distribute the descriptions of messages and
signals, as well as environment variables, to several partial databases. When operating
CANoe on two buses it also makes sense to describe each system by its own
database.
CANoe supports the simultaneous use of multiple databases. You can configure the
databases that you would like to associate with CANoe using the menu command
File│Associate database. Afterwards you can use the symbolic names for messages,
signals and environment variables from all databases in all function blocks
and in CAPL. To do this, you would simply enter the symbolic name in the appropriate
input box. There is a list of all symbolic names in the signal selection dialogs
which you can open by activating the small buttons next to the individual input boxes.
You would select the desired symbolic names there.
If you are using more than one database, the messages in the databases that follow
the first database are qualified with the database name, i.e. the message name is
preceded by the database name followed by two colons. However, you will only need
to use these qualified names to resolve ambiguities. As long as the symbolic names
are unique among all databases, you can forego qualification of symbolic names in
all function blocks and when editing CAPL programs.
2.3.5 Resolving Ambiguities
When multiple databases are used, it is essentially possible to have ambiguities in
the use of symbolic names. These ambiguities must then be resolved by the program.
On the one hand, messages arriving from the bus via one of the two CAN controllers
and logged by the program can have different symbolic names in two databases.
On the other hand, the user may wish to configure function blocks or measurement
windows with different messages that have the same name in different databases.
Ambiguities of the first type are resolved by the sequence in which you have entered
the databases in the list of the database selection dialog. Furthermore, you have the
option of associating a prioritized database to each of the two CAN controllers. For
messages received by this controller, this database then has highest priority in the
symbolic association. Only if the symbolic name is not found there, does the program
search all other databases indicated in the database selection dialog, and this is
done in the sequence defined there.
© Vector Informatik GmbH CANoe/DENoe Manual Version 4.1.1