Baldor MicroFlex e100, Installation Manual

Page: 115 / 172

www.baldormotion.com
Troubleshooting 7-7 MN1942
The MicroFlex
e
100 should recover from the ‘passive’ state once the problem has been rectified
(this may take several seconds).
The CANopen bus is ‘off’:
This means that the internal CAN controller in the MicroFlex
e
100 has experienced a fatal
number of Tx and/or Rx errors, greater than the off threshold of 255. At this point the node will
have switched itself to a state whereby it cannot influence the bus. Check:
H
12-24 V is being applied between pin 9 (+24 V) and pin 6 or 3 (0 V) of the CAN connector, to
power the opto-isolators.
H
There is at least one other CANopen node in the network.
H
The network is terminated
only
at the ends, not at intermediate nodes.
H
All nodes on the network are running at the same baud rate.
H
All nodes have been assigned a unique node ID.
H
The integrity of the CAN cables.
To recover from the ‘off’ state, the source of the errors must be removed and bus then reset. This
can be done using the Mint
BUSRESET keyword, or by resetting the MicroFlex
e
100.
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. MicroFlex
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.