Specifications

www.baldormotion.com
4-24 Input / Output MN1941
4.6 Ethernet in terface
The Ethernet interface provides TCP/IP and ETHERNET Powerlink networking capabilities.
4.6.1 TCP/IP
Transmission Control Protocol / Internet Protocol (TCP/IP) is a common set of protocols used to
transfer information between devices over a network, including the internet. TCP enables two
devices to establish a connection, and guarantees the delivery of packets (datagrams) of
information in the correct order. IP specifies the format of the individual packets (which includes
the destination address of the receiving device) but has no influence on whether the packet is
delivered correctly.
TCP/IP allows the NextMove e100 to support standard Ethernet communication with a host PC
running Mint WorkBench. The connection uses Baldor’s high level ICM (Immediate Command
Mode) protocol to allow Mint commands, Mint programs and even firmware to be sent to the
controller over the Ethernet network.
When operating in standard Ethernet mode, TCP/IP cannot be used to communicate with a
controller on a daisy-chained network. This is due to cumulative timing errors caused by each
controller’s internal hub. It is necessary to connect the host PC to the controller either directly or
via a single hub, as shown in Figure 26:
Host PC
External hub
MicroFlex e100 drivesNextMove e100
Figure 26 - Connecting to controllers using TCP/IP in standard Ethernet mode
When operating in EPL mode, in conjunction with an EPL compatible router, the host PC can use
TCP/IP to communicate with controllers on a daisy-chained network. In this situation, the router
will use TCP/IP only within EPL’s asynchronous time slots. See the Mint help file for further
details.
Host PC
ETHERNET Powerlink
compatible router
NextMove e100 MicroFlex e100 drives
Figure 27 - Connecting to daisy-chained controllers using TCP/IP and EPL mode