6-4 Troubleshooting MN1941WEN
6.2.4 Communication
If the problem is not listed below please contact technical support.
Status LED is off:
Check that the 24 V DC control circuit supply is connected correctly to connector X1 and
is switched on.
Mint WorkBench fails to detect the detect NextMove e100:
Ensure that the NextMove e100 is powered and the Status LED is illuminated (see
section 6.2).
Check that the Ethernet or USB cable is connected between the PC and
NextMove e100.
For serial connections, check that the serial cable is wired correctly and properly
connected. Check that no other application, for example a mouse driver or other serial
device is attempting to use the same serial port. If the “Only scan COMx” option is
selected in Mint WorkBench, check that the correct COM port is selected. Check that the
selected baud rate is supported by the PC and NextMove e100.
For USB connections, check that the cable is properly connected. Check the USB
connector socket pins for damage or sticking. Check that the USB device driver has
been installed; a ‘USB Motion Controller’ device should be listed in Windows Device
Manager.
For Ethernet connections, check that the node ID is not set to 240 (hex F0). Check that
the PC’s Ethernet port has been correctly configured for TCP/IP operation (see section
5.1.7).
In the “Search up to Nodexx“ option in Mint WorkBench’s Select Controller dialog, check
that the NextMove e100’s node ID for the bus is not higher than this value, or search up
to a greater node ID.
Cannot communicate with the controller:
Verify that Mint WorkBench is loaded and that NextMove e100 is the currently selected
controller.
Cannot communicate with the controller after downloading firmware:
After firmware download, always power cycle the controller (remove 24 V power and
then reconnect).
6.2.5 Motor control
Controller appears to be working but will not cause motor to turn:
Check that the connections between motor and drive are correct. Use Mint WorkBench
to perform the basic system tests (see section 5.6 or 5.5).
Confirm that the drive enable output has been configured (see section 5.4.5).
Ensure that while the NextMove e100 is not in error the drive is enabled and working.
When the NextMove e100 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).
(Local servo outputs only) Check that the servo loop gains are setup correctly - check the
Fine-tuning window. See sections 5.6.2 to 5.9.
Motor runs uncontrollably when controller is switched on:
Verify that the NextMove e100 and drive are correctly grounded to a common ground.
(Local servo outputs only) Check that the correct encoder feedback signal is connected
to the encoder input, the encoder has power (if required, see sections 4.4.1 and 7.1.8)
and is functioning correctly.
Check that the drive is connected correctly to the NextMove e100 and that with zero
demand there is 0 V at the drive’s demand input. See section 5.6.1.