Fuji FRENIC-MEGA (G2) Drive Fault Codes
| Fault Code | Cause & Solution |
|---|---|
| CA1 User-defined alarm | Cause: An alarm defined with customizable logic occurred. Solution: 1. An error is displayed if the alarm conditions defined by the user with customizable logic are met. (This is not an error at the inverter itself.) – Check the input/output status in accordance with the alarm conditions set with customizable logic. |
| CA2 User-defined alarm | Cause: An alarm defined with customizable logic occurred. Solution: 1. An error is displayed if the alarm conditions defined by the user with customizable logic are met. (This is not an error at the inverter itself.) – Check the input/output status in accordance with the alarm conditions set with customizable logic. |
| CA3 User-defined alarm | Cause: An alarm defined with customizable logic occurred. Solution: 1. An error is displayed if the alarm conditions defined by the user with customizable logic are met. (This is not an error at the inverter itself.) – Check the input/output status in accordance with the alarm conditions set with customizable logic. |
| CA4 User-defined alarm | Cause: An alarm defined with customizable logic occurred. Solution: 1. An error is displayed if the alarm conditions defined by the user with customizable logic are met. (This is not an error at the inverter itself.) – Check the input/output status in accordance with the alarm conditions set with customizable logic. |
| CA5 User-defined alarm | Cause: An alarm defined with customizable logic occurred. Solution: 1. An error is displayed if the alarm conditions defined by the user with customizable logic are met. (This is not an error at the inverter itself.) – Check the input/output status in accordance with the alarm conditions set with customizable logic. |
| CoF Current input terminals [C1] [C2] signal line break | Cause: A current input signal line break occurred. Solution: 1. Current input command wire break: – Check whether current is flowing to current input terminals [C1] and [C2]*. ➔ Terminal [C1] wire break detection [Subcode: 1] Terminal [C2]* wire break detection [Subcode: 2] Terminal [C1], [C2]* wire break detection [Subcode: 3] *: When equipped with OPC-AIO (option). 2. The inverter was affected by strong electrical noise. – Check noise countermeasures (grounding condition, signal line and communication cable/main circuit wiring installation method, etc.) ➔ Enhance noise countermeasures. ➔ Keep the main circuit wiring and control circuit wiring as far apart as possible. |
| dba Braking transistor error | Cause: A braking transistor error is detected. – The braking transistor is broken. Solution: – Check whether resistance of the braking resistor is correct or there is a misconnection of the resistor. |
| dbh Braking resistor overheated | Cause: Problem The electronic thermal protection for the braking resistor has been activated. Solution: 1. Braking load is too heavy. [Subcode: 0] – Reconsider the relationship between the braking load estimated and the real load. ➔ Lower the real braking load. ➔ Review the selection of the braking resistor and increase the braking capability. Modification of related function codes data (F50, F51, and F52) may be also required. 2. Specified deceleration time is too short. – Recalculate the deceleration torque and time needed for the load currently applied, based on a moment of inertia for the load and the deceleration time. ➔ Increase the deceleration time (function codes F08, E11, E13, E15, and H56). ➔ Review the selection of the braking resistor and increase the braking capability. Modification of related function codes data (F50, F51, and F52) may be also required. 3. Incorrect setting of function code data F50, F51, and F52. [Subcode: 0] – Recheck the modes of the braking resistor. – If using a braking resistor (option) on a model (FRN0046G2S-2G/ FRN0023G2■-4G or below) with built-in braking resistor, check whether the braking resistor electronic thermal overload relay setting been changed. ➔ Review data of function codes F50, F51, and F52, then modify them if required. |
| ECF EN circuit failure | Cause: Enable circuit state was diagnosed and a circuit failure was detected. Solution: 1. Contact defect on interface-PCB – Confirm that the interface-PCB is firmly mounted on the body. – Alarm is released by turning on again. 2. Enable circuit logic failure – Confirm that outputs from safety switch etc. are inputted by the same logic (High/High or Low/Low) with EN1 terminal/EN2 terminal. – Alarm is released by turning on again. 3. A failure (single failure) of enable circuit (safety stop circuit) was detected. – If the circuit failure is not removable by the procedures above, the inverter is out of order. |
| ECL Customizable logic failure | Cause: A setting failure of customizable logic was detected. Solution: 1. Setting of the selection of customizable logic operation was changed during operation. – Check whether the selection (Function code U00) of customizable logic operation is changed during operation. – Do not change the selection of customizable logic operation during operation to prevent a danger. |
| EF Ground fault | Cause: A ground fault current flew from the output terminal of the inverter. Solution: 1. Inverter output terminal(s) grounded (ground fault). – Disconnect the wiring from the output terminals [U], [V] and [W] and perform a Megger test for the inverter and the motor. – Remove the grounded parts (including replacement of the wires, relay terminals and motor). |
| 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 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 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 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 Review the running sequence to avoid input of the run command when er6 has occurred. |
| 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. |
| Erd Step-out detection /detection failure of magnetic pole position at startup | Cause: Synchronous motor step-out was detected. The magnetic pole position at startup failed to be detected. Solution: 1. Function code settings do not agree with the motor characteristics. – Check whether function codes F04*, F05*, P01*, P02*, P03*, P60*, P61*, P62*, P63*, P64* agree with the motor constants. ➔ Perform auto-tuning. 2. Magnetic pole position detection method is not appropriate. – Confirm that the magnetic pole position detection mode matches the motor type. ➔ Match the magnetic pole position detection mode selection (function code P30*) to the motor type. 3. Starting frequency (continuation time) (function code F24) is insufficient. – Check whether a starting frequency (continuation time) (function code F24*) is set optimally, after setting the magnetic pole position detection mode selection (function code P30*) to “0” or “3.” ➔ Set a period of time during which motor can rotate by one or more revolutions. F24* ≥ P01*/2/F23* (P01*: Number of poles, F23*: Starting frequency) 4. Starting torque is insufficient. – Check the data of acceleration times (function codes F07, E10, E12, E14) and a current command value on a start (function code P74*). ➔ Change the acceleration time to match the load. ➔ Increase the current command value at startup. ➔ Increase the control switching level (function code P89) setting. 5. Load is small. – Check the data of a reference current at starting (function code P74*). ➔ Decrease the reference current at starting. Set it to 80% or lower when running a motor single unit in a test run etc. 6. A phase was missing in the connection between the inverter and the motor. ➔ Properly connect the motor to the inverter. |
| ErC Magnetic pole position detection error | Cause: When performing vector control with sensor (synchronous motors), an error occurred when performing synchronous motor magnetic pole position detection. Solution: 1. The inverter settings are not appropriate. – Check whether the motor being used, the existence and type of the speed/magnetic pole position sensor, the control method (F42*) and feedback pulse input method (d14), and the feedback pulse count (d15) are consistent. ➔ Check the machine configuration (motor speed/magnetic pole position sensor type and specifications), and set F42*, d14, and d15 correctly. – Ensure that the magnetic pole position detection method selection (P30*) has been set to either “0” or “3”, and that the magnetic pole position sensor offset (P95*) is not “999 (offset not adjusted)”. ➔ Set P95* correctly. (Auto tuning is also possible. – See “4.7.2 [3] Synchronous motor tuning method”.) 2. There is a problem with the speed/magnetic pole position sensor connection. Check for speed/magnetic pole position sensor output wiring contact defects, and check the AB phase or UVW phase sequence. ➔ Connect the feedback input option card and speed/magnetic pole position sensor correctly. 3. The motor rotation direction and sensor output do not match. Check for motor wiring contact defects, and check the phase sequence. ➔ Connect the motor correctly to the inverter. 4. There is a problem with the option card connection. – Check whether the connector on the option card is properly engaged with that of the inverter. ➔ Reinsert the option card into the inverter. 5. The inverter was affected by strong electrical noise. – Check noise countermeasures (grounding condition, signal line and communication cable/main circuit wiring installation method, etc.) ➔ Take noise countermeasures. |
| ErE Speed inconsistency Excessive speed deviation | Cause: An excessive deviation appears between the speed command and the detected speed. Solution: 1. Incorrect setting of function code data. – Check the motor parameter “Number of poles” (P01*). – Specify the P01* data in accordance with the motor to be used. 2. Overload. Measure the inverter output current. – Reduce the load. – Check whether any mechanical brake is applied. – Release the mechanical brake. 3. The motor speed does not increase due to the current limiter operation. – Check the data of function code F44 (Current limiter (Level)). – Change the F44 data correctly. Or, set the F43 data to “0” (Disable) if the current limiter operation is not needed. – Check the data of the function codes (F04*, F05*, P01*-P12*) to see if V/f is set correctly. – Match the V/f pattern setting with the motor ratings. – Change the function code data in accordance with the motor parameters. 4. Function code settings do not match the motor characteristics. – Confirm that P01*, P02*, P03*, P06*, P07*, P08*, P09*, P10*, P12* match the motor constants. – Perform auto-tuning of the inverter, using the function code P04*. 5. Wiring to the motor is incorrect. Check the wiring to the motor. – Connect the inverter output terminals U, V, and W to the motor input terminals U, V, and W, respectively. 6. The motor speed does not increase due to the torque limiter operation. – Check the data of F40 (Torque limiter (Level)). – Change the F40 data correctly. Or, set the F40 data to “999” (Disable) if the torque limiter operation is not needed. 7. The wire between the pulse generator (PG) and the option card is broken or incorrect. – Check whether the pulse generator (PG) is correctly connected to the option card or any wire is broken. – Check whether the PG is connected correctly. Or, tighten the related terminal screws. |
| 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. |
| Ero Positioning control error | Cause: Excessive position deviation occurred on servo lock / position control. Solution: 1. Insufficient gain in positioning control system (servo lock) – Readjust the settings of J97 (Servo lock (Gain)) and d03 (Speed control 1 P (Gain)). 2. Incorrect control completion width (servo lock) – Check whether the setting of J99 (Servo lock (Completion range)) is correct. – Correct the setting of J99. 3. Position deviation is excessive. (servo lock) – Check whether the excessive error detection level (d78) is set up properly. 4. Position deviation is excessive. (position control) – The position feedback pulses are not received. – Check whether the PG is connected correctly. Or, tighten the related terminal screws. – Check whether any contact part bites the wire sheath. – Replace the wire / pulse generator. |
| Err Simulated failure | Cause: The LED displays the alarm err. Solution: 1. Keep key STOP + FUNC/Data key pressed for five seconds or longer. – To escape from this alarm state, press the PGR/RES key. |
| 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. |
| FAL DC fan lock | Cause: An inverter internal DC fan lock was detected. Solution: 1. Inverter internal cooling fan error – Failure of the air circulation fan inside the inverter (FRN0215G2S-2G/FRN0180G2■-4G or above) ➔ Replace the cooling fan. |
| 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. |
| Lok/LoP Password protection | Cause: The wrong user password was entered more than the prescribed number of times. Solution: User password 1 or 2 was entered incorrectly more than the prescribed number of times. – Clear the alarm. ➔ Turn OFF the inverter power, and then turn it back ON again. |
| 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. |
| nrb NTC wire break error | Cause: A wire break is found in the NTC thermistor detection circuit. Solution: 1. The NTC thermistor cable is broken. Check whether the motor cable is broken. – Replace the motor cable. 2. The temperature around the motor is extremely low (lower than -30°C). – Measure the temperature around the motor. – Reconsider the use environment of the motor. 3. The NTC thermistor is broken. Measure the resistance of the NTC thermistor. – Replace the motor. |
| 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. |
| OH1 Cooling Fin overheat | Cause & Solution: Temperature around heat sink has risen abnormally. 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 | 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. |
| OH6 Charging resistor overheat | Cause: Temperature of the charging resistor inside the inverter has risen abnormally. Solution: 1. The inverter power is turned ON and OFF frequently. – Suppress the inverter power ON/OFF cycles. – Turn ON and OFF the inverter power once or less per 30 min. 2. The inverter power is not turned ON and OFF frequently. – Check that this alarm always occurs when the inverter power is turned ON. – The charging circuit of the inverter is faulty. |
| OLn Overload of motor 1 through 3 | Cause: Electronic thermal protection for motor 1, 2, or 3 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. |
| 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. |
| OL2 Motor 2 overload | Cause: Electronic thermal protection for motor 2 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. |
| OL3 Motor 3 overload | Cause: Electronic thermal protection for motor 3 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: Electronic thermal overload protection for inverter activated. Solution: 1. The surrounding temperature exceeded the inverter’s mode limit. Measure the surrounding temperature. ➔ Lower the temperature (e.g., ventilate the panel where the inverter is mounted). 2. Excessive torque boost specified (F09*) Check whether decreasing the torque boost (F09*) does not stall the motor. ➔ If no stall occurs, decrease the F09* data. 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 of the load and the acceleration/deceleration times. ➔ Increase the acceleration/deceleration times (F07, F08, E10 to E15, and H56). 4. Overload Measure the inverter output current. ➔ Reduce the load (e.g. Use the overload early warning (E34) and reduce the load before the overload protection is activated.) In winter, the load tends to increase. ➔ Decrease the Carrier frequency (function code F26). ➔ Enable overload prevention control (H70).。 5. Ventilation paths are blocked. Check if there is sufficient clearance around the inverter. ➔ Change the mounting place to ensure the clearance. Check if the fin is not clogged. ➔ Clean the fins. 6. Cooling fan’s airflow volume decreased due to the service life expired or failure. Check the cumulative run time of the cooling fan. ➔ Replace the cooling fan. |
| OPL Output phase loss | Cause: Output phase loss occurred. Solution: 1. nverter output wires are broken. – Measure the output current. 2. The motor winding is broken. – Measure the output current. 3. The inverter output terminals or motor input terminals are weakly tightened. – Check if any screws on those terminals have become loose. 4. A single-phase motor has been connected. – Single-phase motors cannot be used. |
| OS/O5 Overspeed | Cause: Motor rotated at excessive speed (When motor speed ≥ (F03 x 1.2)) Solution: 1. Incorrect setting of function code data. – Check the motor parameter “Number of poles” (P01*). ➔ Specify the P01* data in accordance with the motor to be used. – Check the maximum frequency setting (F03*). ➔ Specify the F03* data in accordance with the output frequency. – Check the speed limiting function (d32, d33) setting. ➔ Disable the speed limiting function (d32, d33). – Check the overspeed detection level (d35) setting. ➔ Set the overspeed detection level (d35) to 120%. 2. The speed regulator gain is insufficient. – Check whether the speed has overshot when performing high-speed operation. ➔ Increase the speed regulator gain (d03*). (Depending on the situation, it may be necessary to change the filters or adjust the integral time.) 3. Noise is superimposed on the PG signal. – Check the PG signal input monitor, and check noise countermeasures (grounding condition, signal line/main circuit wiring installation method, etc.) ➔ Take noise countermeasures. For details, refer to Appendix A. 4. The output frequency and motor rotation speed exceeded 599 Hz. – If running the motor near 599 Hz, check whether the acceleration time is too short, whether there are any load fluctuations. and whether the speed regulator gain (d03*) and integral time (d04*) are appropriate. ➔ Reduce the operating frequency. |
| 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. |
| PbF Charger circuit fault | Cause: The magnetic contactor for short-circuiting the charging resistor failed to work. (For 200 V class series of 37 kW or above and those of 75 kW or above). Solution: 1. No control power was supplied to the magnetic contactor (MC) intended for short-circuiting the charging resistor. – Check that, in normal connection of the main circuit (not a connection via the DC link bus), the connector (CN R) on the power printed circuit board (power PCB) is not inserted to NC . 2. Breaks in wiring to the main power input terminals. – Measure the input voltage. |
| PG PG wire break | Cause: The pulse generator (PG) wire has been broken somewhere in the circuit. Solution: 1. PG(Z phase) wire break under master-follower operation. Check whether the pulse generator (PG) is correctly connected to the option card or any wire is broken. ➔ Check whether the PG is connected correctly. Or, tighten the related terminal screws. ➔ Check whether the coating is trapped in the connecting part. ➔ Replace the wire(s). 2. The inverter was affected by strong electrical noise. Check noise countermeasures (grounding condition, signal line and communication cable/main circuit wiring installation method, etc.) ➔ Take noise countermeasures. ➔ Keep the main circuit wiring and control circuit wiring as far apart as possible. |
| dO/D0 Excessive positioning deviation | Cause: The position deviation during position control was excessive. 1. Encoder wire break – Check whether an encoder wire break has occurred. 2. Encoder rotation direction (wiring phase sequence), motor rotation direction (inverter output wiring phase sequence) mismatch – Connect and set so that all directions match. – Review the setting values for d14 to d17 and H190. 3. The deviation overflow setting value is too small. – Review the setting values for d223 and d224. – Increase the setting value if too small. 4. The position control gain is too small. – Review the setting values for d203 and d204. – Increase the setting value if too small. 5. The speed control gain is too small. – Review the setting values for d03 (A45, b45, r45). – Increase the setting value if too small. 6. Torque limiting has been applied. – If torque limiting is triggered, it will not be possible to perform position control or speed control correctly. Take the following countermeasures to prevent torque limiting being applied. ∙ Reduce the load. ∙ Review the acceleration/deceleration time. ∙ Review the machine configuration such as the reduction ratio and motor capacity to reduce the load. |
| CnT Machine life | Inverter life (Number of startups) – This is displayed when the number of times that the motor is started reaches the number of times set with function code H79 (maintenance setting startup count). – Furthermore, the current startup count can be checked at function code H44 (startup count), and therefore the H44 data should be set to “0000” to reset the count. |
| iGb IGBT lifetime alarm | IGBT power cycle life – The element temperature power cycle life for the main circuit semiconductor IGBT due to frequent acceleration and deceleration stoppages is estimated, and this is displayed before the design life is reached. |
| lif Lifetime alarm | Lifetime alarm – It is judged that the service life of any one of the capacitors (DC link bus capacitors or electrolytic capacitors on PCBs), the cooling fan, or the IGBT has expired. |
| OH Cooling fin overheat early warning | Cooling fin overheat early warning – This is displayed as a warning before cooling fin overheating trip 0H1 occurs. |
| Ol Motor overload early warning | Motor overload early warning This is displayed as a warning before the motor overload 0l1 alarm occurs. Set the current at which this is triggered at overload warning operation level (E34). – Check whether the actual motor current is greater than the current set at E34. |
| pid PID alarm output | PID alarm output – This is displayed if a PID control warning (absolute value warning, deviation warning) occurs. Refer to Chapter 5 “FUNCTION CODES ” – “5.3.8 J Codes (Applied functions)” (J11 to J13 PID Control (Select warning output)). |
| pTC PTC thermistor activated | Thermistor detection (PTC) – This warning is displayed when the temperature detected with the motor PTC thermistor exceeds the operation level (H27) threshold value. Refer to “[ 33 ] 0H4 Motor protection (PTC thermistor)” for details on countermeasures. |
| rAf Cooling capability drop | Cooling capability drop – Drops in cooling capability due to the clogging of cooling fins with dust, etc., or drops in cooling fan air flow are detected and displayed. – Clean the cooling fins or replace the cooling fan as necessary. Depending on the usage conditions, cooling fin overheating protection OH1 may occur first. – By using cooling fin overheating early warning OH, an overheating early warning can be detected before cooling fin overheating protection OH1 occurs. |
| ref Reference loss | Command loss – If the analog frequency setting (terminals [12], [C1], [V2]) command drops rapidly to 10% or lower, a wire break is determined, and “ref” is displayed. Check the wiring. |
| rTe Machine life | Inverter life (Cumulative run time) – This is displayed when the motor cumulative running time reaches the time set with function code H78 (maintenance setting time). The motor cumulative running time can be checked at H94* (motor cumulative running time). Furthermore, the time can be reset by setting the H94* value to “0”. |
| UTl Low torque detection | Low torque detection – This is displayed when the output torque drops to the low torque detection level (E80) or below, and persists for the timer (E81) time or longer. |
| Lob Low battery warnig | The TP-A2SW multi-function keypad (option) remaining battery capacity is insufficient. ∙ Check whether the trip history date and time information has been lost. ∙ Refer to the TP-A2SW multi-function keypad instruction manual, and replace the battery (sold separately) and set the date and time information again. |