Siemens sinamics dcp, Руководство пользователя

Страница: 424 / 518

4 Faults and alarms
4.2 List of faults and alarms
SINAMICS DCP
424
List Manual (LH21), 05/2016
Example 2:
BICO output with voltage normalized unit in drive object 1 (DO1), BICO input with voltage normalized unit in drive
object 2 (DO2). The reference values for voltage (p2001) of the two drive objects have different values. This means
that the factor p2001(DO1)/p2001(DO2) is calculated between the BICO output and the BICO input.
p2001: contains the reference value for voltage, drive objects 1, 2
Fault value (r0949, interpret decimal):
Parameter number of the BICO input (signal sink).
Remedy: Not necessary.
A01514 (F) BICO: Error when writing during a reconnect
Drive object: All objects
Cause: During a reconnect operation (e.g. while booting or downloading - but can also occur in normal operation) a
parameter was not able to be written to.
Example:
When writing to BICO input with double word format (DWORD), in the second index, the memory areas overlap (e.g.
p8861). The parameter is then reset to the factory setting.
Alarm value (r2124, interpret decimal):
Parameter number of the BICO input (signal sink).
Remedy: Not necessary.
F01515 (A) BICO: Writing to parameter not permitted as the master control is active
Drive object: DCP_CTRL
Cause: When changing the number of CDS or when copying from CDS, the master control is active.
Remedy: If required, return the master control and repeat the operation.
A01590 (F) Drive: Motor maintenance interval expired
Drive object: CU_DCP, TM150, TM15DI_DO, TM31
Cause: The selected service/maintenance interval for this motor was reached.
Alarm value (r2124, interpret decimal):
Motor data set number.
Remedy: carry out service/maintenance and reset the service/maintenance interval (p0651).
F01800 DRIVE-CLiQ: Hardware/configuration error
Drive object: All objects
Cause: A DRIVE-CLiQ connection fault has occurred.
Fault value (r0949, interpret decimal):
100 ... 107:
Communication via DRIVE-CLiQ socket X100 ... X107 has not been switched to cyclic operation. The cause may be
an incorrect structure or a configuration that results in an impossible bus timing.
10:
Loss of the DRIVE-CLiQ connection. The cause may be, for example, that the DRIVE-CLiQ cable was withdrawn
from the Control Unit or as a result of a short-circuit for motors with DRIVE-CLiQ. This fault can only be
acknowledged in cyclic communication.
11:
Repeated faults when detecting the connection. This fault can only be acknowledged in cyclic communication.
12:
A connection was detected but the node ID exchange mechanism does not function. The reason is probably that the
component is defective. This fault can only be acknowledged in cyclic communication.
Remedy: Re fault value = 100 ... 107:
- ensure that the DRIVE-CLiQ components have the same firmware versions.
- avoid longer topologies for short current controller clock cycles.
For fault value = 10:
- check the DRIVE-CLiQ cables at the Control Unit.
- remove any short-circuit for motors with DRIVE-CLiQ.
- carry out a POWER ON.
For fault value = 11:
- check the electrical cabinet design and cable routing for EMC compliance