| Fault Codes | Cause & Solutions |
|---|---|
| FLT S03 – MTR OVERSPEED FL | Cause: Motor Overspeed Factory Limit – Fault Motor speed has exceeded 590 Hz. Solution: – Check control loop tuning. |
| FLT S04 – MTR OVERSPEED UL | Cause: Motor Overspeed User Limit Fault – Motor speed has exceeded the user-defined speed limit that is given by Motor Overspeed User Limit. Solution: – Check control loop tuning. |
| FLT S07 – MTR OVERLOAD FL | Cause: Motor Thermal Overload Factory Limit Fault – The motor thermal model has exceeded its factory set thermal capacity limit of 110%. Solution: – Modify the command profile to reduce speed or increase time. |
| FLT S08 – MTR OVERLOAD UL | Cause: Motor Thermal Overload User Limit Fault. – The motor thermal model has exceeded the thermal capacity limit that is given by Motor Thermal Overload User Limit. Solution: – Modify the command profile. – Increase the Motor Thermal Overload UL attribute value. |
| FLT S10 – INV OVERCURRENT | Cause: Inverter Overcurrent Fault. – Inverter current has exceeded the instantaneous current limit (determined by hardware). Solution: – Check motor power cable for shorts. – Verify that motor windings are not shorted. – Verify motor power wire gauge. – Operate within the continuous power rating. – Reduce acceleration times. |
| FLT S11 – INV OVERTEMP FL | Cause: Inverter Overtemperature Factory Limit Fault. – The measured inverter temperature has exceeded the factory set temperature limit. Solution: – Modify the command profile to reduce speed or increase time. – Reduce drive ambient temperature. – Verify that airflow through drive is not obstructed. |
| FLT S13 – INV OVERLOAD FL | Cause: Inverter Thermal Overload Factory Limit Fault – The thermal model for the power transistors indicates that the temperature has exceeded the factory set thermal capacity rating of 110%. Solution: – Modify the command profile to reduce speed or increase time. |
| FLT S16 – GROUND CURRENT | Cause: Ground Current Factory Limit Fault – The sensing circuitry in the power stage has detected excessive ground current. Solution: – Check motor power wiring; check power cable for shorts. – Replace motor if the fault persists |
| FLT S23 – AC PHASE LOSS | Cause: AC Single Phase Loss Fault. – A single AC input phase was lost while the drive was enabled. Solution: – Check AC input voltage on all phases. |
| FLT S25 – PRECHARGE FAILURE | Cause: Pre-charge Failure Fault – The pre-charge circuit monitoring algorithm detected that the DC bus did not reach a factory set voltage level after charging for a period of time. Solution: – Check AC input voltage on all phases. – Check input power wiring. – Replace drive if fault persists. |
| FLT S29 – BUS OVERLOAD FL | Cause: Bus Regulator Thermal Overload Factory Limit Fault. – The shunt thermal model has exceeded its factory set thermal capacity limit. Solution: – Modify the duty cycle of the application. – Add external shunt for additional capacity. – Add capacitor module if needed. |
| FLT S34 – BUS UNDERVOLT UL | Cause: Bus Undervoltage User Limit Fault – DC Bus voltage level is below the user set limit as given by Bus Undervoltage User Limit. Solution: – Verify voltage level of the incoming AC. – Monitor AC power source for glitches or line droop. – Install UPS on AC input. – Decrease Bus Undervoltage UL attribute value. |
| FLT S35 – BUS OVERVOLT FL | Cause: Bus Overvoltage Factory Limit Fault – DC Bus voltage level is above the factory set limit as determined by the configured input voltage. Solution: – Change the deceleration or motion profile of all drives that are connected to the DC bus. – Unplug the shunt connector and measure the resistance of the shunt. – Replace drive if shunt resistor is open. |
| FLT S37 – BUS POWER LOSS | Cause: Bus Power Loss. – DC Bus voltage level is below the Bus Power Loss Threshold for more than the timeout period specified Bus Power Loss Time value. Solution: – Verify voltage level of the incoming AC. – Monitor AC power source for glitches or line droop. – Install UPS on AC input. |
| FLT S41 – FDBK SIGNAL NOISE FL | Cause: Feedback Signal Noise Fault – Noise induced A/B channel state changes (illegal states) from a feedback device were detected by the drive. – Specifically, the number of these noise events that have occurred on this channel has exceeded the Feedback Noise Factory Limit. – The offending feedback channel number is encoded in the associated Fault/Alarm Sub Code. Solution: – Check motor feedback cable and connector. – Cycle power. – Check feedback shield connection. – Reduce shock and vibration to motor. – Replace motor if fault continues. – Verify all HTL/TTL DIP switches on the 25-ENC-2/B encoder are set in the same position. |
| FLT S43 – FDBK SIG FL | Cause: Feedback Signal Loss Factory Limit Fault – The absolute value of the differential A/B signals is below a factory limit. Solution: – Check motor feedback cable and connector. – Check that motor power cable and feedback wire shields are secured correctly. – Check that motor frame is grounded correctly. |
| FLT S50 – HARDWARE OVERTRAVEL POSITIVE | Cause: Hardware Overtravel Positive – Axis moved beyond the physical travel limits in the positive direction and activated the Positive Overtravel limit switch. Solution: – Check wiring. – Verify motion profile. – Verify axis configuration in software. |
| FLT S51 – HARDWARE OVERTRAVEL NEGATIVE | Cause: Hardware Overtravel Negative – Axis moved beyond the physical travel limits in the negative direction and activated the Negative Overtravel limit switch. Solution: – Check wiring. – Verify motion profile. – Verify axis configuration in software. |
| FLT S54 – POSN ERROR | Cause: Excessive Position Error Fault – The position error of the position control loop has exceeded the value that is given by Position Error Tolerance for a time period that is given by Position Error Tolerance Time. Solution: – Check position loop tuning. – Increase the feedforward gain. – Verify sizing of the drive and motor. – Check motor power wiring. – Increase Position Error Tolerance and/or Position Error Tolerance Time attribute values. |
| FLT S55 – VEL ERROR | Cause: Excessive Velocity Error Fault – The velocity error of the velocity control loop has exceeded the value that is given by Velocity Error Tolerance for a time period that is given by Velocity Error Tolerance Time. Solution: – Check velocity loop tuning. – Reduce acceleration. – Verify sizing of the drive and motor. – Check motor power wiring. – Increase Velocity Error Tolerance and/or Velocity Error Tolerance Time attribute values. |
| FLT S56 – OVERTORQUE LIMIT | Cause: Overtorque Limit Fault – Motor torque has risen above user-defined maximum torque level that is given by Overtorque Limit for a time period that is given by Overtorque Limit Time. Solution: – Verify Torque Trim value. – Verify motion profile. – Verify sizing of the drive and motor. – Increase Overtorque Limit and/or Overtorque Limit Time attribute values. |
| FLT S57 – UNDERTORQUE LIMIT | Cause: Undertorque Limit Fault – Motor torque has dropped below user- defined minimum torque level that is given by Undertorque Limit for a time period that is given by Undertorque Limit Time. Solution: – Verify motion profile. – Verify sizing of the drive and motor. – Decrease Undertorque Limit and/or Undertorque Limit Time attribute values. |
| FLT S61 – ENABLE INPUT DEACTIVATED | Cause: Enable Input Deactivated. – Enable Input has been deactivated while the axis power structure is in Running state, enabled, and supplying current to the DC Bus or motor. Solution: – Verify Enable Input level. – Check Enable Input wiring. |
| FLT M10 – CONTROL MODULE OVER TEMPERATURE FL | Cause: Control Module Overtemperature Fault – The temperature sensor on the Main Control Board detected excessive heat. Solution: – Reduce drive ambient temperature. – Verify that airflow through drive is not obstructed. – Check control module internal fan. Replace if error persists. |
| FLT M19 – DECEL OVERRIDE | Cause: Decel Override. – The drive is not following a commanded deceleration because it is attempting to limit bus voltage. Solution: – Reprogram Bus Regulator Action to eliminate any “Adjustable Freq” selection. – Reprogram Bus Regulator Action to Shunt Regulator and add external shunt. – Correct AC input line instability or add an isolation transformer. – Reset drive. |
| FLT M21 – MOTOR TEST FAILURE | Cause: Motor Test Failure. – The Motor Test procedure has failed. Solution: – Verify sizing of the drive and motor. – Verify motor data. – Check motor power wiring. |
| FLT M26 – RUNTIME ERROR | Cause: Runtime Error. – The drive firmware encountered an unrecoverable runtime error. Solution: – Cycle power. – Reset the drive. – Return drive for repair if fault continues. |
| FLT M28 – SAFETY MODULE COM ERROR | Cause: Safety Module Communication Error – Error in communicating to the Safety module. • Cycle power. Solution: – Replace module. |
| INIT FLT S03 – NVMEM CHKSUM | Cause: Nonvolatile Memory Checksum Error. – Data in the nonvolatile memory has a checksum error. Solution: – Cycle power. – Reset the drive. – Return drive for repair if fault continues. |
| INIT FLT M14 – INVALID SAFETY FIRMWARE | Cause: Invalid Safety Firmware. – The safety firmware is not compatible with the drive firmware, or the main safety firmware is missing. Solution: – Cycle power. – Upgrade drive firmware. – Return drive for repair if fault continues. |
| INIT FLT M15 – POWER BOARD | Cause: Power Board Checksum Error. – The power board has a checksum error. Solution: – Cycle power. – Reset the drive. – Return drive for repair if fault continues. |
| INIT FLT M22 – ILLEGAL ADDRESS | Cause: Illegal IP Address Configuration. – Invalid Ethernet IP Address configuration or device Node Address is out of range (>254) For example, this fault will occur when the IP address and Gateway address are identical. – When this fault occurs, IP address configuration will be changed to DHCP. Solution: – Change IP address, subnet mask, and gateway address to a legal configuration and cycle power. |
| INHIBIT S01 – AXIS ENABLE INPUT | Cause: Axis Enable Input. – Axis Enable Input is not active. Solution: – Verify Enable Input level. – Check Enable Input wiring. |
| INHIBIT S02 – MOTOR NOT CONFIGURED | Cause: Motor Not Configured. – The motor has not been properly configured for use. Solution: – Verify motor configuration in the Studio 5000 Logix Designer application. |
| INHIBIT S05 – SAFE TORQUE OFF | Cause: Start Inhibit – Safe Torque Off. – The safety function has disabled the power structure. Solution: – Check that Ethernet components such as cables are secured and switches are operational. – Check state of safety devices. |
| INHIBIT M05 – SAFE TORQUE OFF | Cause: Start Inhibit – Safe Torque Off. – The safety function has disabled the power structure. Solution: – Check safety input wiring. – Check state of safety devices. |
| NODE FLT 01 – LATE CTRL UPDATE | Cause: Control Connection Update Fault. – Several consecutive updates from the controller have been lost. Solution: – Remove unnecessary network devices from the motion network. – Change network topology so that fewer devices share common paths. – Use high-performance network equipment. – Use shielded cables. – Separate signal wiring from power wiring. |
| NODE FLT 02 – PROC WATCHDOG nn | Cause: Processor Watchdog Fault. – The processor on the power board or control board failed to update in a certain amount of time. – The nn sub-codes 00…05 are internal and result in the same possible solution. Solution: – Cycle power. – Update the drive firmware. – Return drive for repair if fault continues. |
| NODE FLT 03 – HARDWARE 00 | Cause: Hardware Fault – PwrIF – Communication with the power board could not be established. Solution: – Cycle power. – Update the drive firmware. – Return drive for repair if fault continues. |
| NODE FLT 03 – HARDWARE 01 | Cause: Hardware Fault – Piccolo HW – DSP chip on the power board failure. Solution: – Cycle power. – Return motor for repair if fault continues. |
| NODE FLT 05 – CLOCK SKEW FLT | Cause: Clock Skew Fault The controller time and the drive system time are not the same. Solution: – Cycle power. – Check controller and Ethernet switch operation. |
| NODE FLT 06 – LOST CTRL CONN | Cause: Lost Controller Connection Fault – Communication with the controller has been lost. Solution: – Check Ethernet connection. – Check controller and Ethernet switch operation. |
| NODE FLT 07 – CLOCK SYNC | Cause: Clock Sync Fault. – Drive local clock has lost synchronization with controller’s clock and was not able to resynchronize within allotted time. Solution: – Check Ethernet connection. – Check controller and Ethernet switch operation. |
| NODE FLT 09 – DUPLICATE IP ADDRESS | Cause: Duplicate IP Address Fault. – Several consecutive updates from the controller have been lost. Solution: – Select an IP address not already in use on the network. |
| NODE ALARM 01 – LATE CTRL UPDATE | Cause: Control Connection Update Alarm – Updates from the controller have been late. Solution: – Remove unnecessary network devices from the motion network. – Change network topology so that fewer devices share common paths. – Use high-performance network equipment. – Use shielded cables. – Separate signal wiring from power wiring. |
| NODE ALARM 03 – CLOCK JITTER | Cause: Clock Jitter Alarm – The sync variance has exceeded the sync threshold while the device is running in sync mode. Solution: – Check the Ethernet connection. – Check controller and Ethernet switch operation. |
| NODE ALARM 04 – CLOCK SKEW ALARM | Cause: Clock Skew Alarm – The controller time and the drive system time are not the same. Solution: – Check the Ethernet connection. – Check controller and Ethernet switch operation. |
| NODE ALARM 05 – CLOCK SYNC ALARM | Cause: Clock Sync Alarm. – Drive local clock has lost synchronization with controller’s clock for a short time during synchronous operation. Solution: – Check the Ethernet connection. – Check controller and Ethernet switch operation. |