INVT GD350-19 Series Drive Fault Codes List

Complete reference list of INVT GD350-19 (Premium Crane & Hoist) fault codes. Learn to troubleshoot closed-loop lifting errors, Anti-Sway alarms, Master-Slave sync faults, and Brake logic issues.

INVT GD350-19 Fault Codes Reference Table

Use the search bar in the table below to quickly find your specific error code.

Goodrive350-19 Series VFD Faults and Alarms

Goodrive350-19 Series VFD Troubleshooting

Fault Code and Meaning Cause and Remedy
OUt1
Inverter unit Phase-U protection
Cause: Acceleration is too fast.

Remedy:
  • Increase acceleration time.
OUt2
Inverter unit Phase-V protection
Cause: IGBT module is damaged; Misacts caused by interference; drive wires are poorly connected; To-ground short circuit occurs.

Remedy:
  • Replace the power unit.
  • Check drive wires.
  • Check whether there is strong interference surrounding the peripheral equipment.
OUt3
Inverter unit Phase-W protection
Cause: IGBT module is damaged; Misacts caused by interference; drive wires are poorly connected; To-ground short circuit occurs.

Remedy:
  • Replace the power unit.
  • Check drive wires.
  • Check whether there is strong interference surrounding the peripheral equipment.
OV1
Over-voltage during acceleration
Cause: Exception occurred to input voltage; Large energy feedback; Lack of braking units; Dynamic brake is not enabled.

Remedy:
  • Check input power.
  • Check whether load deceleration time is too short.
  • Check if the motor starts during rotating.
  • Install dynamic braking units.
  • Check the setup of related function codes.
OV2
Over-voltage during deceleration
Cause: Exception occurred to input voltage; Large energy feedback; Lack of braking units; Dynamic brake is not enabled.

Remedy:
  • Check input power.
  • Check whether load deceleration time is too short.
  • Install dynamic braking units.
  • Check the setup of related function codes.
OV3
Over-voltage during constant speed running
Cause: Exception occurred to input voltage; Large energy feedback; Lack of braking units; Dynamic brake is not enabled.

Remedy:
  • Check input power.
  • Check the setup of related function codes.
OC1
Over-current during acceleration
Cause: Acceleration is too fast; Grid voltage is too low; VFD power is too small; Load transient or exception occurred; To-ground short circuit or output phase loss occur; Strong external interference sources; Overvoltage stall protection is not enabled.

Remedy:
  • Increase acceleration time.
  • Check input power.
  • Select the VFD with larger power.
  • Check if the load is short circuited (to-ground or line-to-line) or if rotation is not smooth.
  • Check the output wiring.
  • Check if there is strong interference.
  • Check the setup of related function codes.
OC2
Over-current during deceleration
Cause: Deceleration is too fast; Grid voltage is too low; VFD power is too small; Load transient or exception occurred; To-ground short circuit or output phase loss occur; Strong external interference sources.

Remedy:
  • Increase deceleration time.
  • Check input power.
  • Select the VFD with larger power.
  • Check if the load is short circuited.
  • Check the output wiring.
  • Check if there is strong interference.
OC3
Over-current during constant speed running
Cause: Grid voltage is too low; Load transient or exception occurred; To-ground short circuit or output phase loss occur; Strong external interference sources.

Remedy:
  • Check input power.
  • Check if the load is short circuited.
  • Check the output wiring.
  • Check if there is strong interference.
UV
Bus undervoltage fault
Cause: Grid voltage is too low; Overvoltage stall protection is not enabled.

Remedy:
  • Check grid input power.
  • Check the setup of related function codes.
OL1
Motor overload
Cause: Grid voltage is too low; Rated motor current is set improperly; Motor stall or load jumps violently.

Remedy:
  • Check grid voltage.
  • Reset rated motor current.
  • Check the load and adjust torque boost.
OL2
VFD overload
Cause: Acceleration is too fast; The motor in rotating is restarted; Grid voltage is too low; Load is too large; Power is too small.

Remedy:
  • Increase acceleration time.
  • Avoid restart after stop.
  • Check grid voltage.
  • Select the VFD with larger power.
  • Select proper motor.
SPI
Phase loss on input side
Cause: Phase loss or violent fluctuation occurred to R, S and T input.

Remedy:
  • Check the input power.
  • Check installation wiring.
SPO
Phase loss on output side
Cause: Phase loss occurred to U, V, W output (or the three phases of motor is asymmetrical).

Remedy:
  • Check the output wiring.
  • Check the motor and cable.
OH1
Overheat of rectifier module
Cause: Air duct is blocked or fan is damaged; Ambient temperature is too high; Long-time overload running.

Remedy:
  • Ventilate the air duct or replace the fan.
  • Lower the ambient temperature.
OH2
Overheat of inverter module
Cause: Air duct is blocked or fan is damaged; Ambient temperature is too high; Long-time overload running.

Remedy:
  • Ventilate the air duct or replace the fan.
  • Lower the ambient temperature.
EF
External fault
Cause: SI external fault input terminal acts.

Remedy:
  • Check external device input.
CE
485 communication fault
Cause: Baud rate is set improperly; Communication line fault; Communication address error; Communication suffers from strong interference.

Remedy:
  • Set proper baud rate.
  • Check the wiring of communication interfaces.
  • Set proper communication address.
  • Replace or change the wiring to enhance anti-interference capacity.
ItE
Current detection fault
Cause: Poor contact of the connector of control board; Hall component is damaged; Exception occurred to amplification circuit.

Remedy:
  • Check the connector and re-plug.
  • Replace the hall component.
  • Replace the main control board.
tE
Motor autotuning fault
Cause: Motor capacity does not match with VFD capacity (difference exceeds five power classes); Motor parameter set improperly; Autotuning parameters deviate sharply from standard; Autotuning timeout.

Remedy:
  • Change the VFD model or adopt V/F mode for control.
  • Set proper motor type and nameplate parameters.
  • Empty the motor load and carry out autotuning again.
  • Check motor wiring and parameter setup.
  • Check whether upper limit frequency is larger than 2/3 of the rated frequency.
EEP
EEPROM fault
Cause: R/W error occurred to the control parameters; EEPROM is damaged.

Remedy:
  • Press STOP/RST to reset.
  • Replace the main control board.
PIDE
PID feedback offline fault
Cause: PID feedback offline; PID feedback source disappears.

Remedy:
  • Check PID feedback signal wires.
  • Check PID feedback source.
bCE
Braking unit fault
Cause: Brake circuit fault or brake tube is damaged; The resistance of external braking resistor is too small.

Remedy:
  • Check the braking unit, replace with new brake tubes.
  • Increase brake resistance.
END
Running time is up
Cause: The actual running time of the VFD is larger than the set running time.

Remedy:
  • Ask help from the supplier, adjust the set running time.
OL3
Electronic overload fault
Cause: The VFD releases overload pre-alarm based on the set value.

Remedy:
  • Check the load and overload pre-alarm threshold.
PCE
Keypad communication fault
Cause: Keypad wire poorly contacted or disconnected; Keypad wire too long or suffers strong interference; Circuit fault to keypad/comms part of main board.

Remedy:
  • Check the keypad wires to confirm whether fault exists.
  • Check the surroundings to rule out interference source.
  • Replace the hardware and ask for maintenance service.
UPE
Parameter upload error
Cause: Keypad wire poorly contacted or disconnected; Keypad wire too long or suffers strong interference; Circuit fault to keypad/comms part of main board.

Remedy:
  • Check the surroundings to rule out interference source.
  • Replace the hardware and ask for maintenance service.
DNE
Parameter download error
Cause: Keypad wire poorly contacted or disconnected; Keypad wire too long or suffers strong interference; Data storage error occurred to the keypad.

Remedy:
  • Check the surroundings to rule out interference source.
  • Replace the hardware and ask for maintenance service.
  • Re-backup keypad data.
ETH1
To-ground short circuit fault 1
Cause: VFD output is short connected to the ground; Current detection circuit is faulty; Actual motor power setup deviates sharply from the VFD power.

Remedy:
  • Check whether motor wiring is proper.
  • Replace the hall component.
  • Replace the main control board.
  • Reset the motor parameters properly.
ETH2
To-ground short circuit fault 1 (2)
Cause: VFD output is short connected to ground; Current detection circuit is faulty; Actual motor power setup deviates sharply from the VFD power.

Remedy:
  • Check whether motor wiring is proper.
  • Replace the hall component.
  • Replace the main control board.
  • Reset the motor parameters properly.
dEu
Speed deviation fault
Cause: Load is too heavy, or stall occurred.

Remedy:
  • 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.

Remedy:
  • Check whether load is proper.
  • Check whether control parameters are set correctly.
  • Increase maladjustment detection time.
LL
Electronic underload fault
Cause: The VFD performs underload pre-alarm based on the set value.

Remedy:
  • Check the load and overload pre-alarm threshold.
ENC1O
Encoder offline fault
Cause: Encoder line sequence is wrong, or signal wires are poorly connected.

Remedy:
  • Check the encoder wiring.
ENC1D
Encoder reversal fault
Cause: The encoder speed signal is contrary to the motor running direction.

Remedy:
  • Reset encoder direction.
ENC1Z
Encoder Z pulse offline fault
Cause: Z signal wires are disconnected.

Remedy:
  • Check the wiring of Z signal.
OT
Motor over-temperature fault
Cause: Motor over-temperature input terminal is valid; Exception occurred to temperature detection; Exception occurred to resistor; Long-time overload running or exception occurred.

Remedy:
  • Check the wiring of motor over-temperature input terminal (terminal function 57).
  • Check whether temperature sensor is proper.
  • Check the motor and perform maintenance on the motor.
STO
Safe torque off
Cause: Safe torque off function is enabled by external forces.

Remedy:
  • N/A
STL1
Exception occurred to safe circuit of channel H1
Cause: The wiring of STO is improper; Fault occurred to external switch of STO; Hardware fault occurred to safety circuit of channel H1.

Remedy:
  • Check whether terminal wiring of STO is proper and firm enough.
  • Check whether external switch of STO can work properly.
  • Replace the control board.
STL2
Exception occurred to channel H2 safe circuit
Cause: The wiring of STO is improper; Fault occurred to external switch of STO; Hardware fault occurred to safety circuit of channel H2.

Remedy:
  • Check whether terminal wiring of STO is proper and firm enough.
  • Check whether external switch of STO can work properly.
  • Replace the control board.
STL3
Exception occurred to channel H1 and channel H2
Cause: Hardware fault occurred to STO circuit.

Remedy:
  • Replace the control board.
CrCE
Safety code FLASH CRC check fault
Cause: Control board is faulty.

Remedy:
  • Replace the control board.
E-Err
Repetitive extension card type
Cause: The two inserted extension cards are of the same type.

Remedy:
  • You should not insert two cards with the same type.
  • Check the type of extension card, and remove one card after power down.
ENCUV
Encoder UVW loss fault
Cause: No electric level variation occurred to UVW signal.

Remedy:
  • Check the wiring of UVW.
  • Encoder is damaged.
F1-Er
Failed to identify the extension card in card slot 1
Cause: There is data transmission in interfaces of card slot 1, however, it cannot read the card type.

Remedy:
  • Confirm whether the extension card inserted can be supported.
  • Stabilize the extension 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 extension card in card slot 2
Cause: There is data transmission in interfaces of card slot 2, however, it cannot read the card type.

Remedy:
  • Confirm whether the extension card inserted can be supported.
  • Stabilize the extension 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.
F3-Er
Failed to identify the extension card in card slot 3
Cause: There is data transmission in interfaces of card slot 3, however, it cannot read the card type.

Remedy:
  • Confirm whether the extension card inserted can be supported.
  • Stabilize the extension 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 extension card in card slot 1
Cause: There is no data transmission in interfaces of card slot 1.

Remedy:
  • Confirm whether the extension card inserted can be supported.
  • Stabilize the extension 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 extension card in card slot 2
Cause: There is no data transmission in interfaces of card slot 2.

Remedy:
  • Confirm whether the extension card inserted can be supported.
  • Stabilize the extension 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.
C3-Er
Communication timeout occurred to the extension card in card slot 3
Cause: There is no data transmission in interfaces of card slot 3.

Remedy:
  • Confirm whether the extension card inserted can be supported.
  • Stabilize the extension 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 computer (or PLC).

Remedy:
  • 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 computer.

Remedy:
  • 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 computer (or PLC).

Remedy:
  • 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 computer (or PLC).

Remedy:
  • 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 computer (or PLC).

Remedy:
  • 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 computer (or PLC).

Remedy:
  • 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 computer (or PLC).

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

Remedy:
  • Check whether the communication card wiring is loose or dropped.
S-Err
Master-slave synchronous CAN slave fault
Cause: Fault occurred to one of the CAN slave VFDs.

Remedy:
  • Detect the CAN slave VFD and analyze the corresponding fault cause of the VFD.
dIS
Failure to enable the VFD
Cause: The input terminal selects VFD enabling, but the terminal signal is invalid.

Remedy:
  • Check the input terminal setting and terminal signal.
tbE
Contactor feedback fault
Cause: The contactor feedback circuit is disconnected or in poor contact. The contactor feedback detection time is too short.

Remedy:
  • Check the contactor feedback circuit.
  • Increase the detection time P91.05 to a proper value.
FAE
Brake feedback fault
Cause: The brake feedback circuit is disconnected or in poor contact. The brake feedback detection time is too short.

Remedy:
  • Check the brake feedback circuit.
  • Increase the detection time P90.32 to a proper value.
tPF
Torque verification fault
Cause: The torque verification current, moment force setting, and torque verification fault detection time are set improperly.

Remedy:
  • Set the torque verification current, moment force setting, and torque verification fault detection time P90.30 properly.
StC
Operating lever zero-position fault
Cause: The operating lever does not return to the zero position. The operating lever zero-position signal is adhered.

Remedy:
  • Put the operating lever to the zero position.
  • Check out the operating lever zero-position signal.
LSP
Low-speed running protection fault
Cause: The running speed is too low.

Remedy:
  • Check whether the running speed is continuously lower than P92.03.
tCE
Terminal command exception
Cause: The terminal gives both the upward and downward commands at the same time.

Remedy:
  • Check the input terminal signal.
POE
Terminal command exception at power-on
Cause: The terminal command is detected at power-on.

Remedy:
  • Check whether P01.18 is set to enable the VFD reports a fault when a terminal command is valid at power-on.
  • Check the input terminal signal.
SLE
Loose rope protection fault
Cause: The hook rope is abnormal. The downward loose rope parameter setting is improper.

Remedy:
  • Check whether the hook rope is normal.
  • Check whether the downward loose rope detection torque is proper.
bE
Brake failure
Cause: The brake force is insufficient. The brake detection parameter setting is improper.

Remedy:
  • Check whether the brake is normal.
  • Check whether the brake slip parameter setting is proper.
ELS
Master/salve position synchronization fault
Cause: The encoder pulse difference between the master and slave is too great. The pulse threshold setting is improper.

Remedy:
  • Check the encoders for the master and slave.
  • Check whether the pulse threshold of the slave is too small.
AdE
Analog speed reference deviation fault
Cause: If the speed is given by analog, the analog voltage is greater than 1.0V after zero-position detection is complete.

Remedy:
  • Check the analog wiring and current voltage value.
OtE1
PT100 overtemperature fault
Cause: The current environment temperature is too high. PT100 detection circuit is abnormal. PT100 overtemperature protection setting is improper.

Remedy:
  • Check the current environment temperature.
  • Check PT100 circuit.
  • Check whether PT100 overtemperature protection point is too small.
OtE2
PT1000 overtemperature fault
Cause: The current environment temperature is too high. PT1000 detection circuit is abnormal. PT1000 overtemperature protection setting is improper.

Remedy:
  • Check the current environment temperature.
  • Check PT1000 circuit.
  • Check whether PT1000 overtemperature protection point is too small.
SFE
Set frequency fault
Cause: The set frequency is too small.

Remedy:
  • Check whether the frequency reference is smaller than the set frequency protection point.
PtcE
PTC overtemperature fault
Cause: The current environment temperature is too high.

Remedy:
  • Check the current environment temperature.
A-SPI
Input phase loss alarm
Cause: During stop, a loss of either input phase R, S, or T occurs or fluctuation is great.

Remedy:
  • Check the input power source and wiring.
A-LU
Upward position limit alarm
Cause: The input terminal has set the upward limited position reaching function, and there is a signal reference to the terminal.

Remedy:
  • Check whether the allowed highest position point has been reached.
  • Check the input terminal signal.
A-Ld
Downward position limit alarm
Cause: The input terminal has set the downward limited position reaching function, and there is a signal reference to the terminal.

Remedy:
  • Check whether the allowed lowest position point has been reached.
  • Check the input terminal signal.
A-LvP
Low voltage alarm
Cause: The bus voltage is too low.

Remedy:
  • Check whether the voltage protection point is too high.
  • Check whether the grid voltage or rectifier module is abnormal.
A-OL
Overload protection alarm
Cause: The load is too heavy. The overload protection parameter is set improperly.

Remedy:
  • Check whether the load is too heavy.
  • Check whether the overload protection point is too small.
A-bS
Brake failure alarm
Cause: The brake force is insufficient. The encoder is abnormal. The zero servo detection parameter is set improperly.

Remedy:
  • Check whether the brake works normally.
  • Check whether the encoder works normally.
  • Check whether the zero servo tolerance pulse threshold is too small.
A-FA
Brake feedback alarm
Cause: The brake feedback circuit is disconnected or in poor contact. The brake feedback detection time is too short.

Remedy:
  • Check the brake feedback circuit.
  • Increase the detection time P90.32 to a proper value.
A-SL
Loose rope protection alarm
Cause: The hook rope is abnormal. The downward loose rope parameter setting is improper.

Remedy:
  • Check whether the hook rope is normal.
  • Check whether the downward loose rope detection torque is proper.
A-Ot1
PT100 overtemperature alarm
Cause: The current environment temperature is too high. PT100 overtemperature protection setting is improper.

Remedy:
  • Check the current environment temperature.
  • Check whether PT100 overtemperature protection point is too small.
A-Ot2
PT1000 overtemperature alarm
Cause: The current environment temperature is too high. PT1000 overtemperature alarm setting is improper.

Remedy:
  • Check the current environment temperature.
  • Check whether PT1000 overtemperature protection point is too small.
A-Pt1
PT100 disconnection alarm
Cause: PT100 connection circuit is opened.

Remedy:
  • Check PT100 connection circuit.
A-Pt2
PT1000 disconnection alarm
Cause: PT1000 connection circuit is opened.

Remedy:
  • Check PT1000 connection circuit.
A-Ptc
PTC overtemperature alarm
Cause: The current environment temperature is too high.

Remedy:
  • Check the current environment temperature.
PoFF
System power failure
Cause: The system is powered off or the bus voltage is too low.

Remedy:
  • Check the grid conditions.
 

Troubleshooting Advanced Crane Functions

The GD350-19 manages complex lifting logic. Troubleshooting requires looking at both the drive parameters and the external feedback devices.

  • Closed-Loop Safety (ENC): Most GD350-19 applications use an encoder for precise holding. If the drive detects a discrepancy between the frequency reference and the encoder speed (DevErr or ENC1O), it will trip immediately to prevent a “hook slip” or dropped load.
  • Master-Slave Sync (MS): On large cranes using two motors for one hoist (or rigid gantries), the drives communicate via high-speed bus or fiber optics. A SPI or ComErr here breaks the synchronization, stopping both drives to prevent mechanical twisting of the crane structure.
  • Brake Logic Monitoring: The drive monitors the physical status of the mechanical brake. If the drive commands the brake to open but the feedback switch remains closed (or vice versa), it triggers a Brake Fault.

Frequently Asked Questions (FAQ)

Q: What is “tPF” (Torque Proof Failure)?

A: This is the standard Torque Verification safety fault. Before releasing the brake, the drive builds up current and checks if the motor can hold the load.
Fix:
1. Check if the load exceeds the crane’s rated capacity.
2. If using Closed Loop, check the encoder coupling—if the encoder slips, torque proof fails.
3. Increase the torque proof current threshold or time (Group P91).

Q: How do I handle “SwAy” or “PosErr” codes?

A: These relate to the Anti-Sway and Positioning features.
SwAy: The anti-sway logic cannot calculate the pendulum angle correctly (often due to incorrect rope length parameters).
PosErr: The crane overshot its target position or limits. Check the limit switches and the deceleration ramp times.

Q: The drive shows “STO” but no other fault. Why?

A: STO (Safe Torque Off) is mandatory for modern cranes. It means the safety circuit (E-Stop, Cabin Door Interlock, or Limit Switch) is open. The drive is physically prevented from generating torque. You must close the safety chain (restore +24V to H1/H2) to operate.

Comments

Popular posts from this blog

Allen Bradley Kinetix 5500 Drive Fault Codes List

Danfoss VACON 100 FLOW Drive Fault Codes List

ABB ACH580 Drive Fault Codes List