Operation
7.17 CPU time load with SINAMICS DCP
SINAMICS DCP
372 Operating Instructions, 09/2019, A5E34382853K
7.16.3.5 Forwarding faults and alarms
Forwarding faults and alarms of the CU_DCP
When faults or alarms are triggered on the drive object of the CU_DCP, it is always assumed
that central functions of the drive unit are involved. For this reason, these faults and alarms
are not only signaled on the drive object of the CU_DCP, but are also forwarded to all other
drive objects. The fault response affects the drive object of the CU_DCP and all other drive
objects. This behavior also applies to the faults set in a DCC chart on the CU_DCP using the
DCB STM.
A fault that is set on the drive object of the CU_DCP must be acknowledged on all drive
objects to which this fault was transferred. In this way, the fault is then automatically
acknowledged on the drive object of the CU_DCP. Alternatively, all faults of all drive objects
can also be acknowledged on the CU_DCP.
If a set alarm is reset on the drive object of the CU_DCP, this alarm also disappears
automatically on the other drive objects to which this alarm was forwarded.
Forwarding faults and alarms as a result of BICO interconnections
If two or more drive objects are connected via BICO interconnections, then faults and alarms
of drive objects, type CU_DCP, TM15 DI/DO, TM31, TM150 are forwarded to type
DCP_CTRL drive objects. Faults are not forwarded within these two groups of drive object
types.
This behavior also applies to the faults set in a DCC chart on the previously named drive
object types using DCB STM.
7.17 CPU time load with SINAMICS DCP
The CPU time load of the SINAMICS DCP is indicated in r9976[1] of the drive object
CU_DCP.
The following rules always apply:
1. The cyclic DC closed-loop control of the SINAMICS DCP generates a base load of
approx. 50 % (r9976[1]).
2. The use of peripherals (STARTER, TM15, TM31, TM150, CBE20,…), certain settings in
the closed loop control and/or use of the free function blocks along with the DCC
technology option increases this base load. The additional CPU time load as a result of
the main components is summarized in the following table.
3. It is not permissible that the CPU time load (r9976[1]) exceeds 100 %.
To Next Page
Loading...
