ITT PumpSmart PS220, Руководство по конфигурации и эксплуатации

Страница: 256 / 300

PS220 Configuration & Operation Guide
255 PS220
Fault T
racing
CODE
(HEX)
WARNING CAUSE WHAT TO DO
A4A1 IGBT over temperature Estimated drive IGBT
temperature is excessive.
• Check ambient conditions. Check air flow and fan
operation.
• Check heatsink fins for dust pick-up. Check motor power against
drive power.
A580 PU communication Communication errors detected
between the drive control unit
and the power unit.
• Check the connections between the drive control unit and the
power unit.
• Check the auxiliary code (format XXXY YYZZ). With parallel-
connected modules, “Y YY” specifies the affected BCU control
unit channel (0: broadcast). “ZZ” specifies the error source
• Check fan operation and connection. Replace fan if faulty.
• The auxiliary code identifies the fan (1: Auxiliary fan 1, 2: Auxiliary
fan 2). Check auxiliary fan(s) and connection(s). Replace faulty
fan.
• Make sure the front cover of the drive module is in place and
tightened. If the commissioning of the drive requires that the cover
is off, this warning will be generated even
if the corresponding fault is defeated.
Replace Drive cover is necessary.
A581 Fan Cooling fan feedback missing.
A582 Auxiliary fan missing An auxiliary cooling fan
(connected to the fan
connectors on the control unit)
is stuck or disconnected.
A5A0 Safe torque off
Programmable warning:
31.22 STO indication run/
stop
Safe torque off function is
active, i.e. safety circuit
signal(s) connected to
connector XSTO is lost.
• Check safety circuit connections. For more information, see
appropriate drive hardware manual.
A6A5 No motor data Parameters in group 99 have not
been set.
• Check that all the required parameters in group 99 have been
set.
• Note: It is normal for this warning to appear during the
start-up and continue until the motor data is entered.
A6A6 Supply voltage unselected The supply voltage has not been
defined.
• Set supply voltage in parameter 95.01 Supply voltage.
A6D1 FBA A parameter conflict The drive does not have a
functionality requested by a
PLC, or requested functionality
has not been activated.
• Check PLC programming.
• Check settings of parameter groups 50 Fieldbus adapter (FBA)
and 54 FBA B settings.
A6D2 FBA B parameter conflict The drive does not have a
functionality requested by a PLC
or requested functionality has
not been activated.
• Check PLC programming.
• Check settings of parameter groups 50 Fieldbus adapter (FBA)
and 54 FBA B settings.
A6E5 AI parametrization
The current/voltage hardware
setting of an analog input
does not correspond to
parameter settings.
• Check the auxiliary code. The code identifies the analog input
whose settings are in conflict.
• Adjust either the hardware setting (on the drive control unit) or
parameter 12.15/12.25.
• Note: Control board reboot (either by cycling the power or
through parameter
• 96.08 Control board boot) is required to validate any
changes in the hardware settings.
A780 Motor stall
Programmable
warning:
31.24 Stall function
Motor is operating in stall region
because of e.g. excessive load
or insufficient motor power.
• Check motor load and drive ratings. Check fault function
parameters.
A7AA Extension AI
parameterization
The hardware current/voltage
setting of an analog input (on
an I/O extension module) does
not correspond to parameter
settings.
• Adjust either the hardware setting on the module or the
parameter to solve the mismatch.
• Note: Control board reboot (either by cycling the power or
through parameter 96.08 Control board boot) is required to
validate any changes in the hardware
settings.
A7C1 FBA A communication
Programmable warning:
50.02 FBA A Comm loss
function
Cyclical communication
between drive and fieldbus
adapter module A or between
PLC and fieldbus adapter
module A is lost.
• Check status of fieldbus communication. See user
documentation of fieldbus interface.
• Check cable connections.
• Check if communication master is able to communicate.
Each warning message on the keypad displays the warning name as well as and
unique code. The messages are listed in the ascending order of their fault codes.