Siemens SIMODRIVE 611 universal - Telegram Structure

5
5.10 Slave–to–slave communications (from SW 4.1)
5-320
 Siemens AG 2005 All Rights Reserved
SIMODRIVE 611 universal Description of Functions (FBU) – 04.05 Edition
5.10.4 Telegram structure
In order to be able to use the process data for slave–to–slave commu-
nications, the appropriate signal IDs must be entered into P0915 and
P0916 for the telegram configuration.
For synchronous operation, where position reference values or actual
values are entered for the axis couplings (refer to Chapter 6.3), the fol-
lowing process data is required for data transfer via PROFIBUS–DP:
 Signals for synchronous operation in the actual value direction (publisher)
– Position actual value ––> Signal ID 50206
– Position reference value ––> Signal ID 50208
– Correction, position reference value ––> Signal ID 50210
– Status word, slave–to–slave comm. ––> Signal ID 50118
 Signals for synchronous operation in the setpoint direction (subscriber)
– External position reference value ––> Signal ID 50207
– Correction, ext. position ref. value ––> Signal ID 50209
– Control word, slave–to–slave comm. ––> Signal ID 50117
For a description of this process data, refer to Chapter 5.6.
An example of a synchronous application, from the perspective of the
slave drive, is shown in Fig. 5-33. Most of the control words are ent-
ered from the PROFIBUS–DP master; whereas, the actual setpoints/
reference values are sent from a ”SIMODRIVE 611 universal” as
master drive.
ZSW1
AktSatz
PosZsw
ZSW2
QZsw
XsollP_H
XsollP_L
STW1
SatzAnw
PosStw
STW2
QStw
Xext_H
Xext_L
Setpoints in the
”SIMODRIVE 611
universal” (slave drive)
Setpoint telegram from the master (bytes)
Actual value in the ”SIMODRIVE
universal” (master drive)
Fig. 5-33 Example, assigning the process data for a synchronous application
Configuring a
telegram
Synchronous
operation
Example,synchron
ous operation
5 Communications via PROFIBUS DP
08.99
07.0108.01