Allen Bradley PowerFlex 750 Drive Fault Codes:
| Fault Codes | Cause & Solutions |
|---|---|
| 2 Auxiliary Input | Cause : Auxiliary input interlock is open. Solution: – Check remote wiring. – Verify communications programming for intentional fault. |
| 3 Power Loss | Cause: Excessive DC Bus voltage ripple. Solution: – Monitor the incoming AC line for low voltage or line power interruption. – Check input fuses. – Reduce load. |
| 4 UnderVoltage | Cause: DC bus voltage fell below the min value. Solution: Monitor the incoming AC line for low voltage or line power interruption. |
| 5 OverVoltage | Cause: DC bus voltage exceeded max value. Solution: – Monitor the AC line for high line voltage or transient conditions. – Bus overvoltage can also be caused by motor regeneration. – Extend the decel time or install dynamic brake option. |
| 7 Motor Overload | Cause: Internal electronic overload trip. Solution: – See P7 [Output Current], P26 [Motor NP Amps, P413 [Mtr OL Factor], and/or P414 [Mtr OL Hertz]. |
| 8 Heatsink OvrTmp | Cause: Heatsink/Power Module temperature exceeds a predefined value. Solution: – Check for blocked or dirty heatsink fins. Verify that ambient temperature has not exceeded the rated ambient temperature. – Check fan. |
| 9 Trnsistr OvrTemp | Cause: Output transistors have exceeded their maximum operating temperature. Solution: – Verify that maximum ambient temperature has not been exceeded. – Check fan. – Check for excessive load. |
| 10 DynBrake | Cause: OvrTempThe dynamic brake resistor has exceeded its maximum operating temperature. Solution: – Check settings of parameters P382 [DB Resistor Type] through P385 [DB ExtPulseWatts]. |
| 12 HW OverCurrent | Cause: The drive output current has exceeded the hardware current limit. Solution: – Check the motor and external wiring to the drive output terminals for a grounded condition. Check the programming. – Check for excess load, and other causes of excess current. Insulation Resistance (IR) test the wiring to motor. |
| 13 Ground Fault | Cause: A current path to earth ground has been detected at one or more of the drive output terminals. Solution: – Check the motor and external wiring to the drive output terminals for a grounded condition. |
| 14 Ground Warning | Cause: The ground current has exceeded the level set in P467 [Ground Warn Lvl]. |
| 15 Load Loss | Cause: he output torque current is below the value programmed in P442 [Load Loss Level] for a time period greater than the time programmed in P443 [Load Loss Time]. Solution: – Check for load loss (i.e., a broken belt). |
| 17 Input Phase Loss | Cause: The DC bus ripple has exceeded a preset level. Make these checks and adjustments in this order. Solution: – Check incoming power for a missing phase or blown fuse. If drive is used intentionally with single phase input, apply output derating to 35% actual drive rating. – Check input impedance balance. – Increase the setting of P463 [InPhase Loss Lvl] to make the drive less sensitive. – Tune the bus regulator or speed regulator to mitigate the effects of dynamic cyclic loads on DC bus ripple. – Disable the fault by setting P462 [InPhase LossActn] to 0 “Ignore” and use an external phase loss detector such as a Bulletin 809S relay. |
| 18 Motor PTC Trip | Cause: Motor PTC (Positive Temperature Coefficient) over temperature. |
| 19 Task Overrun | Cause: System resource utilization is at or above 90 % of capacity. |
| 20 TorqPrv Spd Band | Cause: The difference between P2 [Commanded SpdRef] and P3 [Mtr Vel Fdbk] has exceeded the level programmed in P1105 [Speed Dev Band] for a time period greater than the time programmed in P1106 [SpdBand Intgrtr]. Solution: – Check wiring between drive and motor. – Check release of mechanical brake. |
| 21 Output PhaseLoss | Cause: Current in one or more phases has been lost or remains below a preset level. Solution: – Check the drive and motor wiring. – Check for phase-to-phase continuity at the motor terminals. – Check for disconnected motor leads. |
| 24 Decel Inhibit | Cause: The drive is not following a commanded acceleration or deceleration because it is attempting to limit bus voltage. Solution: – Verify that input voltage is within drive specified limits. – Verify that system ground impedance follows proper grounding techniques. – Disable bus regulation and/or add dynamic brake resistor and/or extend deceleration time. |
| 25 OverSpeed Limit | Cause: Functions such as Slip Compensation or Bus Regulation have attempted to add an output frequency adjustment greater than that programmed in [Overspeed Limit]. – The motor operating speed exceeds the limit set by the maximum speed setting P524 [Overspeed Limit]. For forward motor rotation, this limit is P520 [Max Fwd Speed] + P524 [Overspeed Limit]. For reverse motor rotation, this limit is P521 [Max Rev Speed] – P524 [Overspeed Limit]. When flux vector control modes are selected in P35 [Motor Ctrl Mode], P131 [Active Vel Fdbk] determines the motor operating speed. For all other non-flux vector control modes, P1 [Output Frequency] determines the motor operating speed. Solution: – Remove excessive load or overhauling conditions or increase [Overspeed Limit]. |
| 26 Brake Slipped | Cause & Solution: 1. The encoder movement has exceeded the level in P1110 [Brk Slip Count] after the brake was set and the brake slip maneuver is controlling the drive. (Drive is active.) – Cycle power to the drive to reset. 2. The encoder movement has exceeded the level in P1110 [Brk Slip Count] after the brake was set and the brake slip maneuver is finished. (Drive is stopped.) – Cycle power to the drive to reset. |
| 27 Torq Prove Cflct | When P1100 [Trq Prove Cfg] is enabled, these parameters must be properly configured: • P35 [Motor Ctrl Mode] • P125 [Pri Vel Fdbk Sel] and P135 [Mtr Psn Fdbk Sel] must be set to a valid feedback device. The feedback device does not have to be the same device. However, Open Loop and Simulation Feedback are not considered valid feedback devices. If parameters 125 and 135 are set to a feedback module, verify that the module parameters are set properly. On the module, the feedback loss action CANNOT be set to 0 “Ignore.” Does not work in PM FV mode. Does not work with single ended or channel A only encoders. |
| 28 TP Encls Config | Cause: Encoderless TorqProve has been enabled but the application concerns of encoderless operation have not read and understood. Solution: – Read the “Attention” relating to the use of TorqProve with no encoder. |
| 29 Analog In Loss | Cause: An analog input is configured to fault on signal loss. A signal loss has occurred. Solution: – Check the parameters. – Check for broken/loose connections at inputs. |
| 30 Relay0 Life | Cause: Predictive maintenance. This is a informative warning. |
| 33 Auto Rstrt Tries | Cause: The drive attempted to reset a fault and resume running for the programmed number of tries, unsuccessfully. Solution: – Correct the cause of the fault and manually clear. |
| 34 AutClrFlt Exhaust | Cause: Auto Clear Faults Exhausted. – This fault indicates when the running Auto clear faults retry value has exceeded parameter 338 [AutoClrFlt Tries], provided bit 1 in parameter 347 [Auto Retry Fault] is set. |
| 35 IPM OverCurrent | Cause: The current magnitude has exceeded the trip level set by P1640 [IPM Max Cur]. Set this value to 0 only when the drive is set to the V/Hz or SVC mode. |
| 36 SW OverCurrent | Cause: Drive output current has exceeded the 1 ms current rating. – This rating is greater than the 3-second current rating and less than the hardware overcurrent fault level. – It is typically 200…250% of the drive continuous rating. Solution: – Check for excess load, improper DC boost setting. DC brake volts set too high. – If enabled, check level of flux braking in parameter. |
| 38 Phase U to Gnd | Cause: A phase to ground fault has been detected between the drive and motor in this phase. Solution: – Check the wiring between the drive and motor. – Check motor for grounded phase. – Replace drive if fault cannot be cleared. |
| 39 Phase V to Gnd | Cause: A phase to ground fault has been detected between the drive and motor in this phase. Solution: – Check the wiring between the drive and motor. – Check motor for grounded phase. – Replace drive if fault cannot be cleared. |
| 40 Phase W to Gnd | Cause: A phase to ground fault has been detected between the drive and motor in this phase. Solution: – Check the wiring between the drive and motor. – Check motor for grounded phase. – Replace drive if fault cannot be cleared. |
| 41 Phase UV Short | Cause: Excessive current has been detected between these two output terminals. Solution: – Check the motor and drive output terminal wiring for a shorted condition. – Replace drive if fault cannot be cleared. |
| 42 Phase UW Short | Cause: Excessive current has been detected between these two output terminals. Solution: – Check the motor and drive output terminal wiring for a shorted condition. – Replace drive if fault cannot be cleared. |
| 43 Phase VW Short | Cause: Excessive current has been detected between these two output terminals. Solution: – Check the motor and drive output terminal wiring for a shorted condition. – Replace drive if fault cannot be cleared. |
| 48 System Defaulted | Cause: The drive was commanded to write default values to EEPROM. Solution: – Clear the fault or cycle power to the drive. – Program the drive parameters as needed. |
| F49 Drive Powerup | No fault is displayed. Used as a Powe r Up Marker in the Fault Queue indicating that the drive power has been cycled. |
| 51 Flt QueueCleared | No fault displayed. Used as a marker in the Fault Queue indicating that the clear queue function was performed. |
| 55 Cntl Bd Overtemp | Cause: The temperature sensor on the Main Control Board detected excessive heat. Solution: – Check Main Control Board fan. – Check surrounding air temperature. – Verify proper mounting/ cooling. |
| 58 Module Defaulted | Cause: The module was commanded to write default values. |
| 59 Invalid Code | Cause: Internal error. Solution: There is an hardware or software issue in drive. Need to repair or replace drive. |
| 61 Shear Pin 1 | Cause: The programmed value in P436 [Shear Pin1 Level] has been exceeded. |
| 62 Shear Pin 2 | Cause: The programmed value in P439 [Shear Pin2 Level] has been exceeded. |
| 64 Drive Overload | Cause: 1. P940 [Drive OL Count] has exceeded 50 % but is less than 100 %. 2. P940 [Drive OL Count] has exceeded 100 %. – Reduce the mechanical load on the drive. 3. Inverter fiber-optic connection is not detected on Frame 8 drive. – This fault can occur on power-up if the control detects that no inverter is detected via the fiber-optic communication on a Frame 8 drive. Solution: – Reduce load or extend Accel Time. – Reduce the mechanical load on the drive |
| 66 OW Torq Level | Cause: Oil Well Torque Level. – If the Torque goes above P1172 [TorqAlarm Level], then the alarm condition exists. |
| 67 Pump Off | Pump Off condition has been detected. |
| 68 OW Torq Level Lo | Cause: Oil Well Torque Level Low. – If the Torque goes below P1185 [TorqAlarm LoLvl], then the alarm condition exists. |
| 71 Port 1 Adapter | Cause: The communications card has a fault. Solution: – Check DPI device event queue and corresponding fault information for the device. |
| 72 Port 2 Adapter | Cause: The communications card has a fault. Solution: – Check DPI device event queue and corresponding fault information for the device. |
| 73 Port 3 Adapter | Cause: The communications card has a fault. Solution: – Check DPI device event queue and corresponding fault information for the device. |
| 74 Port 4 Adapter | Cause: The communications card has a fault. Solution: – Check DPI device event queue and corresponding fault information for the device. |
| 75 Port 5 Adapter | Cause: The communications card has a fault. Solution: – Check DPI device event queue and corresponding fault information for the device. |
| 76 Port 6 Adapter | Cause: The communications card has a fault. Solution: – Check DPI device event queue and corresponding fault information for the device. |
| 77 IR Volts Range | Cause: The value for P73 [IR Voltage Drop], which is calculated from the motor nameplate data, is not within the range of acceptable values, as determined by the Calculated Autotune procedure. Solution: – Check the motor nameplate data against parameters P25 [Motor NP Volts] through P30 [Motor NP Power]. |
| 78 FluxAmpsRef Rang | Cause: The value for flux amps determined by the Autotune procedure exceeds the programmed [Motor NP FLA]. Solution: – Reprogram [Motor NP FLA] with the correct motor nameplate value. – Repeat Autotune. |
| 79 Excessive Load | Cause: Motor did not come up to speed in the allotted time during autotune. Solution: – Uncouple load from motor. – Repeat Autotune. |
| 80 AutoTune Aborted | Cause: Autotune function was canceled by the user or a fault occurred. Solution: – Restart the procedure. |
| 81 Port 1 DPI Loss | Cause: – DPI port stopped communicating. Solution: – If adapter was not intentionally disconnected, check wiring to the port. Replace wiring, port expander, adapters, Main Control Board, or complete drive as required. – Check connections and drive grounding. |
| 82 Port 2 DPI Loss | Cause: – DPI port stopped communicating. Solution: – If adapter was not intentionally disconnected, check wiring to the port. Replace wiring, port expander, adapters, Main Control Board, or complete drive as required. – Check connections and drive grounding. |
| 83 Port 3 DPI Loss | Cause: – DPI port stopped communicating. Solution: – If adapter was not intentionally disconnected, check wiring to the port. Replace wiring, port expander, adapters, Main Control Board, or complete drive as required. – Check connections and drive grounding. |
| 84 Port 4 DPI Loss | Cause: – DPI port stopped communicating. Solution: – If adapter was not intentionally disconnected, check wiring to the port. Replace wiring, port expander, adapters, Main Control Board, or complete drive as required. – Check connections and drive grounding. |
| 85 Port 5 DPI Loss | Cause: – DPI port stopped communicating. Solution: – If adapter was not intentionally disconnected, check wiring to the port. Replace wiring, port expander, adapters, Main Control Board, or complete drive as required. – Check connections and drive grounding. |
| 86 Port 6 DPI Loss | Cause: – DPI port stopped communicating. Solution: – If adapter was not intentionally disconnected, check wiring to the port. Replace wiring, port expander, adapters, Main Control Board, or complete drive as required. – Check connections and drive grounding. |
| 87 IXo VoltageRange | Cause: -The default for P70 [Autotune] is 1 “Calculate” and the voltage that is calculated for motor inductive impedance exceeds 25 % of the value of P25 [Motor NP Volts]. – P70 [Autotune] is set to 2 “Static Tune” or 3 “Rotate Tune” and the voltage that is measured for motor inductive impedance exceeds 25 % of the value of P25 [Motor NP Volts]. Solution: – Check for proper motor sizing. – Check for correct programming of [Motor NP Volts], parameter 41. – Additional output impedance can be required. |
| 91 Pri VelFdbk Loss | A Feedback Loss has been detected for the source of P127 [Pri Vel Feedback]. The feedback loss could be due to a problem detected by the feedback option module selected by P125 [Pri Vel Fdbk Sel] or due to a loss in communication between the feedback option module and main control board. The source of primary velocity feedback must be configured not to fault if the feedback loss switchover feature is used. |
| 93 Hw Enable | Check The hardware enable is disabled (a jumper is installed) but indicates not enabled. |
| 94 Alt VelFdbk Loss | A Feedback Loss has been detected for the source of P128 [Alt Vel Fdbk Sel]. The feedback loss could be due to a problem detected by the feedback option module selected by P128 [Alt Vel Fdbk Sel], or due to a loss in communication between the feedback option module and main control board. |
| 95 Aux VelFdbk Loss | A Feedback Loss has been detected for the source of P132 [Aux Vel Fdbk Sel]. The feedback loss could be due to a problem detected by the feedback option module selected by P132 [Aux Vel Fdbk Sel], or due to a loss in communication between the feedback option module and main control board. |
| 96 Position FdbkLoss | A Feedback Loss has been detected for the source of P847 [Psn Fdbk]. The feedback loss could be due to a problem detected by the feedback option module selected by P135 [Mtr Psn Fdbk Sel], or due to a loss in communication between the feedback option module and main control board. |
| 97 Auto Tach | Switch Indication that either of the two following conditions exists. – Tach switch has occurred and alternate feedback device has failed. – Tach switch has not occurred, Auto Tach Switch Option is enabled and both primary and alternate devices have failed. |
| 100 Parameter Chksum | Cause: The checksum read from the board does not match the checksum calculated. Solution: – Restore defaults. – Reload User Set if used. |
| 101 PwrDn NVS Blank | Cause: Internal data error. – Reset parameter defaults. See publication 20HIM-UM001 for instructions. – Reload parameters. – If problem persists, replace main control board. Fault normally occurs after a flash update to correct F117 fault. |
| 102 NVS Not Blank | Cause: Internal data error. Solution: There is an harware or software issue in drive. Need to repair or replace drive. |
| 103 PwrDn NVS Incomp | Cause: Internal data error. Solution: There is an harware or software issue in drive. Need to repair or replace drive. |
| 104 Pwr Brd Checksum | Cause: The checksum read from the non-volatile storage does not match the checksum calculated. The data is set to the default value. Solution: – Clear the fault or cycle power to the drive. |
| 106 Incompact MCB-PB | Cause: The main control board did not recognize the power structure. Flash with newer Application revision. Solution: Load compatible version files into drive. |
| 107 Replaced MCB-PB | Cause: The main control board was moved to another power structure. The data is set to the default values. Solution: – Restore defaults. – Reprogram parameters. |
| 108 Anlg Cal Chksum | Cause: The checksum read from the analog calibration data does not match the checksum that is calculated. Solution: – Replace the drive. |
| 110 Ivld Pwr Bd Data | Cause: Power structure data invalid. Solution: – Verify ribbon cable connection between the main control board and the power interface board. – Replace power interface board. |
| 111 PwrBd Invalid ID | Cause: Power structure ID invalid. Solution: – Verify ribbon cable connection between the main control board and the power interface board. – Replace power interface board. |
| 112 PwrBd App MinVer | Cause: Power structure needs newer Application revision. Solution: – Flash with newer Application revision. |
| 113 Tracking DataErr | Cause: Internal data error. Solution: There is an hardware or software issue in drive. Need to repair or replace drive. |
| 115 PwrDn Table Full | Cause: Internal data error. Solution: There is an hardware or software issue in drive. Need to repair or replace drive. |
| 116 PwrDn Entry2La rge | Cause: Internal data error. Solution: There is an hardware or software issue in drive. Need to repair or replace drive. |
| 117 PwrDn Data Chksm | Cause: Internal data error. Solution: There is an hardware or software issue in drive. Need to repair or replace drive. |
| 118 PwrBd PwrDn Chks | Cause: Internal data error. Solution: There is an hardware or software issue in drive. Need to repair or replace drive. |
| 124 App ID Changed | Cause: Application Firmware changed. Solution: Verify Application revision. |
| 125 Using Backup App | Cause: Application did not flash correctly. Solution: Reflash. |
| 134 Start On PowerUp | When P345 [Start At PowerUp] is enabled, an alarm is set for the time programmed in P346 [PowerUp Delay]. |
| 137 Ext Prechrg Err | The seal contact on the external precharge contactor has opened (as signaled by P190 [DI Prchrg Seal]) while the drive was running (PWM was active). |
| 138 Precharge Open | The internal precharge was commanded to open while the drive was running (PWM was active). The internal fault latch is automatically cleared when PWM is disabled. |
| 141 Autn Enc Angle | P78 [Encdrlss AngComp] is out of range. |
| 142 Autn Spd Rstrct | Frequency limit settings are preventing the drive from reaching a suitable speed during an Inertia Tune test. |
| 143 Autotune CurReg | Calculated values for P96 [VCL Cur Reg Kp] and/or P97 [VCL Cur Reg Ki] are out of range. |
| 144 Autotune Inertia | Results from the Inertia Tune test out of range for P76 [Total Inertia]. |
| 145 Autotune Travel | When P77 [Inertia Test Lmt] is set, the Inertia Tune test was prevented from reaching a suitable speed to run the test. |
| 152 No Stop Source | Last stop source has been removed. |
| 155 Bipolar Conflict | P308 [Direction Mode] is set to 1 “Bipolar” or 2 “Rev Disable” and one or more digital inputs is enabled for direction control. |