Hope65 VFD Motor Not Running | Step-by-Step Troubleshooting Guide

Hope65 Series Smart AC Drive / VFD Motor Not Running: Step-by-Step Troubleshooting

Slanvert Hope65 Series | Smidnya Technical Troubleshooting Guide
```

Hope65 Series Smart AC Drive / VFD Motor Not Running

Step-by-step diagnosis for cases where the Hope65 display is ON, but the motor does not rotate, does not respond to RUN, stays at 0 Hz, or does not start from external terminals.

F0-21
Command source
F0-02
Frequency source
F1-02
Start frequency
Motor Not Running Diagnosis
Display ON



0.00 Hz?
Check command + speed source
KeypadTerminals
AnalogRS485
Use this guide before replacing the drive or motor.
```

Quick Answer

```

If a Hope65 Series Smart AC Drive / VFD display is ON but the motor is not running, first check whether the drive has an active fault, whether the RUN command is coming from the correct command source, and whether the selected frequency source is giving a frequency above 0 Hz.

For the first test, set the drive to keypad command, select digital frequency setting, set a low frequency such as 5 Hz to 10 Hz, and press RUN. If the motor runs from keypad, the drive and motor are basically functional and the issue is usually external wiring, terminal logic, analog reference, PLC/RS485 command, or parameter configuration.

Stop troubleshooting and contact technical support if there is smoke, burning smell, visible damage, repeated fault after reset, incorrect supply voltage, suspected short circuit, unsafe wiring, or uncertainty about electrical measurements.

```

Safety Warning Before Troubleshooting

```

Only trained and qualified electrical personnel should inspect wiring, terminals, motor cables, braking resistor wiring, or panel components.

Before touching wiring or terminals, switch off all input power, wait at least 10 minutes, and confirm that the DC bus voltage has discharged to a safe level. Do not change wiring while power is ON.

```

1. What This Article Solves

This article helps diagnose a Hope65 Series Smart AC Drive / VFD when the motor does not rotate or does not respond correctly to RUN commands. The issue may be caused by power wiring, motor wiring, command source mismatch, frequency source mismatch, start frequency settings, terminal input logic, external stop/fault input, analog signal loss, RS485 command settings, motor overload, or mechanical blockage.

The purpose is to separate the problem into two categories: drive/motor side problem and control-command problem. The fastest method is to test the motor from keypad at a low frequency. If keypad operation works, the issue is normally outside the drive power stage and should be checked in the command source, terminal wiring, analog input, communication settings, or external logic.

``` ```
01

Check Status

Confirm display, fault status, RUN indication, frequency display, output current, and keypad response.

02

Test Keypad

Run at 5–10 Hz from keypad to prove the drive, motor cable, motor, and load basics.

03

Check Control

If keypad works, check terminal logic, analog input, PLC command, RS485 command, and protection inputs.

2. Applies To

Product SeriesSlanvert Hope65 Series Smart AC Drive / VFD
Typical SymptomDisplay ON but motor not rotating, keypad RUN not working, terminal start not working, output frequency remains 0 Hz, motor hums but does not rotate, or motor starts only in jog/keypad mode.
Control Methods CoveredKeypad, terminal start/stop, analog input, potentiometer, PLC control, RS485 / Modbus command, and jog operation.
User LevelQualified electrical technician, maintenance engineer, panel builder, machine integrator, or automation engineer.

3. Motor Not Running Diagnostic Flow

Use this workflow to identify whether the problem is caused by the VFD, motor, wiring, parameter settings, or external control logic.

```

Fast Diagnosis Workflow

01
Display ON?
  • Check input supply
  • Check keypad display
  • Check fault code
02
Fault Active?
  • Read fault code
  • Reset only after cause is checked
  • Do not repeatedly reset
03
Keypad Test
  • F0-21 keypad
  • F0-02 digital
  • F0-01 5–10 Hz
04
No Keypad Run?
  • Check start frequency
  • Check motor/load jam
  • Check U/V/W wiring
05
Keypad Works?
  • Drive/motor likely OK
  • Check terminal logic
  • Check AI / RS485
Diagnostic Rule:

If the motor runs from keypad but not from external control, the likely cause is command source, frequency source, digital input wiring, analog reference, PLC/RS485 command, or terminal active logic.

```

4. Identify the Exact Symptom First

“Motor not running” can mean several different conditions. Select the closest symptom before changing parameters.

SymptomMost Likely AreaFirst Check
Display is OFFInput power / supply wiring / internal damageMeasure input voltage at L1/L2 or R/S/T and verify model voltage class.
Display is ON but RUN key does nothingCommand source mismatchCheck F0-21 command source selection.
RUN indication appears but frequency stays 0 HzFrequency source / frequency command / lower limit / start frequency issueCheck F0-02, F0-01, F1-02, and selected frequency reference.
Frequency rises but motor does not rotateMotor wiring, motor fault, load jam, mechanical brake, weak torqueCheck U/V/W wiring, motor shaft, brake release, output current, and motor nameplate settings.
Motor runs from keypad but not from terminalTerminal command logic / DI wiring / NPN-PNP source-sink setupCheck F0-21, F6 input settings, terminal command mode, DI active mode, and 24V/COM wiring.
Motor runs from keypad but not from analog speed referenceAI wiring / jumper / frequency source / scalingCheck F0-02, AI jumper, 0–10 V or 4–20 mA signal, GND reference, and AI curve.
Motor runs from keypad but not from RS485Communication command / Modbus settings / RS485 wiringCheck communication command source, slave address, baud rate, parity, A/B polarity, and master command.

5. Step 1: Check for Fault Code or Protection Status

Before changing parameters, check whether the drive is in fault state, stop state, standby state, terminal stop state, external fault state, or communication command state. If a fault is active, the motor will not run until the cause is corrected and the fault is reset.

Do not repeatedly reset faults without checking the cause. Repeated reset of overcurrent, short circuit, overload, or overvoltage faults may damage the drive, motor, or machine.
What to CheckMeaningAction
Fault code on keypadDrive is blocked by protection.Record the code, check cause, correct issue, then reset.
RUN indicatorShows whether a run command is being accepted.If no RUN status, check command source and start command path.
Set frequencyThe requested speed reference.If 0 Hz, check frequency source and speed command.
Output frequencyActual output frequency delivered by the drive.If 0 Hz while RUN is commanded, check start frequency, stop input, and frequency reference.
Output currentShows whether the motor is drawing current.If current is high and motor does not rotate, suspect mechanical jam, brake, or motor fault.

6. Step 2: Force a Controlled Keypad Test

The keypad test is the most important separation test. It removes PLC, external switches, analog reference, RS485 commands, and field wiring from the first diagnosis. Do this only when wiring and safety checks are complete.

Keypad Test Setup

```
F0-21
Command Source

Set to operation panel / keypad command for first test.

F0-02
Frequency Source

Set to digital frequency setting for controlled local speed reference.

F0-01
Preset Frequency

Set 5.00 Hz to 10.00 Hz for first motor rotation check.

```
  1. Confirm the motor is connected to U/V/W and the motor frame is grounded.
  2. Confirm the machine is safe to rotate or the motor is unloaded for testing.
  3. Set command source to keypad operation.
  4. Set frequency source to digital setting.
  5. Set a low frequency such as 5 Hz to 10 Hz.
  6. Press RUN.
  7. Observe whether the motor shaft rotates.
  8. Observe output current, sound, vibration, and any fault code.
  9. Press STOP/RST and confirm the motor stops safely.
Keypad Test ResultMeaningNext Action
Motor runs correctlyDrive, motor, output wiring, and basic motor/load condition are likely OK.Troubleshoot terminal command, analog reference, PLC, RS485, or external wiring.
Drive accepts RUN but output frequency stays 0 HzSpeed command may be zero, blocked, or below start frequency.Check F0-01, F0-02, F1-02, lower-limit behavior, and selected speed source.
Output frequency rises but motor does not rotateMotor/load/mechanical issue, motor wiring issue, or insufficient torque.Check motor cable, motor brake, load jam, output current, motor parameters, and control mode.
Drive trips immediatelyShort circuit, ground fault, overcurrent, wrong wiring, motor fault, or wrong motor/load setup possible.Record fault code and stop repeated resets. Inspect motor cable and motor insulation.

7. Step 3: Check Command Source F0-21

If the motor does not start when pressing RUN on the keypad, the drive may not be listening to the keypad. The command source determines where the RUN/STOP command is accepted from.

F0-21 SettingCommand SourceExpected Behavior
0Operation panel / keypad commandRUN/STOP from keypad should control the drive.
1Terminal commandExternal DI terminals control start/stop. Keypad RUN may not start the motor.
2Communication commandRS485 / Modbus master must send run command. Keypad RUN may not start the motor.
Practical rule: During first troubleshooting, set command source to keypad. After the motor runs successfully, return the command source to terminal or communication mode as required by the machine.

8. Step 4: Check Frequency Source F0-02

The drive can receive the speed command from digital setting, analog input, pulse input, multi-speed, PLC logic, PID, or communication. If the selected source is not giving a valid speed command, the drive may accept RUN but output 0 Hz.

Selected Frequency SourcePossible Reason for 0 HzCheck
Digital settingPreset frequency is 0 Hz or lower than start frequency.Check F0-01 and F1-02.
AI1 analog inputNo voltage/current signal, wrong jumper, wrong GND, broken shield, or wrong scaling.Measure AI signal and check 0–10 V / 4–20 mA configuration.
Pulse inputNo pulse, wrong DI terminal, or wrong pulse configuration.Check pulse input terminal and signal frequency.
Multi-speedDigital input combination selects zero or undesired speed.Check DI status and multi-speed table values.
PIDPID output is zero because feedback/setpoint logic is not satisfied.Check PID setpoint, feedback, sleep/wake settings, and process signal.
CommunicationModbus master has not written speed reference or communication is not working.Check RS485 wiring, baud rate, address, parity, and write command.

9. Step 5: Check Start Frequency F1-02

A common hidden cause of “RUN command accepted but motor does not start” is start frequency configuration. If the target frequency is lower than the start frequency, the drive can remain in standby instead of executing the start command.

Example: If F0-01 is set to 2.00 Hz but F1-02 start frequency is set to 5.00 Hz, the target frequency is lower than the start frequency. The drive may stay in standby with 0.00 Hz output. Set the test frequency higher than the start frequency.
ParameterFunctionTroubleshooting Guidance
F1-02Start frequencyFor first test, keep the target frequency above this value. Do not set test frequency lower than start frequency.
F1-03Start frequency hold timeIf set long, the drive may hold at start frequency before accelerating further.

10. Step 6: Check Power and Motor Wiring

If the drive shows output frequency but the motor does not rotate, check the output wiring, motor connection, motor brake, and load condition.

Motor-Side Wiring Overview

```
Hope65 Drive Output

U / V / W

  • Connect only to motor
  • Do not connect mains supply
  • Do not connect capacitor banks
  • Use suitable motor cable
Three-Phase Motor

Motor + Load

  • Check motor terminal box
  • Check brake release
  • Check shaft movement
  • Check load jam
+
Grounding

PE Safety Ground

  • Ground drive body
  • Ground motor frame
  • Use correct conductor size
  • Do not run without PE
```
CheckPass ConditionProblem Indication
Motor connected to U/V/WMotor cable is connected only to drive output terminals.Loose terminal, wrong connection, broken motor lead, or bypass wiring problem.
Motor shaft free to rotateShaft/load can move safely by design.Mechanical jam, locked bearing, gearbox problem, or engaged brake.
Motor brake releasedBrake receives correct release signal before motor torque is required.Motor hums or draws current but does not rotate.
Output current during RUNCurrent should be reasonable for low-speed test.Very high current with no rotation suggests jam, wrong motor data, or motor fault.

11. Step 7: If Keypad Works but Terminal Start Does Not Work

If the motor runs from keypad but not from external terminals, the VFD power stage and motor are probably functional. The problem is usually terminal command source, DI wiring, active mode, source/sink selection, two-wire/three-wire logic, or external stop/fault input.

Terminal Start Logic Overview

```
F0-21 = 1
Terminal Command

Drive listens to DI terminal start/stop logic instead of keypad RUN.

F6 Inputs
DI Function

DI1/DI2/DI3 functions must match run, direction, reset, or three-wire logic.

F6 Mode
2-Wire / 3-Wire

Terminal command mode must match switch/button wiring method.

```
Terminal ModeHow It WorksCommon Mistake
Two-wire mode 1Forward/reverse determined by DI1/DI2 command state.Both forward and reverse are active or both inactive, so the drive stops.
Two-wire mode 2DI1 is run enable; DI2 determines direction.DI1 is not active, so the drive never receives run enable.
Three-wire mode 1Enable/stop and momentary start buttons are used.Stop/enable circuit is open, so start button has no effect.
Three-wire mode 2Enable, run command, and direction selection are separated.Button wiring does not match selected terminal mode.

Terminal Start Checklist

  • Confirm keypad test works first.
  • Set command source to terminal mode only after keypad test succeeds.
  • Confirm DI terminal functions match the actual wiring.
  • Confirm whether the model uses 4 DI or 5 DI terminals.
  • Confirm active-high / active-low logic.
  • Confirm NPN/PNP or source/sink wiring method.
  • Confirm 24V and COM wiring are correct.
  • Confirm external stop, free stop, external fault, or emergency stop input is not active.
  • Check DI input status from display/monitoring parameter if available.

12. Step 8: If Analog Speed Control Does Not Work

If the motor runs from keypad but not from analog speed reference, check the analog signal wiring and frequency source. The drive must be configured to use analog input as the frequency source, and the analog input must receive a valid voltage or current signal.

CheckExpected ConditionIssue If Wrong
F0-02Frequency source set to AI1 or required analog source.Drive ignores analog signal and stays at other frequency source.
AI jumperVoltage mode for 0–10 V or current mode for 4–20 mA.Signal scaling becomes incorrect or unreadable.
AI signalMeasure valid voltage/current between AI and GND.If 0 V or 0 mA, speed command may remain 0 Hz.
Shielding and cable routeAnalog wiring should be shielded and away from motor cables.Unstable speed, random frequency change, or noise-related behavior.

13. Step 9: If RS485 / Modbus Start Does Not Work

If the motor runs from keypad but does not start from PLC, HMI, SCADA, or Modbus master, check communication settings and command source. RS485 control needs correct wiring, communication parameters, drive address, and valid command write from the master.

CheckRequired ConditionCommon Problem
Command sourceSet to communication command when PLC/HMI must start the drive.Drive is still in keypad or terminal command mode.
Frequency sourceSet to communication if PLC/HMI must send speed reference.Run command is sent but frequency remains 0 Hz.
RS485 A/B wiringA to A, B to B according to master/device convention.A/B reversed or loose terminal prevents communication.
Address / baud / parityMaster and drive settings must match.No response or illegal response from drive.
Command writeMaster must write valid run command and valid speed reference.Communication is present but command value is wrong.

14. Step 10: If Output Frequency Appears but Motor Still Does Not Rotate

If the drive output frequency increases but the motor does not rotate, the issue may be mechanical, motor-side, or torque-related. Do not continue increasing frequency until the cause is found.

ObservationLikely CauseAction
Output current high, motor not rotatingMechanical jam, brake not released, locked rotor, overloaded motorStop test. Check load, brake, shaft, gearbox, and motor condition.
Output current very low, motor not rotatingMotor not connected, open motor phase, wiring issueCheck U/V/W wiring, motor cable, and motor terminal box.
Motor hums but does not startWeak torque, wrong motor parameters, brake/load problem, single phase at motorCheck motor nameplate data, wiring, brake, and load. Test unloaded if safe.
Motor starts then tripsAcceleration too short, load too heavy, motor data wrong, overcurrent protectionIncrease acceleration time, verify motor data, check load torque.

15. Common Causes and Corrective Actions

CauseTypical SignCorrective Action
Wrong command sourceKeypad RUN does not work when drive expects terminal/communication.Set F0-21 according to required control method.
Wrong frequency sourceRUN command accepted but 0 Hz output.Set F0-02 to valid speed source and confirm reference is present.
Target frequency lower than start frequencyDrive remains standby and output frequency stays 0 Hz.Set test frequency above F1-02 start frequency.
DI terminal logic mismatchTerminal start does not work but keypad works.Check F6 terminal functions, terminal command mode, active mode, and wiring.
Analog signal missingDrive in AI mode but frequency remains 0 Hz.Measure AI signal and check voltage/current jumper.
External stop/fault activeDrive refuses start or stops immediately.Check DI functions for free stop, external stop, external fault, emergency stop, and active logic.
Mechanical brake not releasedMotor draws current or hums but shaft does not rotate.Check brake coil supply, brake contactor, brake timing, and mechanical release.
Motor/load jamHigh current or trip during start.Isolate load if safe and test motor unloaded.

16. Do Not Do These During Troubleshooting

  • Do not repeatedly reset a fault without finding the root cause.
  • Do not change wiring while the drive is powered ON.
  • Do not connect input supply to U/V/W output terminals.
  • Do not bypass the drive output directly to mains without proper mechanical interlock and approved wiring design.
  • Do not increase frequency or acceleration aggressively when the motor is not rotating.
  • Do not assume the VFD is faulty before testing keypad control at low frequency.
  • Do not use terminal, analog, or RS485 control for first diagnosis before proving keypad operation.
  • Do not run without proper PE grounding.
  • Do not ignore motor brake, load jam, gearbox, pump blockage, conveyor jam, or fan obstruction.

17. Information to Share With Technical Support

To reduce troubleshooting time, share the following information when contacting support:

  • Photo of Hope65 drive nameplate
  • Photo of motor nameplate
  • Input supply voltage measured at L1/L2 or R/S/T
  • Photo of input wiring and motor U/V/W wiring
  • Photo of control terminals if terminal start is used
  • Photo or list of changed parameters
  • F0-21 command source setting
  • F0-02 frequency source setting
  • F0-01 preset frequency setting
  • F1-02 start frequency setting
  • Whether motor runs from keypad at 5 Hz to 10 Hz
  • Fault code shown on keypad, if any
  • Application type: pump, fan, conveyor, mixer, blower, manufacturing line, etc.
  • Whether the motor has a mechanical brake
  • Whether the motor is loaded or unloaded during testing

Need Help Diagnosing a Hope65 Motor Not Running Issue?

```

Smidnya technical support can help review your wiring photos, motor nameplate, drive model, parameter settings, command method, and fault code to identify whether the issue is wiring, parameter setup, external control, motor, or load related.

Share drive model + motor nameplate + F0-21/F0-02/F1-02 settings for faster support
```
  • Hope65 Series Smart AC Drive / VFD Quick Start Guide: Wiring, Setup, and First Motor Run
  • Hope65 Series Smart AC Drive / VFD Fault Codes: Causes, Meaning, and Corrective Actions
  • Hope65 Series Smart AC Drive / VFD Standard Power Wiring Guide
  • Hope65 Series Smart AC Drive / VFD Control Terminal Wiring Guide
  • Hope65 Series Smart AC Drive / VFD RS485 Modbus Communication Setup

SEO and Zoho Desk Metadata

SEO TitleHope65 VFD Motor Not Running | Step-by-Step Troubleshooting Guide
Meta DescriptionTroubleshoot Hope65 Series Smart AC Drive / VFD motor not running issues. Covers keypad test, F0-21 command source, F0-02 frequency source, F1-02 start frequency, terminal start, analog input, RS485 Modbus, wiring, and motor/load checks.
Primary KeywordsHope65 motor not running, Hope65 VFD not starting, Hope65 RUN command not working, Hope65 terminal start not working, Hope65 keypad run, VFD motor not rotating
Zoho Desk TagsHope65, Hope65 VFD, Hope65 Smart AC Drive, motor not running, VFD not starting, RUN command, F0-21, F0-02, F1-02, terminal start, keypad run, analog input, RS485, Modbus RTU, VFD troubleshooting, command source, frequency source, motor wiring, Smidnya support
Recommended Display PermissionAll users