Posted on

ABB ACS510 F0009 / MOT TEMP Fault Analysis and Troubleshooting Guide for Motor Overtemperature Protection

The ABB ACS510 is one of the most widely used low-voltage AC drives in HVAC systems, water pumps, constant-pressure water supply systems, ventilation equipment, conveyor systems, industrial fans, and various variable-speed motor applications. In real industrial maintenance work, one of the most common faults encountered on the ACS510 is F0009, also displayed in the fault list as MOT TEMP or Motor Overtemperature.

According to the ABB ACS510 user manual, fault code 9 “MOT TEMP” indicates that the drive has detected a motor overheating condition based on either the internal thermal model calculation or an external temperature feedback signal. ABB recommends checking whether the motor is overloaded, adjusting parameters 3005–3009 related to the motor thermal model, and checking the temperature sensor configuration and parameter group 35 settings.

This fault is frequently misunderstood in the field. Many technicians immediately assume the inverter itself is defective as soon as F0009 appears. In reality, this fault primarily concerns the motor thermal condition rather than the ACS510 heatsink temperature. The ACS510 has separate alarms and faults for drive overtemperature conditions. F0009 specifically focuses on motor thermal protection, including real motor overheating, overload conditions, insufficient cooling at low speed, incorrect motor parameter settings, thermal model mismatch, or external temperature sensor problems.

For this reason, troubleshooting F0009 must follow a systematic process. Resetting the drive repeatedly or replacing boards without analysis often leads to wasted time, unnecessary repair costs, and even motor damage.


F0009 Fault of the ACS510 VFD

1. Understanding the Real Meaning of F0009

The ACS510 determines motor overheating in two primary ways.

The first method is the internal motor thermal model. The drive continuously estimates motor temperature based on:

  • Motor rated current
  • Output current
  • Operating frequency
  • Load conditions
  • Running time
  • Thermal characteristics

When the calculated thermal level exceeds the protection threshold, the drive first may generate a warning and eventually trips with F0009.

The second method is external temperature feedback. If the motor is equipped with a PTC thermistor, PT100 sensor, thermal switch, or other temperature feedback device, and parameter group 35 is enabled, the ACS510 can monitor actual motor temperature through the sensor input.

This explains why the same F0009 fault may have completely different causes depending on the installation.

In some cases the motor is genuinely overheating. In others the issue is caused by incorrect parameters, sensor wiring problems, or thermal model configuration errors.


2. F0009 Does Not Mean the Drive Itself Is Overheating

One of the most common mistakes in industrial troubleshooting is confusing motor overtemperature with inverter overtemperature.

F0009 is specifically related to motor thermal protection.

This does not automatically mean the ACS510 heatsink or power section is overheating.

When the drive itself overheats, troubleshooting usually focuses on:

  • Cooling fan failure
  • Heatsink dust accumulation
  • Poor cabinet ventilation
  • High ambient temperature
  • Improper installation spacing
  • Airflow obstruction

However, when F0009 occurs, the primary focus must remain on:

  • Motor temperature
  • Motor current
  • Mechanical load
  • Motor cooling
  • Thermal protection settings

Even though drive heating and motor heating can occur together under overload conditions, the diagnostic sequence should not start with inverter hardware replacement.


3. Step One: Confirm Whether the Motor Is Actually Hot

The first action after F0009 appears is to verify the real motor temperature.

Use an infrared thermometer or contact thermometer to measure:

  • Motor housing temperature
  • Front bearing temperature
  • Rear bearing temperature
  • Cooling fan area
  • Coupling or pulley area
  • Gearbox or pump bearing temperature

If the motor surface is extremely hot, bearings are overheating, or there is a strong burnt insulation smell, then the fault is likely a real overtemperature condition.

In this situation, repeatedly resetting the drive is dangerous. Continuous restarting may eventually damage motor insulation, burn the winding, or cause mechanical failure.

On the other hand, if the motor is only slightly warm and F0009 occurs quickly after startup, parameter mismatch or sensor issues become more likely.


Industrial Chinese female engineer troubleshooting an ABB ACS510 variable frequency drive inside an electrical control cabinet, measuring PCB signals with multimeter probes while the inverter display shows F0009 motor overtemperature fault.

4. Step Two: Check Whether the Motor Current Exceeds Rated Current

Motor overheating is commonly caused by overload conditions.

The ACS510 should be monitored together with an external clamp meter.

The following values must be compared:

  • Motor nameplate rated current
  • Drive output current
  • Actual measured phase current
  • Phase current balance
  • Starting current
  • Loaded operating current

If the motor is rated at 20A but continuously operates at 25A or higher, overheating is expected.

If the phase currents are significantly unbalanced, such as:

  • Phase A: 18A
  • Phase B: 25A
  • Phase C: 19A

then the problem may involve:

  • Motor winding damage
  • Loose cable connections
  • Output terminal problems
  • Contactor issues
  • Partial short circuit
  • Ground leakage

When the drive display current differs greatly from actual measured current, additional investigation of current feedback or measurement accuracy may be required.


5. Step Three: Inspect Mechanical Load Problems

Many F0009 faults are not electrical failures at all.

Mechanical overload is extremely common.

Typical causes include:

  • Pump blockage
  • Fan blade contamination
  • Damper problems
  • Bearing seizure
  • Belt overtension
  • Gearbox damage
  • Conveyor jams
  • Coupling misalignment
  • Excessive friction
  • Product buildup
  • Increased process load

The inverter only sees increased motor current and rising thermal estimation.

The drive cannot determine the exact mechanical cause.

One effective troubleshooting method is to disconnect the mechanical load temporarily and run the motor unloaded. If the current drops significantly and the overheating fault disappears, the problem is mechanical rather than electrical.


6. Step Four: Low-Speed Operation and Cooling Problems

This is one of the most overlooked causes of motor overheating in variable frequency drive systems.

Standard induction motors use shaft-mounted cooling fans.

When the motor runs at low frequency, such as:

  • 10 Hz
  • 15 Hz
  • 20 Hz

the motor cooling fan also rotates slowly.

As airflow decreases, motor cooling performance drops dramatically.

Even if the current is not extremely high, the motor may gradually overheat.

This problem is especially common in:

  • Conveyors
  • Mixers
  • Compressors
  • Extruders
  • Constant torque applications

Solutions may include:

  • Increasing minimum operating frequency
  • Installing independent cooling fans
  • Using inverter-duty motors
  • Reducing mechanical load
  • Improving ventilation
  • Cleaning motor cooling fins

If the customer reports that the fault occurs mainly during summer or after long low-speed operation, insufficient cooling is a major suspect.


7. Step Five: Verify Motor Nameplate Parameters 9905–9909

The ACS510 motor thermal model relies heavily on accurate motor data.

Incorrect motor parameter settings are a very common cause of F0009.

The following parameters must be checked carefully:

Parameter 9905 — Motor Rated Voltage

This must match the actual motor nameplate voltage.

Parameter 9906 — Motor Rated Current

This is the most critical parameter.

It must match the actual motor nameplate current.

If 9906 is set too low, the ACS510 will falsely estimate motor overheating much earlier than normal.

Parameter 9907 — Motor Rated Frequency

Usually:

  • 50 Hz
  • 60 Hz

depending on the motor.

Parameter 9908 — Motor Rated Speed

Must match the motor nameplate RPM.

Parameter 9909 — Motor Rated Power

Must match actual motor power.

Parameter mismatch frequently occurs when:

  • Motors are replaced
  • Drives are restored to factory settings
  • Used equipment is installed
  • Parameters are copied from another machine
  • Control boards are replaced

For example, if the original motor was 7.5 kW and later replaced with an 11 kW motor while the old current settings remain unchanged, the drive may falsely trip with F0009.


8. Step Six: Check Parameters 3005–3009

The ABB manual specifically recommends checking parameters 3005–3009 when F0009 occurs.

These parameters control the motor thermal protection model.

Parameter 3005 — Motor Thermal Protection

Defines how the drive reacts to thermal overload.

Disabling this protection entirely is not recommended in industrial applications unless external thermal protection exists.

Parameter 3006 — Motor Thermal Time Constant

Defines how quickly the thermal model responds.

If set too low, the drive may trip prematurely.

If set too high, motor protection may become insufficient.

Parameters 3007–3009 — Load Curve and Low-Speed Thermal Characteristics

These parameters influence low-speed motor heating estimation.

Incorrect settings can easily cause false overheating trips.

This is particularly common in:

  • Used drives
  • Systems with modified parameters
  • Equipment with undocumented adjustments

9. Step Seven: Check Parameter Group 35 and Temperature Sensors

If external motor temperature sensors are used, parameter group 35 becomes extremely important.

Common problems include:

  • Open-circuit PTC sensors
  • Incorrect sensor type configuration
  • Broken wiring
  • Loose terminals
  • Grounding problems
  • Analog input interference
  • Incorrect sensor resistance
  • Wrong terminal assignment

In some cases, parameter group 35 is enabled even though no motor temperature sensor exists.

This can directly generate false F0009 faults.

Sensor-related faults often show these characteristics:

  • Motor is physically cool
  • Fault appears immediately after startup
  • Fault changes when wiring is moved
  • Intermittent trips occur randomly

10. Distinguishing Between Alarm and Fault Conditions

The ACS510 may first display a motor overtemperature warning before finally tripping with F0009.

This progression is important.

If the fault develops gradually over time, thermal accumulation is likely.

If the drive trips immediately after startup, parameter or sensor problems are more likely.

If the fault appears mainly in hot weather or during long operating cycles, cooling and environmental conditions become key suspects.


11. Recommended Field Troubleshooting Procedure

A professional troubleshooting sequence should follow these steps:

  1. Record the fault condition.
  2. Measure actual motor temperature.
  3. Measure three-phase motor current.
  4. Inspect mechanical load conditions.
  5. Verify motor nameplate parameters 9905–9909.
  6. Check thermal model parameters 3005–3009.
  7. Inspect parameter group 35 and temperature sensors.
  8. Test the system after reset under controlled load.
  9. Perform insulation resistance testing if necessary.

This structured approach prevents unnecessary board replacement and reduces downtime.


12. Real Overheating vs False Overheating

When the motor is genuinely overheating, the root cause must be corrected physically.

Possible solutions include:

  • Reducing load
  • Repairing bearings
  • Cleaning cooling fins
  • Improving airflow
  • Replacing cooling fans
  • Upgrading motor size
  • Installing forced cooling
  • Correcting alignment
  • Repairing mechanical equipment

Simply disabling thermal protection does not solve the real problem.

When the motor is not actually overheating, the issue usually involves:

  • Incorrect motor parameters
  • Wrong thermal model settings
  • Sensor problems
  • Parameter corruption
  • Wiring errors
  • Control board feedback issues

13. Common Mistakes Made During Troubleshooting

Several mistakes appear repeatedly in industrial service work.

Mistake 1: Assuming the inverter is defective immediately

F0009 primarily concerns the motor thermal condition.

Mistake 2: Repeatedly resetting the drive

This can eventually destroy the motor.

Mistake 3: Disabling thermal protection

This removes a critical protection layer.

Mistake 4: Ignoring mechanical load

Mechanical overload is extremely common.

Mistake 5: Replacing motors without updating parameters

Parameter mismatch causes false trips frequently.

Mistake 6: Ignoring low-speed cooling limitations

This is one of the most common real-world causes.


14. Example Field Case

A water pump system using ACS510 repeatedly generated F0009 during summer operation.

The customer believed the inverter was defective.

Field inspection revealed:

  • Motor current near rated value
  • Long-term operation at 18 Hz
  • Poor ventilation
  • Standard self-cooled motor
  • High ambient temperature

The real issue was insufficient motor cooling at low speed.

The solution included:

  • Cleaning motor cooling fins
  • Improving ventilation
  • Raising minimum frequency
  • Installing independent cooling

No inverter repair was required.

In another case, a larger motor had been installed but parameter 9906 still contained the old motor current value. The drive repeatedly tripped with F0009 after several minutes of operation. Correcting the motor parameters solved the problem immediately.


15. Conclusion

ABB ACS510 fault F0009 / MOT TEMP indicates that the drive believes the motor thermal condition has exceeded safe operating limits. The drive may determine this through the internal thermal model or through external temperature feedback devices.

Successful troubleshooting requires systematic analysis of:

  • Actual motor temperature
  • Motor current
  • Mechanical load
  • Low-speed cooling capability
  • Motor nameplate parameters
  • Thermal protection settings
  • Temperature sensor circuits

The correct diagnostic philosophy is:

Verify real overheating first, then investigate false thermal estimation, and only consider inverter hardware failure after all motor-side causes have been eliminated.

In most real industrial cases, F0009 is caused by:

  • Motor overload
  • Poor cooling
  • Incorrect parameters
  • Mechanical load issues
  • Sensor configuration errors

rather than defective ACS510 hardware itself.

A structured troubleshooting process can prevent unnecessary drive replacement, reduce maintenance costs, avoid repeated downtime, and protect the motor from catastrophic thermal damage.

Posted on

Particle Metrix ZetaView NTA Analyzer Startup Self-Test Failure and Stepper Drive Timeout Fault Diagnosis

1. Overview of the Fault Phenomenon

The Particle Metrix ZetaView is a nanoparticle tracking analysis (NTA) instrument widely used for the characterization of exosomes, viruses, liposomes, nanomaterials, protein aggregates, colloidal suspensions, and other nanoscale particles. Although it appears externally as a compact benchtop laboratory analyzer, internally it integrates a laser illumination system, microscopic imaging system, sample cell positioning mechanism, temperature and fluid control system, camera acquisition module, motion control system, and dedicated analysis software.

One common field failure encountered on this type of instrument is startup initialization failure. After powering on the instrument and launching the ZetaVIEW software, the system cannot complete the self-check procedure. During initialization or Cell Check, the software displays an error message similar to:

A timeout occurred while ZetaVIEW was waiting for the stepper drives to stop.
ZetaVIEW will be stopped without saving the configuration file.
Please contact the ZetaVIEW Video Microscope Administrator.

This error does not simply indicate a software crash or Windows problem. It means that during startup initialization, the software issued a motion command to the internal stepper motor system, but the instrument failed to return the expected “motion completed” or “drive stopped” status within the allowed time window.

For service engineers, this is a critical distinction. Reinstalling the software or replacing the PC may not resolve the issue. In most cases, the fault is associated with one or more of the following subsystems:

  • Sample cell installation or positioning problems
  • Mechanical blockage inside the motion platform
  • Stepper motor or stepper driver failure
  • Home sensor or limit switch malfunction
  • Motion controller communication errors
  • Internal power supply instability
  • Liquid contamination, salt crystallization, or corrosion inside the instrument

Therefore, when a ZetaView analyzer reports a “stepper drives timeout” error during startup, troubleshooting should focus primarily on the internal motion control system rather than the software alone.


Particle Metrix ZetaView NTA analyzer showing a ZetaVIEW software self-test failure with a stepper drive timeout error on the connected computer screen.

2. Basic Internal Structure of the ZetaView NTA Analyzer

Understanding the internal architecture of the analyzer is essential for correct fault diagnosis.

The ZetaView is not merely an optical microscope. Its operation is based on nanoparticle tracking analysis. Nanoparticles suspended in liquid undergo Brownian motion. A laser illuminates the particles inside the sample cell, and the microscopic imaging system captures the scattered light from each particle. The software then calculates particle size distribution by analyzing particle motion trajectories.

To achieve this, the instrument includes several interconnected systems.


2.1 Laser Illumination System

The analyzer requires a stable laser source to illuminate nanoparticles inside the measurement cell. Scattered light from the particles is captured by the camera system.

Laser-related failures usually produce symptoms such as:

  • Dark image
  • No visible particles
  • Weak scattering intensity
  • High optical noise
  • Unstable illumination

However, laser faults generally do not directly trigger “stepper drive timeout” errors unless multiple initialization procedures fail simultaneously.


2.2 Microscopic Imaging System

The instrument includes:

  • Microscope optics
  • Imaging camera
  • Focus adjustment mechanism
  • Optical positioning assembly

The software functions “Auto Alignment” and “Optimize Focus” indicate that the system must move and adjust optical components during initialization.

If the imaging system fails, typical symptoms include:

  • Black image
  • Blurred particles
  • Unstable focus
  • Excessive background noise
  • Missing particle trajectories

Again, these faults alone normally do not generate the specific “waiting for the stepper drives to stop” error unless the motion system involved in focusing is malfunctioning.


2.3 Sample Cell and Fluidic System

The sample cell is where nanoparticle measurements occur. Tubing connections allow sample injection, flushing, and fluid exchange.

The software screen often displays messages such as:

  • Remove Cell Assembly
  • Cell Connected
  • Cell Quality Check

If the sample cell is improperly installed, contaminated, misaligned, or mechanically interfering with the positioning mechanism, the motion platform may fail during initialization.

Common issues include:

  • Misaligned sample cell
  • Salt residue inside the holder
  • Damaged sealing ring
  • Deformed mounting mechanism
  • Mechanical obstruction
  • Improper insertion depth

2.4 Motion Control System

The motion system is the most important subsystem related to this fault.

Inside the analyzer, several precision movements may be controlled by stepper motors:

  • Sample cell positioning
  • Focus adjustment
  • Optical path alignment
  • Stage positioning
  • Internal calibration movement

During startup, the software typically performs:

  • Homing operations
  • Position calibration
  • Focus initialization
  • Alignment verification
  • Motion completion checks

If any axis fails to stop correctly, or if the controller does not receive the expected completion signal, the software eventually reports a timeout error.


Engineer diagnosing and repairing a Particle Metrix ZetaView NTA nanoparticle analyzer with the instrument panel open, using a multimeter and laptop during troubleshooting.

3. Technical Meaning of the Error Message

The key phrase is:

waiting for the stepper drives to stop

This is extremely important.

It means the software successfully communicated with the instrument and attempted to control the internal motion system. The failure occurred after motion commands were already issued.

This implies several important conclusions:

  1. The instrument is at least partially communicating with the PC.
  2. The motion initialization process has started.
  3. The software is waiting for confirmation that the stepper-driven mechanism has stopped or reached its target position.
  4. That confirmation never arrived within the allowed time.

Therefore, the root problem lies somewhere within the motion control chain:

  • Mechanical movement
  • Stepper motors
  • Driver electronics
  • Home sensors
  • Limit switches
  • Motion feedback logic
  • Controller communication

This is not primarily a Windows or GUI software problem.


4. Common Causes of the Fault

4.1 Sample Cell Assembly Problems

The appearance of “Remove Cell Assembly” suggests that the software is checking sample cell status during startup.

If the sample cell is:

  • Improperly seated
  • Mechanically obstructing movement
  • Contaminated
  • Deformed
  • Incorrectly installed

the initialization sequence may fail.

This is particularly common when:

  • Operators force the cell into position
  • Salt crystals accumulate
  • Sample liquid leaks into the holder
  • The positioning mechanism becomes misaligned

A practical first step is always:

  1. Power off the instrument
  2. Remove the sample cell
  3. Clean the mounting area
  4. Restart the analyzer
  5. Retry initialization

If the instrument passes startup without the cell installed, the fault is strongly related to the sample cell assembly or associated positioning mechanism.


4.2 Mechanical Blockage

Mechanical resistance is one of the most common causes of stepper timeout errors.

Typical sources include:

  • Dried sample residue
  • Salt crystallization
  • Corrosion
  • Contaminated guide rails
  • Damaged bearings
  • Misaligned sliders
  • Bent lead screws
  • Foreign debris inside the motion path

Typical symptoms:

  • Humming motor without movement
  • Clicking or knocking sounds
  • Intermittent startup success
  • Axis stalling during homing
  • Excessive resistance during manual movement

NTA analyzers often operate with biological buffers and saline solutions. Even small liquid leaks can eventually contaminate precision mechanical assemblies.


4.3 Stepper Motor Failure

Stepper motors themselves can fail, although this is less common than mechanical blockage or driver board faults.

Possible motor-related issues include:

  • Open motor winding
  • Shorted winding
  • Connector failure
  • Bearing seizure
  • Motor overheating
  • Insufficient holding torque
  • Damaged cables

Diagnostic methods include:

  • Measuring winding resistance
  • Checking motor holding torque
  • Observing motor vibration
  • Listening for abnormal noise

A motor that vibrates but does not rotate often indicates either:

  • Mechanical blockage
  • Incorrect drive signals
  • Coil phase problems
  • Driver current failure

4.4 Stepper Driver Board Failure

The stepper driver board converts motion commands into motor current.

Failures may involve:

  • Burned driver ICs
  • Overcurrent protection triggering
  • Damaged MOSFETs
  • Corroded PCB traces
  • Loose connectors
  • Missing enable signals
  • Driver overheating
  • Power supply collapse

Typical symptoms:

  • Motor has no holding torque
  • Motor briefly moves then stops
  • Driver IC overheating
  • Repeated startup failures
  • Axis movement instability

Because many ZetaView instruments use proprietary motion control boards, board-level diagnosis may require oscilloscope testing and electronic repair skills.


4.5 Home Sensor or Limit Switch Failure

During startup, the instrument typically performs homing operations.

The motion axis moves toward a reference position until:

  • A home sensor activates
  • A limit switch changes state
  • A position feedback signal is detected

If this feedback never occurs, the software waits indefinitely until timeout.

Common causes include:

  • Dust blocking optical sensors
  • Broken limit switches
  • Misaligned sensor flags
  • Loose sensor connectors
  • Broken wires
  • Failed Hall sensors
  • Corroded optical interrupters

This is one of the most common root causes of startup timeout faults.


4.6 Internal Power Supply Problems

Motion systems require stable power.

Typical internal voltages include:

  • 24V motor supply
  • 12V auxiliary supply
  • 5V logic supply

Power-related faults may produce:

  • Random startup failures
  • Weak motor movement
  • Driver resets
  • Unstable communication
  • Excessive ripple noise
  • Voltage drop during motion

Important diagnostic points include:

  • Voltage stability under load
  • Ripple measurement
  • Capacitor aging
  • Connector oxidation
  • Power supply overheating

A static voltage reading alone is insufficient. Dynamic measurements during motor movement are far more useful.


4.7 Communication or Software Configuration Issues

Although the primary fault is usually hardware-related, communication problems should still be considered.

Potential issues include:

  • USB communication instability
  • Driver mismatch
  • Incorrect software version
  • Permission conflicts
  • Corrupted configuration files
  • PC power management problems

However, if the software already reaches the Cell Check interface and displays “Cell Connected,” communication is likely at least partially functional.

Therefore, communication issues are usually secondary rather than primary causes.


5. Recommended Troubleshooting Procedure

Step 1 – Record the Complete Failure Behavior

Before disassembly, record:

  • Software version
  • Exact error message
  • Startup timing
  • Motor sounds
  • Recent maintenance history
  • Sample leakage history
  • Transport history
  • Environmental conditions

This information greatly improves diagnostic efficiency.


Step 2 – Perform Minimal Startup Configuration

Reduce the system to the simplest possible state:

  1. Remove the sample cell
  2. Disconnect unnecessary peripherals
  3. Restart the analyzer
  4. Observe initialization behavior

If startup succeeds without the sample cell installed, focus on the cell assembly mechanism.


Step 3 – Listen to Internal Motion Behavior

Motor sounds provide valuable clues.

No sound at all

Possible causes:

  • No power
  • Dead driver board
  • Controller not issuing commands

Humming without movement

Possible causes:

  • Mechanical blockage
  • Insufficient drive current
  • Jammed axis

Repetitive clicking

Possible causes:

  • Failed homing
  • Sensor malfunction
  • Axis hitting mechanical stop

Brief movement then timeout

Possible causes:

  • Feedback failure
  • Motion interruption
  • Controller communication issue

Step 4 – Inspect Mechanical Assemblies

Check for:

  • Corrosion
  • Salt deposits
  • Contamination
  • Misalignment
  • Loose couplings
  • Damaged rails
  • Broken belts
  • Liquid intrusion

Mechanical inspection should always be performed carefully to avoid disturbing optical alignment.


Step 5 – Check Home Sensors and Limit Switches

Measure:

  • Sensor supply voltage
  • Output signal switching
  • Connector integrity
  • Wiring continuity

A failed home sensor can completely prevent successful initialization even if the motor itself is functioning normally.


Step 6 – Test Motors and Driver Boards

Key checks include:

  • Winding resistance
  • Driver board supply voltage
  • Enable signals
  • STEP/DIR signal activity
  • Motor holding torque
  • Driver temperature

Oscilloscope testing may be required for advanced diagnosis.


Step 7 – Verify Power Supplies

Measure:

  • 24V rail
  • 12V rail
  • 5V rail
  • Ripple voltage
  • Voltage sag during motion

Aging capacitors frequently cause intermittent startup problems in older laboratory instruments.


6. Repair Approaches

Depending on the root cause, repairs may involve:

  • Cleaning contamination
  • Realigning sample cell assemblies
  • Replacing sensors
  • Repairing motion rails
  • Replacing driver ICs
  • Rebuilding power supplies
  • Repairing corroded PCBs
  • Replacing damaged stepper motors
  • Reconfiguring software settings

After repair, the instrument must pass:

  • Startup initialization
  • Cell Quality Check
  • Auto Alignment
  • Optimize Focus
  • Standard particle testing

Only then can the repair be considered complete.


7. Important Diagnostic Distinctions

Software startup failure is not the same as self-test failure

If the software does not launch at all, the issue may be PC-related.

If the software launches but reports stepper timeout during initialization, the fault is inside the instrument.


“Cell Connected” does not mean the analyzer is healthy

This only confirms partial communication. Motion systems, optics, and sensors may still be malfunctioning.


Motor noise does not guarantee proper movement

A powered stepper motor may hum even when stalled.


Smooth mechanics do not guarantee healthy sensors

The axis may move correctly while the controller still fails to detect home position feedback.


Static voltage readings can be misleading

Power supplies may appear normal without load but collapse during motor operation.


8. Preventive Maintenance Recommendations

To reduce future failures:

  • Clean the sample cell after every use
  • Prevent liquid leakage
  • Avoid salt crystallization
  • Periodically exercise the instrument
  • Avoid forcing mechanical assemblies
  • Inspect tubing regularly
  • Monitor unusual startup sounds
  • Keep internal motion systems clean

Proper preventive maintenance significantly reduces the risk of motion system failures.


9. Conclusion

The “waiting for the stepper drives to stop” timeout error on a Particle Metrix ZetaView NTA analyzer is fundamentally a motion control initialization failure rather than a simple software problem.

The root cause usually lies in one or more of the following areas:

  • Mechanical blockage
  • Stepper motor failure
  • Driver board malfunction
  • Home sensor failure
  • Motion controller faults
  • Internal power instability
  • Sample cell positioning issues

Effective troubleshooting requires a structured approach:

  1. Observe startup behavior
  2. Listen to motor activity
  3. Inspect mechanics
  4. Verify sensors
  5. Test power supplies
  6. Diagnose driver electronics
  7. Validate software configuration

For precision laboratory instruments such as the ZetaView, successful repair means more than simply reopening the software. The analyzer must complete initialization, pass Cell Check procedures, perform stable Auto Alignment, and generate reliable nanoparticle measurements before the repair can be considered complete.

In practical field service, the “stepper drives timeout” message is actually highly valuable because it clearly narrows the problem to the motion control system. Once the troubleshooting process is focused on motors, sensors, mechanics, power supplies, and motion feedback signals, the fault can usually be isolated efficiently and repaired systematically.

Posted on

Rotork YT3300 Smart Valve Positioner Output Air at 4 mA: Technical Fault Analysis and Troubleshooting Guide

1. Fault Background: Air Output from Port 1 at Minimum Signal

In a pneumatic control valve system, the smart valve positioner receives a 4–20 mA control signal and converts it into a pneumatic output to move the actuator. Under normal conditions, 4 mA usually corresponds to 0% valve position, while 20 mA corresponds to 100% valve position. Some applications may use reverse action, but the positioner should still control the actuator proportionally and stably.

In this case, the device is a Rotork YT3300 smart valve positioner. The customer reported that when only 4 mA is applied, air immediately comes out from output port 1, causing the actuator to move. At the same time, the LCD shows “CHK AIR”.

This is not normal. It means the positioner is not forming a stable closed-loop control between the input signal, pneumatic output, actuator movement, and position feedback. The problem may come from the air supply, tubing connection, actuator direction, feedback linkage, calibration data, internal pneumatic module, or electronic control circuit.


Rotork YT3300 smart valve positioner installed on a pneumatic actuator, showing a CHK AIR alarm, pressure gauge, blue pneumatic tubing, and industrial piping background.

2. How the Rotork YT3300 Works

The YT3300 receives a 4–20 mA signal from the control system. It compares the target valve position with the actual valve position detected by its feedback mechanism. If the valve is not at the requested position, the positioner increases or decreases pneumatic output until the actuator reaches the target position.

The basic logic is:

Control system sends 4–20 mA signal.
Positioner calculates the target valve position.
Feedback mechanism detects actual valve position.
Positioner compares target and actual position.
If correction is needed, it adjusts pneumatic output.
The actuator moves the valve.
The positioner stops adjusting when the valve reaches the target.

Therefore, if 4 mA is applied and output port 1 immediately releases strong air pressure, the positioner may be trying to correct a position error, or the pneumatic output may be uncontrolled due to internal or external faults.


Rotork YT3300 positioner working principle and troubleshooting diagram, showing 4–20 mA input signal, OUT1 and OUT2 air connections, double-acting actuator, and diagnostic flow for 4 mA output air fault.

3. Meaning of “CHK AIR”

The display message “CHK AIR” generally indicates that the positioner wants the air supply or pneumatic circuit to be checked. It does not always mean that there is no air supply. It may also appear when the positioner sends a pneumatic control command but does not see the expected valve movement through the feedback signal.

Possible reasons include:

Insufficient air pressure.
Unstable air supply.
Air supply port and output port connected incorrectly.
OUT1 and OUT2 connected in reverse.
Actuator diaphragm leakage.
Actuator or valve stuck mechanically.
Internal pilot valve or pneumatic amplifier stuck.
Nozzle or restriction blocked.
Feedback lever not moving correctly.
Wrong actuator action setting.
Auto calibration not completed.
Positioner parameters not matching the valve and actuator.

In this case, because air comes directly from output 1 at 4 mA and the display shows “CHK AIR”, the positioner is very likely unable to control the pneumatic output correctly.


Cutaway internal structure diagram of a Rotork YT3300 smart positioner, showing the LCD display, main PCB, position sensor, feedback lever, pilot valve, pneumatic amplifier, nozzle flapper, supply port, output ports, and exhaust port

4. Possible Cause 1: Air Supply Pressure or Air Quality Problem

The YT3300 requires clean, dry, and stable instrument air. The nameplate indicates a supply pressure range of approximately 0.14–0.7 MPa, equal to about 1.4–7 bar.

If the air pressure is too low, the actuator may not move correctly and the positioner may show “CHK AIR”. If the pressure is too high, the pneumatic output may become too aggressive and unstable. If the air contains water, oil, rust, or dust, the internal pneumatic amplifier, nozzle, restriction, or valve spool may become blocked or stuck.

The following checks should be done first:

Check the pressure regulator outlet pressure.
Observe whether the pressure drops during actuator movement.
Drain the filter bowl and check for water or oil.
Make sure the air source is connected to the supply port, not to OUT1 or OUT2.
Use clean instrument air for testing if possible.
Check all pneumatic fittings for leakage.

Many positioner faults are caused by poor air quality. If dirty air enters the positioner, cleaning the external tubing alone will not solve the problem. The internal pneumatic module may already be contaminated.


Close-up industrial photo of a Rotork YT3300 smart valve positioner with CHK AIR warning on the display, pressure gauge, pneumatic air lines, and valve actuator assembly.

5. Possible Cause 2: Wrong Pneumatic Tubing Connection

Wrong tubing connection is a very common cause of this type of fault.

For a single-acting actuator, usually only one output port is used. For a double-acting actuator, OUT1 and OUT2 are connected to two different actuator chambers. If OUT1 and OUT2 are reversed, the valve may move in the opposite direction from what the positioner expects.

In that situation, the positioner tries to correct the valve position, but the valve moves in the wrong direction. The positioner then increases output even more, causing strong air output and possible alarm.

The following must be confirmed:

Is the actuator single-acting or double-acting?
Is the valve air-to-open or air-to-close?
Should 4 mA mean fully closed or fully open?
Where is OUT1 connected?
Where is OUT2 connected?
Is the supply air connected to the correct supply port?
Is the exhaust port blocked?

If the customer only says “air comes out from OUT1 at 4 mA”, that alone is not enough to confirm the positioner is damaged. The actuator type, valve action, and tubing connection must be checked first.


6. Possible Cause 3: Lost or Incorrect Calibration

A smart positioner must be calibrated after installation. It needs to learn the valve’s zero position, full stroke position, feedback range, movement direction, and actuator response.

If the calibration data is lost or wrong, the positioner may misunderstand the actual valve position. For example, it may think the valve is still far away from the requested 4 mA position, so it continues to output air.

Common symptoms of wrong calibration include:

Valve not closed at 4 mA.
Valve not fully open at 20 mA.
Valve moves in the wrong direction.
Valve hunts or oscillates around the target position.
LCD shows air or stroke-related alarm.
Auto calibration fails.
Displayed valve position does not match actual valve position.

Before recalibration, the following conditions must be satisfied:

Air supply is clean and stable.
Tubing is connected correctly.
Actuator is not stuck.
Feedback linkage is installed correctly.
Valve can move through the full stroke.
Input signal is stable.
No major leakage exists.

If these conditions are not met, auto calibration may fail or store incorrect data again.


7. Possible Cause 4: Feedback Lever or Position Feedback Problem

The positioner does not control the valve only by the 4–20 mA signal. It must also receive correct position feedback from the valve stem or actuator shaft.

If the feedback linkage is loose, disconnected, reversed, or outside its mechanical range, the positioner will not know the real valve position. It may keep outputting air because it believes the valve has not reached the target.

Typical feedback-related problems include:

Valve moves but the position display does not change.
Position display changes in the opposite direction.
Feedback lever is loose.
Linkage is stuck.
Feedback angle is too large or too small.
Lever hits mechanical limit before full valve travel.
Auto calibration cannot complete the stroke.

The customer should check whether the valve stem moves when air is applied, and whether the LCD valve position changes accordingly. If the actuator moves but the display does not follow, the feedback mechanism is the first suspect.


8. Possible Cause 5: Actuator or Valve Mechanical Problem

The positioner may be good, but the actuator or valve may be mechanically stuck.

If the valve stem is jammed, the actuator diaphragm is leaking, the cylinder seal is damaged, or the valve packing is too tight, the positioner may continuously increase air output while the valve does not move properly. This can also trigger “CHK AIR”.

Mechanical causes include:

Actuator diaphragm rupture.
Cylinder seal leakage.
Broken or weak spring.
Valve stem corrosion.
Packing gland too tight.
Valve plug stuck by process deposits.
Linkage looseness.
Mechanical stop incorrectly adjusted.
Actuator internal wear.

To test this, disconnect the positioner output and apply controlled air directly to the actuator. The valve should move smoothly from closed to open and back again. If direct air operation is not smooth, the actuator or valve body must be repaired before working on the positioner.


9. Possible Cause 6: Internal Pneumatic Module Fault

If air supply, tubing, actuator, feedback linkage, and calibration are all correct, but OUT1 still releases air uncontrollably at 4 mA, the internal pneumatic module is likely faulty.

Inside a smart positioner, the electrical control signal drives a pneumatic control system, such as a nozzle, flapper, pilot valve, pneumatic amplifier, spool, diaphragm, restriction, and exhaust passage. If the internal valve spool is stuck in the supply position, output air may flow continuously regardless of input signal.

Typical signs of internal pneumatic module failure include:

OUT1 keeps supplying air regardless of 4 mA, 12 mA, or 20 mA.
Output does not change logically with input signal.
Air leaks continuously from output or exhaust.
Auto calibration always fails.
There is abnormal internal air noise.
Light tapping changes the output temporarily.
Problem remains after correct calibration.

Common causes include dirty air, water contamination, oil contamination, rust particles, long-term storage, corrosion, damaged diaphragm, or aged internal seals.

If this is confirmed, the pneumatic module, pilot valve, diaphragm, nozzle assembly, or whole positioner may need repair or replacement.


10. Possible Cause 7: Electronic Board Fault

Electronic board failure is possible, but it should not be the first conclusion. In many real cases, pneumatic and mechanical problems are more common than electronic failure.

Electronic-related problems may include:

4–20 mA input detection fault.
A/D conversion failure.
Position sensor signal fault.
Electropneumatic driver fault.
Parameter memory failure.
Keypad or LCD abnormality.
Water ingress or corrosion in wiring chamber.

Signs of electronic fault include:

LCD display abnormal.
Buttons not responding.
Input current changes but display does not change.
Valve position value jumps randomly.
Positioner restarts repeatedly.
Parameters cannot be saved.
Calibration always fails at the same step.
No correct control signal is sent to pneumatic module.

If another identical positioner is available, the fastest method is cross-testing. If the fault follows the electronic board, the board is faulty. If the fault follows the pneumatic module, the problem is pneumatic.


11. Recommended Troubleshooting Procedure

For this fault, the recommended sequence is:

First, confirm the valve and actuator type.
Find out whether the actuator is single-acting or double-acting.
Confirm whether the valve is air-to-open or air-to-close.
Confirm whether 4 mA should mean closed or open.

Second, check the air supply.
Confirm pressure is within the correct range.
Drain the filter regulator.
Check for water, oil, and dirt.
Make sure pressure remains stable during movement.

Third, check tubing.
Confirm supply, OUT1, OUT2, and exhaust connections.
Make sure there is no reversed or wrong connection.

Fourth, check the actuator.
Operate the actuator directly with controlled air.
Confirm smooth full-stroke movement.

Fifth, check feedback.
Move the valve and verify that the positioner display changes correctly.
Confirm feedback direction and mechanical linkage.

Sixth, perform complete auto calibration.
Do this only when air, actuator, tubing, and feedback are confirmed normal.

Seventh, isolate the positioner output.
Disconnect the actuator tubing and observe OUT1 and OUT2 at 4 mA, 12 mA, and 20 mA.

Eighth, inspect the internal pneumatic module or electronic board if the fault remains.

This sequence avoids unnecessary replacement of expensive parts.


12. Information Needed from the Customer for Remote Diagnosis

For remote technical support, the customer should provide the following:

Clear photo of the positioner nameplate.
Clear photo of all pneumatic tubing connections.
Video showing pressure gauge during operation.
Video at 4 mA, 12 mA, and 20 mA.
Video showing valve stem or actuator movement.
Photo or video of feedback linkage.
Information on whether the actuator is single-acting or double-acting.
Information on whether the valve is air-to-open or air-to-close.
Video of auto calibration until the alarm appears.
Video of OUT1 and OUT2 output with actuator tubing disconnected.

These details are essential. Without them, it is easy to mistake a tubing or calibration problem for a damaged positioner.


13. Important Safety Notes

Do not increase air pressure blindly.
“CHK AIR” does not always mean the pressure is too low. Increasing pressure may cause violent valve movement.

Do not perform auto calibration while the valve is connected to a live process unless the process allows full valve travel.

Do not force the valve mechanically during diagnosis.

Do not replace the electronic board before checking air supply, tubing, actuator, and feedback.

Do not continue testing with dirty or wet air. It may further damage the pneumatic module.

Always confirm the required fail-safe position of the valve before changing parameters.


14. Repair Decision

If the problem is caused by air pressure, tubing, feedback linkage, or calibration, repair is usually simple and does not require replacing the positioner.

If the actuator or valve is stuck, the actuator or valve body must be repaired first.

If the internal pneumatic module is contaminated or stuck, the pilot valve, pneumatic amplifier, diaphragm, nozzle, or related seals may need cleaning or replacement.

If the electronic board or position sensor is faulty, the electronic module may need replacement, followed by complete calibration.

If the positioner is old, heavily contaminated, or both pneumatic and electronic sections are damaged, replacing the complete positioner may be more economical and reliable.


15. Case Conclusion

In this case, the Rotork YT3300 outputs air from port 1 at only 4 mA and shows “CHK AIR”. The most likely causes are:

Wrong air tubing or actuator action configuration.
Lost or incorrect calibration.
Feedback linkage problem.
Actuator or valve mechanical problem.
Internal pneumatic module stuck or contaminated.

The first recommended actions are:

Check air pressure and air quality.
Confirm all tubing connections.
Confirm actuator type and valve action.
Check whether the feedback display follows valve movement.
Perform complete recalibration only after the above items are correct.
If the output remains uncontrolled, inspect the internal pneumatic module.

The key point is that this fault should not be treated only as an electronic failure. A valve positioner is a closed-loop electropneumatic control device. The input signal, pneumatic output, actuator movement, and feedback signal must all match each other. If any one of these links is wrong, the positioner may output air continuously and show an air-related alarm.

A systematic troubleshooting method is the fastest and safest way to solve this type of Rotork YT3300 fault.

Posted on

Systematic Troubleshooting of Rhinestone Setting Machines: Nozzle Pickup Failure, Wheel Jamming, Excessive Pneumatic Speed, and Fabric Damage

Rhinestone setting machines, ultrasonic rhinestone machines, and automatic stone pickup machines are widely used in garments, shoes, bags, decorative fabrics, and fashion accessories. Their working principle looks simple: the feeding plate arranges rhinestones, the nozzle or needle picks up one stone, the machine moves to the target position on the fabric, and then the stone is fixed by pneumatic pressing, ultrasonic energy, or thermal pressure.

However, in real maintenance work, these machines often show confusing symptoms: the nozzle does not pick stones, the feeding wheel gets stuck, the needle collides with the plate, the machine moves too fast even when the operator has reduced the speed, the wheel does not rotate smoothly, or the machine finally works but the stone cuts through the fabric.

These problems are frequently misdiagnosed. Many users immediately suspect the main board, control program, solenoid valve, cylinder, nozzle, or plate. Some replace the needle, plate, cylinder, or linkage assembly without solving the problem. In many cases, the real cause is not one damaged component, but a combination of pneumatic pressure, vacuum suction, nozzle height, pickup alignment, feeding plate condition, and process parameters.

This article uses a real troubleshooting case of a HUAGUI-type rhinestone setting machine as the basis for analysis. The machine showed several typical complaints: “nozzle not working,” “stuck with wheel,” “stone not working,” “machine is too quick,” and finally “air pressure is so strong, fabric cut by stone.” The goal of this article is to provide a clear, practical, and logical troubleshooting method for technicians, machine users, and remote support engineers.

Realistic blue rhinestone hotfix setting machine with dual transparent feeding plates, pneumatic nozzle head, vacuum tubes, air regulator, control panel, and rhinestones on a workbench.

1. Basic Working Principle of a Rhinestone Setting Machine

A typical rhinestone setting machine consists of several coordinated systems.

The first part is the feeding plate, often called the wheel or plate by users. The plate may be marked with sizes such as SS6, SS8, SS10, and so on. It must match the rhinestone size. Its purpose is to guide loose rhinestones into an organized path and deliver one stone to the pickup point.

The second part is the nozzle or needle. The nozzle is a small metal tip with a tiny hole inside. It uses vacuum suction to pick up one rhinestone from the feeding position. If the nozzle is blocked, bent, installed too low, or not aligned with the pickup point, the machine will fail to pick stones.

The third part is the pneumatic system. Many machines use Festo or similar air preparation units, including an air filter, regulator, pressure gauge, and water separator. Compressed air drives cylinders through solenoid valves. The cylinders then move the nozzle, press head, or mechanical linkage.

The fourth part is the vacuum system. Some machines use a small vacuum pump, while others use a pneumatic vacuum generator. Without stable vacuum suction, the nozzle cannot pick up stones.

The fifth part is the pressing or ultrasonic bonding system. Some machines use ultrasonic energy to bond the rhinestone to fabric. Others use heat or mechanical pressure. Controls such as MARKING, ULTRASONIC SWITCH, or pressing time settings may affect bonding strength, pressure duration, or ultrasonic energy.

The sixth part is the control panel. Common buttons include AUTO/MAN, UP/DOWN, COUNT, TIME, CLEAN PLATE, WHEEL, VACUUM, and MARKING. It is important to understand that the speed or time settings on the panel may not directly control the actual cylinder impact speed. The real speed of the cylinder is usually controlled by pneumatic flow control valves, throttle valves, or exhaust restrictors.

Once this structure is understood, troubleshooting becomes much more logical. A nozzle problem is not always a nozzle defect. A fast movement problem is not always a panel setting problem. A wheel problem is not always a motor problem. The entire machine must be checked as a coordinated system.

Close-up of a HUAGUI-style rhinestone setting machine control panel showing Auto display, manual buttons, marking, wheel and vacuum knobs, ultrasonic switch, power switch, and pneumatic components.

2. Typical Symptoms

In field service, users often describe the problem in simple words:

“Nozzle not working.”

“Stuck with wheel.”

“Stone not working.”

“I changed the needle and plate with the same size, but the machine still does not work.”

“I made it very slow, but the machine is still very quick.”

“The wheel is not rotating easily, but before it was the same and the machine worked.”

“Everything is good now, but the air pressure is so strong that the stone cuts the fabric.”

These descriptions should not be treated as separate unrelated issues. They often represent different stages of the same troubleshooting process. At first, the machine may fail to pick stones. Then the technician finds that the nozzle and plate are misaligned. After that, the machine starts moving, but the cylinder speed is too fast. Finally, once the machine can place stones, the pressure may be too strong and damage the fabric.

The troubleshooting focus must change as the symptoms change.

Technician repairing a blue rhinestone hotfix setting machine in a workshop, adjusting the nozzle and linkage mechanism with tools beside the dual feeding plates and control panel.

3. When the Nozzle Does Not Pick Stones, Do Not Suspect the Main Board First

If the machine powers on, the display shows Auto or Manual, the buttons respond, and the cylinder can move up and down, the main board should not be the first suspect.

A completely failed main board usually causes more severe symptoms: no display, no output, no response from buttons, abnormal logic, or total failure to move. If the machine can move but cannot pick stones, the more likely causes are mechanical position, vacuum suction, nozzle blockage, feeding plate condition, or pneumatic adjustment.

When a user says “nozzle not working,” the first question should be: what exactly does “not working” mean?

If the nozzle does not move up or down, check air pressure, solenoid valve, cylinder, tubing, and control output.

If the nozzle moves but cannot pick up stones, check vacuum suction, nozzle blockage, nozzle alignment, and stone feeding.

If the nozzle moves down and hits the plate or wheel, check nozzle height, cylinder rod length, mechanical limit, and plate position.

If the nozzle can pick and place stones but damages fabric, check air pressure, downward speed, press depth, MARKING setting, ultrasonic time, and bottom support pad.

This classification prevents random part replacement.

4. How to Inspect the Nozzle or Needle

The nozzle is one of the most commonly misdiagnosed parts. It may truly be damaged, but in many cases it is only blocked, bent, installed incorrectly, or adjusted to the wrong height.

First, inspect whether the nozzle tip is bent. The nozzle is usually very thin. If it has hit the feeding plate, transparent cover, or accumulated stones, it may be slightly bent. Even a small bend can move the pickup point away from the correct center.

Second, check whether the tiny hole in the nozzle is blocked. Rhinestone dust, glue powder, fabric fibers, broken stone fragments, or oil contamination can block the hole. Remove the nozzle, clean it carefully with a fine needle, and blow compressed air backward through it. Do not use an oversized needle, because enlarging the hole may reduce stable suction performance.

Third, check whether the nozzle is vertical. The nozzle holder, lock nut, and fixing screw must be secure. The black tube or cable must not pull the nozzle sideways. If the nozzle is installed at an angle, even a new nozzle will fail to pick stones correctly.

Fourth, check the lowest position of the nozzle. When the nozzle moves down to its lowest position, it must not touch the blue plate, transparent cover, wheel edge, or feeding groove. It should only approach the rhinestone and pick it up. If the nozzle touches the plate even when there are no stones inside, the height is too low.

Fifth, check whether the nozzle is centered over the pickup point. The feeding wheel delivers the rhinestone to a fixed position. The nozzle must be exactly above this position. For small stones such as SS6 or SS8, even a one-millimeter error is enough to cause pickup failure.

Therefore, replacing the needle does not automatically solve the problem. After replacing the needle or nozzle, the technician must readjust height, verticality, and pickup alignment.

5. Vacuum Suction Must Be Tested Correctly

Many users test vacuum incorrectly. They place a piece of paper under the nozzle and let the machine press down on it. This only proves that the cylinder moves. It does not prove vacuum suction.

The correct test is simple:

Set the machine to manual mode. Keep the nozzle in a safe position. Activate vacuum. Hold a very small, light piece of paper near the nozzle tip. Do not place the paper under the nozzle for pressing. The paper should be pulled toward the nozzle and held firmly by suction.

If the paper is firmly sucked, vacuum exists. If the nozzle still cannot pick stones, the problem is more likely alignment, stone feeding, stone orientation, or plate condition.

If the paper only moves slightly, vacuum is weak. Check air pressure, vacuum knob, pneumatic vacuum generator, tube leakage, nozzle blockage, and fittings.

If the paper does not move at all, vacuum is not working. In that case, adjusting the feeding plate or replacing stones will not help.

Common vacuum system problems include a closed or low VACUUM knob, insufficient air pressure, blocked vacuum generator, leaking transparent tube, loose fittings, solenoid valve failure, clogged nozzle, or air leakage between the nozzle and tube.

For remote troubleshooting, always ask the user to send a close video of the paper being sucked by the nozzle tip. Without that evidence, vacuum cannot be confirmed.

6. Feeding Plate and Wheel Problems Must Not Be Ignored

Many users underestimate the feeding wheel. They may say, “The wheel is not rotating easily, but before it was the same and the machine worked.” That is not a reliable conclusion.

The wheel does not only need to rotate. It must rotate smoothly and consistently enough to guide stones to the pickup point. If it has hard spots, broken stones, dust, excessive pressure from the transparent cover, an overtightened center screw, or incorrect plate installation, feeding will become unstable.

Too many stones inside the plate can also cause trouble. Operators often believe that adding more stones will improve feeding. In reality, small rhinestone plates cannot work well when stones are piled up at the outlet. Too many stones can cause jamming, flipping, blockage, and collision with the nozzle.

A proper test should be done with only 20 to 30 stones. First, remove all stones. Clean broken stones, dust, glue particles, and debris from the plate. Then add only a small quantity and observe whether the stones reach the pickup point smoothly.

The plate size must also match the stones. If the plate is marked SS6-SS8, it is intended for stones in that range. The nozzle, plate, and rhinestone size must match each other. Mixed sizes, broken stones, or deformed stones will cause pickup instability.

When checking the wheel manually, turn off the machine and gently rotate the wheel by hand. Some resistance is acceptable, but it must not have hard jamming points. The transparent cover must not press against the blue plate. The center screw must not be too tight. There must be no broken stones or dirt under the plate.

7. Why the Nozzle Gets Stuck with the Wheel

“Stuck with wheel” is an important symptom. It usually indicates mechanical interference between the nozzle and the feeding plate.

Common causes include:

The nozzle is installed too low. After replacing the needle, if it is inserted too deeply into the holder, the lowest position becomes too low and the nozzle hits the plate.

The cylinder rod length has changed. If the cylinder, rod end, or linkage has been replaced, even a difference of 1 to 2 mm can make the nozzle hit the plate.

The plate is not installed in the correct position. If the plate is not seated on the positioning pin or groove, or if the transparent cover is shifted, the pickup point may move away from the nozzle center.

The nozzle is bent. A bent nozzle may scrape the plate edge or transparent cover.

Too many stones are accumulated at the outlet. Instead of picking one stone, the nozzle presses into a pile of stones and gets stuck.

The correct test is to remove all stones, set the machine to manual mode, and slowly press DOWN. Observe whether the nozzle touches the plate or transparent cover at the lowest point. Only after confirming no interference should stones be added for further testing.

This step is very important. If the operator keeps running Auto mode while the nozzle is hitting the plate, a new nozzle can quickly bend, the plate can be scratched, and the problem becomes worse.

8. Why the Machine Is Still Too Fast Even After Slowing the Panel Setting

A common complaint is: “I made it very slow, but the machine is still very quick.”

This happens because panel settings and actual cylinder speed are not the same thing. The panel may control work cycle, delay time, feeding rhythm, counter timing, marking duration, or ultrasonic time. But the impact speed of the cylinder is usually controlled by pneumatic air flow.

Cylinder speed depends on air pressure, inlet and exhaust flow, flow control valves, solenoid valve exhaust, and cylinder cushioning. If the flow control valve is fully open and air pressure is high, the cylinder will move down sharply like a punch press. In that case, reducing the panel speed only increases the interval between strokes. Each stroke is still too fast.

To control cylinder speed, look for these parts:

Small pneumatic speed controllers on the cylinder ports.

Flow control valves installed in the air tube.

Throttle silencers on the solenoid valve exhaust ports.

Air fittings with small knobs or slotted adjustment screws.

Adjustment must be done slowly. Turn only one quarter of a turn each time, then test in manual mode. The goal is to make the DOWN movement slow and soft. The return stroke can be slightly faster, but the pressing stroke must not hit the fabric violently.

If adjustment has no effect, the technician may be adjusting the wrong valve, the valve may be damaged, the valve may be installed in the wrong direction, or the air circuit may bypass the speed controller.

9. Excessive Air Pressure and Fabric Cutting

Once the machine can pick and place stones, a new problem may appear: the stone cuts or damages the fabric. Users may describe it as “air pressure is so strong, fabric cut by stone.”

This means the machine has moved from mechanical repair to process adjustment.

Fabric damage is usually caused by several factors together:

Main air pressure is too high.

Cylinder down speed is too fast.

Nozzle or press head lowest position is too low.

MARKING or ultrasonic time is too high.

Fabric is too thin, soft, or elastic.

There is no soft pad under the fabric.

The rhinestone is upside down, damaged, or not a flat-back stone.

Broken stones or incorrect sizes are mixed in the plate.

For thin fabric, elastic fabric, mesh, or shiny delicate fabric, high pressure must not be used. A safe starting range for thin fabric is about 0.20 to 0.30 MPa. For thicker fabric, the test range may be around 0.35 to 0.45 MPa, but pressure should only be increased gradually.

It is important to understand that the pneumatic speed controller adjusts speed, not final pressing force. To reduce pressing force, adjust the main air regulator. The flow control valve can reduce impact, but if the main pressure is too high, the final pressing force may still be excessive.

If fabric is damaged, do four things:

Reduce main air pressure.

Slow down the cylinder’s downward movement.

Raise the nozzle or press head lowest position slightly.

Reduce MARKING or ultrasonic energy/time.

Always test on waste fabric first. Do not test on good production fabric until the parameters are stable.

The correct result is simple: the stone is fixed firmly on the fabric, but the fabric is not cut, broken, whitened, or strongly marked on the back side.

10. Adjusting the Lowest Position of the Press Head

The lowest position of the nozzle or press head is a critical adjustment. Even if air pressure is not very high, if the mechanical stroke is too deep, the stone will be forced into the fabric.

The technician should check the cylinder rod, linkage length, nozzle holder, mechanical limit screw, and rocker position. Different machines have different structures, but the principle is the same: the head should go low enough to press the stone, but not so low that it crushes the fabric.

Adjust in small steps, usually 0.5 to 1 mm at a time. Do not make a large adjustment at once.

After each adjustment, check three results:

Is the stone fixed firmly?

Is the fabric surface damaged, whitened, or cut?

Is the back side of the fabric bulged, torn, or pierced?

If the stone is firm and the fabric is not damaged, the setting is correct. If the stone is not firm but the fabric is safe, slightly increase MARKING or bonding time. Do not immediately increase air pressure.

11. MARKING and Ultrasonic Energy

Many ultrasonic rhinestone machines have an ULTRASONIC SWITCH and a MARKING knob. Depending on the machine design, MARKING may control ultrasonic time, energy, marking strength, or pressing duration.

If MARKING is too high, the fabric may show:

White marks.

Fiber damage.

Heavy indentation around the stone.

Punctures in thin fabric.

Overheated glue.

Hardening or deformation around the stone.

If MARKING is too low, the stone may not be fixed firmly and may fall off easily.

The best method is to start with a low MARKING setting and increase gradually only until the stone is fixed. Do not combine high air pressure, high down speed, and high MARKING. That combination is very likely to damage fabric.

12. The Fabric Needs Proper Bottom Support

Bottom support is often ignored. If thin fabric is placed directly on a hard metal table or hard board, the stone may act like a small cutting point. Under high pneumatic force and fast impact, the local pressure becomes very high and the fabric can be pierced.

A soft rubber pad, silicone pad, or suitable heat-resistant cushion should be placed under the fabric. The pad absorbs impact and allows the glue surface to bond more evenly.

The pad must not be too soft, or positioning may become inaccurate. It must not be too hard, or it will not protect the fabric. The correct pad depends on fabric thickness, elasticity, rhinestone size, and bonding method.

13. Do Not Replace the Rocker Linkage Too Early

Some users point to the mechanical rocker arm, linkage, or joint and ask whether it should be replaced. This part should be inspected, but it should not be the first replacement target.

Check the linkage for:

Severe wear in the pivot holes.

Loose pins.

Bent connecting rods.

Sticking during movement.

Loose screws.

Worn bushings or bearings.

Lack of lubrication.

Heavy dust or dirt.

If the only problem is that the cylinder moves too fast, replacing the linkage usually will not solve it. Fast movement is mainly controlled by air pressure and flow control valves.

However, if the linkage is very tight when moved by hand after air is disconnected, or if it has serious looseness, it should be cleaned, lubricated, repaired, or replaced. If the linkage has excessive play, the nozzle position may change every cycle, causing unstable pickup.

14. Correct Remote Troubleshooting Procedure

For users in areas without local technicians, remote troubleshooting must be structured. Otherwise, the technician may receive many videos but still cannot identify the key problem.

A good remote troubleshooting sequence is:

First, take an overview video of the machine, including the panel, air pressure gauge, feeding plate, nozzle, and machine model.

Second, switch to manual mode, remove all stones, and film the nozzle moving down slowly to its lowest point. Confirm whether it hits the plate.

Third, film a proper vacuum test using a light paper at the nozzle tip.

Fourth, film the feeding wheel rotating by hand with power off. Confirm whether it has hard jamming points.

Fifth, add only 20 to 30 stones and film the pickup point closely.

Sixth, film the nozzle picking up one stone from the plate.

Seventh, test on waste fabric and observe bonding strength, indentation, and fabric damage.

Eighth, adjust air pressure, flow control valves, nozzle height, MARKING, and bottom pad according to the result.

The key principle is single-system verification. Do not test everything at once. Do not run Auto mode while also changing panel parameters, adding many stones, and testing real fabric. If too many variables change together, the real cause cannot be identified.

15. Practical Troubleshooting Order

For combined symptoms such as nozzle failure, wheel jamming, stone pickup failure, fast movement, and fabric damage, the following order is recommended:

Confirm that the machine powers on and the panel can switch between Auto and Manual.

Stop Auto mode. Use Manual mode for all tests.

Inspect the nozzle for bending, blockage, looseness, and incorrect installation.

Remove all stones and check whether the nozzle hits the plate at its lowest point.

Perform a proper vacuum suction test with a light paper.

Clean the wheel and plate. Remove broken stones, dust, glue particles, and foreign objects.

Add only a small number of stones and check whether feeding is stable.

Align the nozzle with the stone pickup point.

Reduce main air pressure to a safe test level.

Adjust the pneumatic flow control valve to make the DOWN movement smooth.

Confirm that the nozzle can pick up one stone.

Test pressing on waste fabric.

If the fabric is damaged, reduce pressure, slow the down stroke, raise the lowest position, reduce MARKING, and use a soft support pad.

After all single tests are stable, run Auto mode for continuous testing.

This sequence avoids unnecessary part replacement and separates the fault into mechanical interference, vacuum failure, feeding instability, pneumatic impact, or process pressure problems.

16. Final Diagnostic Logic

Troubleshooting rhinestone setting machines should not be reduced to the question “Which part is broken?” In many cases, no major component is damaged. Instead, several small adjustments are wrong at the same time.

The nozzle may be new, but its height is wrong.

The plate may be the correct SS6-SS8 type, but the pickup point is not aligned.

The wheel may rotate, but it has hard spots.

The vacuum may seem present, but it has not been tested correctly.

The panel speed may be low, but the cylinder speed is not throttled.

The machine may finally place stones, but the air pressure and stroke are too strong, causing fabric damage.

Therefore, when the machine can move manually, feed stones, and pick stones, do not keep chasing main board faults or large replacement parts. When the fabric is cut by the stone, do not go back to blaming the needle or plate. At that point, the machine has entered process adjustment. The key settings are air pressure, down speed, press depth, MARKING, ultrasonic time, and bottom support.

For remote service, the most useful videos are not general machine videos. The most useful videos show the nozzle lowest point, vacuum suction, stone pickup point, wheel rotation, and fabric test result.

17. Conclusion

A rhinestone setting machine works through the coordination of nozzle, wheel, vacuum, cylinder, and pressing or ultrasonic bonding systems. A small error in any one part can make the whole machine appear “not working.” A one-millimeter nozzle offset can prevent stone pickup. Excessive air pressure can cut fabric. A slightly jammed wheel can cause unstable feeding. A fully open flow valve can make the cylinder hit like a punch press. Too much MARKING can damage delicate fabric.

The correct repair principle is:

Check mechanical position before electronics.

Use manual mode before Auto mode.

Test without stones before testing with stones.

Test with a few stones before filling the plate.

Confirm vacuum before adjusting feeding.

Confirm pickup before testing fabric.

Use waste fabric before production fabric.

For problems such as nozzle not working, wheel jamming, stone pickup failure, excessive speed, and fabric damage, the most effective solution is usually systematic adjustment rather than random part replacement. Clean the plate, align the nozzle, confirm vacuum suction, reduce air pressure, slow the cylinder, raise the press head slightly, reduce MARKING, and use a suitable soft pad under the fabric.

By following this logic step by step, most similar machines can be restored to stable operation without unnecessary replacement of the main board, linkage assembly, or other expensive parts.

Posted on

ACS580 Drive RS485 (Modbus RTU) Communication Testing and Parameter Adjustment Using a Serial Assistant Tool

During industrial maintenance, second-hand drive inspection, PLC communication debugging, HMI integration, and remote technical support, engineers often need to verify whether the embedded fieldbus interface of an ABB ACS580 drive is functioning correctly. The ACS580 includes an internal EFB (Embedded Fieldbus) interface that can operate as a Modbus RTU slave. With a USB-to-RS485 converter, a computer, and a serial communication tool, it is possible to perform complete communication testing, including register reading, control word writing, frequency reference adjustment, remote start/stop control, and fault reset.

This method is extremely practical because it does not require a PLC, HMI, or ABB commissioning software. As long as the RS485 physical layer and the drive parameters are configured correctly, engineers can directly determine whether the communication port, Modbus settings, control logic, and remote control chain are operating properly.

This article explains the complete process of ACS580 Modbus RTU communication testing using a USB-RS485 converter and a serial assistant tool. It covers wiring, parameter configuration, serial software settings, Modbus frames, control word logic, startup and stop procedures, common faults such as 6681 EFB communication loss and AFE1/off2 emergency stop, as well as communication instability caused by electromagnetic interference during drive operation.


Schematic diagram of ACS580 frequency converter EFB interface and USB-RS485 wiring

1. ACS580 EFB Interface and RS485 Wiring

The ACS580 control board includes a three-pin EFB terminal used for embedded fieldbus communication. This interface can be used directly for Modbus RTU testing.

Typical terminal definitions are:

ACS580 TerminalFunction
29B+
30A-
31DGND

The wiring between the ACS580 and the USB-RS485 converter is typically:

ACS580 X5/EFBUSB-RS485 Converter
29 B+RS485 A/B
30 A-RS485 opposite line
31 DGNDGND

One important point is that many USB-RS485 converters use inconsistent A/B or D+/D- labeling. Cheap converters especially may reverse the line naming compared to the drive definition. Therefore, if the parameters and serial settings appear correct but no communication occurs, the first troubleshooting step should be swapping the A and B communication wires.

For single-drive bench testing, it is recommended to enable both TERM and BIAS on the ACS580 communication interface. This improves communication stability in short-distance point-to-point testing.

For long-term industrial use, twisted-pair shielded cable should be used for the A/B communication pair. The shield should typically be grounded at one end only to avoid ground loop current.


ACS580 Modbus RTU Testing Tool

2. ACS580 Parameters Required for Modbus RTU Communication

To allow Modbus RTU control, the embedded fieldbus interface must first be enabled and configured correctly.

Recommended communication parameters:

ParameterRecommended ValueDescription
58.01 Protocol EnableModbus RTUEnable embedded fieldbus
58.03 Node Address1Modbus slave address
58.04 Baud Rate9.6 kbpsMatches serial tool setting
58.05 Parity8 Even 1Matches serial tool
58.06 Communication ControlRefresh SettingsApply communication changes
58.25 Control ProfileABB DriveEnables ABB control word format

After modifying the 58-group parameters, 58.06 “Refresh Settings” must be executed, or the drive must be power-cycled. Many communication failures occur simply because the communication settings were not refreshed.

The command source and frequency reference source must also be assigned to EFB:

ParameterRecommended ValueDescription
19.11 EXT1/EXT2 SelectionEXT1Use external control set 1
20.01 EXT1 CommandsEmbedded Fieldbus / EFBStart/stop via Modbus
28.11 EXT1 Frequency Reference 1EFB Reference 1Frequency reference from Modbus
19.01 Operating ModeScalar Hz / Speed ModeCommon for testing

If 20.01 is not assigned to EFB, the drive may acknowledge Modbus commands without actually starting. If 28.11 is not assigned to EFB Reference 1, writing frequency values may not affect the drive output.

During testing, it is also recommended to temporarily disable communication-loss trips:

ParameterRecommended Temporary Value
58.14 Communication Loss ActionNo Action
58.15 Communication Loss ModeAny Message
58.16 Communication Loss Time30 seconds or longer

This prevents fault 6681 from occurring while manually testing communication using a serial tool.


AFE1 ALARM

3. Serial Assistant Software Configuration

The USB-RS485 converter driver must first be installed so that Windows recognizes the device as a COM port.

Typical serial settings:

SettingValue
COM PortCOM3 / COM4 / etc.
Baud Rate9600
Data Bits8
ParityEven
Stop Bits1
Flow ControlNone
Send FormatHEX
Receive FormatHEX

If ACS580 parameter 58.05 is set to “8 Even 1,” the serial assistant must also use Even parity. A parity mismatch will prevent proper communication.

Another critical point involves CRC handling. Some serial tools automatically append Modbus CRC bytes. If CRC auto-generation is enabled, the user should only enter the Modbus frame without CRC. If the complete frame including CRC is entered manually while auto-CRC is still enabled, the resulting frame becomes invalid.

Example read command:

01 03 00 00 00 06 C5 C8

If CRC auto-generation is disabled, the complete frame above should be transmitted exactly as shown.


6681 Fault

4. Read Registers Before Attempting Startup

The first communication test should always be a register read operation rather than an immediate start command.

Command for reading registers 400001–400006:

01 03 00 00 00 06 C5 C8

Frame meaning:

BytesDescription
01Slave address
03Read holding registers
00 00Starting register
00 06Read 6 registers
C5 C8CRC

A typical response:

01 03 0C 00 00 00 00 00 00 00 00 11 33 00 00 95 E4

If the drive responds, the physical layer, slave address, baud rate, parity, and CRC are likely correct.

ACS580 communication diagnostics can also be monitored:

ParameterDescription
58.08 Received PacketsValid incoming frames
58.09 Sent PacketsValid outgoing frames
58.11 UART ErrorsSerial framing/parity errors
58.12 CRC ErrorsInvalid CRC or communication noise

5. Writing Frequency References

Under the ABB Drive profile, the frequency scaling is typically:

50Hz = 20000

Frequency calculation:

Reference Value = Target Frequency / 50 × 20000

Example for 10Hz:

10 / 50 × 20000 = 4000

4000 decimal equals 0FA0 hexadecimal.

Command to write 10Hz into register 400002:

01 06 00 01 0F A0 DD 82

The drive should echo the same frame back if the command is accepted.

Common frequency conversions:

FrequencyDecimalHEX
5Hz200007D0
10Hz40000FA0
20Hz80001F40
30Hz120002EE0
50Hz200004E20

6. Control Word Logic: Reset, Run, and Stop

The ACS580 control word is the key element for remote control via Modbus.

Common control words:

Control WordFunction
04F7Fault Reset
047FRun
047EStop

Fault reset command:

01 06 00 00 04 F7 CA 8C

Run command:

01 06 00 00 04 7F CA EA

Stop command:

01 06 00 00 04 7E 0B 2A

For stable operation, it is better to periodically write both control word and frequency reference together using Modbus function code 10.

10Hz run command:

01 10 00 00 00 02 04 04 7F 0F A0 C6 CF

Stop and zero-frequency command:

01 10 00 00 00 02 04 04 7E 00 00 92 87

In practical testing, a periodic transmission interval of 200–500ms proved much more stable than one-shot commands. With a 1-second interval, the panel sometimes displayed the frequency reference without actual output. At 500ms intervals, the drive produced stable output frequency and cooling fan operation.


7. Understanding Fault 6681: EFB Communication Loss

Fault 6681 indicates that the drive detected a communication loss on the embedded fieldbus.

Typical causes:

  1. The drive command source is assigned to EFB, but the PC is not continuously transmitting Modbus frames.
  2. Communication-loss action remains enabled during manual testing.
  3. Parameters were copied from another drive, but no real-time control word is being transmitted after power-up.

During manual testing, it is recommended to disable communication-loss trips temporarily. However, in actual industrial applications, communication supervision should remain active and PLCs should continuously refresh control words and references.


8. Understanding AFE1 / OFF2 Emergency Stop

Another common issue is the AFE1 warning showing “Emergency Stop OFF2.”

This is not always caused by hardware emergency stop wiring. It can also occur when the fieldbus control word is incomplete or invalid.

Example:

06.01 = 408 hex

In this state, Off1/Off2/Off3 bits may not be properly enabled.

Under ABB Drive control word logic:

  • OFF2 bit = 1 → OFF2 inactive, operation allowed
  • OFF2 bit = 0 → Emergency stop active

Therefore, after power-up or communication interruption, the drive may interpret the control word as an OFF2 command.

The practical solution is:

  1. Send fault reset 04F7
  2. Begin periodic transmission of 047F + frequency reference

Once the control word stabilizes at 047F, the OFF2 warning disappears.


9. Local Mode vs Remote Mode

For Modbus control, the drive must operate in Remote mode.

In Local mode, panel commands have priority, and Modbus commands may appear to work without actually controlling the drive.

Therefore:

ModeDescription
LocalPanel control priority
RemoteExternal control active
Remote + EFBModbus control active

A successful Modbus test must ultimately operate in Remote mode.


10. Parameter Copying Between Drives

Copying parameters from one ACS580 to another does not copy the current control word state.

The copied drive still requires:

  1. Power cycle
  2. Fault reset
  3. Continuous control-word transmission

Copied parameters include communication settings and command-source assignments, but not the live Modbus control state.


11. USB-RS485 Communication Instability During Drive Output

If the COM port disappears from Windows Device Manager while the drive is running, the issue is usually electromagnetic interference rather than software alone.

Variable-frequency drives generate strong PWM-related common-mode noise on motor cables.

Cheap CH340-based USB-RS485 adapters are especially vulnerable.

Recommended solutions:

  1. Use isolated industrial USB-RS485 converters.
  2. Keep USB and RS485 cables away from motor output cables.
  3. Use twisted-pair shielded communication cable.
  4. Install ferrite cores on USB cables.
  5. Use rear motherboard USB ports instead of front-panel ports.
  6. Enable TERM and BIAS for single-drive testing.

12. Recommended Complete Testing Procedure

Step 1: Configure Drive Parameters

Set all required EFB and Modbus parameters.

Step 2: Read Registers

Send:

01 03 00 00 00 06 C5 C8

Step 3: Reset Faults

Send:

01 06 00 00 04 F7 CA 8C

Step 4: Start Drive at 10Hz

Transmit periodically:

01 10 00 00 00 02 04 04 7F 0F A0 C6 CF

Step 5: Stop Drive

Send:

01 10 00 00 00 02 04 04 7E 00 00 92 87

13. Conclusion

Testing an ACS580 using a USB-RS485 converter and a serial assistant tool is an extremely effective method for verifying embedded Modbus RTU communication without requiring PLCs or engineering software.

A successful communication test requires more than simply receiving Modbus responses. Proper EFB command assignment, valid ABB control words, periodic transmission timing, remote mode selection, and stable hardware wiring are all critical.

The most common troubleshooting issues include reversed A/B wiring, missing communication refresh, incorrect parity, duplicated CRC generation, communication-loss supervision, OFF2 emergency stop logic, and electromagnetic interference affecting USB-RS485 adapters.

Once the Modbus control sequence is understood, ACS580 communication testing becomes a reliable and repeatable process for maintenance, refurbishment, commissioning, and customer technical support.

Posted on

Diagnosing and Calibrating AO2 Analog Current Output Deviation on the JT330S2 Inverter: Complete Analysis from Parameter F6-08 to PLC Engineering Value Scaling

In industrial automation systems, analog outputs from inverters are widely used to transmit operating frequency, output current, output voltage, torque, power, and other real-time operating data to PLCs, HMIs, recorders, or supervisory systems. Although this appears to be a simple analog wiring task, field commissioning often reveals problems such as:

“The parameter has already been set correctly, but the PLC display is still inaccurate.”

A typical example involves a JT330S2 inverter configured to output a 0–20mA analog signal through terminal AO2 so that a Siemens S7-200 SMART PLC can monitor the motor’s actual running current. According to the inverter manual, the technician sets parameter:

F6-08 = 2

which selects “Output Current” as the AO2 output function.

However, during operation, the inverter display or clamp meter shows an actual motor current of approximately 20A, while the PLC displays only 10A — exactly half of the real value.

This type of issue should not immediately be interpreted as:

“The inverter is faulty”
or
“The parameter was set incorrectly.”

From a troubleshooting perspective, the problem is usually related to scaling mismatch between:

1. What signal the inverter actually outputs
2. What signal the PLC actually receives
3. How the PLC program converts that signal into engineering units

To solve the problem correctly, all three stages must be analyzed independently.


JT330S2 inverter AO2 analog current output measurement wiring diagram showing a digital multimeter connected in series between the inverter AO2 terminal and Siemens PLC analog input AI+, with GND connected to PLC M/COM, demonstrating correct 0–20mA current signal testing and AO2 current-output jumper setting.

1. Basic Function of AO2 Analog Output

The JT330S2 inverter provides two analog outputs:

AO1
AO2

These outputs can be configured to represent different operating parameters, including:

Running frequency
Set frequency
Output current
Output torque
Output power
Output voltage
Input analog values
Motor speed
Communication settings

In this application, the user wants the PLC to monitor the motor output current, therefore AO2 should be configured as:

F6-08 = 2

meaning:

AO2 output function = Output Current

This setting direction is correct. However, F6-08 only determines:

“What AO2 outputs”

It does NOT automatically guarantee:

“20A motor current = 20mA analog output”

Analog output accuracy also depends on:

Output mode
Zero offset
Gain
Full-scale mapping
PLC input scaling
Engineering unit conversion

Therefore, F6-08 is only the first step. The technician must still verify:

Whether AO2 is configured as current or voltage output
Whether AO2 outputs 0–20mA or 4–20mA
How the PLC analog module is configured
How the PLC program converts the raw analog value

2. Why the PLC Displays Only Half the Actual Current

The key field symptom is:

Actual motor current: 20A
PLC displayed current: 10A

An error that is exactly “half” is usually not random. It almost always indicates a scaling mismatch.

Suppose the inverter internally defines:

20mA = 40A

Then when the motor current is 20A, AO2 only needs to output half-scale current:

Approximately 10mA

Now suppose the PLC program assumes:

20mA = 20A

Then the PLC interprets 10mA as:

10A

This creates the observed condition:

Actual 20A
→ AO2 outputs approximately 10mA
→ PLC interprets 10mA as 10A

Therefore, the issue is most likely NOT that AO2 is malfunctioning. Instead, the scaling relationship between the inverter analog output and the PLC engineering conversion is inconsistent.


JTE386S2 BA0185G3

3. Measure the Actual AO2 Output Current First

One of the biggest mistakes in field troubleshooting is immediately changing parameters without measurement.

The correct approach is to first measure the real AO2 output current using a multimeter.

Unlike voltage measurement, current measurement must be performed in series.

The correct wiring method is:

Inverter AO2 → Multimeter mA Input
Multimeter COM → PLC Analog Input AI+
Inverter GND → PLC Analog M/COM

In practical terms:

Disconnect the wire between AO2 and PLC AI+
Insert the multimeter in series

The multimeter must be set to:

DC mA measurement mode

The red probe must be inserted into the:

mA terminal

and the black probe into:

COM

If the meter is accidentally placed in voltage mode, AC current mode, or connected in parallel, the reading will be incorrect and the meter fuse may even blow.


4. Using Measured Values to Determine the Root Cause

During testing, record three values simultaneously:

1. Inverter displayed output current
2. Multimeter measured AO2 current signal
3. PLC displayed current

Measurements should be taken at multiple load points:

Low load (e.g. 5A)
Medium load (e.g. 10A)
High load (e.g. 20A)

Case 1: Actual 20A → AO2 ≈ 10mA → PLC Displays 10A

This means the PLC display follows the analog signal correctly, but the engineering scaling range is too small.

The PLC likely assumes:

20mA = 20A

while the inverter output behaves like:

20mA = 40A

Typical PLC conversion formula:

Current = Raw_AI × 20 / 27648

should instead become:

Current = Raw_AI × 40 / 27648

This adjustment causes:

10mA → 20A

which restores correct display.


Case 2: Actual 20A → AO2 ≈ 20mA → PLC Displays 10A

In this case, the inverter analog output is already correct.

The fault is entirely on the PLC side.

Possible causes include:

Incorrect analog module range
Incorrect PLC scaling formula
Incorrect HMI engineering scaling
Additional divide-by-two logic in the program
Incorrect analog module configuration

If the PLC raw analog value already reaches near full scale but the displayed engineering value is still half, the inverter is NOT the problem.


Case 3: Actual 20A → AO2 Has Almost No Current Output

This suggests a hardware or wiring issue.

The technician should verify:

AO2 jumper/switch position
AO2 wiring
PLC analog input type
GND common reference
F6-08 parameter
F6-12 offset
F6-13 gain

On the JT330S2 control board, AO1 and AO2 can be configured as either:

Voltage output (V)
Current output (I)

If AO2 is still configured for voltage output while the PLC expects current input, readings will be abnormal.


5. Recommended Inverter Parameter Settings

For transmitting actual motor current through AO2:


AO2 Hardware Mode

Set AO2 jumper/switch to:

I = Current Output

Do NOT leave it at:

V = Voltage Output

AO2 Function Selection

F6-08 = 2

meaning:

AO2 outputs motor current

AO2 Offset

F6-12 = 0.0%

Normally keep default.

Improper offset adjustment can create false low-current readings.


AO2 Gain

F6-13 = 1.00

Normally keep default initially.

If measurements confirm the AO2 signal is exactly half the desired value, gain can be increased:

F6-13 = 2.00

However, increasing gain also risks premature saturation.

Example:

Originally:

40A = 20mA

After doubling gain:

20A = 20mA

Then any current above 20A can no longer be represented properly.

Therefore, adjusting PLC scaling is usually preferable.


6. PLC Engineering Unit Scaling Is Often Overlooked

Siemens S7-200 SMART analog modules typically convert analog current into digital values.

A common full-scale raw value is:

27648

for:

0–20mA

Engineering conversion formula:

Engineering_Value = Raw_AI × FullScale / 27648

The key question is:

What actual current does 20mA represent?

The PLC does not know automatically.

The programmer must define it.

If the PLC program assumes:

20mA = 20A

then:

10mA = 10A

If the inverter behavior is actually:

20mA = 40A

then the PLC formula must be updated accordingly.


7. 0–20mA and 4–20mA Must Not Be Confused

Industrial analog current signals are commonly:

0–20mA
4–20mA

0–20mA:

0mA = zero signal
20mA = full scale

4–20mA:

4mA = zero signal
20mA = full scale

4–20mA allows wire-break detection because signal loss drops below 4mA.

The following three elements must always match:

Inverter output type
PLC analog input type
PLC scaling formula

If one side uses 0–20mA and the other assumes 4–20mA, scaling errors will occur.


8. Why Special Output Modes Should Not Be Used Randomly

Some JT330S2 firmware versions include special AO2 scaling options such as:

100% = 1000A

These modes are usually intended for:

Special scaling
Communication mapping
Large-current systems
Manufacturer calibration

They are generally unsuitable for standard motor current monitoring applications.

For normal PLC monitoring:

F6-08 = 2

is the preferred choice.

Scaling corrections should then be handled through:

F6-13 gain adjustment
or
PLC engineering scaling

9. Recommended Field Commissioning Procedure

A practical troubleshooting workflow:


Step 1 — Verify Wiring

AO2 → PLC AI+
GND → PLC M/COM

For testing:

AO2 → Multimeter mA input
Multimeter COM → PLC AI+
GND → PLC M/COM

Step 2 — Verify AO2 Hardware Mode

AO2 jumper = I

Step 3 — Verify Parameters

F6-08 = 2
F6-12 = 0.0%
F6-13 = 1.00

Step 4 — Record Operating Data

Measure:

Actual motor current
AO2 mA signal
PLC raw analog value
PLC displayed engineering value

Step 5 — Analyze Results

Correct AO2 but wrong PLC display
→ PLC scaling issue

AO2 signal too small
→ Gain or scaling mismatch

No AO2 signal
→ Wiring/jumper/input mode issue

Unstable signal
→ Grounding/shielding/noise problem

10. Wiring and Safety Considerations

Even though AO2 is a low-level control signal, inverter commissioning still involves dangerous power circuits.

Important precautions:

Never modify power wiring while energized
Do not short 24V, 10V, or GND terminals
Current measurement must be series-connected
Use correct meter terminals
Avoid shorting AO2 to GND
Ensure proper common grounding
Use shielded analog cables
Separate analog cables from motor cables

Many analog signal issues are actually caused by:

Improper shielding
Noise interference
Incorrect grounding
Mixed routing with motor cables
Floating analog commons

rather than parameter settings.


11. Explaining the Problem to Customers

A practical explanation for customers is:

“Setting F6-08=2 only tells the inverter to output motor current through AO2. The PLC display depends on how many milliamps AO2 actually outputs and how the PLC converts those milliamps into amps. If actual current is 20A but PLC shows 10A, the scaling ratio is incorrect. First measure the real AO2 output current with a multimeter. If 20A corresponds to 10mA, either adjust PLC scaling so that 20mA equals 40A, or increase AO2 gain. If 20A already corresponds to 20mA, then the issue is entirely inside the PLC program.”

This explanation helps avoid unnecessary inverter replacement.


12. Conclusion

When using the JT330S2 inverter AO2 analog output to transmit motor current to a Siemens PLC, parameter:

F6-08 = 2

is correct, but it is only the function selection step.

The common field symptom:

Actual 20A
PLC displays 10A

is usually caused by mismatch between:

AO2 output scaling
PLC analog input scaling
Engineering conversion formulas

The proper diagnostic method is to:

Measure the real AO2 mA signal first

using a multimeter connected in series.

Then determine whether the issue lies in:

PLC scaling
AO2 gain
Wiring
Output mode
Grounding

In most practical applications, correcting PLC engineering scaling is preferable to increasing AO2 gain, because it avoids premature analog output saturation and preserves full measurement range.

The key principle in troubleshooting analog output systems is understanding the complete signal chain:

Motor Current
→ Inverter Internal Calculation
→ AO2 Analog Output
→ PLC Analog Acquisition
→ PLC Engineering Conversion
→ HMI Display

By testing and verifying each stage independently, technicians can rapidly locate the true cause of scaling errors and avoid unnecessary hardware replacement or repeated blind parameter adjustments.

Posted on

Troubleshooting Er24.1 and Er16.0 on the Zhishan K5 Servo Drive: Reverse Rotation Failure, Excessive Speed Deviation, and Overload Protection

In CNC equipment, automatic feeding systems, packaging machines, printing machines, dispensing machines, winding machines, and many other automation mechanisms, AC servo systems are responsible for accurate positioning, speed control, and torque output. Once a servo drive reports an alarm, the machine usually stops immediately. Compared with a standard inverter, a servo drive has stricter monitoring logic because it does not only check current, voltage, and temperature; it also continuously compares command position, command speed, actual encoder position, and actual feedback speed.

For this reason, when a servo system fails, the technician should not only ask whether the motor can rotate. It is more important to analyze the relationship between command, feedback, load, wiring, parameters, and the mechanical transmission structure.

In field applications, the Zhishan K5 series AC servo drive may show the following symptom: the drive powers on normally, the servo can be enabled, forward rotation may work, but reverse rotation fails. Once a reverse command is given, the motor may not move, may move slightly and stop, or may immediately trigger Er24.1. In some cases, Er16.0 also appears.

This fault may look like a defective servo drive, but the real cause may be mechanical jamming, excessive load, abnormal encoder feedback, incorrect motor phase wiring, wrong direction logic, active reverse limit signal, brake not released, or improper parameter settings. To solve this problem correctly, the alarm meaning must be combined with the real machine behavior.

Zhishan K5 AC servo drive displaying Er24.1 speed deviation alarm inside an industrial control cabinet during on-site maintenance and troubleshooting.

1. The Meaning of Er24.1: Excessive Speed Deviation

For the K5 servo drive, Er24.1 generally means excessive speed deviation protection. Speed deviation is the difference between the speed commanded by the drive and the actual speed fed back by the motor encoder.

For example, the PLC or motion controller sends a reverse rotation command to the servo drive. The drive outputs three-phase current to make the motor rotate in reverse. However, the encoder feedback shows that the motor speed does not reach the expected value, or the motor almost does not move. In this case, the drive determines that the difference between command speed and actual speed is too large. To prevent overcurrent, overload, mechanical impact, or loss of control, the drive stops and reports Er24.1.

Therefore, Er24.1 does not necessarily mean that the drive is internally damaged. More accurately, it means:

The drive has issued a motion command, but the actual motor movement does not match the expected result.

Common causes include:

motor blocked by mechanical load;

reverse direction mechanically jammed;

mechanical hard limit reached;

motor brake not released;

load inertia too large;

acceleration or deceleration time too short;

motor U/V/W wiring wrong or loose;

encoder cable loose or abnormal;

motor and drive not matched;

reverse direction signal logic incorrect;

speed deviation detection threshold set too small;

servo gain not suitable for the machine.

If the actual symptom is “forward rotation works, but reverse rotation fails,” the key point is not only speed deviation. The real question is:

Why does the motor fail to follow the command only in reverse direction?

2. The Meaning of Er16.0: Overload Protection

Er16.0 is usually related to overload protection. Overload does not always mean an instant short circuit, and it does not always mean that the drive power module is damaged. In servo systems, overload usually means that the motor current has exceeded the allowed range for a certain period of time. The drive judges that the motor or drive is carrying excessive load.

If the machine is mechanically jammed in reverse direction, the drive will increase output current in an attempt to make the motor rotate. But because of mechanical resistance, brake locking, wiring error, or abnormal feedback, the motor cannot reach the target speed. This may first trigger Er24.1. If the high current continues, Er16.0 may also appear.

In other words, Er24.1 and Er16.0 are often connected:

A reverse command is given.

The motor cannot rotate correctly because of mechanical load, limit signal, brake, wiring, or feedback problem.

The drive increases output current.

The encoder feedback speed cannot follow the command.

The drive reports Er24.1.

If high current continues, the drive reports Er16.0.

Therefore, when Er24.1 appears together with Er16.0, do not treat them as two unrelated faults. The correct diagnostic logic is:

Find out why the motor cannot follow the command first, then determine whether overload is the cause or the result.

Zhishan K5 AC servo drive showing Er16.0 overload alarm while a technician performs electrical diagnostics inside an industrial automation control panel.

3. When Reverse Rotation Fails, Mechanical Problems Are Highly Suspect

In real repair work, if a servo system can rotate forward but cannot rotate backward, the mechanical side must be checked first. Many technicians immediately suspect the servo drive and replace it. However, after replacing the drive, the same alarm may still appear because the root cause is not in the drive.

Common mechanical causes include the following.

The first is one-direction mechanical jamming. Lead screws, guide rails, belts, chains, gearboxes, feeding wheels, and clamping mechanisms may move smoothly in one direction but become tight in the opposite direction. Lack of lubrication, damaged bearings, worn lead screw nuts, misaligned belts, damaged gearbox teeth, or foreign objects may all cause reverse movement failure.

The second is a mechanical hard limit. If the mechanism has reached the end position, and the limit switch or software limit does not stop the axis correctly, the servo may command movement against a dead stop. The motor receives torque command but cannot move. Current rises quickly, actual speed remains very low, and the drive reports an alarm.

The third is brake failure. If the servo motor has an electromagnetic brake, the brake must be released before motion. If the brake power supply is missing, the brake relay contact is damaged, the brake coil is faulty, or the brake mechanism is stuck, the motor may hum, vibrate, or fail to rotate. Sometimes the brake is not completely locked but only partially released. This is more difficult to detect because the motor may rotate at no load but fail under load.

The fourth is asymmetric load. Many machines do not have the same load in forward and reverse directions. Lifting mechanisms, feeding systems, pressing rollers, and clamping systems may have very different resistance depending on direction. If reverse direction happens to be the heavy-load direction, Er24.1 and Er16.0 may appear more easily.

For this reason, when a K5 servo drive reports Er24.1 or Er16.0 and the machine cannot reverse, do not start by changing parameters. First confirm whether the machine is mechanically able to move in reverse.

4. The Most Effective First Test: Disconnect the Load

The fastest way to separate mechanical problems from electrical problems is to disconnect the motor from the mechanical load. This means loosening the coupling, belt, gear connection, or other transmission connection so that the motor can run freely without load.

Do not test at high speed first. Use a low-speed jog command, such as 30 rpm, 50 rpm, or 100 rpm, and observe whether the motor rotates smoothly.

Check the following:

Can the motor rotate forward without load?

Can the motor rotate backward without load?

Does the motor vibrate during reverse rotation?

Does it make abnormal noise?

Does Er24.1 still appear?

Does Er16.0 still appear?

If the motor runs normally in both directions without load, the servo drive, motor, and encoder are probably not the main problem. The focus should move to mechanical load, brake, limit switch, or machine process.

If reverse rotation still triggers Er24.1 without load, the problem is more likely in motor wiring, encoder feedback, control signal, parameters, motor, or drive hardware.

This simple test is extremely valuable because it can quickly divide the fault into mechanical side or electrical side. Many servo faults take too long to repair because the technician keeps adjusting drive parameters without first separating the motor from the machine.

5. Check U/V/W Motor Wiring and Encoder Feedback

A servo motor is not the same as a normal three-phase induction motor. For a normal induction motor, changing two phases can reverse the direction. But for a servo motor, U/V/W phases cannot be changed randomly. The drive output phase sequence must correspond correctly to the encoder feedback angle. If the motor phase wiring is wrong, or if the encoder feedback direction does not match the drive output, the servo loop may become unstable.

Possible symptoms include vibration, no torque, excessive current, overcurrent, speed deviation alarm, or overload alarm.

The following points must be checked carefully:

U, V, and W are connected to the correct drive terminals;

motor cable has no broken wire;

terminal screws are tight;

connector pins are not bent or pushed back;

motor cable is not damaged;

encoder connector is fully inserted;

encoder cable shield is properly grounded;

encoder cable is not bundled together with power cables for a long distance;

motor and drive belong to the same axis;

motor cable and encoder cable are not crossed with another axis.

Multi-axis machines are especially prone to cable mix-up. For example, the motor power cable may belong to axis A, but the encoder feedback cable may be connected to axis B. Once the motor and encoder are not matched, the drive cannot close the loop correctly. The result may be immediate alarm, vibration, or dangerous motion.

If the fault appeared after repair, transportation, rewiring, motor replacement, or drive replacement, wiring error must be treated as a high-probability cause.

6. Check Reverse Limit and Inhibit Signals

“Cannot reverse” may also be caused by external control signals. A servo drive usually receives signals from a PLC, motion controller, or control board, including pulse command, direction signal, servo enable, positive limit, negative limit, emergency stop, alarm reset, and inhibit signals.

If the reverse direction limit signal is active, the drive may block movement in that direction. The field symptom may look like the motor cannot reverse, or it may stop immediately when reverse command is given.

Check these signals:

positive limit input;

negative limit input;

forward inhibit input;

reverse inhibit input;

emergency stop input;

servo enable input;

pulse input;

direction input;

PLC output logic;

control common wiring;

input terminal function assignment.

Some machines use normally closed limit logic, while others use normally open logic. If a limit switch, PLC output card, wiring, or parameter has been changed, the input logic may become inverted. The machine may not actually be at the negative limit, but the drive may think the negative limit is active, so reverse movement is blocked.

The correct method is not only to watch whether the limit switch moves mechanically. The technician must confirm the actual input status seen by the servo drive. This can be done through the drive monitor function or by measuring the terminal voltage with a multimeter.

7. Check Whether the Brake Is Released

If the servo motor has a holding brake, the brake circuit must be checked separately. Many technicians assume that the brake will automatically release when the servo is enabled, but in actual machines this is not always true.

The brake often requires an independent 24 VDC supply. It may be controlled by a relay, PLC output, or drive output. If the brake power supply is missing, the relay contact is burnt, the brake coil is damaged, or the brake mechanism is stuck, the motor will be forced to rotate against the brake.

Check the following:

brake rated voltage;

whether brake voltage appears after servo enable;

whether the brake makes a clear release sound;

whether the motor shaft can rotate freely after brake release;

whether brake power supply capacity is enough;

whether relay contacts are burnt;

whether brake coil is open or shorted;

whether brake gap is abnormal;

whether the brake is mechanically stuck.

If the brake is not released and the servo is forced to run, Er24.1 and Er16.0 can appear together. The drive outputs current, but the motor does not reach commanded speed. The result is speed deviation and overload.

8. Parameter Adjustment Should Not Be the First Solution

When technicians see speed deviation alarm, they may want to increase the speed deviation threshold. When they see overload alarm, they may want to increase acceleration time, reduce gain, or modify torque limit. Parameter adjustment can sometimes reduce false alarms, but it should not be used to hide a real mechanical or wiring problem.

If the mechanism is jammed, increasing the speed deviation threshold only delays the alarm. The motor may remain stalled for a longer time, causing motor overheating, drive damage, or mechanical deformation.

If U/V/W wiring or encoder feedback is wrong, parameter adjustment cannot solve the root problem. It may only make the fault more dangerous.

Parameter checking should be done after mechanical and wiring checks. Important parameter groups include:

speed deviation detection threshold;

speed deviation detection time;

acceleration time;

deceleration time;

speed loop gain;

position loop gain;

torque limit;

electronic gear ratio;

pulse input mode;

direction signal polarity;

motor capacity setting;

encoder-related settings;

positive and negative limit input assignment.

Do not restore factory parameters blindly. Machine builders may have set electronic gear ratio, limit logic, pulse mode, gain, and control mode according to the actual machine. A careless factory reset may make the machine unable to return to its original working condition.

9. How to Distinguish Drive Fault, Motor Fault, and External Fault

A practical diagnostic sequence should follow this order:

external mechanical system;

motor and encoder wiring;

control signals;

parameters;

drive and motor hardware.

If the motor runs normally without load but alarms under load, suspect mechanical load, brake, guide rail, lead screw, belt, gearbox, or machine jamming.

If forward works but reverse fails, suspect reverse mechanical resistance, negative limit, reverse inhibit, direction logic, or reverse acceleration impact.

If both forward and reverse vibrate or lack torque, suspect U/V/W wiring, encoder cable, motor matching, or servo gain.

If the alarm appears immediately after servo enable, suspect encoder fault, motor cable fault, drive power module, motor winding, brake locking, or serious parameter mismatch.

If the alarm appears randomly, suspect loose connectors, poor shield grounding, encoder interference, terminal contact problem, unstable power supply, or intermittent mechanical jamming.

If replacing the drive does not change the fault, the problem is probably not inside the drive. It is more likely in motor, encoder, wiring, mechanics, or control signal.

If replacing the motor solves the problem, the original motor may have encoder, winding, or brake failure.

If replacing the encoder cable solves the problem, the original cable or connector has a hidden fault.

If the same drive and motor work normally on a test bench but fail after installation, the machine mechanism or control logic must be checked.

10. Recommended Field Troubleshooting Procedure

For a Zhishan K5 servo drive showing Er24.1, sometimes with Er16.0, and failing to reverse, the following procedure is recommended.

First, record the alarm timing. Confirm whether the alarm appears at power-on, at servo enable, during forward rotation, or only during reverse rotation. The timing is more important than the alarm code alone.

Second, check whether the mechanism can move backward. With power off, manually rotate the transmission mechanism if possible. Check for tight points, hard stops, abnormal noise, brake locking, or one-direction resistance.

Third, disconnect the load and test the motor alone. Run forward and reverse at low speed. If the motor runs normally without load, focus on the mechanical side. If reverse still alarms without load, focus on wiring, feedback, control signal, or parameter.

Fourth, check the brake. If the motor has a brake, confirm that it is really released, not only that the control signal exists.

Fifth, check U/V/W and encoder wiring. Confirm motor phase wiring, encoder cable, shielding, connectors, and axis matching.

Sixth, check control input status. Focus on negative limit, reverse inhibit, emergency stop, servo enable, direction signal, and pulse command.

Seventh, check parameters. Confirm speed deviation threshold, acceleration and deceleration time, torque limit, direction polarity, pulse mode, electronic gear ratio, and limit input function assignment.

Eighth, test again at low speed. Start with no load, then light load, then normal load. Observe current, speed feedback, machine movement, and alarm behavior at each step.

Ninth, use substitution testing only when necessary. A same-model motor, encoder cable, or drive can be exchanged for comparison, but wiring and parameters must be confirmed before testing to avoid causing new damage.

11. Common Mistakes During Repair

Several mistakes are common when repairing this type of servo fault.

The first mistake is increasing the speed deviation threshold immediately after seeing Er24.1. This may hide mechanical jamming and cause more serious damage.

The second mistake is assuming the drive power module is bad after seeing Er16.0. Overload is often caused by load or motion conditions, not necessarily by drive hardware failure.

The third mistake is repeatedly testing the machine without disconnecting the load. If the mechanism is jammed, repeated testing sends high current into the motor and drive.

The fourth mistake is swapping U/V/W phases casually. A servo motor cannot be treated like a normal induction motor.

The fifth mistake is checking only the motor power cable and ignoring the encoder cable. Servo control is closed-loop. Encoder feedback problems can also cause speed deviation and overload.

The sixth mistake is looking only at the physical limit switch but not the drive input status. A switch may move correctly, but the drive terminal may receive the wrong signal.

The seventh mistake is restoring factory settings blindly. This may erase the original electronic gear ratio, limit logic, pulse mode, and gain settings.

The eighth mistake is ignoring the brake. A brake that does not fully release is a frequent cause of overload and speed deviation alarms.

12. Conclusion

When a Zhishan K5 series servo drive reports Er24.1, the core meaning is excessive speed deviation. When Er16.0 appears as well, the system also has an overload condition. For the symptom “reverse rotation failure,” the correct conclusion is not to immediately condemn the servo drive. The most likely causes are reverse-direction mechanical resistance, active reverse limit, brake not released, excessive load, abnormal encoder feedback, wrong wiring, or incorrect direction logic.

The correct repair method is to separate the mechanical side from the electrical side first. Disconnect the load and test forward and reverse rotation at low speed. If the motor works normally without load, check the mechanism, brake, and limit signals. If the alarm still appears without load, check U/V/W wiring, encoder cable, control terminals, direction command, and parameters.

Parameter adjustment should be used only after the real cause is identified. It should never be used to cover up mechanical jamming or wiring errors.

A servo alarm is the result of closed-loop monitoring. Er24.1 means the actual motor speed does not follow the command. Er16.0 means the motor or drive is overloaded. Only by analyzing command, feedback, current, mechanical load, and control signals together can the technician locate the fault quickly, avoid unnecessary part replacement, reduce downtime, and prevent further damage to the motor, drive, and machine mechanism.

Posted on

ABB EL3010-C / Uras26 Gas Analyzer Calibration Failure Analysis: From Abnormal SO₂ Concentration to “Raw Values Cannot Be Sampled”

In industrial flue gas monitoring, process gas analysis, environmental emission control, and chemical process measurement, the ABB EL3000 / EL3010-C gas analyzer is a widely used online analytical instrument. When configured with a Uras26 infrared analyzer module, it can measure infrared-active gases such as SO₂, CO₂, CO, NO, CH₄, and other process components. Because this type of analyzer involves optical detection, sample cells, temperature compensation, pressure compensation, EEPROM data sets, internal calibration cells, and external span gas calibration logic, a calibration failure should never be judged from one parameter alone.

A typical case involves an ABB EL3010-C gas analyzer that failed during SO₂ calibration. Two phenomena appeared at the same time. First, in ABB Optima TCT software, the Calibration Cell 1 parameter showed an apparently abnormal SO₂ concentration component, approximately 0.3134 ppm. Second, when manual zero calibration was performed from the analyzer front panel, the analyzer displayed the following error:

ERROR
Calibration canceled!
Raw values cannot be sampled!
SO2

Many technicians may see the first symptom and immediately conclude that the SO₂ calibration cell concentration is wrong, or that the EEPROM data is corrupted. However, from a troubleshooting perspective, the second message is more important. It means the analyzer cannot acquire a valid raw signal from the SO₂ channel during calibration. Therefore, this problem should not be treated simply as a wrong concentration value in the TCT configuration. The correct diagnostic sequence should be: verify whether the raw signal is valid, check detector status, confirm gas flow and calibration conditions, verify pressure and temperature compensation, and only then investigate whether the configuration data or EEPROM data set is corrupted.

ABB EL3010-C gas analyzer showing an SO2 calibration error while a laptop displays Optima TCT software with Calibration Cell 1 settings and SO2 diagnostic data.

1. Basic Working Logic of ABB EL3010-C and the Uras26 Module

The ABB EL3010-C belongs to the ABB EL3000 / Advance Optima family of gas analyzers. Depending on configuration, the system may include a Uras26 infrared analyzer module, pressure sensor, temperature compensation unit, sample gas handling components, I/O modules, and a system controller.

The Uras26 is a nondispersive infrared gas analyzer module. Its basic principle is that infrared light passes through a sample gas cell. Different gas molecules absorb infrared energy at specific wavelengths. The detector receives the remaining light intensity, and this detector signal changes according to gas concentration. The analyzer then applies linearization, temperature compensation, pressure compensation, cross-sensitivity correction, and other algorithms to convert the raw detector signal into a displayed concentration value.

For service work, three types of data must be clearly distinguished.

The first type is the raw value, meaning the original detector signal or internal raw count. It is not ppm, not vol%, and not the final gas concentration. It is the basic signal used by the analyzer for calculation.

The second type is the measured value, meaning the calculated gas concentration after internal processing, such as SO₂ ppm or CO₂ vol%.

The third type is configuration and calibration data, including detector configuration, gas component settings, measurement ranges, calibration cell parameters, calibration factors, compensation parameters, and linearization data. These values are usually stored in the module EEPROM or related memory.

When the analyzer reports “Raw values cannot be sampled,” the message directly points to the first type of data. The SO₂ channel cannot provide a valid raw value for the calibration algorithm. At this stage, even if a calibration cell concentration value looks suspicious in TCT, it should not immediately be treated as the root cause.

2. The Role of Optima TCT: Not a Simple Routine Calibration Tool

ABB Optima TCT stands for Test & Calibration Tool. It connects to ABB Advance Optima analyzer modules and can read data sets from the module EEPROM. It can also save, archive, configure, test, and write data sets back to the module. In the TCT tree structure, a technician may see items such as General Data, Uras26 Detector, SO₂ component, measurement range, temperature detector, pressure detector, and Calibration Cell.

In field service, TCT is useful mainly for the following tasks:

  1. Reading and saving the original EEPROM configuration data;
  2. Checking the relationship between detectors, components, ranges, and calibration cells;
  3. Checking raw values, component values, and status codes;
  4. Checking pressure and temperature compensation values;
  5. Testing pumps, valves, module communication, and detector status;
  6. Restoring or correcting configuration data after confirming the correct data source;
  7. Comparing data set changes before and after calibration.

However, TCT should not be understood as the tool that must be used for daily zero and span calibration. In normal maintenance, routine zero calibration and span calibration are usually performed from the analyzer front panel, through the automatic calibration sequence, or through a plant control system. TCT is more suitable for engineering configuration, deeper diagnostics, data backup, and data recovery.

Therefore, when a customer asks, “How do you configure such gas analyzers?” the accurate answer is:

Routine zero and span calibration should normally be performed from the analyzer menu. TCT is mainly used to read, back up, inspect, and restore configuration data. When calibration from the analyzer menu fails, when parameters appear corrupted, or when module configuration is suspicious, TCT is then used to analyze EEPROM data sets and module status.

3. Calibration Cell Concentration Is Not the Same as External Span Gas Concentration

In this case, the TCT screen showed Calibration Cell 1 configured approximately as follows:

  • Cell Type: Cell with one component;
  • Detector Component 1: Uras26 Detector 1;
  • Component: SO₂ ppm;
  • Concentration Component 1: approximately 0.3134 SO₂ ppm;
  • Raw Value Component 1: approximately 1714596;
  • Calibration Cell Factor 1: approximately 0.3077.

Since the SO₂ measuring range was 0–200 ppm, many technicians would consider 0.3134 ppm unreasonable. From practical experience, this value does look suspicious for a 0–200 ppm SO₂ range. However, one point must be emphasized: the Calibration Cell concentration component is not the same as the external SO₂ span gas concentration, and it is not the live SO₂ reading.

An internal calibration cell is usually an internal optical reference, such as a reference gas cell or an equivalent absorption element inserted into the infrared optical path. It simulates a known absorption effect so that the analyzer can check or correct drift. Its parameters must match the exact analyzer, exact detector, exact calibration cell certificate, and original factory data. A technician should never simply replace this value with 50 ppm, 100 ppm, or any other span gas concentration just because the value looks wrong.

If the goal is to calibrate SO₂ using an external standard gas cylinder, the correct target is the analyzer’s zero/span calibration menu, not manual modification of the Calibration Cell concentration in TCT.

Therefore, the 0.3134 ppm value in Calibration Cell 1 should be treated as a suspicious parameter, but not as a confirmed fault by itself. The technician must first confirm:

  • Whether this analyzer physically has an internal calibration cell installed;
  • Whether Calibration Cell 1 really belongs to SO₂;
  • Whether Calibration Cell 2 belongs to another detector or component;
  • What the original factory equivalent concentration of the cell should be;
  • Whether the calibration cell factor was modified;
  • Whether the current data set truly belongs to this analyzer;
  • Whether someone previously wrote another analyzer’s data set into this module.

Without this information, EEPROM data should not be modified.

Technician troubleshooting an ABB EL3010-C Uras26 gas analyzer with SO2 zero and span gas connections while Optima TCT shows raw value and overrange status.

4. “Raw Values Cannot Be Sampled” Is the Core Diagnostic Clue

The analyzer front panel displayed:

Calibration canceled!
Raw values cannot be sampled!
SO2

This message is more diagnostically important than the concentration component shown in TCT. It means that during SO₂ calibration, the analyzer attempted to acquire the SO₂ raw signal, but the sampling failed or the sampled value was invalid. As a result, the calibration was canceled.

This type of error usually comes from several main categories.

4.1 Sample Gas Flow Problems

During calibration, zero gas or span gas must actually enter the analyzer sample cell. If the gas does not enter the analyzer, or if the flow is unstable, the analyzer cannot acquire a stable raw value.

Common causes include:

  • Zero gas not opened;
  • Abnormal outlet pressure from the gas cylinder regulator;
  • Too low gas flow;
  • Inlet pressure too high or too low;
  • Blocked sample filter;
  • Blocked exhaust outlet;
  • Internal sample pump not working;
  • Solenoid valve not switching to the correct gas path;
  • Tubing connected incorrectly;
  • Condensate inside the sample cell;
  • Sample gas path blocked by sulfate deposits, dust, or corrosion products.

Online SO₂ analyzers are especially vulnerable to acidic condensate and dust contamination. If the sample conditioning system fails, moisture, acid mist, sulfur compounds, and particles may enter the sample cell. Mild contamination may cause drift, while severe contamination may attenuate the optical path or block the gas path.

4.2 Abnormal Raw Signal from Uras26 Detector 1

If SO₂ is assigned to Uras26 Detector 1, failure to sample raw values may indicate a problem in the detector signal chain.

Typical symptoms include:

  • Raw value is zero or extremely low;
  • Raw value remains frozen;
  • Raw value exceeds the ADC range;
  • Raw value fluctuates violently;
  • Detector status code is abnormal;
  • Analyzer shows overrange, underrange, invalid value, or alarm indication;
  • Calibration cannot reach a stable condition.

Possible causes include infrared source aging, infrared source failure, chopper malfunction, detector aging, preamplifier failure, ADC acquisition fault, loose signal connection, module power problem, or severe contamination of the sample cell.

4.3 Optical System Contamination or Attenuation

The Uras26 measurement depends on a stable infrared optical path. If the source, mirror, window, sample cell, or detector optical path is contaminated, the detector signal will be reduced or distorted. In SO₂ applications, optical contamination is relatively common, especially when sample conditioning is poor. Moisture, acid mist, dust, and reaction products can deposit on optical windows.

If optical attenuation becomes severe, the analyzer may still display some value in measurement mode, but during calibration it may fail to satisfy the required stability, intensity range, or algorithm conditions. The result can be “Raw values cannot be sampled.”

4.4 Temperature or Pressure Compensation Problems

Infrared gas absorption is affected by temperature and pressure. In an EL3010-C / Uras26 configuration, temperature and pressure compensation are often present. In the TCT tree, this may appear as items such as T-Con U26 C and A.Pres hPa. If temperature or pressure measurements are invalid, the final SO₂ calculation may also become invalid, and calibration may be blocked.

The following points should be checked:

  • Whether the pressure value is reasonable, such as close to atmospheric pressure or within the expected process range;
  • Whether the temperature value is reasonable;
  • Whether the pressure sensor has an alarm;
  • Whether the temperature compensation status is normal;
  • Whether the compensation items are configured correctly;
  • Whether the pressure or temperature value is used in the current SO₂ range calculation.

If the pressure sensor is open-circuit, short-circuit, out of range, or incorrectly configured, the analyzer may be unable to calculate a valid SO₂ value.

4.5 Configuration Data or EEPROM Data Set Problems

If hardware and gas flow are normal, but TCT shows logical inconsistencies between detector, component, measurement range, and calibration cell configuration, the EEPROM data set may have been modified incorrectly or corrupted.

Common situations include:

  • A technician wrote another analyzer’s data set into this module;
  • A CPU board or memory device was replaced but the correct data set was not restored;
  • Calibration cell settings were modified incorrectly in the full version of TCT;
  • Detector 1 / Detector 2 assignment does not match SO₂ / CO₂ component assignment;
  • Measurement range is missing;
  • Correction function points to a non-existent component;
  • Calibration cell points to the wrong detector;
  • Data set is incompatible with the actual module type;
  • EEPROM memory is unstable.

However, EEPROM failure should not be the first assumption. It should be investigated only after gas flow, detector raw value, pressure, temperature, and optical condition have been checked.

5. Correct Troubleshooting Sequence: Do Not Modify Parameters First

The worst response to this type of problem is to directly modify the concentration component in TCT and write it back to EEPROM. This may destroy recoverable original data and turn a calibration problem into a serious configuration problem.

A safer diagnostic process is as follows.

Step 1: Fully Back Up the Current Data Set

After connecting TCT, read the module data and save it immediately. The saved file extension depends on the module type. Analyzer module files are commonly saved as a format such as .d04. The automatic backup copy generated by TCT should also be preserved.

At minimum, save two files:

  • Original file before testing;
  • File after zero calibration or after the error occurs.

If it is necessary to determine whether a parameter “changed by itself,” the conclusion must be based on a comparison of before-and-after data files, not memory or screenshots alone.

Step 2: Do Not Write to EEPROM

Before the fault is confirmed, do not execute Send Module Data and do not write any modified data back to the analyzer module. This is especially important for Calibration Cell, Detector, Component, Range, and Correction Function settings.

Step 3: Use Module Test View to Check Real Status

The Module Test View in TCT is the most important diagnostic screen in this case. The following values should be checked:

  • Uras26 Detector 1 raw value;
  • Uras26 Detector 1 status;
  • SO₂ component measured value;
  • SO₂ percentage of range;
  • SO₂ status code;
  • Active correction functions;
  • Pressure value;
  • Temperature value;
  • Pump and valve test status.

If the SO₂ raw value is missing, frozen, overrange, or has an abnormal status, the problem already exists before calibration. In that case, there is no point focusing only on calibration cell concentration.

Step 4: Confirm Zero Gas and Flow

Before performing zero calibration, confirm that the zero gas source is correct. SO₂ zero calibration is usually performed with high-purity nitrogen or suitable zero gas. Clean air may be acceptable in some applications, but only if it meets the analyzer and process requirements.

The following field checks are necessary:

  • Whether zero gas is connected to the correct inlet;
  • Whether flow rate meets analyzer requirements;
  • Whether the outlet is open;
  • Whether the internal pump is operating;
  • Whether solenoid valves are switching correctly;
  • Whether the sample conditioning system is dry and clean;
  • Whether there is condensate or blockage.

If the gas path is not open, the analyzer cannot sample a stable raw value.

Step 5: Observe Whether SO₂ Is Valid in Measurement Mode

Before repeating calibration, check whether SO₂ is displayed normally in measurement mode. If SO₂ is already invalid, unstable, overrange, or constantly negative in measurement mode, the problem is not the calibration operation itself. The detection chain already has an issue.

The symptoms can be interpreted as follows:

  • SO₂ value is stable in measurement mode, but calibration fails: likely calibration condition, stability judgment, or configuration problem;
  • SO₂ value is unstable: likely gas flow fluctuation, optical source problem, or detector issue;
  • SO₂ value is overrange: possible wrong gas concentration, optical contamination, configuration error, or real contamination;
  • SO₂ value is invalid: prioritize raw value, ADC, pressure, and temperature compensation checks;
  • SO₂ value remains frozen: possible signal chain freeze or data update failure.

Step 6: Check Pressure and Temperature Compensation

Verify whether pressure and temperature values are within reasonable ranges. If pressure or temperature is abnormal, correct the compensation signal first. Otherwise, even a healthy SO₂ detector may produce invalid calculated concentration.

Step 7: Only Then Investigate Calibration Cell Configuration

Only after raw value, gas flow, pressure, temperature, and SO₂ measurement stability are confirmed should Calibration Cell 1 and Calibration Cell 2 be investigated.

At that point, check:

  • Whether Calibration Cell 1 should be assigned to SO₂;
  • Whether Calibration Cell 2 should be assigned to CO₂;
  • Whether Cell Type is correct;
  • Whether Detector Component 1 / 2 are correct;
  • Whether Concentration Component matches original factory data;
  • Whether Calibration Cell Factor is reasonable;
  • Whether an original backup data set is available for recovery.

Without an original certificate or backup, calibration cell parameters should not be reconstructed by guesswork.

6. How to Judge Whether EEPROM or Memory Is Faulty

When a parameter appears to change unexpectedly, technicians often suspect EEPROM failure. This is possible, but evidence is required.

A real EEPROM or memory data problem usually shows symptoms such as:

  1. Parameters are lost after power cycling;
  2. The same data reads differently each time;
  3. Serial number, module type, detector configuration, or range configuration becomes abnormal;
  4. Different screens show contradictory component, range, or detector logic;
  5. TCT reports errors such as data not compatible, unknown index, invalid subindex, or module data incorrect;
  6. Before-and-after file comparison shows irregular changes in non-calibration configuration fields;
  7. Write verification fails;
  8. The analyzer randomly reports configuration errors or module identification errors.

If only zero correction, drift, raw reference, or offset-related values change after zero calibration, that may be part of the normal calibration process and does not prove EEPROM failure.

The correct method is data comparison:

  1. Read the module data with TCT and save it as before_zero;
  2. Take screenshots of Calibration Cell 1, Calibration Cell 2, SO₂ component, range, and Module Test View;
  3. Perform zero calibration from the analyzer front panel;
  4. Re-read the module data from the module, instead of opening the old file;
  5. Save it as after_zero;
  6. Compare the two files and screenshots.

If changes are mainly limited to zero, drift, calibration result, or correction values, they may be normal or calibration-related. If nominal Calibration Cell concentration, Detector assignment, Range definition, Component name, or similar configuration fields change without reason, then corrupted data or memory instability becomes much more likely.

7. Relationship Between External Gas Calibration and Internal Calibration Cell

For a 0–200 ppm SO₂ measuring range, reliable calibration is usually based on external standard gas. A typical procedure is:

  1. Introduce zero gas;
  2. Wait until SO₂ measured value and raw value are stable;
  3. Perform zero calibration;
  4. Introduce certified SO₂ span gas;
  5. Wait until the reading is stable;
  6. Perform span calibration or end-point calibration;
  7. Recheck zero gas;
  8. Recheck span gas;
  9. Record calibration deviations before and after adjustment.

The span gas concentration should be selected according to the range. For a 0–200 ppm range, a span gas around 50% to 90% of full scale is commonly used, such as 100 ppm, 150 ppm, or 160 ppm, depending on site rules, analyzer instructions, and metrology requirements.

The internal calibration cell is usually used for drift checking, internal verification, or certain automatic calibration functions. It should not be treated as a complete substitute for external standard gas, especially after repair, optical contamination, detector replacement, suspected data corruption, or long-term drift.

8. Reasonable Fault Chain in This Case

Based on the observed symptoms, the more reasonable fault chain is:

The SO₂ channel cannot provide a valid raw value during calibration
→ The front-panel zero calibration is canceled
→ Calibration Cell 1 or related values in TCT appear abnormal
→ The field technician assumes the Calibration Cell 1 concentration is wrong
→ The actual root cause may be SO₂ raw signal acquisition, gas flow, optical condition, pressure/temperature compensation, or data set consistency.

Therefore, the most important next step is not to modify the 0.3134 ppm value. The priority is to obtain the SO₂ raw value and status code from Module Test View. Without this information, it is impossible to determine whether the root cause is gas path failure, detector failure, optical contamination, pressure/temperature compensation failure, or EEPROM data corruption.

9. Service Conclusion and Recommended Handling

When an ABB EL3010-C / Uras26 gas analyzer reports “Calibration canceled! Raw values cannot be sampled! SO2,” the following principles should be followed.

First, back up data before making any change.
The data set read by TCT is the basis for recovery and comparison. Any write-back action must be performed only after confirming that the data is correct.

Second, check raw value before checking concentration.
The SO₂ displayed concentration is a calculated result. The raw value is the foundation of whether calibration can proceed.

Third, check gas flow before suspecting the circuit board.
Whether zero gas actually enters the analyzer, whether flow is stable, whether the sample cell is blocked, and whether valves and pumps are working are often overlooked but critical.

Fourth, check pressure and temperature compensation before judging the SO₂ algorithm.
Abnormal pressure and temperature values can directly affect gas concentration calculation and calibration validity.

Fifth, do not modify Calibration Cell parameters casually.
The internal calibration cell concentration is not the external span gas concentration. It must be confirmed using the original certificate, backup file, or factory data.

Sixth, EEPROM failure must be proven.
Memory or EEPROM should be strongly suspected only when parameters read inconsistently, configuration fields change without reason, data is lost after power cycling, incompatible data messages appear, or module identification becomes abnormal.

10. Summary

For an ABB EL3010-C / Uras26 gas analyzer, calibration problems should not be judged only by one concentration value or one TCT parameter. An abnormal SO₂ concentration component under Calibration Cell 1 is worth investigating, but the front-panel message “Raw values cannot be sampled! SO2” is the more direct and important diagnostic clue. It means the SO₂ channel cannot provide a valid original signal during calibration, so the calibration algorithm cannot continue.

The correct troubleshooting strategy is to examine SO₂ raw value, detector status, gas flow, optical condition, pressure and temperature compensation, and configuration data consistency step by step. TCT should be used as a diagnostic and backup tool, not as an entry point for blind parameter modification. Only after hardware, gas path, raw signal, and compensation values are confirmed should Calibration Cell configuration be corrected, and only with reliable original data.

For high-precision gas analyzers, the most dangerous service action is not a temporary calibration failure. The real danger is writing new EEPROM data without backup or evidence. The proper method is to save the original data first, then use Module Test View to identify why the SO₂ raw value cannot be sampled. This approach prevents a diagnosable calibration fault from becoming a much more complicated configuration corruption problem.

Posted on

Troubleshooting a Batching Weighing System That Cannot Return to Zero, Displays Negative Weight at Empty Hopper, and Shows Only 19.83 kg with a 20 kg Test Weight

In powder, granule, plastic, chemical, food, feed, and building material production lines, batching weighing systems are one of the most critical parts of the entire automation process. A typical weighing system consists of a weighing hopper, load cells, weighing transmitters or indicators, PLC control systems, HMI touch screens, pneumatic valves, vacuum conveying systems, discharge valves, vibrators, and related mechanical structures.

When a batching scale begins to show symptoms such as:

  • inability to return to zero,
  • negative weight values when the hopper is empty,
  • unstable readings,
  • or inaccurate display values when standard weights are applied,

the issue can directly affect formula accuracy, production consistency, and final product quality.

This article analyzes a real industrial case involving a batching system using a METTLER TOLEDO IND131 weighing module. The system exhibited several typical problems:

  1. The empty hopper displayed approximately -2.03 kg to -2.05 kg.
  2. The HMI and the IND131 module displayed nearly identical values.
  3. Two 10 kg calibration weights produced a reading around 19.90 kg.
  4. A 20 kg test weight later produced a display of 19.83 kg.
  5. The customer reported that the “20 kg weight still shows slightly less than actual.”

Although these symptoms may initially appear minor, they actually reveal potential issues related to zero offset, tare errors, mechanical interference, load cell installation stress, calibration deviation, and weighing repeatability.


Industrial batching weighing system with stainless steel weigh hopper, load cell, pneumatic discharge valve, METTLER TOLEDO IND131 weighing module, and PLC/HMI control panel, illustrating the mechanical isolation required for accurate hopper weighing.

Understanding the Initial Symptoms

The first important observation was that both the HMI screen and the IND131 module displayed nearly the same negative value while the hopper was empty.

This is extremely significant from a troubleshooting perspective.

If the HMI displayed -2.05 kg while the IND131 module itself displayed 0.00 kg, the problem would likely be related to PLC scaling, communication conversion, HMI display configuration, or software logic.

However, because both devices showed nearly identical readings, the weighing signal itself was already offset into the negative range. This strongly suggests that the issue originates from the weighing system itself rather than the communication layer.

Later, when the customer added test weights, the system responded correctly in principle:

  • Two 10 kg weights produced approximately 19.90 kg.
  • A later 20 kg test showed 19.83 kg.

This proves several important things:

  • The load cell is not completely dead.
  • The IND131 module is receiving weight signals.
  • Signal polarity is generally correct.
  • Communication between the weighing module and PLC/HMI is functional.

Therefore, this type of fault should not immediately be classified as a failed weighing module or failed load cell.

A more accurate conclusion is:

The weighing system is operational, but suffers from zero offset, calibration deviation, or external mechanical interference.


Common Causes of Negative Weight at Empty Hopper

Incorrect Zeroing or Taring While Material Was Still Present

This is one of the most common causes in industrial batching systems.

Operators sometimes execute a ZERO or TARE command while residual material is still inside the hopper, while valves are not fully discharged, or while powder buildup remains attached to internal surfaces.

For example:

  • The hopper actually contains 2 kg of material.
  • The operator mistakenly performs a ZERO operation.
  • The system records this condition as 0.00 kg.
  • Later, after the hopper becomes truly empty, the display shows approximately -2 kg.

This does not necessarily indicate load cell failure. It simply means the zero reference was incorrectly established.

This problem is particularly common in powder handling systems where:

  • material sticks to hopper walls,
  • powder accumulates around discharge valves,
  • or vacuum conveying systems leave residual product inside the hopper.

Tare Values Were Not Cleared

Many technicians confuse ZERO and TARE functions, but they are not the same.

ZERO

Used to correct small offsets around true empty scale conditions.

TARE

Used to subtract container or process weight from the gross reading, displaying net weight instead.

If the system still retains a previous tare value, the empty hopper may display a negative number.

For example:

  • The system stored a 2 kg tare.
  • The hopper later becomes empty.
  • The net display becomes approximately -2 kg.

Therefore, troubleshooting must include checking for:

  • TARE,
  • CLEAR TARE,
  • PRESET TARE,
  • GROSS/NET mode,
  • NET WEIGHT display,
  • or hidden PLC tare variables.

Simply pressing ZERO may not solve the problem if an active tare remains inside the system.


Close-up of a METTLER TOLEDO IND131 weighing module inside an industrial control cabinet displaying 19.83 kg during a 20 kg test weight check, with the batching machine HMI and weigh hopper shown in the background.

Mechanical Interference and External Forces

A weighing hopper must remain mechanically isolated.

The hopper’s entire weight should transfer only through the load cell(s). Any external force can distort measurements.

In the provided industrial structure, the weighing hopper is surrounded by:

  • pneumatic tubing,
  • electrical cables,
  • vacuum lines,
  • discharge pipes,
  • vibrators,
  • support frames,
  • and valve assemblies.

Even slight pulling or pushing forces can create weight deviations ranging from several grams to multiple kilograms.

Typical interference sources include:

  • cables tied too tightly,
  • hardened flexible connectors,
  • vacuum hoses pulling upward,
  • discharge valve misalignment,
  • hopper walls touching support frames,
  • poorly installed vibrators,
  • side-loading on the load cell,
  • or piping transmitting external forces into the hopper.

A negative empty-hopper reading may actually indicate that some external structure is slightly lifting the hopper upward.


Load Cell Installation Stress

Load cells are highly sensitive to mechanical installation quality.

They are designed primarily for vertical force measurement. Side forces, torsion, uneven mounting surfaces, excessive tightening, or frame distortion can all affect zero stability and repeatability.

Over time, industrial systems experience:

  • vibration,
  • impact loading,
  • corrosion,
  • dust accumulation,
  • thermal expansion,
  • structural deformation,
  • and mechanical wear.

Even if the electrical part of the load cell remains functional, mechanical stress can still produce symptoms such as:

  • inability to return to zero,
  • unstable repeatability,
  • or inaccurate calibration readings.

What Does 19.83 kg with a 20 kg Test Weight Mean?

When the customer applied a 20 kg calibration weight, the IND131 displayed 19.83 kg.

This result provides two important conclusions.

The Weighing System Is Basically Functional

The system responds proportionally to added weight. This confirms:

  • the load cell generates output,
  • the IND131 receives the signal,
  • the display scaling is generally correct,
  • and signal direction is proper.

This is not a total system failure.


The System Has Measurement Error

The error is:

20.00 kg – 19.83 kg = 0.17 kg

That equals 170 grams.

Relative error:

0.17 ÷ 20.00 = 0.85%

Whether this is acceptable depends on the process requirements.

For large-scale bulk batching, such as 85 kg recipes, 170 g may be tolerable.

For precision chemical dosing, additives, pigments, or specialty materials, this error may be unacceptable.


Accuracy Error vs Repeatability Error

One of the biggest mistakes in industrial weighing maintenance is immediately recalibrating the system after observing a small error.

Before calibration, repeatability must be verified.


Good Repeatability

If repeated tests produce:

  • Empty hopper: 0.00 kg
  • 20 kg applied: 19.83 kg
  • Weight removed: 0.00 kg
  • Repeat cycles remain consistent

then the system likely has good repeatability and only requires span calibration adjustment.


Poor Repeatability

If repeated tests produce:

  • 19.90 kg,
  • then 19.83 kg,
  • then 19.70 kg,
  • and empty readings drift unpredictably,

then the issue is not simple calibration deviation.

Possible causes include:

  • mechanical binding,
  • piping interference,
  • side loading,
  • unstable load cell mounting,
  • inconsistent force transfer,
  • vibration effects,
  • or electrical instability.

In such cases, calibration should NOT be performed until the underlying mechanical instability is corrected.


Importance of Return-to-Zero Performance

A weighing system must reliably return to the same zero point after unloading.

If the scale:

  • drifts after unloading,
  • fails to return to zero,
  • or stabilizes at different empty values,

then mechanical or sensor-related issues remain unresolved.

Poor return-to-zero behavior often results from:

  • hopper friction,
  • pipe tension,
  • load cell side stress,
  • residual product buildup,
  • pneumatic actuator movement,
  • or structural deformation.

Correct Troubleshooting Procedure

Industrial weighing systems should be diagnosed in the following order:

  1. Mechanical condition
  2. Zero condition
  3. Repeatability
  4. Calibration

Step 1 – Ensure the Hopper Is Truly Empty

Stop automatic operation and verify:

  • no residual material remains,
  • discharge valves are fully open,
  • powder buildup is removed,
  • and the hopper is physically empty.

Never rely only on the HMI display.


Step 2 – Verify Mechanical Freedom

Check carefully for:

  • hopper contact with the frame,
  • rigid hoses,
  • over-tightened cables,
  • discharge pipe misalignment,
  • vacuum line tension,
  • vibrator mounting problems,
  • or support interference.

The hopper must move freely on the load cell.


Step 3 – Clear Tare Values

Check whether the system is displaying:

  • NET weight,
  • GROSS weight,
  • or an active TARE value.

Clear all tare values before troubleshooting zero errors.


Step 4 – Zero the IND131 Directly

Do not rely solely on the HMI ZERO button.

The HMI may communicate through PLC logic, which can block or modify the command.

Instead, perform ZERO directly on the IND131 module itself.

If the IND131 zeros correctly but the HMI does not, the problem likely exists in PLC logic or communication commands.


Step 5 – Perform Repeatability Testing

Conduct multiple loading cycles:

  1. Zero the empty hopper.
  2. Apply a known calibration weight.
  3. Record the stable reading.
  4. Remove the weight.
  5. Verify return-to-zero.
  6. Repeat several times.

Repeatability is more important than single-point accuracy.


When Should Calibration Be Performed?

Calibration should only be performed after confirming:

  • stable zero,
  • good repeatability,
  • no mechanical interference,
  • proper load cell mounting,
  • and correct electrical wiring.

If the system consistently displays 19.83 kg for a true 20 kg weight and always returns to zero correctly afterward, then span calibration is appropriate.

However, if the system normally operates around 85 kg batching ranges, using only a 20 kg calibration weight is not ideal.

Calibration loads should preferably approach the normal operating range whenever possible.


Wiring and Load Cell Signal Considerations

Typical IND131 load cell terminals include:

  • +EXC
  • -EXC
  • +SIG
  • -SIG
  • +SEN
  • -SEN

Incorrect wiring may produce:

  • unstable readings,
  • reversed weight direction,
  • poor zero stability,
  • or scaling errors.

If pressing downward causes displayed weight to decrease, signal polarity may be reversed.

Electrical checks should include:

  • terminal tightness,
  • shielding quality,
  • cable insulation,
  • grounding,
  • and moisture contamination.

Determining Whether the Load Cell Is Actually Faulty

A negative reading alone does not prove load cell failure.

True load cell damage usually involves:

  • unstable drift,
  • poor repeatability,
  • severe nonlinearity,
  • inability to return to zero,
  • physical deformation,
  • moisture ingress,
  • or abnormal millivolt output.

If possible, technicians should measure actual load cell mV output using proper instrumentation.


Final Technical Conclusion

This weighing system is not completely nonfunctional.

The 20 kg test producing approximately 19.83 kg demonstrates that:

  • the load cell is active,
  • the IND131 is operating,
  • communication is functioning,
  • and weight response exists.

However, the system still exhibits:

  • zero offset,
  • potential mechanical interference,
  • calibration deviation,
  • or incomplete tare removal.

The correct repair sequence is:

Eliminate mechanical interference → Clear tare → Establish proper zero → Verify repeatability → Perform calibration only afterward.

If repeatability is stable, calibration can correct the remaining offset.

If repeatability remains unstable, mechanical and installation problems must be solved before any recalibration attempt.


Recommended Field Service Procedure

For industrial batching systems showing negative empty readings and inaccurate calibration response:

  1. Fully empty the hopper.
  2. Stop vacuum conveying, vibration, and pneumatic motion.
  3. Inspect all hoses, cables, and structures for mechanical interference.
  4. Clear all tare values.
  5. Perform zero directly on the IND131.
  6. Conduct repeated loading tests.
  7. Verify repeatability before calibration.
  8. Correct mechanical issues before recalibrating.
  9. Use calibration weights near actual operating range whenever possible.
  10. Verify return-to-zero after every test.

The most important principle in industrial weighing diagnostics is:

Mechanical freedom comes first. Stable zero comes second. Repeatability comes before calibration.

Ignoring this order often leads to repeated calibration failures, unstable production batches, and ongoing weighing problems in industrial batching systems.

Posted on

Troubleshooting the TECO JSDAP Servo Drive RL-04 Overcurrent Alarm: Fault Mechanism and On-Site Diagnostic Method

In CNC machine tools, turret mechanisms, feeder axes, clamping axes, and automated special-purpose machines, servo systems are responsible for precise positioning, fast response, and closed-loop control. Compared with a standard inverter driving an induction motor, a servo system has much higher requirements for motor power wiring, encoder feedback wiring, parameter matching, mechanical load condition, and control sequence. Once any of these links becomes abnormal, the servo drive may not merely show unstable speed or positioning deviation. Instead, it may directly trigger protective alarms such as overcurrent, encoder fault, overload, or excessive position deviation.

In the TECO JSDAP series servo drive, one common field alarm is RL-04, AL-04, or simply 04 on the keypad display. In actual repair work, many users tend to interpret this alarm as “high motor current” or “heavy load.” However, from a maintenance perspective, alarm 04 should not be treated as a simple overload. It is closer to an instantaneous abnormal current protection in the main power circuit. Possible causes include incorrect U/V/W motor phase wiring, abnormal encoder feedback, servo motor winding defects, damaged drive power module, mismatch between parameter Cn030 and the actual motor, mechanical jamming, or a brake that has not been released.

When a machine-tool customer reports that “the servo motor should normally rotate two turns, but now it only moves briefly and then reports RL-04 overcurrent,” this symptom has strong diagnostic value. It usually means the system is not completely faulty at power-on. Instead, the alarm occurs when the servo is enabled, the drive begins outputting current, and the motor just starts to respond. The diagnostic focus should therefore be placed on why the current rises abnormally at the moment of operation, rather than only looking at the auxiliary alarm displayed on the CNC screen.

TECO JSDAP-15A servo drive showing an RL-04 overcurrent alarm during CNC machine troubleshooting, with visible drive label, wiring terminals, technician test probes, and LNC control panel in the background.

1. Basic Meaning of the TECO JSDAP RL-04 Alarm

On the TECO JSDAP series servo drive, alarm 04 generally corresponds to drive overcurrent. From the drive’s protection logic, overcurrent does not simply mean that the load is slightly higher than usual. It means that the main circuit has detected current exceeding the protection threshold. To protect the IGBT/IPM power module, motor windings, and mechanical system, the drive immediately cuts off output and issues an alarm.

For alarm 04, the diagnostic direction normally includes checking whether the motor-side U, V, W wiring and encoder wiring are normal, and confirming that the wiring follows the standard connection diagram. If the alarm still exists after the power has been turned off for a period and then reapplied, the fault may involve the internal power transistor module of the servo drive or severe electrical noise interference.

This means RL-04/04 is not caused by one single fixed fault. It is a protective result for a class of abnormal output-current conditions. Maintenance personnel must judge the cause together with the timing of the alarm: whether it appears immediately after power-on, after servo enable, after the motor moves briefly, after a period of running, under mechanical load, or even when the motor is disconnected. Different timing points correspond to completely different fault ranges.

2. Why “The Motor Moves Once and Then Reports 04” Is Important

In field service, customers often describe the problem as “the servo motor moves a little and then alarms,” “normally it should rotate two turns, but now it stops immediately,” or “after reset, the same thing happens again.” This simple description actually contains several important clues.

First, the drive is not completely unable to power up. If the drive reports 04 immediately after control power or main power is applied, the first suspects would be the drive power module, current detection circuit, main-circuit short circuit, or serious internal component failure. In this case, however, the alarm occurs after operation begins, which means the drive can at least complete part of its initialization. The fault is triggered during output.

Second, the motor has made a short movement. If the motor can move briefly, it means the main circuit has probably output three-phase current, and the servo enable signal and part of the control logic are present. But when the motor starts and the alarm immediately appears, it suggests that the drive detects an abnormal closed-loop control condition. The current response may be much higher than expected, or the motor feedback may not match the drive output, causing the servo amplifier to increase current sharply before tripping.

Third, if the motor should normally complete two revolutions but now cannot, the axis may be involved in homing, turret indexing, clamping-axis positioning, or a fixed travel sequence. If the CNC screen also displays a message such as “clamping axis not returned to home,” that CNC message may not be the root cause. It may simply be the interlock result after the servo axis fails to complete its action. The true primary fault should still be judged from the servo drive display.

Therefore, “one brief movement followed by RL-04” should not be directly judged as motor failure, nor should it immediately be judged as drive failure. The correct approach is to distinguish mechanical load problems, motor feedback problems, power wiring problems, parameter mismatch, and drive hardware failure.

3. Common Cause 1: Incorrect, Loose, or Poorly Insulated U/V/W Motor Wiring

The U, V, W three-phase power wires of a servo motor cannot be swapped casually like those of a standard induction motor. For an ordinary three-phase induction motor, swapping any two phases mainly changes the rotation direction. But an AC servo system is closed-loop controlled. The current vector output by the drive must strictly correspond to the rotor position feedback from the encoder. If the U/V/W phase sequence is wrong, or if one phase is loose or intermittently connected, the drive may find that the motor feedback direction, speed, or phase does not match the expected response. It may then rapidly increase current to correct the error, eventually causing overcurrent protection.

In real field cases, U/V/W problems commonly occur in the following situations:

The motor or drive has been removed for repair, and the wiring was restored without a reference photo.

The terminal screws are aged or not tightened, and vibration causes poor contact during operation.

The motor cable has been worn by the drag chain, sheet-metal edge, or oil-contaminated area, damaging the insulation.

The motor connector has oil or water ingress, causing leakage or short circuits between pins.

The motor cable was replaced, but the wire colors do not match the original factory definition.

The drive output cables are bundled together with other strong-current cables, causing interference or insulation damage.

For field maintenance, wire color alone should not be used as the final judgment. The motor nameplate, connector pinout, original wiring diagram, and actual terminal marks must all be compared. After power-off and full discharge, check whether U, V, and W correspond correctly from the drive to the motor. Then measure the resistance of U-V, V-W, and W-U with a multimeter. The three values should be basically balanced. Next, measure insulation from U/V/W to the motor frame or ground. A standard multimeter can only detect serious short circuits. If insulation degradation is suspected, a megohmmeter should be used. In servo motors, insulation problems may not appear as a complete static short circuit, but may become obvious only when the drive outputs PWM voltage.

JSDAP-15A

4. Common Cause 2: Abnormal Encoder Feedback

The core of a servo system is closed-loop control. The drive not only outputs three-phase current to the motor, but also reads encoder feedback in real time to determine rotor position, speed, and direction. If encoder feedback is lost, reversed, distorted, intermittent, or affected by broken wires or poor connector contact, the drive’s judgment of motor status becomes unreliable.

Encoder faults do not always immediately appear as a dedicated encoder alarm. In some cases, the encoder signal seems normal while stationary, but once the motor starts, vibration causes an internally broken conductor to lose contact, or the feedback position jumps. The drive may then output abnormal current and finally show overcurrent protection. In machine-tool environments, oil mist, coolant, metal chips, long-term vibration, and repeated drag-chain bending can all cause hidden encoder cable damage.

Encoder troubleshooting should be performed systematically. First, power off and unplug the encoder connector. Check whether the pins are bent, retracted, oxidized, or contaminated by oil. Second, inspect the cable sheath for crushing, pulling, or excessive bending. Third, check whether the encoder power supply is normal. Many systems use 5 V encoder power, but the actual value should be confirmed according to the motor and manual. Fourth, if a same-model motor or cable is available, cross-substitution is the most effective method. Encoder cables are one of the most easily overlooked but most common fault points in field service.

If the motor is separated from the mechanical load and still shakes, rushes briefly, or reports 04 as soon as it is enabled, while U/V/W wiring shows no obvious short circuit, encoder feedback should be placed very high on the suspect list.

5. Common Cause 3: Mechanical Jamming, Brake Not Released, or Clamping Mechanism Not Open

In machine tools, a servo motor often does not drive a light free-running load. It may be connected through a coupling, timing belt, reducer, ballscrew, turret, clamping mechanism, homing mechanism, or other mechanical transmission. If the mechanical side is not fully released, the servo motor may face a near-stall load at startup. The current rises instantly, and the drive may report RL-04.

The word “no-load rotation” must be clarified. Customers may use it in two different ways. One means the motor is physically disconnected from the machine and the motor shaft is truly unloaded. The other simply means the machine is running an “empty cycle” or homing program, while the motor is still connected to the mechanical structure. These two meanings are completely different for diagnosis.

If the motor remains connected to the mechanism, the following problems may cause overcurrent:

The mechanical brake has not released.

The turret clamping mechanism has not opened.

Hydraulic or pneumatic pressure is insufficient, so unclamping is incomplete.

The reducer is internally damaged or jammed.

The ballscrew, bearing, or guideway resistance is too high.

The coupling is eccentric, over-tightened, or deformed during installation.

The home switch or limit switch state is incorrect, causing the axis to drive into a mechanical stop.

The machine has been idle for a long time, and oil sludge, chips, or dried coolant has blocked the mechanism.

For servo motors with mechanical brakes, the brake power supply must be checked carefully. A brake usually requires an external DC 24 V control supply to release. The brake wires must not be mistaken for ordinary signal wires. If the brake is not released, the motor is effectively starting against a locked rotor, and overcurrent is almost unavoidable.

The most effective way to identify a mechanical problem is to disconnect the coupling, timing belt, or reducer and let the motor truly run without load. If the motor runs normally after being disconnected and no longer reports 04, the drive and motor are probably not the main cause. The fault should be traced to the mechanical side. If the motor is completely disconnected and still reports 04 immediately after movement, the mechanical side can largely be excluded, and the electrical system should be checked first.

6. Common Cause 4: Incorrect Cn030 Motor Matching Parameter

The TECO JSDAP series drive cannot run any motor arbitrarily. The drive must know the connected motor’s power, rated current, rated speed, encoder type, inertia class, and related characteristics. The parameter Cn030 is used for the motor/drive series matching setting. The diagnostic item dn-08 can be used to check the currently configured drive and motor combination. If the displayed combination does not match the actual motor, Cn030 must be corrected.

This point is especially important for second-hand machine tools, old equipment repair, drive replacement, and parameter initialization. Many field failures are not caused by damaged hardware, but by a mismatch between the drive parameters and the actual motor. For example, the drive may be a JSDAP-15A, but the connected motor may have a different encoder type, rated current, or power class. If Cn030 is set for another motor combination, the drive’s understanding of motor electrical angle, rated current, and feedback resolution will be wrong. The result may be vibration, abnormal movement, or overcurrent immediately after operation.

Parameter mismatch is common in the following situations:

The drive has been replaced, but the original parameters were not imported.

The drive was repaired and reset to default parameters.

A used drive was installed as a substitute, with similar appearance but wrong parameter settings.

The motor was replaced, but the old drive parameters were retained.

Only part of the motion parameters was restored, while the motor-series parameter was ignored.

Different JSDAP capacity ranges or encoder specifications were mixed incorrectly.

Therefore, when troubleshooting RL-04, hardware measurement alone is not enough. The drive’s diagnostic item dn-08 should be checked and compared with the actual motor nameplate. If the motor model, power, speed, or encoder specification does not match the drive setting, Cn030 must be corrected before trial operation. Repeated testing under wrong parameter conditions not only fails to solve the problem, but may also expand the damage.

7. Common Cause 5: Servo Motor Failure

Servo motor failure can also trigger RL-04. Common motor faults include winding turn-to-turn short circuit, three-phase imbalance, insulation breakdown to ground, encoder internal failure, bearing seizure, rotor demagnetization, or brake mechanism failure.

Turn-to-turn short circuit is a relatively hidden fault. It may not show as a complete U/V/W short circuit. When measured with a standard multimeter, one phase resistance may only be slightly different, or the difference may not be obvious. However, once the drive outputs PWM current, the shorted turns generate abnormal current and heat, causing the drive to trip on overcurrent. Motors that have overheated, been contaminated by oil or water, or suffered insulation aging are more likely to develop this fault.

Insulation degradation to ground is also common. In machine-tool environments, coolant, oil mist, and metal powder can enter the motor connector or junction area, causing leakage to ground. Servo drives are sensitive to output-side leakage and current abnormalities. When leakage current becomes large, the drive may report 04 or another main-circuit alarm.

Motor bearing seizure should not be ignored either. If the motor shaft feels tight, has periodic sticking points, produces abnormal noise, or feels as though it is scraping internally, the bearing, brake, or internal mechanical structure may be damaged. A motor with a brake cannot be rotated normally unless the brake is released, so the brake-release condition must be confirmed before judgment.

For the motor itself, the most effective method is still cross-substitution. If a same-model normal motor is available, install the original motor on a known-good axis, or connect a known-good motor to the faulty drive. If the fault follows the motor, the motor or encoder is confirmed as the likely cause. If the fault remains with the original drive or original machine axis, continue checking the drive, cable, and mechanical load.

8. Common Cause 6: Drive Power Module or Current Detection Circuit Failure

If the motor, cable, encoder, parameters, and mechanical load have all been excluded, the drive itself must be considered. The power module inside the JSDAP servo drive converts the DC bus voltage into three-phase output current for the servo motor. If the IGBT/IPM module is aged, partially shorted, or if the gate drive circuit or current detection circuit is abnormal, alarm 04 may appear during operation.

Drive hardware failure often appears in the following ways:

The drive reports 04 even when the motor is disconnected.

Any connected motor causes the same 04 alarm.

The drive runs briefly when cold but frequently reports 04 after warming up.

The output three-phase current is obviously unbalanced.

The motor produces abnormal squealing or vibration before alarm.

There is a burnt smell, visible explosion mark, heavy oil contamination, or dust accumulation inside the drive.

The power module shows abnormal readings in diode-mode testing.

After power-off and full discharge, an experienced technician may perform a preliminary diode-mode check between U/V/W and the DC bus points. However, this type of inspection must be done by qualified personnel. A servo drive contains high-voltage capacitors, and dangerous voltage may remain after power is turned off. Touching internal circuits before the charge indicator is off is unsafe.

If the drive power module is confirmed to be damaged, parameter reset or external cable replacement will not solve the problem. The drive must be inspected internally, including the IPM/IGBT, gate drive optocouplers, current sensors, DC bus capacitors, snubber circuit, power supply board, and control board. For old machine tools, the external motor and cables should also be checked for the original cause. Otherwise, the repaired drive may fail again after installation.

9. Correct On-Site Troubleshooting Sequence

For alarms like RL-04, the diagnostic sequence is very important. If the drive is removed and repaired immediately, time may be wasted. If the mechanical system is jammed and the operator repeatedly resets and retries the machine, the drive power module may be damaged. A reasonable diagnostic procedure is as follows.

First, confirm the true alarm source. CNC screen messages such as “clamping axis not returned to home,” “servo abnormal,” or “axis not ready” are often system interlock messages, not necessarily the root cause. A clear photo of the servo drive display must be taken to confirm whether the alarm is 04, AL-04, or RL-04.

Second, observe the alarm timing. If the alarm appears immediately after power-on, suspect the drive body, main-circuit short circuit, or serious wiring error first. If it appears after servo enable, focus on motor wiring, encoder wiring, and parameters. If it appears only at a fixed mechanical position, mechanical jamming, limit status, clamping mechanism, and program sequence become more suspicious.

Third, disconnect the mechanical load. Separate the motor from the coupling, timing belt, or reducer so the motor can truly run unloaded. If it runs normally unloaded, the mechanical side is the priority. If it still alarms unloaded, the electrical side is the priority.

Fourth, check U/V/W and encoder wiring. Confirm phase order, terminal tightness, connector condition, shielding, grounding, insulation, and possible internal cable breakage. Pay special attention to drag-chain cables and oil-contaminated connectors.

Fifth, check Cn030 and dn-08. Confirm whether the drive model, motor model, power, speed, and encoder specification match. This step is essential for second-hand machines and machines whose drives have been replaced or repaired.

Sixth, test the motor. Check three-phase resistance balance, insulation to ground, brake release, shaft rotation resistance, and encoder feedback condition.

Seventh, perform cross-substitution. Use a known-good same-model motor, cable, or drive for comparison. Cross-substitution is more reliable than guessing.

Eighth, evaluate drive hardware. If the drive reports 04 without the motor connected, or if the same alarm remains after replacing the motor and cable, the drive should enter the internal repair process.

10. Analysis of the CNC “Clamping Axis Not Returned to Home” Message

On some CNC lathes or special-purpose machines, the servo axis may not be a standard X/Z feed axis. It may be used for a clamping axis, turret, indexing table, feeder mechanism, or auxiliary homing mechanism. When the CNC screen displays “clamping axis not returned to home,” this does not necessarily mean the home switch is faulty. It may mean the servo axis reported RL-04 immediately after starting during the homing process, so the PLC never received the home-complete signal.

In this situation, the fault chain should be divided into two layers.

The lower-level fault is the servo drive 04 overcurrent alarm.
The upper-level fault is the CNC/PLC message caused by the servo axis failing to complete the required motion.

If only the upper-level alarm is handled, such as replacing the home switch, changing the PLC input, or forcing home completion, the real problem may remain. The correct method is to make the servo axis run stably first, then handle the homing logic. For clamping, unclamping, turret positioning, and similar mechanisms, pneumatic or hydraulic signals are often required before servo movement. If the unclamp signal is not complete and the servo axis is forced to move, the motor is effectively starting against a mechanical lock, so overcurrent is a reasonable result.

For JSDAP servo alarms on clamping-axis or turret mechanisms, the following items should be checked at the same time:

Whether the unclamping solenoid valve operates.

Whether air pressure or hydraulic pressure meets the required level.

Whether the clamped and unclamped position switches provide correct feedback.

Whether the mechanical lock pin has fully retracted.

Whether the homing direction is correct.

Whether the servo enable sequence occurs after unclamping is completed.

Whether an abnormal PLC input causes the servo to start under the wrong condition.

11. Maintenance Precautions

When dealing with RL-04, frequent reset and forced operation are not recommended. Every overcurrent trip stresses the power module, motor winding, and DC bus capacitors. If the actual fault is U/V/W short circuit, unreleased brake, or mechanical jamming, repeated trial operation can turn a repairable minor fault into a damaged power module.

U/V/W should also not be swapped casually to “test direction.” In a servo system, direction should be corrected through parameters, command settings, or proper motor matching, not by randomly swapping output phases like an induction motor. Incorrect phase sequence may cause closed-loop runaway and instantaneous current shock.

Encoder wiring must not be modified randomly either. Encoder feedback is a low-voltage high-speed signal. It should use proper shielded cable and be routed away from power wiring. Shield grounding should follow the original design. Multiple random grounding points can create interference loops. If the encoder cable has been soaked in oil or repeatedly bent in the drag chain, replacing the cable is often more effective than merely cleaning the connector.

For old machine tools, the cabinet environment also matters. Oil mist, metal dust, poor heat dissipation, fan failure, poor grounding, supply voltage fluctuation, and strong electrical interference can all reduce servo system stability. The drive should be installed in an environment with proper ventilation, limited dust and oil mist, reliable grounding, and sufficient heat dissipation.

12. Conclusion

The TECO JSDAP servo drive RL-04 or 04 alarm is essentially a drive overcurrent protection. It may be caused by a damaged drive power module, but in machine-tool field service, more common causes include abnormal U/V/W motor power wiring, encoder feedback problems, mechanical jamming, unreleased brake, clamping mechanism not open, or mismatch between parameter Cn030 and the actual motor.

For the symptom “the servo motor only moves briefly and then reports RL-04, while it should normally rotate two turns,” the most important diagnostic method is to disconnect the motor from the mechanical load and perform a true no-load test. If the motor runs normally after being disconnected, focus on the mechanical lock, brake, reducer, turret, or clamping-axis mechanism. If it still reports 04 when disconnected, focus on U/V/W wiring, encoder cable, motor body, Cn030/dn-08 matching, and drive hardware.

When repairing this type of fault, do not rely only on the CNC screen message, and do not immediately assume the drive is damaged. The correct procedure is: confirm the alarm source, observe the alarm timing, disconnect the mechanical load, check power wiring, check encoder feedback, verify parameters, test the motor, perform cross-substitution, and then repair the drive if necessary. This sequence reduces misjudgment, lowers unnecessary replacement cost, and prevents repeated trial operation from expanding the fault.

In actual machine-tool maintenance, RL-04 is not an isolated alarm. It is the protective result of interaction among the servo drive, motor, cable, mechanical structure, and PLC sequence. Only by analyzing it as a complete system can the real cause be found.