Difference between revisions of "Motor not moving troubleshooting"

Revision as of 20:27, 21 April 2014

This article lists common reasons for motor not producing desired motion when using GD motor drives.

The suggested actions are described for drives supporting Granity software. Hoever similar instructions apply to older GDtool based drives too.

List of reasons

Fault state of drive

Drive suspends all motor control until fault is cleared. If fault occurs again, check parameterization of drive or try adjusting fault tolerance limits to higher. If no stability can be achieved, pay attention to correctness of motor parameters MPC, FBR, FBI and FBH. In many cases counting direction of encoder is opposite of assumed, so inverting FBI setting may be needed. All of these settings safe to experiment if motor is shaft unmounted.

Incorrect motor settings

Double check all motor parameters especially on Machine tab of Granity. Also see the previous paragraph ↑↑.

No setpoint signal

Try moving motor by giving commands Granity's Set Abs and Set Inc buttons.

Output current is insufficient to overcome load friction or weight

Try increasing motor current limits or try motor without any load

No current flow on motor

Verify that current really flows through motor by doing response tests at Granity Testing page. Tick Torque setpoint & achieved signals to see the target current and actual current of motor. Both curves should stay together. If Torque achieved lags behind, it is sign of insuffucient supply voltage to overcome motor coil resistance or EMF. One possibility is also activation of STO that forces drive power stage off.

Motor initialization has failed

If Hall sensonrs (FBH) are not used, then drive may fail to initialize motor properly under significant mechanical load or due to weight of vertical axis. Try increasing current limits or connecting Hall sensors (if motor is equipped with them).