Rockwell Automation 700-1384-01, User Manual, Page: 62 / 344

Design Guidelines
Transport System Layout
62 MagneMotion
Rockwell Automation Publication MMI-UM007F-EN-P - September 2020
Node Controllers
Once all paths and nodes have been identified on the QSHT transport system layout, the node
controllers and their connections to the motors at the nodes must be defined. This definition
typically includes identifying the type of node controllers being used (the example in
Figure 3-4 shows an NC-12 node controller with RS-422 motor communication being used).
Node controllers coordinate all motor operations and communicate with the high-level con-
troller (HLC). In QSHT transport systems, one node controller is designated as the HLC. The
HLC manages the communication between all node controllers in the transport system and the
host controller. The node controller types that the QSHT transport system supports are:
• NC-S Node Controller – Node controller with one active network port and eight
RS-422 ports. This node controller can support multiple nodes (for example, Merge,
Diverge, and Relay).
• NC-E Node Controller – Node controller with one active network port, four digital
inputs, and four digital outputs. This node controller can support multiple nodes (for
example, Merge, Diverge, and Relay) and additional functions (for example, E-stop
and interlocks).
• NC-12 Node Controller – Node controller with one network port, 12 RS-422 ports,
two RS-232 ports, 16 digital inputs, and 16 digital outputs. This node controller can
support multiple nodes (for example, Merge, Diverge, and Relay) and additional func-
tions (for example, E-stop and interlocks).
• NC LITE Node Controller – Node controller with one network port and four RS-422
ports. This node controller typically supports one node (for example, Merge). How-
ever, some configurations of nodes allow the node controller to support multiple nodes
(for example, Simple and Relay).
Motor Communications – Identifies the communication connections between each motor
and motor drive. Also identifies the connections between the motor drives for motors on the
same path, and between motor drives at path ends and the node controllers.
NOTE: All motor drive connections at a node must be made to the same node controller.