Table of Contents
Advertisement
Appendix C
Connect to Networks via Ethernet Interface
EtherNet/IP Connections
102
The ArmorBlock module contains two 10/100Base-T, M12-D (4-pin)
IMPORTANT
Ethernet connectors which connect to standard Ethernet hubs or
switches via RJ-45 (8-pin) twisted-pair straight-through cable. It can also
connect to another ArmorBlock module via a four wire twisted pair
straight-through or cross-over cable. To access other Ethernet mediums,
use 10/100Base-T media converters or Ethernet hubs or switches that
can be connected together via fiber, thin-wire, or thick-wire coaxial
cables, or any other physical media commercially available with Ethernet
hubs or switches.
Connecting to an Ethernet Network
The ArmorBlock module supports the following Ethernet settings:
•
10 Mbps half duplex or full duplex
•
100 Mbps half duplex or full duplex
Mode selection can be automatic, based on the IEEE 802.3 auto negotiation
protocol. In most cases, using the auto negotiation function results in proper
operation between a switch port and the ArmorBlock module.
With Studio 5000 Logix Designer software version 18 or later, you can
manually set the communication rate and duplex mode of an Ethernet port
you have connected to the switch port. The settings of the Ethernet port and
the switch port must match.
Cables
Shielded and non-shielded twisted-pair 10/100Base-T cables with D-coded M12
connectors are supported. The maximum cable length (without repeaters or
fiber) is 100 m (323 ft). However, in an industrial application, cable length
should be kept to a minimum.
TCP/IP is the mechanism used to transport Ethernet messages. On top of TCP,
the EtherNet/IP protocol is required to establish sessions and to send MSG
commands. Connections can be initiated by either a client program (RSLinx
software) or a processor.
The client program or processor must first establish a connection to the
ArmorBlock module to enable the ArmorBlock module to receive solicited
messages from a client program or processor.
In order to exchange I/O data with another device on Ethernet, that device
must first originate a connection with the ArmorBlock via TCP/IP. Once an I/O
connection is established via TCP/IP the I/O data is exchanged via UDP/IP.
Rockwell Automation Publication 1732E-UM003D-EN-E - November 2021
Advertisement
Table of Contents
