Forwarding Of Faults - Siemens SINAMICS S120 Commissioning Manual

3.5.5

Forwarding of faults

Forwarding of CU faults
When faults are triggered on the drive object of the CU, it is always assumed that central
functions of the drive unit are affected. For this reason, these faults are not only signaled on
the drive object of the CU, but may also be forwarded to all other drive objects (propagation).
The fault reaction affects the drive object of the CU and all other drive objects. This behavior
also applies to the faults set in a DCC chart on the CU with the aid of DCB STM.
A fault that is set on the drive object of the CU must be acknowledged on all drive objects to
which this fault was forwarded. In this way, the fault is then automatically acknowledged on
the drive object of the CU. Alternatively all faults of all drive objects can also be
acknowledged on the CU.
Alarms are not forwarded to other drive objects by the CU.
Example
Drive object faults are only transferred to the drives, i.e. a fault on a TB30 stops the drive -
however, a fault on the drive does not stop the TB30.
Forwarding of faults due to BICO interconnections
If two or more drive objects are connected via BICO interconnections, then faults from drive
objects, type CU, TB30, DMC20, TM31, TM15, TM17, TM15DIDO, TM54F_MA, TM54F_SL
and CU_LINK are transferred to drive objects, type BIC, SERVO, VECTOR, TM41. There is
no forwarding of faults within these two groups of drive object types.
This behavior also applies to the faults set in a DCC chart on the above drive object types
with the aid of DCB STM.
Commissioning Manual
Commissioning Manual, (IH1), 01/2011, 6SL3097-4AF00-0BP1
Diagnostics
3.5 Fault and alarm messages
233