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

The SINAMICS S DXB GSD file contains among other things standard telegrams, free
telegrams and slave-to-slave telegrams for configuring slave-to-slave communication. The
user must take these telegram parts and an axis separator after each drive object to
compose a telegram for the drive unit.
Processing a GSD file in HW Config is covered in the SIMATIC documentation. Suppliers of
PROFIBUS components can provide their own bus configuration tool. The description of the
respective bus configuration tool is described in the relevant documentation.
Device identification
Identification for individual slaves facilitates diagnostics and provides an overview of the
nodes on the PROFIBUS.
The information for each slave is stored in the Control Unit parameter r0964[0...6] device
identification.
10.2.4.5

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.
r2074 and r2075 enable the source of a slave-to-slave communication relationship to be
verified in the Subscriber.
Note
The Subscribers do not monitor the existence of an isochronous Publisher sign of life.
Faults and alarms with PROFIBUS slave-to-slave communication
The alarm A01945 signals that the connection to a least one Publisher of the drive device is
missing or has failed. Any interruption to the Publisher is also reported by the fault F01946 at
the affected drive object. A failure of the Publisher only impacts the respective drive objects.
More detailed information on the messages can be found in
References: SINAMICS S120/150 List Manual
Drive functions
Function Manual, (FH1), 01/2012, 6SL3097-4AB00-0BP2
10.2 Communication via PROFIBUS DP
Communication
627