Rockwell Automation 283D ArmorStart - Getting Started - Manual (Page 19)

Publication 283D-QS001C-EN-P - July 2006
19
Fault LED indications for
Bulletin 283D ArmorStart
Distributed Motor Controllers
Table 8 Controller Fault LED Definitions
Blink
Pattern
Definitions Possible Causes or Remedies
1
Short Circuit The motor circuit protector has tripped, or the internal wiring protection algorithm has detected an unsafe
current range. Try to reset the protector if tripped. If the condition continues, check the power wiring. This
fault cannot be disabled.
2
Overload trip The load has drawn excessive current and based on the trip class selected, the device has tripped. Verify
that the load is operating correctly and the ArmorStart is properly set-up. This fault cannot be disabled.
3
Phase Loss The ArmorStart has detected a missing phase. Verify that three-phase voltage is present at the line side
connections. This fault can be disabled and is disabled by default.
4
Shorted SCR Prior to every start, the unit will check all SCRs for shorts and unit load connections to the motor. If there is
a shorted SCR in the SMC-3 and/or open load, the start will be aborted and a shorted SCR/open load fault
will be indicated. This prevents damage from phase imbalance. This fault cannot be disabled.
5
Phase Rotation When enabled, 3-phase input power will be verified before starting. If input power phasing is detected to
be incorrect, the start will be aborted and a fault indicated. This fault can be disabled and is disabled by
default.
6
Control Power The ArmorStart has detected a loss of the control power voltage. Check control voltage, wiring, and proper
polarity. Also, check and replace the control voltage fuse ,if necessary. This fault can be disabled and is
disabled by default.
7
I/O Fault This error indicates a shorted sensor, shorted input device, wiring input mistakes, or a blown output fuse. If
this fault occurs, the offending problem should be isolated or removed prior to restarting the system. This
fault can be disabled and is disabled by default.
8 Over Temperature This fault is generated when the operating temperature has been exceeded. This fault cannot be disabled.
9
Phase Imbalance The ArmorStart has detected a voltage imbalance. Check the power system and correct if necessary. This
fault can be disabled and is disabled by default.
10
DNet Power Loss DeviceNet power has been lost or has dropped below the 12V threshold. Check the state of the network
power supply and look for DeviceNet media problems. This fault can be disabled and is disabled by default.
11
Internal Communication This fault occurs when communication between the main board and the SMC-3 is lost. This fault cannot be
disabled.
12
Heatsink Over
temperature/JAM This fault indicates either an over temperature fault or a JAM fault. The heatsink is monitored by
thermistors and the SCR temperature is tracked by an algorithm. When a maximum temperature is reached
by either, the microcomputer switches off the SMC and indicates a fault code of 12. A fault code of 12
could also indicate a JAM fault.This fault cannot be disabled.
13
EEPROM Fault This is a major fault, which renders the ArmorStart inoperable. Possible causes of this fault are transients
induced during EEprom storage routines. If the fault was, initiated by a transient, power cycling should
clear the problem otherwise replacement of the ArmorStart may be required. This fault cannot be disabled.
14
Hardware Fault This fault indicates that a serious hardware problem exists. Check for a base/starter module mismatch. If
no mismatch exists, the ArmorStart may need to be replaced. (Hdw Flt is the factory-enabled default
setting.) This fault cannot be disabled.
16 Miscellaneous Fault This fault cannot be disabled.