Net Eni

MicroLogix Ethernet Interface
1761-NET-ENI and 1761-NET-ENIW
User Manual
Important User Information
Solid state equipment has operational characteristics differing from those of electromechanical equipment. Safety Guidelines for the Application, Installation and Maintenance of Solid State Controls (Publication SGI-1.1 available from your local Rockwell Automation sales office or online at http://www.ab.com/manuals/gi) describes some important differences between solid state equipment and hard-wired electromechanical devices. Because of this difference, and also because of the wide variety of uses for solid state equipment, all persons responsible for applying this equipment must satisfy themselves that each intended application of this equipment is acceptable. In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment. The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and requirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for actual use based on the examples and diagrams. No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software described in this manual. Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation, Inc. is prohibited. Throughout this manual we use notes to make you aware of safety considerations.
WARNING
Identifies information about practices or circumstances that can cause an explosion in a hazardous environment, which may lead to personal injury or death, property damage, or economic loss.
IMPORTANT
Identifies information that is critical for successful application and understanding of the product. Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic loss. Attentions help you: identify a hazard avoid a hazard recognize the consequence
ATTENTION
SHOCK HAZARD
Labels may be located on or inside the drive to alert people that dangerous voltage may be present.
BURN HAZARD
Labels may be located on or inside the drive to alert people that surfaces may be dangerous temperatures.
Summary of Changes
The information below summarizes the changes to this manual since the last printing, including new 1761-NET-ENIW functionality. To help you find new and updated information in this release of the manual, we have included change bars as shown to the right of this paragraph. The table below lists the sections that document new features and additional or updated information on existing features.
For this information: See
change of ENI/ENIW Installation Instruction page P-2 number Series C LED description Series C Enhancements Overview of web server functionality added 100-Base-T for Ethernet connections LED sequence at power-up Series C Troubleshooting using the LED indicators Series C Marine certification requirement page 1-3 page 1-5 page 1-6 page 2-5 page 9-2 page 9-3 page A-1
Publication 1761-UM006D-EN-P - March 2004
Summary of Changes
Table of Contents
Preface
Who Should Use this Manual. . . . . . . . . . . . . . . . Purpose of this Manual . . . . . . . . . . . . . . . . . . . . Related Documentation . . . . . . . . . . . . . . . . . Common Techniques Used in this Manual . . . . . . Rockwell Automation Support . . . . . . . . . . . . . . . Installation Assistance . . . . . . . . . . . . . . . . . . New Product Satisfaction Return . . . . . . . . . . . Your Questions or Comments on this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-1 P-1 P-2 P-2 P-3 P-3 P-3 P-4
Chapter 1 Product Overview

EtherNet/IP Connectivity . . . Hardware Features . . . . . . . Product Drawing . . . . . . LED Indicators . . . . . . . . Default Settings . . . . . . . Operating Modes . . . . . . . . Messaging . . . . . . . . . . . Device Compatibility . . . . . . Series B Enhancements . . . . Series C Enhancements . . . . Ethernet Networks . . . . . . . Basic Ethernet Topology Web Server Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 1-2 1-2 1-2 1-4 1-4 1-4 1-5 1-5 1-5 1-5 1-5 1-6
Chapter 2 Installation and Wiring

European Communities (EC) Directive Compliance . EMC Directive . . . . . . . . . . . . . . . . . . . . . . . . . . Low Voltage Directive . . . . . . . . . . . . . . . . . . . . Safety Considerations . . . . . . . . . . . . . . . . . . . . . . . External Power Supply Wiring . . . . . . . . . . . . . . . . . Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DIN Rail Mounting . . . . . . . . . . . . . . . . . . . . . . . Panel Mounting . . . . . . . . . . . . . . . . . . . . . . . . . ENI/ENIW Port Identification . . . . . . . . . . . . . . . . . . Ethernet Connections . . . . . . . . . . . . . . . . . . . . . . . Ethernet 8-Pin 10/100-Base-T Connector (Port 1). Ethernet Cables . . . . . . . . . . . . . . . . . . . . . . . . . Maintain ENI and ENIW Cable Connections . . . . RS-232 Port Connections . . . . . . . . . . . . . . . . . . . . . RS-232 Connector . . . . . . . . . . . . . . . . . . . . . . . RS-232 Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 2-1 2-1 2-2 2-3 2-3 2-4 2-4 2-5 2-5 2-5 2-6 2-6 2-7 2-7 2-7
iii
iv
Table of Contents
Chapter 3 Operation
Operation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Allocation of Ethernet Connections . . . . . . . . . . . . . . . . . . ENI and ENIW Functional Overview . . . . . . . . . . . . . . . . . General Ethernet Information . . . . . . . . . . . . . . . . . . . . . . RSLinx/RSWho Connectivity Example Using ENI/ENIW Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PC Connected Directly to Ethernet (RSLinx on Ethernet) PC Connected to Ethernet via the ENI or ENIW. . . . . . . 3-1 3-1 3-2 3-2 3-2 3-4 3-7
Chapter 4 ENI/ENIW Configuration (Nodes 248 to 254)

Configuration Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 ENI/ENIW Configuration Utility . . . . . . . . . . . . . . . . . . . . . 4-1 COM Port Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 RS-232 Baud Rate, TCP/IP Parameters, and BOOTP/DHCP Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Save to ENI/ENIW RAM or ENI/ENIW ROM . . . . . . . . . 4-4 E-Mail Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4 Message Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4 Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5 Controller Messaging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5 Configuring ENI/ENIW Data Parameters. . . . . . . . . . . . . . . 4-6 Configuring ENI/ENIW String Parameters . . . . . . . . . . . . . . 4-8 Configuring the ENI/ENIW E-Mail From String . . . . . . . 4-8 ENI/ENIW Configuration Parameters . . . . . . . . . . . . . . . . . 4-10 Node 248 - Save/Reset Function . . . . . . . . . . . . . . . . . . 4-11 Node 249 - From String . . . . . . . . . . . . . . . . . . . . . . . . 4-11 Node 250 - TCP/IP Configuration . . . . . . . . . . . . . . . . . 4-12 Node 251 - E-Mail Server . . . . . . . . . . . . . . . . . . . . . . . 4-15 Node 252 - BOOTP Configuration . . . . . . . . . . . . . . . . 4-15 Node 253 - Baud Rate . . . . . . . . . . . . . . . . . . . . . . . . . 4-16 Node 254 - Ethernet Hardware Address . . . . . . . . . . . . 4-17
Chapter 5 Peer-to-Peer Messaging

Messaging Between the ENI/ENIW and DF1 Devices . . . . . 5-1 Message to Configuration Nodes (Nodes 100 to 149) . . . . . 5-2 Sending a Message to a Destination Controller (Nodes 0 to 49). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Table of Contents
Chapter 6 E-Mail Messages (Node 50 to 99)

Overview . . . . . . . . . . . . . . . . . . . . . Configuring E-Mail . . . . . . . . . . . . . . SMTP E-Mail Address . . . . . . . . . . Destination Addresses . . . . . . . . . Message Text. . . . . . . . . . . . . . . . Message Fields (to, from, subject) . Sending an E-Mail Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 6-2 6-2 6-2 6-3 6-4 6-5
Chapter 7 Using 1761-NET-ENIW Web Server Web Browser Compatibility . . . . . . . . . . . . . . . . . . . . . . . . 7-1 Pages and Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1 Capabilities
index.html . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2 home.html. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2 reference.html . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3 User Pages (page1.html through page4.html) . . . . . . . . 7-4 event.html . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5 Defining URL Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5 Displaying Device Data . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6 String Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7 Integer Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8 Floating-point Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9 Writing Data to the ENIW. . . . . . . . . . . . . . . . . . . . . . . 7-10 Auto-Refresh of Detail Pages . . . . . . . . . . . . . . . . . . . . 7-11 ENIW Update Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11 Posting Data to the Device . . . . . . . . . . . . . . . . . . . . . . . . 7-12 Setting Passwords for Detail Pages . . . . . . . . . . . . . . . . 7-12 Posting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12 Displaying Event Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13 Using the ENIW Utility to Configure the ENIWs Web Server Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14 Configuring the Home Page . . . . . . . . . . . . . . . . . . . . . 7-14 Configuring Detail Pages . . . . . . . . . . . . . . . . . . . . . . . 7-15
vi
Table of Contents
Chapter 8 Connecting CompactLogix Controllers on Ethernet

System Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2 General CompactLogix Messaging Guidelines. . . . . . . . . . . 8-3 Configuring ENI #1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4 Configuring ENI #2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6 Configuring ENI #2 Via the ENI/ENIW Configuration Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7 Configuration Via Ladder Logic. . . . . . . . . . . . . . . . . . . 8-9 Downloading To The CompactLogix Controller Through Two Series A ENIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16 Downloading to the CompactLogix Controller Through a ENI/ENIW Series B/C via Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17 Create MSG Programs for the SLC 5/05 and the 5550 Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20
Chapter 9 Troubleshooting
Network Troubleshooting . . . . . . . . . . . . . Maintain ENI/ENIW Cable Connections. Using ENI/ENIW with Routers . . . . . . . . . . LED Sequence at Power-Up. . . . . . . . . . . . Troubleshooting Using the LED Indicators . Error Codes Generated by the ENI/ENIW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1 9-1 9-1 9-2 9-2 9-5
Appendix A Specifications
Physical Specifications. Ethernet Specifications MicroLogix Web Site . . Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1 A-1 A-1 A-2
Appendix B BOOTP Configuration Method (default)

Using the Rockwell BOOTP Utility. . . . . . . . . . . . . . . . . . . B-2 Using DCHP Software To Configure Your ENI/ENIW . . . . . B-4
Glossary Index
Preface
Read this preface to familiarize yourself with the rest of the manual. It provides information concerning: who should use this manual the purpose of this manual related documentation conventions used in this manual Rockwell Automation support
Who Should Use this Manual
Use this manual if you are responsible for designing, installing, programming, or troubleshooting control systems that use Allen-Bradley Controllers on Ethernet. You should have a basic understanding of Allen-Bradley programmable controllers and Ethernet networking. You should understand programmable controllers and be able to interpret the ladder logic instructions required to control your application. If you do not, contact your local Allen-Bradley representative for information on available training courses before using this product.
Purpose of this Manual
This manual is a reference guide for the Ethernet Interface (ENI) and Web-enabled Ethernet Interface (ENIW). It describes the procedures you use to install and configure the ENI and ENIW.
Preface
Related Documentation
The following documents contain additional information concerning Rockwell Automation products. To obtain a copy, contact your local Rockwell Automation office or distributor.
For Instructions on installing a 1761-NET-ENI or 1761-NET-ENIW Interface Converter. Information on DF1 open protocol.
Read this Document Ethernet Interface Installation Instructions DF1 Protocol and Command Set Reference Manual
Document Number 1761-IN007 1770-6.5.16 ENET-IN001 1770-4.1
In-depth information on designing, implementing, and maintaining an EtherNet/IP Media Planning and industrial control system using EtherNet/IP (Ethernet Industrial Protocol) Installation Manual In-depth information on grounding and wiring Allen-Bradley programmable controllers A description of important differences between solid-state programmable controller products and hard-wired electromechanical devices An article on wire sizes and types for grounding electrical equipment A glossary of industrial automation terms and abbreviations Allen-Bradley Programmable Controller Grounding and Wiring Guidelines Application Considerations for Solid-State Controls
SGI-1.1
National Electrical Code - Published by the National Fire Protection Association of Boston, MA. Allen-Bradley Industrial Automation Glossary AG-7.1
Common Techniques Used in this Manual
The following conventions are used throughout this manual: Bulleted lists such as this one provide information, not procedural steps. Numbered lists provide sequential steps or hierarchical information. Italic type is used for emphasis. ENI/ENIW is used when information and instructions are applicable to both the 1761-NET-ENI and 1761-NET-ENIW. In cases where information applies to only one type of interface, the appropriate model and series is identified.
Preface
Rockwell Automation Support
Rockwell Automation provides technical information on the web to assist you in using our products. At http://support.rockwellautomation.com, you can find technical manuals, a knowledge base of FAQs, technical and application notes, sample code and links to software service packs, and a MySupport feature that you can customize to make the best use of these tools. For an additional level of technical phone support for installation, configuration and troubleshooting, we offer TechConnect Support programs. For more information, contact your local distributor or Rockwell Automation representative, or visit http://support.rockwellautomation.com.
Installation Assistance
If you experience a problem with a hardware module within the first 24 hours of installation, please review the information that's contained in this manual. You can also contact a special Customer Support number for initial help in getting your module up and running:
United States Outside United States 1.440.646.3223 Monday Friday, 8am 5pm EST Please contact your local Rockwell Automation representative for any technical support issues.
New Product Satisfaction Return

Rockwell tests all of our products to ensure that they are fully operational when shipped from the manufacturing facility. However, if your product is not functioning and needs to be returned:
United States Contact your distributor. You must provide a Customer Support case number (see phone number above to obtain one) to your distributor in order to complete the return process. Please contact your local Rockwell Automation representative for return procedure.
Outside United States
Preface
Your Questions or Comments on this Manual

If you find a problem with this manual, or you have any suggestions for how this manual could be made more useful to you, please contact us at the address below: Rockwell Automation Automation Control and Information Group Technical Communication, Dept. A602V P.O. Box 2086 Milwaukee, WI 53201-2086 or visit our internet page at: http://www.rockwellautomation.com
Chapter
Product Overview
This chapter gives an overview of the Ethernet Network Interface. The following topics are covered: EtherNet/IP Connectivity Hardware Features Operating Modes Device Compatibility Ethernet Networks Web-Server Functionality
EtherNet/IP Connectivity
The 1761-NET-ENI and 1761-NET-ENIW provide EtherNet/IP connectivity for all MicroLogix controllers, CompactLogix controllers, and other DF1 full-duplex devices. The Ethernet Network Interface, ENI or ENIW, allows you to easily connect non-Ethernet controllers onto new or existing Ethernet networks and upload/download programs, communicate between controllers, and generate e-mail messages via SMTP (simple mail transport protocol). EtherNet/IP is an industry standard open protocol which provides inter-device compatibility. You can exchange information with other Allen-Bradley Ethernet controllers (SLC, PLC, and ControlLogix) in a peer-to-peer relationship, so you do not need any master-type device. The ENI and ENIW also support an SMTP mail service that allows an existing controller to send e-mail messages to any destination connected to the network. The e-mail can be used to initiate the transmission of data or status information.
1-2
Product Overview
Hardware Features
Product Drawing
RS-232 Mini-DIN Port Ethernet Port Series A/B: 10-Base-T Series C: 10/100-Base-T
C
R
ETHERNET INTERFACE
CAT SER FRN
1761-NET-ENI
E N I *B 2 2 0 0 1 0 2 0 0 0 1
B 2.20
FAC . xx
Ethernet Hardware Address
LISTED IND.CONT.EQ. FOR HAZ.
US LOC. A196 TEMPERATURE CODE T3C OPERATING

CLASS I, GROUPS A,B,C, AND D, DIV 2
N223
ETHERNET ADDRESS
F F -F F -F F -F F -F F -F F
EXTERNAL POWER REQUIREMENTS
24 V dc +10/-15% AT 100 mA N.E.C. CLASS 2
IP Address Write-On Area
USE EXTERNAL DC SOURCE FOR CLASS I DIVISION 2 APPLICATIONS. SEE INSTALLATION INSTRUCTIONS MADE IN U.S.A.
24VDC
DC NEUT
CHS GND
LED Indicators
The ENI and ENIW have five LED indicators:
Table 1.1 Series A/B Descriptions: LED

FAULT LINK Ethernet TX/RX RS-232 TX/RX
Description RS-232 data transmission indicator module power Ethernet link status Ethernet data transmission indicator
Function flashes when the RS-232 port is transmitting or receiving data lit when module is powered lit when there is a valid physical Ethernet connection flashes when the Ethernet port is transmitting or receiving data
Color green green green green red
TX/RX POWER LINK TX/RX
POWER
FAULT
fault condition indicator lit when a fault condition is present
Product Overview
1-3
Table 1.2 Series C Descriptions:

FAULT 10 100 RS-232 TX/RX
LED TX/RX
Description RS-232 data transmission indicator module power 10-Base-T Ethernet link status and data transmission indicator
Function RS-232 port is transmitting or receiving data no RS-232 traffic module is powered No link or continuous data activity 10-Base-T Half Duplex; Link good however no data activity
Color flashing green off green off amber
POWER 10
POWER
10-Base-T Half Duplex; Link good with flashing sporadic data activity amber 10-Base- T Full Duplex; Link good however no data activity 10-Base-T Full Duplex; Link good with sporadic data activity 100 100-Base-T Ethernet link status and data transmission indicator No link or continuous data activity 100-B ase-T Half duplex; Link good however no data activity 100-Base-T Half Duplex; Link good with sporadic data activity 100-Base-T Full Duplex; Link good however no data activity 100-Base-T Full Duplex; Link good with sporadic data activity FAULT fault condition indicator lit when a fault condition is present green flashing green off amber flashing amber green flashing green red
For more detailed information on LED operation, see Chapter 9, Troubleshooting.
IMPORTANT
The IP addresses in any of the examples in this manual were arbitrarily assigned and should only be used on an isolated Ethernet network. Contact your system administrator for unique IP addresses if you are connecting your Ethernet devices to your employers Ethernet network.
1-4
Product Overview
Default Settings
The ENI/ENIWs RS-232 port has the following default settings:
Table 1.3 RS-232 Settings Setting Baud Rate Handshaking (hardware, software) Data Bits Stop Bits Parity Default Autobaud none 8 1 none Other Options see table 4.10 none none none none
Table 1.4 DF1 Settings Setting Duplicate Message Detection Error Detection Default Enabled Auto-detect (for Autobaud) for reception only(1) 1 second 3 NAK retries 3 ENQs retries Dont Care Other Options none Auto-detect when Autobaud is true, otherwise CRC none none none none
Embedded Response Operation DLE ACK Timeout DLE NAK Receive DLE ENQ for Response DF1 Node Address
(1)
The ENI and ENIW can receive embedded NAKs and ACKs, but do not initiate them.
Operating Modes
Messaging
When the ENI/ENIW is connected to a programmable controller (and connected to an Ethernet network), the controller can be accessed from other devices on Ethernet, or initiate communications to other EtherNet/IP devices. E-Mail The ENI/ENIW also support SMTP mail service, which allows a controller to send e-mail messages to any e-mail address on the
Product Overview
1-5
network. The e-mail can be used to initiate the transmission of data or status information.
Device Compatibility
The ENI/ENIW are compatible with the following devices and applications: All MicroLogix, SLC, PLC-5, CompactLogix, FlexLogix, and ControlLogix controllers, which support DF1 Full-Duplex capable controllers that have at least one available RS-232 port Personal Computers using the RSLinx (V2.30.00 and higher) DF1 Full-Duplex Driver Other DF1 Full-Duplex compliant products that have at least one RS-232 port, for example, operator interface devices RSLinx (V2.31.00 and higher) Ethernet Driver
Series B Enhancements
The 1761-NET-ENI Series B features the following enhancements: elimination of the need for two ENIs in a CompactLogix, FlexLogix, or ControlLogix system using RSLogix 5000 ability to use Dynamic Host Configuration Protocol (DHCP) two new BOOTP options The 1761-NET-ENIW has the same features as the 1761-NET-ENI, but includes web-serving capabilities as discussed on page 1-6.
Series C Enhancements
The 1761-NET-ENI/ENIW Series C features the following enhancements: 10/100-Base-T Ethernet port that auto-negotiates between 10 Megabits per second and 100 Megabits per second, either half-duplex or full-duplex. increased temperature range up to 60C (140F) increased messaging performance
Ethernet Networks
Basic Ethernet Topology

The ENI/ENIW Ethernet connectors conform to ISO/IEC 8802-3 STD 802.3 and utilizes 10/100 Base-T media. Connections are made directly from the ENI/ENIW to an Ethernet switch. The network setup is simple and cost effective. Typical network topology is pictured below.
1-6
Product Overview
Ethernet Switch
RJ45 connectors on both ends of cable (10/100 Base-T)
to PC Ethernet Card or other Ethernet Device
to ENI or ENIW
IMPORTANT
The ENI/ENIW provides a 10/100 Base-T, RJ45 Ethernet connector which connects to standard Ethernet hubs and switches via an 8-wire twisted pair straight-through cable. To access other Ethernet mediums, use 10/100 Base-T media converters or Ethernet switches that can be connected together via fiber, thin-wire, or thick-wire coaxial cables, or any other physical media commercially available with Ethernet switches. See page 2-6 for more cable information.
Web Server Functionality
The ENIW enhances ENI Series B/C operation with web server functionality, enabling it to: display 40 data table values on 4 standard data web pages consisting of 7 integer and 3 floating-point values on each page display 10 user-configurable data description strings on each data web page password protect writable data files to prevent unauthorized modification provide 10 user-configurable web page links You can access information about the ENI/ENIW via your web browser. Simply enter its TCP/IP address into the address field of your browser. See Chapter 7 for details on using the ENIWs web server capabilities.
Chapter
Installation and Wiring
This chapter covers installation and wiring for the ENI/ENIW. It is divided into the following sections: European Communities (EC) Directive Compliance Safety Considerations Mounting External Power Supply Wiring ENI/ENIW Port Identification Ethernet Connections RS-232 Port Connections
European Communities (EC) Directive Compliance
This product has the CE mark. It is approved for installation within the European Union and EEA regions. It has been designed and tested to meet the following directives.
EMC Directive
This product is tested to meet the Council Directive 89/336/EC Electromagnetic Compatibility (EMC) by applying the following standards, in whole or in part, documented in a technical construction file: EN 50081-2 EMC Generic Emission Standard, Part 2 Industrial Environment EN 50082-2 EMC Generic Immunity Standard, Part 2 Industrial Environment This product is intended for use in an industrial environment.
Low Voltage Directive

This product is tested to meet Council Directive 73/23/EEC Low Voltage, by applying the safety requirements of EN 61131-2 Programmable Controllers, Part 2 - Equipment Requirements and
2-2
Tests. For specific information required by EN 61131-2, see the appropriate sections in this publication, as well as the Allen-Bradley publication Industrial Automation Wiring and Grounding Guidelines For Noise Immunity, publication 1770-4.1. Open style devices must be provided with environmental and safety protection by proper mounting in enclosures designed for specific application conditions. See NEMA Standards publication 250 and IEC publication 529, as applicable, for explanations of the degrees of protection provided by different types of enclosure.
Safety Considerations
This equipment is suitable for use in Class I, Division 2, Groups A, B, C, D, or non-hazardous locations only. The following WARNING statement applies to use in hazardous locations.
WARNING
Explosion Hazard Substitution of components may impair suitability for Class I, Division 2. Do not replace components or disconnect equipment unless power has been switched off and the area is known to be non-hazardous. Do not connect or disconnect connectors or operate switches while circuit is live unless the area is known to be non-hazardous. This product must be installed in an enclosure. All cables connected to the product must remain in the enclosure or be protected by conduit or other means. The ENI/ENIW must be operated using the external power source. The DC power source switch must be in the EXTERNAL position. All wiring must comply with N.E.C. article 501-4(b).
Use only the following communication cables and replacement connectors in Class I Division 2 Hazardous Locations.
Environment Classification Class I, Division 2 Hazardous Environment
Communication Cable and Connectors 1761-CBL-PM02 Series C 2707-NC8 Series B 1761-CBL-HM02 Series C 2707-NC9 Series B 1761-CBL-AM00 Series C 2707-NC10 Series B 1761-CBL-AP00 Series C 2707-NC11 Series B
2-3
External Power Supply Wiring
WARNING
EXPLOSION HAZARD In Class I Division 2 applications, an external, Class 2 power supply must be used. The DC Power Source selector switch on the ENI/ENIW must be set to EXTERNAL before connecting the power supply to the ENI/ENIW.
IMPORTANT
24 VDC DC NEUT CHS GND
Bottom View
In non-hazardous locations, external power is not required. Some devices (such as a MicroLogix controller) provide power to the ENI/ENIW via a cable connected to the ENI/ENIWs port 2. Be sure to set the DC power source selector switch to match your particular configuration, CABLE or EXTERNAL. Always connect the CHS GND (chassis ground) terminal to the nearest earth ground. This connection must be made whether or not an external 24V dc supply is used.
Mounting
The ENI/ENIW must be mounted in the vertical position, as shown. Horizontal mounting is not recommended due to thermal considerations. Allow 50 mm (2 in.) of space on all sides for adequate ventilation. See page A-1 for operating temperature specification.
protective debris strip
FAULT
top
ETHERNET RS232
TX/RX
side
IP
PWR
side
CABLE
EXTERNAL
bottom
ATTENTION
Do not remove the protective debris strip until after all the equipment in the panel is mounted and wiring is complete. Once wiring is complete, remove the protective debris strip. Failure to remove strip before operating can cause overheating.
2-4
DIN Rail Mounting

Installation
1. Mount your DIN rail.

DIN Rail Latch
2. Snap the DIN rail latch into the closed position. 3. Hook the top slot over the DIN rail. 4. While pressing the unit against the rail, snap the unit into position.
Removal
DIN Rail
Side View
1. Place a screwdriver in the DIN rail latch at the bottom of the unit. 2. Holding the unit, pry downward on the latch until the unit is released from the DIN rail.
Panel Mounting
Template
See Appendix A for panel mounting template.
Installation
ATTENTION
Be careful of metal chips when drilling mounting holes for your equipment within the enclosure or panel. Drilled fragments that fall into the equipment could cause damage. Do not drill holes above mounted equipment if the protective debris strip has been removed.
2-5
Mounting Template
1. Remove the mounting template from the back of this document. 2. Secure the template to the mounting surface. 3. Drill holes through the template. 4. Remove the mounting template. 5. Mount the unit.
ENI/ENIW Port Identification

Ethernet Port (Port 1) RS-232 Mini-DIN (Port 2)
Write-on area for Ethernet IP address
Ethernet Connections
Ethernet 8-Pin 10/100-Base-T Connector (Port 1)

The Ethernet connector is an RJ45, 10/100-Base-T connector. The pin-out for the connector is shown below:
Pin 1 2 3 4 5 6 7 8
Pin Name Tx+ TxRx+ not used not used Rxnot used not used
2-6
When to use straight-through and cross-over cables: ENI/ENIW Ethernet port to 10/100-Base-T Ethernet switch cables utilize a straight-through pin-out (1-1, 2-2, 3-3, 6-6). Direct point-to-point 10/100-Base-T cables connecting the ENI/ENIW Ethernet port directly to another ENI/ENIW Ethernet port (or a computer 10/100-Base-T port) require a cross-over pin-out (1-3, 2-6, 3-1, 6-2).
Ethernet Cables
Shielded and non-shielded twisted-pair 10/100-Base-T cables with RJ45 connectors are supported. The maximum cable length between an ENI/ENIW Ethernet port and a 10/100-Base-T port on an Ethernet switch (without repeaters or fiber) is 100 meters (323 feet). However, in an industrial application, the cable length should be kept to a minimum. With media converters or Ethernet switches, you can also connect to the following media: fiber optic broadband thick-wire coaxial cable (10Base-5) thin-wire coaxial cable (10Base-2)
Maintain ENI and ENIW Cable Connections

The unshielded twisted pair (UTP) patch cable on a switch should be labeled and treated as dedicated. Be careful when moving any cables, as port identity may be effected. If you are using a switch and must move the ENI/ENIW to a new port for any reason, power-cycle the interface. The power cycle forces a new Address Resolution Protocol (ARP) sequence which should immediately associate the ENI/ENIWs IP address with the port it is connected to. To help prevent problems with network communications affected by moving cables, discourage any field personnel from treating the ports of a switch as all the same.
2-7
RS-232 Port Connections
RS-232 Connector
7 6 8-pin mini-DIN 8
5 4 2 1
Table 2.1 RS-232 Connector Pin Assignments Pin 1 2 3 4 5 6 7 8 Port 2 24V dc ground (GND) no connection ENI/ENIW input data, RxD no connection no connection ENI/ENIW output data, TxD ground (GND)
RS-232 Cables
Port 2 of the ENI/ENIW is an 8-pin mini-DIN RS-232 port that provides connection to DF1 compatible RS-232 devices. The table below describes the RS-232 compatible cables.
ENI/ENIW Connected to: MicroLogix 1000, 1200, and 1500, Channel 0 (all series) SLC 5/03, SLC 5/04, or SLC 5/05, Channel 0 MicroLogix 1500 LRP, Channel 1 CompactLogix, FlexLogix, or ControlLogix serial ports
Catalog Number 1761-CBL-AM00 1761-CBL-HM02 1761-CBL-AP00 1761-CBL-PM02
Use Cable Mini DIN to Mini DIN 45 cm (17.7 in) 2m (6.5 ft.) Mini DIN to D-Shell 45 cm (17.7 in) 2m (6.5 ft.)
See page 2-2 for the list of cables that can be used in a hazardous environment.
2-8
Chapter
Operation
This chapter describes ENI/ENIW operation. The following information is included: Operation Overview Allocation of Ethernet Connections ENI and ENIW Functional Overview General Ethernet Information RSLinx/RSWho Connectivity Example Using ENI/ENIW Interface
Operation Overview
Ethernet is the protocol used to transport TCP/IP messages. On top of TCP, EtherNet/IP is the open protocol used by the ENI and ENIW. EtherNet/IP allows devices to exchange information (data); or to upload, download, and edit logic programs over Ethernet. To communicate between devices, EtherNet/IP uses a connection model. Connections are dedicated paths across Ethernet between devices.
Allocation of Ethernet Connections
The ENI and ENIW support a maximum of 6 connections, allowing simultaneous communication with up to 6 other devices or applications. The connections are dedicated as follows:
Number of Connections 2 2 2
Dedicated to: outgoing messages incoming messages either incoming or outgoing messages
TIP
For peer connections, no more than one connection per destination node is established. If multiple MSG instructions use the same destination node, they use the same connection.
3-2
Operation
ENI and ENIW Functional Overview
The ENI and ENIW provide EtherNet/IP connectivity for RS-232 devices that use DF1 full-duplex protocol. DF1 full-duplex is an open, point-to-point protocol used in any Allen-Bradley controller with an RS-232 port, and in many other devices. DF1 full-duplex supports up to 255 node addresses. The ENI and ENIW use these node addresses for different functions. The ENI and ENIW use a memory (node) map to provide access to the different functions you can perform. Each function uses a different group of node addresses. The following table illustrates the ENI and ENIW functions by groups of node numbers:
ENI and ENIW Function Message Routing
Node Group Node 100 to 149 Node 0 to 49
Node Function Configure Route Address Route DF1 MSG to IP at Configured Route Address Configure SMTP e-mail address Send e-mail message to configured SMTP e-mail address ENIW Web page data ENI and ENIW Configuration Registers
Valid Data Type Integer Integer String String String, integer, or floating point Integer or String depending on parameter
For More Information see chapter 5 see chapter 5 see chapter 6 see chapter 6 see chapter 7 see chapter 4
E-Mail
Node 150 to 199 Node 50 to 99
Web Data ENIand ENIW Configuration
Node 200 to 204 Node 248 to 254
General Ethernet Information
Each Ethernet device requires a unique IP address. If your Ethernet network is isolated from the company-wide network, any valid IP address may be used. If your Ethernet hub is connected to a larger Ethernet network, contact your System Administrator for unique IP addresses.
RSLinx/RSWho Connectivity Example Using ENI/ENIW Interface
For this example, the following IP addresses will be assigned to the various Ethernet devices on our network:
Table 3.1 Example Network IP Addresses IP Address 131.200.50.92 131.200.50.93 131.200.50.94 131.200.50.95 Series A ENI ENI or ENIW Series Device SLC 5/05 controller 1756-ENET 1761-NET-ENI #2 (1769-L20 or 1769-L30 CompactLogix controller)
Series A ENI or B/C (ENI 1761-NET-ENI #1 (computer COMM port) or ENIW)
Operation
3-3
Table 3.1 Example Network IP Addresses IP Address 131.200.50.96 131.200.50.97 Series B/C ENI or ENIW Series Device computers Ethernet card 1761-NET-ENI/1761-NET-ENIW #3 (1769-L20 or 1769-L30 CompactLogix controller) 1761-NET-ENI/1761-NET-ENIW #4 (MicroLogix 1500)
131.200.50.98
Series A or B/C
The subnet mask for each Ethernet device is then, 255.255.0.0.

IMPORTANT
The RS-232/DF1 interface between the CompactLogix controller and its ENI/ENIW module, and between the computer (RSLogix5000/RSLinx) and its ENI/ENIW module, should use 38400 baud. This will allow the fastest upload/download of programs. When using 38400 baud, the number of Stop Bits in RSLinx and in the CompactLogix controller must be set to 2.
Figure 3.1 Example Ethernet Network

1769-L20 and 1769-L30 (CompactLogix) 1769-L20 and 1769-L30 (CompactLogix) 1747-L552 (SLC 5/05)
ETHERNET RS232
FAULT
NET TX/RX TX/RX
IP
PWR
CABLE EXTERNAL
ENI #3 (Series B/C) 24V dc MicroLogix 1500
RS-232/DF1
ETHERNET RS232
FAULT
ENI #2 (Series A)
NET TX/RX TX/RX
IP
PWR
CABLE EXTERNAL
Ethernet Hub/Switch (10 Base T)
ENI #4 (Series A or B/C)

ETHERNET RS232
FAULT
NET TX/RX TX/RX
IP
PWR
CABLE EXTERNAL
24V dc 1756-L1 (ControlLogix)

<... > ETHERNET
Personal Computer with RSLogix 5000, RSLogix 500 and RSLinx
PC Ethernet Interface Card 1756-ENET

ETHERNET RS232
FAULT
NET TX/RX TX/RX
IP
PWR
PC COMM Port RS-232/DF1 ENI #1 (only necessary for connection to series A ENI #2)
CABLE EXTERNAL
24V dc
3-4
Operation
The ENI/ENIW allows you to connect from your PC to controllers over Ethernet. The following procedure can be used when the computer has a connection directly onto Ethernet (PCI card, PCMCIA interface, built in TCP/IP port, etc.) and also when the ENI/ENIW is plugged into the computers RS-232 (COMM) port.
PC Connected Directly to Ethernet (RSLinx on Ethernet)

IMPORTANT
You must use RSLinx version 2.31.00 or newer to browse with the ENI/ENIW Series B/C via Ethernet to a CompactLogix controller.
Follow these steps to configure RSLinx for Ethernet operation. 1. Open RSLinx and open the driver configuration dialog.
Operation
3-5
2. Select Ethernet devices from the available drivers, and then click OK to load the driver into RSLinx.
Once the Ethernet driver is loaded, either highlight and select Configure or simply double click on the Ethernet driver. 3. Click OK to accept the default driver name.
At that point, the station mapping screen will appear as illustrated here. Double click on the row below Host Name, and enter the TCP/IP addresses that match the devices on your network.
3-6
Operation
When you are done entering the stations, click OK to close the station mapping window. 4. Open the AB_ETH-1 tree on your computer. Autobrowse should be running and any active device that you have configured should be shown on the screen as illustrated below.
TIP
If the ENI or ENIW shows up as an Unrecognized Device, you may need to install the latest ENI or ENIW (Series B or Series C) EDS file. You can download this file from http://www.ab.com/networks/eds/.
Operation
3-7
IMPORTANT
You may NOT go online through the AB_ETH-1 Ethernet driver using RSLogix 5000 to the CompactLogix controller at IP address 131.200.50.94, because it is connected to Ethernet using a Series A ENI. You MAY go online through the AB_ETH-1 Ethernet driver using RSLogix 5000 to the CompactLogix controller that shows up under the ENI at IP address 131.200.50.97, because it is connected to Ethernet using a Series B/C ENI.
PC Connected to Ethernet via the ENI or ENIW

As shown below, the ENI/ENIW can also be used to connect a computers RS-232 port to EtherNet/IP and allow program upload and download and online sessions with a maximum of four EtherNet/IP devices. (Note: The ENI/ENIW limits the number of outgoing connections to four).
MicroLogix 1500 DF1 Node 4
CompactLogix DF1 Node 2
CompactLogix DF1 Node 3
ETHERNET RS232
FAUL AULT
ETHERNET RS232
FAUL AULT
ETHERNET RS232
FAUL AULT
NET TX/RX TX/RX
NET TX/RX TX/RX
NET TX/RX TX/RX
IP
PWR
ENI
IP
PWR
ENI 24V dc
IP
PWR
ENI 24V dc
CABLE EXTERNAL
CABLE EXTERNAL
CABLE EXTERNAL
Ethernet
ETHERNET RS232
FAUL AULT
NET TX/RX TX/RX
ENI Route Configuration TCP/IP DF1 131.200.50.92 Node 1 131.200.50.94 Node 2 131.200.50.97 Node 3 131.200.50.98 Node 4
IP
PWR
CABLE EXTERNAL
24V dc
RSLogix/RSLinx
SLC 5/05 DF1 Node 1
When using the ENI/ENIW as the computers interface, you can only perform functions supported by RSLogix/RSLinx and ENI/ENIW configuration operations (using the ENI/ENIW Configuration Utility). In addition, before you can use the ENI/ENIW to connect across Ethernet to destination devices in this fashion, the ENI/ENIW must have a valid TCP/IP address, and you must configure the ENI/ENIWs message routing table (nodes 100 to 149). Once the ENI/ENIW is properly configured, you can configure RSLinx.
3-8
Operation
RSLinx Configuration
1. Open RSLinx. 2. Open the configure drivers dialog box. 3. Select RS-232 DF1 devices. Click Add New. 4. Configure AB_DF1-1 driver to match the example below.
5. Click OK when the AB_DF1-1 driver is configured. The 1770-KF3/1747-KE device type only allows you to address nodes 0 to 31 (decimal). In order to address nodes 32 to 49, you must select the 1770-KF2/1785-KE device type and convert the octal addresses to decimal (408 = 3210 . . . 618 = 4910).
TIP
Operation
3-9
6. If you have set up the ENI/ENIW Message Routing table with IP addresses in entries between 1 and 31, those devices should respond when you browse the AB_DF1 driver.
TIP
If you use the AB_DF1 driver through an ENI/ENIW, you may go online with CompactLogix controllers using RSLogix 5000 whether they are connected to Ethernet through Series A or Series B/C ENI/ENIW modules. Although you may be able to successfully browse a 1756-Lxx controller located in slot 0 through a 1756-ENxT module using the AB_DF1 driver with an ENI/ENIW, you will not be able to go online with that 1756-Lxx controller using RSLogix 5000 programming software.
IMPORTANT
IMPORTANT
You can browse a maximum of four devices at one time from the DF1 driver, because the ENI/ENIW supports only four outgoing connections.
3-10
Operation
Chapter
ENI/ENIW Configuration (Nodes 248 to 254)
This chapter describes configuration methods and parameters. It is arranged as follows: Configuration Methods ENI/ENIW Configuration Utility Controller Messaging Configuring ENI/ENIW Data Parameters Configuring ENI/ENIW String Parameters ENI/ENIW Configuration Parameters
Configuration Methods
The ENI/ENIWs IP information can be entered using either: the ENI/ENIW Configuration Utility via the RS-232 port a write message from the Allen-Bradley controller to node address 250 via the RS-232 port a BOOTP server over Ethernet (BOOTP configuration is described in Appendix B of this manual) a DHCP server over Ethernet (once configured for DHCP)
ENI/ENIW Configuration Utility
The ENI/ENIW Configuration Utility is free software designed for configuring the ENI/ENIW. It is available for download from http://www.ab.com/micrologix.
TIP
When using the ENI/ENIW Configuration Utility, be sure to use a 1761-CBL-PM02 Series C cable between the ENI/ENIW and the computer. Also, make sure RSLinx is not running a driver that is using the COM port that you plan to use for the ENI/ENIW Configuration Utility.
4-2
COM Port Settings
Use the Utility Settings screen to set the following: COM Port - The PCs RS-232 port that the communications cable is plugged into. Baud Rate - Set the baud rate to match the baud rate configured for the ENI/ENIW. If youre not sure which baud rate the ENI/ENIW is configured for, try 38,400 first and if that doesnt work, try 19,200. These are the most commonly used baud rates. Parameter Upload Behavior and Parameter Download Behavior - This setting controls which parameters will be saved or loaded when you use the Load From or Save To buttons.
RS-232 Baud Rate, TCP/IP Parameters, and BOOTP/DHCP Options
4-3
Use the ENI/ENIW IP Addr screen to set the following: 232 Baud Rate Select a baud rate or choose Autobaud. See page 4-16 for more information. TCP/IP Parameters See page 4-12 for more information on valid addresses.(1) BOOTP/DHCP Options See the following section on Series B options and also see Table 4.9 on page 4-15 for details on the settings. TIP If you want to obtain the TCP/IP information via BOOTP, you must do that separately from the ENI/ENIW Configuration Utility. See Appendix B.
Enabling Series B Options

IMPORTANT
The ENI/ENIW Series B options are not available until the Enable Series B Options checkbox is selected. The enable Series B option is de-selected when a download is performed with no Series B options selected and the controller reverts to Series A type functionality. However, because of the difference in firmware level, the functionality may not be identical to an original ENI Series A.
The 1761-NET-ENI/1761-NET-ENIW Series B Configuration Utility features five Series B options: CompactLogix Routing Checkbox allows a Logix controller connected to the ENI/ENIW to go online using RSLogix 5000 on Ethernet. Always Checkbox when this checkbox is selected, the ENI/ENIW attempts to obtain the BOOTP IP address on every power cycle. The Always option is only available when Obtain via BOOTP is selected. Fallback Checkbox when this checkbox is selected, the ENI/ENIW attempts to obtain a BOOTP IP address on every power cycle. If a response is received, the ENI/ENIW uses the obtained address. If a response is not received, the ENI/ENIW falls back to the previously assigned IP address. The Fallback option is only available when Obtain via BOOTP is selected.
(1) Entering leading zeros in the octets of the IP address will not convert the decimal address to a octal value.
4-4
DHCP Checkbox when this checkbox is selected, the ENI/ENIW attempts to obtain the IP address from a DHCP server on every power cycle.
Save to ENI/ENIW RAM or ENI/ENIW ROM

You must save the configurations you have set. Click ENI/ENIW RAM for temporary setups or ENI/ENIW ROM to permanently save your settings. If you do not save the settings, they will revert to out-of-box on the next power-up.
E-Mail Settings
Use the E-mail screen to fill in the information for e-mail messages. E-mail servers are described on page 4-15. See Chapter 6 for information on the To and From strings.
Message Routing
Use the Message Routing screen to fill in the destination addresses for DF1 messaging. Message routing is described in Chapter 5.
4-5
Reset
Use the Reset screen to issue reset commands and to set the type of behavior that will occur at reset. The reset behavior options are described on page 4-11. For configurations uploaded from an ENI, the reset screen also displays information, such as the ENI/ENIW Ethernet hardware address and ENI/ENIW firmware revision.
Controller Messaging
When using this method, a write message is used to configure the TCP/IP configuration parameters. A 485CIF write message is initiated to the controller. CIF stands for Common Interface File and is supported by all Allen-Bradley programmable controllers that have an RS-232 port. TIP A 485CIF write may also be referred to as a PLC2 Unprotected Write.
4-6
The first item to configure is the ENI/ENIWs IP address on your network. See the following section, Configuring ENI/ENIW Data Parameters, for that configuration procedure.
IMPORTANT
The IP addresses in any of the examples in this manual were arbitrarily assigned and should only be used on an isolated Ethernet network. Contact your system administrator for unique IP addresses if you are connecting your Ethernet devices to your employers Ethernet network.
The configuration parameters are described in more detail later in this chapter.
Configuring ENI/ENIW Data Parameters
This example illustrates how to configure the ENI/ENIWs TCP/IP address (Node 250). TIP This procedure can also be used for any parameter that requires integer numbers (nodes 50 to 150, 250, 251, 252 and 253).
1. Create an integer data file. Inside the file arrange your TCP/IP data in groups of 4 words (as illustrated in file N50 below).
2. Create your message logic using whatever conditional instructions you may need. In this MicroLogix example, bit B3:0/8 is used to condition the message instruction and message file 10, element 1 is used to manage the message session.
4-7
3. Open the message instruction and enter the appropriate variables. The variables are described in Table 4.1.
Table 4.1 Message Instruction Variables for Configuring ENI/ENIW Data Parameters Variable Communication Command Setting For the ENI/ENIW configuration, this must be set to: 485CIF for MicroLogix and SLC a PLC2 Unprotected Write command for CompactLogix and PLC-5 In this example we are using integer file 50, element 5 (instruction starts at N50:5) to set the ENI/ENIWs IP address to 195.100.100.1. For all ENI/ENIW TCP/IP data configuration, always set this to 4 (4 words). The RS-232 communication channel that is connected to the ENI/ENIW, typically 0 or 1. Leave this value at the default. Always 0. This is the destination node address, in this example it is 101. Always Local.
This Controller Parameters:
Data Table Address
Size in Elements Channel
Target Device Parameters: Message Timeout Data Table Offset Local Node Addr (dec). Local/Remote
4. With the controller in Run, initiate the message. The new TCP/IP information is transmitted to the ENI/ENIW. At this point, the new configuration has NOT been saved to permanent memory. See Node 248 information on page 4-11 for instructions.
ATTENTION
4-8
Configuring ENI/ENIW String Parameters
Configuring the ENI/ENIW E-Mail From String

This example illustrates configuring the ENI/ENIW E-Mail From String (Node 249). To configure the E-Mail From String, initiate a message with a String element as the data.
IMPORTANT
E-Mail messages can only be initiated by controllers that support String elements. Therefore, this functionality cannot be used with the MicroLogix 1000 family of controllers.
EXAMPLE
Node 249 - E-Mail From String Node 249 holds the ASCII string that will be sent with any e-mail message initiated by the ENI/ENIW. To configure the E-Mail From String, initiate a message with a string element as the data. To do this, follow the procedure below.
TIP
This procedure can also be used for any parameter that requires string data (nodes 150 to 199 and 249).
1. Create a valid string file element as illustrated below. This example has data file 25 configured for string elements. In File ST25, element 0 has a valid e-mail from string, Station_0@My_Company.com.
4-9
2. Create your message logic using whatever conditional instructions you may need. This example uses bit B3:0/7 to condition the MSG instruction and message file 10, element 16 to manage the message session.
Table 4.2 Message Instruction Variables for Configuring ENI/ENIW String Parameters Variable Setting
This Controller Parameters: Communication Command For the ENI/ENIW configuration, this must be set to: 485CIF for MicroLogix and SLC a PLC2 Unprotected Write command for CompactLogix and PLC-5 Data Table Address Size in Elements Channel In this example we are using string file 25, element 0 (ST25:0) For all ENI/ENIW parameters that require a string configuration, always set this to 1. The RS-232 communication channel that is connected to the ENI/ENIW, typically 0 or 1. Leave this value at the default.
Target Device Parameters: Message Timeout
4-10
Table 4.2 Message Instruction Variables for Configuring ENI/ENIW String Parameters Variable Data Table Offset Local Node Addr (dec). Local/Remote Setting Always 0. This is the destination node address, in this example it is 249. Always Local.
ENI/ENIW Configuration Parameters

Table 4.3 Configuration Node Functions Node 248 Function Save/Reset(1)
The following table shows the functions that nodes 248 to 255 perform and their default values. Descriptions of each function can be found following the table.
Data Type Integer
Number of Elements 1
Options
Default
0 = save configuration to flash n/a 1 = simple reset 2 = reset to factory defaults 3 = conditional reset
249 250 251 252
From String TCP/IP Configuration E-Mail Server BOOTP Configuration
ASCII String Integers Integers Integer
1 4, 8, 12, 16, or 20 4 1
ENI/ENIW Identifier TCP/IP Parameters E-Mail Server Address 0 = BOOTP initially 1 = DF1 configuration 2 = BOOTP fallback 3 = BOOTP always 4 = DHCP always
ENI0.0.0.0@eni1761.org(2) 000.000.000.000 000.000.000.000 0
253 254
Baud Rate(3) Ethernet Hardware Address
Integer ASCII String
1 1
See page 4-16. Factory Value
Autobaud enabled with autodetect of CRC/BCC Factory Value - Read Only (see nameplate on unit)
255
Reserved
(1) See page 4-11 for more information on Save/Reset. (2) The ENI/ENIW address, 0.0.0.0 will be replaced by the IP address assigned to the ENI/ENIW. For example, the string may be ENI191.225.181.52@eni1761.org. If the ENI/ENIW does not have an assigned IP address, the string will be read as ENI0.0.0.0@eni1761.org. (3) Changes to the Baud Rate take effect when the ENI/ENIW power is cycled, or the configuration is saved to flash.
4-11
These parameters are described in more detail in the following sections.
Node 248 - Save/Reset Function

Depending on the value of the Save/Reset option, the ENI/ENIW performs the following operations when receiving a 485CIF/PLC2 Unprotected Write message of one element (integer) to Node 248.
Table 4.4 Save/Reset Function Value of Save/Reset 0 ENI/ENIW Operation The ENI/ENIW immediately stops all normal operations and saves the configuration to non-volatile memory. IMPORTANT The ENI/ENIW may take up to 60 seconds to complete this save operation. The configuration is not permanently saved until the Save command is sent.
1 2 3
The ENI/ENIW immediately stops all normal operations and performs a soft reset. The ENI/ENIW immediately stops all normal operations, performs a soft reset, and returns all parameters to their out-of-box settings. The ENI/ENIW immediately stops all normal operations, performs a soft reset, and returns all parameters to their out-of-box settings (except for the IP address, Subnet Mask, Gateway ID, and Security Mask).
Node 249 - From String

Node 249 holds the ASCII string that is sent with any e-mail message initiated by the ENI/ENIW. Criteria for a valid E-mail From String include: The From String remains at the default value unless changed by the user. See page 4-10 for default information. The From String must contain an @ symbol. The From String cannot contain any spaces or special ASCII characters. The maximum length of the From String is 64 characters. Any additional characters are ignored. To configure the From String, initiate a message with a string element as the data. The message instruction procedure is shown on page 4-8.
4-12
Node 250 - TCP/IP Configuration

This procedure describes configuration for the TCP/IP parameters. The TCP/IP parameters are configured by sending a message instruction to the ENI/ENIW (or by using the ENI/ENIW Configuration Utility). 1. Configure a 485CIF/PLC2 write message in the Allen-Bradley controller.
IMPORTANT
To configure TCP/IP parameters in this manner, BOOTP and DHCP must be disabled. Only PLC2 type or 485CIF write messages can be used to configure the ENI/ENIW.
2. Set the destination (target) node to 250. Using node address 250 directs this message to the TCP/IP configuration function. 3. The local integer file must be set up for at least 4 integer locations. The first 4 words define the IP address and are required. All remaining variables are optional. The table below describes the TCP/IP functions that can be configured. The sections following the table describe the functions in more detail.
Table 4.5 TCP/IP Configuration Parameters Function(1) IP Address Data Type Integer Length 4 words Notes Format aaa.bbb.ccc.ddd (decimal). The ENI/ENIW verifies the first/highest octet of any IP as follows: The first octet is between 1 and 223 and not equal to 127 or 169 The first octet is 0, and the entire IP is 0.0.0.0 otherwise the IP address is treated as an error For example, 0.168.0.75 is an error, or 127.0.0.0 is an error. Subnet Mask Integer 4 words If not sent, the default mask is derived from the class of the IP address as shown in Table 4-13. Only needed if a Gateway is present on the Subnet. The default is 000.000.000.000. If not present, the default is no security mask 000.000.000.000.
Gateway Security Mask 1 Security Mask 2
Integer Integer
4 words 4 words
(1) The IP address must be configured. All other functions are optional.
4-13
Subnet Mask
A subnet mask is used to interpret IP addresses when the network is divided into subnets. If your network is not divided into subnets, then leave the subnet mask at the default or allow the ENI/ENIW Configuration Utility to assign a default. The subnet mask defaults to auto-detect mode out-of-box. As long as the subnet mask is not manually set, the auto-detect mode follows the rules as shown below:
Table 4.6 Subnet Mask Auto-Detect Operation When the IP Address is set to: Out of Box: 0.0.0.0 Class A address Class B address Class C address And the Subnet Mask is in auto-detect: The Subnet Mask is set to: Switch-on auto-detect 255.0.0.0 255.255.0.0 255.255.255.0
Subnet Mask Auto-Detect Rules: Reading the subnet mask when the IP address is 0.0.0.0 returns a value of 0.0.0.0. When you manually configure the subnet mask, auto-detect is switched off and the configured mask is used. The ENI/ENIW validates the configured subnet mask and if: The first octet is not equal to 255, the ENI/ENIW returns status 0x10 and reverts to the previous mask, or The first octet is 255, but the remaining mask is not proper, the ENI/ENIW returns status 0x10 and reverts to the previous mask. The definition of proper is that the mask must be a contiguous series of 1s with no zeroes in between (i.e. 255.0.0.0 or 255.224.0.0 or 255.192.0.0 are valid, but 255.160.0.0 is not).
Security Mask
The Security Mask, when configured, allows you to restrict controller access to sources with IP addresses that are within some prescribed range. For example, if you wanted to restrict all message sources to be from within a companys allocated IP address range, a Security Mask could be configured that would block any IP address outside that range. This only applies to messages to the controller. Web page access, for example, is not restricted.
4-14
The security masks default value is 0.0.0.0 out-of-box, which is defined as accept all register session requests. A Security Mask of 255.255.255.255 is also defined as accept all register session requests. TIP The security mask acts as a filter on the source IP address such that any mask octet set to the value of 255 becomes dont care octets in the source IP address and all other fields must match exactly.
The follow examples illustrate the behavior of the security masks:

Table 4.7 Security Mask Behavior Example Condition If a security mask is set to 192.168.15.255 and an IP address 203.129.75. 23 attempts to message into the controller and an IP address 192.168.15.76 attempts to message into the controller If a security mask is set to 192.168.255.76 Security Mask Behavior The packet is rejected because 203.129.75 does not equal 192.168.15 (the 4th octet, 23, is dont care). The packet is processed because the upper 3 octets match (the 4th octet is still dont care). All source IPs that equal 192.168.xxx.76 are accepted because 255 is dont care.
You can use one or two security masks. If you wish to use only one security mask, use Security Mask 1 because it takes precedence over Security Mask 2 (for example, if Security Mask 1 is accepted, Security Mask 2 is not evaluated). Details of the relationship between the two masks are shown in the following table.
Table 4.8 Using Security Mask 1 and Security Mask 2 Example Condition If the security mask 1 filter results in an Accept decision If the security mask 1 filter results in a Deny decision Security Mask Behavior security mask 2 is not evaluated and the register session request is processed. security mask 2 is evaluated as follows: If the security mask 2 filter results in an Accept decision, the register session request is processed If the security mask 2 filter results in a Deny decision, the register session request is not replied to and the socket is closed.
Security masks 1 and 2 are evaluated using the following logic:
4-15
Node 251 - E-Mail Server

The TCP/IP address stored in this location defines the mail server. The ENI/ENIW sends all e-mail requests to this server, which then sends the e-mail message to the destination.
Node 252 - BOOTP Configuration

The ENI/ENIW allows the BOOTP request to be disabled by clearing the BOOTP Enable parameter in the channel Configuration File. BOOTP Enable behaves as follows:
Table 4.9 BOOTP Configuration Settings Node 252 Setting 0 1 2 ENI Configuration Utility Setting Obtain via BOOTP and save none Obtain via BOOTP and Fallback Always obtain via BOOTP DHCP Description ENI/ ENIW Series A (ENI only) and B A (ENI only) and B B
initial BOOTP configuration, where ENI/ENIW saves the result in non-volatile RAM (NVRAM) and uses that saved configuration on subsequent power cycles soft configuration via DF1 (utility or controller) special BOOTP where ENI/ENIW saves the result in non-volatile RAM (NVRAM), but tries BOOTP first. BOOTP is used only to change the IP address of the ENI/ENIW. traditional BOOTP where ENI/ENIW does not save the result in NVRAM and relies on the BOOTP response for every power cycle
3 4
traditional Dynamic Host Configuration Protocol (DHCP) where the ENI/ENIW B does not save the result in NVRAM and relies on a DHCP response for every boot
When BOOTP Enable is disabled, the ENI/ENIW will wait for a manual configuration. The BOOTP enable/disable setting is only evaluated on power-up. Changes to the BOOTP configuration will not take effect until the next power cycle.
IMPORTANT
If BOOTP is disabled, or no BOOTP server exists on the network, you must use a soft configuration method to enter or change the IP address for each ENI/ENIW. See page 4-1 for more information.
See Appendix B for information on using BOOTP.
4-16
Node 253 - Baud Rate

The first time the ENI/ENIW is powered-up (out-of-the-box), it is set to Autobaud so that it can synchronize to the attached controller. The baud rate can be changed by sending a message to address 253 with one of the configuration values shown in the table below. Changes to the baud rate take effect when the ENI/ENIW power is cycled or when a Save configuration to flash command (write to node 248) is received. The ENI/ENIW also performs a CRC/BCC check when autobaud is operational. When Autobaud is selected in a ENI/ENIW Series B, the ENI/ENIW communicates with the DF1 device attached to it at each power up to determine whether or not the ENI/ENIW should be in CompactLogix Routing mode, and to set the baud rate and checksum.
Table 4.10 ENI/ENIW Baud Rate Options Baud Rate Configuration Value For CRC with CompactLogix Routing Disabled (Series A or B) Autobaud 1200 2400 4800 9600 19.2K 38.4K(1) 57.6K Autobaud Enabled 0 1 2 3 4 5 6 7 For CRC with CompactLogix Routing Enabled (Series B only) 100 101 102 103 104 105 106 107
Autodetect of CRC/BCC occurs when autobaud is selected using values 8 to 99 and 108 to 65535.
(1) All CompactLogix devices must be configured to use two stop bits when communicating with the ENI/ENIW at 38.4K.
IMPORTANT
If the controllers baud rate is from 1200 to 38.4K, and the ENI/ENIW is configured for Autobaud, the ENI/ENIW will synchronize with the controllers baud rate. The ENI/ENIW cannot Autobaud to 57.6K to synchronize to the attached controller. You must manually set the baud rate to 57.6K.
4-17
Node 254 - Ethernet Hardware Address

ETHERNET INTERFACE
CAT SER FRN
1761-NET-ENI
E N I *B 2 2 0 0 1 0 2 0 0 0 1
B 2.20
FAC. xx
Hardware Address
LISTED IND.CONT.EQ. FOR HAZ.
US LOC. A196 TEMPERATURE CODE T3C OPERATING

CLASS I, GROUPS A,B,C, AND D, DIV 2
N223
ETHERNET ADDRESS
F F -F F -F F -F F -F F -F F
EXTERNAL POWER REQUIREMENTS
24 V dc +10/-15% AT 100 mA N.E.C. CLASS 2
You will find the hardware address on a label affixed to the ENI/ENIW as shown to the left. The hardware address can also be read from node address 254.
USE EXTERNAL DC SOURCE FOR CLASS I DIVISION 2 APPLICATIONS. SEE INSTALLATION INSTRUCTIONS MADE IN U.S.A.
24VDC
DC NEUT
CHS GND
4-18
Chapter
Peer-to-Peer Messaging
This chapter describes messaging between the ENI/ENIW and DF1 devices. The following topics are covered: Messaging Between the ENI/ENIW and DF1 Devices Message to Configuration Nodes (Nodes 100 to 149) Sending a Message to a Destination Controller (Nodes 0 to 49)
Messaging Between the ENI/ENIW and DF1 Devices
The ENI/ENIW can route a DF1 message received from the attached controller to a compatible destination TCP/IP device, using DF1 node addresses 0 through 49. ENI/ENIW Node addresses 100 through 149 store TCP/IP destination addresses. When the ENI/ENIW receives a write message to nodes 100 to 149, it stores the TCP/IP destination address in the corresponding map register. To configure the destination TCP/IP addresses, you can use either the ENI/ENIW Configuration Utility, or you can send a 485CIF/PLC2 message to each node as described in this section. The table below illustrates the relationship between messages and their corresponding configuration addresses.
Table 5.1 Message Routing ENI/ENIW receives read or write 485CIF/PLC2 message to Node 0 Node 1 ENI/ENIW TCP/IP route configuration Node100 Node101 Message forwarded to destination node TCP/IP address 111.222.233.200 (stored at Node 100) 111.222.233.201 (stored at Node 101)
IMPORTANT
When the ENI/ENIW receives a 485CIF/PLC2 write message to a configuration node address (100 through 149), it closes any open communications currently active on that connection and reconfigures the IP address to match the new configuration. If the received data matches the current configuration, the ENI/ENIW closes any open communications with the destination device.
5-2
If the ENI/ENIW receives a 485CIF/PLC2 read message to any of its configuration addresses (nodes 100 to 149), the ENI/ENIW responds with the current configuration of that node/address. Using the configuration shown in Table 5.1; if the controller initiates a read or write message to node 0, the ENI/ENIW forwards the request to the TCP/IP address at Node 100 (111.222.233.200).
Message to Configuration Nodes (Nodes 100 to 149)
When the ENI/ENIW receives a message from the attached controller to Node Address 0 to 49, it looks up the TCP/IP address associated with the address at Nodes 100 to 149. The ENI/ENIW preserves the original DF1 address when sending back a reply. The following table illustrates the relationship between configuration addresses and their corresponding messaging address.
Table 5.2 Peer-to-Peer Message Routing Node Number(1) 0 1 2 3 49
(1)
Function DF1 Route 0 MSG DF1 Route 1 MSG DF1 Route 2 MSG DF1 Route 3 MSG
Node Number 100 101 102 103
Routing Table Route 0 IP Address Route 1 IP Address Route 2 IP Address Route 3 IP Address Route 149 IP Address
Data Type Integer (4 words) Integer (4 words) Integer (4 words) Integer (4 words) Integer (4 words)
DF1 Route 49 MSG 149
See the IMPORTANT note below about assigning Nodes to various devices.
IMPORTANT
In the ENI/ENIW, node addresses 45 through 49 are dedicated for sending messages to 1756-ENxT/ControlLogix controllers. When sending messages to a 1756-ENxT/ControlLogix controller, the controller MUST be in slot 0 of the ControlLogix chassis for the message to be delivered to it. Node addresses 0 through 44 are to be used for all other Ethernet devices, such as other MicroLogix or CompactLogix controllers connected to ENI/ENIW modules or SLC 5/05 controllers.
To configure the route address (nodes 100 to 149), write a 485CIF/PLC2 message with 4 integer data words. An example is shown in the next section of this chapter.
5-3
Sending a Message to a Destination Controller (Nodes 0 to 49)
The ENI/ENIW uses a pair of node addresses to send data messages over TCP/IP. For data, two sets of addresses are used as illustrated in the table below. Node numbers 100 to 149 are used to define or store the actual TCP/IP address, and nodes 0 to 49 are used to send the data to the destination.
Table 5.3 DF1 Message Routing ENI/ENIW Node(1) 0 1 2 3 48 49
(1)
Function Route DF1 MSG to IP@address 100 Route DF1 MSG to IP@address 101 Route DF1 MSG to IP@address 102 Route DF1 MSG to IP@address 103 Route DF1 MSG to IP@address 148 Route DF1 MSG to IP@address 149
ENI/ENIW Function Node 100 101 102 103 148 149 Route 0 IP Address Route 1 IP Address Route 2 IP Address Route 3 IP Address Route 48 IP Address Route 49 IP Address
See the IMPORTANT note below about assigning Nodes to various devices.
IMPORTANT
In the ENI/ENIW, node addresses 45 through 49 are dedicated for sending messages to 1756-ENET/ControlLogix controllers. When sending messages to a 1756-ENET/ControlLogix controller, the controller MUST be in slot 0 of the ControlLogix chassis for the message to be delivered to it. Node addresses 0 through 44 are to be used for all other Ethernet devices, such as other MicroLogix or CompactLogix controllers connected to ENI/ENIW modules or SLC 5/05 controllers.
The procedure to send configuration data (nodes 100 to 149), or data (nodes 0 to 49) is exactly the same as discussed previously in Configuring ENI/ENIW Data Parameters on page 4-6.
5-4
Open the message instruction and enter the appropriate variables. The variables are described in Table 5.4.
Table 5.4 Message Instruction Variables for Sending a Message to a Destination Controller Variable Communication Command Data Table Address Size in Elements Channel Setting Use any command supported by your controller and the target device. Use any valid file. Use any valid size. The RS-232 communication channel that is connected to the ENI/ENIW, typically 0 or 1. Leave this value at the default. Use any valid file. The destination node address, Nodes 0 to 49 (decimal). Always Local.
Target Device Parameters: Message Timeout Data Table Address Local Node Addr (dec). Local/Remote
Chapter
E-Mail Messages (Node 50 to 99)
This chapter describes using the ENI/ENIWs e-mail feature. The following topics are included: Overview Configuring E-Mail Sending an E-Mail Message
Overview
The ENI/ENIW is capable of transmitting e-mail messages generated by the attached controller. This provides an extremely versatile mechanism to report alarms, status, and other data-related functions. To send an e-mail message, the controller generates a 485CIF/PLC2 write message, with a string element as the data, to a node number that correlates to the e-mail destination address.
IMPORTANT
E-Mail messages can only be initiated by controllers that support String elements. Therefore, this functionality cannot be used with the MicroLogix 1000 family of controllers.
ENI/ENIW e-mail behavior in a system is described by the following diagram.

DF1 String Message Mail Queue
Controller
485CIF/PLC2 Message with Embedded E-Mail
ENI/ENIW
SMTP Client
TCP Connection Destination Server Primary Relay Agent mailgate.xyz.com Destination Mailbox
Local Ethernet or Internet
6-2
Configuring E-Mail
SMTP E-Mail Address

To configure the e-mail function, two parameters must be configured: SMTP mail server IP address - configured by sending a write message to node 251 (e-mail server). See page 4-15 for more information.
IMPORTANT
The ENI/ENIW only accepts the configuration in the form of 4 elements (words) from an Integer file.
A From String - configure by sending a write message to node 249 (from string). The string element text can be stored in a String File as shown below. The string element text (ASCII characters) contains the verbatim from string. See page 4-8 for more information.
Destination Addresses
The ENI/ENIW stores e-mail addresses; it does not store the e-mail messages. To store a destination address, write a message to a specific node number (nodes 150 to 199). The message data must be a string element that contains a valid e-mail ASCII text string address, as illustrated in ST15:2 through ST15:5 in the example below.
6-3
IMPORTANT
Remember the following when setting up destination addresses: The ENI/ENIW can store up to 50 e-mail addresses. E-mail addresses can be up to 45 characters long; exceeding this will result in an error. The e-mail address must contain an @ character. E-mail addresses cannot contain any spaces or any other special ASCII characters other than the @ character.
Message Text
To send the actual e-mail message, the controller generates a write message, with a string element as the data (see ST15:7 to ST15:9 in the example above) to a node number (50 to 99) that correlates to the e-mail address (150 to 199). The following table shows the relationship between the e-mail message and the e-mail address. The maximum size of the message is 1 string element of 82 bytes.
6-4
Table 6.1 E-mail Address Configuration E-Mail Message Node 50 Node 51 Node 52 Node 98 Node 99 E-Mail Address Configuration Node 150 Node 151 Node 152 Node 198 Node 199 Description The data within the message is sent to Node 50 and forwarded to the e-mail address stored at Node 150. The data within the message is sent to Node 51 and forwarded to the e-mail address stored at Node 151. The data within the message is sent to Node 52 and forwarded to the e-mail address stored at Node 152. The data within the message is sent to Node 98 and forwarded to the e-mail address stored at Node 198. The data within the message is sent to Node 99 and forwarded to the e-mail address stored at Node 199.
IMPORTANT
The ENI/ENIW does not support non-printable ASCII characters and may exhibit unpredictable behavior when these characters are used in an e-mail message. Avoid using non-printable ASCII characters such as Carriage Return, Line Feed, Tabs, etc.
Message Fields (to, from, subject)

The ENI/ENIW includes the to, from, and subject fields in the body of the message. The default from text is ENI0.0.0.0@eni1761.org. This can be changed in the ENI/ENIW configuration, Node 249. See page 6-2 or Chapter 4. The standard format of the subject line is:
Subject: 1761ENI.MSG(plus the first 32 characters of text)
For example, if the message text was The quick brown fox jumped over the lazy dogs back, the subject line would read:
Subject 1761ENI.MSG(The quick brown fox jumped over )
6-5
Sending an E-Mail Message
The ENI/ENIW uses a pair of node addresses to send e-mail or data messages over TCP/IP. To send e-mail, two sets of addresses are used as illustrated in the table below. Node numbers 150 to 199 are used to define or store the actual e-mail address, and nodes 50 to 99 are used to send the string element to the e-mail recipient.
Table 6.B Email Node # 50 51 52 99 SMTP email message email message email message email message Node # 150 151 152 199 String File Data email address email address email address email address String File Data ASCII String ASCII String ASCII String ASCII String
TIP
The procedure to send configuration strings (nodes 150 to 199), or message strings (nodes 50 to 99) is exactly the same as discussed, Configuring ENI/ENIW String Parameters on page 4-8.
1. Start by configuring a MSG instruction.
6-6
Table 6.3 Message Instruction Variables for Sending an E-Mail Message Variable Communication Command Data Table Address Size in Elements Channel Setting 485CIF/PLC2 Any valid string, such as ST25:21 as shown below. 1 The RS-232 communication channel that is connected to the ENI/ENIW, typically 0 or 1. Increase this value to 10 or greater to avoid MSG timeouts. Always 0. This is the destination node address. Nodes 50 to 99 send e-mail messages; nodes 150 to 199 configure the e-mail address. Always Local.
Target Device Parameters: Message Timeout Data Table Offset Local Node Addr (dec).
Local/Remote
Chapter
Using 1761-NET-ENIW Web Server Capabilities
This chapter covers using the ENIWs web server features. It describes: web browser compatibility pages and file types defining URL links displaying device data on web pages ENIW update timer posting data to the device displaying event data using the ENIW Utility to configure the ENIWs web server functionality
You can access information from the ENIW via your web browser. Simply enter the ENIWs TCP/IP address into the address field of your browser.
Web Browser Compatibility
Because the ENIW standard web pages use frames and a cascading style sheet, your browser must support both of these features. The minimum web browser versions are Netscape 4.7 and MicroSoft Internet Explorer 5.5.
Pages and Files
The ENIW HTTP server utilizes the pages and files listed in the following table. See the indicated pages for details on using these files.
Table 7.1 ENIW Files File Name index.html home.html reference.html Description default base page list of URL links default content of lower frame of index.html Type static dynamic See Page 7-2 7-2 7-3
displays a summary of ENIW configuration details static content for the lower frame of index.html
7-2
Table 7.1 ENIW Files File Name page1.html page2.html page3.html page4.html event.html list of ENIW events content for lower frame of index.html dynamic 7-5 Description user data display and input primary content for lower frame of index.html Type dynamic See Page 7-4
Static files are returned to the browser as is. Dynamic files include "live" data from the attached controller and the formatting is very specific.
index.html
This is the default base page which contains two frames, an upper and a lower. The upper frame is fixed in size and contains the graphic elements and navigation buttons, as shown below.
Figure 7.1 Upper Frame
The scrollable lower frame contains the selected web page. The following web pages may be chosen for display in the lower frame: home.html page1.html through page4.html reference.html event.html
home.html
This dynamic page displays a titled, bulleted list of 16 URL links. The first 6 links are fixed, displaying links to ENIW Page 1 of 4 through ENIW Page 4 of 4, and to event.html and reference.html. The remaining links can be defined by the user as described on page 7-5.
7-3
Figure 7.2 Example home.html Page
Only the page title and the first 4 links of the home page can be renamed, using a write message of a single string to the offset elements of node 200 specified in the table below. For SLC or MicroLogix 485CIF Write MSG instruction, enter the offset value in decimal. For CompactLogix PLC-2 Unprotected Write MSG instruction, enter the element value in octal.
Table 7.2 Renaming Home Page and User Pages Item Home Page Title Page 1 User String Page 2 User String Page 3 User String Page 4 User String Affected Pages Home Page Home and Page 1 Home and Page 2 Home and Page 3 Home and Page 4 Default Title ENIW Home Page ENIW Page 1 of 4 ENIW Page 2 of 4 ENIW Page 3 of 4 ENIW Page 4 of 4 Element 0200 05600 06200 06600 07200 Offset 1 23 25 27 29
The ENIW allows limited HTML formatting. For example, the string <B>Go to Allen-Bradley website</B> would create a bold title.
IMPORTANT
The ENIW does not validate HTML code or provide protection against HTML coding errors.
The link to event.html is titled ENIW Event Page and the link to reference.html is titled ENIW User Reference. Neither can be changed.
reference.html
This static content page for the lower frame of index.html displays a summary of ENIW configuration details. It contains the configuration nodes used to read or write ENIW configuration.
7-4
Figure 7.3 Example reference.html Page
User Pages (page1.html through page4.html)

These 4 dynamic pages contain the primary content for the lower frame of index.html. They contain the 10-line tables which show user data and accept user input as shown in the example page below.
Figure 7.4 Example User Page
The first column, Data Description, contains string (ST) elements. The second column, Writes from Device, contains integer (N) or floating-point (FP) data. See Displaying Device Data on page 7-6. The Writes to Device column is for entering data, which can be written to the device. A fourth column, indicates the integer or floating-point destination for the write data. See Posting Data to the Device on page 7-12.
7-5
event.html
This dynamic page displays the lines buffered by the ENIW as a last specified number of events (Event Log) as shown below.
Figure 7.5 Example event.html Page
For information on Displaying Event Data, see page 7-13.
Defining URL Links
The home.html page consists of 16 URL links. The first 6 are fixed links to the data display, event log, and configuration reference pages, as discussed earlier. You can customize the remaining 10 links for your application. To define these links, use write messages to elements of node 200, as listed in Table 7.3. The first write message contains the title of the link and the second write message contains the URL. Each string may be up to 45 characters in length. For SLC or MicroLogix 485CIF Write MSG instruction, enter the offset value in decimal. For CompactLogix PLC-2 Unprotected Write MSG instruction, enter the element value in octal. EXAMPLE When defining User Link 1 as a link to the Allen-Bradley website, ST Offset 3 is the user text displayed, in this case "Go to AB main web site"; ST Offset 4 is the URL, in this case "http://www.ab.com".
7-6
The ENIW allows limited HTML formatting. For example, the string <B>Go to Allen-Bradley website</B> would create a bold title.
IMPORTANT
The ENIW does not validate the URL.
Table 7.3 Defining URL Links on the Home Page Node 200 Offset 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 Defines Element 0600 01000 01200 01400 01600 02000 02200 02400 02600 03000 03200 03400 03600 04000 04200 04400 04600 05000 05200 05400 Title URL Title URL Title URL Title URL Title URL Title URL Title URL Title URL Title URL Title URL For User Link 1 2 3 4 5 6 7 8 9 10
TIP
Unused links cannot be removed from the list. Rename them reserved to indicate they are not used.
Links may also be configured with the ENI/ENIW Configuration Utility.
Displaying Device Data
The four detail pages show data pushed to the ENIW by the attached device. If no data has been written to the ENIW by the attached device or configuration utility, these pages display empty cells. The integer and floating-point data on this page is volatile and is cleared every time the ENIW boots.
7-7
Each of the four detail pages are titled with either the default ENIW Page 1 of 4" etc., or with user-defined page names. See page 7-3 for information on how to rename the detail pages. Detail pages display string data in column 1 and either integer or floating point data in column 2.
String Data
String Data for the detail pages is written to Node 201, offset elements 1 to 40 as described in Table 7.4. Strings are left-justified. For SLC or MicroLogix 485CIF Write MSG instruction, enter the offset value in decimal. For CompactLogix PLC-2 Unprotected Write MSG instruction, enter the element value in octal.
Figure 7.6 Example Write to First String on Second Detail Page
7-8
Integer Data
Integer data for the detail pages is written to Node 202, offset elements 0 to 27, as described in Table 7.4. Integers are displayed as right-justified, signed decimal numbers from -32768 to +32767.
IMPORTANT
The 1761-NET-ENIW does not support either 485CIF Writes or PLC2 (Unprotected Writes) for displaying integer or floating-point device data. Instead, the web page DST of the ENIW uses the SLC-type write (Protected Type Logical Write with three address fields), which allows the data type and element index to be relevant.
Figure 7.7 Example Write to First Integer on Second Detail Page
7-9
Floating-point Data
Floating-point data for the detail pages is written to Node 203, offset elements 0 through 11, as described in Table 7.4. Floating-points in column 2 are right-justified with 7 significant digits plus the decimal point. If an exponent is required, it is displayed as "e-xx" with one significant digit to the left of the decimal point. The valid range is 1.175495e-38 to 3.402823e+38.
Figure 7.8 Example Write to First Floating-Point on Second Detail Page
7-10
Writing Data to the ENIW

The following table summarizes how string, integer, and floating-point device data is written to the ENIW.
Table 7.4 Writing Device Data to ENIW Data Type String Displayed in Column 1 1 2 3 4 5 6 7 8 9 10 Integer 2 1 2 3 4 5 6 7 FloatingPoint 2 8 9 10 203 202 Write to page1.html Node Row Offset Element 201 1 2 3 4 5 6 7 8 9 10 0 1 2 3 4 5 6 0 1 2 0200 0400 0600 01000 01200 01400 01600 02000 02200 02400 page2.html Offset 11 12 13 14 15 16 17 18 19 20 7 8 9 10 11 12 13 3 4 5 Element 02600 03000 03200 03400 03600 04000 04200 04400 04600 05000 page3.html Offset 21 22 23 24 25 26 27 28 29 30 14 15 16 17 18 19 20 6 7 8 Element 05200 05400 05600 06000 06200 06400 06600 07000 07200 07400 page4.html Offset 31 32 34 35 36 37 38 39 40 21 22 23 24 25 26 27 9 10 11 Element 07600 10000 10400 10600 11000 11200 11400 11600 12000
330260 10200
7-11
Auto-Refresh of Detail Pages

By default, each detail page has an update frequiency of 10 seconds. You can enter a refresh time in seconds (5 to 9999) and post this information to the ENIW by clicking anywhere within the frame.
Figure 7.9 Auto-refresh Field
TIP
To avoid excessive loading of the Ethernet network, set the refresh rate as long as is practical for your application and set the value to 9999 when not in use.
ENIW Update Timer
The ENIW provides a counter displaying the time, in seconds, since the last PLC write to the ENIW. The counter resets to 0 whenever the ENIW detects a valid write on one of the following nodes: 201 202 203 204 205 (Strings) (Integers) (Floating-points) (Event Strings) (Null String to Clear)
The counter displays a maximum value of 65,535 seconds. Once the counter reaches that maximum, it displays a value of 65,535 until it detects a valid write. The counter is viewable on all four of the ENIWs detail pages.
Figure 7.10 ENIW Update Timer
7-12
Posting Data to the Device
Each of the 4 detail pages has the option for user updates to the attached device using 500CPU/SLC-type write messages. Each of these pages protects data using a unique, case-sensitive password containing a maximum of 8 characters. You must enter the correct password to enable device update.
Setting Passwords for Detail Pages

Passwords for the detail pages are configured using 485CIF string writes to elements of Node 200, as listed in Table 7.5. For SLC or MicroLogix 485CIF Write MSG instruction, enter the offset value in decimal. For CompactLogix PLC-2 Unprotected Write MSG instruction, enter the element value in octal.
Table 7.5 Setting Passwords To set a password for: Page 1 Page 2 Page 3 Page 4 write a string to Node 200: offset 24, element 06000 offset 26, element 06400 offset 28, element 07000 offset 30, element 07400 Default password none; writes disabled
A pages password can configure the ENIW to disable device update or to remove the password protection. To disable device update, enter a null string in the password field. To allow device update, enter a case-sensitive string of one to eight characters in the password field. To permit widespread access, use a "*" password. Passwords may also be configured from the ENI/ENIW Configuration Utility.
Posting Data
Values entered in column 3 of the detail pages are written by the ENIW to the attached device only after you enter the password (if required) and click on the Write to Device button. The ENIW writes one value at a time to the data table addresses shown in the table below. (Multiple values are not combined into one SLC type Write message). The Data Table addresses are also reflected in column 4 of each user page.
7-13
Table 7.6 Data Table Addresses for Detail Pages Row 1 2 3 4 5 6 7 8 9 10 Data Table Addresses page1.html N50:0 N50:1 N50:2 N50:3 N50:4 N50:5 N50:6 F51:0 F51:1 F51:2 page2.html N50:7 N50:8 N50:9 N50:10 N50:11 N50:12 N50:13 F51:3 F51:4 F51:5 page3.html N50:14 N50:15 N50:16 N50:17 N50:18 N50:19 N50:20 F51:6 F51:7 F51:8 page4.html N50:21 N50:22 N50:23 N50:24 N50:25 N50:26 N50:27 F51:9 F51:10 F51:11
Integer data, written to N50 can be in the range of -32768 to +32767. Floating point data, written to F51, can be any valid 32-bit floating point number. However, ASCII representation is limited to 7 characters plus the decimal and any exponents. Values that do not change are not written to the device. The data is not validated by the ENIW. Failed writes are indicated by six question marks (??????). TIP The device updates run at a slightly higher priority than regular EtherNet/IP network traffic. However, the ENIW does not guarantee delivery or write performance and will discard data after the standard DF1 retry and timeout periods.
Displaying Event Data
The event.html page displays a log of events in a buffered list composed of up to 50 string elements. Each string is displayed in a single line on the page. The event log displays the last number (n) of strings received, with the newest message at the top. Once the buffer is full, each new string received overwrites the oldest. Strings written by the attached device to the ENIW to node 204 at element 0 are added to the Event Log. Strings written to node 205 clear the buffer.
7-14
Using the ENIW Utility to Configure the ENIWs Web Server Functionality
The ENI/ENIW Utility includes two new tabs for configuring the ENIWs web pages: Web Config and Web Data Desc. These two tabs allow you to title the home page and detail pages, to enter URL links, and to enter data descriptions for the detail pages, as described below.
Configuring the Home Page

Use the Web Config tab to enter the title of your home page and to customize the last 10 URL links, by entering the title of the link and the URL as show below.
Figure 7.11 Configuring Home Page
7-15
Configuring Detail Pages

Use the Web Config tab to enter page titles and passwords, if desired, for the four detail pages.
Figure 7.12 Entering Detail Page Titles and Setting Passwords
The Web Data Desc tab allows you to enter data descriptions for the ten rows/lines of data on each of the four detail pages. Descriptions can be 45 characters in length.
Figure 7.13 Entering Web Data Descriptions
7-16
Chapter
Connecting CompactLogix Controllers on Ethernet

The chapter contains an example of using the ENI/ENIW on an Ethernet network. It is arranged as follows: System Diagram Purpose Scope General CompactLogix Messaging Guidelines Configuring ENI #1 Configuring ENI #2 Downloading To The CompactLogix Controller Through Two Series A ENIs Downloading to the CompactLogix Controller Through a ENI/ENIW Series B/C via Ethernet Create MSG Programs for the SLC 5/05 and the 5550 Controllers
System Diagram
Figure 8.1 Example ENI/ENIW Network

1769-L20 and 1769-L30 (CompactLogix) 1769-L20 and 1769-L30 (CompactLogix) 1747-L552 (SLC 5/05)
ETHERNET RS232
FAULT
NET TX/RX TX/RX
IP
PWR
CABLE EXTERNAL
ENI #3 (Series B/C) 24V dc MicroLogix 1500
RS-232/DF1
ETHERNET RS232
FAULT
ENI #2 (Series A)
NET TX/RX TX/RX
IP
PWR
CABLE EXTERNAL
Ethernet Hub/Switch (10 Base T)
ENI #4 (Series A or B/C)

ETHERNET RS232
FAULT
NET TX/RX TX/RX
IP
PWR
CABLE EXTERNAL
24V dc 1756-L1 (ControlLogix)

<... > ETHERNET
Personal Computer with RSLogix 5000, RSLogix 500 and RSLinx
PC Ethernet Interface Card 1756-ENET

ETHERNET RS232
FAULT
NET TX/RX TX/RX
IP
PWR
PC COMM Port RS-232/DF1 ENI #1 (only necessary for connection to series A ENI #2) Publication 1761-UM006D-EN-P - March 2004
CABLE EXTERNAL
24V dc
8-2
The computer must include the following software: RSLogix5000, version 7.00 or later for CompactLogix 5320 (1769-L20) RSLogix5000, version 8.00 or later for CompactLogix 5330 (1769-L30) RSLinx, version 2.31.00 or later RSLogix500 ENI/ENIW Configuration Utility The 1769-L20 controller must contain firmware 7.17 or later. The 1769-L30 controller must contain firmware 8.14 or later. The Ethernet Interface Card in the computer is used to connect directly to the SLC 5/05 controller (channel 1), to the 5550 controller via the 1756-ENET or 1756-ENBT card, and to the CompactLogix controller via a Series B ENI/ENIW. Alternatively, the computers COMM Port can be used to connect to the CompactLogix controller via two ENI/ENIW modules
IMPORTANT
If the CompactLogix controller is connected to a ENI Series A, then you must connect a second ENI/ENIW to your PCs RS-232 port (as shown in the example network on page 8-1) in order to go online with it using RSLogix 5000. If the CompactLogix controller is connected via a ENI/ENIW Series B/C, then you may go online with it using RSLogix 5000 through the PCs Ethernet card.
Purpose
Provide Ethernet connectivity for CompactLogix controllers via the RS-232 serial port and the ENI/ENIW module.
Scope
Connecting CompactLogix controllers on Ethernet requires one ENI/ENIW per CompactLogix controller. The ENI/ENIW converts RS-232 hardware connections and DF1 full-duplex protocol to Ethernet 10BaseT hardware connections and EtherNet/IP protocol. The ENI/ENIW must be configured with IP addresses assigned to node numbers 0 to 49. The Destination Node Address in DF1 messages is then used by the ENI/ENIW to route the message to the proper device on Ethernet.
8-3
This application example shows how to configure the ENI/ENIW module and how to send messages from the CompactLogix controller to the other controllers on Ethernet. This example also shows how to initiate messages from the Ethernet controllers to the CompactLogix controller. Messages sent to the ENI/ENIW modules IP address will be delivered to the serial port of the CompactLogix controller. TIP In the ENI/ENIW, node addresses 45 through 49 are dedicated for 1756-ENET/ControlLogix controllers located in slot 0. Node addresses 0 through 44 are to be used for all other Ethernet devices, such as other CompactLogix controllers connected to ENI/ENIW modules and SLC 5/05 controllers.
For this example, we will assign the following IP addresses to the devices on Ethernet:
Table 8.1 Example IP Addresses for Ethernet Devices Device SLC-5/05 1756-ENET 1761-NET-ENI #2 1761-NET-ENI #1 Computer Ethernet Card Node Address (for L20 MSG) 1 45 N/A N/A N/A IP Address 131.200.50.92 131.200.50.93 131.200.50.94 131.200.50.95 131.200.50.96
IMPORTANT
The IP addresses in Table 8.5 were arbitrarily assigned for this demonstration and should only be used on an isolated Ethernet network as in this example. Contact your system administrator for unique IP addresses if you are connecting your Ethernet devices to your companys Ethernet network.
General CompactLogix Messaging Guidelines
Rungs 0 and 1, shown in Figure 8.2, of the CompactLogix controllers ladder program show an example of throttling two message (MSG) instructions. In this case, sending a MSG to the SLC 5/05, and then when its complete (Done bit set), initiating a MSG to the 1756-ENET/ControlLogix controller and so on. The two MSG instructions toggle, with only one outstanding MSG at a time. This is recommended for the CompactLogix controller to keep the amount of user memory needed for incoming and outgoing messages
8-4
to a minimum. Each message requires approximately 1.1K bytes of user memory, allocated when the message is to be sent or received. If two messages were enabled at the same time, 2.2K bytes of user memory would need to be available.
Figure 8.2 Throttling Message Instructions
Configuring ENI #1
The ENI/ENIW Configuration Utility, free software designed for configuring the 1761-NET-ENI/1761-NET-ENIW, is available for download from www.ab.com/micrologix. TIP If the CompactLogix controller is connected to a Series B ENI/ENIW and your computer has an Ethernet network connection, you may skip directly to Configuring ENI #2 on page 8-6.
First, configure the ENI/ENIW module connected to the computer. This is ENI #1 per Figure 8.1. A 1761-CBL-PMO2 serial cable is used to connect a computer serial communication port to the RS-232 mini-din serial port on the ENI/ENIW. The ENI/ENIW Configuration Utility is
8-5
used to configure this ENI/ENIW. When you start the ENI/ENIW Configuration Utility, the following screen appears:
Figure 8.3 ENI/ENIW Configuration Utility ENI IP Addr Screen
For this example, we use 38400 baud on all serial connections. We also assign IP addresses to all Ethernet products rather than using BOOTP.
IMPORTANT
Series B options are grayed out until the Enable Series B Options check box is selected. The ENI will revert to Series A type functionality if a download is performed with the Enable Series B Options box unchecked. However, because of the difference in firmware level, the functionality may not be identical to an original ENI Series A.
The ENI IP Addr tab and the Message Routing tab in the ENI/ENIW Configuration Utility must be modified for the purposes of this example. The IP address for the ENI/ENIW connected to the CompactLogix controller (ENI #2) is the only address we need to add to the ENI #1 Message Routing table. The other two Ethernet devices are accessed by the computer via the computers Ethernet card. Set up the two ENI #1 tabs as follows:
Figure 8.4 ENI #1 Configuration - ENI IP Addr Screen
8-6
Figure 8.5 ENI #1 Configuration - Message Routing Screen
Before we download our configuration to ENI #1, we must configure the Utility Settings tab in the ENI/ENIW Configuration Utility. Choose the following settings.
Figure 8.6 ENI #1 Configuration - Utility Settings Screen
Then, connect the serial cable between your computer and ENI #1 and click on the ENI IP Addr tab. From this tab, under the Save To column, click the ENI ROM button. This downloads your configuration parameters to ENI #1 and saves it to non-volatile memory.
Configuring ENI #2
ENI #2 is connected to the CompactLogix controller. This ENI/ENIW must be configured with its own IP address (131.200.50.94 for this example) and we must add the IP addresses of the SLC 5/05 controller and the 1756-ENET/ControlLogix controller to its Message Routing table. The Message Routing table allows for up to 50 IP addresses to
8-7
be linked to DF1 destination node addresses, for the following purposes:

Table 8.2 Message Routing Nodes 0 to 44 Function When sending messages to any Ethernet device, other than ControlLogix, that supports the same command set as the CompactLogix controller, i.e. SLC 5/05, PLC-5E and other ENI/ENIW modules. We will use the PLC-5 Typed Write commands for this example. CIP commands are not supported by the ENI/ENIW. When sending messages to a 1756-ENET/ControlLogix Controller, the controller MUST be in slot 0 of the ControlLogix chassis for the message to be delivered to it.
45 to 49
At this point we need to configure ENI #2 as we did ENI #1, using the ENI/ENIW Configuration Utility. You could also use the method outlined in Chapter 5 to configure ENI #2. This method sends configuration Messages from the CompactLogix controller via the DF1 link. If for any reason this ENI/ENIW would need to be replaced, it could then be easily and quickly configured via messages from the CompactLogix controller. A ladder program to accomplish this is shown on page 8-9.
Configuring ENI #2 Via the ENI/ENIW Configuration Utility

When you start the ENI/ENIW Configuration Utility, the following screen appears:
Figure 8.7 ENI/ENIW Configuration Utility ENI IP Addr Screen
For this example, we use 38400 baud on all serial connections. The 232 Baud Rate field on the ENI IP Addr tab must be left at Auto for the Series B ENI/ENIW to detect that a CompactLogix controller is attached to it, and that it should use bridged mode, allowing RSLogix 5000 to upload/download/go online with the CompactLogix from Ethernet. We also assign IP addresses to all Ethernet products rather than using BOOTP.
8-8
The ENI IP Addr tab and the Message Routing tab in the ENI/ENIW Configuration Utility must be modified for the purposes of this example. We need to add the addresses of the SLC 5/05 and the 1756-ENET to the ENI #2 Message Routing table. These addresses are taken from Table 3.1 on page 3-2. Set up the two ENI #2 tabs as follows:
Figure 8.8 ENI #2 Configuration - ENI IP Addr Screen
Figure 8.9 ENI #2 Configuration - Message Routing Screen
Before we download our configuration to ENI #2, we must configure the Utility Settings tab in the ENI/ENIW Configuration Utility. Choose the following settings.
Figure 8.10 ENI #2 Configuration - Utility Settings Screen
Then, connect the serial cable between your computer and ENI #2 and click on the ENI IP Addr tab. From this tab, under the Save To column, click the ENI ROM button. This downloads your configuration parameters to ENI #2 and saves it to non-volatile memory.
8-9
Configuration Via Ladder Logic

Rungs 2 through 8, on page 8-9, and the rungs 0 and 1 shown on page 8-4 in this application example, make up the ladder program for the CompactLogix controller. Details of each MSG instruction follow.
Figure 8.11 ENI #2 Configuration - RSLogix 5000 Ladder Program
In the above program, Rung 2 initiates the string of configuration messages with input instruction Reconfig_ENI. This could be an alias to an input connected to a pushbutton for example, for quick configuration of the ENI/ENIW module.
8-10
The 7 rungs used to configure ENI #2 are defined as follows:

Table 8.3 ENI #2 Configuration - Rung Descriptions Rung 2 3 4 5 Function This rung initiates the process and configures the ENI/ENIW modules Serial port for bridge mode at 38400 Baud. This rung is initiated by the Done bit of the previous MSG and it disables BOOTP. This rung configures the ENI/ENIW with its own IP address. This rung adds the IP address of the SLC 5/05 controller to the ENI/ENIW modules Message Routing table at DF1 node 1. This means that any message sent by the CompactLogix controller with a DF1 destination address of 1, will be sent to the SLC 5/05 controller on Ethernet. This rung adds the IP address of the 1756-ENET module to the ENI/ENIW modules Message Routing table at DF1 node 45. This means that any message sent by the CompactLogix controller with a DF1 destination address of 45, will be sent to the 5550 controller in slot 0, via the 1756-ENET module on Ethernet. This rung adds an e-mail address to the ENI/ENIW modules e-mail routing table at DF1 node 50. This means that any e-mail message sent by the CompactLogix controller with a DF1 destination address of 50 will be sent to this e-mail address. This rung instructs the ENI/ENIW module to save the configuration data sent to it in non-volatile memory.
The following table contains the information needed to send messages to the ENI/ENIW to configure it for this example. For a complete list of ENI/ENIW configurable features, please refer to Chapters 4 and 5.
Table 8.4 ENI #2 Configuration - Message Instructions Parameters Configuration Node Number 101 145 150 248 250 252 253 Configuration Function Configure Route 1 Address Configure Route 45 Address Configure E-mail Address Save/Reset TCP/IP Config. BOOTP Baud Rate Data Type Integers Integers Integers Strings(2) Integer Integer Integer Integer
(1)
Message Node Number 1 45 50 N/A N/A N/A N/A
Message Length (bytes) 8 8 84 5 to 49(2) 2 8 2 2
Message Function Route DF1 MSG to IP at Address 1 Route DF1 MSG to IP at Address 2 Route e-mail message to Address 50 0 = save configuration to flash Assign an IP Address to the ENI/ENIW 1 = disable BOOTP 106 = bridge mode at 38400 Baud
(1) First integer must contain the number of characters (45 maximum) in the e-mail address. The second integer contains the first two ASCII characters of the e-mail address. The third integer contains the next two ASCII characters, and so on, until the complete e-mail address has been entered. All remaining integers in the integer array must be zero. (2) For ENI/ENIW Series B FRN 2.20 or higher, you may use a string variable of length 5 bytes (for 1 character) to 49 bytes (for 45 characters). The first 4 bytes of a CompactLogix string element contains the number of characters in the string (1 to 45).
8-11
The Message Instructions for the CompactLogix controller, Rungs 2 through 8, used to configure the ENI/ENIW module, must be PLC2 Unprotected Write Message Type. The Destination Element can be any valid PLC2 command value. 010 is used in this example because it is the first available valid value. This parameter is not used by the ENI/ENIW, but must be a valid value for RSLogix 5000 to accept it. An example of the MSG Configuration tab and the Communication tab for the MSG instruction used to configure the IP address for the ENI/ENIW (Rung 4) are as follows:
Figure 8.12 ENI #2 Configuration - Message Configuration Tab
8-12
Figure 8.13 ENI #2 Configuration - Message Communication Tab
The MSG length is 8 bytes or 4 integer words. These 4 words contain the IP address for ENI #2 and are stored in tag ENI_IP_VALUE, which is a tag address containing 4 integer words. This is shown in the CompactLogix controllers tag database shown below. On the MSG Instructions Communication tab above, the path is 2,250, where the 2 represents the CompactLogix5320 controllers serial port and the 250 tells the ENI/ENIW module that the 4 words of data contain its IP address. TIP The 2 in the Path shown in the screen above (2, 250) directs the MSG to Channel 0 of the CompactLogix5320 controller. Use 3 for Channel 1 of the CompactLogix5330 controller.
8-13
Figure 8.14 CompactLogix5320 Controllers Tags
As indicated in Table 8.4, the MSGs in Rungs 2, 3 and 8 are 2 bytes or 1 integer word in length. Their Paths are 2,253, 2,252 and 2,248 respectively; where 253 represents Baud Rate, 252 represents BOOTP Enable/Disable, and 248 represents the Save function. The single integer data value for these messages is shown in Table 8.4. 0 is the value for the Save MSG data tag (ENI_SAVE_TO_FLASH_VALUE), which instructs the ENI/ENIW to save its configuration to non-volatile memory. 106 is the value for the Baud Rate MSG data tag (ENI_BAUD_VALUE) which instructs the ENI/ENIW to begin communicating on its RS-232 port at 38400 Baud. 1 is the value to disable BOOTP (BootP_disable_value). As shown in Table 8.4, the MSGs in Rungs 5 and 6 assign IP addresses to node numbers in the ENI/ENIW modules Message Routing Table. These two MSG Instructions are the same as the MSG Instruction in Rung 3, except the paths are 2,101 and 2,145 and the data tags have different names; this time containing the IP addresses of the SLC 5/05 and 1756-ENET module. The MSG in Rung 7, shown in Table 8.4, configures an e-mail address into node 50 of the e-mail table, using a path of 2, 150. For the ENI prior to series B FRN 2.20, the ASCII e-mail address is encoded into an integer array tag of size 42 (INT[41]) as follows:
8-14
1. In element 0 of the integer array, enter the number of ASCII characters in the new e-mail address. 2. Change the radix of element 1 to ASCII. 3. Type in the first two ASCII characters of the e-mail address in single quotes. 4. Change the radix of the next element to ASCII. 5. Type in the next two ASCII characters of the e-mail address in single quotes. 6. Repeat steps 4 and 5 until the entire e-mail address is entered. TIP For an odd number of characters, the last element should look like x$00, where x is the last character in the e-mail address.
7. Leave all remaining elements at zero.

Figure 8.15 Entering an E-mail Address
Enter your CompactLogix ladder program per Rungs 0 through 8 as shown and described above. Be sure to enter your IP addresses for ENI #2, the SLC 5/05, and the 1756-ENET into the proper tags in the controllers tag database. Before saving your program, enter the Controller Properties window by clicking on the Edit pull-down menu and select Controller Properties. Click on the System Protocol tab and change Error Detection from BCC to CRC and the Baud Rate from 19200 to 38400. Click APPLY, then OK. If you fix the baud rate in the ENI/ENIW, it assumes CRC error detection.
8-15
If you do not change this parameter in your CompactLogix controller, it will not be able to communicate with the ENI/ENIW. The Baud Rate of 38400 is being used to increase the upload/download speed. Finally, since Logix controllers do not use the structured data table addressing scheme used by PLC and SLC controllers, we must map file numbers used in the commands sent to any Logix controller to tag names within them. For example, a MSG sent by an SLC 5/05 controller to the CompactLogix controller uses a PLC-5 Typed Write command. The target data table address used is N12:0. This file 12 must be mapped to a valid tag name in the CompactLogix. Since the MSG is 20 integer words in length, a tag in the CompactLogix controller called Data_From_505 was created as a 20 integer word tag. While offline in the CompactLogix controller project, click on the Logic pull-down menu and select Map PLC/SLC Messages. The following screen appears:
Figure 8.16 File Mapping in RSLogix 5000
In the File Number column, enter 12. Under the Tag Name, click on the right side in the white box to reveal your Controller Tags and select the tag name you created for this purpose (Data_From_505 for this example). More than one entry may be mapped. When finished, your Map PLC/SLC screen for the CompactLogix controller should look like the following:
8-16
Figure 8.17 File Mapping for the CompactLogix Controller in RSLogix 5000
Save your program.
Downloading To The CompactLogix Controller Through Two Series A ENIs
The ladder program written for the CompactLogix controller can be downloaded to the controller via the two ENI modules. A full-duplex DF1 driver must be configured in RSLinx to initiate the download through ENI #1. 1. Open RSLinx. 2. Open the configure drivers dialog box. 3. Select RS-232 DF1 devices. Click Add New. 4. Configure AB_DF1-1 driver to match the example below.
8-17
5. Click OK when the AB_DF1-1 driver is configured. 6. If you have set up the ENI Message Routing table with IP addresses in entries between 1 and 31, those devices should respond when you browse the AB_DF1 driver.
Start RSLogix 5000. Open the CompactLogix program created earlier. Click on the Communications pull-down menu and select Who Active. From the Who Active screen. Click on the + sign left of AB_DF1-1, DF1. The CompactLogix controller should appear. Single-click on it to highlight it, then click Download. Your program should download to the controller. You should be online with the controller when the download is complete.
Downloading to the CompactLogix Controller Through a ENI/ENIW Series B/C via Ethernet
In order to download your programs to the CompactLogix controller directly through the ENI/ENIW Series B/C to the SLC 5/05 controller and to the 5550 controller via Ethernet, you must configure an Ethernet driver in RSLinx.
IMPORTANT
You must use RSLinx version 2.31.00 or newer to browse with the 1761-NET-ENI/1761-NET-ENIW Series B/C via Ethernet to a CompactLogix controller.
Follow these steps to configure RSLinx for Ethernet operation.
8-18
1. Open RSLinx and open the driver configuration dialog.
2. The Configure Dialog will open, select Ethernet devices from the available drivers, and then click OK to load the driver into RSLinx.
Once the Ethernet driver is loaded, either highlight and select Configure or simply double click on the Ethernet driver. 3. Click OK to accept the default driver name.
At that point the station mapping screen will appear as illustrated here. Double click on the row below Host Name,
8-19
and enter the TCP/IP addresses that match the devices on your network that you will need access to.
When you are done entering the stations, click OK to close the station mapping window. 4. Open the Who Active screen by clicking on the Communications pull-down menu and selecting Who Active. If your system is properly connected, you should be able to click on the + sign left of the AB_ETH-1 driver you created to establish Ethernet communications with the ENI/ENIW Series B, the 1756-ENET, and the SLC 5/05 controller. The DF1 port is displayed underneath the ENI/ENIW Series B/C. Clicking on the + sign left of the DF1 port should display the CompactLogix controller.
8-20
Close RSWho. Minimize, but do not close, RSLinx.
Create MSG Programs for the SLC 5/05 and the 5550 Controllers
You must create MSG ladder programs for the other two controllers on Ethernet. The following is the MSG ladder program for the SLC 5/05 controller, developed with RSLogix 500. Following the ladder program are four additional screens showing the two tabs for each MSG Instruction. Before saving your program, be sure to configure Channel 1 with its IP address, subnet mask and disable BOOTP. Then, save your program.
Figure 8.18 SLC 5/05 Controller Ladder Program
8-21
Figure 8.19 SLC 5/05 Rung 0 MSG General Tab
Figure 8.20 SLC 5/05 Rung 0 MSG Multihop Tab
8-22
Figure 8.21 SLC 5/05 Rung 1 MSG General Tab
Figure 8.22 SLC 5/05 Rung 1 MSG Multihop Tab
Figure 8.23 on page 8-23 shows the MSG ladder program for the 5550 controller, developed with RSLogix 5000. Following the ladder program are six additional screens showing the two tabs for each MSG Instruction. The third MSG instruction highlights the new functionality of a ENI/ENIW Series B connected to a CompactLogix controller to support the native CIP read and write commands initiated by the ControlLogix 5550. As part of your program, you must configure your 1756-ENET module with the proper IP address.
8-23
Figure 8.23 ControlLogix 5550 Controller Ladder Program
Figure 8.24 ControlLogix 5550 Rung 0 Message Configuration Tab
8-24
Figure 8.25 ControlLogix 5550 Rung 0 Message Communication Tab
8-25
Where PLC_5 Typed Write commands are used, they require a PLC-5 type address to send the data to the receiving controller. Such addresses do not exist in Logix controllers, so they must be mapped to existing tags in these controllers, as described on page 8-26. 1. From the Logic pull down menu, select Map PLC/SLC Messages. Your mapped table for your 5550 program should look like the following:
8-26
Figure 8.30 File Mapping for the ControlLogix 5550 Controller in RSLogix 5000
2. Save your program. 3. From the RSLogix 500 programming software, you should now be able to download your SLC 5/05 program. Then, from the RSLogix 5000 software you should now be able to download your 5550 controller program. 4. Once all programs are downloaded to their respective controllers, place each controller into the RUN mode and a MSG from each controller will be sent to each of the other controllers. Each controller will only send one MSG at any given time. Go online with the CompactLogix, SLC 5/05, and 5550 controllers to verify the successful completion of their Messages.
Chapter
Troubleshooting
This chapter covers the following Troubleshooting topics: Network Troubleshooting Using ENI/ENIW with Routers LED Sequence at Power-Up Troubleshooting Using the LED Indicators Error Codes Generated by the ENI/ENIW
Network Troubleshooting
Maintain ENI/ENIW Cable Connections

The UTP (unshielded twisted pair) patch cable on a switch should be labeled and treated as dedicated. Be careful when moving any cables, as port identity may be effected. If you must move the ENI/ENIW to a new port for any reason, power-cycle the ENI/ENIW. The power cycle forces a new ARP (address resolution protocol) request to be sent which should immediately associate the ENI/ENIWs IP address with the port it is connected to. You should also discourage any field personal from treating the ports of a switch as all the same. This helps to prevent any problems with network communications being effected by moving cables.
Using ENI/ENIW with Routers
In order to use the ENI/ENIW with standard Ethernet routers, you must configure the IP address of the router on the local subnet into the ENI/ENIW Gateway field using either the ENI config utility or controller messaging. See Chapter 4 for details. The target device port or socket number is a required field in the TCP/IP header. When configuring routers, you may need to specify the module port assignment. The CIP inbound port uses 44818. The outbound port assignment varies as the processor makes and breaks connections and binds sockets.
9-2
Troubleshooting
LED Sequence at Power-Up
The following LED test is performed at power-up.

Table 9.1 Series A/B LED Sequence at Power-Up LED Ethernet TX/RX, Link and FAULT FAULT Ethernet TX/RX and FAULT Fault Power-Up Sequence 1. on solid for 2 seconds 2. flashes for 4 seconds 3. on solid for 1/4 second 4. off, unless an error condition exists (see troubleshooting table on page 9-2)
Table 9.2 Series C LED Sequence at Power-Up LED Ethernet TX/RX, Link and FAULT FAULT Ethernet TX/RX and FAULT Fault Power-Up Sequence 1. on solid for 2 seconds 2. flashes for 4 seconds 3. on solid for 1/4 second 4. off, unless an error condition exists (see troubleshooting table on page 9-2)
Troubleshooting Using the LED Indicators

Table 9.3 Series A/B LED Indicators LED RS-232 TX/RX POWER LINK Description RS-232 data transmission indicator module power Ethernet link status Color green
The ENI/ENIW status LEDs provide a mechanism to determine the current status of the ENI/ENIW if a programming device is not present or available. The LED behavior is described in the following table.
State flashing off
Indicates data is being transmitted or received over the RS-232 port no RS-232 traffic module is powered module may not be powered the module detects a valid Ethernet connection the module does not detect a valid Ethernet connection
green green
on off on off
Troubleshooting
9-3
Table 9.3 Series A/B LED Indicators LED Ethernet TX/RX Description Ethernet data transmission indicator Color green State flashing steady flash sequence Indicates During normal operation (Fault LED is off) the Ethernet port is transmitting or receiving NetLinx packets. For example, if you use Ping or Telnet, the Ethernet TX/RX LED will not flash. When the Fault LED is on steady, the Ethernet TX/RX LED flashes the following error codes: ROM Error - 1 flash, then off RAM Error - 2 flashes, then off Net Controller Error - 3 flashes, then off EEPROM error: 4 flashes, then off
Duplicate IP: 5 flashes, then off When the FAULT LED is flashing, the Ethernet TX/RX LED flashes the following error codes: Faulty Network Connection: 4 flashes, then off ENI/ENIW Not Configured: 5 flashes, then off Unspecified Fault: off off FAULT fault condition indicator red on no Ethernet traffic lit when a fault condition is present, possible causes ROM Checksum Error RAM Test Error Network Controller Error EEPROM Checksum Error Duplicate IP (see Ethernet TX/RX LED behavior above for error codes) flashing one of the following: faulty network connection ENI/ENIW does not have a valid IP address off hardware is functioning normally
Table 9.4 Series C LED Indicators LED RS-232 TX/RX POWER LINK Description RS-232 data transmission indicator module power Ethernet link status Color green State flashing off green green on off on off Indicates data is being transmitted or received over the RS-232 port no RS-232 traffic module is powered module may not be powered the module detects a valid Ethernet connection the module does not detect a valid Ethernet connection
9-4
Troubleshooting
Table 9.4 Series C LED Indicators LED Ethernet TX/RX Description Ethernet data transmission indicator Color green State flashing steady flash sequence Indicates During normal operation (Fault LED is off) the Ethernet port is transmitting or receiving NetLinx packets. For example, if you use Ping or Telnet, the Ethernet TX/RX LED will not flash. When the Fault LED is on steady, the Ethernet TX/RX LED flashes the following error codes: ROM Error - 1 flash, then off RAM Error - 2 flashes, then off Net Controller Error - 3 flashes, then off EEPROM error: 4 flashes, then off
Duplicate IP: 5 flashes, then off When the FAULT LED is flashing, the Ethernet TX/RX LED flashes the following error codes: Faulty Network Connection: 4 flashes, then off ENI/ENIW Not Configured: 5 flashes, then off Unspecified Fault: off off FAULT fault condition indicator red on no Ethernet traffic lit when a fault condition is present, possible causes ROM Checksum Error RAM Test Error Network Controller Error EEPROM Checksum Error Duplicate IP (see Ethernet TX/RX LED behavior above for error codes) flashing one of the following: faulty network connection ENI/ENIW does not have a valid IP address off hardware is functioning normally
Troubleshooting
9-5
Error Codes Generated by the ENI/ENIW

Error Code 10H
This table shows the MSG error codes that may be generated by the ENI/ENIW to the connected DF1 device.
Table 9.5 ENI/ENIW-Generated Error Codes Description of Error Condition Target node cannot respond because of incorrect command parameters or unsupported command. Possible causes: 30H D0H The data size of the message is invalid. The data format is incorrect for any of the supported PCCC messages. Register parameters are not formatted correctly, or there is not enough data provided. RS-232 configuration packet data is not the correct size. The Node Address is invalid or out-of-range. The distant ENI/ENIW, controller, or device may not be responding. There may be a break in the connection between the ENI/ENIW devices or controllers. BOOTP/DF1 parameter is invalid.
Target node responded with: Remote station host is not there, disconnected, or shutdown. One of the following: No IP address configured for the network or ENI/ENIW not configured for Node Address used. Bad command - unsolicited message error. Bad address - unsolicited message error. No privilege - unsolicited message error.
9-6
Troubleshooting
Appendix
Specifications
Physical Specifications
Description 24V dc Power Source Requirement 24V dc Current Draw Maximum Inrush Current Internal Isolation Vibration Shock ENI/ENIW Specification 20.4 to 26.4V dc 50 mA typical, 100 mA maximum 200 mA 710V dc for one minute operating: 10 to 500 Hz, 5.0g, 0.030 in. peak-to-peak, 2 hour each axis operating: 30g, 3 times each axis non-operating: 35g (DIN Rail Mount) 50g (Panel Mount), 3 times each axis Operating Ambient Temperature Storage Temperature Humidity Agency Certification(1) 0 C to +60 C (+32 F to +140 F) -40 C to +85 C (-40 F to +185 F) 5% to 95% relative humidity (non-condensing) UL 1604 C-UL C22.2 No. 213 Class I Division 2 Groups A,B,C,D CE compliant for all applicable directives C-Tick marked for all applicable acts Radiated and Conducted Emissions: ESD Immunity (EN 61000-4-2) Radiated Immunity (EN 61000-4-3) Fast Transient Burst (EN 61000-4-4) Surge Immunity (EN 61000-4-5) EN 50081-2, Class A The module has passed testing at the following levels: 4 kV contact, 8 kV air, 4 kV indirect 10V/m, 80 to 1000 MHz, 80% amplitude modulation, and 900 MHz keyed carrier Power supply: 2 kV, 5 kHz RS-232 and Ethernet: 1kV, 5 kHz Power Supply: 500V Ethernet (unshielded cable): 2 kV RS-232 and Ethernet (shielded cable): 1 kV galvanic gun Conducted Immunity (EN 61000-4-6) Power Supply: 10V, 0.15 to 80 MHz RS-232 and Ethernet (unshielded cable): 3V, 0.15 to 80 MHz RS-232 and Ethernet (shielded cable): 10V, 0.15 to 80 MHz
(1) Shielded Ethernet cable required for marine certification.
Ethernet Specifications
Communication Rate: Auto-negotiates 10 Mbps, full- or half-duplex and 100 Mbps, full- or half-duplex Connector: 10/100-Base-T
MicroLogix Web Site
Visit http://www.ab.com/micrologix for more information on MicroLogix products. You can find a variety of application information and White Papers covering specific technical topics.
A-2
Specifications
Dimensions
Product Dimensions
52.07 mm (2.05 in.)
118 mm (4.64 in.)

Mounting Dimensions
107 mm (4.20 in.)
52.07 mm (2.05 in)
27.7 mm (1.09 in.)

Allow 15 mm (0.6 in.) clearance for DIN rail latch movement during installation and removal.
64.8 mm (2.55 in.)
118 mm (4.64 in)
107 mm (4.20 in)
27.7 mm (1.09 in)
Allow 15 mm (0.6 in.) clearance for DIN rail latch movement during installation and removal.
Appendix
BOOTP Configuration Method (default)
BOOTP (Bootstrap protocol) is a low-level protocol that provides configuration information to other nodes on a TCP/IP network with DOS, Microsoft Windows, Windows NT, Windows 9x, VMS, and HP-UNIX platforms. BOOTP configuration files let you automatically assign IP addresses to the ENI/ENIW. You can also set Subnet Masks and Gateway addresses using BOOTP. To use BOOTP, a BOOTP Server must exist on the local Ethernet Subnet. The server is a computer that has BOOTP Server software installed and running which reads a text file containing network information for individual nodes on the network.
TIP
If you do not have BOOTP Server capabilities on your network, and you want to dynamically configure the ENI/ENIW, you can download the Rockwell Automation BOOTP Utility from www.ab.com/networks/bootp/index.html.
When the ENI/ENIW receives a configuration message via BOOTP, it uses the data within the message to configure its TCP/IP parameters.
Table B.1 TCP/IP Parameters Function IP Address Format Integer Notes This is a unique IP Address for the ENI/ENIW. Format is aaa.bbb.ccc.ddd. Default is 000.000.000.000. If not sent, the default mask is derived from the class of the IP address. See page 4-13 for more information on the subnet mask. Only needed if a Gateway is present on the Subnet. Default is 000.000.000. The default is no security mask 000.000.000.000. See page 4-13 for more information on the Security Mask.
Subnet Mask
optional(1)
Gateway Security Mask 1 Security Mask 2
optional(1) Zero
(1) Depending upon whether your BOOTP server allows these optional fields to be included, you might not be able to configure these parameters. If that is the case, configure them using the soft configuration method. See page 4-1 for more information. If you do not need to define a Subnet Mask or Gateway, simply ignore these parameters.
B-2
When BOOTP is enabled, the following events occur at power-up: The ENI/ENIW broadcasts a BOOTP-request message containing its hardware address over the local network or subnet. The BOOTP server compares the hardware address with the addresses in its look-up table. The BOOTP server sends a message back to the ENI/ENIW with the IP address and other network information that corresponds to the hardware address it received. With all hardware and IP addresses in one location, you can easily change IP addresses in the BOOTP configuration file if your network needs change. The ENI/ENIW allows the BOOTP request to be disabled by clearing the BOOTP Enable parameter. See Node 252 - BOOTP Configuration on page 4-15.
Using the Rockwell BOOTP Utility
The Rockwell BOOTP utility is a standalone program that incorporates the functionality of standard BOOTP software with a user-friendly graphical interface. It is located in the Utils directory on the RSLogix 5000 installation CD. It can also be downloaded from www.ab.com/networks/bootp/index.html web page. The device must have BOOTP enabled (factory default) to use the utility. To configure your device using the BOOTP utility, perform the following steps: 1. Run the BOOTP software. In the BOOTP Request History panel you will see the hardware addresses of devices issuing BOOTP requests.
B-3
2. Double-click on the hardware address of the device you want to configure. You will see the New Entry pop-up window with the device's Ethernet Address (MAC).
3. Enter the IP Address, Subnet Mask, and Gateway you want to assign to the device, and click on OK. The device will be added to the Relation List, displaying the Ethernet Address (MAC) and corresponding IP Address, Subnet Mask, and Gateway (if applicable).
Does not apply to ENI/ENIW
B-4
Using DCHP Software To Configure Your ENI/ENIW
DHCP software automatically assigns IP addresses to client stations logging onto a TCP/IP network. DHCP is based on BOOTP and maintains some backward compatibility. The main difference is that BOOTP was designed for manual configuration, while DHCP allows for dynamic allocation of network addresses and configurations to newly attached devices. Be cautious about using DHCP software to configure your ENI/ENIW. A BOOTP client can boot from a DHCP server only if the DHCP server is specifically written to also handle BOOTP queries. This is specific to the DHCP software package you use. Check with your system administrator to see if your DHCP package supports BOOTP commands and manual IP allocation. The ENI/ENIW must be assigned a fixed network address. The IP address of the ENI/ENIW must not be dynamically provided. Failure to observe this precaution may result in unintended machine motion or loss of process control.
ATTENTION
Glossary
ASA (Advanced System Architecture) Autobaud A feature that allows a communications port to automatically synchronize to the device or network that it is attached to. This feature typically minimizes the amount of configuration required, and also makes is easier to replace devices. Auto BCC/CRC Sends a test message during autobaud to detect which Error Detecting setting to use, BCC or CRC. This will not occur for fixed baud rate settings. The ENI/ENIW uses CRC for fixed baud rates. Baud Rate The speed of communication between devices on a network. All devices must communicate at the same baud rate. For example, the DH-485 network devices default to 19,200 baud. CIP (Control and Information Protocol) DHCP (Dynamic Host Configuration Protocol) DNI (DeviceNet Network Interface) Allen-Bradley catalog number 1761-NET-DNI. The DNI allows you to connect DF1 devices to DeviceNet networks. DF1 Full-Duplex DF1 is a standard (open) point-to-point communication protocol. Virtually all Allen-Bradley controllers (PLC-3, PLC-5, SLC, MicroLogix) that have an RS-232 communications port support DF1. DF1 Protocol A peer-to-peer link-layer protocol that combines features of ANSI X3.28-1976 specification subcategories D1 (data transparency) and F1 (two-way simultaneous transmission with embedded responses). ENI (Ethernet Network Interface) Allen-Bradley catalog number 1761-NET-ENI and 1761-NET-ENIW. The ENI allows you to connect DF1 devices to Ethernet networks. The ENIW adds web server capabilities.
Glossary
Ethernet Network A local area network with a baseband communication rate of 10M bits per second. Full-duplex A high-performance protocol that allows simultaneous two-way data transmission. For point-to-point applications only. IP (Internet Protocol) IP specifies the format of packets and the addressing scheme. Most networks combine IP with a higher-level protocol called Transport Control Protocol (TCP), which establishes a virtual connection between a destination and a source. IP by itself is something like the postal system. It allows you to address a package and drop it in the system, but there's no direct link between you and the recipient. TCP/IP, on the other hand, establishes a connection between two hosts so that they can send messages back and forth for a period of time. IP Address A 32-bit address assigned to hosts that want to participate in a TCP/IP internet. IP addresses are the abstraction of physical hardware addresses, with a network and host partition which makes routing efficient. NetLinx Services The NetLinx services occur over the well-known port 0xAF12 and define a connection protocol that exists after a TCP/IP connection is established. It also defines a set of services and packet formats to support the protocol. Also implied by this protocol is that the end devices have implemented some portion of the ASA CIP addressing architecture. Network A series of stations (nodes) connected by some type of communication medium. A network may be made up of a single link or multiple links. Node Also called a station. An address or software location on the network.
Glossary
MTA (Mail Transfer Agent) The software function responsible for delivering outgoing mail to its final destination. PCCC (Programmable Controller Communications Commands) RS-232 An EIA standard that specifies electrical, mechanical, and functional characteristics for serial binary communication circuits. Security Mask The Security Mask, when configured, allows you to restrict incoming TCP/IP and/or UDP messages to have source IP addresses that are within some prescribed range. For example, if you wanted to restrict all message sources to be from within a companys allocated IP address range, a Security Mask could be configured that would block any IP address outside that range. SMTP (Simple Mail Transfer Protocol) This protocol defines the interface and commands with the Mail Transfer Agent and defines how the ENI/ENIW will deliver the outgoing mail. Single-Hop/ Multi-Hop Term that refers to how many different networks a message must traverse to reach its destination. For the ENI/ENIW, a single-hop message is one whose source and destination nodes are both TCP/IP end points. TCP (Transmission Control Protocol) TCP is one of the main protocols in TCP/IP networks. Whereas the IP protocol deals only with packets, TCP enables two hosts to establish a connection and exchange streams of data. TCP guarantees delivery of data and also guarantees that packets will be delivered in the same order in which they were sent. TCP/IP (Transmission Control Protocol/Internet Protocol) The suite of communications protocols used to connect hosts on the Internet. TCP/IP uses several protocols, the two main ones being TCP and IP. TCP/IP is built into the UNIX operating system and is used by the Internet, making it the de facto standard for transmitting data over networks. Even network operating systems that have their own protocols, such as Netware, also support TCP/IP.
Glossary
UCMM (Unconnected Message Manager) The UCMM is an object defined in the CIP protocol. This object is responsible for handling connection requests and unconnected message traffic. UTP (Unshielded Twisted Pair) The type of cable used in 10BaseT systems.
Index
A
ASA definition Glossary-1 Auto BCC/CRC definition Glossary-1 Autobaud CRC with bridge function 4-16 definition Glossary-1 restrictions 4-16 Auto-Refresh 7-11 Dimensions A-2 DNI definition Glossary-1
E
EDS file download 3-6 E-Mail Message Fields 6-4 E-Mail Messages 6-1 E-Mail Server 4-15 E-Mail, sending a message 6-5 EMC Directive 2-1 ENI configuration 4-1 definition Glossary-1 functional overview 3-2 LED indicators 1-2 operating modes 1-4 operation 3-1 overview 1-1 port identification 2-5 product drawing 1-2 ENI Configuration Utility 4-1 Ethernet Connections 2-5 Ethernet Hardware Address 4-17 Ethernet Network connections 1-5 definition Glossary-2 ENI connection 1-1 example 8-1 Ethernet Port 1-2 event.html description 7-5 displaying data 7-13 Example using the CompactLogix serial port to connect to an Ethernet network 8-1 Explosion Hazard 2-2
B
Baud Rate configuring 4-16 definition Glossary-1 with bridge function 4-16 BOOTP Configuration 4-15, B-1
C
Cables 2-2, 2-6, 2-7 CE Mark 2-1 CIP definition Glossary-1 Common Techniques Used in this Manual P-2 Compatibility 1-4 Configuration 4-1 BOOTP 4-15 controller messaging 4-5 e-mail 6-2 list of parameters 4-10 via BOOTP B-1 via message instruction 5-2 Configuration Utility 4-1 Connections allocation of Ethernet connections 3-1 Ethernet switch 2-6
D
DF1 Full-Duplex definition Glossary-1 messaging 5-1 DF1 Protocol default settings 1-4 definition Glossary-1 DHCP definition Glossary-1 software for ENI configuration B-4 DHCP configuration 4-15
F
Fault LED 1-2, 1-3 From String 4-11, 6-2 Full-Duplex definition Glossary-2
G
Grounding 2-3
H
Index
Hardware Address 1-2, 4-17 Hardware Features 1-2 Hazardous Location 2-2 home.html 7-2
I
index.html 7-2 Installation and Wiring 2-1 Integer Files 4-6 IP definition Glossary-2 IP Address assigning 1-3 definition Glossary-2 ENI write-on area 1-2
L
LED Indicators 1-2 LED Sequence at Power-Up 9-2 LInk LED 1-2 Low Voltage Directive 2-1
M
Manuals, Related P-2 Memory Map 3-2 Messaging 4-5, 5-1 Mounting 2-3 dimensions A-2 MTA definition Glossary-3
displaying data 7-6 posting data 7-12 page2.html data table addresses 7-13 description 7-4 displaying data 7-6 posting data 7-12 page3.html data table addresses 7-13 description 7-4 displaying data 7-6 posting data 7-12 page4.html data table addresses 7-13 description 7-4 displaying data 7-6 posting data 7-12 Password Protection disabling device update 7-12 Password-Protection removing 7-12 PCCC definition Glossary-3 Peer Connections 3-1 Peer-to-Peer Messaging 5-1 Posting Data 7-12 Power LED 1-2, 1-3 Power Supply Wiring 2-3 Product Overview 1-1 Publications, Related P-2 Purpose of this Manual P-1
R
reference.html 7-3 Related Publications P-2 RS-232 cables 2-7 connector 2-7 default settings 1-4 definition Glossary-3 ENI port 1-2 pin assignments 2-7 RSLinx 3-4
N
Netlinx Services definition Glossary-2 Network definition Glossary-2 Node definition Glossary-2
O
Operating Modes 1-4 Operation 3-1
S
Safety Considerations 2-2 Save/Reset 4-11 Security Mask 4-13 definition Glossary-3 Single-Hop
P
page1.html data table addresses 7-13 description 7-4
Index
definition Glossary-3 SMTP definition Glossary-3 SMTP E-Mail Address 6-2 Specifications A-1 String Files 4-8 Subnet Mask 4-13
U
UCMM definition Glossary-4 URL links defining 7-5 on home.html 7-2 unused links 7-6 UTP definition Glossary-4
T
TCP definition Glossary-3 TCP/IP configuration 4-12 definition Glossary-3 Troubleshooting maintain ENI connnections 2-6 procedure 9-1 TX/RX LED 1-2, 1-3
W
Web Browser Compatibility 7-1 Web Server file types supported 7-1 Wiring 2-1
Index
Rockwell Automation Support
Rockwell Automation provides technical information on the web to assist you in using our products. At http://support.rockwellautomation.com, you can find technical manuals, a knowledge base of FAQs, technical and application notes, sample code and links to software service packs, and a MySupport feature that you can customize to make the best use of these tools. For an additional level of technical phone support for installation, configuration and troubleshooting, we offer TechConnect Support programs. For more information, contact your local distributor or Rockwell Automation representative, or visit http://support.rockwellautomation.com.
Installation Assistance
If you experience a problem with a hardware module within the first 24 hours of installation, please review the information that's contained in this manual. You can also contact a special Customer Support number for initial help in getting your module up and running: United States Outside United States 1.440.646.3223 Monday Friday, 8am 5pm EST Please contact your local Rockwell Automation representative for any technical support issues.
New Product Satisfaction Return

Rockwell tests all of our products to ensure that they are fully operational when shipped from the manufacturing facility. However, if your product is not functioning and needs to be returned: United States Contact your distributor. You must provide a Customer Support case number (see phone number above to obtain one) to your distributor in order to complete the return process. Please contact your local Rockwell Automation representative for return procedure.
Outside United States
Allen-Bradley and MicroLogix are trademarks of Rockwell Automation. Microsoft is a registered trademark of Microsoft Corporation. Netscape is a registered trademark of Netscape Communications Corporation.
Publication 1761-UM006D-EN-P - March 2004 2

Supersedes Publication 1761-UM006C-EN-P - June 2003
PN XXXXXX-XX
Copyright 2004 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.

Net Eni

Uploaded by

Copyright:

Available Formats

Net Eni

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Net Eni

Uploaded by

Copyright:

Available Formats

MicroLogix Ethernet Interface

1761-NET-ENI and 1761-NET-ENIW

Important User Information

Publication 1761-UM006D-EN-P - March 2004

Publication 1761-UM006D-EN-P - March 2004

Chapter 1 Product Overview

Chapter 2 Installation and Wiring

Publication 1761-UM006D-EN-P - March 2004

Chapter 4 ENI/ENIW Configuration (Nodes 248 to 254)

Chapter 5 Peer-to-Peer Messaging

Publication 1761-UM006D-EN-P - March 2004

Chapter 6 E-Mail Messages (Node 50 to 99)

Publication 1761-UM006D-EN-P - March 2004

Chapter 8 Connecting CompactLogix Controllers on Ethernet

Appendix B BOOTP Configuration Method (default)

Publication 1761-UM006D-EN-P - March 2004

Who Should Use this Manual

Purpose of this Manual

Publication 1761-UM006D-EN-P - March 2004

Document Number 1761-IN007 1770-6.5.16 ENET-IN001 1770-4.1

Common Techniques Used in this Manual

Publication 1761-UM006D-EN-P - March 2004

Rockwell Automation Support

New Product Satisfaction Return

Outside United States

Publication 1761-UM006D-EN-P - March 2004

Your Questions or Comments on this Manual

Publication 1761-UM006D-EN-P - March 2004

Publication 1761-UM006D-EN-P - March 2004

Ethernet Hardware Address

LISTED IND.CONT.EQ. FOR HAZ.

US LOC. A196 TEMPERATURE CODE T3C OPERATING

IP Address Write-On Area

Table 1.1 Series A/B Descriptions: LED

Color green green green green red

TX/RX POWER LINK TX/RX

fault condition indicator lit when a fault condition is present

Publication 1761-UM006D-EN-P - March 2004

Table 1.2 Series C Descriptions:

Color flashing green off green off amber

For more detailed information on LED operation, see Chapter 9, Troubleshooting.

Publication 1761-UM006D-EN-P - March 2004

Publication 1761-UM006D-EN-P - March 2004

Basic Ethernet Topology

Publication 1761-UM006D-EN-P - March 2004

RJ45 connectors on both ends of cable (10/100 Base-T)

to PC Ethernet Card or other Ethernet Device

Web Server Functionality

Publication 1761-UM006D-EN-P - March 2004

Installation and Wiring

European Communities (EC) Directive Compliance

Low Voltage Directive

Publication 1761-UM006D-EN-P - March 2004

Installation and Wiring

Environment Classification Class I, Division 2 Hazardous Environment

Publication 1761-UM006D-EN-P - March 2004

Installation and Wiring

External Power Supply Wiring