The following terms are used for the function described in this chapter:
● Slave-to-slave communication
● Data Exchange Broadcast (DXB.req)
● Slave-to-slave communication (is used in the following)
With the "slave-to-slave communication" function, at least one slave must act as the publisher.
The publisher is addressed by the master when the output data is transferred with a modified
layer 2 function code (DXB.req). The publisher then sends its input data for the master with a
broadcast telegram to all bus nodes.
The subscribers evaluate the broadcast telegrams, sent from the publishers, and use the data
which has been received as setpoints. These setpoints of the publisher are used, in addition
to the setpoints received from the master, corresponding to the configured telegram structure
Configuration Manual, 08/2017, A5E36912609A
From the perspective of the Class 1 master
Slave-to-slave communication with the publisher-subscriber model