F_AF High Temperature fault |
Cause:
Drive is too hot inside
Remedy:
- Reduce drive load
- Improve cooling
|
F_AL Assertion Level fault |
Cause:
- Assertion Level switch is changed during operation
- P120 is changed during operation
- P100 or P121…P124 are set to a value other than 0 and P120 does not match the Assertion Level Switch.
Remedy:
Make sure the Assertion Level switch and P120 are both set for the type of input devices being used, prior to setting P100 or P121…P124.
Refer to 3.2.3 and P120.
|
F_bF Personality fault |
Cause:
Drive Hardware
Remedy:
- Cycle Power
- Power down and install EPM with valid data
- Reset the drive back to defaults (P199 = 3, 4) and then re-program
- If problem persists, contact factory technical support
|
F_cF Control fault |
Cause:
An EPM has been installed that is either blank or corrupted
Remedy:
- Power down and install EPM with valid data
- Reset the drive back to defaults (P199 = 3, 4) and then re-program
- If problem persists, contact factory technical support
|
F_cF Incompatible EPM fault |
Cause:
An EPM has been installed that contains data from an incompatible parameter version
Remedy:
If problem persists, contact factory technical support
|
F_dbF Dynamic Braking fault |
Cause:
Dynamic braking resistors are overheating
Remedy:
- Increase active decel time (P105, P126, P127).
- Check mains voltage and P107
|
F_EF External fault |
Cause:
- P121…P124 = 21 and that digital input has been opened.
- P121…P124 = 22 and that digital input has been closed.
Remedy:
- Correct the external fault condition
- Make sure digital input is set properly for NC or NO circuit
|
F_F1 EPM fault |
Cause:
EPM missing or defective
Remedy:
Power down and replace EPM
|
F_F2 … F_F12 Internal faults |
Cause:
Internal faults
Remedy:
Contact factory technical support
|
F_Fnr Control Configuration Fault |
Cause:
- The drive is setup for REMOTE KEYPAD control (P100=2 or 5) but is not setup to communicate with a remote keypad
- The drive is setup for NETWORK ONLY control (P100=3) but is not setup for network communications
Remedy:
- Set P400 = 1, or P600 = 1
- Set P400 or P600 to a valid network communications protocol selection
|
F_FoL Loss of 4-20 mA signal fault |
Cause:
4-20 mA signal (at TB-25) is below 2 mA (P163 = 1)
Remedy:
Check signal/signal wire
|
F_GF OEM Defaults data fault |
Cause:
Drive is powered up with P199 =1 and OEM settings in the EPM are not valid.
Remedy:
Install an EPM containing valid OEM Defaults data or change P199 to 0.
|
F_HF High DC Bus Voltage fault |
Cause:
- Mains voltage is too high
- Decel time is too short, or too much regen from motor
Remedy:
- Check mains voltage and P107
- Increase active decel time (P105, P126, P127) or install Dynamic Braking option
|
F_IL Digital Input Configuration fault (P121…P124) |
Cause:
- More than one digital input set for the same function
- Only one digital input configured for MOP function (Up, Down)
- PID mode is entered with setpoint reference and feedback source set to the same analog signal
- One of the digital inputs (P121…P124) is set to 10 and another is set to 11…14.
- One of the digital inputs (P121…P124) is set to 11 or 12 and another is set to 13 or 14.
- PID enabled in Vector Torque mode (P200 = 1 or 2 and P300 = 5)
Remedy:
- Each setting can only be used once (except settings 0 and 3)
- One input must be set to MOP Up, another must be set to MOP Down
- Change PID setpoint reference (P121…P124) or feedback source (P201).
- Reconfigure digital inputs
- PID cannot be used in Vector Torque mode
|
F_JF Remote keypad fault |
Cause:
Remote keypad disconnected
Remedy:
Check remote keypad connections
|
F_LF Low DC Bus Voltage fault |
Cause:
Mains voltage too low
Remedy:
Check mains voltage
|
F_nId No Motor ID fault |
Cause:
An attempt was made to start the drive in Vector or Enhanced V/Hz mode prior to performing the Motor Auto-calibration
Remedy:
See P300…P399 for Drive Mode setup and calibration.
|
F_ntF Module communication fault |
Cause:
Communication failure between drive and Network Module.
Remedy:
Check module connections
|
F_nF1 … F_nF9 Network Faults |
Cause:
Refer to the module documentation for Causes and Remedies.
Remedy:
Refer to the module documentation.
|
F_OF Output fault: Transistor fault |
Cause:
- Output short circuit
- Acceleration time too short
- Severe motor overload (Mechanical problem, Drive/motor too small)
- Boost values too high
- Excessive capacitive charging current of the motor cable
- Failed output transistor
Remedy:
- Check motor/motor cable
- Increase P104, P125
- Check machine / system
- Verify drive/motor are proper size for application
- Decrease P168, P169
- Use shorter motor cables with lower charging current
- Use low capacitance motor cables
- Install reactor between motor and drive.
- Contact factory technical support
|
F_OF1 Output fault: Ground fault |
Cause:
- Grounded motor phase
- Excessive capacitive charging current of the motor cable
Remedy:
- Check motor and motor cable
- Use shorter motor cables with lower charging current
|
F_PF Motor Overload fault |
Cause:
Excessive motor load for too long
Remedy:
- Verify proper setting of P108
- Verify drive and motor are proper size for application
|
F_rF Flying Restart fault |
Cause:
Controller was unable to synchronize with the motor during restart attempt; (P110 = 5 or 6)
Remedy:
Check motor / load
|
F_SF Single-Phase fault |
Cause:
A mains phase has been lost
Remedy:
Check mains voltage
|
F_UF Start fault |
Cause:
Start command was present when power was applied (P110 = 0 or 2).
Remedy:
- Must wait at least 2 seconds after power-up to apply Start command
- Consider alternate starting method (refer to P110).
|