Specifications and Site Requirements
Communication
230 MagneMotion
Rockwell Automation Publication MMI-UM002F-EN-P - October 2022
connected. If a fifth connection to the status TCP/IP port is attempted, it causes the first status
connection to be disconnected.
The TCP/IP connection to all node controllers uses standard Ethernet network wiring. If mul-
tiple node controllers are connected to the same network, the IP address of each additional
node controller must be changed to a unique address to avoid IP conflicts. The TCP/IP address
that is used on the node controllers must be configured as specified in the Node Controller
Interface User Manual, MMI-UM001.
TCP/IP Communication – Node Controller to Motor
When using motors that support Ethernet communication, the NC-S, NC-E, NC-12, and NC
LITE node controllers are connected to the motors and switches in a network using standard
Cat 5 cable. The motors can use different network style connection schemes depending on the
application (see Ethernet Motor Communication Recommendations on page 90).
When using Ethernet, all motors in a specific path must be connected to the same node con-
troller (see Figure 3-10 on page 91 through Figure 3-21 on page 95). Additionally, multiple
paths can be connected to the node controller using the same Ethernet chain. See Figure 4-57
and Figure 4-59 for the locations of these connections on the motors and switches. See the
Node Controller Hardware Manual, MMI-UM013, for the locations of these connections on
the node controllers.
TCP/IP Communication – Motor to Motor
When using motors that support Ethernet communication, the motors are connected to each
other or the network, depending on the connection scheme being used (see Ethernet Motor
Connection Examples on page 91), using standard Cat 5 cable. If multiple motors are con-
nected to the same network, the IP address of each motor must be unique to avoid IP conflicts.
The TCP/IP address that is used on the motors must be configured as specified in Ethernet
Motor Communication Recommendations on page 90.
EtherNet/IP Communication – Host Controller to HLC
EtherNet/IP communication is supported for use when the host controller uses UDP-based
implicit messaging. EtherNet/IP communication allows the host controller to communicate
with the HLC as described in the Host Controller EtherNet/IP Communication Protocol User
Manual, MMI-UM004.
The connection from the host controller to the node controller that is configured as the HLC
uses standard Ethernet network wiring. The EtherNet/IP address that is used on the node con-
troller that is configured as the HLC must be configured as specified in the Node Controller
Interface User Manual, MMI-UM001.