Diagnosing The Profibus Slave-To-Slave Communication In Starter - Siemens SINAMICS S120 Function Manual

The details after creation of the slave-to-slave communication link for a drive object of the
drive device are as follows:
Figure 11-27 Details after the creation of the slave-to-slave communication link
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.
11.2.4.4

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).
Drive functions
Function Manual, 11/2017, 6SL3097-4AB00-0BP5
11.2 Communication via PROFIBUS DP
Communication
801