Yaskawa iQPump Micro Drive

Fault Code and MeaningCause and Remedy
AJF
Anti-Jam Fault

Cause: The drive was not able to clear debris from the impeller in fewer than the number of attempts set in P7-02.



Remedy:

  • Check for proper pump operation. Remove debris from the pump impeller.

  • Adjust the P7-03 level or the P7-02 counts.

  • Drive response to this condition is controlled by P7-01 (Anti-jam Operation Selection).


bUS
Option Communication Error

Cause: The connection was lost after establishing initial communication. Only detected when run command is assigned to option card.



Remedy:

  • Check for faulty wiring, disconnected cables, or short circuits.

  • Counteract noise in control/main circuits and ground wiring.

  • Use surge absorbers on other equipment (switches/relays).

  • Use shielded lines and ground correctly.

  • Separate communication wiring from power lines. Install EMC filter.

  • Replace the option card if damaged.

  • Ensure option card connector pins allow proper alignment; reinstall card.


CE
MEMOBUS/Modbus Communication Error

Cause: Control data was not received for the CE detection time set to H5-09.



Remedy:

  • Check for faulty wiring, disconnected cables, or short circuits.

  • Counteract noise in control/main circuits and ground wiring.

  • Use shielded lines and ground correctly.

  • Use surge suppressors on switches/relays if required.

  • Separate communication wiring from drive power lines. Install EMC filter.


CPF02
A/D Conversion Error

Cause: Control circuit is damaged.



Remedy:

  • Cycle power to the drive.

  • If the problem continues, replace the drive.


N/A
Control circuit terminals shorted / Input current exceeded

Cause: Control circuit terminals have shorted out (+V, AC) or input current exceeded allowable levels.



Remedy:

  • Check for wiring errors along the control circuit terminals.

  • Correct the wiring.

  • Check input current; reduce current input to control terminal (+V) to 20 mA.


CPF03
PWM Data Error

Cause: Hardware is damaged (Problem with PWM data).



Remedy:

  • Replace the drive.


CPF06
EEPROM Memory Data Error

Cause: Error in the data saved to EEPROM. (e.g., Power supply switched off while saving).



Remedy:

  • Turn off the power and check the connection between the control board and the drive.

  • If the problem continues, replace the drive.

  • Reinitialize the drive (A1-03 = 2220, 3330).


CPF07
Terminal Board Communications Error

Cause: There is a faulty connection between the terminal board and the control board.



Remedy:

  • Turn off the power and reconnect the control circuit terminals.


CPF08
EEPROM Serial Communication Fault

Cause: Terminal board or control board is not connected properly.



Remedy:

  • Turn the power off and check the control terminal connections.

  • Turn off the power and reconnect the control circuit terminals.


CPF11
RAM Fault

Cause: Hardware is damaged.



Remedy:

  • Replace the drive.


CPF12
FLASH Memory Fault

Cause: Hardware is damaged (Problem with ROM/FLASH memory).



Remedy:

  • Replace the drive.


CPF13
Watchdog Circuit Exception

Cause: Hardware is damaged (Self-diagnostics problem).



Remedy:

  • Replace the drive.


CPF14
Control Circuit Fault

Cause: Hardware is damaged (CPU error due to noise, etc).



Remedy:

  • Replace the drive.


CPF16
Clock Fault

Cause: Hardware is damaged (Standard clock error).



Remedy:

  • Replace the drive.


CPF17
Timing Fault

Cause: Hardware is damaged (Timing error during internal process).



Remedy:

  • Replace the drive.


CPF18
Control Circuit Fault

Cause: Hardware is damaged (Non-Maskable Interrupt triggered by noise).



Remedy:

  • Replace the drive.


CPF19
Control Circuit Fault

Cause: Hardware is damaged (CPU error, manual reset due to noise).



Remedy:

  • Replace the drive.


CPF20 or CPF21
RAM/FLASH/Watchdog/Clock Error

Cause: Hardware is damaged (RAM, FLASH, Watchdog, or Clock error).



Remedy:

  • Replace the drive.


CPF22
A/D Conversion Fault

Cause: Control circuit is damaged.



Remedy:

  • Cycle power to the drive.

  • If the problem continues, replace the drive.


CPF23
PWM Feedback Fault

Cause: Hardware is damaged.



Remedy:

  • Replace the drive.


CPF24
Drive Unit Signal Fault

Cause: Hardware is damaged (Drive capacity cannot be detected correctly).



Remedy:

  • Replace the drive.


CPF25
Terminal Board Not Connected

Cause: Terminal board is not connected correctly.



Remedy:

  • Reconnect the terminal board to the connector on the drive, then cycle the power to the drive.


CPF26 to CPF35
CPF40 to CPF43
Control Circuit Error / CPU Error

Cause: Hardware is damaged.



Remedy:

  • Replace the drive.


E5
SI-T3 Watchdog Timer Error

Cause: Data has not been received from the PLC.



Remedy:

  • Execute DISCONNECT or ALM_CLR.

  • Issue a CONNECT command or SYNC_SET command and proceed to phase 3.

  • Refer to the SI-T3 Option Technical Manual for more details.


EF0
Option Card External Fault

Cause: An external fault was received from the PLC and F6-03 is set to a value other than 3. Problem with PLC program.



Remedy:

  • Remove the cause of the external fault.

  • Remove the external fault input from the PLC.

  • Check the PLC program and correct problems.


EF1 to EF7
Pump Fault (External Faults S1-S7)

Cause: An external device tripped an alarm function. Wiring is incorrect.



Remedy:

  • Remove the cause of the external fault and reset the fault.

  • Properly connect the signal lines to the terminals assigned for external fault detection (H1-xx = 20 to 2F).

  • Reconnect the signal line.


Err
EEPROM Write Error

Cause: Noise has corrupted data while writing to EEPROM or Hardware problem.



Remedy:

  • Press “ENTER” on the digital operator.

  • Correct the parameter setting.

  • Cycle power to the drive.

  • If the problem continues, replace the drive.


FAn
Internal Cooling Fan Failure

Cause: Internal cooling fan has malfunctioned.



Remedy:

  • Cycle power to the drive.

  • Check for fan operation.

  • If the problem continues, replace the fan.


Fdb-L
PID Feedback Loss

Cause: Analog input programmed for PID feedback dropped below or rose above limits (3mA / 21mA).



Remedy:

  • Confirm that the PID feedback source is installed and working properly.

  • Drive response is controlled by b5-12 and b5-13.

  • Auto-restart is controlled by L5-42.


GF
Ground Fault

Cause: Motor insulation damaged, cable short circuit, or excessive leakage current.



Remedy:

  • Check the insulation resistance of the motor. Replace motor if needed.

  • Check motor cable for shorts. Check resistance between cable and ground. Replace cable if needed.

  • Reduce carrier frequency.

  • Reduce stray capacitance.

  • Enable Speed Search (Set b3-01 to 1) if fault occurs during coasting.

  • If hardware problem, replace the drive.


Err
EEPROM Write Error

Cause: Noise has corrupted data while writing to the EEPROM.



Remedy:

  • Press “ENTER” on the digital operator.

  • Correct the parameter setting.

  • Cycle power to the drive.

  • If the problem continues, replace the drive.


FAn
Internal Cooling Fan Failure

Cause: Internal cooling fan has malfunctioned.



Remedy:

  • Cycle power to the drive.

  • Check for fan operation.

  • If the problem continues, replace the fan.


Fdb-L / FDBKL
PID Feedback Loss

Cause: The analog input programmed for PID feedback has risen above 21 mA or fallen below 3 mA (effective only when b5-12 is set to 2).



Remedy:

  • Confirm that the PID feedback source is installed and working properly.

  • Check settings b5-12 (Detection Selection) and b5-13 (Go To Frequency).

  • Check L5-42 for Auto-restart settings.


GF
Ground Fault

Cause: Motor insulation is damaged, cable is damaged causing a short, excessive leakage current, or drive started during current offset/coasting.



Remedy:

  • Check the insulation resistance of the motor and replace if damaged.

  • Check motor cable for shorts and resistance; replace if necessary.

  • Reduce carrier frequency or stray capacitance.

  • Set b3-01 to 1 to enable Speed Search at Start.

  • If Hardware problem persists, replace the drive.


HFb / HFB
High Feedback

Cause: The feedback signal has risen above the level set in P1-11 for the time set in P1-12.



Remedy:

  • Set the High Feedback fault characteristics in P1-11 and P1-12.

  • Check Drive response settings in P1-13.

  • Check Auto-restart settings in L5-41.


HWL (H1H20)
High Water Level

Cause: The “High Water Level” digital input is active (H1-xx = 90), or switch is programmed incorrectly.



Remedy:

  • Lower the water level.

  • Adjust the High Water Level switch.

  • Check P1-31 configuration.


LF
Output Phase Loss

Cause: Output cable disconnected, motor winding damaged, loose terminals, motor rated current too low (<5%), or damaged transistor.



Remedy:

  • Check wiring and properly connect output cable.

  • Check resistance between motor lines; replace motor if winding damaged.

  • Tighten terminals to specified torque.

  • Check drive and motor capacities.

  • Ensure a single-phase motor is not being used.

  • If problem continues, replace the drive.


LF2
Output current imbalance

Cause: Phase loss on output side, loose terminal wires, or uneven motor impedance.



Remedy:

  • Check for faulty wiring or poor connections on the output side.

  • Tighten terminals to specified torque.

  • Measure line-to-line resistance for each motor phase (ensure values are equal).

  • Replace the motor or contact Yaskawa if drive is faulty.


LFb / LFB
Low Feedback

Cause: Feedback signal dropped below level set in P1-08 for time set in P1-09.



Remedy:

  • Set Low Feedback fault characteristics in P1-08 and P1-09.

  • Check response settings in P1-10.

  • Check Auto-restart settings in L5-40.


LoP / LOP
Loss of Prime

Cause: Pump load (current/power) dropped below P1-19 level for time P1-20.



Remedy:

  • Check for dry well, air in system, or no water. Restart using preferred priming method.

  • Set Loss of Prime characteristics in P1-18 through P1-21.

  • Check Auto-restart settings in L5-51 and P1-23.


LoH20 / LWL
Low Water Level

Cause: The “Low Water Level” digital input is active, switch defective, or programmed incorrectly.



Remedy:

  • Raise the water level.

  • Adjust the Low Water Level switch.

  • Check P1-30 configuration.


n5L / MSL
Net Master Lost

Cause: MEMOBUS master has been lost or timeout occurred.



Remedy:

  • Increase P9-26 setting to account for network latency.

  • Verify drive exists on network (P1-01 set to 3).

  • Check network connections and H5-01/P9-25 settings.


not5P / NMS
Not Maintaining Setpoint

Cause: Feedback deviates from setpoint > P1-15 for time P1-16.



Remedy:

  • Check for blocked impeller, over cycling, or broken pipe.

  • Set fault characteristics in P1-16 and P1-17.

  • Check Auto-restart settings in L5-50.


n5E / nSE
Node Setup Error

Cause: A terminal assigned to the node setup function closed during run.



Remedy:

  • Stop the drive when using the node setup function.


oC
Overcurrent

Cause: Motor overheated/insulation damaged, short circuit, heavy load, accel/decel time too short, incorrect V/f setting, or hardware issue.



Remedy:

  • Check insulation resistance and motor cables.

  • Measure current; replace with larger capacity drive if needed.

  • Increase acceleration time (C1-01, C1-03).

  • Check voltage/frequency ratios and E1-04 settings.

  • Reduce torque compensation gain (C4-01).

  • Set b3-01 to 1 to enable Speed Search at Start.


oFA00
Option Card Connection Error

Cause: The option card installed into port CN5 is incompatible.



Remedy:

  • Check if the drive supports the option card to be installed.

  • Contact Yaskawa for assistance.


oFA01
Option Card Fault

Cause: The option card connection to port CN5 is faulty.



Remedy:

  • Turn off power and reconnect the option card.

  • Check if card is properly plugged and fixed.


oFA03 to oFA43
Option Card / Comm Error

Cause: Option card or hardware is damaged.



Remedy:

  • Cycle power to the drive.

  • If problem continues, replace control board or entire drive.


oH
Heatsink Overheat

Cause: Surrounding temperature is too high.



Remedy:

  • Check the temperature surrounding the drive. Verify temperature is within drive specifications.

  • Improve the air circulation within the enclosure panel.

  • Install a fan or air conditioner to cool the surrounding area.

  • Remove anything near the drive that might be producing excessive heat.




Cause: Load is too heavy.



Remedy:

  • Measure the output current.

  • Decrease the load.

  • Lower the carrier frequency (C6-02).




Cause: Internal cooling fan is stopped.



Remedy:

  • Replace the cooling fan.

  • After replacing the cooling fan, set parameter o4-03 to 0 to reset the cooling fan maintenance.


oH1
Overheat 1 (Heatsink Overheat)

Cause: Surrounding temperature is too high.



Remedy:

  • Check the temperature surrounding the drive.

  • Improve the air circulation within the enclosure panel.

  • Install a fan or air conditioner to cool the surrounding area.

  • Remove anything near the drive that might be producing excessive heat.




Cause: Load is too heavy.



Remedy:

  • Measure the output current.

  • Lower the carrier frequency (C6-02).

  • Reduce the load.




Cause: The internal cooling fan has reached its performance life or has malfunctioned.



Remedy:

  • Check the maintenance time for the cooling fan (U4-04).

  • If U4-04 exceeds 90%, replace the cooling fan.

  • After replacing fan, reset the fan maintenance time (o4-03 = “0”).




Cause: Current flowing to control circuit terminal +V exceeded the tolerance level.



Remedy:

  • Check the current level of the terminal.

  • Set the current to the control circuit terminal to be 20 mA or less.


oH4
Motor Overheat Fault (PTC Input)

Cause: Motor has overheated.



Remedy:

  • Check the size of the load, the accel/decel times, and the cycle times.

  • Decrease the load.

  • Increase the acceleration and deceleration times (C1-01 through C1-04).

  • Adjust the preset V/f pattern (E1-04 through E1-10) by reducing E1-08 and E1-10.

  • Do not set E1-08 and E1-10 too low. This reduces load tolerance at low speeds.

  • Check the motor rated current.

  • Enter the motor rated current to parameter E2-01 as indicated on the motor nameplate.

  • Ensure the motor cooling system is operating normally.

  • Repair or replace the motor cooling system.


oL1
Motor Overload

Cause: Load is too heavy.



Remedy:

  • Reduce the load.




Cause: Cycle times are too short during acceleration and deceleration.



Remedy:

  • Increase the acceleration and deceleration times (C1-01 through C1-04).




Cause: A general-purpose motor is driven below the rated speed with a high load.



Remedy:

  • Reduce the load.

  • Increase the speed.

  • If the motor is supposed to operate at low speeds, either increase the motor capacity or use a motor specifically designed to operate in the desired speed range.




Cause: The output voltage is too high.



Remedy:

  • Adjust the user-set V/f pattern (E1-04 through E1-10) by reducing E1-08 and E1-10.

  • Do not set E1-08 and E1-10 too low.




Cause: The wrong motor rated current is set to E2-01.



Remedy:

  • Check the motor-rated current.

  • Enter the motor rated current to parameter E2-01 as indicated on the motor nameplate.




Cause: The base frequency is set incorrectly.



Remedy:

  • Check the rated frequency indicated on the motor nameplate.

  • Enter the rated frequency to E1-06 (Base Frequency).




Cause: The electrical thermal protection characteristics and motor overload characteristics do not match.



Remedy:

  • Check the motor characteristics.

  • Correct the type of motor protection that has been selected (L1-01).

  • Install an external thermal relay.




Cause: Motor overheated by overexcitation operation.



Remedy:

  • Prevent excessive overexcitation operation or apply proper cooling to the motor.

  • Reduce the excitation deceleration gain (n3-13).

  • Set L3-04 (Stall Prevention during Deceleration) to a value other than 4.




Cause: Parameters related to Speed Search are set incorrectly.



Remedy:

  • Check values set to Speed Search related parameters.

  • Adjust the Speed Search current and Speed Search deceleration times (b3-02 and b3-03 respectively).

  • After Auto-Tuning, set b3-24 to 1 to enable Speed Estimation Speed Search.




Cause: Output current fluctuation due to power supply loss.



Remedy:

  • Check the power supply for phase loss.


oL2
Drive Overload

Cause: Load is too heavy.



Remedy:

  • Reduce the load.




Cause: Acceleration or deceleration time is too short.



Remedy:

  • Increase the settings for the acceleration and deceleration times (C1-01 through C1-04).




Cause: The output voltage is too high.



Remedy:

  • Adjust the preset V/f pattern (E1-04 through E1-10) by reducing E1-08 and E1-10.

  • Do not lower E1-08 and E1-10 excessively.




Cause: Drive capacity is too small.



Remedy:

  • Replace the drive with a larger model.




Cause: Overload occurred when operating at low speeds.



Remedy:

  • Reduce the load when operating at low speeds.

  • Replace the drive with a model that is one frame size larger.

  • Lower the carrier frequency (C6-02).




Cause: Excessive torque compensation.



Remedy:

  • Reduce the torque compensation gain in parameter C4-01 until there is less current but no speed loss.




Cause: Parameters related to Speed Search are set incorrectly.



Remedy:

  • Check the settings for all Speed Search related parameters.

  • Adjust the current used during Speed Search (b3-03) and the Speed Search deceleration time (b3-02).

  • After Auto-Tuning, set b3-24 to 1 to enable Speed Estimation Speed Search.




Cause: Output current fluctuation due to input phase loss.



Remedy:

  • Check the power supply for phase loss.


oL3
Overtorque Detection 1

Cause: Parameter settings are not appropriate for the load.



Remedy:

  • Check L6-02 and L6-03 settings.




Cause: Fault on the machine side (e.g., machine is locked up).



Remedy:

  • Check the status of the load. Remove the cause of the fault.


oL4
Overtorque Detection 2

Cause: Parameter settings are not appropriate for the load.



Remedy:

  • Check the settings of parameters L6-05 and L6-06.


oL5
Mechanical Weakening Detection 1

Cause: Overtorque occurred, triggering the mechanical weakening level set to L6-08.



Remedy:

  • Check for the cause of mechanical weakening.


oPr
External Operator Connection Fault

Cause: External operator is not properly connected to the drive.



Remedy:

  • Check the connection between the keypad and the drive.

  • Replace the cable if damaged.

  • Turn off the drive input power and disconnect the keypad. Reconnect the keypad and reapply drive input power.


ou / ov
Overvoltage

Cause: Deceleration time is too short and regenerative energy is flowing from the motor into the drive.



Remedy:

  • Increase the deceleration time (C1-02 and C1-04).

  • Install a dynamic braking resistor or a dynamic braking resistor unit.

  • Set L3-04 to 1 to enable stall prevention during deceleration.




Cause: Fast acceleration time causes the motor to overshoot the speed reference.



Remedy:

  • Check if sudden drive acceleration triggers an overvoltage alarm.

  • Increase the acceleration time.

  • Use longer S-curve acceleration and deceleration times.

  • Enable the Overvoltage Suppression function (L3-11 = 1).

  • Lengthen the S-curve at acceleration end.




Cause: Excessive braking load.



Remedy:

  • The braking torque was too high, causing regenerative energy to charge the DC bus. Reduce the braking torque, use a dynamic braking option, or lengthen decel time.




Cause: Surge voltage entering from the drive input power.



Remedy:

  • Install a DC link choke.




Cause: Ground fault in the output circuit causes the DC bus capacitor to overcharge.



Remedy:

  • Check the motor wiring for ground faults.

  • Correct grounding shorts and reapply power.




Cause: Improper parameters related to Speed Search (including Speed Search after a momentary power loss and after a fault restart).



Remedy:

  • Check the settings for Speed Search-related parameters.

  • Enable Speed Search restart function (b3-19 greater than or equal to 1 to 10).

  • Adjust the current level during Speed Search and the deceleration time (b3-02 and b3-03 respectively).

  • Perform Stationary Auto-Tuning for line-to-line resistance and then set b3-14 to 1 to enable Speed Estimation Speed Search.




Cause: Drive input power voltage is too high.



Remedy:

  • Check the voltage.

  • Lower drive input power voltage within the limits listed in the specifications.


PF
Input Phase Loss

Cause: There is phase loss in the drive input power.



Remedy:

  • Check for wiring errors in the main circuit drive input power.

  • Correct the wiring.




Cause: There is loose wiring in the drive input power terminals.



Remedy:

  • Ensure the terminals are tightened properly.

  • Apply the tightening torque as specified in the manual.




Cause: There is excessive fluctuation in the drive input power voltage.



Remedy:

  • Check the voltage from the drive input power.

  • Review the possible solutions for stabilizing the drive input power.




Cause: There is poor balance between voltage phases.



Remedy:

  • Stabilize drive input power or disable phase loss detection.




Cause: The main circuit capacitors are worn out.



Remedy:

  • Check the maintenance time for the capacitors (U4-05).

  • Replace the capacitor if U4-05 is greater than 90%.

  • Check for problems with the drive input power.


PoC
Pump Over Cycle

Cause: The pump has exceeded the number of cycles set in P2-10 in the time set in P2-11 and P2-12 is set to 2 (fault).



Remedy:

  • Set the Pump Over Cycle fault characteristics in P2-10 and P2-11.

  • Drive response to this condition is controlled by P2-12, Over Cycling Mode.

  • Auto-restart of this fault is controlled by L5-52, Pump Over Cycle Fault Retry Selection.

  • Set the Pump Over Cycle automatic setpoint compensation in P2-12, Over Cycling Mode, P2-13, Setpoint Compensation, and P2-14, Maximum Setpoint Compensation.


rH
Braking Resistor Overheat

Cause: Deceleration time is too short and excessive regenerative energy is flowing back into the drive.



Remedy:

  • Check the load, deceleration time, and speed.

  • Reduce the load inertia.

  • Increase the deceleration times (C1-01 to C1-04).

  • Replace the dynamic braking option with a larger device that can handle the power that is discharged.




Cause: The duty cycle is too high.



Remedy:

  • Check the duty cycle. Maximum of 3% duty cycle is available when L8-01 = 1.




Cause: Excessive braking inertia.



Remedy:

  • Recalculate braking load and braking power. Reduce the braking load by adjusting braking resistor settings.




Cause: The braking operation duty cycle is too high.



Remedy:

  • Check the braking operation duty cycle. Braking resistor protection for ERF-type braking resistors (L8-01 = 1) allows a braking duty cycle of maximum 3%.




Cause: The proper braking resistor has not been installed.



Remedy:

  • Check the specifications and conditions for the braking resistor device.

  • Select the optimal braking resistor.


rr
Dynamic Braking Transistor

Cause: The built-in dynamic braking transistor failed. The braking transistor or the control circuit is damaged.



Remedy:

  • Cycle power to the drive and check for reoccurrence of the fault.

  • Replace the drive.


SC
IGBT Short Circuit or Ground Fault

Cause: An IGBT fault occurred or the drive is damaged (IGBT short circuit detection circuit fault).



Remedy:

  • Check motor wiring.

  • Turn off the power supply, then turn it on. If the problem continues, contact your Yaskawa representative.

  • Check the drive output side short circuit for a broken output transistor (B1, U/T1, V/T2, W/T3).


SEr
Too Many Speed Search Restarts

Cause: The number of Speed Search restarts exceeded the value set to b3-19. Parameters related to Speed Search are set to wrong values, or the motor is coasting in the opposite direction.



Remedy:

  • Reduce the detection compensation gain during Speed Search (b3-10).

  • Increase the current level when attempting Speed Search (b3-17).

  • Increase the detection time during Speed Search (b3-18).

  • Repeat Auto-Tuning.

  • Set b3-14 to 1 to enable Bi-Directional Speed Search.


TIE
Time Interval Error

Cause: An error has occurred in the Real-Clock Time function of the HOA keypad.



Remedy:

  • Replace the HOA keypad. Contact Yaskawa or your nearest sales representative.


UL3
Undertorque Detection 1

Cause: The current has fallen below the minimum value set for torque detection (L6-02) for longer than the allowable time (L6-03). Parameter settings may not be appropriate, or there is a fault on the machine side.



Remedy:

  • Check the settings of parameters L6-02 and L6-03.

  • Check the load for any problems.


UL4
Undertorque Detection 2

Cause: The current has fallen below the minimum value set for torque detection (L6-05) for longer than the allowable time (L6-06). Parameter settings may not be appropriate, or there is a fault on the machine side.



Remedy:

  • Check L6-05 and L6-06 settings.

  • Check the load for any problems.


UL6
Motor Underload (Underload Det 6)

Cause: The load has fallen below the underload curve defined in L6-14 for longer than the time set to L6-03.



Remedy:

  • Adjust the value set to L6-14 so that output current remains above the motor underload curve during normal operation.


Uv1
DC Bus Undervoltage

Cause: Voltage in the DC bus fell below detection level (L2-05). Causes include input power phase loss, loose wiring terminals, voltage problems, power interruption, worn capacitors, or damaged relay/contactor.



Remedy:

  • Correct the wiring (check for phase loss).

  • Ensure there are no loose terminals; apply specified tightening torque.

  • Check voltage and correct to be within range.

  • Check for problems with the main circuit magnetic contactor.

  • Check capacitor maintenance time (U4-05); replace drive if >90%.

  • Cycle power; if fault reoccurs, replace the drive.


Uv2
Control Power Supply Voltage Fault

Cause: Voltage is too low for the control drive input power. L2-02 changed from default, wiring damaged, or internal circuitry damaged.



Remedy:

  • Correct the setting to L2-02 or install an optional Momentary Power Loss Ride-Thru unit.

  • Cycle power. If fault persists, replace control board, entire drive, or control power supply.

  • If internal circuitry is damaged, replace the drive.


Uv3
Undervoltage 3 (Soft-Charge Bypass Circuit Fault)

Cause: The soft-charge bypass circuit failed (relay or contactor damaged).



Remedy:

  • Cycle power to the drive and see if the fault reoccurs.

  • Check monitor U4-06 for performance life of soft-charge bypass.

  • Replace the drive if U4-06 exceeds 90% or if the problem continues.


VLTS
Volute-Thermostat Fault

Cause: The digital input assigned to volute/thermostat (H1-0x = 88 or 89) is active, or both inputs are programmed simultaneously.



Remedy:

  • Check the wiring or wait for the volute or motor to cool.

  • Program only one digital input to either H1-0x = 88 or H1-0x = 89.


AEr
Station Address Setting Error

Cause: Station number is set outside the possible setting range (CC-Link, CANopen, MECHATROLINK).


Remedy:

  • Set parameter F6-10 to the proper value if a CC-Link option card is used.

  • Set parameter F6-20 to the proper value if a MECHATROLINK option card is used.

  • Set parameter F6-35 to the proper value if a CANopen option card is used.


AfbL
Analog Feedback Lost

Cause: Defective or broken analog input source. H3-0x is not set to B (PID Feedback).


Remedy:

  • Confirm that the PID feedback source is installed and working properly.

  • If there is no feedback source, set P9-02 to 3 so the drive will read the network PID feedback from another drive.

  • Set H3-0x to B if the analog input source is to be used for PID feedback.


AJA
Anti-Jam Active

Cause: The drive is attempting to clear debris from the impeller. This is only effective when P7-01 (Anti-jam Operation) is set to 1.


Remedy:

  • Alarm will clear when function is complete.

  • Drive response to this condition is controlled by P7-01, Anti-jam Operation Selection.


bAT
Digital Operator Battery Voltage Low

Cause: The digital operator battery is low.


Remedy:

  • Replace the digital operator battery.


bb
Baseblock

Cause: External baseblock signal was entered via one of the multi-function input terminals (S1 to S7).


Remedy:

  • Check external sequence and baseblock signal input timing.


bUS
Option Communication Error

Cause: The connection was lost after initial communication was established, or option is damaged/improperly connected.


Remedy:

  • Check for faulty wiring or disconnected cables.

  • If there are no problems with wiring, replace the option.

  • Ensure connector pins on the option are properly lined up with the drive.

  • Reinstall the option.


CALL
Serial Communication Transmission Error

Cause: Communications wiring is faulty, short circuit, or programming error on master side.


Remedy:

  • Check for wiring errors, disconnected cables, and short circuits.

  • Check communications at start-up and correct programming errors.

  • Perform a self-diagnostics check.

  • Install a termination resistor at both ends of a communication line (DIP switch S2 to ON).


CE
MEMOBUS/Modbus Communication Error

Cause: Control data was not received correctly for two seconds (Noise, Protocol incompatibility, or Timeout).


Remedy:

  • Check options available to minimize the effects of noise (surge absorbers, shielded lines).

  • Check the H5 parameter settings and the protocol setting in the controller.

  • Set a longer CE detection time using parameter H5-09.

  • Check the connector to make sure the cable has a signal.


Clock Not Set
Time and Date Not Set

Cause: Drive powered up for the first time, or button not pressed during setup screen.


Remedy:

  • Pressing the F2 (Data) key will display the setting screen again.


CrST
Cannot Reset

Cause: Fault reset was being executed when a run command was entered.


Remedy:

  • Ensure that a run command cannot be entered from the external terminals or option card during fault reset.

  • Turn off the run command.


CyC
MECHATROLINK Comm. Cycle Setting Error

Cause: The controller is using a comm. cycle beyond the allowable setting range.


Remedy:

  • Set the comm. cycle for the upper controller within the allowable setting range for the MECHATROLINK option unit.


dnE
Drive Disabled

Cause: “Drive Enable” is set to a multi-function contact input (H1-xx = 6A) and the contact is open.


Remedy:

  • Check the operation sequence.


E5
MECHATROLINK Watchdog Timer Error

Cause: The watchdog timer expired while waiting for data from the controller.


Remedy:

  • Issue a DISCONNECT or ALM_CLR command, followed by a CONNECT or SYNC_SET command and move to phase 3.


EF
Forward/Reverse Run Command Input Error

Cause: Both forward run and reverse run closed simultaneously for longer than 0.5 s.


Remedy:

  • Check the forward and reverse command sequence and correct the problem.

  • Note: When minor fault EF detected, motor ramps to stop.


EF0
Option Card External Fault

Cause: An external fault was received from the PLC with F6-03 set to 3.


Remedy:

  • Remove the cause of the external fault.

  • Remove the external fault input from the PLC.

  • Check the PLC program and correct problems.


EF1
Pump Fault (Input Terminal S1)

Cause: External device has tripped alarm or wiring incorrect on S1.


Remedy:

  • Remove the cause of the external fault and reset the multi-function input value.

  • Ensure signal lines connected properly to terminals assigned for external fault detection (H1-xx = 20 to 2F).


EF2
Pump Fault (Input Terminal S2)

Cause: External device has tripped alarm or wiring incorrect on S2.


Remedy:

  • Remove the cause of the external fault and reset the multi-function input value.

  • Ensure signal lines connected properly.


EF3
Pump Fault (Input Terminal S3)

Cause: External device has tripped alarm or wiring incorrect on S3.


Remedy:

  • Remove the cause of the external fault and reset the multi-function input value.


EF4
Pump Fault (Input Terminal S4)

Cause: External device has tripped alarm or wiring incorrect on S4.


Remedy:

  • Remove the cause of the external fault and reset the multi-function input value.


EF5
Pump Fault (Input Terminal S5)

Cause: External device has tripped alarm or wiring incorrect on S5.


Remedy:

  • Remove the cause of the external fault and reset the multi-function input value.


EF6
Pump Fault (Input Terminal S6)

Cause: External device has tripped alarm or wiring incorrect on S6.


Remedy:

  • Remove the cause of the external fault and reset the multi-function input value.


EF7
Pump Fault (Input Terminal S7)

Cause: External device has tripped alarm or wiring incorrect on S7.


Remedy:

  • Remove the cause of the external fault and reset the multi-function input value.

  • Check if unused terminals have been set for H1-xx = 20 to 2F.


EoF
Emergency Override Forward Run

Cause: The multi-function digital input for EmergOverrideFWD (H1-xx = AF) has been closed.


Remedy:

  • Open H1-xx = AF if the emergency condition is no longer present.


Eor
Emergency Override Reverse Run

Cause: The multi-function digital input for EmergOverrideREV (H1-xx = B0) has been closed.


Remedy:

  • Open H1-xx = B0 if the emergency condition is no longer present.


E5
SI-T3 Watchdog Timer Error

Cause: The watchdog timed out. Data has not been received from the PLC.


Remedy:

  • Execute DISCONNECT or ALM_CLR, then issue a CONNECT command or SYNC_SET command.

  • Refer to the SI-T3 Option Technical Manual for troubleshooting.


FAn
Internal Cooling Fan Error

Cause: Internal cooling fan has malfunctioned.


Remedy:

  • Cycle power to the drive.

  • Check for fan operation.

  • If the problem continues, replace the fan.


Hbb / HbbF
Safe Disable Signal Input

Cause: There is no signal at terminal H1, or the safe disable input hardware is defective.


Remedy:

  • Check if external safety circuit tripped and disabled the drive.

  • If the Safe Disable function is not utilized, check if the terminals HC, H1, and H2 are linked.

  • If internally broken (HbbF), replace the drive.


FLGt
PID Feedback Loss (Go To Freq)

Cause: PID feedback source is incorrectly installed or not working (Effective when b5-12 is 3).


Remedy:

  • Confirm that the PID feedback source is installed and working properly.

  • Drive response is controlled by b5-12 and b5-13.


Fdb-L
PID Feedback Loss (Wire Break)

Cause: The analog input for PID feedback has gone above 21 mA or fallen below 3 mA.


Remedy:

  • Confirm that the PID feedback source is installed and working properly.

  • Auto-restart of this fault is controlled by L5-42.


PFrEF
Minimum Pump Frequency Reference

Cause: The frequency reference is set lower than P1-06 (Minimum Pump Frequency).


Remedy:

  • Increase the frequency reference to a value greater than P1-06.


PtHrt
Thrust Frequency Reference

Cause: The fixed frequency reference is set to a value lower than the P4-12 (Thrust Frequency) setting.


Remedy:

  • Increase the frequency reference to a value greater than P4-12.


HCA
Current Alarm

Cause: Load is too heavy. Drive current exceeded overcurrent warning level (150% of rated current).


Remedy:

  • Reduce the load for applications with repetitive operations (i.e., stops and starts).

  • Replace the drive if necessary.


HbbF
Safe Disable Signal Input

Cause: The safe disable input hardware is defective or the Safe Disable channel is broken.


Remedy:

  • Replace the drive.


FLGt
PID Feedback Loss (Go To Freq)

Cause: PID feedback source is incorrectly installed or is not working. Effective only when b5-12 is set to 3.


Remedy:

  • Confirm that the PID feedback source is installed and working properly.

  • Check settings for b5-12 (Detection Selection) and b5-13 (Go To Frequency).


Fdb-L
PID Feedback Loss (Wire Break)

Cause: The analog input programmed for PID feedback has gone above 21 mA or fallen below 3 mA.


Remedy:

  • Confirm that the PID feedback source is installed and working properly.

  • Check settings for b5-12 and b5-13.

  • Auto-restart of this fault is controlled by L5-42.


PFrEF
Minimum Pump Frequency Reference

Cause: Drive frequency reference is set lower than P1-06 (Minimum Pump Frequency).


Remedy:

  • Increase the frequency reference to a value greater than P1-06.


PtHrt
Thrust Frequency Reference

Cause: The fixed frequency reference is set to a value lower than the P4-12 (Thrust Frequency) setting.


Remedy:

  • Increase the frequency reference to a value greater than P4-12.


HCA
Current Alarm

Cause: Drive current exceeded overcurrent warning level (150% of rated current). Load is too heavy.


Remedy:

  • Reduce the load for applications with repetitive operations.

  • Replace the drive.

  • Increase acceleration and deceleration times (C1-01 through C1-04).

  • Check motor capacity.


H1Fb
High Feedback Level Alarm

Cause: The feedback signal is too high (risen above P1-11).


Remedy:

  • Decrease the feedback signal.

  • Set the High Feedback alarm characteristics in P1-11 and P-12.


LoP
Loss of Prime

Cause: Water level dropped below P1-19. Could be due to dry well, air in system, or no water.


Remedy:

  • If there is resistance in the pump, allow the system to pump water again.

  • Set the Loss of Prime alarm characteristics in P1-18, P1-19, P1-20, and P1-21.


LCP
Low City Pressure

Cause: Insufficient pressure is present on the inlet to the pump.


Remedy:

  • Check pressure switch contact for correct operation.

  • Check control wiring to drive terminal strip from pressure switch contact.

  • Check to make sure that suction pressure is present by means of a separate measuring device.


LoFb
Low Feedback Level Alarm

Cause: The feedback signal is too low (dropped below P1-08).


Remedy:

  • Increase the feedback signal.

  • Set the Low Feedback alarm characteristics in P1-08 and P1-09.


LSP
Low Suction Pressure

Cause: Insufficient suction pressure is present.


Remedy:

  • Check pressure switch contact for correct operation.

  • Check control wiring to drive terminal strip from pressure switch contact.

  • Check to make sure that suction pressure is present by means of a separate measuring device.


LLLt
Low Water in Tank

Cause: The water level in the tank is too low.


Remedy:

  • Check pressure switch contact for correct operation.

  • Check control wiring to drive terminal strip from pressure switch contact.

  • Raise the water level.


LT-1
Cooling Fan Maintenance Time

Cause: The cooling fan has reached 90% of its expected performance life.


Remedy:

  • Replace the cooling fan.

  • Set o4-03 to 0 to reset the Maintenance Monitor.


LT-2
Capacitor Maintenance Time

Cause: The main circuit and control circuit capacitors have reached 90% of their expected performance lives.


Remedy:

  • Replace the drive.


LT-3
Soft Charge Bypass Relay Maintenance Time

Cause: The DC bus soft charge relay has reached 90% of expected performance life.


Remedy:

  • Replace the drive.


LT-4
IGBT Maintenance Time (50%)

Cause: IGBTs have reached 50% of their expected performance life.


Remedy:

  • Check the load, carrier frequency, and output frequency.


nEtSC
NETSCAN Waiting for Master

Cause: No message was received from the master within the time set in P9-28.


Remedy:

  • Increase the P9-26 setting to account for network latency.

  • Verify that there is a drive on the network with parameter P1-01 set to 3 and P9-27 to 0.

  • Check network connections and settings.


notSP
Not Maintaining Setpoint

Cause: The setpoint cannot be maintained (deviation > P1-15 for time P1-16).


Remedy:

  • Check for a blocked impeller, over cycling, or broken pipe.

  • Set the Not Maintaining Setpoint alarm characteristics in P1-16 and P1-17.


oH
Heatsink Overheat

Cause: Heatsink temperature exceeded L8-02. Cooling fan stopped. Airflow restricted.


Remedy:

  • Check surrounding temperature and improve air circulation.

  • Replace cooling fan (and reset o4-03).

  • Clear debris caught in the fan.


oH2
Drive Overheat Warning

Cause: An external device triggered an overheat warning (input terminal S1-S7).


Remedy:

  • Search for the device that tripped the overheat warning.

  • Remove the cause of the problem.


oH3
Motor Overheat

Cause: Motor thermostat wiring faulty. Machine fault. Motor overheated.


Remedy:

  • Repair PTC input wiring.

  • Check status of machine (e.g. locked up).

  • Decrease load.

  • Adjust preset V/f pattern (E1-04 to E1-10).

  • Check motor-rated current (E2-01).


oL1
Motor Overload

Cause: Load too heavy. Cycle times too short. Wrong V/f pattern. Wrong motor rated current setting.


Remedy:

  • Reduce the load.

  • Increase acceleration/deceleration times.

  • Adjust V/f pattern (reduce E1-08/E1-10).

  • Check motor nameplate and enter correct rated current in E2-01.

  • Check motor protection type (L1-01).


oL2
Drive Overload

Cause: Thermal sensor of drive triggered. Load too heavy. Accel/Decel too short. Low speed operation.


Remedy:

  • Reduce the load.

  • Increase acceleration/deceleration times.

  • Replace drive with larger model.

  • Lower the carrier frequency (C6-02).


oL3
Overtorque Detection 1

Cause: Current exceeded value in L6-02 for longer than L6-03.


Remedy:

  • Check L6-02 and L6-03 settings.

  • Check status of the load (e.g. machine locked up).



oL2



Drive Overload

(The thermal sensor of the drive triggered overload protection)

Cause:



  • Load is too heavy.

  • Acceleration or deceleration time is too short.

  • The output voltage is too high.

  • Drive capacity is too small.

  • Overload occurred when operating at low speeds.

  • Excessive torque compensation.

  • Parameters related to Speed Search are set incorrectly.

  • Output current fluctuation due to input phase loss.




Remedy:



  • Reduce the load.

  • Increase the settings for acceleration and deceleration times (C1-01 through C1-04).

  • Adjust the preset V/f pattern (E1-04 through E1-10) by reducing E1-08 and E1-10.

  • Replace the drive with a larger model.

  • Lower the carrier frequency (C6-02).

  • Reduce the torque compensation gain in parameter C4-01.

  • Adjust Speed Search current (b3-03) and deceleration time (b3-02).

  • Check the power supply for phase loss.



oL3



Overtorque Detection 1

(Current exceeded value set in L6-02 for longer than L6-03)

Cause:



  • Parameter settings are not appropriate for the load.

  • Fault on the machine side (e.g., machine is locked up).




Remedy:



  • Check L6-02 and L6-03 settings.

  • Check the status of the load. Remove the cause of the fault.



oL4



Overtorque Detection 2

(Current exceeded value set in L6-05 for longer than L6-06)

Cause:


Parameter settings are not appropriate for the load.



Remedy:


Check the settings of parameters L6-05 and L6-06.

ov



DC Bus Overvoltage

(DC bus voltage exceeded the trip point)

Cause:



  • Surge voltage present in the drive input power.

  • The motor is short-circuited.

  • Ground current has overcharged the main circuit capacitors via the drive input power.

  • Noise interference causes the drive to operate incorrectly.




Remedy:



  • Install a DC link choke or an AC reactor.

  • Check the motor power cable, relay terminals, and motor terminal box for short circuits.

  • Review section on handling noise interference and check control circuit lines and ground wiring.

  • If magnetic contactor is the noise source, install a surge protector to the MC coil.

  • Set number of fault restarts (L5-01) to a value other than 0.



PCYC



Pump Over Cycle

Cause:


The pump has exceeded the number of cycles set in P2-10 in the time set in P2-11 and P2-12 is set to 1 (alarm).



Remedy:



  • Set the Pump Over Cycle alarm characteristics in P2-10 and P2-11.

  • Drive response to this condition is controlled by P2-12 (Over Cycling Mode).



rdd



Remote Drive Disable

Cause:



  • Terminal S□ (H1-0□ = 95) has been closed for the time set in P4-26 (N.O. setting).

  • Terminal S□ (H1-0□ = 95) has been open for the time set in P4-26 (N.C. setting).




Remedy:


Remove conditions causing the terminal to close (or open, depending on selection).

SE



MEMOBUS/Modbus Communication Test Mode Error

Cause:


A digital input set to 67H (MEMOBUS/Modbus test) was closed while the drive was running.



Remedy:


Stop the drive and run the test again.

TdE



Time Data Error

Cause:


An error has occurred in the Real-Clock Time function of the HOA keypad.



Remedy:


Replace the HOA keypad. Contact Yaskawa or your nearest sales representative.

TrPC



IGBT Maintenance Time (90%)

Cause:


IGBTs have reached 90% of their expected performance life.



Remedy:


Replace the drive.

UL3



Undertorque Detection 1

(Current fallen below L6-02 for longer than L6-03)

Cause:



  • Parameter settings are not appropriate for the load.

  • There is a fault on the machine side.




Remedy:



  • Check the settings of parameters L6-02 and L6-03.

  • Check the load for any problems.



UL4



Undertorque Detection 2

(Current fallen below L6-05 for longer than L6-06)

Cause:



  • Parameter settings are not appropriate for the load.

  • There is a fault on the machine side.




Remedy:



  • Check L6-05 and L6-06 settings.

  • Check the load for any problems.



UL6



Motor Underload

(Load fallen below underload curve L6-14)

Cause:


The output current has fallen below the motor underload curve defined in L6-14 for longer than the time set to L6-03.



Remedy:


Adjust the value set to L6-14 so that output current remains above the motor underload curve during normal operation.

Uv



Undervoltage

Cause:



  • Phase loss in the drive input power.

  • Loose wiring in the drive input power terminals.

  • There is a problem with the drive input power voltage.

  • Drive internal circuitry is worn.

  • The drive input power transformer is too small and voltage drops when power is switched on.




Remedy:



  • Check for wiring errors in the main circuit drive input power. Correct the wiring.

  • Ensure terminals are properly tightened (Refer to torque specs).

  • Check the voltage. Lower the voltage of the drive input power so it is within limits.

  • Check maintenance time for capacitors (U4-05). Replace drive if U4-05 exceeds 90%.

  • Check the capacity of the drive input power transformer.


oPE01
Drive Capacity Setting Fault

Cause:

The drive model selection (o2-04) and the actual capacity of the drive are not the same.



Remedy:


  • Correct the value set to o2-04.


oPE02
Parameter Range Setting Error

Cause:

Parameters were set outside the possible setting range.



Remedy:


  • Use U1-18 to find parameters set outside the range.

  • Set parameters to the proper values.


oPE03
Multi-Function Input Selection Error

Cause:

A contradictory setting is assigned to multi-function contact inputs H1-01 to H1-07. Common conflicts include:

  • The same function is assigned to two inputs.

  • Up command set without Down command (or vice versa).

  • Run/Stop (2-wire) set without FWD/REV command.

  • Contradictory functions set simultaneously (e.g., Up/Down and PID control).





Remedy:


  • Ensure all multi-function inputs are assigned to different functions.

  • Re-enter the multi-function settings to ensure this does not occur.

  • Check if contradictory settings have simultaneously been assigned to the multi-function input terminals.

  • Set b5-01 to 0 to disable control PID or disable the Up/Down command if both are enabled.


oPE04
Initialization Required (Term <-> Ctrl Chg)

Cause:

The drive, control board, or terminal board have been replaced and the parameter settings between the control board and the terminal board no longer match.



Remedy:


  • Set A1-03 to 5550 to load the parameter settings stored in the terminal board to the drive.

  • Initialize parameters after drive replacement by setting A1-03 to 1110 or 2220.


oPE05
Run Command/Frequency Reference Source Selection Error

Cause:


  • Frequency reference or Run command is assigned to an option card (b1-01/b1-02 = 3) but no card is connected.

  • Frequency reference assigned to pulse train input (b1-01 = 4) and terminal RP is not set for frequency reference input.





Remedy:


  • Reconnect the input option card to the drive.

  • Set H6-01 to 0 if pulse train is not used properly.


oPE07
Multi-Function Analog Input Selection Error

Cause:

A contradictory setting is assigned to multi-function analog inputs H3-02 or H3-10 and PID functions conflict (set to the same value).



Remedy:


  • Change the settings to H3-02 or H3-10 so that functions no longer conflict.


oPE09
PID Control Selection Fault

Cause:

PID control function selection is incorrect.

  • Simultaneous contradictory settings for PID Feedback/Target vs Pulse Train.

  • b5-01 is set to 1 or 2 (PID enabled), but lower limit (d2-02) is not 0 while reverse output is enabled (b5-11=1).





Remedy:


  • Disable one of the PID selections.

  • Correct the parameter settings for b5-01, d2-02, or b5-11.


oPE10
V/f Data Setting Error

Cause:

V/f pattern setting error. One of the following errors occurred:
E1-09 ≤ E1-07 < E1-06 ≤ E1-11 ≤ E1-04.



Remedy:


  • Correct the settings for E1-04, E1-06, E1-07, E1-09, and E1-11.


oPE11
Carrier Frequency Setting Error

Cause:

The following simultaneous contradictory settings have occurred:

C6-05 > 6 and C6-04 > C6-03 (carrier frequency lower limit is greater than the upper limit).



Remedy:


  • Correct the setting for the carrier frequency (C6-02 to C6-05).


oPE33
Net Incompatible

Cause:

Parameter selection is incompatible with the selected network P9-99.



Remedy:


  • Confirm parameter settings for P1-01, P9-01, P9-99, and P9-05.


CoPy
Writing Parameter Settings (flashing)

Cause:

Parameters are being written to the drive.



Remedy:


  • This is not an error. Wait for the process to complete.


CoPyE
Error Writing Data

Cause:

Failed writing parameters.



Remedy:


  • Attempt to write parameters again.


CSEr
Copy Unit Error

Cause:

Hardware fault.



Remedy:


  • Replace the HOA keypad or the USB Copy Unit.


dFPS
Drive Model Mismatch

Cause:

The drives used in the copy and write process are not the same model.



Remedy:


  • Verify the model number of the drive from which the parameters were copied.

  • Make sure the two drives are the same model and have the same software version.


End
Task Complete

Cause:

Finished reading, writing, or verifying parameters.



Remedy:


  • This is not an error.


iFEr
Communication Error

Cause:

A communication error occurred between the drive and the HOA keypad or the USB copy unit.



Remedy:


  • Check the cable connection.

  • Use the cable originally packaged with the USB Copy Unit.


ndAT
Model, Voltage Class, Capacity Mismatch

Cause:

The drive from which the parameters were copied and the drive to which they are being written have different electrical specifications, capacities, or control modes.



Remedy:


  • Make sure model numbers and specifications are the same for both drives.


rdEr
Error Reading Data

Cause:

Failed while attempting to read parameter settings from the drive.



Remedy:


  • Press and hold the READ key on the USB Copy Unit for at least one second.


rEAd
Reading Parameter Settings (flashing)

Cause:

Displayed while the parameter settings are being read onto the USB Copy Unit.



Remedy:


  • This is not an error.


vAEr
Voltage Class, Capacity Mismatch

Cause:

The drive from which parameters were copied and the drive being verified have different specifications.



Remedy:


  • Make sure electrical specifications and capacities are the same for both drives.


vFyE
Parameter Settings Mismatch

Cause:

Indicates that parameter settings that have been Read and loaded onto the Copy Unit/Keypad are different from the drive.



Remedy:


  • Synchronize parameters by writing saved parameters to the drive, or reading parameters from the drive.


vrFy
Comparing Parameter Settings (flashing)

Cause:

The Verify mode has confirmed that parameters on the drive and copy device are identical.



Remedy:


  • This is not an error.


CrST
Cannot Reset

Cause:

Fault reset was being executed when a Run command was entered.



Remedy:


  • Ensure that a Run command cannot be entered from external terminals or options during fault reset.

  • Turn off the Run command.


Cur
Current Limit Foldback

Cause:

Displayed when drive output speed is being limited due to the output current limit.



Remedy:


  • Reduce the load.

  • Replace with a higher capacity drive.


dStGE
De-staging in X sec

Cause:

Displayed during multiplexing when drive de-staging is in progress.



Remedy:


  • Wait for the timer to elapse (X indicates time left).


FbcH-
Feedback Drop Check

Cause:

Displayed when the drive is determining whether the feedback will change abruptly when entering Sleep Mode.



Remedy:


  • Check P2-08 and P2-09 settings if operation is unexpected.


LoC-P
Parameter Locked

Cause:

Displayed after an attempt to change a parameter when A1-01 = 3.



Remedy:


  • Unlock the keypad by setting A1-01 = 2.


nEtEr
Net Pump Err (Chk Faulted Pump)

Cause:

Displayed when the drive has been stopped because another drive in the network has a system fault or a Low City Pressure alarm.



Remedy:


  • Check other drives in the network for faults.


nEtSt
Net Start Delay (P9-29 Active)

Cause:

Displayed when the MEMOBUS network is waiting for the P9-29 timer to elapse.



Remedy:


  • Wait for the timer to elapse.


nEtFb
Network FB Lost (Check FB Source)

Cause:

Displayed when no valid analog PID feedback source can be found on the network.



Remedy:


  • Check the network and PID feedback source connections.


PASS
MEMOBUS/Modbus Comm. Test Mode Complete

Cause:

MEMOBUS/Modbus test has finished normally.



Remedy:


  • No action required.


PrCHG
Pre Chg Mode (Exit in Xsec)

Cause:

Pre-charge 1 or 2 active. X indicates time left before pre-charge exits due to timers (P4-03 + P4-07).



Remedy:


  • Wait for pre-charge to complete.


1PH
Single Phase Foldback

Cause:

Displayed when an input phase has been lost, or when excess load is being drawn by the motor in a single phase application.



Remedy:


  • Check input power phases.

  • Check motor load.


SLEEP
Sleep Active Wait for Start

Cause:

Displayed when the drive is in Sleep Mode or waiting for the feedback level to reach the level set in P1-04.



Remedy:


  • Normal operation. Drive will start when demand increases.


booSt
Sleep Boost Active

Cause:

Displayed when the drive entering Sleep Mode and the pressure setpoint is being boosted.



Remedy:


  • Normal operation during Sleep Boost.


StAGE
Staging in X sec

Cause:

Displayed during multiplexing when drive staging is in progress.



Remedy:


  • Wait for staging timer to elapse.