supporting Sequence of Events
Table Of Contents
- 1732E-UM002A-EN-E 1732E EtherNet/IP ArmorBlock Supporting Sequence of Events User Manual
- Important User Information
- Table of Contents
- Preface
- Chapter 1 - About 1732E ArmorBlock Modules
- Chapter 2 - Module Overview
- Chapter 3 - Use the Module in an ArmorBlock System
- Chapter 4 - Install Your Module
- Chapter 5 - Configure the Module for Your EtherNet/IP Network
- Chapter 6 - Configure the Module Using RSLogix 5000
- Introduction
- Set Up the Hardware
- Create the Example Application
- Configure Your I/O Module
- Overview of the Configuration Process
- Add a New Bridge and Module to Your RSLogix 5000 Project
- Use the Default Configuration
- Change the Default Configuration
- Download Your Configuration
- Edit Your Configuration
- Access Module Data in RSLogix 5000
- Configure RSLogix 5000 and the 1756-EN2T Communication Module for CIP Sync
- Chapter Summary and What’s Next
- Chapter 7 - Module Features
- Introduction
- Determine Module Compatibility
- Module Features That Can Be Configured
- Chapter Summary and What’s Next
- Chapter 8 - Using the Module
- Chapter 9 - Interpret Status Indicators
- Chapter 10 - Troubleshoot the Module
- Appendix A - ArmorBlock 2 Port Ethernet Module Specifications
- Appendix B - Module Tags
- Appendix C - 1732E EtherNet/IP ArmorBlock Supporting Sequence of Events Data Tables
- Appendix D - Connect to Networks via Ethernet Interface
- Appendix E - 1732E ArmorBlock I/O Embedded Web Server
- Glossary
- Index
- How Are We Doing?
- Back Cover
Publication 1732E-UM002A-EN-P - March 2010
Connect to Networks via Ethernet Interface 91
Ethernet Connections
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 application) 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
IO connection is established via TCP/IP the IO data is exchanged via
UDP/IP.
Duplicate IP address
Detection
The ArmorBlock module firmware supports duplicate IP address detection.
When you change the IP address or connect one of the modules to an
EtherNet/IP network, the module checks to make sure that the IP address
assigned to this device does not match the address of any other network
device. The module will periodically check for a duplicate IP address on the
network. If the module determines that there is a conflict (another device on
the network with a matching IP address), the Network Status Indicator
becomes solid red.
To correct this conflict, the IP address of one of the modules will need to
changed. If you decide to change the IP address of the ArmorBlock then,
assign a unique IP address to the module then cycle power to the module.
If you decide to change the IP address of the other module, remove the device
with the incorrect IP address or correct its conflict. To get the ArmorBlock
out of conflict mode, cycle power to the module or disconnect its Ethernet
cables and reconnect the cables. If you choose to disconnect the Ethernet
cables to correct this conflict you will need to disconnect both Ethernet cables
from two port Ethernet modules at the same time.
Configure Ethernet
Communications on the
ArmorBlock module
There are five ways to configure ArmorBlock module Ethernet
communications.
• via a DHCP request at module powerup
• manually setting the configuration parameters using RSLogix 5000
software
• manually setting the configuration parameters using RSLinx software
• manually configuring the network settings using the embedded web
server