Baldor NXE100-1608Dx, Installation Manual

Page: 97 / 114

www.baldormotion.com
Troubleshooting 6-7 MN1941
The Manager node cannot scan/recognize a node on the network using the Mint
NODESCAN keyword:
Assuming that the network is working correctly (see previous symptoms) and the bus is in an
‘Operational’ state, check:
H
Only nodes that conform to DS401, DS403 and other Baldor CANopen nodes are
recognized by the Mint
NODESCAN
keyword. Other types of node will be identified with a type
“unknown” (255) when using the Mint
NODETYPE
keyword.
H
Check that the node in question has been assigned a unique node ID.
H
The node must support the node guarding process. NextMove e 100 does not support the
Heartbeat process.
H
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.
The node has been successfully scanned / recognized by the Manager node, but
communication is still not possible:
For communication to be allowed, a connection must be made to a node after it has been
scanned:
H
Baldor controller nodes are automatically connected to after being scanned.
H
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.