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 Troubleshooting
| Fault Code and Meaning | Cause and Remedy |
|---|---|
| OUt1 Inverter unit Phase-U protection |
Cause: Acceleration is too fast.
Remedy:
|
| 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:
|
| 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:
|
| OV1 Over-voltage during acceleration |
Cause:
Exception occurred to input voltage; Large energy feedback; Lack of braking units; Dynamic brake is not enabled.
Remedy:
|
| OV2 Over-voltage during deceleration |
Cause:
Exception occurred to input voltage; Large energy feedback; Lack of braking units; Dynamic brake is not enabled.
Remedy:
|
| 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:
|
| 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:
|
| 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:
|
| 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:
|
| UV Bus undervoltage fault |
Cause:
Grid voltage is too low; Overvoltage stall protection is not enabled.
Remedy:
|
| OL1 Motor overload |
Cause:
Grid voltage is too low; Rated motor current is set improperly; Motor stall or load jumps violently.
Remedy:
|
| 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:
|
| SPI Phase loss on input side |
Cause:
Phase loss or violent fluctuation occurred to R, S and T input.
Remedy:
|
| SPO Phase loss on output side |
Cause:
Phase loss occurred to U, V, W output (or the three phases of motor is asymmetrical).
Remedy:
|
| OH1 Overheat of rectifier module |
Cause:
Air duct is blocked or fan is damaged; Ambient temperature is too high; Long-time overload running.
Remedy:
|
| OH2 Overheat of inverter module |
Cause:
Air duct is blocked or fan is damaged; Ambient temperature is too high; Long-time overload running.
Remedy:
|
| EF External fault |
Cause:
SI external fault input terminal acts.
Remedy:
|
| CE 485 communication fault |
Cause:
Baud rate is set improperly; Communication line fault; Communication address error; Communication suffers from strong interference.
Remedy:
|
| ItE Current detection fault |
Cause:
Poor contact of the connector of control board; Hall component is damaged; Exception occurred to amplification circuit.
Remedy:
|
| 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:
|
| EEP EEPROM fault |
Cause:
R/W error occurred to the control parameters; EEPROM is damaged.
Remedy:
|
| PIDE PID feedback offline fault |
Cause:
PID feedback offline; PID feedback source disappears.
Remedy:
|
| bCE Braking unit fault |
Cause:
Brake circuit fault or brake tube is damaged; The resistance of external braking resistor is too small.
Remedy:
|
| END Running time is up |
Cause:
The actual running time of the VFD is larger than the set running time.
Remedy:
|
| OL3 Electronic overload fault |
Cause:
The VFD releases overload pre-alarm based on the set value.
Remedy:
|
| 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:
|
| 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:
|
| 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:
|
| 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:
|
| 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:
|
| dEu Speed deviation fault |
Cause:
Load is too heavy, or stall occurred.
Remedy:
|
| 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:
|
| LL Electronic underload fault |
Cause:
The VFD performs underload pre-alarm based on the set value.
Remedy:
|
| ENC1O Encoder offline fault |
Cause:
Encoder line sequence is wrong, or signal wires are poorly connected.
Remedy:
|
| ENC1D Encoder reversal fault |
Cause:
The encoder speed signal is contrary to the motor running direction.
Remedy:
|
| ENC1Z Encoder Z pulse offline fault |
Cause:
Z signal wires are disconnected.
Remedy:
|
| 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:
|
| STO Safe torque off |
Cause:
Safe torque off function is enabled by external forces.
Remedy:
|
| 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:
|
| 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:
|
| STL3 Exception occurred to channel H1 and channel H2 |
Cause:
Hardware fault occurred to STO circuit.
Remedy:
|
| CrCE Safety code FLASH CRC check fault |
Cause: Control board is faulty.
Remedy:
|
| E-Err Repetitive extension card type |
Cause: The two inserted extension cards are of the same type.
Remedy:
|
| ENCUV Encoder UVW loss fault |
Cause: No electric level variation occurred to UVW signal.
Remedy:
|
| 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:
|
| 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:
|
| 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:
|
| 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:
|
| 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:
|
| 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:
|
| E-DP Profibus card communication timeout fault |
Cause: There is no data transmission between the communication card and the host computer (or PLC).
Remedy:
|
| E-NET Ethernet card communication timeout fault |
Cause: There is no data transmission between the communication card and the host computer.
Remedy:
|
| E-CAN CANopen card communication timeout fault |
Cause: There is no data transmission between the communication card and the host computer (or PLC).
Remedy:
|
| E-PN Profinet card communication timeout fault |
Cause: There is no data transmission between the communication card and the host computer (or PLC).
Remedy:
|
| E-CAT EtherCat card communication timeout fault |
Cause: There is no data transmission between the communication card and the host computer (or PLC).
Remedy:
|
| E-BAC BACNet card communication timeout fault |
Cause: There is no data transmission between the communication card and the host computer (or PLC).
Remedy:
|
| E-DEV DeviceNET card communication timeout fault |
Cause: There is no data transmission between the communication card and the host computer (or PLC).
Remedy:
|
| ESCAN Can master/slave communication card communication timeout fault |
Cause: There is no data transmission between the CAN master and slave communication cards.
Remedy:
|
| S-Err Master-slave synchronous CAN slave fault |
Cause: Fault occurred to one of the CAN slave VFDs.
Remedy:
|
| dIS Failure to enable the VFD |
Cause: The input terminal selects VFD enabling, but the terminal signal is invalid.
Remedy:
|
| tbE Contactor feedback fault |
Cause: The contactor feedback circuit is disconnected or in poor contact. The contactor feedback detection time is too short.
Remedy:
|
| FAE Brake feedback fault |
Cause: The brake feedback circuit is disconnected or in poor contact. The brake feedback detection time is too short.
Remedy:
|
| tPF Torque verification fault |
Cause: The torque verification current, moment force setting, and torque verification fault detection time are set improperly.
Remedy:
|
| 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:
|
| LSP Low-speed running protection fault |
Cause: The running speed is too low.
Remedy:
|
| tCE Terminal command exception |
Cause: The terminal gives both the upward and downward commands at the same time.
Remedy:
|
| POE Terminal command exception at power-on |
Cause: The terminal command is detected at power-on.
Remedy:
|
| SLE Loose rope protection fault |
Cause: The hook rope is abnormal. The downward loose rope parameter setting is improper.
Remedy:
|
| bE Brake failure |
Cause: The brake force is insufficient. The brake detection parameter setting is improper.
Remedy:
|
| 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:
|
| 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:
|
| OtE1 PT100 overtemperature fault |
Cause: The current environment temperature is too high. PT100 detection circuit is abnormal. PT100 overtemperature protection setting is improper.
Remedy:
|
| OtE2 PT1000 overtemperature fault |
Cause: The current environment temperature is too high. PT1000 detection circuit is abnormal. PT1000 overtemperature protection setting is improper.
Remedy:
|
| SFE Set frequency fault |
Cause: The set frequency is too small.
Remedy:
|
| PtcE PTC overtemperature fault |
Cause: The current environment temperature is too high.
Remedy:
|
| 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:
|
| 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:
|
| 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:
|
| A-LvP Low voltage alarm |
Cause: The bus voltage is too low.
Remedy:
|
| A-OL Overload protection alarm |
Cause: The load is too heavy. The overload protection parameter is set improperly.
Remedy:
|
| A-bS Brake failure alarm |
Cause: The brake force is insufficient. The encoder is abnormal. The zero servo detection parameter is set improperly.
Remedy:
|
| 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:
|
| A-SL Loose rope protection alarm |
Cause: The hook rope is abnormal. The downward loose rope parameter setting is improper.
Remedy:
|
| A-Ot1 PT100 overtemperature alarm |
Cause: The current environment temperature is too high. PT100 overtemperature protection setting is improper.
Remedy:
|
| A-Ot2 PT1000 overtemperature alarm |
Cause: The current environment temperature is too high. PT1000 overtemperature alarm setting is improper.
Remedy:
|
| A-Pt1 PT100 disconnection alarm |
Cause: PT100 connection circuit is opened.
Remedy:
|
| A-Pt2 PT1000 disconnection alarm |
Cause: PT1000 connection circuit is opened.
Remedy:
|
| A-Ptc PTC overtemperature alarm |
Cause: The current environment temperature is too high.
Remedy:
|
| PoFF System power failure |
Cause: The system is powered off or the bus voltage is too low.
Remedy:
|
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
Post a Comment