Monitoring Telegram Failure - Siemens sinamics dcp Operating Instructions Manual

Operation
8.5 Communication via PROFIBUS DP
Field
DBB, DBW, DBD
(data block offset)
Length
Acquisition cycle
Number of elements
Decimal places
Note
• You can operate a SIMATIC HMI together with a drive unit independently of an existing
controller.
A basic "point-to-point" connection can only be established between two nodes (devices).
• The "variable" HMI functions can be used for drive units. Other functions cannot be used
(e.g. "messages" or "recipes").
• Individual parameter values can be accessed. Entire arrays, descriptions, or texts cannot
be accessed.
8.5.3.6

Monitoring telegram failure

When monitoring telegram failure, SINAMICS differentiates between two cases:
● Telegram failure with a bus fault
After a telegram failure, and the additional monitoring time has elapsed (p2047), bit
r2043.0 is set to "1" and alarm A01920 is output. Binector output r2043.0 can be used for
a quick stop, for example.
Once the delay time p2044 has elapsed, fault F01910 is output. Fault F01910 triggers
fault response OFF3 (quick stop) on the DO DC_CTRL. If no OFF response is to be
triggered, the fault response can be reparameterized accordingly.
Fault F01910 can be acknowledged immediately. The drive can then be operated even
without PROFIdrive.
Image 8-22
172
Monitoring telegram failure with a bus fault
Value
Drive object no. and subindex
bit 15 ... 10:
Drive object no. 0 ... 63
bit 9 ... 0: Subindex 0 ... 1023
or expressed differently
DBW = 1024 * drive object no. + subindex
Not activated
Any
1
Any
Operating Instructions, 05/2016, A5E34382853K
SINAMICS DCP