Fuji FRENIC-HVAC Drive Fault Codes:
| Fault Code | Cause & Solution |
|---|---|
| OCn Overcurrent | Cause & Solution: 1. Ground fault or short circuit exists in the output circuit. – Check whether short-circuit occurs on the motor, the motor cable or contactor. 2. Acceleration time is too short. – Increase acceleration time. 3. Customized torque boost or V/F curve is not appropriate. – Adjust the customized torque boost or V/F curve. 4. The voltage is too low. – Adjust the voltage to normal range. 5. The spinning motor is started. – Enable the catching a spinning motor function or start the motor after it stops. 6. A load is applied suddenly during acceleration. – Cancel the suddenly added load. 7. The rated AC drive power is low. – Replace the drive by one with higher rated power. 8. The braking resistor resistance is small. – The braking resistor is short circuited. – Replace a new braking resistor. |
| OC1 Overcurrent during acceleration | Cause & Solution: 1. Ground fault or short circuit exists in the output circuit. – Check whether short-circuit occurs on the motor, the motor cable or contactor. 2. Acceleration time is too short. – Increase acceleration time. 3. Customized torque boost or V/F curve is not appropriate. – Adjust the customized torque boost or V/F curve. 4. The voltage is too low. – Adjust the voltage to normal range. 5. The spinning motor is started. – Enable the catching a spinning motor function or start the motor after it stops. 6. A load is applied suddenly during acceleration. – Cancel the suddenly added load. 7. The rated AC drive power is low. – Replace the drive by one with higher rated power. 8. The braking resistor resistance is small. – The braking resistor is short circuited. – Replace a new braking resistor. |
| OC2 Overcurrent during deceleration | Cause & Solution: 1. Ground fault or short circuit exists in the output circuit. – Check whether short-circuit occurs on motor, motor cable or contactor. 2. Acceleration time is too short. – Increase acceleration time. 3. The voltage is too low. – Adjust the voltage to normal range. 4. A load is added suddenly during deceleration. – Cancel the suddenly added load. 5. Braking unit and braking resistor are not installed. – Install the braking unit and braking resistor. 6. The braking resistor resistance is small or the braking resistor is short circuited. – Replace a new braking resistor. |
| OC3 Overcurrent at constant speed | Cause & Solution: 1. Ground fault or short circuit exists in the output circuit. – Check whether short-circuit occurs on the motor, motor cable or contactor 2. The voltage is too low. – Adjust the voltage to normal range. 3. A load is added suddenly during running. – Cancel the suddenly added load. 4. The rated AC drive power is low. – Replace the drive by one with higher rated power. 5. The braking resistor resistance is small or the braking resistor is short circuited. – Replace a new braking resistor. |
| EF Earth fault | Cause: A earth fault current flew from the output terminal of the inverter. Solution: 1. The output terminal of the inverter is short-circuited to the ground (ground fault, or earthed). – Disconnect the wires from the output terminals ([U], [V], and [W]) and perform a megger test. – Remove the earthed path (including the replacement of the wires, the terminals, or the motor as necessary). |
| OUn Overvoltage | Cause & Solution: 1. Input voltage is too high. – Adjust input voltage to normal range. 2. An external force drives motor during acceleration. – Cancel the external force. 3. Braking unit and braking resistor are not installed. – Install the braking unit and braking resistor. 4. Acceleration time is too short. – Increase acceleration time. |
| OV1/OU1 Overvoltage during acceleration | Cause & Solution: 1. Input voltage is too high. – Adjust input voltage to normal range. 2. An external force drives motor during acceleration. – Cancel the external force. 3. Braking unit and braking resistor are not installed. – Install the braking unit and braking resistor. 4. Acceleration time is too short. – Increase acceleration time. |
| OV2/OU2 Overvoltage during deceleration | Cause & Solution: 1. Input voltage is too high. – Adjust input voltage to normal range. 2. An external force drives motor during deceleration. – Cancel the external force or install the braking resistor. 3. Deceleration time is too short. – Increase deceleration time. 4. Braking unit and braking resistor are not installed. – Install the braking unit and braking resistor. |
| OV3/OU3 Overvoltage at constant speed | Cause & Solution: 1. Input voltage is too high. – Adjust input voltage to normal range. 2. An external force drives motor during running. – Cancel the external force or install a braking resistor. |
| LU/LV Undervoltage | Cause & Solution: 1. An instantaneous power failure occurs. – Reset the fault 2. The AC drive’s input voltage is not within the permissible range. – Adjust the voltage to normal range. 3. The bus voltage is abnormal. – Replace the AC drive. 4. The rectifier bridge, the pre-charge resistor, the drive board or the control board are abnormal. – Replace the AC drive. |
| Lin Input phase loss | Cause & Solution: 1. Three phase input is abnormal. – Eliminate faults in external circuitry 2. Drive board is abnormal. – Eliminate faults in external circuitry 3. Lightning protection board is abnormal. – There is an hardware or software issue in drive. Need to repair or replace drive. 4. Control board is abnormal. – There is an hardware or software issue in drive. Need to repair or replace drive. |
| OPL Output phase loss | Cause & Solution: 1. Motor winding is damaged. Check resistance between motor cables. – Replace motor is winding is damaged. 2. The cable connecting the AC drive and the motor is abnormal. – Check for wiring errors and ensure the output cable is connected properly 3. The AC drive’s three-phase outputs are unbalanced when the motor is running. – Check whether the motor three-phase winding is normal. 4. The drive board or the IGBT is abnormal. – Replace the AC drive. |
| OH1 Heat sink overheat | Cause & Solution: 1. The ambient temperature is too high. – Lower the ambient temperature. 2. The ventilation is clogged. – Clean the ventilation. 3. The fan is damaged. – Replace the cooling fan. 4. The thermally sensitive resistor of IGBT is damaged. – Replace the AC drive. 5. The AC drive IGBT is damaged. – Replace the AC drive. |
| OH2 External alarm input | Cause: External alarm was inputted (THR). Solution: 1. An alarm function of the external equipment was activated. – Inspect external equipment operation. – Remove the cause of the alarm that occurred. 2. Connection has been performed incorrectly. – Check if the wire for the external alarm signal is correctly connected to the terminal to which the “Alarm from external equipment” has been assigned. – Connect the wire for the alarm signal correctly. 3. Incorrect settings. – Check if the “Alarm from external equipment” has not been assigned to an unassigned terminal. – Correct the assignment. |
| OH3 Inside of the inverter overheat | Cause: The temperature inside the inverter exceeded the allowable limit. Solution: 1. The ambient temperature exceeded the allowable limit specified for the inverter. – Measure the ambient temperature. – Lower the ambient temperature by improving the ventilation. |
| OH4 Motor overheat (PTC/NTC thermistor) | Cause: Temperature of the motor has risen abnormally. Solution: 1. The temperature around the motor exceeded the range of the motor specification. – Measure the temperature around the motor. 2. Cooling system for the motor defective. – Check if the cooling system of the motor is operating normally. 3. The activation level of the PTC thermistor for motor overheat protection was set inadequately. – Check the PTC thermistor specifications and recalculate the detection voltage. 4. Settings for the PTC/NTC thermistor are improper. – Check the setting of the thermistor mode selection. |
| FUS/FU5 Fuse blown | Cause: The fuse inside the inverter blew. Solution: 1. The fuse blew because of a short-circuiting inside the inverter. – Check whether there has been any excess surge or noise coming from outside. – Take measures against surges and noise. – Have the inverter repaired. |
| PbF Charger circuit fault | Cause: The magnetic contactor for short-circuiting the resistor for charging failed to work. Solution: Control power was not supplied to the magnetic contactor intended for short-circuiting the charging resistor. 1. Check whether, in normal connection of the main circuit (not connection via the DC link bus), the connector on the power supply printed circuit board is not inserted to NC . – Insert the connector to FAN . 2. Check whether you have quickly turned the circuit breaker ON and OFF to confirm safety after cabling/wiring. – Wait until the DC link bus voltage has dropped to a sufficiently low level and then reset the current alarm, and turn ON the power again. (Do not turn the circuit breaker ON and OFF quickly.) (Turning ON the circuit breaker supplies power to the control circuit to the operation level (lighting LEDs on the keypad) in a short period. Immediately turning it OFF even retains the control circuit power for a time, while it shuts down the power to the magnetic contactor intended for short-circuiting the charging resistor since the contactor is directly powered from the main power. – Under such conditions, the control circuit can issue a turn-on command to the magnetic contactor, but the contactor not powered can produce nothing. This state is regarded as abnormal, causing an alarm.) |
| OL1 Motor 1 overload | Cause: Electronic thermal protection for motor 1 activated. Solution: 1. The electronic thermal characteristics do not match the motor overload characteristics. – Check the motor characteristics. 2. The activation level for the electronic thermal protection was not appropriate. – Check the continuous allowable current of the motor 3. The specified acceleration/ deceleration time was too short. – Recalculate the acceleration/deceleration torque and time needed for the load, based on the moment of inertia for the load and the acceleration/deceleration time. 4. Overload. – Measure the output current. |
| OLU Inverter overload | Cause & Solution: Temperature inside inverter rose abnormally. 1. The load is too heavy or locked-rotor occurs on the motor. – Reduce the load or check motor and mechanical conditions. 2. The rated AC drive power is low. – Replace the drive by one with higher rated power. 3. Temperature around the inverter exceeded that of inverter specifications. – Measure the temperature around the inverter. |
| Er1 Memory error | Cause: Error occurred in writing the data to the memory in the inverter. Solution: 1. While the inverter was writing data (especially initializing data), power supply was turned off and the voltage for the control circuit dropped. – Check if pressing the PGR/RESET key resets the alarm after the function code data are initialized by setting the data of H03 to 1 – Return the initialized function code data to their previous settings, then restart the operation. 2. A high intensity noise was given to the inverter while data (especially initializing data) was being written. – Check if appropriate noise control measures have been implemented (e.g., correct grounding and routing of control and main circuit wires). – Improve noise control. Alternatively, return the initialized function code data to their previous settings, then restart the operation. 3. The control circuit failed. – Initialize the function code data by setting H03 to 1, then reset the alarm by pressing the PGR/RESET key and check that the alarm goes on. – This problem was caused by a problem of the printed circuit board (PCB) (on which the CPU is mounted). |
| Er2 Remote keypad communications error | Cause: A communications error occurred between the keypad and the inverter. Solution: 1. Break in the communications cable or poor contact. – Check continuity of the cable, contacts and connections. – Replace the cable. 2. A high intensity noise was given to the inverter. – Check if appropriate noise control measures have been implemented (e.g., correct grounding and routing of control and main circuit wires). – Improve noise control. 3. The remote keypad malfunctioned. – Check that alarm er2 does not occur if you connect another remote keypad to the inverter. – Replace the remote keypad. 4. The RS-485 communications card malfunctioned. – Check that alarm er2 occurs even if you connect another remote keypad to the inverter. – Replace the keypad. |
| Er3 CPU error | Cause: A CPU error (e.g. erratic CPU operation) occurred. Solution: 1. A high intensity noise was given to the inverter. – Check if appropriate noise control measures have been implemented (e.g. correct grounding and routing of control and main circuit wires). – Improve noise control. |
| Er4 Option card communications error | Cause: A communications error occurred between the option card and the inverter. Solution: 1. There was a problem with the connection between the bus option card and the inverter. – Check whether the connector on the bus option card is properly mating with the connector of the inverter. – Reload the bus option card into the inverter. 2. There was a high intensity noise from outside. – Check whether appropriate noise control measures have been implemented (e.g. correct grounding and routing of control and main circuit wires and communications cable). – Reinforce noise control measures. |
| Er5 Option card error | Cause: An error detected by the option card. Refer to the instruction manual of the option card for details. |
| Er6 Incorrect operation error | Cause: An error occurred due to incorrect operation of the motor. You incorrectly operated the inverter. Solution: 1. The STOP key was pressed when H96 = 1 or 3. Even though a run command was present at the input terminal or the communication port, the inverter was forced to decelerate to stop and er6 was displayed. – If this was not intended, check the setting of H96. 2. The start check function was activated when H96 = 2 or 3. When one of the following conditions occurred while a run command was present at the input, the inverter did not run and er6 was displayed: – The power was switched on – An alarm was released – The inverter was switched to link command LE operation. Review the running sequence to avoid input of the run command when er6 has occurred. If this was not intended, check the setting of H96. (To reset the alarm, turn the run command off.) |
| Er7 Tuning error | Cause: Auto-tuning failed. Solution: 1. A phase was missing (There was a phase loss) in the connection between the inverter and the motor. – Properly connect the motor to the inverter. 2. V/f or the rated current of the motor was not properly set. 3. The connection between the inverter and the motor was too long. – Check whether the connection length between the inverter and the motor is not exceeding 50m. – Review, and if necessary, change the layout of the inverter and the motor to shorten the connection wire. 4. The rated capacity of the motor was significantly different from that of the inverter. – Check whether the rated capacity of the motor is smaller than that of the inverter by three or more orders of class or larger by two or more orders of class. – Check whether it is possible to replace the inverter with one with an appropriate capacity. 5. The motor was a special type such as a high-speed motor. |
| Er8 RS-485 communications error | Cause: A communications error occurred during RS-485 communications. Solution: 1. Host controllers (e.g., PLCs and personal computers) did not operate due to incorrect settings and/or defective software/hardware. – Check the controllers. – Remove the cause of the controller error. 2. RS-485 converter did not operate due to incorrect connections and settings, or hardware defective. – Check the RS-485 converter (e.g., check for poor contact). – Change the various RS-485 converter settings, reconnect the wires, or replace the converter with a recommended device as appropriate. 3. Broken communications cable or poor contact. – Check continuity of the cable, contacts and connections. – Replace the cable. 4. Even though no response error detection time has been set, communications did not occur cyclically. – Check the host controllers. – Change the settings of host controller software, or make the no response error detection time invalid. 5. A high intensity noise was given to the inverter. – Check if appropriate noise control measures have been implemented (e.g., correct grounding and routing of control and main circuit wires). – Improve noise control. – Improve noise reduction measures on the host side. – Replace the relay converter with a recommended insulated converter. |
| ErP RS-485 communications error | Cause: A communications error occurred during RS-485 communications. Solution: 1. Host controllers (e.g., PLCs and personal computers) did not operate due to incorrect settings and/or defective software/hardware. – Check the controllers. – Remove the cause of the controller error. 2. RS-485 converter did not operate due to incorrect connections and settings, or hardware defective. – Check the RS-485 converter (e.g., check for poor contact). – Change the various RS-485 converter settings, reconnect the wires, or replace the converter with a recommended device as appropriate. 3. Broken communications cable or poor contact. – Check continuity of the cable, contacts and connections. – Replace the cable. 4. Even though no response error detection time has been set, communications did not occur cyclically. – Check the host controllers. – Change the settings of host controller software, or make the no response error detection time invalid. 5. A high intensity noise was given to the inverter. – Check if appropriate noise control measures have been implemented (e.g., correct grounding and routing of control and main circuit wires). – Improve noise control. – Improve noise reduction measures on the host side. – Replace the relay converter with a recommended insulated converter. |
| ErF Data save error during undervoltage | Cause: The inverter was unable to save data such as the frequency commands, timer operation time, and PID process command set through the keypad when the power was switched off. Solution: 1. The control circuit voltage dropped suddenly while data was being saved when the power was turned off, because the DC link bus was rapidly discharged. – Check how long it takes for the DC link bus voltage to drop to the preset voltage when power is turned off. – Remove whatever is causing the rapid discharge of the DC link circuit. After pressing the PGR/RESET key and releasing the alarm, set, using a remote keypad, the data of the relevant function codes (such as the frequency commands, timer operation time, and PID process command) back to the original values and then restart the operation. 2. A high intensity noise affected the operation of the inverter while data was being saved when the power was turned off. – Check if appropriate noise control measures have been implemented (e.g., correct grounding and routing of control and main circuit wires). – Improve noise control. After pressing the PGR/RESET key and releasing the alarm, set, using a remote keypad, the data of the relevant function codes (such as the frequency commands, timer operation time, and PID process command) back to the original values and then restart the operation. 3. The control circuit failed. Check if erf occurs each time power is switched off. – This problem was caused by a problem of the printed circuit board (PCB) (on which the CPU is mounted). |
| ErH Hardware error | Cause: An error occurred in the LSI on the power printed circuit board (power PCB). Solution: 1. The capacity is not set properly on the control printed circuit board. – The inverter capacity needs to be modified again. 2. The contents of the memory on the power supply printed circuit board are corrupted. – The power supply printed circuit board needs to be replaced. 3. Connection problem between the control printed circuit board and the power supply printed circuit board – Either the control printed circuit board or the power supply printed circuit board needs to be replaced. |
| CoF Terminal [C1] wire break | Cause: The terminal [C1] wire is broken. Solution: 1. The wiring to the terminal [C1] is broken. – Check whether the wire is broken. – Replace the wire. 2. The current signal input to [C1] has fallen to 2 mA or less. – Check the main inverter unit connection and wiring and transmission-side equipment. – Review function code (H91) data. |
| ECL Customizable logic error | Cause: An ECL occurred due to a customizable logic setting error. Solution: 1. The customizable logic operation selection setting was changed during operation. – Check whether the customizable logic operation selection (function code U00) was changed during operation. – Do avoid potential hazards, do not change the customizable logic operation selection during operation. |
| ECF Enable circuit error | Cause: A circuit error was detected when diagnosing the enable circuit status. Solution: 1. Interface board contact defect Check whether the interface board is securely attached to the unit. – The alarm will be cleared by turning ON the power again. 2. Enable circuit logic error Check whether outputs from safety switches and so on are input to both terminals EN1 and EN2 with the same logic (High/High or Low/Low). – The alarm will be cleared by turning ON the power again. 3. An enable circuit (safety stop circuit) fault (single fault) was detected. – If unable to clear the error with the above procedures, the inverter condition is abnormal. |
| PVn/PUn PID feedback wire break | Cause: The PID feedback wire is broken. Solution: 1. The PID feedback signal wire is broken. – Check whether the PID feedback signal wires are connected correctly. – Check whether the PID feedback signal wires are connected correctly. Or, tighten up the related terminal screws. – Check whether any contact part bites the wire sheath. 2. PID feedback related circuit affected by strong electrical noise. – Check if appropriate noise control measures have been implemented (e.g., correct grounding and routing of signal wires, communication cables, and main circuit wires). – Implement noise control measures. – Separate the signal wires from the main power wires as far as possible. -The PID control feedback error upper limit (J129, J229) settings are too high. – Review the set feedback value. 3. The function code setting is not appropriate. – The PID control feedback error lower limit (J130, J230) settings are too low. – Review the set feedback value. |
| PV1/PU1 PID feedback wire break | Cause: The PID feedback wire is broken. Solution: 1. The PID feedback signal wire is broken. – Check whether the PID feedback signal wires are connected correctly. – Check whether the PID feedback signal wires are connected correctly. Or, tighten up the related terminal screws. – Check whether any contact part bites the wire sheath. 2. PID feedback related circuit affected by strong electrical noise. – Check if appropriate noise control measures have been implemented (e.g., correct grounding and routing of signal wires, communication cables, and main circuit wires). – Implement noise control measures. – Separate the signal wires from the main power wires as far as possible. -The PID control feedback error upper limit (J129, J229) settings are too high. – Review the set feedback value. 3. The function code setting is not appropriate. – The PID control feedback error lower limit (J130, J230) settings are too low. – Review the set feedback value. |
| PV2/PU2 PID feedback wire break | Cause: The PID feedback wire is broken. Solution: 1. The PID feedback signal wire is broken. – Check whether the PID feedback signal wires are connected correctly. – Check whether the PID feedback signal wires are connected correctly. Or, tighten up the related terminal screws. – Check whether any contact part bites the wire sheath. 2. PID feedback related circuit affected by strong electrical noise. – Check if appropriate noise control measures have been implemented (e.g., correct grounding and routing of signal wires, communication cables, and main circuit wires). – Implement noise control measures. – Separate the signal wires from the main power wires as far as possible. -The PID control feedback error upper limit (J129, J229) settings are too high. – Review the set feedback value. 3. The function code setting is not appropriate. – The PID control feedback error lower limit (J130, J230) settings are too low. – Review the set feedback value. |
| PVA External PID control 1 feedback error | Cause: External PID control 1 feedback error. Solution: 1. The PID feedback signal wire is broken. – Check whether the PID feedback signal wires are connected correctly. – Check whether the PID feedback signal wires are connected correctly. Or, tighten up the related terminal screws. – Check whether any contact part bites the wire sheath. 2. PID feedback related circuit affected by strong electrical noise. – Check if appropriate noise control measures have been implemented (e.g., correct grounding and routing of signal wires, communication cables, and main circuit wires). – Implement noise control measures. – Separate the signal wires from the main power wires as far as possible. – The external PID control feedback error upper limit (J529, J629, J679) settings are too high. – Review the set feedback value. 3. The function code setting is not appropriate. – The external PID control feedback error lower limit (J530, J630, J680) settings are too low. – Review the set feedback value. |
| PVB External PID control 2 feedback error | Cause: External PID control 2 feedback error. Solution: 1. The PID feedback signal wire is broken. – Check whether the PID feedback signal wires are connected correctly. – Check whether the PID feedback signal wires are connected correctly. Or, tighten up the related terminal screws. – Check whether any contact part bites the wire sheath. 2. PID feedback related circuit affected by strong electrical noise. – Check if appropriate noise control measures have been implemented (e.g., correct grounding and routing of signal wires, communication cables, and main circuit wires). – Implement noise control measures. – Separate the signal wires from the main power wires as far as possible. – The external PID control feedback error upper limit (J529, J629, J679) settings are too high. – Review the set feedback value. 3. The function code setting is not appropriate. – The external PID control feedback error lower limit (J530, J630, J680) settings are too low. – Review the set feedback value. |
| PVC External PID control 3 feedback error | Cause: External PID control 3 feedback error. Solution: 1. The PID feedback signal wire is broken. – Check whether the PID feedback signal wires are connected correctly. – Check whether the PID feedback signal wires are connected correctly. Or, tighten up the related terminal screws. – Check whether any contact part bites the wire sheath. 2. PID feedback related circuit affected by strong electrical noise. – Check if appropriate noise control measures have been implemented (e.g., correct grounding and routing of signal wires, communication cables, and main circuit wires). – Implement noise control measures. – Separate the signal wires from the main power wires as far as possible. – The external PID control feedback error upper limit (J529, J629, J679) settings are too high. – Review the set feedback value. 3. The function code setting is not appropriate. – The external PID control feedback error lower limit (J530, J630, J680) settings are too low. – Review the set feedback value. |
| Pdr Dry pump protection | Cause: Drought conditions were detected during PID control. Solution: 1. The water level in the water tank has dropped to the drought position. – Check whether the water level in the water tank is sufficient. – Check whether the correct amount of water is being supplied to the water tank. – Check whether the motor-operated value is closed. 2. Water is leaking from the pipes or pump system. – Check whether water is leaking from the pump system or from around the pipes. – Check whether water is leaking from the pump itself. – Check for cracks in the pipes and so on, and check whether water is leaking from the connections between pipes. Increase the tightening at the pipe connections. – Check whether the drought protection (detection current) (J177, J277) setting is too high. – Review the set current value. 3. The function code setting is not appropriate. – Check whether the drought protection (deviation) (J178, J278) setting is too small. – Review the set amount of deviation. 4. The function code setting for the flow sensor is not appropriate. (This applies only when drought protection (flow sensor) (J179, J279) is set to “1: Operate”.) – If inputting a flow sensor signal by analog input, the flow sensor OFF level (J165) is too high. – Review the set OFF level setting. 5. The flow sensor signal wiring is damaged. – Check whether the flow sensor signal wire is connected properly. – Check whether the flow sensor signal wire is connected properly. Or alternatively, tighten the screws. – Check whether the connection coating is caught. |
| roC Control of maximum starts per hour | Cause: A PID control insufficient water stoppage occurred frequently. Solution: 1. PID feedback signal wire contact defect – Check whether the PID feedback signal wire is connected properly. – Check whether the PID feedback signal wire is connected properly. Or alternatively, tighten the screws. – Check whether the connection coating is caught. 2. An accumulator (hydraulic regeneration) fault occurred due to such reasons as the lifetime being reached. – Check the accumulator parts. – Replace the accumulator. |
| PoL End of curve protection | Cause: A large water quantity condition was detected during PID control. Solution: 1. The PID feedback signal wiring is damaged. – Check whether the PID feedback signal wire is connected properly. – Check whether the PID feedback signal wire is connected properly. Or alternatively, tighten the screws. – Check whether the connection coating is caught. 2. There is insufficient pump capacity or there are not enough pumps. – Check whether the required amount of supply water is being supplied properly. – Increase the number of pumps. – Increase the pump capacity. – Check whether the large water quantity protection (detection current) (J183) setting is too low. – Review the set current value. 3. The function code setting is not appropriate. – Check whether the large water quantity protection (deviation) (J184) setting is too small. – Review the set amount of deviation. |
| rLo Anti jam | Cause: Impurities became trapped in the pump impeller, and an overcurrent was detected. Solution: 1. Impurities are trapped in the pump impeller. – Check for any impurities in the suction side water tank or well. – Check for any impurities inside the pump. – Eliminate any impurities from the water tank or well as best as possible. 2. A pump fault occurred due to such reasons as the lifetime being reached. – Check the pump parts. – Check whether an abnormal noise is being emitted by the pump. – Check whether the pump bearings are overheating. |
| FoL Filter clogging error | Cause: An overload condition was detected during PID control. Solution: 1. The filter of the fan being driven by the inverter is clogged with dust. – Check whether the fan filter is clogged with dust. – Check whether the filter is clogged with dust. – Clean or replace the filter. 2. A fault occurred in the fan being driven by the inverter due to the fan’s service life expired, etc. – Check the fan parts. – Check whether an abnormal noise is being emitted by the fan. – Check whether the fan bearings are overheating. – Check whether the filter clogging (load resistance current) (J190) setting is too low. – Check the set current value. 3. The function code setting is not appropriate. – Check whether the filter clogging (load resistance PV signal) (J191) setting is too low. – Check the set feedback value. |
| LoK Password protection (inverter lock) | Cause: An incorrect user password was entered more than the specified number of times. Solution: 1. User password 1 or 2 was entered incorrectly more than the specified number of times. – Delete the password setting. – Delete the password with the all clear command (PRG >5 > 2 >10). When doing so, all inverter settings will also be initialized simultaneously. – Reset the password. – To clear the Lok alarm while retaining the inverter settings, notify Fuji Electric and append the clear application number (PRG > 5 > 8). We will ensure that no illegal operations have been performed, and then issue an alarm clear code. |
| Err Mock alarm | Cause: The LCD displays the alarm err. Solution: 1. The STOP+SET keys were held down for more than 5 seconds. – To escape from this alarm state, press the RESET key. 2. H45 was set to “1”. – Press the RESET key to rese |
| Lob Low battery | Cause: The voltage in the battery used to protect date information is low. Solution: 1. Battery connector contact defect Check whether the battery is securely attached to the connector on the unit board. – If normal battery voltage is detected, the cause of the problem will be cleared, and resetting will be possible. 2. Battery degradation, battery defect – Check whether the battery is degraded. – Replace the battery with a new one. |
| dtL Date information loss | Cause: Date information set in the inverter was lost. Solution: 1. It was not possible to protect the date information when the inverter power was turned OFF. – Check whether the date information protection battery is properly connected. – Check the battery connection, and then reset the date. 2. The date information is abnormal. – The clock function in this product is programmed to run until 23:59:59 on December 31, 2099. The date count will be stopped if this date is exceeded. – Set the correct date again. |