Siemens SINAMICS Configuration Manual page 134

Communication
A.1 Communication
Figure A-18
10.You should therefore adjust the telegrams for each drive object of the selected drive device
that is to participate actively in slave-to-slave communication.
Autodetect in the STARTER
The settings configured in HW Config for the cross-reference telegrams are automatically
detected by the STARTER. A telegram extension is not required in the STARTER.
Diagnosing the PROFIBUS slave-to-slave communication in STARTER
Since the PROFIBUS slave-to-slave communication is implemented on the basis of a
broadcast telegram, only the subscriber can detect connection or data faults, e.g. via the
publisher data length (see "Configuration telegram").
The publisher can only detect and report an interruption of the cyclic connection to the DP
master (A01920, F01910). The broadcast telegram to the subscriber will not provide any
feedback. A fault of a subscriber must be fed back via slave-to-slave communication. In case
of a "master drive" 1:n, however, the limited quantity framework (see "Links and requests")
should be observed. It is not possible to have n subscribers report their status via slave-to-
slave communication directly to the "master drive" (publisher).
Diagnostics can be performed using the diagnostic parameters r2075 ("Receive PROFIBUS
diagnostics telegram offset PZD") and r2076 ("Send PROFIBUS diagnostics telegram offset
PZD"). The parameter r2074 ("PROFIBUS diagnostics, receive bus address PZD") displays
the DP address of the setpoint source of the respective PZD.
134
Details after the creation of the slave-to-slave communication link
Configuration Manual, 08/2017, A5E36912609A
Industrial Security