Filter
Top Products
7-4 Troubleshooting MN1928
7.2.3 Communication
If the problem is not listed below please contact Baldor technical support.
Symptom
Check
Cannot detect NextMove ES Check that the NextMove ES is powered.
For serial connections, check that the serial cable is wired
correctly and properly connected. Check that no other
application on the PC is attempting to use the same serial
port.
For USB connections, check that the cable is properly
connected. Check that the USB device driver has been
installed.
Cannot communicate with
the controller.
Verify that WorkBench v5 is loaded and that NextMove ES is
the currently selected controller .
Check that the NextMove ES card is correctly connected to
the backplane.
7.2.4 Motor control
Symptom Check
Controller appears to be
working but will not cause
motor to turn.
Check that the connections between motor and drive are
correct. Use WorkBench v5 to perform the basic system
tests (see section 6.5 or 6.4).
Confirm that the drive enable output has been configured
(see section 6.3.2).
Ensure that while the NextMove ES is not in error the drive
is enabled and working. When the NextMove ES is first
powered up the drive should be disabled if there is no
program running (there is often an LED on the front of the
drive to indicate status).
(Servo outputs only) Check that the servo loop gains are
setup correctly - check the Fine-tuning window. See
sections 6.5.2 to 6.7.
Motor runs uncontrollably
when controller is switched
on.
Verify that the backplane (if used) and drive are correctly
grounded to a common earth point.
(Servo outputs only) Check that the correct encoder
feedback signal is connected to the encoder input, the
encoder has power (if required, see section 5.2.11) and is
functioning correctly.
Check that the drive is connected correctly to the
NextMove ES and that with zero demand there is 0V at the
drive’s demand input. See section 6.5.1.