Isoevent; Constraints For Mx840B - HBM QUANTUM X Bedienungsanleitung

Functional description
48
The transmission of a CAN message can also be trig­
gered by a control (see Section 5.8.1).

6.5.8.4 IsoEvent

This corresponds to the behavior implemented in the
MX471B up to and including firmware version 4.4: The
CAN message is sent when one of the "mapped" signal
sources has been received isochronously (via Firewire).
<Divisor> can also be used to establish that only every n
received isochronous events are sent. This can reduce
the workload of the CAN bus, if measured values with
low dynamics (e. g. temperature) are to be sent,
for example.
In addition, the transmission of a CAN message can also
be triggered by a control item (see Section 5.8.1).
6.5.9

Constraints for MX840B

The MX840B is able to send measured values obtained
within the module via CAN messages. There are clear
constraints here, for reasons of performance. CAN map­
ping is not possible.
To maintain compatibility with the new XML trees in the
MX471B, the MX840B will also only use the new XML
trees. This allows both the module types to be
parameterized with the same software interface.
The MX840B will also only be able to send a maximum of
10 different CAN messages, and each CAN message will
only be able to have 1 source, corresponding to an ana­
log measured value within the module.
So these parameters cannot be freely selected in the
MX840B, they are fixed as stated:
A4461-2.0 HBM: public
CANBus