-
Controller displays ERR25 motor drive fault, motor fails to start. How to fix?
Background / Cause:
Abnormality occurs in motor power drive circuit. Mainly caused by short circuit, internal drive module burnout or motor short circuit.
Solutions:
1.Cut off power immediately, stop repeated power-on attempts.
2.Check if motor coil has short circuit or leakage to ground.
3.Inspect motor wiring for short circuit and wrong connection.
4.If wiring and motor are normal, replace the faulty controller main board.
Notes:
This is serious hardware failure, forced operation will cause more severe damage.
-
Controller displays ERR29 absolute encoder reset fault, unable to reset position normally. How to solve?
Background / Cause:
Failed to complete reset initialization of absolute encoder. Mainly due to abnormal encoder data, wiring instability or position deviation.
Solutions:
1.Power off and restart the device to perform automatic reset again.
2.Re-plug the encoder cable to ensure firm connection without loose pins.
3.Re-do full stroke travel learning after confirming wiring is normal.
4.If reset keeps failing, replace the absolute encoder.
Notes:
This fault will lead to inaccurate door position judgment.
-
Controller displays ERR40 external emergency stop fault, equipment locked and unable to run. How to resolve?
Background / Cause:
External emergency stop switch is triggered or emergency stop circuit is disconnected, cutting off operation permission.
Solutions:
1.Check if physical emergency stop button is pressed down, reset it manually.
2.Inspect emergency stop signal wiring for breakage or loose connection.
3.Confirm emergency stop terminal is normally closed and in good contact.
4.Restore circuit connection, then power restart to cancel fault lock.
Notes:
Emergency stop is safety protection function, do not short-circuit it randomly.
-
Controller prompts ERR27 system overheating and stops working. How to troubleshoot?
Background / Cause:
Internal main control board temperature exceeds safe range, triggered overheat protection. Caused by poor heat dissipation, long-time continuous operation or high ambient temperature.
Solutions:
1.Cut off power supply and let the controller fully cool down.
2.Improve ventilation and heat dissipation around the control box.
3.Avoid frequent opening and closing and long-time continuous running.
4.Check for overload operation leading to rapid temperature rise.
Notes:
Long-term overheating will accelerate aging and damage internal electronic components.
-
Controller reports ERR11 Limit Signal Fault, door stops. How to resolve?
Background / Cause:
No correct limit signal detected. Usually caused by loose limit wiring, damaged limit switch, or incorrect limit parameters.
Solutions:
1.Check limit wiringInspect all open/close limit cables and terminals for looseness, damage or poor contact.
2.Test limit switchesManually trigger each limit switch and confirm the controller receives the signal. Replace faulty switches.
3.Verify limit parametersCheck that limit type and logic (NO/NC) are set correctly in the controller.
4.Replace controller if neededIf wiring and switches are normal, the controller’s input circuit may be damaged.
Notes:
• Incorrect NO/NC setting is a common reason for this fault.
• Ensure limit switches are properly aligned and not stuck.
-
Controller shows ERR15 Communication Fault, door does not run. How to resolve?
Background / Cause:
Communication failure between controller and motor drive board. Caused by loose/damaged motor signal wires (B1/B2), external short circuit, or motor driver board failure.
Solutions:
1.Check motor signal wiringInspect B1/B2 wires between controller and motor for looseness, damage or abrasion.
2.Measure communication voltageCheck voltage between B1-B3 and B2-B3 to confirm normal communication.
3.Disconnect external devicesRemove all external sensors/accessories to eliminate short circuit interference.
4.Replace motor driver boardIf wiring and voltage are normal, the motor driver board is faulty and needs replacement.
Notes:
• This fault points to motorside communication, different from ERR10.
• Do not run the motor repeatedly when this fault occurs.
-
Controller reports ERR17 Brake Release Fault, motor fails to start. How to resolve?
Background / Cause:
Brake does not release when the motor runs. Caused by brake mechanism failure, loose wiring, damaged brake coil, or driver board fault.
Solutions:
1.Check brake wiringInspect brake terminals and wires for looseness, damage or poor contact.
2.Verify brake operation in Jog modeRun in Jog mode and listen for the brake release click; no sound means release failure.
3.Manually release the brakeUse the manual release lever to check if the brake mechanism moves freely.
4.Replace faulty partsIf wiring and mechanism are normal, replace the brake assembly or motor driver board.
Notes:
• Running with unreleased brake will burn the motor quickly.
• Power off before checking brake wiring.
-
Controller shows ERR10 Communication Fault, door cannot run. How to fix?
Background / Cause:
Communication failure between controller and motor/encoder. Caused by loose/damaged cable, bad contact, mismatched communication parameters or controller hardware fault.
Solutions:
1.Check communication wiringInspect the communication cable (motor signal wire/encoder cable). Ensure connectors are tight, no broken wires or loose pins.
2.Verify communication parametersCheck baud rate, address and protocol settings. Confirm they match between controller and motor.
3.Avoid electromagnetic interferenceSeparate communication cables from highvoltage motor power cables. Do not bundle them together.
4.Test componentsIf wiring and parameters are normal, replace communication cable or controller to confirm fault.
Notes:
• Poor wiring contact is the most common cause.
•Always power off before checking cables.