Baldor NextMove ESB-2 Installation Manual page 87

Symptom
The Manager node cannot
scan/recognize a node on the
network using the Mint
NODESCAN keyword.
The node has been
successfully scanned /
recognized by the Manager
node, but communication is
still not possible.
Servo Systems Co. • 115 Main Road • P.O. Box 97 • Montville, NJ,
6-8 Troubleshooting
Check
Assuming that the network is working correctly (see
previous symptoms) and the bus is in an 'Operational'
state, check the following:
Only nodes that conform to DS401, DS403 and other

Baldor CANopen nodes are supported by the Mint
NODESCAN keyword.
Check that the node in question has been assigned a

unique node ID.
The node must support the node guarding process.

NextMove ESB-2 does not support the Heartbeat
process.
Try power-cycling the node in question.

If the node in question does not conform to DS401 or
DS403 and is not a Baldor CANopen node, communication
is still possible using a set of general purpose Mint
keywords. See the Mint help file for further details.
For communication to be allowed, a connection must be
made to a node after it has been scanned.
Baldor controller nodes are automatically connected to

after being scanned.
Nodes that conform to DS401, DS403 must have the

connections made manually using the Mint CONNECT
keyword.
If a connection attempt using CONNECT fails then it may be
because the node being connected to does not support an
object which needs to be accessed in order to setup the
connection.
07045-0097 • (973) 335-1007 • Toll Free: (800) 922-1103
Fax: (973) 335-1661 • www.servosystems.com
www.baldormotion.com
MN1957