CANoe DENoe - KEMT FEI TUKE

174
Figure 86: Signal layout of CANdb++ message
The counting of bytes for the layout view of the message starts with 0 at byte 5 of the
MOST frame. This has to be taken into account during placement of signals onto a
database entry for a MOST message. The first parameter ‘PosX’ shown in Table 1
has a start bit of 0 and is shown in byte 0 of the layout view, although it is placed in
the bytes 5 and 6 of the MOST frame (see Table 1).
In this release CANdb++ supports parameters with a fixed length only. Parameters
where the length is determined at runtime, e.g. with zero terminated strings, are not
supported, because the position of the following parameters cannot be determined at
design time.
In addition, only signals up to a length of 12 bytes and a placement within the bytes 5
to 16 can be defined. Segmented messages as through the application message service
are not supported in this release.
9.7.5 HW Configuration
The data structure described above relates only to the application layer of a MOST
system. It does not contain any information about the HW structure of the MOST ring.
In MOST nodes the NetServices translate the addressing from the application layer
addresses (FBlock, FunctionId,…) to physical addresses. In the recent release of
CANoe Option MOST there’s no NetServices support available.
The translation of physical addresses can be achieved by adding network nodes to
the database. Each network node has the attribute ‘MostNodeAdr’. CANoe.MOST
translates the physical address into a symbolic device name by matching the address
with the value of the node attribute and displaying the name of the corresponding
network node.
The same procedure allows the translation of group addresses into group names. For
each group address a network node with a suitable name could be entered into the
database (attribute ‘MostGroupAdr’).
© Vector Informatik GmbH CANoe/DENoe Manual Version 4.1.1