Siemens SINAMICS Configuration Manual page 127

Setpoint assignment in the subscriber
Information about setpoints
● Number of setpoint
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).
● Contents of the setpoints
The structure and contents of the data are determined using the local process data
configuration for the "SINAMICS slave".
● Operation as "standard" slave
The drive unit (slave) only receives its setpoints as output data from the master.
● Operation as subscriber
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.
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).
Activation in the subscriber
The slave, which is to be used as subscriber, requires a filter table. The slave must know which
setpoints are received from the master and which are received from a publisher.
The filter table is created automatically via the bus configuration tool (e.g. HW Config).
The following diagram shows the information contained in the filter table.
Industrial Security
Configuration Manual, 08/2017, A5E36912609A
Communication
A.1 Communication
127