Introduction

With the rapid development of industrial automation, variable frequency drives (VFDs) have evolved from simple motor speed regulators into intelligent drive systems integrating motor control, speed feedback, torque management, communication functions, and advanced fault diagnosis.

In applications requiring high speed accuracy and dynamic response, such as machine tools, cranes, textile equipment, printing machinery, packaging lines, and automated production systems, closed-loop vector control with encoder feedback has become increasingly common.

The AnyHz (Foster Technology) FST-650 series is a high-performance vector control inverter that supports multiple control modes, including:

• V/F control;
• Sensorless vector control;
• Closed-loop vector control with encoder feedback.

When the FST-650 displays the fault code Err20, the inverter has detected an abnormality in the encoder feedback system.

The meaning of Err20 is:

Err20 = Encoder Fault / PG Card Fault

However, in practical maintenance work, Err20 does not always mean that the encoder itself is damaged. Many real-world cases are caused by:

• Incorrect control mode selection;
• Wrong encoder parameter settings;
• Encoder wiring problems;
• Missing encoder power supply;
• PG card failure;
• Incorrect replacement configuration.

This article provides a detailed analysis of the working principle behind Err20, common causes, diagnostic procedures, and repair methods to help engineers quickly troubleshoot AnyHz FST-650 encoder-related faults.

---

1. Working Principle of Err20 Fault in FST-650 Inverter

1.1 The Role of Encoder Feedback in Closed-Loop Vector Control

A conventional inverter operating in open-loop mode controls the motor based on the output frequency and voltage.

For example:

• Frequency command: 50Hz;
• Output voltage calculated according to motor model;
• Motor speed estimated by inverter algorithm.

This type of control does not require an encoder.

However, in closed-loop vector control, the inverter must continuously know:

• Actual motor speed;
• Rotor position;
• Rotation direction;
• Speed deviation.

Therefore, an encoder is installed on the motor shaft.

The control process is:

Speed Command
      ↓
Vector Control Algorithm
      ↓
IGBT Output Three-Phase Power
      ↓
Motor Rotation
      ↓
Encoder Detects Actual Speed
      ↓
PG Card Processes Feedback Signal
      ↓
CPU Receives Feedback Data
      ↓
Adjusts Output Frequency and Torque

The encoder acts like the “eyes” of the inverter.

If the encoder signal disappears, the inverter cannot accurately determine the motor operating condition, so it triggers Err20 protection.

---

2. Main Causes of AnyHz FST-650 Err20 Fault

According to the FST-650 technical documentation, Err20 is mainly related to encoder feedback abnormalities. The possible causes include:

1. Incorrect encoder type setting;
2. Incorrect encoder wiring;
3. Damaged encoder;
4. Faulty PG feedback card.

In practical applications, these causes can be divided into several categories.

---

2.1 Incorrect Encoder Type Setting

This is one of the most common reasons for Err20.

The FST-650 supports different feedback devices, such as:

• Incremental AB encoder;
• ABZ encoder;
• UVW encoder;
• Resolver.

Different encoder types output completely different signals.

For example:

Actual hardware:

Incremental encoder
A+
A-
B+
B-

But inverter parameter setting:

UVW encoder

The encoder itself may be working normally, but the inverter receives an incompatible signal format.

The result:

Encoder signal abnormal
        ↓
No valid speed feedback
        ↓
Err20 alarm

---

2.2 Encoder Wiring Failure

Encoder systems usually contain several signal lines:

Signal	Function
+5V	Encoder power supply
GND	Power ground
A+	Channel A positive signal
A-	Channel A negative signal
B+	Channel B positive signal
B-	Channel B negative signal
Z+	Zero pulse signal
Z-	Zero pulse return signal

Any problem in these connections may cause Err20.

Common wiring problems include:

• Broken encoder cable;
• Loose connector;
• Poor grounding;
• Incorrect phase connection;
• Damaged shielding layer.

For example:

If the encoder power supply line is disconnected:

Encoder has no power
        ↓
No pulse output
        ↓
PG card receives no signal
        ↓
Err20

---

2.3 Encoder Damage

Encoders are precision electronic components. Long-term operation may cause:

• Optical sensor aging;
• Internal IC failure;
• Mechanical shaft damage;
• Dust or moisture contamination;
• Vibration damage.

Typical symptom:

The inverter powers on normally.

However:

When the motor starts running:

Motor rotates
       ↓
Encoder should output pulses
       ↓
No feedback detected
       ↓
Err20 appears

At standstill, the problem may not be obvious because the encoder is not generating speed pulses.

---

2.4 PG Card Failure

The PG card is the interface between the encoder and inverter CPU.

Its function:

Encoder signal
       ↓
Signal conditioning
       ↓
Voltage conversion
       ↓
Filtering
       ↓
CPU feedback input

If the PG card fails, even a good encoder cannot provide feedback to the inverter.

Typical PG card failures:

• Input circuit damage;
• RS422 receiver failure;
• Optical isolation failure;
• Power supply abnormality;
• Poor connector contact.

---

3. First Maintenance Step: Confirm Whether an Encoder Is Actually Required

A very common situation in the field is:

The inverter reports Err20, but the motor does not have an encoder.

This usually happens after:

• Parameter reset;
• Replacement of inverter;
• Second-hand equipment installation;
• Incorrect commissioning.

Example:

Original system:

Standard motor
+
V/F control

After parameter modification:

Closed-loop vector control enabled

The inverter starts searching for encoder feedback:

No encoder signal
        ↓
Err20

---

Check Control Mode Parameter

Enter the inverter parameter menu and check the control mode.

If the inverter is set to:

Closed-loop vector control

then the system must have:

• Encoder;
• PG card;
• Correct encoder parameters.

If the machine does not use an encoder, change the control mode to:

V/F Control

or:

Sensorless Vector Control

Then save the parameters and restart the inverter.

---

4. Complete Err20 Troubleshooting Procedure

The following procedure is suitable for field maintenance.

---

Step 1: Determine When Err20 Appears

Situation A: Err20 appears immediately after power-on

Possible causes:

• Wrong parameters;
• PG card failure;
• Encoder configuration mismatch.

Focus on:

• Control mode;
• Encoder type;
• PG card installation.

---

Situation B: Err20 appears only after motor starts

Possible causes:

• Encoder signal loss;
• Encoder cable problem;
• Encoder damage.

Focus on:

• Encoder output waveform;
• Cable continuity;
• Mechanical installation.

---

Step 2: Check Whether a PG Card Exists

Open the inverter control section.

Confirm whether a PG expansion card is installed.

If:

• Control mode = closed-loop vector;
• No PG card installed;

then Err20 is expected.

The solution is:

Change the control mode.

---

Step 3: Check Encoder Power Supply

Use a multimeter.

Measure:

Encoder +5V – GND

Normal value:

Approximately:

5V DC

If voltage is:

• 0V;
• unstable;
• significantly lower;

check:

• PG card power supply;
• Cable short circuit;
• Encoder internal failure.

---

Step 4: Check Encoder Output Signal

For incremental encoders:

Rotate the motor shaft manually.

The A and B channels should generate pulse changes.

Normal signal:

A channel:

0V → 5V → 0V → 5V

B channel:

Phase shifted 90° from A channel

If there is no signal:

Possible causes:

• Encoder failure;
• Missing power supply;
• Broken cable.

---

Step 5: Verify Encoder Parameters

Important parameters include:

Encoder Type

The inverter setting must match the actual encoder.

Example:

Actual:

AB incremental encoder

Parameter:

AB encoder

Incorrect:

Resolver

or:

UVW encoder

---

Encoder Resolution

Example:

Encoder nameplate:

1024 P/R

Parameter must be:

1024

Incorrect pulse number settings may cause:

• Incorrect speed feedback;
• Speed deviation;
• Err20 alarm.

---

5. Typical Field Repair Case

Fault Description

A machine equipped with AnyHz FST-650 inverter shows:

Err20

The motor cannot start.

---

Inspection Results

1. Motor has no encoder;
2. No PG card installed;
3. Inverter configured for closed-loop vector control.

---

Fault Analysis

The inverter entered closed-loop vector mode.

The CPU expected encoder feedback.

However:

No encoder signal existed.

Therefore:

Missing feedback
        ↓
Encoder fault detection
        ↓
Err20

---

Solution

Change control mode:

Closed-loop vector control
              ↓
Sensorless vector control

Save parameters.

Power cycle inverter.

Result:

Machine returns to normal operation.

---

6. Precautions When Replacing an Encoder

Replacing an encoder is not simply a matter of installing a new component.

Several factors must be considered.

---

6.1 Mechanical Installation

The encoder shaft must be:

• Properly aligned;
• Concentric with the motor shaft;
• Mechanically fixed.

Poor installation may cause:

• Vibration;
• Pulse loss;
• Feedback instability.

---

6.2 Rotation Direction Verification

If A/B phase sequence is reversed:

Symptoms:

• Motor rotates opposite direction;
• Speed feedback abnormal.

Solutions:

• Exchange A and B signals;
• Modify encoder direction parameter.

---

6.3 Encoder Resolution Matching

The replacement encoder must have the same resolution.

Example:

Original:

2048 P/R

Replacement:

1024 P/R

may cause:

• Incorrect speed calculation;
• Speed deviation;
• Control instability.

---

7. Difference Between Err20 and Other FST-650 Faults

Correct fault identification prevents unnecessary replacement.

Err19

Motor auto-tuning fault.

Common causes:

• Incorrect motor parameters;
• Auto-tuning failure.

---

Err20

Encoder feedback fault.

Focus on:

• Encoder;
• PG card;
• Feedback wiring;
• Encoder parameters.

---

Err21

EEPROM read/write fault.

Usually related to:

• Control board memory;
• Parameter storage failure.

---

8. Recommended Repair Strategy

For AnyHz FST-650 Err20 faults, follow this sequence:

1. Confirm control mode

Does the application actually require an encoder?

---

2. Check PG card

Verify:

• Installed or not;
• Connector condition;
• Power supply.

---

3. Check encoder power

Confirm:

+5V supply is stable

---

4. Check encoder output

Verify:

• A/B pulse signals;
• Signal quality;
• Cable condition.

---

5. Verify parameters

Confirm:

• Encoder type;
• Pulse number;
• Motor parameters.

---

Conclusion

The AnyHz FST-650 Err20 fault is essentially a protection response caused by abnormal speed feedback in the closed-loop vector control system.

Although the display message indicates an “encoder fault”, the actual cause may exist in multiple areas:

• Incorrect control mode;
• Wrong encoder configuration;
• Wiring problems;
• Encoder power failure;
• PG card damage;
• Encoder hardware failure.

In practical maintenance work, engineers should avoid immediately replacing the encoder. A systematic troubleshooting approach is more effective:

Control Mode Verification → PG Card Inspection → Encoder Power Check → Signal Measurement → Parameter Verification → Hardware Replacement

Understanding the operating principle of closed-loop vector control allows technicians to diagnose FST-650 Err20 faults faster, reduce unnecessary component replacement, and improve industrial equipment maintenance efficiency.

1. Application Background

In dust extraction fan retrofit projects, the variable frequency drive often needs to accept remote PLC control while retaining a local operating option for commissioning, maintenance, and emergency adjustment.

A typical requirement is as follows:

Remote mode: the PLC sends a 4–20mA analog signal to control fan speed.

Local mode: the operator sets the frequency directly from the VFD keypad.

LI1 is used as the run/stop command input.

LI3 is used to switch between local and remote frequency reference sources.

AO1 provides actual output frequency feedback to the PLC.

AO2 provides actual output current feedback to the PLC.

This control architecture is commonly used for dust extraction fans, exhaust fans, induced draft fans, supply fans, ventilation fans, circulation fans, and other centrifugal fan applications.

Although the wiring appears straightforward, commissioning problems are often caused by inconsistent parameter planning rather than incorrect wiring. Typical issues include selecting the wrong analog input channel, setting the wrong current range, confusing run-command switching with frequency-reference switching, or assigning unsuitable analog output scaling.

The Controlway IE series VFD provides two frequency reference channels, configurable digital inputs, AI1 and AI2 analog inputs, as well as AO1 and AO2 analog outputs. These functions make it suitable for PLC-controlled fan systems requiring both local and remote operation.

2. Define the Control Architecture Before Editing Parameters

Before changing any VFD parameters, the complete control structure should be defined clearly.

For this application, the recommended arrangement is:

Run command source: external terminals.

Run/stop input: LI1.

Remote frequency reference: AI2, 4–20mA signal from PLC.

Local frequency reference: VFD keypad frequency setting.

Frequency reference selection input: LI3.

AO1 output: actual output frequency, 4–20mA.

AO2 output: actual output current, 4–20mA.

The operating logic should be as follows:

In remote mode, the PLC sends a 4–20mA signal to AI2. The VFD converts this analog signal into the target operating frequency.

In local mode, the VFD ignores the remote frequency reference and follows the frequency manually entered through the keypad.

LI1 remains responsible for start and stop control in both local and remote frequency modes.

A critical distinction must be made between run-command source switching and frequency-reference source switching.

Run-command source switching determines whether the VFD start/stop command comes from the keypad, external terminals, or communication.

Frequency-reference source switching determines whether the speed command comes from AI2, AI1, keypad setting, communication, multi-speed inputs, or another source.

In many dust extraction fan projects, only the frequency reference needs to change between local and remote modes. The run/stop command remains controlled through LI1 or the PLC. In that case, the VFD must remain in external terminal run-command mode. Only the frequency source should switch between AI2 and keypad reference.

If the VFD is switched completely to keypad local mode, LI1 start/stop control may no longer function as intended. This is a frequent cause of commissioning confusion.

3. Run Command Configuration

The Controlway IE series normally uses parameter f002 to select the run command channel.

Typical selections are:

f002 = 0: External terminal run command.

f002 = 1: Keypad run command.

f002 = 2: Serial communication run command.

For this application, the recommended setting is:

f002 = 0

This ensures that the fan is always started and stopped through external terminal logic.

LI1 should be configured as a forward run command.

When LI1 is active, the VFD runs the fan.

When LI1 is inactive, the VFD stops the fan.

For a standard one-direction dust extraction fan, LI1 is normally assigned to forward run only. Reverse operation is generally unnecessary and may create process problems, reverse airflow, belt stress, abnormal duct pressure, or unexpected dust movement.

A recommended arrangement is:

LI1: Forward run command.

LI2: Unused, fault reset, or reserved.

Reverse operation: Disabled.

The stop mode should also be selected according to the fan inertia and process requirements. For most dust extraction fans, deceleration stop is preferred because it provides a controlled stop. Free-run stop may cause a large fan to coast for a long period, affecting process interlocks and safety sequencing.

4. AI2 as the PLC 4–20mA Remote Frequency Reference

In remote mode, the PLC analog output should be wired to AI2.

The standard scaling principle is:

4mA = minimum frequency.

20mA = maximum frequency.

Intermediate current values correspond proportionally to intermediate frequencies.

For example, if the fan maximum frequency is 50Hz:

4mA = 0Hz or the minimum allowed operating frequency.

12mA = 25Hz.

20mA = 50Hz.

In many fan applications, the lower limit should not be set to 0Hz. Fans may suffer from poor cooling, unstable airflow, resonance, or insufficient dust extraction at very low speed.

For example:

4mA = 20Hz.

20mA = 50Hz.

Under this configuration, the fan runs at 20Hz when the PLC output is 4mA and reaches 50Hz at 20mA.

The minimum frequency should be determined according to fan curve, motor cooling, duct resistance, process airflow demand, and mechanical vibration conditions.

The Controlway IE series allows separate main and auxiliary frequency references. The recommended configuration is:

f003 = AI2.

f005 = Keypad frequency setting.

f006 = Frequency reference switching mode between f003 and f005.

f021 = Single-channel frequency reference structure.

With this arrangement:

Main frequency reference: AI2, used for remote PLC control.

Auxiliary frequency reference: keypad setting, used for local manual adjustment.

LI3 is then used to switch between the two frequency reference sources.

5. LI3 as the Local/Remote Frequency Reference Selector

LI3 should be assigned to the frequency-reference switching function.

It should not be assigned as a normal run command, stop command, multi-speed input, reset input, or other unrelated function.

A typical operating definition can be:

LI3 OFF: Remote mode, frequency reference from AI2.

LI3 ON: Local mode, frequency reference from keypad.

The opposite logic can also be used:

LI3 ON: Remote mode.

LI3 OFF: Local mode.

Either method is acceptable, but the electrical design, PLC program, switch label, operation manual, and VFD parameter logic must all match exactly.

A common site problem occurs when the selector switch is labeled “REMOTE,” but the actual LI3 state causes the VFD to use keypad frequency. Operators then assume that the PLC system has failed even though the VFD is simply using the wrong reference source.

The panel door should clearly identify the operating condition, for example:

REMOTE: PLC AI2 4–20mA frequency reference.

LOCAL: VFD keypad frequency reference.

RUN/STOP: Controlled by LI1.

The logic input type must also match the PLC output type.

The Controlway IE series supports source logic and sink logic.

For PNP transistor outputs, source logic is normally used.

For NPN transistor outputs, sink logic is normally used.

For relay dry-contact outputs, the actual control supply connection and COM/0V wiring must be checked carefully.

An incorrect source/sink logic setting can cause LI1 or LI3 to operate in reverse, remain permanently active, or fail to respond.

6. AI2 4–20mA Wiring and Signal Considerations

The PLC analog output should generally be connected as follows:

PLC AO+ to VFD AI2.

PLC AO− to VFD analog common or signal COM.

Use shielded twisted-pair cable for the analog signal.

Ground the shield at one end only, normally at the control cabinet side.

Do not route analog signal cables in parallel with motor output cables for long distances.

Keep analog signal cables separate from U, V, W motor cables.

Where crossing is unavoidable, cross at approximately 90 degrees.

A 4–20mA signal is generally more suitable than a 0–10V signal in industrial fan systems, especially where cable runs are long and electromagnetic interference is present.

Advantages include:

Better immunity to electrical noise.

Less influence from cable voltage drop.

More reliable transmission over longer distances.

Ability to detect some open-circuit or signal-failure conditions.

If the PLC output circuit opens or the signal cable is damaged, the analog value may drop below 4mA. Depending on process requirements, the VFD or PLC should include low-signal detection, minimum speed protection, fault alarms, or interlock logic to prevent the fan from operating at an unsuitable low speed.

It is also important to confirm that the actual VFD hardware and firmware version supports AI2 current input. Older manuals or earlier VFD versions may describe AI2 differently. Before commissioning, verify the VFD model, terminal board type, firmware version, and applicable manual revision.

7. AO1 Output Frequency Feedback Configuration

AO1 is used to provide actual VFD output frequency feedback to the PLC.

Recommended configuration:

AO1 signal type: 4–20mA.

AO1 monitored value: Actual output frequency.

4mA = 0Hz.

20mA = Maximum operating frequency.

For a 50Hz fan system:

0Hz = 4mA.

25Hz = 12mA.

50Hz = 20mA.

AO1 normally requires two separate settings:

First, the electrical output type must be set to current output.

Second, the internal monitored variable must be set to output frequency.

These two settings do not conflict. One defines the electrical format of the output signal, while the other defines the process value being transmitted.

For example:

AO1 output type = 4–20mA current output.

AO1 monitored value = output frequency.

The PLC should then scale the received signal correctly. If 4–20mA corresponds to 0–50Hz, the PLC engineering conversion should be:

Actual Frequency = (Measured Current − 4mA) / 16mA × 50Hz.

Incorrect PLC scaling can make the display value incorrect even when the VFD output is functioning properly.

8. AO2 Output Current Feedback Configuration

AO2 is used to provide the actual motor output current to the PLC.

This signal can be used for:

Motor load monitoring.

Fan blockage detection.

Belt slip indication.

Fan impeller fouling analysis.

Filter blockage trend monitoring.

Overload warning.

Maintenance planning.

Recommended configuration:

AO2 signal type: 4–20mA.

AO2 monitored value: Actual output current.

4mA = 0A.

20mA = VFD rated output current or selected monitoring full-scale current.

For example, if the VFD rated output current is 38A:

4mA = 0A.

20mA = 38A.

The PLC engineering conversion would be:

Actual Current = (Measured Current − 4mA) / 16mA × 38A.

The selected full-scale current must be consistent in three locations:

VFD AO2 scaling.

PLC analog input scaling.

HMI display and alarm thresholds.

If these values are inconsistent, the PLC may show incorrect motor current, false overload alarms, or an inaccurate loading trend.

9. Recommended Parameter Logic Summary

Run command channel:

f002 = External terminal control.

Main frequency reference:

f003 = AI2.

Auxiliary frequency reference:

f005 = Keypad frequency setting.

Frequency source switching:

f006 = Switch between f003 and f005.

Frequency reference structure:

f021 = Single-channel reference.

LI1:

Configure as Forward Run.

LI3:

Configure as Frequency Reference Source Switching.

Logic input type:

Configure according to PLC PNP/NPN output type and actual wiring.

AO1:

Set as current output.

Set monitored value as output frequency.

Set output range as 4–20mA.

AO2:

Set as current output.

Set monitored value as output current.

Set output range as 4–20mA.

Motor and fan protection settings:

Set maximum frequency according to fan design limits.

Set upper frequency limit according to process requirements.

Set lower frequency limit according to minimum stable fan operating speed.

Set acceleration time according to fan inertia.

Set deceleration time according to fan inertia and required stop behavior.

Disable reverse operation unless reverse rotation is specifically required.

Select deceleration stop unless free-run stop is required by the process.

10. Recommended Commissioning Sequence

Do not place the complete PLC control system into automatic operation immediately. Commission the system in stages.

Step 1: Disconnect the PLC analog output or force the PLC output to 4mA.

Step 2: Confirm motor nameplate data, maximum frequency, acceleration time, deceleration time, and rotation direction.

Step 3: Confirm that LI1 starts and stops the fan correctly.

Step 4: Switch LI3 to local mode and verify that keypad frequency setting controls the fan speed.

Step 5: Switch LI3 to remote mode and verify that AI2 receives the PLC 4–20mA signal correctly.

Step 6: Output 4mA, 8mA, 12mA, 16mA, and 20mA from the PLC and confirm that VFD frequency changes linearly.

Step 7: Verify that AO1 feedback matches the actual VFD output frequency.

Step 8: Verify that AO2 feedback matches the VFD current display and a clamp meter reading.

Step 9: Verify PLC display values, alarm thresholds, trend curves, remote/local status, and interlock logic.

Step 10: Run the dust extraction system under actual process load and monitor airflow, duct pressure, fan vibration, motor current, filter differential pressure, and operating stability.

11. Conclusion

The most important point in dust extraction fan VFD retrofit work is not a single parameter value. It is the consistency of the entire control architecture.

AI2 provides the PLC remote 4–20mA frequency reference.

The keypad provides the local frequency reference.

LI1 controls fan start and stop.

LI3 switches between local and remote frequency references.

AO1 sends actual frequency feedback to the PLC.

AO2 sends actual motor current feedback to the PLC.

When the frequency source, run command source, digital inputs, analog inputs, analog outputs, PLC scaling, and operator switch labeling are all coordinated correctly, the system becomes stable, maintainable, and easy to troubleshoot.

---

1. Introduction: Why ERR29 Is Not Just a “Communication Fault Code”

In industrial inverter maintenance, ERR29 is often superficially categorized as a “communication fault.” However, in real-world GOOBELL G500 applications, this fault frequently represents a system-level control failure, involving:

• Control source configuration logic
• Communication state machine failure
• HMI (keypad) UI access locking mechanism
• Internal low-voltage control board instability

A typical field scenario shows the following behavior:

• ERR29 appears immediately after power-on
• No RUN command is required to trigger the fault
• Fault persists even after disconnecting RS485/PLC wiring
• Menu/parameter access is completely blocked
• STOP/RESET cannot restore access

This indicates that the issue is no longer a simple communication wiring problem, but a control architecture-level fault state.

---

2. Overview of GOOBELL G500 Control Architecture

To understand ERR29 correctly, the internal structure must be considered.

2.1 Power Circuit

• Three-phase rectifier stage
• DC bus (approx. 560–600V)
• IGBT inverter module

2.2 Control System (Core Layer)

• Main MCU (control logic processor)
• PWM generation module
• Protection detection circuits (overcurrent, overvoltage, undervoltage, overtemperature)

2.3 Human-Machine Interface (HMI)

• Keypad panel (PRG / ENT / ESC / STOP)
• Internal communication bus between keypad and main board

2.4 External Control Interfaces

• RS485 Modbus communication
• DI/DO terminal control
• PLC remote operation signals

---

3. Actual Meaning of ERR29 in G500 Systems

In GOOBELL G500-type platforms, ERR29 is generally defined as:

External communication loss or invalid communication control source

However, in engineering practice, the key point is:

❗ ERR29 is not only “communication failure”, but also a “control authority loss condition”

When the drive is configured as:

• RUN command source = COMMUNICATION (PLC/RS485)
• Frequency reference = communication-based
• External control enabled

If the inverter detects:

• No valid PLC RUN command
• Communication not established
• Incorrect station address or baud rate

It enters:

Communication Fault Protection State (COMM FAULT LOCK)

---

4. Key Abnormal Symptoms in This Case

This case exhibits three critical symptoms:

4.1 ERR29 appears immediately after power-on

This indicates:

• Fault occurs during initialization phase
• Communication system fails at startup stage

---

4.2 Fault remains even after communication disconnection

This confirms:

• External communication wiring is not the root cause
• Internal logic state remains locked

---

4.3 Menu/parameter access is completely unavailable

This is the most critical symptom:

The UI system is locked at the fault display level.

---

5. Fault Priority Lock Mechanism in G500

The GOOBELL G500 inverter uses a fault priority display system:

When communication control mode is active and communication is lost → the system enters a fault latch mode.

Characteristics:

• Fault screen is permanently displayed (ERR29)
• Keypad menu entry is blocked
• RESET function is partially or fully ineffective
• Control state machine is frozen awaiting communication recovery

---

6. Root Cause Analysis of This Case

Based on full isolation testing (communication removed, reset attempted, power cycling), the fault can be narrowed down to three categories:

---

6.1 Control Mode Latch State Not Cleared (High Probability)

If the drive is configured as:

• Communication control mode enabled
• PLC not responding at startup

The system enters a latched fault state where:

Even after communication is removed, the internal state remains in “waiting for communication” mode.

Result:

• Menu access remains blocked
• UI layer cannot be entered

---

6.2 Keypad-to-Mainboard Communication Failure (Medium Probability)

The keypad is not independent; it communicates with the main control board.

Possible issues:

• Internal communication bus failure
• Loose keypad cable connection
• Keypad IC malfunction

Symptoms:

• Display is normal
• Keys are unresponsive or partially responsive
• Menu cannot be accessed

---

6.3 Low-Voltage Control Power Instability (Medium-Low Probability)

Control board requires stable low-voltage rails:

• +5V logic supply
• +15V driver supply

If +5V is unstable:

• MCU cannot properly execute state transitions
• UI logic becomes frozen
• Fault state cannot be cleared

---

7. Why “Communication Disconnected but Still Faulty” Is Critical

In normal communication faults:

Action	Expected Result
Disconnect RS485	Fault clears
Switch to local mode	Menu accessible

However, in this case:

❗ ERR29 persists even after full isolation

This indicates:

• External control dependency has been removed
• Internal state machine remains locked

---

8. Field Diagnostic Procedure (Engineering Standard)

Step 1: Full isolation of external control

• Disconnect RS485 (A/B/SG)
• Remove PLC control wiring
• Keep only main power input

---

Step 2: Forced reset attempt

• Hold STOP/RESET ≥ 5 seconds
• Repeat multiple times

---

Step 3: UI access verification

Check if menu can be accessed:

• PRG
• Parameter groups
• Monitoring mode

---

Step 4: Keypad function test

Test all keys:

• STOP/RESET
• PRG/MENU
• ENT/ESC
• Arrow keys

---

Step 5: Control voltage measurement

Measure control board supply:

• +5V (4.8–5.1V)
• +15V
• Ground stability

---

9. Fault Classification Model

Level 1: External communication issue

✔ Already excluded

Level 2: Control mode latch state

✔ Most likely cause

Level 3: Keypad/HMI communication fault

✔ Possible

Level 4: Main control board hardware fault

✔ Requires confirmation

---

10. Recommended Repair Strategy

Option 1: Fast recovery method

• Disconnect communication wiring
• Switch to local control mode
• Perform forced reset

Applicable only if menu access is possible

---

Option 2: Module replacement test (recommended)

• Replace keypad panel
• Cross-test UI functionality

---

Option 3: Mainboard-level diagnosis

• Check +5V logic supply
• Verify MCU operation
• Inspect EEPROM/state memory lock

---

11. Key Engineering Insights

This case highlights an important field principle:

ERR29 on GOOBELL G500 is not always a simple communication fault; when accompanied by “no menu access,” it often indicates an internal control-state lock condition rather than an external wiring issue.

Key takeaways:

1. ERR29 is a system-level fault, not only communication-related
2. “No menu access” is more critical than the fault code itself
3. Disconnecting communication without recovery indicates internal logic lock
4. Diagnosis must shift from external wiring to internal control state

---

12. Conclusion

The GOOBELL G500 ERR29 “power-on immediate lockout with no menu access” case represents a multi-layer control system failure involving:

• Communication control configuration
• Internal fault latch mechanism
• UI access restriction logic
• Possible keypad or control board communication failure

The resolution is not limited to parameter adjustment, but requires a structured approach:

• Control source recovery
• Fault latch clearing
• UI communication restoration
• Hardware validation when necessary