Rockwell Automation 1756-ENET-B User Manual
ControlLogix
Ethernet
Communication
Interface Module
1756-ENET/B
User Manual
Important User Information
Because of the variety of uses for the products described in this
publication, those responsible for the application and use of this
control equipment must satisfy themselves that all necessary steps
have been taken to assure that each application and use meets all
performance and safety requirements, including any applicable laws,
regulations, codes and standards.
The illustrations, charts, sample programs and layout examples shown
in this guide are intended solely for purposes of example. Since there
are many variables and requirements associated with any particular
installation, Allen-Bradley does not assume responsibility or liability
(to include intellectual property liability) for actual use based upon
the examples shown in this publication.
Allen-Bradley publication SGI-1.1, Safety Guidelines for the
Application, Installation and Maintenance of Solid-State Control
(available from your local Allen-Bradley office), describes some
important differences between solid-state equipment and
electromechanical devices that should be taken into consideration
when applying products such as those described in this publication.
Reproduction of the contents of this copyrighted publication, in whole
or part, without written permission of Rockwell Automation, is
prohibited.
Throughout this manual we use these notes to make you aware of
safety considerations:
WARNING
Identifies information about practices or
circumstances that have the potential to create an
explosion hazard.
!
ATTENTION
Identifies information about practices or
circumstances that can lead to personal injury or
death, property damage or economic loss.
!
Warning and Attention statements help you to:
identify a hazard
•
avoid a hazard
•
recognize the consequences
•
IMPORTANT
Allen-Bradley and ControlLogix are trademarks of Rockwell Automation.
Ethernet is a trademark of Digital Equipment Corporation, Intel, and Xerox Corporation.
RSLinx and RSLogix 5000 are trademarks of Rockwell Software.
Windows 95/98 and Windows NT are trademarks of Microsoft Corporation.
Identifies information that is critical for successful
application and understanding of the product.
European Communities (EC) Directive Compliance
If 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
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,
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.
Rockwell Automation Support
Rockwell Automation offers support services worldwide, with over 75
sales/support offices, 512 authorized distributors and 260 authorized
systems integrators located throughout the United States alone, as well
as Rockwell Automation representatives in every major country in the
world.
Local Product Support
Contact your local Rockwell Automation representative for:
sales and order support
•
product technical training
•
warranty support
•
support service agreements
•
Technical Product Assistance
If you need to contact Rockwell Automation for technical assistance,
call your local Rockwell Automation representative, or call Rockwell
directly at: 1 440 646-6800.
For presales support, call 1 440 646-3NET.
You can also obtain technical assistance online from the following
Rockwell Automation WEB sites:
www.ab.com/mem/technotes/kbhome.html
•
www.ab.com/networks/eds
•
(electronic data sheets)
(knowledge base)
Your Questions or Comments on this Manual
If you find a problem with this manual, please notify us of it on the
enclosed Publication Problem Report.
About This User Manual
Preface
What this Preface Contains
Who Should Use This Manual
This preface describes how to use this manual. The following table
describes what this preface contains and where to find specific
information.
For information about See page
Who Should Use This Manual P-1
Common Techniques Used in This Manual P-2
How To Use This Manual P-2
About the Example Applications P-3
System Components P-4
Where to Find More Information P-5
Terminology P-6
This manual is intended for control engineers and technicians who are
installing, programming, and maintaining a control system that
communicates on an Ethernet network through a 1756-ENET/B
module.
We assume you have a good understanding of Ethernet and the
(TCP/IP) protocol. This user manual contains a brief description of
Ethernet and TCP/IP in Chapter 3. For detailed information on TCP/IP
protocol and networking in general, see the following publications:
Comer, Douglas E. Internetworking with TCP-IP, Volume 1:
•
Protocols and Architecture, 2nd ed. Englewood Cliffs, N.J.:
Prentice-Hall, 1995. ISBN 0-13-216987-8.
Tanenbaum, Andrew S. Computer Networks, 2nd ed.
•
Englewood Cliffs, N.J.: Prentice-Hall, 1989. ISBN 0-13-162959-X.
1 Publication 1756-UM051B-EN-P - November 2000
P-2 About This User Manual
Common Techniques Used in This Manual
The following conventions are used throughout this manual:
Bulleted lists provide information, not procedural steps.
•
Numbered lists provide sequential steps.
•
Information in bold contained within text identifies menu
•
windows, or screen options, screen names and areas of the
screen, such as dialog boxes, status bars, radio buttons and
parameters.
TIP
This is a definition
box. When a word is
bold within the text
of a paragraph, a
definition box will
appear in the left
margin to further
define the text.
This symbol identifies helpful tips.
A definition box defines terms that may be
unfamiliar to you.
How To Use This Manual
Screen captures are pictures of the software’s
actual screens. The names of screen buttons and
fields are often in bold in the text of a
procedure. Pictures of keys represent the actual
keys you press.
This manual provides an overview of the 1756-ENET/B module, as
well as general information about Ethernet. It describes how to install
and configure the module, and provides three example applications
showing how to use the module to communicate over Ethernet.
The example applications are intended as building blocks to help you
get your own network up and running. We recommend that you set
up and run the example applications and use them as a guide for
setting up your own system.
Publication 1756-UM051B-EN-P - November 2000
About This User Manual P-3
About the Example Applications
The example applications presented in this manual are as follows:
Rack Optimized I/O (chapter 5)
•
Using Analog I/O with Direct Connection (chapter 6)
•
Produced and Consumed tags (chapter 7)
•
Here’s an example of the type of system you’ll be creating for I/O
applications:
Slot 0 1 Slot 0 1 2 3
Local
Chassis
Logix5550
Controller
1756-ENET/B
130.130.130.2
130.130.130.1
Data
Switch
1756-ENET/B
130.130.130.3
Programming
Ter mi na l
Remote
Chassis
1756-OF8
Analog Output
1756-OB16I
Digital Output
1756-IB16I
Digital Input
Publication 1756-UM051B-EN-P - November 2000
P-4 About This User Manual
System Components
We used the following components for the example applications:
Quantity Product Name Catalog Number
Hardware
2 ControlLogix chassis 1756-A4, (or -A7, -A13, -A13, -A17)
2 ControlLogix power supply 1756-PA72, (or -PB72)
2 Ethernet Communications Interface Module 1756-ENET/B
2 Logix5550 controller 1756-L1
1 Analog Output Module 1756-OF8
1 Digital Input Module 1756-IB16I
1 Digital Output Module 1756-0B16I
1 Personal computer that supports RSLogix
5000 software
1 Ethernet switch Refer to manufacturer’s
Associated media and connectors as needed
Software
1 RSLinx 9355-WAB, -WABOEM, -WABC
1 RSLogix 5000 programming software 9324-RLD300ENE
Any appropriate model running
Windows NT 4.0, Service Pack 5 or
higher
specifications
Publication 1756-UM051B-EN-P - November 2000
About This User Manual P-5
Where to Find More Information
For information about See this publication Publication number
Using Ethernet for Industrial Control Ethernet/IP Performance and Application Guide ENET-AP001A-EN-P
Ethernet Media Ethernet/IP Cable Planning and Installation Guide ENET-IN001A-EN-P
1756-ENET/B module ControlLogix Ethernet Communication Module Installation
ControlLogix Chassis ControlLogix Chassis Installation instructions 1756-5.69 (Series A)
ControlLogix power supplies ControlLogix Power Supplies Installation Instructions 1756-5.67 (PA72/PB72)
Logix5550 programmable controllers Logix5550 Controller User Manual 1756-6.5.12
ControlLogix Analog I/O modules ControlLogix Analog I/O Users Manual 1756-6.5.9
ControlLogix Digital I/O modules ControlLogix Digital I/O Users Manual 1756-6.5.8
RSLogix 5000 programming software Getting Results with RSLogix5000 9399-RLD300GR
RSLinx Lite software RSLinx Lite User’s Guide 9399-WAB32LUG
Refer to the following Rockwell publications as needed for additional help
when setting up and using your network.
1756-IN015B-EN-P
Instructions
1756-5.80 (Series B)
1756-5.78 (PA75/PB75)
TIP
Many of the above publications are available online
from the Automation Bookstore:
TIP
http://www.theautomationbookstore.com
.
For more information about Rockwell Software
products, visit the Rockwell Software internet site:
http://www.software.rockwell.com
.
Publication 1756-UM051B-EN-P - November 2000
P-6 About This User Manual
Terminology
This term Means
bandwidth The transmission capacity of the network, expressed in bits per
second. Traditional Ethernet has a 10Mbit bandwidth. Fast
Ethernet is 100Mbit.
BootP BootP (Bootstrap Protocol) is a low-level protocol that provides
configurations to other nodes on a TCP/IP network. BootP
configuration files let you automatically assign IP addresses to
an Ethernet module (you can also obtain subnet masks and
gateway addresses from BootP).
The Ethernet module factory default is BootP enabled. Upon
powerup, the module sends a message containing its hardware
address to the BootP server on the network. The server is a
computer with BootP server software installed. The server
compares that hardware address to those in its lookup table in
the configuration file and sends a message back to the module
with the appropriate IP address.
bridge An internetwork node between two similar communication
subnets where protocol translation is minimal.
CIP Control and Information Protocol, the Ethernet/IP application
layer. CIP uses the “producer/consumer” networking model. In
this model one producer broadcasts (multicasts) the data once to
all the consumers. All consumers see the data simultaneously,
and may choose whether to consume (receive) the data or not.
Delivery time is consistent, no matter how many consumers
there are.
consumer A destination device in the CIP networking model. See CIP.
CSMA/CD Carrier Sense Multiple Access/Collision Detection. The access
method used in Ethernet. When a device wants to gain access to
the network, it checks to see if the network is quiet (senses the
carrier). If it is not, it waits a random amount of time before
retrying. If the network is quiet and two devices access the line
at exactly the same time, their signals collide. When the
collision is detected, they both back off and each waits a
random amount of time before retrying.
determinism The ability to predict when information will be delivered.
Important in time critical applications.
DHCP The Dynamic Host Configuration Protocol (DHCP) is an Internet
protocol, similar to BootP, for automating the configuration of
computers that use TCP/IP. DHCP can be used to automatically
assign IP addresses, to deliver TCP/IP stack configuration
parameters such as the subnet mask and default router, and to
provide other configuration information such as the addresses
for printer, time and news servers.
DNS The Domain Name System (DNS) is a hierarchical, distributed
method of organizing the name space of the Internet. The DNS
administratively groups hosts into a hierarchy of authority that
allows addressing and other information to be widely distributed
and maintained. A big advantage to the DNS is that using it
eliminates dependence on a centrally-maintained file that maps
host names to addresses.
Ethernet
A physical layer standard using Carrier Sense Multiple Access with
Collision Detection (CSMA/CD) methods.
Publication 1756-UM051B-EN-P - November 2000
About This User Manual P-7
This term Means
Ethernet network A local area network designed for the high-speed exchange of
information between computers and related devices.
Ethernet/IP
Ethernet Industrial Protocol. Ethernet/IP
applies a common
application layer (CIP) over Ethernet by encapsulating
messages in TCP/UDP/IP.
explicit messaging
Non-time critical messaging used for device configuration
and data collection, such as downloading programs or
peer-to-peer messaging between two PLCs.
fast Ethernet Ethernet operating at 100Mbps/second.
full duplex A mode of communication that allows a device to send and
receive information at the same time, effectively doubling the
bandwidth.
fully qualified
domain name
gateway A module or set of modules that allows communications
A Fully Qualified Domain Name (FQDN) is a domain name that
includes all higher level domains relevant to the entity named. If
you think of the DNS as a tree-structure with each node having
its own label, a Fully Qualified Domain Name for a specific node
would be its label followed by the labels of all the other nodes
between it and the root of the tree. For example, for a host, a
FQDN would include the string that identifies the particular host,
plus all domains of which the host is a part up to and including
the top-level domain (the root domain is always null). For
example, PARIS.NISC.SRI.COM is a Fully Qualified Domain
Name for the host at 192.33.33.109.
between nodes on dissimilar networks.
host name The Host Name is the unique name for a computer within its
domain. It’s always the first element of a full name, and, with its
domain and top-level domain suffix, creates the unique name of
that computer on the Internet. For example, let’s say the foobar
website is www.foobar.com. The Host Name is “www”, which
is not unique on the web, but is unique within the foobar
domain.
The Host Name can also refer to the Fully Qualified Domain
Name, or in this example, www.foobar.com. Both naming
methods seem to be used interchangeably in various documents.
For the purposes of this document, the Host Name will refer to
the FQDN, or as in this example, www.foobar.com.
hub A central connecting device that joins devices together in a star
configuration. Hubs are generally not suitable for use in I/O
control systems, since they are time critical applications that
cannot tolerate lost packets.
implicit messaging Real time messaging of I/O data.
IP
Internet Protocol that
provides the routing mechanism for
messages. All messages contain not only the address of
the destination station, but the address of a destination
network, which allows messages to be sent to multiple
networks within an organization or around the world.
Publication 1756-UM051B-EN-P - November 2000
P-8 About This User Manual
This term Means
IP address 32-bit identification number for each node on an Internet
Protocol network. These addresses are represented as four sets
of 8-bit numbers (numbers from 0 to 255), with periods between
them. Each node on the network must have a unique IP address.
latency The time between initiating a request for data and the beginning
of the actual data transfer.
module address A six-bit number used to uniquely identify any module on the
local and extended ControlLogix backplane.
multicast In the CIP producer/consumer model one producer multicasts
(broadcasts) the data once to all the consumers.
producer The source of information in the CIP networking model. See CIP.
rack A physical and logical collection of application modules sharing
a common power supply and backplane for module to module
communication.
star configuration A network configuration in which the devices are connected to a
central hub or switch.
subnet mask An extension of the IP address that allows a site to use a single
net ID for multiple networks.
switch A network device that cross connects devices or network
segments. A switch provides each sender/receiver the full
network bandwidth (2x in full duplex mode), reduces collisions,
and increases determinism.
TCP Transport Control Protocol. More reliable but slower transport
protocol than UDP. Used for explicit (not time critical) messaging
in Ethernet/IP.
TCP/IP Transmission Control Protocol/Internet Protocol (TCP/IP). A
transport-layer protocol (TCP) and a network-layer protocol (IP)
commonly used for communication within networks and across
internetworks.
transaction An exchange of request and data and response and data
UDP
User Datagram Protocol. Transport protocol that provides a
.
very simple, but fast capability to send datagrams
between two devices. Used for I/O (implicit) messaging in
Ethernet/IP.
Publication 1756-UM051B-EN-P - November 2000
About the 1756-ENET/B Module
Installing the Ethernet Module
Table of Contents
Chapter 1
What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Module Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Hardware/Software Compatibility . . . . . . . . . . . . . . . . . . . . . . 1-2
What the Module Does. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Support of Rack Optimized and Direct Connections. . . . . . . . . 1-2
Mixing Rack Optimized and Direct Connections. . . . . . . . . 1-3
Use of the Control and Information Protocol (CIP) . . . . . . . . . 1-4
Understanding the Producer/Consumer Model. . . . . . . . . . . . . 1-4
Specifying the Requested Packet Interval (RPI) . . . . . . . . . . . . 1-5
What’s Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Chapter 2
What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Identifying Module Features . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Insertion and Removal Under Power. . . . . . . . . . . . . . . . . . . . 2-2
Installing the Ethernet Module . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Preparing the Chassis for Module Installation. . . . . . . . . . . 2-2
Determining Module Slot Location. . . . . . . . . . . . . . . . . . . 2-3
Inserting the Module in the Chassis . . . . . . . . . . . . . . . . . . 2-4
Removing or Replacing the Module (when applicable). . . . 2-5
Wiring the Ethernet Connector . . . . . . . . . . . . . . . . . . . . . 2-6
Connecting the Module to the Ethernet Network . . . . . . . . 2-6
Applying Chassis Power . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Checking Power Supply and Module Status . . . . . . . . . . . . 2-8
What’s Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Chapter 3
Before You Configure Your
Module
i Publication 1756-UM051B-EN-P - November 2000
What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Ethernet Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Transmission Control Protocol/Internet Protocol (TCP/IP) . 3-1
User Datagram Protocol (UDP) . . . . . . . . . . . . . . . . . . . . . 3-2
Ethernet/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Simple Network Management Protocol (SNMP) . . . . . . . . . 3-2
Configuring the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Subnet Masks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
For More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
What’s Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Table of Contents ii
Configuring the Ethernet Module
Rack Optimized I/O
Chapter 4
What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Using the Rockwell BootP Utility . . . . . . . . . . . . . . . . . . . . . . 4-1
Using RSLinx Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Using a BootP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Using DHCP Software to Configure Your Module . . . . . . . . . . 4-7
What’s Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Chapter 5
About the Example Application . . . . . . . . . . . . . . . . . . . . . . . 5-1
Set Up the Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Create the Example Application . . . . . . . . . . . . . . . . . . . . . . . 5-3
Add the Local Ethernet Module to the I/O Configuration . . 5-4
Add the Remote Ethernet Module to the I/O Configuration. 5-6
Add the Remote I/O Modules to the I/O Configuration . . . 5-8
Add the Remote Digital Input Module . . . . . . . . . . . . . 5-8
Add the Remote Digital Output Module . . . . . . . . . . . 5-10
Edit the Controller Tags . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Create the Ladder Program . . . . . . . . . . . . . . . . . . . . . . . 5-14
Download the Program to the Controller . . . . . . . . . . . . . 5-15
Test the Example Application . . . . . . . . . . . . . . . . . . . . . . . . 5-16
What’s Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Analog I/O with Direct Connection
Produced and Consumed Tags
Chapter 6
About the Example Application . . . . . . . . . . . . . . . . . . . . . . . 6-1
Set Up the Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Create the Example Application . . . . . . . . . . . . . . . . . . . . . . . 6-3
Add the Remote Analog I/O Module
to the I/O Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Edit the Controller Tags . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
Modify the Ladder Program. . . . . . . . . . . . . . . . . . . . . . . 6-10
Download the Program. . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Test the Example Application . . . . . . . . . . . . . . . . . . . . . . . . 6-12
What’s Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
Chapter 7
About the Example Application . . . . . . . . . . . . . . . . . . . . . . . 7-1
Set Up the Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Create the Producer Application . . . . . . . . . . . . . . . . . . . . . . . 7-3
Create the Producer Tags . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Create the Producer Ladder Program . . . . . . . . . . . . . . . . . 7-6
Download the Producer Application . . . . . . . . . . . . . . . . . 7-7
Create the Consumer Application . . . . . . . . . . . . . . . . . . . . . . 7-8
Create the Consumer Controller. . . . . . . . . . . . . . . . . . . . . 7-8
Add the Producer to the Consumer’s I/O Configuration . . . 7-9
Add the Local ENET/B Module
to the I/O Configuration . . . . . . . . . . . . . . . . . . . . . . . 7-9
Publication 1756-UM051B-EN-P - November 2000
LED Status Indicators
1756-ENET/B Module Web Pages
Table of Contents iii
Chapter 7 (continued)
Add the Remote ENET/B Module
to the I/O Configuration . . . . . . . . . . . . . . . . . . . . . . 7-11
Add the Remote (Producer) Controller
to the I/O Configuration . . . . . . . . . . . . . . . . . . . . . . 7-13
Create the Consumer Tags. . . . . . . . . . . . . . . . . . . . . . . . 7-15
Download the Configuration to the Consumer . . . . . . . . . 7-18
Test the Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
What’s Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
Appendix A
Interpreting the Status Indicators. . . . . . . . . . . . . . . . . . . . . . . A-1
Appendix B
Web Page Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Module Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
TCP/IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
Diagnostic Information . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
ENET/IP Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
ENET/IP (CIP) STATISTICS . . . . . . . . . . . . . . . . . . . . . B-4
Chassis Who. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5
Configuring the RSLinx Ethernet
Communication Driver
1756-ENET/B Support of
ControlLogix Gateway
Communication
Example Network Configurations
Electronic Keying
Index
Appendix C
What This Appendix Contains. . . . . . . . . . . . . . . . . . . . . . . . . C-1
Installing the RSLinx Software . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Configuring the AB_ETH Driver . . . . . . . . . . . . . . . . . . . . . . . C-2
Appendix D
Using the 1756-ENET/B Module in a ControlLogix Gateway. . D-1
Appendix E
What This Appendix Contains. . . . . . . . . . . . . . . . . . . . . . . . . E-1
Small System Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-2
Expanded System with FLEX I/O . . . . . . . . . . . . . . . . . . . . . . E-3
Larger Control Networks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-4
Appendix F
Specifying Electronic Keying. . . . . . . . . . . . . . . . . . . . . . . . . . F-1
Publication 1756-UM051B-EN-P - November 2000
Table of Contents iv
Publication 1756-UM051B-EN-P - November 2000
About the 1756-ENET/B Module
Chapter
1
What This Chapter Contains
Module Features
This chapter provides an overview of the ControlLogix 1756-ENET/B
module, its primary features, what it does, and how to use it. You will
need to understand the concepts discussed in this chapter in order to
configure your Ethernet module and use it in a control system. The
following table lists where to find specific information in this chapter.
.
For information about See page
Module Features 1-1
What the Module Does 1-2
Hardware/Software Compatibility 1-2
Support of Rack Optimized and Direct Connections 1-2
Mixing Rack Optimized and Direct Connections 1-3
Use of the Control and Information Protocol (CIP) 1-4
Understanding the Producer/Consumer Model 1-4
Specifying the Requested Packet Interval (RPI) 1-5
The 1756-ENET/B module’s features include:
use Ethernet/IP messages encapsulated within standard
•
TCP/UDP/IP protocol
common application layer with ControlNet and DeviceNet
•
interfacing via AUI and 10 Base-T media
•
removal or insertion under power
•
• number of modules per chassis limited only by chassis size
• communication to and from other ControlLogix modules in the
same chassis
• communication supported by RSLinx software
• configurable via RSLinx or standard BootP tools
• no network scheduling required
• no routing tables required
1 Publication 1756-UM051B-EN-P - November 2000
1-2 About the 1756-ENET/B Module
Hardware/Software Compatibility
What the Module Does
The 1756-ENET/B module is compatible with the following firmware
versions and software releases. Contact Rockwell Automation if you
need software or firmware upgrades to use this equipment.:
Product Firmware Version/
Software Release
1756-ENET/B module 2.01 or higher
Logix 5550 Controller 6.10 or higher
RSLogix 5000 software 7.0 or higher
RSLinx software 2.2 or higher
The 1756-ENET/B module performs two primary tasks:
1. Control of real time I/O data (also known as “implicit messaging”)
in conjunction with a Logix 5550 controller. The Ethernet module
may serve as an adaptor, interfacing the I/O modules to the
network, or as a scanner, sending and receiving data between the
controller and the network.
Support of Rack Optimized and Direct Connections
Scanner
L
E
5
N
5
E
5
T
0
EtherNet Network
I/O
Adaptor
E
N
I/O
E
T
I/O
Adaptor
E
N
I/O
E
T
I/O
Adaptor
E
N
I/O
E
T
2. Support of messaging data for configuration and programming
information, operator interfaces, etc. (also known as “explicit
messaging.”).
The 1756-ENET/B module supports both Rack Optimized and Direct
Connections. A direct connection is a real-time data transfer link
between the controller and the device that occupies the slot that the
configuration data references. A rack optimized connection is a
grouping of data from more than one I/O module into a single block
of data sent over a single connection.
Publication 1756-UM051B-EN-P - November 2000
About the 1756-ENET/B Module 1-3
Rack optimized connections reduce the total number of connections
needed to transfer data when using many I/O modules in a system.
The following example illustrates the benefit of rack optimized
connections.
Assume you have set up a system that contains 10 discrete I/O
modules in a remote ControlLogix chassis. If you use direct
connections to transfer data to each of the these I/O modules, you
need 10 connections to transfer all of the data, one to each of the ten
I/O modules. If you use a rack-optimized connection to transfer the
data, you only need a single connection – the connection to the
Ethernet module.
IMPORTANT
Although rack optimized connections offer an
efficient way to use resources, there are a few
limitations on their use:
You can only use rack optimized connections to
•
send data to and from discrete digital I/O
modules. Analog I/O requires direct connections.
Rack optimized connections can contain I/O data
•
and status information only. Additional module
information, such as diagnostics, is not available
through a rack-optimized connection.
All data is sent at the same time at the RPI rate of
•
the Ethernet module, regardless of a COS on a
particular module.
See the Ethernet Performance and Application Guide, publication
number ENET-AP001A-EN-P, for more information on connections.
Mixing Rack Optimized and Direct Connections
You can mix communication formats for different I/O modules in the
same chassis. I/O modules set up to use Rack Optimization will
communicate at the rate of the RPI (requested packet interval)
configured for the 1756-ENET/B module. I/O modules configured for
direct communication will communicate at their set RPI and ignore the
Ethernet module’s RPI.
Publication 1756-UM051B-EN-P - November 2000
1-4 About the 1756-ENET/B Module
Use of the Control and Information Protocol (CIP)
Understanding the Producer/Consumer Model
The Ethernet module uses the Control and Information Protocol (CIP).
CIP is the application layer protocol specified for Ethernet/IP, the
Ethernet Industrial Protocol, as well as for ControlNet and DeviceNet.
It is a message-based protocol that implements a relative path to send
a message from the “producing” device in a system to the
“consuming” devices. The producing device contains the path
information that steers the message along the proper route to reach its
consumers. Since the producing device holds this information, other
devices along the path simply pass this information; they do not need
to store it. This has two significant benefits:
You do not need to configure routing tables in the bridging
•
module, which greatly simplifies maintenance and module
replacement.
You maintain full control over the route taken by each message,
•
which enables you to select alternative paths for the same end
device.
CIP uses the “producer/consumer” networking model, replacing the
old source/destination (master/slave) model. The producer/consumer
model reduces network traffic and increases speed of transmission. In
traditional I/O systems, controllers poll input modules to obtain their
input status. In the CIP system digital input modules are not polled by
a controller. Instead, they produce (“multicast”) their data either upon
a change of state (COS) or periodically. The frequency of update
depends upon the options chosen during configuration and where on
the network the input module resides. The input module, therefore, is
a producer of input data and the controller is a consumer of the data.
The controller can also produce data for other controllers to consume.
The produced and consumed data is accessible by multiple controllers
over the ControlLogix backplane and over the Ethernet network. This
data exchange conforms to the producer/consumer model.
You configure the producer and consumer by creating controller
scoped tags using RSLogix 5000 software (see chapter 7).
Tag Type Description Specify Using RSLogix5000 Software
Produced
Consumed
(1)
Publication 1756-UM051B-EN-P - November 2000
(1)
(1)
Produced and consumed tags must be controller-scoped tags of DINT or REAL data type, or in an array or structure.
Tags that the controller produced for other
nodes to consume.
Tags whose values are produced by another
controller.
Enabled for producing
Number of consumers allowed
Name of controller that owns the tag the local controller wants
to consume
Tag name or instance that the local controller wants to consume
Data type of the tag to consume
Update interval of how often the local controller consumes the tag
data
About the 1756-ENET/B Module 1-5
Specifying the Requested Packet Interval (RPI)
What’s Next?
The RPI is the update rate specified for a particular piece of data on
the network. The RPI can be specified for an entire rack (using a rack
optimized connection) or for a particular module (using direct
connection). When you add a module to the I/O configuration of a
controller, you must enter the RPI as a parameter. ‘This value specifies
how often to produce the data for that module. For example, if you
specify an RPI of 50ms, it means that every 50ms the I/O module
should send its data to the controller or that the controller should send
its data to the I/O module.
RPIs are only used for modules that produce data. For example a local
1756-ENET/B module (i.e., an ENET/B module in the same chassis as
the controller) does not require an RPI because it is not a
data-producing member of the system; it is used only as a bridge to
remote racks.
The following chapter describes how to install the Ethernet module
and connect it to the network.
Publication 1756-UM051B-EN-P - November 2000
1-6 About the 1756-ENET/B Module
Publication 1756-UM051B-EN-P - November 2000
Installing the Ethernet Module
Chapter
2
What This Chapter Contains
Identifying Module Features
This chapter describes how to install the module in the ControlLogix
chassis and connect it to the network. The following table describes
what this chapter contains and where to find specific information.
For information about See page
Insertion and Removal Under Power 2-2
Installing the Ethernet Module 2-2
Preparing the Chassis for Module Installation 2-2
Determining Module Slot Location 2-3
Inserting the Module in the Chassis 2-4
Removing or Replacing the Module (when applicable) 2-5
Wiring the Ethernet Connector 2-6
Connecting the Module to the Ethernet Network 2-6
Applying Chassis Power 2-7
Checking Power Supply and Module Status 2-8
Use the following illustration to identify the external features of the
1756-ENET/B module.
Backplane
Connector
1 Publication 1756-UM051B-EN-P - November 2000
Product
Label
Side View
Front
Panel
AUI Ethernet
Connector
MAC ID
Label
10BT Ethernet
Connector
<
www
>
Front View
ETHERNET
OKTXDRXD
AUI
10 BASET
1756-ENET
2-2 Installing the Ethernet Module
Insertion and Removal Under Power
Installing the Ethernet Module
The Ethernet module is designed to be installed or removed while
chassis power is applied. However, please observe the following
precautions.
WARNING
!
Use the following procedure to install the Ethernet module.
When you insert or remove the module while
backplane power is on, or you connect or disconnect
the communications connectors, an electrical arc can
occur. This could cause an explosion in hazardous
location installations. Be sure that power is removed
or the area is nonhazardous before proceeding.
Preparing the Chassis for Module Installation
Before you install the Ethernet module, you must install and connect a
ControlLogix chassis and power supply.
20805-M
(1)
(1)
(2)
(2)
1756-A4
Chassis
Power Suppl y
Installation
1756-5.67
1756-5.78
Power
Supply
For information on installing these products, refer to the publications
listed in the following table.
Chassis
Ty pe
Series A: 1756-A4, -A7, -A10, -A13 1756-5.69
Series B: 1756-A4, -A7, -A10, -A13 1756-5.80
(1)
Compatible with Series A chassis
(2)
Compatible with Series B chassis
Chassis
Installation
Power
Supply
1756-PA72/B
1756-PB72/B
1756-PA75/A
1756-PB75/A
Publication 1756-UM051B-EN-P - November 2000
Installing the Ethernet Module 2-3
Determining Module Slot Location
You can install the module in any slot in the ControlLogix chassis. You
can also install multiple ENET/B modules in the same chassis. The
figure below shows chassis slot numbering in a 4-slot chassis. In a
ControlLogix chassis slot 0 is the first slot and is always the leftmost
slot in the rack (the first slot to the right of the power supply).
Power Supply
Slot 0
Slot 1
Slot 2
Slot 3
Chassis
Publication 1756-UM051B-EN-P - November 2000
2-4 Installing the Ethernet Module
Inserting the Module in the Chassis
1
Align the circuit board with top and
bottom guides in the chassis.
Circuit Board
2
Slide the module into the chassis.
Make sure the module backplane
connector properly connects to the
chassis backplane.
3
The module is properly installed
when it is flush with the power
supply or other installed modules.
Publication 1756-UM051B-EN-P - November 2000
Installing the Ethernet Module 2-5
IMPORTANT
Removing or Replacing the Module (when applicable)
1
Push on upper and lower module
tabs to disengage them.
2
Slide module out of chassis.
If you are replacing an existing module with an
identical one, and you want to resume identical
system operation, you must install the new module
in the same slot.
Publication 1756-UM051B-EN-P - November 2000
2-6 Installing the Ethernet Module
N
Wiring the Ethernet Connector
ote: If your application requires the module
door to be closed, use one of the custom AUI
connector cables, available in two lengths:
• 2 meters (cat. no. 1756- TC02)
• 15 meters (cat. no. 1756- TC15)
Use either an AUI or an RJ45 connector to connect to the Ethernet
network. Wire the appropriate connector as shown below:
Protective Ground
1 ------ TD+
2 ------ TD3 ------ RD+
4 ------ NC
5 ------ NC
6 ------ RD7 ------ NC
8 ------ NC
8
1
RJ 45
9-Ctrl IN Ckt B
10-Data OUT Ckt B
11-Data OUT Ckt B
12-Data OUT Ckt B
13-Voltage Plus
14-Voltage Shield
15-Ctrl OUT Ckt B
1-Ctrl IN Ckt Shield
2-Ctrl IN Ckt A
3-Data OUT Ckt A
4-Data IN Ckt Shield
5-Data In Ckt A
6-Voltage Comm
7-Ctrl OUT Ckt A
8-Ctrl OUT Ckt Shield
AUI
Connecting the Module to the Ethernet Network
ATTENTION
!
If you connect or disconnect the Ethernet cable
with power applied to the module or any device
on the network, an electrical arc can occur. This
could cause an explosion in hazardous location
installations. Be sure that power is removed or the
area is nonhazardous before proceding.
Publication 1756-UM051B-EN-P - November 2000
Loading...