Rockwell Automation 294D ArmorStart LT Distributed Motor Controller DeviceNet Version - User Manual - Manual (Page 172)

172 Rockwell Automation Publication 290D-UM001A-EN-P - June 2012
Chapter 5 Diagnostics
Bulletin 294D Faults Bulletin 294E faults are detected by the main control board and/or the internal
drive. When there is an internal drive fault, the main control board simply polls
the drive for the existence of faults and reports the fault state. Writing a value to
[ProtFltResetMode] Parameter 41 determines auto-reset ability for some faults.
The auto-reset ability of faults that are generated on the drive are controlled by
[AutoRestartTries] Parameter 84 and [AutoRestar Delay] Parameter 85.
Auto Reset
Table 25 - Auto Reset Ability
Auto Reset Function Description
Drive Control Auto-Reset/Run When this type of fault occurs, and [AutoRestartTries] Parameter 84 is set to a value greater than “0,” a user-configurable timer,
[AutoRestartDelay] Parameter 85, begins. When the timer reaches zero, the drive attempts to automatically reset the fault. If the
condition that caused the fault is no longer present, the fault will be reset and the drive will be restarted.
No User Action Needed This type of fault requires drive or motor repair, or is caused by wiring or programing errors. The cause of the fault must be
corrected before the fault can be cleared via manual or network reset. A rising edge of the “Fault Reset” DeviceLogix bit will also
clear the fault.
Yes [ProtFltResetMode]
Parameter 41 = 1 which
is automatic Faults are cleared automatically when the fault condition goes away.
Table 26 - Fault LED Indicator for Bulletin 294D
Blink
Pattern
Auto-Reset
Capable Disable Default
Bulletin 294E
Trip Status Description Action
1 Drive
Controlled
No On Overload Trip
(PF 4M Codes 7 and
64) This fault is a result of the drive’s Motor
Overload fault or the Drive Overload fault.
Exceeding the Drive overload rating of
150% for 1 minute or 200% for 3 seconds
caused the device to trip. The fault may be reset only after the overload
algorithm determines that the motor has sufficiently
cooled or that the Drive heatsink temperature falls to
an acceptable level. Check the following:
1. Excessive motor load. Reduce load so drive output
current does not exceed the current set by
[MotorOLCurrent] Parameter 30.
2. Verify [BoostSelect] Parameter 86 setting.
2 No No On Phase Short
(PF 4M Codes
38…43) This fault is a result of the drive’s Phase to
Ground Short faults (Codes 38…40) or
Phase to Phase Short faults (Codes
41…43). 1. Check the wiring between the drive and motor.
2. Check motor for grounded phase.
3. Replace ArmorStart LT if fault cannot be cleared.
3 Yes No On Under Power Trip The ArmorStart LT detected switched or
unswitched power dip below 19.2 V for
greater than 50 ms, or 13 V for greater
than 4 ms. Check control voltage, wiring, and proper polarity (A1/
A2 terminal). Correct power loss or disable fault using
[ProtectFltEnable] Parameter 42.
4 No No On Sensor Short Trip This error indicates a shorted sensor,
shorted input device, wiring input
mistakes. Correct, isolated or remove wiring error prior to
restarting the system.
5 Drive
Controlled
No On Over Current
(PF 4M Codes 12 and
63) This fault is a result of the drive’s HW
OverCurrent fault or it’s SW OverCurrent
fault. 1. Check for excess load, improper [BoostSelect]
Parameter 86 setting or other causes of excess
current or
2. Check load requirements and [SWCurrentTrip]
Parameter 83 setting.
6 No No On Non-Volatile Memory
Trip
(PF 4M Code 100) This is a major fault, which renders the
ArmorStart LT inoperable. Possible causes
of this fault are transients induced during
Non-Volatile Storage (NVS) routines. 1. If the fault was initiated by a transient, power
cycling may clear the problem.
2. This fault may be reset by a [SetToDefaults]
Parameter 68.
3. Replacement of the ArmorStart LT may be required.