A.1.2.3 Slave-To-Slave Communication - Siemens SINAMICS Configuration Manual

Communication
A.1 Communication
Example: Quick stop at telegram failure
Assumption:
● A drive unit with an Active Line Module and a Single Motor Module.
● VECTOR mode is activated.
● After a ramp-down time (p1135) of two seconds, the drive is at a standstill.
Settings:
CU
A_INF
VECTOR
Sequence:
1. Following a telegram failure and once the additional monitoring time (p2047) has elapsed,
binector output r2043.0 of drive object CU switches to "1".
At the same time, alarm A01920 is output for the A_INF drive objects and alarm A01920
and fault F01910 are output for VECTOR.
2. When F01910 is output, an OFF3 is triggered for the drive.
3. After a two-second delay time (p2044), fault F01910 is output on the infeed and triggers
OFF2.
A.1.2.3 Slave-to-slave communication
For PROFIBUS DP, the master interrogates all of the slaves one after the other in a DP cycle.
In this case, the master transfers its output data (setpoints) to the particular slave and receives
as response the input data (actual values). Fast, distributed data transfer between drives
(slaves) is possible using the "slave-to-slave communication" function without direct
involvement from the master.
124
p2047 = 20 ms
p2044 = 2 s
p2044 = 0 s
Configuration Manual, 08/2017, A5E36912609A
Industrial Security