INVT GD270 Drive

INVT GD270 Drive Fault Codes:

Fault CodesCause & Solution
OUt1
Inverter
unit U
phase
protection		Cause:

1. The acceleration is too fast;
2. IGBT module fault;
3. Misacts caused by interference;
4. The connection of the driving wires is not good;
5. Grounding is not properly.

Solution:

1. Increase ACC time;
2. Change the power unit;
3. Check the driving wires;
4. Inspect external equipment and eliminate interference
OUt2
Inverter
unit V
phase
protection		Cause:

1. The acceleration is too fast;
2. IGBT module fault;
3. Misacts caused by interference;
4. The connection of the driving wires is not good;
5. Grounding is not properly.

Solution:

1. Increase ACC time;
2. Change the power unit;
3. Check the driving wires;
4. Inspect external equipment and eliminate interference
OUt3
Inverter
unit W
phase
protection		Cause:

1. The acceleration is too fast;
2. IGBT module fault;
3. Misacts caused by interference;
4. The connection of the driving wires is not good;
5. Grounding is not properly.

Solution:

1. Increase ACC time;
2. Change the power unit;
3. Check the driving wires;
4. Inspect external equipment and eliminate interference
OC1
Overcurrent
during
acceleration		Cause:

– The acceleration or deceleration is too fast;
– The voltage of the grid is too low;
– The power of the VFD is too low;
– The load transients or is abnormal;
– The grounding is short circuited or the output is phase loss;
– There is strong external interference;
– The overvoltage stall protection is not open.

Solution:

– Increase the ACC time;
– Check the input power;
– Select the VFD with a larger power;
– Check if the load is short circuited (the grounding short circuited or the wire short circuited) or the rotation is not smooth;
– Check the output configuration;
– Check if there is strong interference;
– Check the setting of related function codes
OC2
Overcurrent
during
deceleration		Cause:

– The acceleration or deceleration is too fast;
– The voltage of the grid is too low;
– The power of the VFD is too low;
– The load transients or is abnormal;
– The grounding is short circuited or the output is phase loss;
– There is strong external interference;
– The overvoltage stall protection is not open.

Solution:

– Increase the ACC time;
– Check the input power;
– Select the VFD with a larger power;
– Check if the load is short circuited (the grounding short circuited or the wire short circuited) or the rotation is not smooth;
– Check the output configuration;
– Check if there is strong interference;
– Check the setting of related function codes
OC3
Overcurrent
at constant
speed		Cause:

– The acceleration or deceleration is too fast;
– The voltage of the grid is too low;
– The power of the VFD is too low;
– The load transients or is abnormal;
– The grounding is short circuited or the output is phase loss;
– There is strong external interference;
– The overvoltage stall protection is not open.

Solution:

– Increase the ACC time;
– Check the input power;
– Select the VFD with a larger power;
– Check if the load is short circuited (the grounding short circuited or the wire short circuited) or the rotation is not smooth;
– Check the output configuration;
– Check if there is strong interference;
– Check the setting of related function codes
OV1/OU1
Overvoltage
during
acceleration		Cause:

– The input voltage is abnormal;
– There is large energy feedback;
– No braking components;
– Braking energy is not open.

Solution:

– Check the input power;
– Check if the DEC time of the load is too short or the VFD starts during the rotation of the motor or it needs to increase the energy consumption components;
– Install the braking components;
– Check the setting of related function codes.
OV2/OU2
Overvoltage
during
deceleration		Cause:

– The input voltage is abnormal;
– There is large energy feedback;
– No braking components;
– Braking energy is not open.

Solution:

– Check the input power;
– Check if the DEC time of the load is too short or the VFD starts during the rotation of the motor or it needs to increase the energy consumption components;
– Install the braking components;
– Check the setting of related function codes.
OV3/OU3
Overvoltage
at constant
speed		Cause:

– The input voltage is abnormal;
– There is large energy feedback;
– No braking components;
– Braking energy is not open.

Solution:

– Check the input power;
– Check if the DEC time of the load is too short or the VFD starts during the rotation of the motor or it needs to increase the energy consumption components;
– Install the braking components;
– Check the setting of related function codes.
UV
Bus
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.
OL1
Motor
overload		Cause:

– The voltage of the power supply is too low;
– The motor setting rated current is incorrect;
– The motor stall or load transients is too strong.

Solution:

– Check the power of the supply line;
– Reset the rated current of the motor;
– Check the load and adjust the torque lift.
OL2
VFD
overload		Cause:

– The acceleration is too fast;
– Reset the rotating motor;
– The voltage of the power supply is too low;
– The load is too heavy;
– The motor power is too large, and the power of the VFD is too small.

Solution:

– Increase the ACC time;
– Avoid the restarting after stopping;
– Check the power of the supply line;
– Select a VFD with bigger power;
– Select a proper motor.
SPI
Phase loss
on input
side		Cause & Solution: Phase loss or violent fluctuation occurred to R, S, and T input.

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.
SPO
Phase loss
on output
side		Cause & Solution: Phase loss occurred to U, V, W output (or the three phases of motor is asymmetrical)

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
Rectifier
module
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.
OH2
Inverter
module
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.
EF
External
Fault		Cause: SI external fault input terminals action. External fault comes when the drive has detected an issue with an external control circuit or device connected to it. This means the drive has detected an issue with an external device or control circuit connected to it. Unlike error codes specific to internal drive components, the EF code is more general and can be triggered by various external factors.

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.
CE
RS485
communication
Fault		Cause:

– The baud rate setting is incorrect;
– Fault occurs to the communication wiring;
– The communication address is wrong;
– There is strong interference to the communication.

Solution:

– Set proper baud rate;
– Check the communication connection distribution;
– Set proper communication address;
– Chang or replace the connection distribution or improve the anti-interference capability.
ItE
Current
detection
fault		Cause:

– The control panel connector is in poor contact;
– An exception occurs on the magnifying circuit.

Solution:

– Check the connector and re-plug
– Change the main control panel
tE
Motor
autotuning
fault		Cause:

– The motor capacity does not comply with the VFD capability;
– The rated parameter of the motor does not set correctly;
– The offset between the parameters from autotuning and the standard parameter is huge;
– Autotuning overtime.

Solution:

– Change the VFD mode;
– Set the rated parameter according to the motor name plate;
– Empty the motor load;
– Check the motor connection and set the parameter;
– Check if the upper limit frequency is above 2/3 of the rated frequency
EEP
EEPROM
operation
fault		Cause:

– Error of controlling the write and read of the parameters;
– Damage to EEPROM.

Solution:

– Press STOP/RST to reset;
– Change the main control panel.
PIDE
PID
feedback
offline
fault		Cause:

– PID feedback offline;
– PID feedback source disappear.

Solution:

– Check the PID feedback signal;
– Check the PID feedback source.
bCE
Braking
unit fault		Cause:

– Braking circuit fault or damage to the braking pipes;
– The external braking resistor is not sufficient.

Solution:

– Check the braking unit, and change new braking pipe;
– Increase the braking resistor.
END
Running
time
reached		Cause: The actual running time of the VFD is above the internal setting running time.

Solution: Ask for the supplier and adjust the setting running time.
OL3
Electronics
overload		Cause: The VFD will report overload pre-alarm according to the set value.

Solution: Check the load and the overload pre-alarm threshold.
PCE
Keypad
communication
error		Cause:

– The keypad is not in good connection or offline;
– The keypad cable is too long and there is strong interference;
– Part of the communication circuits of the keypad or main board have fault.

Solution:

– Check the keypad cable and and ensure it is normal;
– Check the environment and eliminate the interference source;
– Change hardware and ask for maintenance service.
UPE
Parameter
upload
error		Cause:

– The keypad is not in good connection or offline;
– The keypad cable is too long and there is strong interference;
– Part of the communication circuits of the keypad or main board have fault.

Solution:

– Check the environment and eliminate the interference source;
– Change hardware and ask for maintenance service;
– Change hardware and ask for maintenance service.
DNE
Parameter
download
error		Cause:

– The keypad is not in good connection or offline;
– The keypad cable is too long and there is strong interference;
– Data storage error in keypad.

Solution:

– Check the environment and eliminate the interference source;
– Change hardware and ask for maintenance service;
– Back up data in the keypad again.
ETH1
To-ground
short-
circuit
fault 1 		Cause:

– The output of the VFD is short circuited with the ground;
– There is fault in the current detection circuit;
– There is a great difference between the actual motor power setting and the VFD power.

Solution:

– Check if the connection of the motor is normal or not;
– Change the hall;
– Change the main control panel;
– Reset the correct motor parameter;
– Check whether motor power parameters in P2 group is consistent with the motor power actually used.
ETH2
To-ground
short-
circuit
fault 2		Cause:

– The output of the VFD is short circuited with the ground;
– There is fault in the current detection circuit;
– There is a great difference between the actual motor power setting and the VFD power.

Solution:

– Check if the connection of the motor is normal or not;
– Change the hall;
– Change the main control panel;
– Reset the correct motor parameter;
– Check whether motor power parameters in P2 group is consistent with the motor power actually used.
dEu
Speed
deviation
fault		Cause: Load is too heavy, or stall occurred.

Solution:

– Check the load to ensure it is proper, increase the detection time.
– Check whether control parameters are set properly.
STo
Maladjustment
fault		Cause:

– Control parameters of synchronous motor is set improperly;
– The parameter gained from autotuning is inaccurate;
– The VFD is not connected to motor

Solution:

– Check the load to ensure it is proper,
– Check whether load is proper;
– Check whether control parameters are set correctly;
– Increase maladjustment detection time
LL
Electronic
underload
fault		Cause: The VFD will report the underload pre-alarm according to the set value.

Solution:

1. Check the load and the underload pre-alarm point.
OT
Motor
over
temperature		Cause: Motor over-temperature input terminal is valid.
– Exception occurred to t temperature detection Exception occurred to resistor.
– Long-time overload running or exception occurred.

Solution:

– Check the wiring of motor over-temperature input terminal.
– Check whether temperature sensor is proper;
– Check the motor and perform maintenance on the motor
E-Err
Repetitive
expansion
card type		Cause: The two inserted expansion cards are of the same type.

Solution:

– You should not insert two cards with the same type;
– Check the type of expansion card, and remove one card after power down.
F1-Er
Failed to
identify the
expansion
card in card
slot 1		Cause: There is data transmission in interfaces of card slot 1, however, it cannot read the card type.

Solution:

– Confirm whether the expansion card inserted can be supported;
– Stabilize the expansion card interfaces after power down, and confirm whether fault still occurs at next power-on;
– Check whether the insertion port is damaged, if yes, replace the insertion port after power down
F2-Er
Failed to
identify
the expansion
card in card
slot 2		Cause: There is data transmission in interfaces of card slot 2, however, it cannot read the card type.

Solution:

– Confirm whether the expansion card inserted can be supported;
– Stabilize the expansion card interfaces after power down, and confirm whether fault still occurs at next power-on;
– Check whether the insertion port is damaged, if yes, replace the insertion port after power down
C1-Er
Communication
timeout
occurred to
the expansion
card in card
slot 1		Cause: There is no data transmission in interfaces of card slot 1.

Solution:

– Confirm whether the expansion card inserted can be supported;
– Stabilize the expansion card interfaces after power down, and confirm whether fault still occurs at next power-on;
– Check whether the insertion port is damaged, if yes, replace the insertion port after power down.
C2-Er
Communication
timeout
occurred to
the expansion
card in card
slot 2		Cause: There is no data transmission in interfaces of card slot 2.

Solution:

– Confirm whether the expansion card inserted can be supported;
– Stabilize the expansion card interfaces after power down, and confirm whether fault still occurs at next power-on;
– Check whether the insertion port is damaged, if yes, replace the insertion port after power down
E-DP
PROFIBUS card
communication
timeout fault		Cause: There is no data transmission between the communication card and the host controller (or PLC).

Solution:

– Check whether the communication card wiring is loose or dropped.
E-NET
Ethernet card
communication
timeout fault		Cause: There is no data transmission between the communication card and the host controller.

Solution:

– Check whether the communication card wiring is loose or dropped.
E-CAN
CANopen card
communication
timeout fault		Cause: There is no data transmission between the communication card and the host controller (or PLC).

Solution:

– Check whether the communication card wiring is loose or dropped.
E-PN
PROFINET card
communication
timeout fault		Cause: There is no data transmission between the communication card and the host controller (or PLC).

Solution:

– Check whether the communication card wiring is loose or dropped.
E-CAT
EtherCAT card
communication
timeout fault		Cause: There is no data transmission between the communication card and the host controller (or PLC).

Solution:

– Check whether the communication card wiring is loose or dropped.
E-BAC
BACNet card
communication
timeout fault		Cause: There is no data transmission between the communication card and the host controller (or PLC).

Solution:

– Check whether the communication card wiring is loose or dropped.
E-DEV
DeviceNet card
communication
timeout fault		Cause: There is no data transmission between the communication card and the host controller (or PLC).

Solution:

– Check whether the communication card wiring is loose or dropped
SECAN
CAN
master/slave
communication
card
communication
timeout fault		Cause: There is no data transmission between the CAN master and slave communication cards.

Solution:

– Check whether the communication card wiring is loose or dropped.
S-Err
CAN slave fault
in master/slave
synchronization		Cause: Fault occurred to one of the CAN slave VFDs.

Solution:

– Detect the CAN slave VFD and analyze the corresponding fault cause of the VFD.
FrOST
Freezing
fault		Cause: The temperature is lower than the freezing protection threshold.

Solution:

– Check the temperature.
BLOCK
Stalling
fault 		Cause: The current is greater than the stalling current.

Solution:

– Check for stalling.
Dr
Dry pumping		Cause: The current is lower than the current limit for motor dry pumping.

Solution:

– Check for dry pumping.
PoFF
System
power off 		Cause: System power off or low DC voltage.

Solution: Check the grid.