Technical data

Communication
9.3 Communication via PROFIBUS DP
Function Manual
Function Manual, 06/2012, 6SL3097-4AB10-0BP4
639
The following terms are used for the functions described here:
● Slave-to-slave communication
● Data Exchange Broadcast (DXB.req)
● Slave-to-slave communication (is used in the following)
3*3&
)URPWKHSHUVSHFWLYHRIWKH&ODVVPDVWHU
$QVZHU
,QSXWGDWD

2XWSXWGDWD

&ODVVPDVWHU
HJ6,0$7,&6
3DUDPHWHUDVVLJQPHQWPDVWHU
GHILQHVWKHF\FOHFORFN
+:&RQILJ
&RQILJXULQJ
6ODYH
6,1$0,&6
3XEOLVKHU
6ODYH
6,1$0,&6
6XEVFULEHU
6ODYH
6,1$0,&6
6XEVFULEHU
/LQNV
'ULYH(6%DVLF
Figure 9-25 Slave-to-slave communication with the publisher-subscriber model
Publisher
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 are transferred with a
modified layer 2 function code (DXB.req). The publisher then sends its input data to the
master with a broadcast telegram to all bus nodes.
Subscriber
The subscribers evaluate the broadcast telegrams, sent from the publishers, and use the
data which has been received as setpoints. The setpoints are used, in addition to the
setpoints received from the master, corresponding to the configured telegram structure
(p0922).