Can Message Parameters; Data Length Of The Can Message - HBM QUANTUM X Bedienungsanleitung

Functional description
sent as a hexadecimal numerical value, taking
<BitSequence> into account. The number of bits is deter­
mined by the <SignalLength> of the source. The bits of
the error value are transmitted, starting with Bit 0 of the
error value.
6.5.6

CAN message parameters

How are CAN messages transmitted?
The contents of a CAN message, that is, which source
data are to be "mapped" in which CAN message at which
point, are defined in the subtree <Source>. The header
of the CAN message is defined in the <CanMessage>
subtree.
The parameters <Identifier> and <ExtendedFrame> in
the subtree <Source> establish the <CanMessage> into
which this signal source is to be "mapped".

6.5.6.1 Data length of the CAN message

The data in CAN messages are always multiple bytes.
The length of the CAN message corresponds to the
number of bytes required to transmit all the signal
sources actively "mapped" into this CAN message.
If, for example, only the first 18 data bits of a CAN mes­
sage are mapped, the data length of the CAN message
<ByteCount> is 3 bytes.
It is always possible and acceptable to have "gaps" in the
CAN message. Their unspecified bits are transmitted
with "0".
CANBus 43
A4461-2.0 HBM: public