Setpoint Assignment In The Subscriber; Activating/Parameterizing Slave-To-Slave Communication - Siemens SINAMICS S120 Function Manual

11.2.4.1

Setpoint assignment in the subscriber

Information about setpoints
● Number of setpoint
● Contents of the setpoints
● Operation as "standard" slave
● Operation as subscriber
11.2.4.2

Activating/parameterizing slave-to-slave communication

The "slave-to-slave communication" function must be activated both in the publishers as well
as in the subscribers, whereby only the subscriber is to be configured. The publisher is
automatically activated during bus startup.
Activation in the publisher
The master is informed abut which slaves are to be addressed as publishers with a modified
layer 2 function code (DXB req) via the configuration of the subscriber links.
The publisher then sends its input data not only to the master but also as a broadcast
telegram to all bus nodes.
These settings are made automatically using the bus configuration tool (e.g. HW Config).
Drive functions
Function Manual, (FH1), 04/2014, 6SL3097-4AB00-0BP4
When bus communication is being established, the master signals the slave the number
of setpoints (process data) to be transferred using the configuring telegram (ChkCfg).
The structure and contents of the data are determined using the local process data
configuration for the "SINAMICS slave".
The drive unit (slave) only receives its setpoints as output data from the master.
These setpoints of the publisher are used, in addition to the setpoints received from the
master, corresponding to the configured telegram structure (p0922).
The slave is informed of the assignment via the parameterization and configuration
telegram when bus communication is being established.
11.2 Communication via PROFIBUS DP
Communication
693