Advertisement
Advertisement
ControlNet Modules in Logix5000 Control
Systems
1734-ACNR, 1756-CN2, 1756-CN2R,
1756-CNB, 1756-CNBR, 1769-L32C,
1769-L35CR, 1784-PCC, 1784-PCIC,
1784-PCICS, 1784-PKTCS,
1788-CNC, 1788-CNCR, 1788-CNF,
1788-CNFR, 1794-ACN15,
1794-ACNR15, 1797-ACNR15
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.rockwellautomation.com/literature) 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, when necessary 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
ATTENTION
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, and recognize the consequence
SHOCK HAZARD
Labels may be located on or inside the equipment, for example a drive or motor, to alert people that dangerous voltage may be present.
BURN HAZARD
Labels may be located on or inside the equipment, for example a drive or motor, to alert people that surfaces may be dangerous temperatures.
Introduction
New and Revised
Information
Summary of Changes
This release of this document contains updated information. Changes are designated by change bars in margin, as shown to the right.
The table below lists the new information included in this release of the
ControlNet Modules in Logix5000 Control Systems user manual.
Information About
ControlLogix ControlNet Bridge Modules
1756-CN2 and 1756-CN2R
Location
All chapters
New or Revised
New
1 Publication CNET-UM001C-EN-P - November 2005
Summary of Changes 2
Notes:
Publication CNET-UM001C-EN-P - November 2005
Preface
Purpose of This Manual
This manual describes how you can use ControlNet with your Logix5000 controller. With this manual, you can learn how to communicate between your controller and various devices on the ControlNet network.
Who Should Use
This Manual
You should use this manual if you program applications that use ControlNet with one of the following Logix5000 controllers:
• CompactLogix controller
• ControlLogix controller
• FlexLogix controller
• PowerFlex 700S with DriveLogix controller
• SoftLogix5800 controller
You should also:
• have a basic understanding of networking concepts
• have a basic familiarity with the following software:
– RSLogix 5000 software
– RSLinx Classic software
– RSNetWorx for ControlNet software
1 Publication CNET-UM001C-EN-P - November 2005
Preface 2
Information This
Manuals Contains
l
This table describes the information available in this manual.
Section
Title
About the Logix5000 ControlNet Communication Modules
Connect a Computer to the ControlNet Network
Produce and Consume Tags (Interlock Controllers)
Communicate with PanelView and RSView Products
Chapter 8 Troubleshoot Your ControlNet Communication Modules
Appendix A Connection Use Over ControlNet
Appendix B ControlNet Overview
Appendix C Determine Your ControlNet Media Requirements
Appendix D Control 1771 I/O Over ControlNet
Publication CNET-UM001C-EN-P - November 2005
Related Documentation
Preface 3
This table lists ControlNet products and documentation that may be valuable as you program your application.
Catalog
Number
1756-CN2,
1756-CN2R
1756-CNB,
1756-CNBR
1769-L32C,
1769-L35CR
1784-PCC
1784-PCIC,
1784-PCICS
1784-PKTCS
Title
ControlLogix ControlNet Bridge Module
Installation Instructions
ControlLogix ControlNet Bridge Module
Installation Instructions
CompactLogix 1769-L32C, 1769-L35CR Controller
Installation Instructions
CompactLogix System User Manual
ControlNet PCMCIA Communication Card
Installation Instructions
ControlNet Universal PCI Communication Interface
Card Installation Instructions
ControlNet Universal PCI Scanner Card
Installation Instructions
ControlNet Daughtercard Installation Instructions 1788-CNC,
1788-CNCR
1788-CNF,
1788-CNFR
1794-ACNR
ControlNet Daughtercard Installation Instructions
1797-ACNR15
1734-ACNR
FLEX I/O ControlNet Adapter Module
Installation Instructions
ControlNet Ex Redundant Media Adapter
Installation Instructions
ControlNet Ex Coax Media System
POINT I/O ControlNet Adapter
Installation Instructions
POINT I/O ControlNet Adapter User Manual
Networks Series NetLinx Selection Guide
1786-RG6 and
1786-RG6F
ControlNet Standard and High-flex Coax Cable
Installation Instructions
1786 Series ControlNet Fiber Media Planning and
Installation Guide
ControlNet Media System Components List
AC Drives, DC
Drives
ControlNet Coax Media Planning and
Installation Guide
Safety Guidelines - Application and Installation
Publication
Number
1756-IN602
1756-IN571
1769-IN070
1769-UM011
1784-IN034
1784-IN003
1784-IN042
1788-IN002
1788-IN005
1794-IN101
1797-5.14
1797-6.2.1
1734-IN582
1734-UM008
NETS-SG001
1786-IN009
CNET-IN001
AG-PA002
CNET-IN002
SGI-1.1
To view or download these publications, go to: http://www.rockwellautomation.com/literature
To obtain a hard copy, contact your Rockwell Automation distributor or sales representative.
Publication CNET-UM001C-EN-P - November 2005
Preface 4
Notes:
Publication CNET-UM001C-EN-P - November 2005
Table of Contents
Summary of Changes
Preface
Table of Contents
About the Logix5000 ControlNet
Communication Modules
Connect a Computer to the
ControlNet Network
Important User Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary of Changes-1
New and Revised Information . . . . . . . . . . . . . Summary of Changes-1
Purpose of This Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preface-1
Who Should Use This Manual. . . . . . . . . . . . . . . . . . . . . . . . . . Preface-1
Information This Manuals Contains . . . . . . . . . . . . . . . . . . . . . Preface-2
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preface-3
Chapter 1
Choose a ControlNet Communication Module . . . . . . . . . . . . . . . . . 1-1
1756-CN2, 1756-CN2R Overview . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1756-CNB, 1756-CNBR Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
1769-L32C, 1769-L35CR Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
1784-PCC Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
1784-PCIC, 1784-PCICS, 1784-PKTCS Overview . . . . . . . . . . . . . . 1-5
1788-CNC, 1788-CNCR, 1788-CNF, 1788-CNFR Overview. . . . . . 1-6
1794-ACN15, 1794-ACNR15 Overview . . . . . . . . . . . . . . . . . . . . . . 1-6
1797-ACNR15 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
1734-ACNR Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Use the ControlNet Communication Modules in a Control System. 1-8
Bridge Across Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Chapter 2
Connect a Computer to Any Network . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Configure the ControlNet Communication Driver in the RSLinx
Connect a SoftLogix Controller to ControlNet . . . . . . . . . . . . . . . . . 2-5
Chapter 3
1
Configure a ControlNet Module
Set Up Your Computer to Connect to ControlNet . . . . . . . . . . . . . . 3-2
Use RSLogix 5000 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Overview of the RSLogix 5000 Software Configuration Process 3-2
Add a Local ControlNet Module . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Add a Remote ControlNet Module . . . . . . . . . . . . . . . . . . . . . . . 3-7
Download the Project to the Logix5000 Controller . . . . . . . . . 3-10
Use RSNetWorx for ControlNet Software. . . . . . . . . . . . . . . . . . . . 3-12
Schedule a ControlNet Network for the First Time . . . . . . . . . 3-12
Publication CNET-UM001C-EN-P - November 2005
Table of Contents 2
Control I/O
Produce and Consume Tags
(Interlock Controllers)
Peer-to-Peer Messaging
Publication CNET-UM001C-EN-P - November 2005
Schedule the Network Offline . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Schedule the Network Online . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Reschedule a ControlNet Network That Has Previously
Been Scheduled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
Chapter 4
Set Up the Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Set a Requested Packet Interval. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Select a Communication Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Direct or Rack Optimized Connection. . . . . . . . . . . . . . . . . . . . . 4-5
Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Add Local and Remote ControlNet Modules. . . . . . . . . . . . . . . . . . 4-10
Add Distributed I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Access Distributed I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Validate Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Chapter 5
Set Up the Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Determine Connections for Produced and Consumed Tags . . . . . . . 5-3
Organize Tags for Produced or Consumed Data. . . . . . . . . . . . . . . . 5-5
Adjust for Bandwidth Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Additional Steps for a PLC-5C or ControlNet Scanner Card . . . . . 5-12
Use RSNetWorx to Produce a Tag from a ControlNet Scanner 5-13
Use RSNetWorx to Consume a Tag by a ControlNet Scanner. 5-15
Reconstruct Values with PLC-5C Controller . . . . . . . . . . . . . . . 5-17
Chapter 6
Set Up the Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Guidelines for MSG Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Determine Connections for Messages . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Guidelines for Caching Message Connections . . . . . . . . . . . . . . . 6-5
Enter Message Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Add the ControlNet Modules and Remote Devices to the Local
Controller’s I/O Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Enter a Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Configure a Message Instruction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Table of Contents 3
Troubleshoot Your ControlNet
Communication Modules
Message Type to Configure a MSG to Logix5000 Controller . . 6-8
Message Type to Configure a MSG to an SLC 500 Processor . . 6-9
Message Type to Configure a MSG to a PLC-5 Processor . . . 6-10
Communicate with PLC-5 or SLC 500 Processors . . . . . . . . . . . . . 6-12
Initiate MSGs from PLC-5 Processors to Logix5000
Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
Map Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Stagger the Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16
Route PLC-5 Messages Between ControlNet Networks . . . . . . . . . 6-16
Route a ControlNet Message . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17
Chapter 7
Communicate with PanelView and
RSView Products
Set Up the Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Determine Connections to PanelView Terminals . . . . . . . . . . . . . . . 7-2
Add a PanelView Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Organize Controller Data for a PanelView Terminal. . . . . . . . . . . . . 7-6
Determine Connections to RSView Applications . . . . . . . . . . . . . . . 7-7
Chapter 8
1756-CN2 and 1756-CN2R ControlNet Communication
Module Status Indicator and Module Status Display
Diagnostic Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Network Channel Status Indicator Interpretation . . . . . . . . . . . . 8-4
1756-CNB and 1756-CNBR ControlNet Communication
Module Status Indicator and Module Status Display
Diagnostic Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Network Channel Status Indicator Interpretation . . . . . . . . . . . . 8-9
1769-L32C and 1769-L35CR CompactLogix Controllers . . . . . . . . 8-11
Interpret Status Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
Module Status (MS) indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13
Network Channel Status Indicators . . . . . . . . . . . . . . . . . . . . . . 8-14
1784-PCIC, 1784-PCICS and 1784-PKTCS ControlNet PCI
Network Channel Status Indicator Interpretation . . . . . . . . . . . 8-15
1788-CNC, 1788-CNCR, 1788-CNF and 1788-CNFR ControlNet
Module and I/O Status Indicator Interpretation . . . . . . . . . . . . 8-18
Network Channel Status Indicator Interpretation . . . . . . . . . . . 8-20
Publication CNET-UM001C-EN-P - November 2005
Table of Contents 4
1794-ACN15 and 1794-ACNR15 ControlNet FLEX I/O
1797-ACNR15 ControlNet FLEX Ex Redundant Media I/O
Appendix A
Connection Use Over ControlNet
Use This Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
ControlNet Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Connected Messaging Limits. . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Unconnected Messaging Limits . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Appendix B
ControlNet Overview
Determine Your ControlNet
Media Requirements
Understand the ControlNet Network. . . . . . . . . . . . . . . . . . . . . . . . . B-1
Exchange Information on ControlNet . . . . . . . . . . . . . . . . . . . . . . . . B-2
Network Update Time (NUT) . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4
Requested Packet Interval (RPI) . . . . . . . . . . . . . . . . . . . . . . . . . . B-4
Actual Packet Interval (API) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5
Schedule the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6
Understand the Network Keeper . . . . . . . . . . . . . . . . . . . . . . . . . B-8
Default Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-10
ControlNet Capacity and Topology . . . . . . . . . . . . . . . . . . . . . . . . . B-11
Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-11
Number of Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-14
Distances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-14
Appendix C
Use This Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Design a ControlNet Media System . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Application Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Media Needs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
ControlNet Media Components . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
Determine How Many Taps You Need . . . . . . . . . . . . . . . . . . . . . . . C-4
Connect Programming Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5
Determine What Type of Cable You Need . . . . . . . . . . . . . . . . . . . . C-6
Determine Trunk Cable Section Lengths . . . . . . . . . . . . . . . . . . . . . . C-7
Determine if You Need Repeaters . . . . . . . . . . . . . . . . . . . . . . . . . . C-10
Determine How Many Trunk Terminators You Need . . . . . . . . . . C-11
Configure Your Link With Repeaters . . . . . . . . . . . . . . . . . . . . . C-11
Install Repeaters In Series . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-12
Install Repeaters In Parallel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-13
Install Repeaters In A Combination Of Series And Parallel . . . C-14
Determine What Type of Connectors You Need. . . . . . . . . . . . . . . C-15
Publication CNET-UM001C-EN-P - November 2005
Table of Contents 5
Use Redundant Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-17
Application Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-20
General Wiring Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-21
Order Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-23
General Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-23
Segment Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-23
Link Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-23
Appendix D
Control 1771 I/O Over ControlNet
Use This Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
How to Use This Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Add the Local 1756-CN2(R) or 1756-CNB(R) Module. . . . . . . . . . D-2
Add the 1771-ACN(R)15 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
Read Data From a Block Transfer Module . . . . . . . . . . . . . . . . D-4
Configure the Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-5
Write Configuration or Output Data To a Block Transfer
Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-6
Configure the Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-7
Index
Rockwell Automation Support . . . . . . . . . . . . . . . . . . . . . . . . Backcover
Installation Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Backcover
Publication CNET-UM001C-EN-P - November 2005
Table of Contents 6
Publication CNET-UM001C-EN-P - November 2005
1
Chapter
1
About the Logix5000 ControlNet
Communication Modules
Use This Chapter
This chapter introduces the Logix5000 ControlNet communication modules and describes how you can use these modules in a control system:
For This Information
Choose a ControlNet Communication Module
1769-L32C, 1769-L35CR Overview
1784-PCIC, 1784-PCICS, 1784-PKTCS Overview
See Page
1788-CNC, 1788-CNCR, 1788-CNF, 1788-CNFR Overview 1-6
1794-ACN15, 1794-ACNR15 Overview
The remaining chapters in this publication describe how to configure and program the ControlNet communication modules. A listing of catalog numbers at the beginning of each chapter identifies the modules that support the feature described in that chapter.
Choose a ControlNet
Communication Module
The Logix5000 family offers several ControlNet communication modules.
Select the module you need based on the ControlNet functions your application requires.
Publication CNET-UM001C-EN-P - November 2005
1-2 About the Logix5000 ControlNet Communication Modules
This table describes the ControlNet communication modules’ functionality.
Table 1.1 The Functions of the ControlNet Communication Module
ControlNet Module
1756-CN2, 1756-CN2R
1756-CNB, 1756-CNBR
1769-L32C, 1769-L35CR
1784-PCC
1784-PCIC
1784-PCICS
1784-PKTCS
(1)
1788-CNC, 1788-CNCR,
1788-CNF, 1788-CNFR
1794-ACN15,
1794-ACNR15
1797-ACNR15
1734-ACNR
Functions as an
I/O Bridge
X
X
X
X
X
X
(2)
Functions as a
Messaging
Bridge
(3)
X
X
X
(4)
X
X
X
X
X
Functions as an
I/O Adapter
X
X
X
X
X
(5)
(1)
The module is a scanner (for example, the module can originate connections to remote I/O).
(2)
(3)
(4)
(5)
When it functions as an I/O bridge, the module can (in conjunction with the controller) originate connections to remote I/O.
When it functions as a messaging bridge, the module can function as a gateway from one network to another network or backplane without a controller program. To enable gateway functionality for the 1784-PCC card,
RSLinx Gateway is required.
When you use the CompactLogix 1769-L32C or 1769-L35CR controllers as a bridge from ControlNet to
DeviceNet, you must use a 1769-SDN module in the local chassis.
When it functions as an I/O adapter, the module can interface to I/O and serve as the target of a remote I/O connection from a controller.
The ControlNet communication modules:
• support messaging, produced/consumed tags and distributed I/O.
• share a common application layer with DeviceNet and EtherNet/IP.
• interface via RG-6 coaxial cable or 200/230 micron HCS (hard-clad silica) fiber optic cable.
• require no routing tables.
• support the use of coax and fiber repeaters for isolation and increased distance.
Publication CNET-UM001C-EN-P - November 2005
About the Logix5000 ControlNet Communication Modules 1-3
1756-CN2, 1756-CN2R
Overview
1756-CN2R shown
43605
ControlLogix ControlNet communication modules bridge ControlNet links to route messages to devices on other networks. The modules also monitor and control I/O modules located remotely from the ControlLogix controller.
The 1756-CN2 and 1756-CN2R modules are supported in the following software:
• RSLogix 5000 software version 15.01
The module can be used as a replacement for the 1756-CNB(R) when you select compatible keying for RSLogix 5000 software version 10 and later.
• RSNetWorx software version 6.
You must install EDS files for earlier versions of RSNetWorx software.
This module provides:
• high-speed I/O bridge functionality to manage distributed I/O modules.
• transfer of scheduled data via produced/consumed tags.
• unscheduled MSG instruction communication with other
ControlNet nodes.
• messaging data for configuration and programming information, operator interfaces, upload/download.
This module supports:
• adapter functionality for remote ControlLogix I/O modules.
• local communication network access through the network access port
(NAP).
• redundant media (1756-CN2R only).
Publication CNET-UM001C-EN-P - November 2005
1-4 About the Logix5000 ControlNet Communication Modules
1756-CNB, 1756-CNBR
Overview
1756-CNBR shown
43605
ControlLogix ControlNet communication modules bridge ControlNet links to route messages to devices on other networks. The modules also monitor and control I/O modules located remotely from the ControlLogix controller.
This module provides:
• adapter functionality for remote ControlLogix I/O modules.
• messaging data for configuration and programming information, operator interfaces, upload/download.
This module supports:
• I/O bridge functionality for applications requiring less performance than those applications that require the high-speed 1756-CN2(R).
• transfer of scheduled data via produced/consumed tags.
• unscheduled MSG instruction communication with other
ControlNet nodes.
• local communication network access through the network access port
(NAP).
• redundant media (1756-CNBR only).
1769-L32C, 1769-L35CR
Overview
43925
The CompactLogix 1769-L32C and 1769-L35CR controllers have an integrated ControlNet port. This controller supports:
• transfer of scheduled data via produced/consumed tags.
• unscheduled MSG instruction communication with other
ControlNet nodes.
• messaging data for configuration and programming information, operator interfaces, upload/download.
• local communication network access through the NAP.
• redundant media (1769-L35CR only).
1769-L35CR shown
Publication CNET-UM001C-EN-P - November 2005
About the Logix5000 ControlNet Communication Modules 1-5
1784-PCC Overview
43678
The 1784-PCC communication interface cards are personal computer memory card international association (PCMCIA) interface cards that enable laptop computers to communicate directly with other ControlNet products. These cards support:
• messaging data for configuration and programming information, operator interfaces, upload/download.
• unscheduled messaging communication with other ControlNet nodes.
• local communication network access through another ControlNet device’s NAP.
• serves as a ControlNet traffic analyzer, catalog number 9220-WINTA.
1784-PCIC, 1784-PCICS,
1784-PKTCS Overview
1784-PCICS shown
42281
The 1784-PCIC, 1784-PCICS and 1784-PKTCS communication interface cards are peripheral component interconnect (PCI) open-bus interface cards that enable PCI local bus compatible computers to communicate directly with other ControlNet products.
All of these cards support:
• unscheduled MSG instruction communication with other
ControlNet nodes.
• messaging data for configuration and programming information, operator interfaces, upload/download.
• local communication network access through the NAP.
• redundant media.
The 1784-PCICS card also supports:
• I/O bridge functionality to manage distributed I/O modules.
• transfer of scheduled data via produced/consumed tags.
• a ControlNet I/O interface for the SoftLogix5800 controller.
The 1784-PKTCS card also supports:
• I/O scanner functionality to manage distributed I/O modules as well as monitoring and configuration capabilities.
• transfer of scheduled data via produced/consumed tags.
• the IOLinx API for C++ and Visual Basic control applications.
You cannot use the 1784-PKTCS card as a ControlNet I/O interface for the SoftLogix5800 controller.
Publication CNET-UM001C-EN-P - November 2005
1-6 About the Logix5000 ControlNet Communication Modules
1788-CNC, 1788-CNCR,
1788-CNF, 1788-CNFR
Overview
1788-CNCR shown
43679
The ControlNet communication card links the FlexLogix controller and
PowerFlex 700S with DriveLogix controller to other devices on a ControlNet network. The ControlNet communication card also provides access for the
FlexLogix controller to monitor and control I/O modules located remotely from the controller on the ControlNet network. These cards support:
• I/O bridge functionality to manage distributed I/O modules.
• transfer of scheduled data via produced/consumed tags.
• unscheduled MSG instruction communication with other
ControlNet nodes.
• messaging data for configuration and programming information, operator interfaces, upload/download.
• local communication network access through the NAP - not available on the 1788-CNFR.
• redundant media (1788-CNCR and 1788-CNFR only).
• fiber media for optical isolation and increased noise immunity
(1788-CNF and 1788-CNFR only) used in conjunction with the
ControlNet short distance fiber repeaters.
• uses 200 micron cable (1786-FSxxx) with V-pin connectors and
1786-RPFS/RPA to connect to the network (1788-CNFR only).
1794-ACN15, 1794-ACNR15
Overview
1794-ACNR shown
43607
The 1794-ACN15 and 1794-ACNR15 modules operate as adapters for FLEX
I/O modules on a ControlNet network. This module supports:
• control of I/O within its chassis–you can connect up to 8 FLEX I/O modules to one 1794-ACN15 or 1794-ACNR15 module.
• unscheduled messaging data for configuration.
• local communication network access through the NAP.
• control of individual I/O modules by different controllers.
• redundant media (1794-ACNR15 only).
Publication CNET-UM001C-EN-P - November 2005
About the Logix5000 ControlNet Communication Modules 1-7
1797-ACNR15 Overview
41411
The 1797-ACNR15 modules operate as adapters for FLEX Ex I/O modules on a ControlNet network in an intrinsically safe environment. This module supports:
• control of I/O within its chassis–you can connect up to 8 FLEX Ex
I/O modules to one 1797-ACNR15 module.
• unscheduled messaging data for configuration.
• control of individual I/O modules by different controllers.
• redundant media.
1734-ACNR Overview
43248
The 1734-ACNR module operates as an adapter for POINT I/O modules on a ControlNet network. This module supports:
• control of I/O within its chassis, with up to 63 POINT I/O modules connected to the adapter.
• unscheduled messaging data for configuration.
• local communication network access through the NAP.
• redundant media.
The 1734-ACNR module appears as an I/O module, rather than as a
ControlNet communication module, in RSLogix 5000–the programming software for Logix5000 control systems. Additionally, the 1734-ACNR module is compatible with Logix5000 systems only; the module will not work with
PLC or SLC controllers.
For more information, see the 1734-ACNR user manual, publication
1734-UM008.
Publication CNET-UM001C-EN-P - November 2005
1-8 About the Logix5000 ControlNet Communication Modules
Use the ControlNet
Communication Modules in a Control System
This figure shows how the different ControlNet modules can fit into a control system.
Figure 1.1 ControlNet Modules and the Control System Relationship
ControlLogix controller with 1756-CN2(R) or 1756-CNB(R) module as the scanner.
PC Running
SoftLogix5800
Controller with
1784-PCICS Card
Distributed I/O
PowerFlex 700S Drive
1756-CNB Module
(as an adapter) with
1756 I/O Modules
For a redundant system you must use a 1756-CNB(R) communication module. The
1756-CN2(R) Series A module does not support redundancy.
ControlNet
1794-ACN15 Adapter with 1794 I/O Modules
FlexLogix Controller with
1788-CNC Card
CompactLogix
1769-L35CR
Controller with Local
1769 I/O Modules
1734-ACNR
Adapter with
1734 I/O
Modules
PanelView Terminal
PLC-5/40C Controller
In this example:
IMPORTANT
If you are creating a ControlNet redundant system you will need to use a 1756-CNB module and refer to the
ControlLogix Redundancy System User Manual,
1756-UM532. The 1756-CN2 Series A module does not support redundancy.
• The controllers, for example CompactLogix, ControlLogix, FlexLogix,
SoftLogix or PLC-5C can produce and consume tags among each other.
• The controllers can initiate MSG instructions that send/receive data or configure devices.
• The personal computer can upload/download projects to the controllers.
• The personal computer can configure devices on ControlNet, and it can configure the network itself.
Publication CNET-UM001C-EN-P - November 2005
About the Logix5000 ControlNet Communication Modules 1-9
Bridge Across Networks
Some ControlNet modules support the ability to bridge or route communication to and from different networks, depending on the capabilities of the platform and communication devices.
With unscheduled communication, you have a bridge when you have a connection between communication devices on two separate networks. For example, the bridge device shown below has both ControlNet and DeviceNet connections so that Device 1 on ControlNet can communicate with Device 2 on DeviceNet through the bridge.
Device 1
ControlNet Network
Bridge
DeviceNet Network
Device 2
Communication can bridge these networks:.
A Device on This Network Can Access a Device on This Network
EtherNet/IP
ControlNet
DeviceNet
RS-232
EtherNet/IP yes yes no yes
ControlNet yes yes no yes
(1)
DeviceNet yes yes yes yes
RS-232
(2) yes yes no yes
(1)
To use RSNetWorx software to configure and schedule a ControlNet network, we recommend that you either: connect to an EtherNet/IP network and bridge to a ControlNet network or use a 1784-PCC interface device to connect directly to a ControlNet network.
(2)
Typically, this is a point-to-point connection between a Logix5000 controller and another device, such as a PanelView™ Plus operator terminal.
Publication CNET-UM001C-EN-P - November 2005
1-10 About the Logix5000 ControlNet Communication Modules
In this example, a workstation configures a drive on a DeviceNet network. The workstation bridges from ControlNet to DeviceNet to reach the drive.
Figure 1.2 Configure a Drive on a DeviceNet Network
Workstation
PanelView Station
ControlNet Network
Bridge
DeviceNet Network
PWR
STS
PORT
MOD
NET A
NET B
Drive
In this example, the bridge can be a ControlNet to DeviceNet bridging device, for example a 1788-CN2DN or a Logix5000 system with a ControlNet communication module and a DeviceNet communication module. This table describes how to use Logix5000 systems in this example.
Table 1.2 Example Bridges and Related Components
If The Bridge Is
CompactLogix system
ControlLogix system
FlexLogix system
SoftLogix system
You Need These Components
• a CompactLogix 1769-L32C, or
1769-L35CR controller
• a 1769-SDN scanner
• a 1756-CN2 module
• a 1756-CNB module
• a 1756-DNB module
• a FlexLogix controller
• a 1788-CNx card
• a 1788-DNBO card
• a SoftLogix controller
• a 1784-PCIC(S) card
• a 1784-PCIDS card
Publication CNET-UM001C-EN-P - November 2005
About the Logix5000 ControlNet Communication Modules 1-11
Keep in mind that you can only bridge messages across networks . You cannot bridge I/O connections from one network to another.
IMPORTANT
The CompactLogix and FlexLogix controllers’ performance degrades significantly if you use the controller as a bridge. Bridging over the FlexLogix controller should be targeted toward applications that are not real time dependent, for example RSLogix 5000 software program downloads.
In the Configure a Drive on a DeviceNet Network figure, status data can also be transferred from DeviceNet through the Logix5000 controller to a
RSView32 operator interface. For a FlexLogix controller, map the data into the
DeviceNet I/O image and then use RSLinx OPC from the PC to the
Logix5000 controller over ControlNet. This avoids using the limited bridging resources of the FlexLogix controller.
The example RSLinx software screen below shows how the EtherNet/IP bridge links to the ControlNet network:
EtherNet/IP Network
EtherNet/IP Bridge in
1794 System
ControlNet Bridge in
Same 1794 System
ControlNet Network
You can bridge messages across multiple networks, but I/O Control is mostly restricted to being bridged across only one network. I/O Control from a
ControlLogix controller over ControlNet to a scanner device is supported.
You cannot go through a gateway chassis to control I/O, even though in some circumstances, RSLogix 5000 software accepts such a configuration in the I/O
Configuration folder.
Publication CNET-UM001C-EN-P - November 2005
1-12 About the Logix5000 ControlNet Communication Modules
This table lists the possible bridges between communication networks.
Table 1.3 Bridges Between Communication Networks
To Bridge
From This
Network
ControlNet
EtherNet/IP
To This
Network:
DeviceNet
You Can Use the Following
(1)
In a CompactLogix System
•
1769-L32C or 1769-L35CR controller
•
1769-SDN scanner or
•
1769-L32C or 1769-L35CR controller
• one 1788-CN2DN module
(2)
EtherNet/IP NA
In a ControlLogix Chassis
•
1756-CN2(R) module
•
1756-CNB(R) module
•
1756-DNB module
ControlNet
DeviceNet
NA
•
1769-L32E or 1769-L35E controller
•
1769-SDN scanner
•
1756-CN2(R) module
•
1756-CNB(R) module
•
1756-ENBT module
•
1756-ENBT module
•
1756-CN2(R) module
•
1756-CNB(R) module
•
1756-ENBT module
•
1756-DNB module or
•
1769-L32E or 1769-L35E controller
• one 1788-EN2DN module
(3)
In a FlexLogix Controller or or
•
1788-CN(x) card
•
1788-DNBO card
•
•
•
•
•
•
•
•
1788-CN(x) card
• one 1788-CN2DN module
(2)
1788-CN(x) card
1788-ENBT card
1788-ENBT card
1788-CN(x) card
1788-ENBT card
1788-DNBO card
1788-ENBT card
• one 1788-EN2DN module
(3)
(1)
(2)
(3)
You can bridge from a ControlNet network to an Ethernet network and from an Ethernet network to a ControlNet via a SoftLogix virtual chassis. However, the products and methods you must use to do so are more detailed than can be effectively described in this table. For more information on how to bridge from one network to another via a
SoftLogix virtual chassis, see the SoftLogix5800 System User Manual, publication number 1789-UM002.
Can serve as a dedicated standalone bridge from ControlNet to DeviceNet.
Can serve as a dedicated standalone bridge from EtherNet/IP to DeviceNet.
Publication CNET-UM001C-EN-P - November 2005
1
Chapter
2
Connect a Computer to the
ControlNet Network
Use This Chapter
Read this chapter for:
•
1784-PCC, 1784-PCIC, 1784-PCICS,
1784-PKTCS cards
This chapter describes how to configure a personal computer to operate on a
ControlNet network.
For This Information
Connect a Computer to Any Network
Configure the ControlNet Communication Driver in the RSLinx Software
Connect a SoftLogix Controller to ControlNet
See Page
You need to load a ControlNet communication driver for a personal computer to communicate with other devices on a ControlNet network. A personal computer needs this driver to:
• upload and download controller projects over ControlNet via RSLogix
5000 programming software.
• schedule the ControlNet network via RSNetWorx for ControlNet software.
• operate an HMI type application.
Before you load a communication driver, make sure the:
• ControlNet communication card is already installed in the personal computer.
• personal computer is properly connected to the ControlNet network.
For more information on how to install the ControlNet communication cards, use the installation instructions for each card. The respective installation instructions are listed in the table Related Documentation in the Preface.
Publication CNET-UM001C-EN-P - November 2005
2-2 Connect a Computer to the ControlNet Network
Connect a Computer to Any
Network
To access a network, either:
• connect directly to the network or
• connect to a different network and browse (bridge) to the desired network. This requires no additional programming.
IMPORTANT
To use RSNetWorx software to configure and schedule a
ControlNet network, either:
• connect to an EtherNet/IP network and bridge to the
ControlNet network or
• use one of the laptop or desktop cards listed below to connect directly to the ControlNet network.
The figure below shows your options. ports, cards, or modules in a Logix5000 controller, chassis, or linking device
Logix5000
Controller
EtherNet/IP
Port
ControlNet
Port
DeviceNet
Port
Serial Port
Point-to-point
RS-232
Connection
EtherNet/IP Network
Ethernet Card
Laptop
1784-PCC
1770-KFC15
(1)
Desktop
1784-PCIC
1784-PCICS
1784-PKTCS
1784-KTCX15
1770-KFC15
(1)
This module offers an RS-232 connection to standalone devices such as multi-vendor automation equipment,
PCs, or modems.
ControlNet Network
Only lets you access devices on the
DeviceNet network.
DeviceNet Network
Laptop
1784-PCD
1770-KFD
(1)
Desktop
1784-PCID
1784-PCIDS
1770-KFD
(1)
This module offers an RS-232 connection to standalone devices such as multi-vendor automation equipment, PCs, or modems.
If you connect directly to a
DeviceNet network, you can access only the devices on that network.
Publication CNET-UM001C-EN-P - November 2005
Connect a Computer to the ControlNet Network 2-3
Configure the ControlNet
Communication Driver in the RSLinx Software
To configure the ControlNet communication driver for the personal computer
(programming workstation):
IMPORTANT
Do not use these steps to configure a ControlNet communication driver for any application that uses a
SoftLogix5800 controller. With the SoftLogix5800 controller, you can configure a ControlNet communication driver via the SoftLogix5800 Chassis Monitor. For more
information on how to do this, see the section Connect a
SoftLogix Controller to ControlNet.
1.
In RSLinx software, select Configure Driver.
A.
Click Communications .
B.
Click Configure Drivers .
2.
Select a driver for ControlNet devices. In the example below, we choose the 1784-PCICS card. You can also connect your PC to a ControlNet network via the 1784-PCC card.
A.
Use the pull-down menu to select the
ControlNet driver.
B.
Click Add New.
Publication CNET-UM001C-EN-P - November 2005
2-4 Connect a Computer to the ControlNet Network
3.
Name the new ControlNet driver.
A.
Name the driver. This example shows the default name
AB_PCIC-1.
B.
Click OK.
A.
If multiple cards are located in your computer, choose the correct one.
B.
Make sure you use the correct Network Address.
C.
Click OK.
4.
After you create the driver, configure it to correspond to the ControlNet module within your computer.
The appearance of this screen varies widely depending on the type of card used.
The driver is now available and you can select the ControlNet port from Who
Active in RSLogix 5000 programming software.
Publication CNET-UM001C-EN-P - November 2005
Connect a SoftLogix
Controller to ControlNet
Connect a Computer to the ControlNet Network 2-5
The SoftLogix5800 controller is a soft control solution that runs in a
Microsoft Windows NT, Windows 2000, or Windows XP environment. When using this controller, you must install the SoftLogix5800 Chassis monitor–a virtual chassis that takes the place of hardware chassis used with other
Logix5000 controllers.
Before you can connect the SoftLogix system to the ControlNet network, you must create the 1784-PCIC, 1784-PCICS or 1784-PKTCS card as part of the
SoftLogix chassis.
IMPORTANT
You can use only the 1784-PCIC, 1784-PCICS, or
1784-PKTCS cards to connect a SoftLogix controller to
ControlNet.
1.
In the SoftLogix chassis monitor, create a New Module.
A.
Click Slot.
B.
Click Create Module.
2.
Select the 1784-PCIC, 1784-PCICS or 1784-PKTCS card.
A.
Select the ControlNet card.
B.
Specify the virtual backplane slot number.
C.
Click OK.
3.
Select the serial number of the ControlNet card you want.
If you previously configured the card that you selected by serial number, the chassis monitor remembers the configuration from the last time you used the card (whether in the same or different slot).
A.
If multiple cards are located in your computer, choose the serial number of the correct one.
B.
Click Next.
Publication CNET-UM001C-EN-P - November 2005
2-6 Connect a Computer to the ControlNet Network
4.
Configure the card.
A.
Specify the node address on the
ControlNet network.
B.
Enter the label name for the card
(this is the name you wrote on the label of the card to help you identify the card from others in the same computer).
C.
Click Finish.
You can specify any slot number greater than 0 for the communication card.
RSLinx software resides in slot 0.
By creating the card in the virtual chassis, you configure the communication driver information needed by the SoftLogix controller. DO NOT use RSLinx software to install the ControlNet communication driver to the same card; installation through RSLinx software adds the potential for conflicting configuration between RSLinx software and the SoftLogix software chassis monitor.
Instead, configure a Virtual Backplane driver in RSLinx software. After you add the card to the chassis monitor and configure a Virtual Backplane driver, you can browse the network by expanding the Virtual Backplane driver and then expanding the port on the desired ControlNet communication card.
Browsing ControlNet through the Virtual Backplane driver provides the same functionality as the RSLinx software driver.
The chassis monitor shows the 1784-PCICS card as a virtual module in the
SoftLogix chassis. The LEDs on the virtual monitor emulate either a
1756-CN2R or a 1756-CNBR communication module.
This chassis monitor has a
1784-PCICS card installed in slot 2.
Publication CNET-UM001C-EN-P - November 2005
Chapter
3
Configure a ControlNet Module
1
Use This Chapter
Read this chapter for:
•
1756-CN2, 1756-CN2R modules
•
1756-CNB, 1756-CNBR modules
•
1769-L32C, 1769-L35CR controllers
•
1784-PCIC, 1784-PCICS,
1784-PKTCS cards
•
1788-CNx cards
•
1794-ACN15, 1794-ACNR15 adapters
•
1797-ACNR15 adapter
This chapter describes how to configure a ControlNet communication module to operate on a ControlNet network.
For This Information
Set Up Your Computer to Connect to ControlNet
Add a Remote ControlNet Module
Download the Project to the Logix5000 Controller
Use RSNetWorx for ControlNet Software
Schedule a ControlNet Network for the First Time
Reschedule a ControlNet Network That Has Previously
See Page
IMPORTANT
The example configuration process shown in this chapter uses a ControlLogix ControlNet Bridge module
(1756-CNB) in a ControlLogix controller project.
However, the overall configuration process (briefly
described in the section Overview of the RSLogix 5000
Software Configuration Process) generally applies to any of
the ControlNet communication modules covered by this manual.
To configure a ControlNet communication module to operate on the
ControlNet network, you must:
• connect your computer to the RSLogix 5000 project via an RSLinx
ControlNet software communication driver.
• add the ControlNet communication module to your RSLogix 5000 project.
• schedule the ControlNet network via RSNetWorx for ControlNet software.
Publication CNET-UM001C-EN-P - November 2005
3-2 Configure a ControlNet Module
Set Up Your Computer to
Connect to ControlNet
You connect your personal computer to the ControlNet network via an
RSLinx ControlNet software communication driver. You use the ControlNet communication driver to:
• upload and download controller projects using RSLogix 5000 software.
• schedule the ControlNet network via RSNetWorx for ControlNet software.
For more information on how to connect a computer to the ControlNet
network, see chapter Connect a Computer to the ControlNet Network.
Use RSLogix 5000 Software
Use RSLogix 5000 software to configure the I/O tree in your project.
Overview of the RSLogix 5000 Software Configuration Process
When you use RSLogix 5000 software to configure a ControlNet communication module, you must perform the following steps:
1.
Add the new local module to your project.
2.
Configure the local module, including: a. naming the module.
b. choosing a Communication Format.
c. setting the Revision level.
d. setting the module location as necessary such as the slot number for a
1756-CNB module.
e. choosing an Electronic Keying method.
3.
Add the new remote module to your project.
4.
Configure the remote module similarly to the local module.
IMPORTANT
There are some differences between configuring a local
ControlNet communication module and a remote
ControlNet communication module. Those differences are covered later in this chapter.
5.
Download configuration to the controller.
Publication CNET-UM001C-EN-P - November 2005
A.
Right-click on I/O
Configuration.
B.
Select New Module.
Configure a ControlNet Module 3-3
Add a Local ControlNet Module
After you have started RSLogix 5000 software and created a controller project, you can add ControlNet communication modules. A local ControlNet module is a module that resides in the same chassis as the controller.
IMPORTANT
When you create a new RSLogix 5000 project with the
CompactLogix 1769-L32C or 1769-L35CR controller, the
Controller Organizer creates a ControlNet port in the local chassis. In this case, you do not need to add a separate local communication module.
1.
Select a New Module for the I/O Configuration.
2.
Select the module type from the Select Module Type pop-up. The example below uses a 1756-CNB module.
A.
Select the local ControlNet communication module.
B.
Click OK.
Publication CNET-UM001C-EN-P - November 2005
3-4 Configure a ControlNet Module
A.
Name the module.
B.
Select the module’s slot number.
C.
Select the module’s minor revision level.
D.
Select an Electronic Keying level. For more information on choosing a keying level, see
the table Electronic Keying Options.
E.
Click Next.
This table lists the ControlNet communication modules available locally such as in the local chassis, computer, or controller with each Logix5000 controller.
Table 3.1 ControlNet Communication Modules Available Locally
If You Are Using This Logix5000
Controller
CompactLogix
ControlLogix
FlexLogix
SoftLogix
You Can Use This ControlNet
Communication Module Locally
1769-L32C and 1769-L35CR controllers have a built-in ControlNet port
1756-CN2, 1756-CN2R
1756-CNB, 1756-CNBR
1788-CNC, 1788-CNCR, 1788-CNF, 1788-CNFR
1784-PCIC, 1784-PCICS, 1784-PKTCS
3.
Configure the local ControlNet communication module.
IMPORTANT
The example below shows configuration for a 1756-CNB module. However, depending on module-type such as a
1756, 1769, 1784, or 1788, there may be slight differences in how to configure a local ControlNet communication module. If you need help configuring a specific module, use online help in RSLogix 5000 software.
Publication CNET-UM001C-EN-P - November 2005
Configure a ControlNet Module 3-5
F.
Inhibit the module, if necessary.
Initially, do you want the module to communicate with the controller?
Yes
Then
No
Leave the box unchecked
Check the box
(1)
(1)
When you test this portion of the system, clear the check box.
G.
Determine if you want a major fault on the controller if the connection to the local communication module fails in Run Mode.
Then If You Want The
Controller To fault (major fault) continue operating
Select the check box
Leave the check box unchecked
(1)
(1)
Monitor the connection using ladder logic.
F.
Click Finish.
Publication CNET-UM001C-EN-P - November 2005
3-6 Configure a ControlNet Module
Keying Option
Exact Match
Compatible Match
Disable Keying
This table describes the keying options available in RSLogix 5000 software.
Table 3.2 Electronic Keying Options
Definition
When a controller establishes a connection with the ControlNet module, the following parameters must match or the inserted module will reject the connection:
•
Vendor
•
Product Type
•
Catalog Number
•
Major Revision
•
Minor Revision
When a controller establishes a connection with the ControlNet module, the inserted module decides whether it is compatible with the parameters listed above. Generally, all except Minor Revision must match or it will reject the connection.
TIP
We recommend using Compatible Match whenever possible. However, keep in mind that modules can emulate older revisions and, with major revision changes, the module only works to the level of the configuration.
If a slot is configured for a module with major.minor revision of 1.7 and you insert a module with a major.minor revision of 2.3, the module works at the 1.7 level, with respect to module functions that are related to RSLogix 5000 software such as interface changes. However, bug fixes that are affected by the module’s firmware, would work at the 2.3 revision level.
If possible, we suggest you make sure configuration is updated to match the revision levels of all I/O modules. Failure to do so may not prevent the application from working but may defeat the purpose of upgrading your modules’ revision levels.
When a controller establishes a connection with the ControlNet module, the inserted module attempts to accept the connection regardless of its type.
ATTENTION
Be extremely cautious when using the disable keying option; if used incorrectly, this option can lead to personal injury or death, property damage or economic loss.
Even if keying is disabled, a controller will not establish a connection if the slot is configured for one module type such as a communication module, and a module of another type such as an output module, is inserted in the slot.
Publication CNET-UM001C-EN-P - November 2005
A.
Right-click on the local communication module.
B.
Select New Module.
Configure a ControlNet Module 3-7
Add a Remote ControlNet Module
After you have added the local ControlNet communication module, you must add remote ControlNet communication modules. A remote ControlNet module is a module that resides in a separate chassis from the controller.
1.
Select a New Module for the I/O Configuration.
2.
Select the module type from the Select Module Type pop-up.
You can connect any remote ControlNet communication module, to a local ControlNet communication module.
A.
Select the remote ControlNet communication module.
B.
Click OK.
Publication CNET-UM001C-EN-P - November 2005
3-8 Configure a ControlNet Module
3.
Configure the remote ControlNet communication module.
IMPORTANT
The example below shows configuration for a 1756-CNB module. However, depending on the remote module-type such as a 1734, 1756, 1769, 1784, 1788, or 1794, there are differences in how to configure a remote ControlNet communication module. If you need help configuring a specific module, use online help in RSLogix 5000 software.
A.
Name the remote module.
B.
Select the remote module’s Node.
C.
Select the remote Chassis Size.
D.
Select the Slot containing the remote module.
E.
Select a Comm Format. For more information on choosing a Comm Format, see the section
Communication Format.
F.
Select the remote module’s minor revision level.
G.
Select an Electronic Keying level. For more information on choosing a keying
level, see the table Electronic Keying
H.
Click Next.
I.
Set the RPI rate.
The RPI must be equal to or greater than the ControlNet Network Update Time
(NUT). This parameter only applies if the module uses one of the Rack Optimized communication formats.
J.
Inhibit the module, if necessary.
Initially, do you want the module to communicate with the controller?
Yes
Then
No
Leave the box unchecked
Check the box
(1)
(1)
When you test this portion of the system, clear the check box.
K.
Determine if you want a major fault on the controller if the connection to the PanelView fails in Run Mode.
If you want the controller to fault (major fault)
Then
Select the check box
(1) continue operating Leave the check box unchecked
(1)
Monitor the connection using ladder logic.
L.
Click Finish.
Publication CNET-UM001C-EN-P - November 2005
Configure a ControlNet Module 3-9
Communication Format
The communication format determines:
• what configuration options are available - for example, if the module uses None, then you do not have to configure an RPI rate on the next screen.
• what type of data is transferred between the owner-controller and I/O connected via the communication module.
• what tags are generated when configuration is complete.
• the type of connection between the owner-controller and the I/O connected via the communication module.
The communication format setting affects the Requested Packet Interval (RPI) rate on the next configuration screen. This table lists Communication Format choices.
Table 3.3 Communication Formats
This Communication
Format Choice
Rack Optimized
Means And Affects The RPI This Way
The communication module creates a rack image and returns I/O data in the rack image to the owner-controller.
Listen-Only Rack Optimized
- Choice is not available on all ControlNet communication modules.
This option is available only for digital I/O modules.
Also keep in mind that diagnostic I/O modules will not return diagnostic data when you use this format.
The communication module creates a rack image and returns I/O input data in the rack image to the owner-controller.
The difference between this choice and Rack
Optimized is that the I/O data in the rack image is returned to a controller that does not control the outputs but is listening only to its input data.
You can specify an RPI that is:
• equal to or greater than the NUT.
• in the range permitted by RSLogix 5000 software, for example 2 - 750ms.
When you set the RPI for a remote ControlNet communication module, we recommend you use a rate that is a power of two times the NUT.
For example, if your NUT = 5ms, we recommend the following RPI values:
NUT = 5m
Optimal RPI values x 2
0 x 2
1 x 2
2 x 2
3 x 2
4
5ms 10ms 20ms 40ms 80ms
None No RPI is required The RPI box is grayed out.
Communication format does not apply to all ControlNet communication modules. For example, you do not choose a communication format when using the 1784-PCIC, 1784-PCICS nor 1788-CNx cards.
Publication CNET-UM001C-EN-P - November 2005
3-10 Configure a ControlNet Module
Download the Project to the Logix5000 Controller
IMPORTANT
Before you your RSLogix5000 project configuration to your ControlNet Communication modules, consider whether you will schedule the ControlNet network offline or online.
• If you are going to schedule the network offline,
complete the steps beginning in the section Schedule the Network Offline before downloading
configuration.
• If you are going to schedule the network online, complete the steps beginning below and then move to
the section Schedule the Network Online.
When you finish adding the local and remote ControlNet communication modules to your RSLogix 5000 project, you must download the new configuration to your Logix5000 controller.
1.
Because you must schedule the ControlNet network (explained in the following section) before using the new configuration, switch your
Logix5000 controller to Program mode in one of the following ways:
• Turn the controller keyswitch to PROG.
• Turn the controller keyswitch to REM and use RSLogix 5000 software to change the controller to Remote Program mode.
2.
Use the Who Active button to begin the download process.
Click Who Active.
Publication CNET-UM001C-EN-P - November 2005
Configure a ControlNet Module 3-11
3.
Use the Who Active pop-up screen to download the project to the controller.
A.
Expand the tree until you find the correct driver.
B.
Select the controller to which you need to download configuration.
In this example, the
Logix5550 controller is connected via an RS-232
DF1 device.
C.
Click Download.
The window above uses a previously configured driver for the communication path to the controller. In this example, the computer is connected to the controller’s RS-232 port, so the configuration is downloaded to the controller via RS-232 and DF-1 protocol.
4.
Download the configuration.
Click Download.
Be aware, however, that before downloading configuration, the RSLogix
5000 software warns you of any implications the download has on your application.
Publication CNET-UM001C-EN-P - November 2005
3-12 Configure a ControlNet Module
Use RSNetWorx for
ControlNet Software
You must use RSNetWorx for ControlNet software to schedule the network before the configured I/O devices in your application will become active. You must also reschedule the network if a change is made to an existing network that was already scheduled.
Schedule a ControlNet Network for the First Time
RSNetWorx software stores information in keeper devices. The following
ControlNet communication modules are keeper cable devices:
• 1756-CN2(R) modules
• 1756-CNB(R) modules
• 1769-L32C and 1769-L35CR controllers
• 1784-PCICS and 1784-PKTCS cards
• 1788-CNx cards
• 1797-ACNR15
• PLC-5C controller
If you configure a keeper on one network and then use it on another network, the conflicting information can make it difficult to use RSNetWorx software to schedule the new network. In extreme cases it may be impossible to go online, more commonly you get many apparently irrelevant error messages about devices that existed on the old network but do not exist or are different on the new one.
• For more information on the network keeper, refer to the section
Understanding the Network Keeper.
• For more information on how to reset valid keepers to an unconfigured state to resolve mismatches, see the RSNetWorx software online help.
• For more information on how to clear the memory or keeper information in a ControlNet communication module, refer to the
Knowledgebase at http://support.rockwellautomation.com.
You can schedule a ControlNet network either:
• offline or
• online.
These options are covered in the following sections.
Publication CNET-UM001C-EN-P - November 2005
A.
Right-click on the local ControlNet communication module.
B.
Click Properties.
Configure a ControlNet Module 3-13
Schedule the Network Offline
The following instructions assume that:
• your RSLogix 5000 project uses 1 controller and 1 network. We recommend that you use only one (1) 1756-CN2 or 1756-CNB module in the local chassis when scheduling the network offline.
• your RSLogix 5000 project is complete but has not been downloaded to the controller.
If your network has already been scheduled and you made a change to it, you must reschedule it. Refer to the section Rescheduling a ControlNet Network
That Has Previously Been Scheduled for more information.
1.
In your RSLogix 5000 project, access the local ControlNet module’s properties.
Publication CNET-UM001C-EN-P - November 2005
3-14 Configure a ControlNet Module
A.
Click on the RSNetWorx tab.
B.
Type the name of the new
ControlNet file.
C.
Click Apply.
2.
On the RSNetWorx tab, name the new ControlNet file.
3.
Because this is the first time you are scheduling the network, the file does not exist. When RSLogix 5000 software prompts you to create the new file, click Yes.
Click Yes.
This step creates the file that RSNetWorx for ControlNet software uses offline to browse and schedule network.
4.
Launch RSNetWorx for ControlNet software to create the schedule.
A.
Click on Schedule the ControlNet network. If you make this selection, RSNetWorx software automatically enable edits, create the schedule and disable edits.
B.
Click this button to launch the
RSNetWork for ControlNet software.
Publication CNET-UM001C-EN-P - November 2005
Click here to enable edits.
Click OK.
Configure a ControlNet Module 3-15
5.
The RSNetWorx for ControlNet software starts and creates a schedule that includes the devices in your RSLogix 5000 project. When the software prompts you to Optimize and re-write schedule for all connections, click OK.
Because you selected the Schedule the Network option in a previous step, RSNetWorx for ControlNet software automatically enables and disables edits before and after creating the schedule for the network respectively.
6.
Enable Edits in the schedule.
TIP
We recommend that you return to the RSLogix 5000 software and save the project after you enable edits in the
RSNetWorx for ControlNet software. Saving the file updates the network file in your RSLogix 5000 project.
7.
To change the network properties from default settings to those that best fit your network, access the network properties.
A.
Click Network.
B.
Click Properties.
Publication CNET-UM001C-EN-P - November 2005
3-16 Configure a ControlNet Module
8.
Configure the network parameters as needed.
A.
Configure the network parameters.
B.
Click OK.
The table Network Parameters for Scheduling the Network Offline
describes the parameters used on this screen.
Publication CNET-UM001C-EN-P - November 2005
This example shows the default media configuration of
1000m of RG6 coaxial cable.
Configure a ControlNet Module 3-17
Table 3.4 Network Parameters for Scheduling the Network Offline
Parameter
Network
Update
Time (ms)
Max.
Scheduled
Address
Description
The smallest user-configurable repetitive time cycle in milliseconds at which data can be sent on ControlNet.
This is the node with the highest network address that can use scheduled time on a ControlNet link. I/O data is transferred during scheduled time.
Max.
Unscheduled
Address
RSNetWorx for ControlNet software sets this value. We recommend that you do not change it.
Node with the highest network address that can use unscheduled time on a ControlNet link. Messaging data is transferred during unscheduled time.
Nodes set at addresses higher than the maximum unscheduled node do not communicate on the network, for example they will not display in
RSLinx software.
Designates if the network uses media redundancy Media
Redundancy
Network
Name
User-defined name of the network
9.
If necessary, change the media configuration. The default media configuration is sufficient in most cases. However, adjust the configuration if your network is longer or uses repeaters. If the media configuration does not accurately represent the maximum propagation delay between any two nodes, your network may experience errors.
Publication CNET-UM001C-EN-P - November 2005
3-18 Configure a ControlNet Module
A.
Select Optimize and re-write schedule for all connections.
B.
Click OK.
10.
Save the file.
11.
Return to your RSLogix 5000 project to: a. save the project again.
b. download configuration, as described in the section Download the
Project to the Logix5000 Controller.
Publication CNET-UM001C-EN-P - November 2005
Click File > New.
Configure a ControlNet Module 3-19
Schedule the Network Online
The following instructions assume that all keepers are unconfigured or do not conflict with the current network. If your network has already been scheduled and you made a change to it, you must reschedule it.
Refer to the section Reschedule a ControlNet Network That Has Previously
Been Scheduled for more information.
1.
Start RSNetWorx for ControlNet software.
2.
Create a new ControlNet file.
3.
Choose a ControlNet configuration for the new file.
Choose ControlNet and click OK.
Click Network > Online.
4.
Go online.
Publication CNET-UM001C-EN-P - November 2005
3-20 Configure a ControlNet Module
5.
Select a communication path to the ControlNet network.
A.
Expand the tree to find your communication path.
B.
Select your communication path.
C.
Click OK.
Select Network > Single Pass Browse.
The window above uses a previously configured communication path to the controller. In this example, the computer is connected to the
ControlNet network via a 1784-PCIC card. The driver was previously
configured via RSLinx software, as described in the chapter Connect a
Computer to the ControlNet Network.
6.
Set the network to Single Browse Pass.
Check Edits Enabled.
7.
Enable edits on the file. When you enable edits, the RSNetWorx for
ControlNet software reads data in the ControlNet modules and builds a schedule for the network.
Publication CNET-UM001C-EN-P - November 2005
A.
Click Network.
B.
Click Properties.
8.
Access the network properties.
Configure a ControlNet Module 3-21
9.
Configure the network parameters.
A.
Configure the network parameters.
B.
Click OK.
The table Network Parameters for Scheduling the Network Online
describes the parameters used on this screen.
Publication CNET-UM001C-EN-P - November 2005
3-22 Configure a ControlNet Module
Table 3.5 Network Parameters for Scheduling the Network Online
Parameter
Network Update
Time (ms)
Max. Scheduled
Address
Description
The smallest user-configurable repetitive time cycle in milliseconds at which data can be sent on ControlNet.
This is the node with the highest network address that can use scheduled time on a ControlNet link. I/O data is transferred during scheduled time.RSNetWorx for ControlNet software sets this value. We recommend that you do not change it.
Max. Unscheduled
Address
Node with the highest network address that can use unscheduled time on a ControlNet link. Messaging data is transferred during unscheduled time.
Media Redundancy
Network Name
Nodes set at addresses higher than the maximum unscheduled node do not communicate on the network, for example they will not display in RSLinx software.
Designates if the network uses media redundancy on any of the network communication modules.
User-defined name of the network
10.
If necessary, change the media configuration. The default media configuration is sufficient in most cases. However, adjust the configuration if your network is longer or uses repeaters. If the media configuration does not accurately represent the maximum propagation delay between any two nodes, your network may experience errors.
This example shows the default media configuration of
1000m of RG6 coaxial cable.
11.
Save the file. This will schedule and activate the network.
A.
Select Optimize and re-write schedule for all connections.
B.
Click OK.
12.
In RSLogix 5000 software, save the online project.
Publication CNET-UM001C-EN-P - November 2005
A.
Click File.
B.
Click Open.
Configure a ControlNet Module 3-23
Reschedule a ControlNet Network That Has Previously
Been Scheduled
If you change a network that has already been scheduled, you must reschedule the network for the changes to take effect. For example, if you add I/O to an existing ControlNet network, you must reschedule the network for the I/O to become active.
1.
Start RSNetWorx for ControlNet software.
2.
Open the ControlNet file that matches the existing network.
C.
Select the file.
D.
Click Open.
A.
Click Network.
B.
Click Online.
3.
Go online.
Publication CNET-UM001C-EN-P - November 2005
3-24 Configure a ControlNet Module
4.
Enable edits on the file. When you enable edits, the RSNetWorx for
ControlNet software reads data in the ControlNet modules and builds a schedule for the network.
Click Enable
Edits.
5.
Save the file. This will schedule and activate the network.
A.
Select Optimize and re-write schedule for all connections.
B.
Click OK.
IMPORTANT
It is always preferable to optimize connections. However, in some cases involving multiple controllers, the Merge changes... option is available. This option lets controllers whose connections have not changed to continue uninterrupted operation. When you merge changes into the existing schedule, those controllers whose connections have not changed remain in Run mode rather than changing to Program mode.
6.
In RSLogix 5000 software, save the online project.
Publication CNET-UM001C-EN-P - November 2005
1
Chapter
4
Control I/O
Use This Chapter
Read this chapter for:
•
1756-CN2, 1756-CN2R modules
•
1756-CNB, 1756-CNBR modules
•
1769-L32C, 1769-L35CR controllers
•
1784-PCICS, 1784-PKTCS cards
•
1788-CNx cards
•
1794-ACN15, -ACNR15 adapters
•
1797-ACNR15 adapter
This chapter describes how a controller controls distributed I/O over
ControlNet. The controller requires a communication module to connect to the network. Distributed I/O modules require an adapter to connect to the network.
For This Information
Set a Requested Packet Interval
Add Local and Remote ControlNet Modules
See Page
To control distributed I/O over ControlNet, you must:
• Add local and remote ControlNet communication modules to your
RSLogix 5000 project.
When you create a new RSLogix 5000 project with the CompactLogix
1769-L32C or 1769-L35CR controller, the Controller Organizer creates a ControlNet port in the local chassis. In this case, you do not need to add a separate local communication module.
• Add distributed I/O to your RSLogix 5000 project.
• Schedule the ControlNet network via RSNetWorx for ControlNet software.
• Use the I/O information in RSLogix 5000 software.
You can also validate connections to distributed I/O when controlling it over
ControlNet. This task is particularly useful when one or more of the connections are not working but is not required, especially when all connections appear to work normally.
Publication CNET-UM001C-EN-P - November 2005
4-2 Control I/O
Set Up the Hardware
Local Chassis
Logix5000 Controller
With ControlNet
Communication Module
In this example, the Logix5000 controller uses a ControlNet communication module in the local chassis to connect to the ControlNet network. The distributed (remote) I/O has a ControlNet adapter to connect it to the
ControlNet network.
Data
Distributed I/O
ControlNet Adapter
With I/O Modules
Set a Requested
Packet Interval
Programming
Terminal
43611
Make sure:
• all wiring and cabling is properly connected.
• the communication driver (such as, AB-PCICS-1) is configured for the programming workstation.
When you configure an I/O module, you define the RPI for the module. The
RPI specifies the period at which data updates over a connection. For example, an input module sends data to a controller at the RPI that you assign to the module. Configure the RPI in milliseconds.
RPIs are only used for modules that produce or consume data. For example a local ControlNet communication module does not require an RPI because it is not a data-producing member of the system; it is used only as a bridge.
In Logix5000 controllers, I/O values update at a period that you configure via the I/O configuration folder of the project. The values update asynchronously to the execution of logic. At the specified interval, the controller updates a value independently from the execution of logic.
Publication CNET-UM001C-EN-P - November 2005
Select a
Communication Format
Control I/O 4-3
When you configure a remote ControlNet communication module or an I/O module, you select a communication format. The communication format you choose determines the data structure for the tags that are associated with the module. Many I/O modules support different formats. Each format uses a different data structure.
The communication format that you choose also determines:
• Direct or rack optimized connection
• Ownership of outputs
For a remote ControlNet communication module, you must select one of the
formats listed in the table Communication Formats.
Table 4.1 Communication Formats
Use This Communication
Format with a Remote
ControlNet Communication
Module
None
In These Scenarios
Rack optimized
Rack optimized - Listen only
•
All of the remote I/O communicating with a controller via the remote ControlNet communication module use a Direct Connection communication format.
•
The connection is used for scheduled peer interlocking.
•
When I/O will be predominately direct connections.
•
When multiple controllers control the outputs in the chassis
•
Some or all of the remote I/O communicating with a controller via the remote ControlNet communication module use a Rack Optimized communication format.
•
To minimize ControlNet bandwidth when using large volume of digital I/O.
•
If only one controller will control the I/O.
•
Some or all of the remote I/O communicating with a controller via the remote ControlNet communication module use a Rack Optimized communication format.
•
The connection is going to read inputs but is not going to be controlling outputs.
Publication CNET-UM001C-EN-P - November 2005
4-4 Control I/O
For I/O modules the available communication formats depend on the module type. This table describes the different communication formats for general module types.
Table 4.2 Communication Format for Module Types
If You Have This Type of I/O Module digital module
And Want Select a Communication Format That Specifies a rack optimized connection a direct connection or to use specialty features of the module, such as diagnostics, timestamps, or electronic fuses
Rack Optimization
The data your controller needs from the I/O module. For example, if your application uses a 1756-IA16I module in a remote chassis that must provide timestamped input data, you should select the CST
Timestamped Input Data communication format.
analog module or to only listen to data from the module a direct connection or to use specialty features of the module, such as diagnostics, timestamps, or electronic fuses
A Listen Only communication format that matches the data the I/O module is broadcasting to other controllers.
The data your controller needs from the I/O module. For example, if your application uses a 1756-OF6CI module in a remote chassis that must provide floating point output data, you should select the Float
Data communication format.
or to only listen to data from the module
A Listen Only communication format that matches the data the I/O module is broadcasting to other controllers.
See the online help in RSLogix 5000 programming software for specific communication formats per I/O module.
Publication CNET-UM001C-EN-P - November 2005
Control I/O 4-5
This Term
Direct Connection
Direct or Rack Optimized Connection
Logix5000 controllers use connections to transmit I/O data. These connections can be direct connections or rack optimized connections.
Means
A direct connection is a real-time, data transfer link between the controller and an I/O module–analog or digital.
This connection enables your controller to collect more data from an I/O module. For example, with a direct connection, the controller can collect diagnostic status data from a 1756-IA8D module that would not be collected in a rack optimized connection.
The controller maintains and monitors the connection with the I/O module. Any break in the connection, such as a module fault or the removal of a module while under power, sets fault bits in the data area associated with the module.
Rack optimized
Connection
A direct connection is any connection that does not use the Rack Optimization
Comm Format.
Digital I/O modules only – A rack optimized connection consolidates connection usage between the controller and all the digital I/O modules in the chassis (or DIN rail). Rather than having individual, direct connections for each I/O module, there is one connection for the entire chassis (or DIN rail).
Anytime a remote chassis houses I/O modules that use rack optimized connections, the remote ControlNet communication module connecting these modules to their owner-controller must also use a rack optimized connection. However, you can mix direct and rack optimized connections to the same remote chassis. For example, if your remote chassis houses 6 digital I/O modules and your application requires that you use direct connections for 3 but rack optimized connections for the other others, you can select direct connections for the 3 that require them and rack optimized connections for the other 3. In this case, even though you must use a rack optimized connection for the remote ControlNet communication module the owner-controller still makes direct connections with the 3 I/O modules that are configured as such.
You can only make up to 5 rack optimized connections to a single remote ControlNet communication module. rack optimized connection
Publication CNET-UM001C-EN-P - November 2005
4-6 Control I/O
Direct Connections for I/O Modules
In this example, assume that each distributed I/O module is configured for a direct connection to the controller.
Controller with ControlNet
Communication Module
ControlNet Network
I/O I/O I/O I/O I/O I/O
ControlNet Adapter with
Digital I/O Modules
ControlNet Adapter with
Analog I/O Modules
ControlNet Adapter with
Digital I/O Modules
This table calculates the connections in this example.
Table 4.3 Connection Calculations
System Connections
Controller to local ControlNet communication module
Controller to ControlNet adapter
(1)
Amount
0
0 direct connection for digital I/O modules
4 direct connection for analog I/O modules
2 total connections used: 6
(1)
In this example, the remote ControlNet adapter uses the None communication format.
TIP
If you have a high number of modules, direct connections to each module may not be feasible because the module supports a finite number of connections, and direct connections may require more resources than the module has available.
In this case, use rack optimized connections (see the section Rack Optimized Connections for I/O Modules) to conserve connection use and network traffic.
Publication CNET-UM001C-EN-P - November 2005
Control I/O 4-7
Rack Optimized Connections for I/O Modules
In this example, assume that each digital I/O module is configured for a rack optimized connection to the controller. Analog modules must be configured for direct connections.
Controller with ControlNet
Communication Module
ControlNet Network
I/O I/O I/O I/O I/O I/O
ControlNet Adapter with
Digital I/O Modules
ControlNet Adapter with
Analog I/O Modules
ControlNet Adapter with
Digital I/O Modules
This table calculates the connections in this example.
Table 4.4 Connection Calculations
System Connections
Controller to local ControlNet communication module
Controller to ControlNet adapters with digital modules
(rack optimized connection to each adapter)
Controller to ControlNet adapter with analog modules 0
(direct connection for each analog I/O module) 2 total connections used: 4
Amount
0
2
The rack optimized connection conserves connections, but can limit the status and diagnostic information that is available from the digital I/O modules.
To increase the number of available connections, use a rack optimized connection to any remote adapter with multiple digital I/O modules that allow rack optimized connection, instead of direct connections to those I/O modules.
Publication CNET-UM001C-EN-P - November 2005
4-8 Control I/O
Owner Controller
Ownership
In a Logix5000 system, modules multicast data. This means that multiple controllers can receive the same data at the same time from a single module.
When you choose a communication format, you have to choose whether to establish an owner or listen-only relationship with the module.
The controller that creates the primary configuration and communication connection to a module. The owner controller writes configuration data and can establish a connection to the module. The owner controller is the only device that controls the outputs.
An owner connection is any connection that does not include Listen-Only in its
Comm Format.
Listen-only Connection An I/O connection where another controller owns/provides the configuration data for the I/O module. A controller using a listen-only connection only monitors the module. It does not write configuration data and can only maintain a connection to the I/O module only when the owner controller is actively controlling the I/O module. listen-only connection
Publication CNET-UM001C-EN-P - November 2005
Control I/O 4-9
Choose the Type of Ownership for a Module
Table 4.5 Choose the Type of Module Ownership
If The Module Is An And Another Controller
Input Module Does not own the module
Owns the module
Output Module Does not own the module
Owns the module
And You Want To
Maintain communication with the module if it loses communication with the other controller
Stop communication with the module if it loses communication with the other controller
Then Use This Type of Connection
Owner, such as: not listen-only
Owner, such as: not listen-only
Use the same configuration as the other owner controller.
Listen-only
Owner, such as: not listen-only
Listen-only
There is a noted difference in controlling input modules versus controlling output modules
Table 4.6 Module Ownership Control
Controlling
Input Modules
This Ownership
Owner
Listen-only
Output Modules Owner
Listen-only
Description
The controller that establishes an owner connection to an input module configures that module. This configuring controller is the first controller to establish an owner connection.
Once a controller owns and configures an input module, other controllers can establish owner connections to that module. This lets additional owners to continue to receive multicasted data if the original owner-controller’s connection to the module breaks. All other additional owners must have the identical configuration data and identical communication format that the original owner controller has, otherwise the connection attempt is rejected.
Once a controller owns and configures an input module, other controllers can establish a listen-only connection to that module. These controllers can receive multicast data while another controller owns the module. If all owner controllers break their connections to the input module, all controllers with listen-only connections no longer receive multicast data.
The controller that establishes an owner connection to an output module configures that module. Only one owner connection is allowed for an output module. If another controller attempts to establish an owner connection, the connection attempt is rejected.
Once a controller owns and configures an output module, other controllers can establish listen-only connections to that module. These controllers can receive multicast data while another controller owns the module. If the owner controller breaks its connection to the output module, all controllers with listen-only connections no longer receive multicast data.
Publication CNET-UM001C-EN-P - November 2005
4-10 Control I/O
Add Local and Remote
ControlNet Modules
Before you can connect to and control distributed I/O, you must add local and remote ControlNet communication modules. The type of distributed I/O determines your choice of a remote ControlNet adapter. For more
information, see the table Choose the Appropriate Remote Adapter.
Table 4.7 Choose the Appropriate Remote Adapter
If The Distributed I/O Is Select This Remote
Adapter
1756 ControlLogix I/O 1756-CN2, 1756-CN2R
1756-CNB, 1756-CNBR
1794 FLEX I/O
1797 FLEX Ex I/O
1794-ACN15,
1794-ACNR15
1797-ANCR
1734 POINT I/O 1734-ACNR
Which You Configure Via
RSLogix 5000 software
The figure Add Local and Remote ControlNet Modules to an RSLogix 5000
Project shows a brief series of screens used when adding local and remote
ControlNet communication modules to an RSLogix 5000 project. For more detailed information on how to add local and remote ControlNet modules to
your project, see the chapter Configure a ControlNet Module.
Figure 4.1 Add Local and Remote ControlNet Modules to an RSLogix 5000 Project
1.
Add Local ControlNet Communication Module
2.
Add Remote ControlNet Communication Module.
Publication CNET-UM001C-EN-P - November 2005
Control I/O 4-11
Add Distributed I/O
For a Typical Distributed I/O Network
Controller
Local
Communication
Module
To communicate with the I/O modules in your system, you add bridge, adapter, and I/O modules to the I/O Configuration folder of the controller.
Within the I/O Configuration folder, you organize the modules into a hierarchy (tree/branch, parent/child).
Remote
Adapter
I/O
Module
Device
You Build the I/O Configuration in This Order
A.
Add the local communication module (bridge).
B.
Add the remote adapter for the distributed I/O chassis or DIN rail.
C.
Add the distributed I/O module.
Do these steps to add distributed I/O to your RSLogix 5000 project:
1.
Add the local and remote ControlNet communication modules as
described in section Add Local and Remote ControlNet Modules or in
the chapter Configure a ControlNet Module .
2.
Add the distributed I/O module.
A.
Right-click on the remote
ControlNet communication module.
B.
Click New Module.
Publication CNET-UM001C-EN-P - November 2005
4-12 Control I/O
To
Use the module’s default configuration.
Customize the configuration.
Do This
Specify the general information about the module, such as name, comm format,
RPI and click Finish.
Specify the general information about the module such as name, comm format,
RPI. Then click Next to step through subsequent screens to configure such parameters as filter times and fault actions.
3.
Configure the distributed I/O module. Depending on the distributed
I/O type, the configuration screens differ. The example below shows screen for a 1794-IB16XOB16P/A digital combo module.
For more information on configuring distributed I/O modules over
ControlNet, see the modules’ individual technical documentation and the RSLogix 5000 software online help.
Publication CNET-UM001C-EN-P - November 2005
The Comm Format selection you make when you add distributed I/O modules is based on whether you want rack optimized or direct connections to each distributed I/O module. In general, use this table to select distributed
I/O formats.
Control I/O 4-13
Table 4.8 Distributed I/O Formats
If You Select This Format For The
Remote Adapter
Rack Optimization
None
Select This Format For The Distributed
I/O Module
Rack Optimization an appropriate direct-connection format
Access Distributed I/O
This Address Variable
Location
SlotNumber
Type
MemberName
SubMemberName
Bit (optional)
I/O information is presented as a structure of multiple fields that depend on the specific features of the I/O module. The name of the structure is based on the location of the I/O module in the system. Each I/O tag is automatically created when you configure the I/O module in RSLogix 5000 software. Each tag name follows this format: where:
Location:SlotNumber:Type.MemberName.SubMemberName.Bit
Is
Identifies network location
LOCAL = local DIN rail or chassis
ADAPTER_NAME = identifies remote adapter or bridge that you specify
Slot number of I/O module location in its chassis
Type of data
I = input
O = output
C = configuration
S = status
Specific data from the I/O module; depends on the type of data the module can store. For example,
Data and Fault are possible fields of data for an I/O module. Data is the common name for values that are sent to or received from I/O points.
Specific data related to a MemberName.
Specific point on the I/O module; depends on the size of the I/O module (0-31 for a 32-point module)
Publication CNET-UM001C-EN-P - November 2005
4-14 Control I/O
Double-click on the Controller Tags portion of your RSLogix 5000 project.
I/O information is available in the Controller Tags portion of your RSLogix
5000 project. You can monitor or edit the tags. The example screens below show how to access the Controller Tags and some sample tags.
Publication CNET-UM001C-EN-P - November 2005
The screen above contains a tag named:
Remote_FLEX_CNET_adapter:1:C.Filter_0
where:
This Address Variable
Location
SlotNumber
Type
MemberName
Is
Remote_FLEX_CNET_adapter
1
Configuration
Filter_0
EXAMPLE
Control I/O 4-15
The example below shows an I/O tree configured with a remote FLEX I/O adapter and four remote FLEX I/O modules.
Example 1
Example 2
Example 3
Example 4
Example 5
The table Example Tag Names describes some of the tag names that appear
for these modules. The tags listed are not a complete list of the tags created for each module type. For a full list of the tags created for each module when configured as shown the second column, see the tag monitor/editor portion of
RSLogix 5000 software.
Publication CNET-UM001C-EN-P - November 2005
4-16 Control I/O
Example
Example 1
Example 2
Example 3
Example 4
Example 4
Table 4.9 Example Tag Names
Module remote 1794-ACN15 adapter
“FLEX_adapter”
Example Tag Names (automatically created by the software)
FLEX_adapter:I
FLEX_adapter:I.SlotStatusBits
FLEX_adapter:I.Data
FLEX_adapter:O
FLEX_adapter:O.Data
remote 1794-IA16
“Input_module” in slot 0 rack optimized connection remote 1794-OB8EP
“Output_module” in slot 1 rack optimized connection
FLEX_adapter:0:C
FLEX_adapter:0:C.Config
FLEX_adapter:0:C.DelayTime_0
FLEX_adapter:0:I
FLEX_adapter:1:C
FLEX_adapter:1:C.SSData
FLEX_adapter:1:O
FLEX_adapter:1:O remote 1794-IRT8
“RTD_thermocouple” in slot 2 direct connection remote 1794-IF2XOF2I
“Combo_analog” in slot 3 direct connection
FLEX_adapter:2:C
FLEX_adapter:2:C.Config1
FLEX_adapter:2:C.FilterCutoff0
FLEX_adapter:2:C.ReferenceJunction3
FLEX_adapter:2:C.FaultMode_0_3
FLEX_adapter:2:C.DataFormat11
FLEX_adapter:2:I
FLEX_adapter:2:I.Fault
FLEX_adapter:2:I.Ch0Data
FLEX_adapter:2:I.Alarms
FLEX_adapter:3:C
FLEX_adapter:3:C.InputFilter
FLEX_adapter:3:C.RTSInterval
FLEX_adapter:3:C.Ch0InputCalibrate
FLEX_adapter:3:I
FLEX_adapter:3:I.Fault
FLEX_adapter:3:I.RealTimeSample
FLEX_adapter:3:O
FLEX_adapter:3:O.SafeStateConfig0
FLEX_adapter:3:O.OutputEnable
FLEX_adapter:3:O.Ch0OutputData
Publication CNET-UM001C-EN-P - November 2005
Validate Connections
Control I/O 4-17
Verify that the controller can communicate with the devices that you have just configured. Do these steps:
1.
Determine if communications has been established with the devices.
a. If a
!
is NOT over the I/O Configuration folder, the controller can communicate with the device. Connections are valid.
b. If a
!
is over the I/O Configuration folder, the controller cannot communicate with the device. Go to step 2.
2.
Identify any faults.
Start looking for faults at the communication module and work down through the tree. In the example screen below, faults occurred at the remote 1756-CNB module and the I/O modules added below it.
Publication CNET-UM001C-EN-P - November 2005
4-18 Control I/O
A.
Right-click on the fault module.
B.
Click Properties.
3.
Identify the fault code.
If multiple faults appear on the screen, as shown above, identify the fault at the module that is highest in the I/O tree.
C.
Click on the Connection tab.
D.
Identify the code for the fault.
E.
Use the Help button to access the online help and determine what the fault codes mean.
For more information on fault codes, see step 4 on page 4-19.
Publication CNET-UM001C-EN-P - November 2005
A.
Click Help.
B.
Click Contents
C.
Click on the Index tab.
D.
Type module faults.
Control I/O 4-19
4.
If necessary, get the definition of the fault code from the online help.
E.
When the list of module fault codes appears, select the range for the code you just identified.
F.
Click Display.
5.
Follow the recommendations for your fault code.
6.
Return to the step: Determine if communications has been established with the devices.
Publication CNET-UM001C-EN-P - November 2005
4-20 Control I/O
Notes:
Publication CNET-UM001C-EN-P - November 2005
Chapter
5
Produce and Consume Tags
(Interlock Controllers)
1
Use This Chapter
Read this chapter for:
•
1756-CN2, 1756-CN2R modules
•
1756-CNB, 1756-CNBR modules
•
1769-L32C, 1769-L35CR controllers
•
1784-PCICS, 1784-PKTCS cards
•
1788-CNx cards
This chapter describes how to interlock (produce and consume tags) controllers via a ControlNet network.
For This Information
See Page
5-1
5-2
Determine Connections for Produced and Consumed Tags
Organize Tags for Produced or Consumed Data
Adjust for Bandwidth Limitations
5-3
Additional Steps for a PLC-5C or ControlNet Scanner Card 5-12
Interlocking controllers is a method of sharing scheduled data between controllers. Methods of communicating with other controllers are listed below:
If The Data
Needs regular, fast delivery at an interval that you specify
Is sent when a specific condition occurs in your application
Then
Produce and consume a tag
Execute a message (MSG) instruction
See Chapter
Terminology
A Logix5000 controller lets you produce (broadcast) and consume (receive) system-shared tags.
Term produced tag
Definition
A tag that a controller makes available for use by other controllers. Multiple controllers can simultaneously consume (receive) the data. A produced tag sends its data to one or more consumed tags (consumers) without using logic.
The produced tag sends its data at the RPI of the fastest consuming tag.
consumed tag
A tag that receives the data of a produced tag. The data type of the consumed tag must match the data type (including any array dimensions) of the produced tag. The RPI of the fastest consumed tag determines the period at which the produced tag is produced.
For two controllers to share produced or consumed tags, both controllers must be attached to the same ControlNet network.
Publication CNET-UM001C-EN-P - November 2005
5-2 Produce and Consume Tags (Interlock Controllers)
Set Up the Hardware
Chassis #1
Logix5000 Controller with ControlNet
Communication Module
In this example, the controller in the first chassis produces a tag that is consumed by the controller in the second chassis.
Data
Chassis #2
Logix5000 Controller with ControlNet
Communication Module
ControlNet
Programming
Terminal
43611
The Logix5000 controller in the first chassis and in the second chassis can be any of the following, with their ControlNet communication modules:
• 1756 ControlLogix controller with a 1756-CN2 or 1756-CN2R communication module in the chassis
• 1756 ControlLogix controller with a 1756-CNB or 1756-CNBR communication module in the chassis
• 1769-L32C or 1769-L35CR CompactLogix controller
• 1789 SoftLogix controller with a 1784-PCICS or 1788-PKTCS communication card
• 1794 FlexLogix controller with a 1788-CNx ControlNet communication card
• PowerFlex 700S with DriveLogix controller and a 1788-CNx
ControlNet communication card
• Non-Logix5000 controller or other device connected to ControlNet via a ControlNet scanner card. For more information refer to the section
Additional Steps for a PLC-5C or ControlNet Scanner Card.
Make sure that:
• the ControlNet communication modules are connected to a scheduled
ControlNet network.
• all wiring and cabling is properly connected.
Publication CNET-UM001C-EN-P - November 2005
Produce and Consume Tags (Interlock Controllers) 5-3
• the communication driver (such as., AB-PCICS-1) is configured for the programming workstation.
TIP
If you are only sharing tags between ControlLogix controllers (the controllers are not controlling any I/O modules), you can set the communication format of the
1756-CN2(R) or the 1756-CNB(R) module in the remote chassis to None. This reduces connection usage and network traffic.
Determine Connections for
Produced and Consumed
Tags
Logix controllers can produce (broadcast) and consume (receive) system-shared tags that are sent and received via the ControlNet communication module. Produced and consumed tags each require connections.
This Type of Tag Requires These Connections produced The produced tag requires two connections. The producing controller must have one connection for the produced tag and the first consumer and one more connection for each additional consumer
(heartbeat). The heartbeat is a small scheduled packet the consumer sends to indicate that it is getting the produced data.
consumed
As you increase the number of controllers that can consume a produced tag, you also reduce the number of connections the controller has available for other operations, like communication and
I/O.
Each consumed tag requires one connection for the controller that is consuming the tag.
All ControlNet modules support at least 32 connections. Additionally, the total number of tags that can be produced or consumed is limited by the number of available connections. If the communication module uses all of its connections for I/O and other communication modules, no connections are left for produced and consumed tags.
Publication CNET-UM001C-EN-P - November 2005
5-4 Produce and Consume Tags (Interlock Controllers)
This table describes each produced or consumed tag and the number of connections used.
Table 5.1 Produced and Consumed Tags and number of Connections
A Consumed Tag Uses This
Many Connections
This Controller Has This Many
Connections Available
A Produced Tag Uses This
Many Connections
CompactLogix
FlexLogix 100
PowerFlex 700S with DriveLogix
ControlLogix
250
SoftLogix5800
This Communication Card Has This Many
Connections Available
32 ControlNet port on the
CompactLogix controller
1788-CNx card in either:
•
FlexLogix controller
•
PowerFlex 700S with
DriveLogix controller
32 total ControlNet connections,
22 of which can be scheduled and used for producing and consuming tags number of consumers + 1
A Produced Tag Uses This
Many Connections
1756-CN2 in the local chassis of a ControlLogix controller
1756-CNB in the local chassis of a ControlLogix controller
100
1784-PCICS card in a SoftLogix5800 controller
64 - We recommend that you do not use more than 40 to 48 scheduled connections.
127 number of consumers
1
A Consumed Tag Uses This
Many Connections
1
Publication CNET-UM001C-EN-P - November 2005
Produce and Consume Tags (Interlock Controllers) 5-5
Organize Tags for Produced or Consumed Data
This table describes the guideline to follow as you organize your tags for produced or consumed data (shared data).
Table 5.2 Guidelines for Produced or Consumed Data Tags
Guideline
Create the tags at the controller scope.
Produce and consume specific tags.
Use one of these data types:
•
DINT
•
REAL
• array of DINTs or REALs
• user-defined
Limit the size of the tag to
≤
480 bytes.
To share tags with a PLC-5C controller, use a user-defined data type.
Details
You can only produce and consume controller-scoped tags.
You cannot produce or consume the following tag types:
•
Alias
•
Axis type
•
BOOL
•
Consumed
•
I/O
•
INT
•
Message
•
To share other data types, create a user-defined data type that contains the required data.
•
Use the same data type for the produced tag and corresponding consumed tag or tags.
If you must transfer more than 480 bytes, create logic to transfer the data in smaller packets or create multiple produce/consume tags.
To produce consume
This integers, BOOLs or combinations of both
Then
Create a user-defined data type that contains an array of INTs with an even number of elements, such as INT[2].
only one REAL value Use the REAL data type.
more than one REAL value
Create a user-defined data type that contains an array of REALs.
integers Create a user-defined data type that contains the following members:
Data type
DINT
Description
Status
Use the highest permissible RPI for your application.
INT[x], where x is the output size of the data from the PLC-5C controller. (If you are consuming only one INT, omit x .)
BIT 0 = 0 PLC5 in PROG mode
= 1 PLC5 in RUN mode
Data produced by a PLC-5C controller
If the controller consumes the tag over a ControlNet network, use a binary multiple of the ControlNet network update time (NUT). For example, if the NUT is 5 ms, use an RPI of 5, 10, 20, 40 ms.
Publication CNET-UM001C-EN-P - November 2005
5-6 Produce and Consume Tags (Interlock Controllers)
Guideline
Combine data that goes to the same controller.
Details
If you are producing several tags for the same controller:
•
Group the data into one or more user-defined data types. (This uses less connections than producing each tag separately.)
•
Group the data according to similar update intervals. (To conserve network bandwidth, use a greater RPI for less critical data.)
For example, you could create one tag for critical data and another tag for data that is not as critical.
Adjust for Bandwidth
Limitations
When you share a tag over a ControlNet network, the tag must fit within the bandwidth of the network:
• As the number of connections over a ControlNet network increases, several connections, including produced or consumed tags, may need to share a network update time (NUT).
• A ControlNet node can transmit approximately 500 bytes of scheduled data in a single NUT.
Depending on the size of your system, you may not have enough bandwidth on your ControlNet network for large tags. If a tag is too large for your
ControlNet network, make one or more of the following adjustments.
Table 5.3 Tag Adjustments
Adjustment
Increase the requested packet interval (RPI) of your connections – Recommended method
Reduce your network update time (NUT).
For a ControlNet bridge module, CN2(R) or
CNB(R) in a remote chassis, select the most efficient communication format for that chassis:
Description
At higher RPIs, connections can take turns sending data during an update period.
At a faster NUT, less connections have to share an update period.
Are most of the modules in the chassis non-diagnostic, digital I/O modules?
Then select this communication format for the remote CN2 or CNB module:
Separate the tag into two or more smaller tags.
Yes
No
Rack Optimization
None
The Rack Optimization format uses an additional 8 bytes for each slot in its chassis. Analog modules or modules that are sending or getting diagnostic, fuse, timestamp, or schedule data require direct connections and cannot take advantage of the rack optimized form.
Selecting “None” frees up the 8 bytes per slot for other uses, such as produced or consumed tags.
1. Group the data according to similar update rates. For example, you could create one tag for data that is critical and another tag for data that is not as critical.
Create logic to transfer the data in smaller sections (packets).
2. Assign a different RPI to each tag.
For information on how to do this, see the Logix5000 Controllers Common Procedures
Programming Manual, publication 1756-PM001.
Publication CNET-UM001C-EN-P - November 2005
Produce a Tag
Produce and Consume Tags (Interlock Controllers) 5-7
A Logix5000 controller can only produce controller-scoped user-created tags in the local controller’s tag structure. The Logix5000 controllers cannot produce I/O tags or tags aliased to I/O tags.
Follow the steps below to produce a tag:
1.
Open the RSLogix 5000 project that contains the tag that you want to produce.
IMPORTANT
You can only create produced tags when your RSLogix
5000 project is offline.
2.
Access the edit tab of the controller tags.
A.
Right-click on
Controller Tags.
B.
Click on Edit Tags.
3.
Create the tag you want to produce.
A.
Type the name of the new tag in an available
Tag Name field.
B.
Press Enter.
Publication CNET-UM001C-EN-P - November 2005
5-8 Produce and Consume Tags (Interlock Controllers)
4.
Access the tag properties.
A.
Right-click on the new tag name.
B.
Click on Edit Tag Properties.
5.
Change the tag properties as needed.
A.
Choose the Produced Tag Type.
B.
Make sure the Data Type is one that the controller can produce
A controller cannot produce a tag using the MSG [or INT]
Data Type.
C.
Click on the Connection tab.
D.
Adjust the number of consumers. If you are unsure of the number of consumers, you can use a number higher than the actual number of consumers. However, unused connections are deducted from the number of connections your controller has available.
E.
Click OK.
Publication CNET-UM001C-EN-P - November 2005
IMPORTANT
When your Logix5000 controller produces a tag, any device that interfaces to ControlNet can consume the tag.
However, when a non-Logix controller such as a PC using a 1784-PKTCS card, is consuming the tag produced by a
Logix controller, you must perform additional tasks in
RSNetWorx for ControlNet software.
For more information, see the section Additional Steps for a PLC-5C or ControlNet Scanner Card.
Consume a Tag
Local ControlNet Module in
Consuming Controller’s Chassis
Remote ControlNet Module
Producing Controller
Produce and Consume Tags (Interlock Controllers) 5-9
Logix5000 controllers can only consume controller-scoped user-created tags from another controller’s tag structure. The Logix5000 controllers cannot consume I/O tags or tags aliased to I/O tags. Follow the steps below to consume a tag:
IMPORTANT
You can only create consumed tags when your RSLogix
5000 project is offline.
1.
Open the RSLogix 5000 project that contains the controller that you want to consume the produced tag.
2.
Make the sure the controller producing the tag to be consumed is in the consuming controller’s I/O configuration, as shown in the example below. Additionally, make sure the Communication Format for the remote ControlNet module is None.
3.
Access the edit tab of the controller tags.
A.
Right-click on
Controller Tags.
B.
Click Edit Tags.
A.
Type the name of the new tag in an available
Tag Name field.
B.
Press Enter.
4.
Create the tag you want to consume.
Publication CNET-UM001C-EN-P - November 2005
5-10 Produce and Consume Tags (Interlock Controllers)
5.
Access the tag properties.
A.
Right-click on the new tag name.
B.
Click on Edit Tag Properties.
6.
Change the tag properties as needed.
A.
Choose the Consumed Tag Type.
B.
Make sure the Data Type and
Data Style matches the Type and Style in the tag created in step 5 on page 5-8.
C.
Click on the Connection tab.
D.
Choose the Producer, the producing controller, from the pull-down menu. The menu contains all possible paths to previously configured controllers in the I/O tree.
E.
Type in the name of the produced tag in the producing controller.
F.
Set the RPI. The consuming controller determines the rate at which the tag is produced.
G.
Click OK.
Publication CNET-UM001C-EN-P - November 2005
Produce and Consume Tags (Interlock Controllers) 5-11
7.
Use RSNetWorx for ControlNet software to schedule the network.
IMPORTANT
Your Logix5000 controller can consume a tag that was produced by any device that interfaces to ControlNet.
However, when a non-Logix controller such as a PC using a 1784-PKTCS card, produces the tag that a Logix controller consumes, you must perform additional tasks in
RSNetWorx for ControlNet. For more information, refer to the section Additional Steps for a PLC-5C or
ControlNet Scanner Card.
Publication CNET-UM001C-EN-P - November 2005
5-12 Produce and Consume Tags (Interlock Controllers)
Additional Steps for a
PLC-5C or ControlNet
Scanner Card
Some devices connect to the ControlNet network via a ControlNet scanner and can use produced and consumed tags to share scheduled data with
Logix5000 controllers. For example, you can connect a real-time control application, such as a Visual Basic application, to ControlNet through a
1784-PKTCS scanner card to exchange data with Logix5000 controllers.
When you use produced and consumed tags to exchange data between
Logix5000 controllers and a ControlNet scanner, you must also use the
RSNetWorx Scanlist Configuration Tool to configure the scanner to produce and consume the data sent to and/or received from the Logix5000 controllers.
The following ControlNet scanners require additional steps to exchange data with a Logix5000 controller via produced and consumed tags:
• PLC-5C controller
• 1784-PKTCS communication scanner card
– This card is used in a personal computer with a real-time control application and IOLinx or an HMI application and RSView ME.
• 2711P-RN15S communication scanner card
– This card is used in PanelView Plus and VersaView CE HMI terminals.
• 2711P-RN15C communication module
– This module is used in a PanelView Plus HMI terminal.
Publication CNET-UM001C-EN-P - November 2005
A.
Click Network.
B.
Click Online.
Produce and Consume Tags (Interlock Controllers) 5-13
Use RSNetWorx to Produce a Tag from a ControlNet Scanner
Use the RSNetWorx Scanlist Configuration tool to configure a ControlNet scanner to produce tags. In the example used for the following steps, a
2711P-RN15S ControlNet Scanner module located in a PanelView Plus terminal produces a tag for a ControlLogix controller to consume.
1.
Open the RSNetWorx for ControlNet file for your project.
2.
Go online.
3.
Enable edits.
Click Enable Edits.
A.
Right-click on the ControlNet scanner card.
B.
Click Scanlist Configuration.
4.
Access the Scanlist Configuration for the ControlNet Scanner.
Publication CNET-UM001C-EN-P - November 2005
5-14 Produce and Consume Tags (Interlock Controllers)
5.
Insert a Target for Connections on the ControlNet scanner that is producing the tag.
A.
Right-click on the
ControlNet scanner device.
B.
Click Insert Target for
Connections....
A.
Choose Send Data.
B.
Make sure the Produce Buffer
ID equals the Remote Data, the tag name or instance value for the consumed tag in
RSLogix 5000 software.
C.
Make sure the Output Size matches the consumed tag’s size.
Note that the size on this screen is in 16-bit words.
6.
When the Insert Target for Connections pop-up menu appears, make sure it is configured correctly.
7.
Save the file. This will schedule the network.
Publication CNET-UM001C-EN-P - November 2005
A.
Click Network.
B.
Click Online.
Produce and Consume Tags (Interlock Controllers) 5-15
Use RSNetWorx to Consume a Tag by a ControlNet Scanner
You must use the RSNetWorx Scanlist Configuration tool to configure a
ControlNet scanner to consume tags. In the example used for the following steps, a 2711P-RN15S ControlNet Scanner module located in a PanelView
Plus terminal consumes a tag produced by a ControlLogix controller.
1.
Open the RSNetWorx for ControlNet file for your project.
2.
Go online.
3.
Enable edits.
Click Enable Edits.
A.
Right-click on the
ControlNet scanner card.
B.
Click Scanlist Configuration.
4.
Access the Scanlist Configuration for the ControlNet Scanner.
Publication CNET-UM001C-EN-P - November 2005
5-16 Produce and Consume Tags (Interlock Controllers)
5.
Insert a connection to the Logix5000 controller that will consume the tag that the ControlNet scanner produces.
A.
Right-click on the
Logix5000 controller.
B.
Click Insert Connection.
A.
Choose Receive Data.
B.
Type Tag in the
Name field.
C.
Type the name of the
Produced tag from the
Logix5000 controller’s
RSLogix 5000 project in the Value field.
If this name does not exactly match the name of the produced tag, the
ControlNet scanner will not consume the tag.
D.
Make sure the Input Size matches the produced tag’s size.
Note that the size on this screen is in 16-bit words and must be an even number.
Publication CNET-UM001C-EN-P - November 2005
6.
When the Connection Properties pop-up menu appears, make sure the
Connection tab is configured correctly.
Produce and Consume Tags (Interlock Controllers) 5-17
When you are using a PLC-5C controller or a ControlNet scanner to consume tags, keep the following in mind about the Input Size field:
• If the scanner is consuming a DINT, in the Input Size field, enter two times the number of DINTs you need to read from the produced tag.
For example, if the produced tag contains 10 DINTs, enter 20 for the
Input size; the input size must be an even number.
• If the scanner is consuming REALs, in the Input Size field, enter two times the number of REALs you need to read from the produced tag.
For example, if the produced tag contains 10 REALs, enter 20 for the
Input size; the input size must be an even number.
7.
Save the file. This will schedule the network.
Reconstruct Values with PLC-5C Controller
When your Logix5000 controller produces REALs (32-bit floating-point values) to a PLC-5C controller, the PLC-5C consumes the data in consecutive
16-bit integers:
• The first integer contains the upper (left-most) bits of the value.
• The second integer contains the lower (right-most) bits of the value.
• This pattern continues for each floating-point value.
Publication CNET-UM001C-EN-P - November 2005
5-18 Produce and Consume Tags (Interlock Controllers)
EXAMPLE
The following example shows how to re-construct a REAL (floating point value) in the PLC-5C controller
Re-construct a floating point value. This example takes two consumed integers that were originally a produced REAL, reverses the order of the integers and assembles them into a floating point value equal to the original REAL.
The two MOV instructions reverse the order of the integers and move them to a new location.
Because the destination of the COP instruction is a floating-point address, it takes two consecutive integers, for a total of 32 bits, and converts them to a single floating-point value.
The length of a COP instruction is always multiplied by the size of the destination data type, so one in this example means one times the size of REAL, for example 32 bits. COP uses as many consecutive elements from the source file as necessary to satisfy this.
Consumed Integer Value A
Stored Data Low 16 Bits of the
Floating Point Word
42354
Consumed Integer Value B
Stored Data High 16 Bits of the
Floating Point Word
Stored Data Low 16 Bits of the
Floating Point Word
Final Floating Point Value
Publication CNET-UM001C-EN-P - November 2005
1
Chapter
6
Peer-to-Peer Messaging
Use This Chapter
Read this chapter for:
•
1756-CN2, 1756-CN2R modules
•
1756-CNB, 1756-CNBR modules
•
1769-L32C, 1769-L35CR controllers
•
1784-PCIC, 1784-PCICS,
1784-PKTCS cards
•
1788-CNx cards
This chapter describes how to use MSG instructions to send data to and receive data from other modules on a ControlNet network.
For This Information
Guidelines for MSG Instructions
Determine Connections for Messages
Configure a Message Instruction
Access Logix Data from a PLC-5 or SLC Processor
Route PLC-5 Messages Between ControlNet Networks
See Page
There are different methods of communicating with other controllers:
If the Data
Needs regular, fast delivery at an interval that you specify
Then
Produce and consume a tag
• is sent when a specific condition occurs in your application
• is sent at a slower rate than required by produced and consumed tags
• is sent to devices that only communicate with unscheduled data
Execute a message (MSG) instruction
See Chapter
Publication CNET-UM001C-EN-P - November 2005
6-2 Peer-to-Peer Messaging
Set Up the Hardware
Local Chassis
Logix5000 Controller
In this example, the controller in the local chassis sends a message (using a
MSG instruction) to another module (which can be a controller) on the
ControlNet network.
Data
Remote Chassis
ControlNet
Programming
Terminal
43611
The Logix5000 controller in the local chassis can be any of the following, with its ControlNet communication module:
• 1756 ControlLogix controller with a 1756-CN2 or 1756-CN2R communication module in the chassis
• 1756 ControlLogix controller with a 1756-CNB or 1756-CNBR communication module in the chassis
• 1769-L32C or 1769-L35CR CompactLogix controller
• 1789 SoftLogix controller with a 1784-PCIC, 1784-PCICS or
1784-PKTCS communication card
• 1794 FlexLogix controller with a 1788-CNx ControlNet communication card
• PowerFlex 700S with DriveLogix controller and a 1788-CNx
ControlNet communication card
Publication CNET-UM001C-EN-P - November 2005
Peer-to-Peer Messaging 6-3
The destination for the message can be any of the following:
• PLCs, SLC or Logix5000 controllers on ControlNet or other networks
• I/O modules, such as ControlLogix analog module configuration data on ControlNet or other networks
IMPORTANT
The 1769-L32C and 1769-L35CR controllers can produce and consume tags over ControlNet to other Logix5000 controllers. However, Compact I/O that is local to the
1769-L32C and 1769-L35CR controller is not accessible to other Logix5000 controllers.
• 1771 block transfer modules
Make sure that:
• the ControlNet communication modules are connected to a ControlNet network.
• all wiring and cabling is properly connected.
• the communication driver (such as, AB-PCICS-1) is configured for the programming workstation.
Publication CNET-UM001C-EN-P - November 2005
6-4 Peer-to-Peer Messaging
Guidelines for MSG
Instructions
This table describes guidelines to use when working with message instructions.
Table 6.1 Guidelines for MSG Instructions
Guideline
1. For each MSG instruction, create a control tag.
5. Cache the connected MSGs that execute most frequently.
Details
Each MSG instruction requires its own control tag. This tag contains control elements for messages, for example: DN and EN, error codes and information to execute the message such as destination path and number of words to transfer.
2. Keep the source and/or destination data at the controller scope.
3. If your MSG is to a module that uses
16-bit integers, use a buffer of INTs in the MSG and DINTs throughout the project.
•
Data type = MESSAGE
•
Scope = controller
•
The tag cannot be part of an array or a user-defined data type.
A MSG instruction can access only tags that are in the Controller Tags folder (controller scope).
If your message is to a module that uses 16-bit integers, such as a PLC-5® or SLC 500™ controller, and it transfers integers (not REALs), use a buffer of INTs in the message and
DINTs throughout the project.
4. If you want to enable more than 16
MSGs at one time, use some type of management strategy.
This increases the efficiency of your project because Logix5000 controllers execute more efficiently and use less memory when working with 32-bit integers (DINTs).
If you enable more than 16 MSGs at one time, some MSG instructions may experience delays in entering the queue. To guarantee the execution of each message, use one of these options:
•
Enable each message in sequence.
•
Enable the messages in smaller groups.
•
Program a message to communicate with multiple modules.
•
Program logic to coordinate the execution of messages.
Cache the connection for those MSG instructions that execute most frequently, up to the maximum number permissible for your controller revision.
6. Keep the number of unconnected and uncached MSGs less than the number of unconnected buffers.
This optimizes execution time because the controller does not have to open a connection each time the message executes.
The controller can have 10 - 40 unconnected outgoing buffers. The default number is 10.
•
If all the unconnected buffers are in use when an instruction leaves the message queue, the instruction errors and does not transfer the data.
•
You can increase the number of unconnected buffers to a maximum of 40.
For more information on programming MSG instructions, refer to the
Logix5000 Controller General Instructions Reference Manual, publication
1756-RM003. The individual system user manuals for Logix5000 controllers also provide MSG examples unique to specific controller platforms.
Publication CNET-UM001C-EN-P - November 2005
Peer-to-Peer Messaging 6-5
Determine Connections for
Messages
Messages transfer data to other modules, such as other controllers, I/O modules or operator interfaces. Each message uses one connection, regardless of how many modules are in the message path. To conserve connections, you can configure one message to read from or write to multiple modules. Also, you configure multiple messages for the same path and use only 1 connection if only 1 message is active at a time; however, this requires that you write your ladder logic correctly to make sure only 1 message is active at any time.
These connected messages can leave the connection open (cache) or close the connection when the message is done transmitting. The following table shows which messages use a connection and whether or not you can cache the connection:
Table 6.2 Message Connections and Communication Methods
This Type of Message
CIP generic
Using this
Communication Method
CIP CIP data table read or write
PLC2, PLC3, PLC5, or SLC (all types) CIP
CIP with Source ID
DH+
CIP
Uses a
Connection yes no no yes your choice
(1) yes block-transfer read or write na
(1)
You can connect CIP generic messages, but for most applications we recommend you leave CIP generic messages unconnected.
Guidelines for Caching Message Connections
Follow these guidelines when you consider whether to cache a connection or not:
Table 6.3 Caching Guidelines
If the Message
Executes
Repeatedly
Then You Should
Infrequently
Cache the connection.
This keeps the connection open and optimizes message completion time. Opening a connection each time the message executes increases execution time.
Do not cache the connection.
This closes the connection upon completion of the message, which frees up that connection for other uses.
Publication CNET-UM001C-EN-P - November 2005
6-6 Peer-to-Peer Messaging
Enter Message Logic
To send or receive data from a ControlNet module via a message, you must program a MSG instruction in the local controller’s logic. If the target module is configured in the I/O Configuration folder of the controller, you can browse to select the module. Otherwise, you can manually enter the message path in the MSG instruction.
Add the ControlNet Modules and Remote Devices to the Local
Controller’s I/O Configuration
Use Browse to select the target device of a MSG instruction and add that remote device to the I/O Configuration folder of the local controller. Within the I/O Configuration folder, you organize the local and remote devices into a hierarchy (tree/branch, parent/child).
For a Typical Local or Remote MSG Structure…
Local
Controller
Local
Communication
Module
Remote
Communication
Module
Remote
Controller
…You Build the I/O Configuration in this Order
1.
Add the local communication module for the local controller. Remember, the
1769-L35CR does not require that you add a local communication module.
2.
Add the remote communication module for the remote controller. The communication format for the remote module should be
None.
3.
Add the remote controller.
If the remote controller is added, you can browse to it as a destination when you configure the message instruction.
For more information on how to add ControlNet modules and remote devices to the local controller’s I/O configuration, see the chapter Controlling I/O.
Publication CNET-UM001C-EN-P - November 2005
Peer-to-Peer Messaging 6-7
EXAMPLE
Enter a Message
Use relay ladder logic to enter a MSG instruction. Click to configure the
MSG instruction.
Enter a MSG instruction
If user_bit and count_messages.EN = 0 (MSG instruction is not already enabled), then execute a
MSG instruction that sends data to another controller.
Configure a Message
Instruction
TIP
We recommend an XIO of the MSG control block tag.en, for example: the count_messages.EN
portion of the rung above, as an in series precondition for all message instructions
Do not manipulate the control bits of a message instruction.
To configure a MSG instruction, do these tasks:
1.
Click in the MSG box.
Publication CNET-UM001C-EN-P - November 2005
6-8 Peer-to-Peer Messaging
2.
On the Configuration tab, specify the type of MSG instruction:
A.
Choose a Message Type.
B.
Depending on the Message Type, you have additional parameters to configure.
For more information on how to configure the various Message types, see the tables Message Type to Configure a MSG to Logix5000
Controller, Message Type to
Configure a MSG to an SLC 500
Processor, and Message Type to
Configure a MSG to a PLC-5
Processor.
The message instruction’s destination determines what specific information is used on the Configuration tab.
Table 6.4 Select a Message Type Table
To Select a
Message Type to Configure a MSG to Logix5000
Message Type to Configure a MSG to an SLC 500
Message Type to Configure a MSG to a PLC-5
See Table
Message Type to Configure a
MSG to Logix5000 Controller
Message Type to Configure a
MSG to an SLC 500 Processor
Message Type to Configure a
MSG to a PLC-5 Processor
Message Type to Configure a MSG to Logix5000 Controller
Table 6.5 Message Type to Configure a MSG to Logix5000 Controller
If You Want To
Read (receive) the data
For This Item
Message Type
Source Element
Number of Elements
Destination Tag
Type or Select
CIP Data Table Read first element of the tag that contains data in the other controller number of elements to transfer first element of the tag (controller-scoped) in this controller for the data
Publication CNET-UM001C-EN-P - November 2005
Peer-to-Peer Messaging 6-9
Table 6.5 Message Type to Configure a MSG to Logix5000 Controller
If You Want To write (send) the data
For This Item
Message Type
Source Tag
Number of Elements
Destination Element
Type or Select
CIP Data Table Write first element of the tag (controller-scoped) in this controller that contains the data number of elements to transfer first element of the tag for the data in the other controller
Message Type to Configure a MSG to an SLC 500 Processor
Table 6.6 Message Type to Configure a MSG to an SLC 500 Processor
If The Data Is integer (s) floating-point (REAL)
And You Want To read (receive) data write (send) data read (receive) data write (send) data
For This Item
Message Type
Type or Select
SLC Typed Read
Source Element data table address in the SLC 500 controller, such as N7:10
Number of Elements number of integers to transfer
Destination Tag
Message Type first element of int_buffer
SLC Typed Write
Source Tag first element of int_buffer
Number of Elements number of integers to transfer
Destination Element data table address in the SLC 500 controller, such as N7:10
Message Type SLC Typed Read
Source Element data table address in the SLC 500 controller, such as F8:0
Number Of Elements number of values to transfer
Destination Tag first element of the tag (controller-scoped) in this controller for the data
SLC Typed Write Message Type
Source Tag first element of the tag (controller-scoped) in this controller that contains the data
Number Of Elements number of values to transfer
Destination Element data table address in the SLC 500 controller, such as F8:0
Publication CNET-UM001C-EN-P - November 2005
6-10 Peer-to-Peer Messaging
Message Type to Configure a MSG to a PLC-5 Processor
Table 6.7 Message Type to Configure a MSG to a PLC-5 Processor
If The Data Is integer (s) floating-point (REAL)
And You Want To read (receive) data write (send) data read (receive) data write (send) data
For This Item
Message Type
Source Element
Type or Select
PLC5 Typed Read data table address in the PLC-5 controller, such as N7:10
Number of Elements number of integers to transfer
Destination Tag first element of int_buffer
Message Type
Source Tag
PLC5 Typed Write first element of int_buffer
Number of Elements number of integers to transfer
Destination Element data table address in the PLC-5 controller, such as N7:10
Message Type
Source Element
PLC5 Typed Read data table address in the PLC-5 controller, such as F8:0
Number of Elements number of values to transfer
Destination Tag first element of the tag (controller-scoped) in this controller for the data
Message Type PLC5 Typed Write
Source Tag first element of the tag (controller-scoped) in this controller that contains the data
Number of Elements number of values to transfer
Destination Element data table address in the PLC-5 controller, such as F8:0
3.
On the Communication tab, specify the communication details:
A.
If you added the module for which the message instruction is sent to the I/O configuration tree, you can use the
Browse button to choose the path.
If you haven’t added the module, you can type the path in manually, as described below.
B.
Select a Communication Method.
Publication CNET-UM001C-EN-P - November 2005
4.
Click OK.
A manually entered path starts with the controller’s connection to the backplane and follows a path as shown in the example below:
Peer-to-Peer Messaging 6-11
EXAMPLE
Communication path from a Logix5000 controller to a PLC5 controller over a ControlNet network
ControlNet Network
Node Address = 7
5
0
5
5
C
N
2
Message
Node Address = 1
PLC5-C
Path = 1, 1, 2, 1
Where Indicates
1
1
2
1 connection to the backplane in local chassis slot number of 1756-CN2 module in local chassis connection to port 2 of the 1756-CN2 module (get on ControlNet) node address of remote PLC5
Publication CNET-UM001C-EN-P - November 2005
6-12 Peer-to-Peer Messaging
Communicate with PLC-5 or
SLC 500 Processors
If the message is to a PLC-5 or SLC 500 processor and it reads or writes integers (not REALs), use a buffer of INTs in the message.
• Logix5000 controllers execute more efficiently and use less memory when working with 32-bit integers (DINTs).
• PLC-5 and SLC 500 processors require 16-bit integers.
• Use an INT buffer in the message and move the data to or from DINTs as needed. Use the DINTs in the rest of the program; this can decrease the program scan.
IMPORTANT
Logix5000 controllers can only send messages to SLC 500 processors over ControlNet if the SLC processor uses a
KFC ControlNet communication card.
However, an SLC cannot send messages to Logix5000 controllers over ControlNet at all.
Initiate MSGs from PLC-5 Processors to Logix5000 Controllers
If the originating controller is a PLC-5 processor, in the MSG instruction, select PLC5.
The figure Configure the Message shows how to configure the message above.
Publication CNET-UM001C-EN-P - November 2005
Figure 6.1 Configure the Message
A.
Select either a PLC5 Typed Read or PLC5 Typed
Write for the Communication Command.
B.
Type the starting address of the data in the
PLC-5 controller.
C.
Type the number of elements to read or write.
D.
Select Port Number 2 for ControlNet.
E.
Type, in quotation marks, the tag name of the
Logix5000 tag.
You can only specify the Logix5000 tag in quotation marks if the PLC is PLC-5C Series
C/Revision M, Series D/Revision C, Series
E/Revision B, Series F/Revision A or greater.
F.
Select Yes for Multihop.
G.
Type the node number of the destination
1756-CN2 module.
H.
Type the backplane slot number of the
Logix5000 controller.
I.
Select No for RSLinx Destination.
Peer-to-Peer Messaging 6-13
Publication CNET-UM001C-EN-P - November 2005
6-14 Peer-to-Peer Messaging
Map Tags
A Logix5000 controller stores tag names on the controller so that other devices can read or write data without having to know physical memory locations. Many products only understand PLC/SLC data tables formatting, so the Logix5000 controller offers a PLC/SLC mapping function that lets you map Logix tag names to memory locations.
IMPORTANT
The mapping function is particularly useful if your
Logix5000 controller is communicating with a PLC-5C
Series C/Revision L, Series D/Revision B, Series
E/Revision A or earlier.
• You have to map only the file numbers that will be referenced by
READ/WRITE messages requested from other controllers; the other file numbers do not need to be mapped. For example, if another controller will send a READ message only to N7, you need to map that file.
• The mapping table is loaded into the controller and is used whenever a
“logical” address accesses data.
• You can only access controller-scoped tags (global data).
• For each file that is referenced in a PLC-5 command, make a map entry:
– Type the PLC file number of the logical address.
– Type or select the Logix5000 controller-scoped (global) tag that supplies or receives data for the file number. (You can map multiple files to the same tag.)
• For PLC-2 commands, specify the tag that supplies or receives the data.
Publication CNET-UM001C-EN-P - November 2005
A.
Click Logic.
B.
Click Map PLC/SLC
Messages.
Peer-to-Peer Messaging 6-15
Follow these steps to map tags:
1.
If the RSLogix 5000 project is online, go offline. You can only map tags when the project is offline.
2.
Access the PLC/SLC Mapping screen.
3.
Configure the PLC/SLC Mapping as needed.
A.
Type the File Number.
B.
Type the corresponding
Tag Name from the
RSLogix 5000 project.
When mapping tags:
• Do not use file numbers 0, 1, and 2. These files are reserved for Output,
Input, and Status files in a PLC-5 processor.
• Use PLC-5 mapping only for tag arrays of data type INT, DINT, or
REAL. Attempting to map elements of system structures may produce undesirable effects.
• Use the PLC file identifier of N or B when accessing elements in an
INT tag array.
Publication CNET-UM001C-EN-P - November 2005
6-16 Peer-to-Peer Messaging
Stagger the Messages
As you add messages to your project, you may have to coordinate the execution of the messages. To avoid errors and assure that each message is processed, follow these rules:
Rule 1
Rule 2
Enable no more than 16 messages at one time (including block transfers).
Enable no more than 10 of the following types of messages at one time:
•
CIP data table reads or writes that are not cached
•
CIP generic
•
PLC-2, PLC-3, PLC-5, or SLC (all types)
• block transfer reads or writes that are not cached
If the number of messages in your application exceeds rules 1 and 2, then stagger the execution of your messages. Here are some options:
• Send each message in sequence.
• Send the messages in groups that are within the limits of rules 1 and 2.
• Program a message to communicate with multiple devices.
Route PLC-5 Messages
Between ControlNet
Networks
You can use ControlLogix communication modules to route a message between PLC-5 controllers that are on different networks, such as a bridged message. The following example depicts a ControlLogix chassis with two
1756-CN2 modules that route a message from one ControlNet network to a different ControlNet network.
EXAMPLE
Message from a PLC-5C on a ControlNet network to a
PLC-5C on a different ControlNet network
C
N
2
C
N
2
ControlNet
Network A
Node 3 Node 5
ControlNet
Network B
P
L
C
5
C
Node 2
Message
P
L
C
5
C
Node 1
Publication CNET-UM001C-EN-P - November 2005
Peer-to-Peer Messaging 6-17
Route a ControlNet Message
To send a message from a PLC-5C controller to a PLC-5C controller on a different ControlNet network:
IMPORTANT
This section uses RSLogix 5 software, revision 3.x or greater and PLC-5C Series C/Revision M,
Series D/Revision C, Series E/Revision B,
Series F/Revision A or greater
1.
Open the RSLogix 5 project for the PLC-5 controller that sends the message.
2.
Display the set-up screen for the message.
Double-click on Set up Screen.
A.
Type the Communication Command.
Use either PLC-5 Typed Read or PLC-5
Typed Write.
B.
Type the starting address of the data in this PLC-5 controller, the controller sending the message.
C.
Type the number of elements to write or read in Size in Elements.
D.
Type the Port Number (always 2).
E.
Type the starting address of the data in the controller that receives the message.
F.
Choose Yes for Multihop.
3.
Configure the General tab of the message instruction.
Publication CNET-UM001C-EN-P - November 2005
6-18 Peer-to-Peer Messaging
A.
Click on the MultiHop tab.
B.
Type the ControlNet node number of the 1756-CN2 module that is on the same ControlNet network as the controller that sends the message.
C.
Type the slot number of the 1756-CN2 module that is on the other network.
4.
Configure the MultiHop tab.
A.
Select 1756-CN2 or 1756-CNB.
B.
Type the ControlNet node number of the controller that receives the message.
5.
Select the ControlLogix backplane row.
6.
Press Insert to add a hop.
7.
Configure the new hop.
Publication CNET-UM001C-EN-P - November 2005
1
Communicate with PanelView and
RSView Products
Chapter
7
Use This Chapter
Read this chapter for:
•
1756-CN2, 1756-CN2R modules
•
1756-CNB, 1756-CNBR modules
•
1769-L32C, 1769-L35CR controllers
•
1784-PCIC, 1784-PCICS,
1784-PKTCS cards
•
1788-CNx cards
This chapter describes how a controller uses a ControlNet communication module to communicate with PanelView and RSView software products over a
ControlNet network.
For This Information
Determine Connections to PanelView Terminals
Organize Controller Data for a PanelView Terminal
Determine Connections to RSView Applications
See Page
Set Up the Hardware
Local Chassis
Logix5000 controller with ControlNet
Communication Module
In this example, the controller in the local chassis shares data with an HMI application on the ControlNet network. This application could be running any of the following:
• PanelView terminal
• PanelView Plus terminal
• workstation running an RSView 32 software
• workstation running an RSView Enterprise application, such as RSView
Machine Edition software or RSView Supervisory Edition software
Data
HMI Terminal
Publication CNET-UM001C-EN-P - November 2005
7-2 Communicate with PanelView and RSView Products
The Logix5000 controller in the local chassis can be any of the following, with their ControlNet communication modules:
• 1756 ControlLogix controller with a 1756-CN2 or 1756-CN2R communication module in the chassis
• 1756 ControlLogix controller with a 1756-CNB or 1756-CNBR communication module in the chassis
• 1769-L32C or 1769-L35CR CompactLogix controller
• 1789 SoftLogix controller with a 1784-PCIC, 1784-PCICS or
1784-PKTCS communication card
• 1794 FlexLogix controller with a 1788-CNx ControlNet communication card
• PowerFlex 700S with DriveLogix controller and a 1788-CNx
ControlNet communication card
Make sure that:
• the ControlNet communication modules are connected to a scheduled
ControlNet network.
• all wiring and cabling is properly connected.
Determine Connections to
PanelView Terminals
How you establish communication between a PanelView or PanelView Plus terminal and a Logix5000 controller over ControlNet depends on how you want to use controller connections.
Type of Communication
Scheduled (always connected)
Unscheduled connected
Unscheduled unconnected
Terminal Type
PanelView Standard PanelView Plus
Supported
Not supported
Supported in version 3.2 and greater
Supported
Supported Not supported
A Logix controller supports up to 40 outgoing and 3 incoming unconnected buffers. This limited number of incoming unconnected buffers limits how many PanelView Standard terminals can request data from a controller.
Publication CNET-UM001C-EN-P - November 2005
Communicate with PanelView and RSView Products 7-3
We recommend the following when you use PanelView terminals with
Logix5000 controllers over ControlNet:
• PanelView Standard terminals
– A maximum of 4 PanelView Standard terminals can request data from a Logix5000 controller.
• PanelView Plus terminals
– Because these terminals use unscheduled connections, the number of
PanelView Plus terminals that can request data from a Logix5000 controller is dependent on the number of available unconnected buffers in the Logix5000 controller.
A typical PanelView Plus application uses 5 unconnected buffers in a
Logix5000 controller. With 32 unconnected buffers available at any time in a Logix5000 controller, a maximum of 6 PanelView Plus terminals can request data from a Logix5000 controller. Keep in mind, however, that if 6 PanelView Plus terminals are requesting data from a single
Logix5000 controller, there are few unconnected buffers remaining for anything else.
For scheduled connected communication, you must add the PanelView or
PanelView Plus terminal to the I/O configuration tree for the controller project.
Add a PanelView Terminal
Adding a PanelView terminal is similar to adding distributed I/O. You add the local ControlNet communication module and then you add the terminal to that module.
1.
If your application is online, go offline.
2.
Select a New Module for the I/O Configuration.
A.
Right-click on I/O
Configuration.
B.
Select New Module.
Publication CNET-UM001C-EN-P - November 2005
7-4 Communicate with PanelView and RSView Products
3.
Select the local ControlNet communication module type from the Select
Module Type pop-up. The example below uses a 1788-CNC card.
A.
Select the local ControlNet communication module.
B.
Click OK.
The table ControlNet communication Modules Available Locally lists
the ControlNet communication modules available locally (in the local chassis, computer or controller) with each Logix5000 controller.
Table 7.1 ControlNet communication Modules Available Locally
If You Are Using This Logix5000
Controller
CompactLogix
ControlLogix
FlexLogix
SoftLogix
You Can Use This ControlNet
Communication Module Locally
1769-L32C, 1769-L35CR have a built-in
ControlNet port
1756-CN2, 1756-CN2R
1756-CNB, 1756-CNBR
1788-CNC, 1788-CNCR, 1788-CNF, 1788-CNFR
1784-PCIC (unscheduled data only), 1784-PCICS,
1784-PKTCS (unscheduled data only)
4.
Configure the local ControlNet communication module.
Publication CNET-UM001C-EN-P - November 2005
For more information on how to configure ControlNet communication
modules, see the chapter Configure a ControlNet Module.
Communicate with PanelView and RSView Products 7-5
5.
Add a PanelView terminal to the project.
A.
Right-click on the local communication module.
B.
Select New Module.
A.
Select the PanelView terminal.
B.
Click OK.
6.
Select the PanelView terminal for your project.
Publication CNET-UM001C-EN-P - November 2005
7-6 Communicate with PanelView and RSView Products
7.
Configure the terminal.
Organize Controller Data for a PanelView Terminal
Organize data for a PanelView or PanelView Plus terminal based on how the data is used.
For Data That Is
Time-critical
(scheduled data) -
PanelView terminals only
Do This
Use the I/O tags of the terminal. The terminal supports a maximum of 32 input tags and 32 output tags.
The tags for this data were created when you added the
PanelView terminal to the I/O configuration of the controller. They are similar to the tags of I/O modules.
Create arrays to store the data: Not time-critical - either PanelView or
PanelView Plus terminals
1. For each screen, create a BOOL array with enough elements for the bit-level objects on the screen.
For example, the BOOL[32] array gives you 32 bits for push buttons, indicators.
2. For each screen, create a DINT array with enough elements for the word-level objects on the screen.
For example, the DINT[28] array, gives you 28 values for numeric entry controls, numeric displays.
Publication CNET-UM001C-EN-P - November 2005
Communicate with PanelView and RSView Products 7-7
To access the scheduled I/O tags of the PanelView terminal, use the following address format:
If The Terminal writes the data reads the data
Then Use This Address name_of_terminal :I.Data[ x ].
y name_of_terminal :O.Data[ x ].
y where: x y
This Address Variable Is name_of_terminal name of the instance in the I/O configuration of the controller element of the input (I) or output (O) structure.
bit number within the input or output element
Determine Connections to
RSView Applications
An RSView application is a self-contained, PC-based HMI that offers both local and distributed client/server systems. This HMI can view updated tag information in a Logix5000 controller via OPC connectivity available in
RSLinx software.
How you establish communication to an RSView software application depends on how you configure RSLinx software to collect tags from the controller. RSView 32 software uses RSLinx Classic software as a data server;
RSView Enterprise software uses RSLinx Enterprise software as a data server.
RSLinx Classic software and RSLinx Enterprise software each default to 4 read connections and 1 write connection per configured controller. You can modify your RSLinx Classic configuration as needed such as changing the number of read and write connections. However, the RSLinx Enterprise is not configurable. You can only use a configuration of 4 read connections and 1 write connection.
Publication CNET-UM001C-EN-P - November 2005
7-8 Communicate with PanelView and RSView Products
Notes:
Publication CNET-UM001C-EN-P - November 2005
Use This Chapter
Chapter
8
Troubleshoot Your ControlNet Communication
Modules
This chapter provides descriptions for status indicators used on the
ControlNet communication modules and adapters and how to use those indicators to troubleshoot your application.
For This Information
1756-CN2 and 1756-CN2R ControlNet Communication Modules
1756-CNB and 1756-CNBR ControlNet Communication Modules
1769-L32C and 1769-L35CR CompactLogix Controllers
1784-PCIC, 1784-PCICS and 1784-PKTCS ControlNet PCI Cards
1788-CNC, 1788-CNCR, 1788-CNF and 1788-CNFR ControlNet
1794-ACN15 and 1794-ACNR15 ControlNet FLEX I/O Adapters 8-21
1797-ACNR15 ControlNet FLEX Ex Redundant Media I/O Adapter 8-23
See Page
1 Publication CNET-UM001C-EN-P - November 2005
8-2 Troubleshoot Your ControlNet Communication Modules
1756-CN2 and 1756-CN2R
ControlNet Communication
Modules
This figure shows the status indicators used on the 1756-CN2 and 1756-CN2R modules.
Figure 8.1 1756-CN2 and 1756-CN2R Status Indicators
1756-CN2 1756-CN2R
Module Status Display
Module Status Indicator
Network Channel
Status Indicators
Channel A BNC Connector
Channel B BNC Connector
Module Status Indicator and Module Status Display
Diagnostic Information
This table describes the Module Status Indicator LED and Module Status
Display diagnostic information.
Table 8.1 1756-CN2 and 1756-CN2R Module Status Indicator and Display
If the OK
Indicator Is
Off
With This
Module Status
Display
None
It Means
Module not communicating due to a power supply fault or internal fault.
Take This Action
1. Check the power supply.
2. Check the cable connectors.
3. Make sure the module is firmly seated in the chassis.
4. If the indicator remains off, replace the module.
Publication CNET-UM001C-EN-P - November 2005
Troubleshoot Your ControlNet Communication Modules 8-3
If the OK
Indicator Is
Red
Flashing Red
Green
With This
Module Status
Display
Msg scrolls
(1)
It Means
Module’s network address is set to 00, an invalid ControlNet address. See footnote at end of table.
Take This Action
1. Optional – Turn chassis power supply off.
2. Remove the module from the chassis.
BPA# ERR
BPRX ERR
3. Set the network address switches to a unique address (01 to 99)
4. Install the module in the chassis.
Module detected a different slot address from that latched when you cycled power. Excessive noise on the backplane causes this error.
Too many CRC errors being generated by the multicast backplane receiver, so the backplane multicast receivers have been shut off.
Hardware fault within the module.
5. If off, turn chassis power supply on.
Replace the chassis or module.
Replace the module.
Replace the module.
BPIC
ERR
CNIC
ERR
DUPL NODE The module’s network address is the same as another module’s on the link.
RACK ERR
1. Turn chassis power supply off.
(Optional)
2. Remove the module from the chassis.
3. Set the network address switches to a unique address (01-99).
4. Install the module in the chassis.
5. If off, turn chassis power supply on.
Replace the chassis.
BOOT
Cannot read backplane EEPROM, or rack/slot address incorrect
Module has invalid firmware.
Flash update is in progress.
Update module firmware with ControlFlash
Update Utility.
None required.
ROM
UPDT
SNGL KPR!
OK
INIT
BW >MAX
Module detected that it has been connected to a Cnet 1.0 or 1.25 (single-keeper) network.
Normal operation
Module is initializing.
Module is receiving too much network traffic and connections are timing out. The network bandwidth has been exceeded.
Update the firmware of module at node address
01 and reschedule the network.
There is at least one connection to or through the module. No action required.
No action required.
None required (temporary condition).
If this happens frequently, add another bridge module and split the traffic between them.
Publication CNET-UM001C-EN-P - November 2005
8-4 Troubleshoot Your ControlNet Communication Modules
If the OK
Indicator Is
Flashing Green
With This
Module Status
Display
SW
ERR
OK
CNFG
ERR
NET
ERR
It Means Take This Action
Node address switch changed after power-up.
None required, but we recommend that you either return switches to their original settings or replace the module, since this could indicate a latent hardware problem.
Normal operation.
ControlNet configuration error.
No connections to or through the module. No action required
Recheck configuration.
Network cabling error or no other active nodes on network.
(1)
If switches are set to 00 the display scrolls “FAULT: ADDRESS SWITCHES = 00, ILLEGAL”
Re-check your network cabling and make sure another node on the network is active (online).
Network Channel Status Indicator Interpretation
IMPORTANT
When you connect the module to a ControlNet network using only the NAP, the LEDs are meaningless.
• Steady - indicator is on continuously in the defined state.
• Alternating - the two indicators alternate between the two defined states at the same time (applies to both indicators viewed together). The two indicators are always in opposite states, out of phase.
• Flashing - the indicator alternates between the two defined states
(applies to each indicator viewed independent of the other). If both indicators flash, they must flash together, in phase.
Publication CNET-UM001C-EN-P - November 2005
Troubleshoot Your ControlNet Communication Modules 8-5
This table describes the 1756-CN2 and 1756-CN2R network channel status indicators.
Table 8.2 1756-CN2 and 1756-CN2R Network Channel Status Indicators
If Both Channel
Status Indicators Are
Off
Steady red
It Means
No power
Faulted module
Take This Action
Apply power.
1. Cycle power to the module.
Alternating red/green
Alternating red/off
Self-test
Incorrect node configuration
2. If fault persists, contact your Rockwell Automation representative or distributor.
None
Check network address and other ControlNet configuration parameters.
Take This Action If Either Channel
Status Indicators Are
Off
Steady green
Flashing green/off
It Means
Channel disabled
Normal operation
Temporary network errors
Flashing red/off
Flashing red/green
Node is not configured to go online
Media fault
No other nodes present on network
Incorrect node address
Incorrect network configuration
Program network for redundant media, if necessary.
None
None unit will self-correct or
1. Check media for broken cables, loose connectors, missing terminators.
2. If condition persists, refer to the ControlNet Coax
Media Planning and Installation Manual, publication and CNET-IN002.
Make sure the network keeper is present and working and the selected address is less or equal to the UMAX
(1)
.
1. Check media for broken cables, loose connectors, missing terminators.
2. If condition persists, refer to the ControlNet Coax
Media Planning and Installation Manual, publication and CNET-IN002
Add other nodes to the network.
1. Change the node address so that it is less than or equal to UMAX.
2. Stop and restart the PCIC/PCICS driver in RSLinx software.
Reconfigure the ControlNet network so that UMAX is greater than or equal to the node address.
(1)
UMAX is the highest node address on a ControlNet network that can transmit data.
Publication CNET-UM001C-EN-P - November 2005
8-6 Troubleshoot Your ControlNet Communication Modules
1756-CNB and 1756-CNBR
ControlNet Communication
Modules
This figure shows the status indicators used on the 1756-CNB and
1756-CNBR modules.
Figure 8.2 1756-CNB and 1756-CNBR Status indicators
1756-CNB 1756-CNBR
Module Status Display
Module Status Indicator
Network Channel
Status Indicators
Channel A BNC Connector
Channel B BNC Connector
Module Status Indicator and Module Status Display
Diagnostic Information
This table describes the Module Status Indicator LED and Module Status
Display diagnostic information.
Table 8.3 1756-CNB and 1756-CNBR Module Status Indicator and Display
If The OK
Indicator Is
Off
With This
Module Status
Display
None
It Means
Module not communicating due to a power supply fault or internal fault.
Take This Action
1. Check the power supply.
2. Check the cable connectors.
3. Make sure the module is firmly seated in the chassis.
4. If the indicator remains off, replace the module.
Publication CNET-UM001C-EN-P - November 2005
Troubleshoot Your ControlNet Communication Modules 8-7
If The OK
Indicator Is
Steady red
With This
Module Status
Display
Msg scrolls
(1)
It Means
Module’s network address is set to 00, an invalid ControlNet address, or 99, an invalid
ControlNet address if you are using redundant control. See footnote at end of table.
Take This Action
1. Optional – Turn chassis power supply off.
2. Remove the module from the chassis.
BPA# ERR
BPRX ERR
3. Set the network address switches to a unique address (01-99, or 01-98 if redundant control)
4. Install the module in the chassis.
Module detected a different slot address from that latched in at power-up. Excessive noise on the backplane causes this error.
Too many CRC errors being generated by the multicast backplane receiver, so the backplane multicast receivers have been shut off.
Hardware fault within the module.
5. If off, turn chassis power supply on.
Replace the chassis or module.
Replace the module.
Replace the module.
BPIC
ERR
CNIC
ERR
DUPL NODE
RACK ERR
STOP
WAIT RM
For a redundant system this may be a temporary condition during chassis switchover. Otherwise, the module’s network address is the same as another module’s on the link.
For redundant systems only. wait 10 seconds; if the condition persists, do the following steps:
1. Turn chassis power supply off.
(Optional)
2. Remove the module from the chassis.
3. Set the network address switches to a unique address (01-99).
4. Install the module in the chassis.
Cannot read backplane EEPROM, or rack/slot address incorrect
CNB commanded to stop functioning by the redundancy module. This occurs when a non-redundancy compliant CNB is placed into a redundant secondary chassis.
CNB waiting for the redundancy module to complete power-up.
5. If off, turn chassis power supply on.
Replace the chassis.
Remove non-redundancy compliant CNB from redundant secondary chassis and replace with redundancy compliant CNB.
None required.
Publication CNET-UM001C-EN-P - November 2005
8-8 Troubleshoot Your ControlNet Communication Modules
If The OK
Indicator Is
Flashing red
Steady green
Flashing green
With This
Module Status
Display
BOOT
It Means
Module has invalid firmware.
Flash update is in progress.
ROM
UPDT
SNGL KPR!
OK
INIT
BW >MAX
CMPT
DSNP
PwDS
PwQg
PwQS
PwNS
Qfng
QS
SW
ERR
CNFG ERR
NET
ERR
OK
Take This Action
Update module firmware with ControlFlash
Update Utility.
None required.
Module detected that it has been connected to a Cnet 1.0 or 1.25 (single-keeper) network.
Normal operation
Update the firmware of module at node address
01 and reschedule the network.
None required. In this case, at least one connection has been made to or through the module.
Module is initializing.
Module is receiving too much network traffic and connections are timing out. The network bandwidth has been exceeded.
None required.
None required (temporary condition).
If this happens frequently, add another module and split the traffic between them.
Secondary CNB is compatible with its partner.
None required.
Secondary CNB is disqualified with no partner.
Check corresponding slot of primary chassis for type and revision of module.
CNB is primary with a disqualified secondary partner.
Check the type and revision of the module.
CNB is primary with a qualifying secondary partner.
CNB is primary with a qualified secondary partner.
CNB is primary with no secondary partner.
Redundant system status. No action required.
Check corresponding slot of secondary chassis for correct module.
Redundant system status. No action required.
Secondary CNB is qualifying.
Secondary CNB is qualified.
Node address switch changed after power-up.
None required, but we recommend that you either return switches to their original settings or replace the module, since this could indicate a latent hardware problem.
ControlNet configuration error.
Network cabling error or no other active nodes on network.
Recheck configuration.
Re-check your network cabling and make sure another node on the network is active (on line).
Normal operation None required. In this case, no connections have been made to or through the module.
Publication CNET-UM001C-EN-P - November 2005
Troubleshoot Your ControlNet Communication Modules 8-9
If The OK
Indicator Is
Steady green or off
With This
Module Status
Display
SO_1
SO_2
SO_3
SN_1
SN_2
SN_3
?Cpt
!Cpt
It Means Take This Action
Old primary switchover phase 1 in progress.
Old primary switchover phase 2 in progress.
Old primary switchover phase 3 in progress.
New primary switchover phase 1 in progress.
If the display shows any message for more than three seconds, then the CNB module failed during transition from one redundancy phase to another. Replace one or both redundancy modules.
New primary switchover phase 2 in progress.
New primary switchover phase 3 in progress.
CNB has not determined if it is compatible.
CNB has determined that it is not compatible.
Replace the CNB module with correct type and revision.
(1)
If switches are set to 00 the display scrolls “FAULT: ADDRESS SWITCHES = 00, ILLEGAL” If switches are set to 99 in a redundant chassis, the display scrolls: “FAULT:
ADDRESS SWITCHES = 99, ILLEGAL IN REDUNDANT SYSTEM”
Network Channel Status Indicator Interpretation
IMPORTANT
When you connect the module to a ControlNet network using only the NAP, the LEDs are meaningless.
• Steady - indicator is on continuously in the defined state.
• Alternating - the two indicators alternate between the two defined states at the same time (applies to both indicators viewed together). The two indicators are always in opposite states, out of phase.
• Flashing - the indicator alternates between the two defined states
(applies to each indicator viewed independent of the other). If both indicators flash, they must flash together, in phase.
Publication CNET-UM001C-EN-P - November 2005
8-10 Troubleshoot Your ControlNet Communication Modules
If Both Channel
Status Indicators Are
Off
Steady red
It Means
No power
Faulted module
This table describes the 1756-CNB and 1756-CNBR network channel status indicators.
Table 8.4 .1756-CNB and 1756-CNBR Network Channel Status Indicators
Take This Action
Apply power.
1. Cycle power to the module.
None
2. If fault persists, contact your Rockwell Automation representative or distributor.
Check the node address and other ControlNet configuration parameters.
Alternating red/green
Alternating red/off
Self-test
One of the following:
• incorrect node configuration
• duplicate ControlNet node address
It means: If either channel status indicators are:
Off
Steady green
Flashing green/off
Channel disabled
Normal operation
Temporary network errors
Take this action:
Flashing red/off
Flashing red/green
Node is not configured to go online
Media fault
No other nodes present on network
Incorrect node address
Incorrect network configuration
Program network for redundant media, if necessary.
None
1. Check media for broken cables, loose connectors, missing terminators.
2. If condition persists, refer to the ControlNet Coax
Media Planning and Installation Manual, publication and CNET-IN002
Make sure the network keeper is present and working and the selected address is less or equal to the UMAX
(1)
.
1. Check media for broken cables, loose connectors, missing terminators.
2. If condition persists, refer to the ControlNet Coax
Media Planning and Installation Manual, publication and CNET-IN002
Add other nodes to the network.
1. Change the node address so that it is less than or equal to UMAX.
2. Stop and restart the PCIC/PCICS driver in RSLinx software.
Reconfigure the ControlNet network so that UMAX is greater than or equal to the node address.
(1)
UMAX is the highest node address on a ControlNet network that can transmit data.
Publication CNET-UM001C-EN-P - November 2005
Troubleshoot Your ControlNet Communication Modules 8-11
1769-L32C and 1769-L35CR
CompactLogix Controllers
This figure shows the status indicators used on the 1769-L32C and
1769-L35CR CompactLogix controller.
Figure 8.3 1769-L32C and 1769-L35CR CompactLogix Controller Status Indicators
Network Channel A
Status Indicator
Network Channel B
Status Indicator
Module Status
Indicator
43870
For information on how to use the module status indicator and the network
channel status indicators, see the section Interpret Status Indicators.
In addition to ControlNet status indicators, the 1769-L32C and 1769-L35CR controllers have controller, serial and CompactFlash indicators. For more information, the CompactLogix System User Manual, publication
1769-UM011.
Publication CNET-UM001C-EN-P - November 2005
8-12 Troubleshoot Your ControlNet Communication Modules
Interpret Status Indicators
Use the following status indicators to determine how your CompactLogix
1769-L32C or 1769-L35CR controller is operating on the ControlNet network:
• Module Status
• Network Channel Status
These status indicators provide information about the controller and the network when the controller is connected to ControlNet via the BNC connectors. describes the possible conditions for module and network status indicators.
• Steady - indicator is on continuously in the defined state.
• Alternating - the two indicators alternate between the two defined states at the same time (applies to both indicators viewed together). The two indicators are always in opposite states, out of phase.
• Flashing - the indicator alternates between the two defined states
(applies to each indicator viewed independent of the other). If both indicators flash, they must flash together, in phase.
IMPORTANT
Keep in mind that the Module Status indictor reflects the module state such as self-test, firmware update, or normal operation but no connection established. The network status indicators, A and B, reflect network status.
Remember that the host is able to engage in local messaging with the card although it is detached from the network. Therefore, the Module Status LED is flashing green if the host has successfully started the card. Note, however, that until the host removes reset, all LEDs on the daughtercard will remain off.
When you view the indicators, always view the Module
Status indicator first to determine the state of the daughtercard. This information may help you to interpret the network status indicators. As a general practice, view all status indicators (Module Status and Network Status) together to gain a full understanding of the daughtercard’s status.
Publication CNET-UM001C-EN-P - November 2005
Troubleshoot Your ControlNet Communication Modules 8-13
Module Status (MS) indicator
This table describes the 1769-L32C and 1769-l35CR CompactLogix controller module status indicators.
Table 8.5 1769-L32C and 1769-L35CR CompactLogix Controller Module Status Indicators
If The Module Status
(MS) Indicator Is
Off
It Means Take This Action
Steady red
Flashing red
Steady green
Flashing green
Flashing red/green
The controller has no power.
The controller is faulted.
A major fault has occurred on the controller.
A firmware update is in progress.
A node address switch change occurred. The controller’s node address switches may have been changed since power-up.
The controller has invalid firmware.
The controller’s node address duplicates that of another device.
Connections are established.
No connections are established.
The controller is performing self-diagnostics.
Apply power.
Make sure that the controller is properly installed.
1. Cycle power.
2. If the problem persists, replace the controller.
No action required (firmware update in progress.)
Change the node address switches back to the original setting. The module will continue to operate properly.
Update the controller firmware with the ControlFlash
Update utility.
1. Remove power.
2. Change the node address to a unique setting.
None
3. Reapply power.
Establish connections, if necessary.
Wait briefly to see if problem corrects itself.
If problem persists, check the host. If the daughtercard cannot communicate with the host, the card may remain in self-test mode.
Publication CNET-UM001C-EN-P - November 2005
8-14 Troubleshoot Your ControlNet Communication Modules
Network Channel Status Indicators
Channel B is only labelled on the 1769-L35CR controller. The 1769-L32C controller only has channel A but uses the second indicator in some LED patterns as described in (Table 10)Need CR.
This table describes the 1769-L32C and 1769-l35CR CompactLogix network channel status indicators.
Table 8.6 1769-L32C and 1769-L35CR Network Channel Status Indicators
If Both Channel
Indicators Are
Off
Steady green
Flashing green/off
It Means
A channel is disabled.
Normal operation is occurring.
Temporary network errors have occurred.
Take This Action
Flashing red/off
Flashing red/green
The node is not configured to go online.
Media fault has occurred.
No other nodes present on the network.
The network is configured incorrectly.
It Means
Program network for redundant media, if necessary.
None
1. Check media for broken cables, loose connectors, missing terminators.
2. If condition persists, refer to the ControlNet
Coax Media Planning and Installation
Manual, publication and CNET-IN002.
Make sure the network keeper is present and working and the selected address is less or equal to the UMAX
(1)
.
1. Check media for broken cables, loose connectors, missing terminators.
2. If condition persists, refer to the ControlNet
Coax Media Planning and Installation
Manual, publication and CNET-IN002.
Add other nodes to the network.
Reconfigure the ControlNet network so that UMAX > the card’s node address.
Take This Action: If Either Channel
Indicator Is
Off
Steady red
You should check the module status indicator.
The controller is faulted.
Alternating red/green
Alternating red/off
The controller is performing a self-test.
The node is configured incorrectly.
Check the module status indicator.
1. Cycle power.
None
2. If the fault persists, contact your Rockwell
Automation representative or distributor.
Check the card’s network address and other
ControlNet configuration parameters.
(1)
UMAX is the highest node address on a ControlNet network that can transmit data.
Publication CNET-UM001C-EN-P - November 2005
Troubleshoot Your ControlNet Communication Modules 8-15
1784-PCIC, 1784-PCICS and
1784-PKTCS ControlNet
PCI Cards
This figure shows the status indicators used on the 1784-PCIC, 1784-PCICS and 1784-PKTCS cards.
Figure 8.4 1784-PCIC, 1784-PCICS and 1784-PKTCS Channel Status indicators
Network Channel
Status Indicators
43609
The status indicators on the card give you information about the card and the
ControlNet network when you are connected via the BNC connectors.
Network Channel Status Indicator Interpretation
IMPORTANT
When you connect the module to a ControlNet network using only the NAP, the LEDs are meaningless.
• Steady - indicator is on continuously in the defined state.
• Alternating - the two indicators alternate between the two defined states at the same time (applies to both indicators viewed together). The two indicators are always in opposite states, out of phase.
• Flashing - the indicator alternates between the two defined states
(applies to each indicator viewed independent of the other). If both indicators flash, they must flash together, in phase.
This table describes the 1784-PCIC, -PCICS and -PKTCS network channel status indicators.
Publication CNET-UM001C-EN-P - November 2005
8-16 Troubleshoot Your ControlNet Communication Modules
Table 8.7 1784-PCIC, 1784-PCICS and 1784-PKTCS Network Channel Status Indicators
If Both Channel Status
Indicators Are
Off
It Means
No power
1784-PCIC(S) driver not started
Take This Action
Apply power.
1. Start RSLinx software.
Steady red
Alternating red/green
Alternating red/off
Steady green
Off
Flashing green/off
Flashing red/off
Flashing red/green
1784-PKTCS driver is not installed or the card is not configured
Faulted card
2. Verify that the appropriate driver has been configured properly in RSLinx software.
Install the driver and/or configure the card.
Channel disabled
Faulted card
Self-test
One of the following:
• incorrect node configuration
• duplicate ControlNet node address
Normal operation
Channel disabled
1. Check operating system event log for details of fault (if the PC’s operating system supports an event log).
2. Cycle power to the PC.
3. Verify that you have firmly inserted the card into a PCI local bus expansion slot and that the expansion slot screw is tightened.
4. If fault persists, contact your Rockwell Automation representative or distributor.
Program network for redundant media, if required
1. Check operating system event log for details of fault (if the PC’s operating system supports an event log).
2. Cycle power to the PC.
3. Verify that you have firmly inserted the card into a PCI local bus expansion slot and that the expansion slot screw is tightened.
None
4. If fault persists, contact your Rockwell Automation representative or distributor.
Check card’s node address and other ControlNet configuration parameters.
Temporary network errors
Media fault
No other nodes present on network
Incorrect node address
Incorrect network configuration
None
Use RSNetWorx software to configure the ControlNet network for redundant media, if necessary.
1. Check media for broken cables, loose connectors, missing terminators.
2. If condition persists, refer to the ControlNet Coax
Media Planning and Installation Manual, publication and CNET-IN002
1. Check media for broken cables, loose connectors, missing terminators.
2. If condition persists, refer to the ControlNet Coax
Media Planning and Installation Manual, publication and CNET-IN002.
Add other nodes to the network.
1. Change card’s node address so that it is less than or equal to UMAX
(1)
.
2. Stop and restart the card’s driver in RSLinx software
(1784-PCIC and 1784-PCICS only).
Reconfigure the ControlNet network so that UMAX is greater than or equal to the card’s node address.
(1)
UMAX is the highest node address on a ControlNet network that can transmit data.
Publication CNET-UM001C-EN-P - November 2005
Troubleshoot Your ControlNet Communication Modules 8-17
1788-CNC, 1788-CNCR,
1788-CNF and 1788-CNFR
ControlNet Daughtercards
This figure shows the status indicators used on the 1788-CNC and
1788-CNCR cards.
Figure 8.5 1788-CNC, 1788-CNCR Status indicators
NAP
I/O Status Indicator Module Status Indicator Node Address
Switches
1788-CNC
Network Channel Status Indicators (A and B)
NAP
I/O Status Indicator Module Status Indicator
Node Address
Switches
1788-CNCR
31044
Network Channel Status Indicators (A and B)
Channel A connector
I/O Status
Indicator
NAP
Module Status
Indicator Node Address
Switches
1788-CNF
Network Channel Status Indicators (A and B)
Node Address
Switches
1788-CNFR
3115
Channel A Connector
Channel B Connector
Network
Channel
Status
Indicators
(A and B)
Publication CNET-UM001C-EN-P - November 2005
8-18 Troubleshoot Your ControlNet Communication Modules
Module and I/O Status Indicator Interpretation
Status indicators provide information about the card and the network when you are connected via the BNC connectors.
• Steady - indicator is on continuously in the defined state.
• Alternating - the two indicators alternate between the two defined states at the same time (applies to both indicators when viewed together ); the two indicators are always in opposite states, out of phase.
• Flashing - the indicator alternates between the two defined states
(applies to each indicator viewed independent of the other); if both indicators are flashing, they flash together, in phase.
IMPORTANT
Keep in mind that the Module Status indictor reflects the module state. For example: self-test, firmware update, and normal operation but no connection established. The network status LEDs, A and B, reflect network status.
Remember that the host is able to engage in local messaging with the card although it is detached from the network. Therefore, the Module Status LED is flashing green if the host has successfully started the card. Note, however, that until the host removes reset, all LEDs on the daughtercard will remain off.
When you view the indicators, always view the Module
Status indicator first to determine the state of the daughtercard. This information may help you to interpret the network status indicators. As a general practice, view all three status indicators (Module Status, I/O Status, and
Network Status) together to gain a full understanding of the daughtercard’s status.
Publication CNET-UM001C-EN-P - November 2005
Troubleshoot Your ControlNet Communication Modules 8-19
This table describes the 1788-CNC, 1788-CNCR and 1788-CNF module and
I/O status indicators.
Table 8.8 1788-CNC, 1788-CNCR and 1788-CNF Module and I/O Status Indicators
If The Module
Status (MS)
Indicator Is
Off
It Means
If The I/O Status
(IO) Indicator Is
Always off
It Means
Take This Action
Steady red
Flashing red
Steady green
Flashing green
No power
Host is faulted
Host is holding daughtercard in reset
Major fault
Minor fault
Firmware update in progress
Node address switch change – The daughtercard’s node address switches may have been changed since power-up.
I module firmware
Duplicate node address – The daughtercard’s node address duplicates that of another device.
Apply power.
Make sure that the daughtercard is firmly seated in the slot.
1. Cycle power.
2. If the indicator remains off, replace the daughtercard or the host.
1. Cycle power.
2. If the problem persists, replace the daughtercard.
No action required (firmware update in progress.)
No action required (firmware update in progress.)
Change the node address switches back to the original setting. The module will continue to operate properly.
Connections established
No connections established
Flashing red/green Module is performing self-diagnostics.
Update module firmware with ControlFlash Update utility.
1. Remove power.
2. Change the node address to a unique setting.
3. Reapply power.
None
Establish connections, if necessary.
Wait briefly to see if problem corrects itself.
If problem persists, check the host. If the daughtercard cannot communicate with the host, the card may remain in self-test mode.
Take This Action
This LED is on during the LED portion of the self-tests.
Publication CNET-UM001C-EN-P - November 2005
8-20 Troubleshoot Your ControlNet Communication Modules
Network Channel Status Indicator Interpretation
IMPORTANT
When you connect the module to a ControlNet network using only the NAP, the LEDs are meaningless.
• Steady - indicator is on continuously in the defined state.
• Alternating - the two indicators alternate between the two defined states at the same time (applies to both indicators viewed together). The two indicators are always in opposite states, out of phase.
• Flashing - the indicator alternates between the two defined states
(applies to each indicator viewed independent of the other). If both indicators flash, they must flash together, in phase.
This table describes the 1788-CNC, 1788-CNCR, 1788-CNF and 1788-CNFR network channel status indicators.
Table 8.9 1788-CNC, 1788-CNCR, 1788-CNF and 1788-CNFR Network Channel Status Indicators
If Both Channel Status
Indicators Are
Off
Steady green
Flashing green/off
Flashing red/off
Flashing red/green
It Means
Channel disabled
Normal operation
Temporary network errors
Node is not configured to go online
Media fault
No other nodes present on network
Incorrect network configuration
It Means
Take This Action
Program network for redundant media, if necessary.
None
1. Check media for broken cables, loose connectors, missing terminators.
2. If condition persists, refer to the ControlNet Fiber
Media Planning and Installation Manual, publication
CNET-IN001 or the ControlNet Coax Media Planning and Installation Manual, publication CNET-IN002.
Make sure the network keeper is present and working and the selected address is less or equal to the UMAX
(1)
.
1. Check media for broken cables, loose connectors, missing terminators.
2. If condition persists, refer to the ControlNet Fiber
Media Planning and Installation Manual, publication
CNET-IN001 or the ControlNet Coax Media Planning and Installation Manual, publication CNET-IN002.
Add other nodes to the network.
Reconfigure the ControlNet network so that UMAX is greater than or equal to the card’s node address.
Take This Action If Either Channel
Status Indicators Are
Off
Steady red
You should check the MS indicators
Faulted card
Check the MS indicators.
1. Cycle power.
Alternating red/green
Alternating red/off
The card is performing a self-test
Incorrect node configuration
None
2. If the fault persists, contact your Rockwell
Automation representative or distributor.
Check the card’s network address and other ControlNet configuration parameters.
(1)
UMAX is the highest node address on a ControlNet network that can transmit data.
Publication CNET-UM001C-EN-P - November 2005
Troubleshoot Your ControlNet Communication Modules 8-21
1794-ACN15 and
1794-ACNR15 ControlNet
FLEX I/O Adapters
This figure shows the status indicators used on the 1794-ACN15 and
1794-ACNR15 modules.
Figure 8.6 1794-ACN15 and 1794-ACNR15 Status Indicators
Module Status Indicators
43610
Network Channel Status Indicators
This graphic shows a 1794-ACNR15.
The modules use the following 2 status indicators:
• Comm - Communication status indicator for each channel; the
1794-ACN15 module has 1 Comm indicator, and the 1794-ANCR15 module has 2 Comm indicators
• Status - Module status indicator
This table describes the 1794-ACN15 and 1794-ACNR15 communication status indicators.
Table 8.10 1794-ACN15 and 1794-ACNR15 Communication Status Indicators
If Both Channel
Status Indicators Are
Off
Steady green
Flashing green/off
It Means
Channel disabled
Normal operation
Temporary network errors
Take This Action
Flashing red/off
Flashing red/green
Node is not configured to go online
Media fault
No other nodes present on network
Incorrect network configuration
Program network for redundant media, if necessary.
None
1. Check media for broken cables, loose connectors, missing terminators.
2. If condition persists, refer to the ControlNet Coax
Media Planning and Installation Manual, publication
CNET-IN002.
Make sure the network keeper is present and working and the selected address is less or equal to the UMAX
(1)
.
1. Check media for broken cables, loose connectors, missing terminators.
2. If condition persists, refer to the ControlNet Coax
Media Planning and Installation Manual, publication
CNET-IN002.
Add other nodes to the network.
Reconfigure the ControlNet network so that UMAX is greater than or equal to the module’s node address.
Publication CNET-UM001C-EN-P - November 2005
8-22 Troubleshoot Your ControlNet Communication Modules
If Either Channel
Status Indicators Are
Off
Steady red
It Means
No power
Faulted module
Alternating red/green
Alternating red/off
The module is performing a self-test
Incorrect node configuration
Take This Action
Apply power.
1. Cycle power.
2. If the fault persists, contact your Rockwell
Automation representative or distributor.
None
Check the module’s network address and other ControlNet configuration parameters.
(1)
UMAX is the highest node address on a ControlNet network that can transmit data.
This table describes the 1794-ACN15 and 1794-ACNR15 module status indicators.
Table 8.11 1794-ACN15 and 1794-ACNR15 Module Status Indicators
If The Module Status
Indicator Is:
Off
It Means
Module not communicating due to a power supply fault or internal fault.
Take This Action
Steady green
Flashing green
Steady red
Flashing red
Connections established
No connections established
Major fault
I/O module removed
Wrong I/O module inserted
FLASH program update in progress
1. Check the power supply.
2. Check the cable connectors.
3. Make sure the module is properly installed on the
DIN rail.
None
4. If the indicator remains off, replace the module.
Establish connections, if necessary.
1. Cycle power.
2. If the problem persists, replace the daughtercard.
Reinsert the module.
Replace the wrong module with the correct module.
Wait for the program update to finish.
Publication CNET-UM001C-EN-P - November 2005
Troubleshoot Your ControlNet Communication Modules 8-23
1797-ACNR15 ControlNet
FLEX Ex Redundant Media
I/O Adapter
This figure shows the status indicators used on the 1797-ACNR module.
Figure 8.7 1797-ACNR15 Status Indicators
Network Channel Status
Power
Module Status
41412
The modules use the following 2 status indicators:
• Comm - Communication status indicator for each channel
• Status - Module status indicator
This table describes the 1797-ACNR15 communication status indicators.
Table 8.12 1797-ACNR15 Communication Status Indicators
If Both Channel
Status Indicators Are
Off
Steady green
Flashing green/off
It Means
Channel disabled
Normal operation
Temporary network errors
Take This Action
Flashing red/off
Flashing red/green
Node is not configured to go online
Media fault
No other nodes present on network
Incorrect network configuration
Program network for redundant media, if necessary.
None
1. Check media for broken cables, loose connectors, missing terminators.
2. If condition persists, refer to the ControlNet Coax
Media Planning and Installation Manual, publication
CNET-IN002.
Make sure the network keeper is present and working and the selected address is less or equal to the UMAX
(1)
.
1. Check media for broken cables, loose connectors, missing terminators.
2. If condition persists, refer to the ControlNet Coax
Media Planning and Installation Manual, publication
CNET-IN002.
Add other nodes to the network.
Reconfigure the ControlNet network so that UMAX is greater than or equal to the module’s node address.
Publication CNET-UM001C-EN-P - November 2005
8-24 Troubleshoot Your ControlNet Communication Modules
If Either Channel
Status Indicators Are
Off
Steady red
It Means
No power
Faulted module
Alternating red/green
Alternating red/off
The module is performing a self-test
Incorrect node configuration
Take This Action
Apply power.
1. Cycle power.
2. If the fault persists, contact your Rockwell
Automation representative or distributor.
None
Check the module’s network address and other ControlNet configuration parameters.
(1)
UMAX is the highest node address on a ControlNet network that can transmit data.
This table describes the 1797-ACNR15 module status indicators.
Table 8.13 1797-ACNR15 Module Status Indicators
If The Module Status
Indicator Is
Off
It Means
Module not communicating due to a power supply fault or internal fault.
Take This Action
Steady green
Flashing green
Steady red
Flashing red
Connections established
No connections established
Major fault
I/O module removed
Wrong I/O module inserted
FLASH program update in progress
1. Check the power supply.
2. Check the cable connectors.
3. Make sure the module is properly installed on the
DIN rail.
4. If the indicator remains off, replace the module.
None
Establish connections, if necessary.
1. Cycle power.
2. If the problem persists, replace the daughtercard.
Reinsert the module.
Replace the wrong module with the correct module.
Wait for the program update to finish.
Publication CNET-UM001C-EN-P - November 2005
Appendix
A
Connection Use Over ControlNet
Use This Appendix
Read this chapter for:
•
1756-CN2, 1756-CN2R modules
•
1756-CNB, 1756-CNBR modules
•
1769-L32C, 1769-L35CR controllers
•
1784-PCC, 1784-PCIC, 1784-PCICS,
1784-PKTCS cards
•
1788-CNx cards
•
1794-ACN15, -ACNR15 adapters
•
1797-ANCR adapter
ControlNet communication modules use connections to manage communication. A connection is a point-to-point communication mechanism that transfers data between a transmitter and a receiver.
ControlNet communication modules use connections that transfer data from a
Logix application running on one end-node to another device, such as a Logix application or I/O, running on another end-node.
1
ControlNet Connections
Connection Type
Bridged
Rack-optimized
Direct
Produced/consumed tag
Connections are allocations of resources that provide faster more reliable communication between modules than unconnected messages. The
ControlNet communication modules and adapters support both direct and rack-optimized connections to remote I/O adapters.
Connected messaging supports the following example functions:
• Logix controller message transfer to Logix controller
• I/O or produced/consumed tag
• Program upload
• RSLinx DDE/OPC client
• PanelView polling of Logix controller
There are four types of ControlNet connections:
Table A.1 ControlNet Connection Types
Description
A connection that passes through the ControlNet module. The end point of the connection could be an
I/O module, another ControlNet node, another controller or a device on a different network (bridged).
Example: a connection from a controller through a 1756-CNB and 1756-CNBR to another controller.
A rack-optimized connection is a connection to a rack or assembly object in the ControlNet module.
Data from selected I/O modules is collected and produced on one connection (the rack-optimized connection) rather than on a separate direct connection for each module.
A connection from a controller to an specific I/O module (as opposed to a rack-optimized connection).
A connection that allows multiple controllers to share tags. One controller produces the tag and one or more controllers consume it.
Publication CNET-UM001C-EN-P - November 2005
A-2 Connection Use Over ControlNet
The Logix5000 controller supports 250 connections. But the limit of connections ultimately resides in the communication module you use for the connection. If a message path routes through a communication module or card, the connection related to the message also counts towards the connection limit of the communication module or card.
Product
1756-CN2 or 1756-CN2R
1756-CNB or 1756-CNBR
1769-L32C or 1769-L35CR
1784-PCC
1784-PCIC
1784-PCICS
1784-PKTCS
Connected Messaging Limits
Table A.2 Connected Messaging Limits
Connected Messaging Limits
Supports 100 connections.
•
5 controllers can have a rack-optimized connection to the module
•
5 controllers can have a rack-optimized, listen-only connection to the module
Supports 64 connections.
•
5 controllers can have a rack-optimized connection to the module
•
5 controllers can have a rack-optimized, listen-only connection to the module
Built-in ControlNet port only supports 32 communication connections. With these controllers, the number of end-node connections they effectively support is dependent on the application’s NUT and RPI of the connection:
If the NUT is
2 ms
3 ms
5 ms
10 ms
14 ms
5 ms
4 ms
And the RPI is
2 ms
3 ms
5 ms
10 ms
14 ms
20 ms
64 ms
The controller’s built-in ControlNet port effectively supports this many communication connections
(1)
0 - 1
1 - 2
3 - 4
6 - 9
10 - 12
12 - 16
31
(1)
For each NUT/RPI combination, the number of connections supported is listed in a range. The lower number is the number of connections we recommend you make to maintain reasonable ControlNet port CPU utilization rates. The higher number is the maximum number of connections possible for that NUT/RPI combination.
Each module supports 31 unscheduled connections.
Each module supports 128 unscheduled connections.
Each module supports 128 unscheduled and 127 scheduled connections.
Each module supports 128 unscheduled connections and 127 scanlist entries for scheduled connections.
Publication CNET-UM001C-EN-P - November 2005
Connection Use Over ControlNet A-3
Product
1788-CNx
1794-ACN15, 1794-ACNR15 and 1797-ANCR
Connected Messaging Limits
Each module supports 32 connections, of which 22 connections can be scheduled connections. With these controllers, the number of end-node connections they effectively support is dependent on the application’s NUT and RPI:
If the NUT and the RPI are each
5 ms
10 ms
20 ms
40 ms +
The controllers support a maximum of this many connections
3
6
13
22
In the table above, with a NUT and RPI of 40 ms and greater, the ControlNet card supports 22 communications connections. In this case, the remaining 10 connections can be used for unscheduled connections.
Each module supports a maximum 32 end-node connections for messages. With these cards, the number of end-node connections they support is dependent on the application’s NUT:
At this NUT
2.0 - 2.99ms
3.0 - 3.99ms
4.0 - 7.99ms
8.0 - 100.0
The cards support this many end-node connections
3
12
20
32
Unconnected Messaging Limits
The following limits of unconnected messages are the maximum number of outstanding unconnected messages. These are unconnected messages that have been sent to the module and are being processed and have not yet generated a response or time-out.
Table A.3 Unconnected Messaging Limits
Product
1756-CN2 or 1756-CN2R
1756-CNB or 1756-CNBR
1769-L32C or 1769-L35CR
1784-PCC
1784-PCIC or 1784-PCICS
1784-PKTCS
1788-CNx
1794-ACN15, 1794-ACNR15 or
1797-ACNR15
Unconnected Messaging Limits
Supports up to 20 unconnected messages
Supports up to 20 unconnected messages
Supports up to 6 unconnected messages
Supports up to 50 unconnected messages
Supports up to 50 unconnected messages
Supports up to 50 unconnected messages
Supports up to 20 unconnected messages.
Supports up to 16 unconnected messages.
Publication CNET-UM001C-EN-P - November 2005
A-4 Connection Use Over ControlNet
Notes:
Publication CNET-UM001C-EN-P - November 2005
1
Appendix
B
ControlNet Overview
This chapter defines some basic ControlNet concepts and how the
ControlNet network is used for control.
Understand the ControlNet
Network
ControlNet is a real-time control network that provides high-speed transport of both time-critical I/O and interlocking data and messaging data, including upload/download of programming and configuration data on a single physical media link. The ControlNet network’s highly efficient data transfer capability significantly enhances I/O performance and peer-to-peer communication in any system or application where it is used.
ControlNet is highly deterministic and repeatable, and remains unaffected as devices are connected or disconnected from the network. This ensures dependable, synchronized, and coordinated real-time performance.
The ControlNet network is most often used in these types of configurations:
• as the default network for the ControlLogix platform.
• as a substitute/replacement for the Remote I/O (RIO) network, because ControlNet handles large numbers of I/O points well.
• as a backbone to multiple distributed DeviceNet networks.
• as a peer interlocking network.
• instead of Data Highway Plus.
Publication CNET-UM001C-EN-P - November 2005
B-2 ControlNet Overview
Exchange Information on ControlNet
ControlNet communication modules use a message-based protocol that implements a relative path to send a message from the producing module in a system to the consuming modules. This protocol also allows you to communicate between devices on ControlNet and DeviceNet or EtherNet/IP without writing additional application code.
With unscheduled data the device where a message originates such as a
Logix5000 controller, contains the path information that steers the message along the proper route to reach its consumers.
A full explanation of unscheduled and scheduled data is available on page B-4.
Since the producing module holds this information, other modules 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 module.
Scheduled data in Logix-based systems use the producer/consumer networking model instead of a 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 a Logix 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
Logix backplane and over the ControlNet network. This data exchange conforms to the producer/consumer model.
Publication CNET-UM001C-EN-P - November 2005
ControlNet Overview B-3
A ControlNet link’s most important function is to transport time-critical control information, such as I/O data and control interlocking. Other information (non-time-critical messages such as program uploads and downloads) is also transported but does not interfere with time-critical messages because of ControlNet’s transmission of scheduled and unscheduled data.
On a ControlNet link, information is transferred between nodes by establishing connections. Each message sent by a producer contains a
Connection ID (CID). Nodes that have been configured to recognize the CID consume the message, therefore becoming consumers.
Media access to the network is controlled by a time-slice access algorithm,
Concurrent Time Domain Multiple Access (CTDMA), which regulates a node’s opportunity to transmit in each network update interval (NUI). You configure how often the NUI repeats by selecting a network update time
(NUT) in milliseconds.
Publication CNET-UM001C-EN-P - November 2005
B-4 ControlNet Overview
Network Update Time (NUT)
The network update time (NUT) is the smallest repetitive time interval in which data can be sent on the ControlNet network. It represents the fastest possible update rate for scheduled data transfers on that network. For example, a network that runs with a 5ms NUT cannot send scheduled data at a rate faster than 5ms. It can, however, send data at a slower rate. The minimum
NUT you can specify is 2ms. The NUT is divided into three parts:
Table B.1 NUT(Network Update Time) Structure
This part of the NUT
Scheduled
Unscheduled
Maintenance
Lets
Every scheduled node (on a rotating basis in sequential order) one guaranteed opportunity to transmit per NUT.
Information that is time-critical is sent during this part of the interval.
All nodes transmit on a rotating basis in sequential order. This rotation repeats until the time allotted for this portion is used up.
The amount of time available for the unscheduled portion is determined by the traffic load of the scheduled portion. ControlNet guarantees at least 1 node will have the opportunity to transmit unscheduled data every
NUT.
Information that can be delivered without time constraints is sent during this part of the interval.
The node with the lowest address transmits information to keep the other nodes synchronized. This time is automatically subtracted from your NUT. However, the time required for network maintenance is small
(microseconds) when compared to that used for the scheduled and unscheduled portions of the NUT.
Figure B.1 NUT Structure
Boundary Moves According to
Scheduled Traffic Load
Start
•
Scheduled Traffic
•
Each Device
Transmits Only
Once
• Unscheduled
Traffic
• Network
Maintenance
31446
Publication CNET-UM001C-EN-P - November 2005
Requested Packet Interval (RPI)
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 of I/O (using a rack-optimized connection), for a particular module (using a direct connection) or peer-to-peer data. When you add a module to the I/O configuration of a controller, you must configure the RPI. This value specifies
ControlNet Overview B-5 how often to produce the data for that module. For example, if you specify an
RPI of 50ms, every 50ms the I/O module sends its data to the controller and/or the controller sends its data to the I/O module.
Set the RPI only as fast as needed by the application. The RPI also determines the number of packets per second that the module will handle on a connection. Each module has a limit of how many packets it can handle per second. If you exceed this limit, the module cannot open any more connections.
Keep in mind that the faster your RPI, the more network bandwidth used. So only set the RPI as fast as necessary to avoid draining the network bandwidth unnecessarily. For example, if your application uses a thermocouple module that has data change every 100ms, do not set the RPI for that node at 5ms because the network bandwidth is used for data transmissions that are mostly old data.
IMPORTANT
You cannot set the RPI to a rate faster than the NUT. The network cannot send data at a rate that is faster than NUT.
When you run RSNetWorx for ControlNet software an Actual Packet Interval
(API) is calculated. The API is equal to or faster than the RPI.
Actual Packet Interval (API)
The API is the actual update rate for a particular piece of data on the network.
ControlNet will set this rate equal to or faster than the RPI, based upon the binary multiple of the NUT which is the next fastest rate at which a module can send data. If this can not be done, ControlNet will provide feedback that the configuration can not be supported.
Understand the Effect of the NUT on the API
The following example illustrates how the NUT affects the API. A module on the network can produce data only at binary multiples of the NUT to a maximum of the NUT multiplied by 128. These multiples are referred to as
“rates” on ControlNet. Therefore, in the example of a NUT of 5ms, the module can send data at the following rates:
Publication CNET-UM001C-EN-P - November 2005
B-6 ControlNet Overview
Publication CNET-UM001C-EN-P - November 2005
Table B.2 NUT Example Data Rates
With this NUT
5ms
And this multiple
16
32
64
128
4
8
1
2
The Module Can Send
Data at this Rate
5ms
10ms
20ms
40ms
80ms
160ms
320ms
640ms
In our example, if you specify an RPI of 25ms, then the network produces an
API of 20ms, which is the next fastest rate at which the module can send data.
The module places the data on the network at every fourth network update interval to produce the 20ms API. Similarly, if you specify an RPI of 150ms, the network produces an API of 80ms.
Schedule the Network
Connections over ControlNet can be:
• scheduled - data transfers occur at specific times or
• unscheduled - data transfers occur when the network can accommodate the transfer
To use scheduled connections, you must schedule the ControlNet network via
RSNetWorx for ControlNet software. For more information on how to schedule a ControlNet network with RSNetWorx for ControlNet software, see
the section Use RSNetWorx for ControlNet Software.
You must use RSNetWorx for ControlNet software to enable any connection in a remote chassis. In addition, RSNetWorx software transfers configuration information for the remote modules, verifies and saves NUT and other user-specified network parameters, and establishes a schedule that is compliant with the RPIs and other connection options specified for each module.
IMPORTANT
RSNetWorx software must be run whenever a scheduled connection is added to, removed from, or changed in your system.
ControlNet Overview B-7
Control of Scheduled I/O
Scheduled connections allow you to send and to receive data repeatedly at a predetermined rate. You can use the 1756-CNB or the 1756-CN2 module to control scheduled I/O when you use it in conjunction with a ControlLogix controller. When you place the module in the I/O configuration list of a
ControlLogix controller and configure a second ControlLogix chassis, with a remote 1756-CNB or 1756-CN2 module, on the same ControlNet network, you can perform remote control operations on the I/O, or to a second controller, in the second chassis.
In this situation, the ControlLogix controller and the 1756-CN2 module in the local chassis together act as a scanner, while the 1756-CN2 module in the remote chassis with the I/O plays the role of an adapter.
Publication CNET-UM001C-EN-P - November 2005
B-8 ControlNet Overview
Understand the Network Keeper
Every ControlNet network requires at least one module that stores programmed parameters for the network and configures the network with those parameters at start-up. This module is called a “keeper” because it keeps the network configuration. RSNetWorx for ControlNet software configures the keeper.
To avoid a single point of failure, ControlNet supports multiple redundant keepers. The following ControlNet communication modules are keeper cable devices:
• 1756-CN2(R) modules
• 1756-CNB(R) modules
• 1769-L32C and 1769-L35CR controller
• 1784-PCICS and 1784-PKTCS cards
• 1788-CNx cards
• PLC-5C module
On a multi-keeper network, any keeper capable module can keep the network at any legal node address (01 to 99). The multi-keeper capable node with the lowest node address becomes the active keeper provided it is valid. It has been configured by RSNetWorx software and that configuration is the same as that of the first keeper that became active after the network was formed or reconfigured by RSNetWorx software.
If the active keeper is taken off the network, a valid back-up keeper can take over for it and continue to act as keeper. As long as at least one valid multi-keeper device is present on the network, new scheduled connections can be established.
Publication CNET-UM001C-EN-P - November 2005
A.
Click Network.
B.
Click Keeper Status.
ControlNet Overview B-9
To see a list of valid keeper devices on your network, do the following steps:
1.
Go online in RSNetWorx for ControlNet software.
2.
Access the Keeper Status for the network.
The Keeper Status screen appears with a list of all nodes on the network and indications of whether the nodes are:
• Keeper Capable Nodes
• Active Keeper
• Valid Keepers
The screen below shows an example of the Keeper Status screen.
Publication CNET-UM001C-EN-P - November 2005
B-10 ControlNet Overview
Default Parameters
When a ControlNet network is powered-up for the first time, it comes up with a default set of ControlNet parameters capable of sending only unscheduled data. The default set of network parameters in all ControlNet devices, is:
• Network Update Time (NUT) = 100ms
• Scheduled Maximum Node Address (SMAX) = 0
The SMAX is the highest network address of a node that can use the scheduled service.
• Unscheduled Maximum Node Address (UMAX) = 99
The UMAX is the highest network address of a node that can communicate on the ControlNet network. The UMAX must be set equal to or higher than the SMAX.
• Assumed maximum cable lengths and maximum number of repeaters
With this default ControlNet network, you can have unscheduled communication between the various devices on the network by using such software packages as RSNetWorx for ControlNet, RSLogix5000 and RSLinx.
IMPORTANT
The ControlNet network should be configured using
RSNetWorx for ControlNet software to improve performance.
At a minimum, we recommend that the Unscheduled
Maximum Node Address (UMAX) be set equal to the highest node address on the network. Leaving this parameter at the default value of 99 will waste bandwidth and reduce system performance.
We also recommend setting the Scheduled Maximum Node
Address (SMAX) to a value 3 or 4 above the highest scheduled node address to allow you to expand the network in the future.
Publication CNET-UM001C-EN-P - November 2005
ControlNet Capacity and Topology
ControlNet Overview B-11
When planning a ControlNet network, you should consider the following:
• topology
• number of nodes
• distances
• connections
Topology
ControlNet supports a variety of topologies, including trunkline/dropline, star, tree, and ring redundancy. In its simplest form, ControlNet is a trunkline, to which you connect nodes with a tap and a 1-meter dropline, as shown in the figure Example ControlNet System Trunkline/Dropline Topology.
Repeaters are required to create other topologies, as shown in the figures
Example ControlNet System Star Topology (star) and Example ControlNet
System Ring Topology (ring).
TIP
• Coax repeaters are typically used in trunkline and star topologies. Refer to publication CNET-IN002,
ControlNet Coax Media Planning and Installation
Guide, for more specific information on coax topologies you can create.
• Using fiber media allows you to configure your network in trunkline and star topologies and is the only method of implementing ring redundancy. You can only use the
1786-RPFRL and 1786-RPFRXL repeaters in a ring.
Refer to publication CNET-IN001, ControlNet Fiber
Media Planning and Installation Guide, for more information on fiber media and topologies.
Publication CNET-UM001C-EN-P - November 2005
B-12 ControlNet Overview
Tap with
Dropline
Figure B.2 Example ControlNet System Trunkline/Dropline Topology
Trunkline
Node
Tap with
1-meter
Dropline
Node
Node
Node Node
Figure B.3 Example ControlNet System Star Topology
Coax
Repeater
Node Node
Node
Node Node
43620
43621
Publication CNET-UM001C-EN-P - November 2005
ControlNet Overview B-13
Figure B.4 Example ControlNet System Ring Topology tap with
1-meter
Dropline
ControlNet Repeater
Adapter and Fiber
Ring Module
Node Node
Fiber Cables
Coaxial Cable
Node Node
Node Node
Node Node
43622
Publication CNET-UM001C-EN-P - November 2005
B-14 ControlNet Overview
Number of Nodes
Each ControlNet network supports up to 99 nodes. Logix5000 controllers support multiple ControlNet networks, giving you the flexibility to add more nodes to your ControlNet network, or to boost performance.
Distances
In a ControlNet network, the maximum distance depends on the number of nodes on a segment; a segment is a section of trunk between 2 terminators.
Use repeaters to add more segments or gain more distance.
Use this figure to determine whether repeaters are required.
Maximum Allowable Segment Length = 1000m (3280ft) - 16.3m (53.4ft) X [Number of Taps - 2]
1000 (3280)
750 (2460)
500 (1640)
250 (820)
Add a Repeater
No Repeater
Required
2 16 32
Note: This graph assumes 1786-RG6 usage.
48
30014-M
Publication CNET-UM001C-EN-P - November 2005
1
Use This Appendix
Appendix
C
Determine Your ControlNet
Media Requirements
Use this appendix to determine your network media requirements.
For More Information
Determine How Many Taps You Need
Determine What Type of Cable You Need
Determine Trunk Cable Section Lengths
Determine if You Need Repeaters
Determine How Many Trunk Terminators You Need
Determine What Type of Connectors You Need
See Page
After reading this appendix, consult engineering drawings of your facility for specific information concerning the best location to install the ControlNet network.
IMPORTANT
The ControlNet cable system is a ground-isolated network.
Proper selection of cable, connectors, accessories, and installation techniques are necessary to make sure it is not accidentally grounded. If conditions occur where other means are needed to ensure no metal to ground connections, items like blue tape can be used. Any accessories should have a dielectric rating of greater than
500 V.
Publication CNET-UM001C-EN-P - November 2005
C-2 Determine Your ControlNet Media Requirements
Design a ControlNet Media
System
The design of a ControlNet media system is a process of measurement and judgement. The objective is to select the ControlNet media that will serve as the foundation for the network operations. When designing a network for an application, you must address the following deciding factors to assure a steady control foundation:
•
•
•
Application Requirements
Application requirements are environmental factors that, if not considered in the network design, could limit or prevent network operation. Application requirements are important in making the following decisions:
• What type of cable is needed?
• What type of cable connectors are needed?
The following application requirements should be factored into a network design as well:
• High ambient temperature
• EMF noise
• Flooding
• Hazardous environments
Publication CNET-UM001C-EN-P - November 2005
Media Needs
Media needs are the physical requirements of a network and are measured against the limitations of the media used. If the media needs are addressed without regarding the media limitations, then this oversight could result in a weak or unusable signal that could halt network operation. Media needs are important in making the following decisions:
• How much cable is needed?
• How is the programming device connected?
The following media needs should be factored into a network design:
• Network length from first device to last device
• Ability to configure the network from any device connected to the network
Determine Your ControlNet Media Requirements C-3
ControlNet Media Components
ControlNet network media components provide flexibility when designing a communication network for a particular application. A ControlNet network consists of a combination of the media components listed in the following table.
Table C.1 ControlNet Media Components
Component
Trunk cable
Cable connector
Repeater
Terminator
Tap
Node
Definition
A bus or central part of a network media system that serves as a communication channel between any two points on a network.
A piece of hardware for mating and demating network media and devices.
A piece of hardware that receives a signal on a cable, amplifies the signal, and then retransmits it along the next segment of the cable.
A piece of hardware attached to the end-points of a network to absorb signals so that they do not reflect back to create interference with other signals.
A piece of hardware that acts as a communication link between the network and a device, extracting a portion of the signal from the trunk cable.
A connection point with the programmed or engineered capability to recognize and process incoming data or transmit data to other nodes.
Publication CNET-UM001C-EN-P - November 2005
C-4 Determine Your ControlNet Media Requirements
Determine How Many Taps
You Need
The number of taps you need depends on the number of devices you want to connect to the network. You need a tap for each node and fiber hub on a segment.
If you plan to add nodes at a later date, you should consider ordering and installing the cable and connectors for these additional nodes when you install the initial network. This will minimize disruption to the network during operation.
IMPORTANT
A disconnected drop cable can cause noise on the network.
Because of this, we recommend having only one unconnected drop cable per segment for maintenance purposes. Be sure to keep the dust cap on any unconnected drop cable. If your cable system requires more than one unconnected drop cable, unused drop cables should be terminated with a tap terminator, such as the 1786-TCAP.
TIP
If you are planning future installation of additional nodes, do not install the tap. Instead, install a BNC bullet connector. For more information on BNC connectors, see
the section Determine What Type of Connectors You
Each tap kit contains:
Figure C.1 Contents of a Tap Kit
BNC Connector Kits
Tap
(1786-TPR, -TPS, -TPYR, -TPYS)
(1797-TPR, -TPS, -TPYR, -TPYS
Dust Cap
ControlNet Cable Labels
Universal Mounting bracket
Screws
For noise suppression, ferrite beads are molded on the drop cable.
Intrinsically Safe
Sheaths
41329
Publication CNET-UM001C-EN-P - November 2005
Straight T-taps
Determine Your ControlNet Media Requirements C-5
These tap kits are available:
Figure C.2 Available Tap Kits
Straight Y-tap Right-angle T-tap Right-angle Y-tap
41330
1786-TCT2BD1 1786-TPS
1797-TPS
1786-TPYS
1797-TPYS
1786-TPR
1797-TPR
1786-TPYR
1797-TPYR
Connect Programming
Devices
Programming devices in non-hazardous areas may be connected to the
ControlNet cable system through a 1784-PCIC, 1784-PCICS or 1784-PCC communication card. The 1784-PCIC, 1784-PCICS and 1784-PKTCS cards connect to the network using a ControlNet tap.
Figure C.3 1784-PCICS Communication Card on Coax Media
Programming
Terminal
Using a 1784-PCICS Communication Card on Coax Media
1784-PCICS
Node
41331
Publication CNET-UM001C-EN-P - November 2005
C-6 Determine Your ControlNet Media Requirements
Determine What Type of
Cable You Need
There are several types of RG-6 quad shield cable that may be appropriate for your installation, depending on the environmental factors associated with your application and installation site.
IMPORTANT
You should install all wiring for your ControlNet cable system in accordance with the regulations contained in the
National Electric Code (or applicable country codes), state codes, and applicable municipal codes. All metal connectors must be insulated from the ground.
Table C.2 Determine Cable Types
For
Light industrial applications
Heavy industrial applications
Use This Cable Type
Standard-PVC CM-CL2
Lay-on Armoured and
Interlocking Armour
Plenum-FEP CMP-CL2P High and low temperature applications, as well as corrosive areas (harsh chemicals), low smoke generation and low flame spread
Festooning or flexing applications
Moisture resistant applications; direct burial, with flooding compound, fungus resistant
High Flex
Flood Burial
Publication CNET-UM001C-EN-P - November 2005
Determine Trunk
Cable Section
Lengths
Trunk Cable Section
Determine Your ControlNet Media Requirements C-7
A segment is comprised of several sections of trunk cable separated by taps between 75 Ω terminators. The total cable length of a segment is equal to the sum of all of the trunk-cable sections.
Figure C.4 Taps and Trunk Cable Sections
Tap Tap Tap
Trunk Cable Section
30094-m
IMPORTANT
When determining the cable length of trunk-cable sections, make sure you measure the actual cable path as it is routed in your network. Consider vertical dimensions as well as horizontal dimensions. You should always calculate the three-dimensional routing path distance when determining cable lengths.
For intrinsically-safe applications, make sure to cover all exposed metal with either the intrinsically safe sheaths or other forms of insulation.
Select the shortest path for routing the cable to minimize the amount of cable you need. The specific details of planning such a cable route depends on the needs of your network.
Publication CNET-UM001C-EN-P - November 2005
C-8 Determine Your ControlNet Media Requirements
The total allowable length of a segment containing standard RG-6 quad shield cable depends upon the number of taps in your segment. There is no minimum trunk-cable section length requirement. The maximum allowable total length of a segment is 1,000 m (3280 ft) with two taps connected. Each additional tap decreases the maximum length of the segment by 16.3 m (53 ft).
The maximum number of taps allowed on a segment is 48 with a maximum length of 250 m (820 ft).
Maximum Allowable Segment Length = 1000 m (3280 ft) - 16.3 m (53.4 ft) X [number of taps - 2]
1000 (3280)
750 (2460)
500 (1640)
250 (820)
2 16 32
Number of Taps
48
30014-m
EXAMPLE
If your segment requires 10 taps, the maximum segment length is:
1000 m (3280 ft) - 16.3 m (53.5 ft) x [10 - 2]
1000 m (3280 ft) - 130.4 m (427.7 ft) = 869.6 m (2852.3 ft)
Publication CNET-UM001C-EN-P - November 2005
Determine Your ControlNet Media Requirements C-9
The amount of high-flex RG-6 cable you can use in a system is less than the amount of standard RG-6 cable due to higher attenuation, so you should keep high-flex cable use to a minimum. Use BNC bullet connectors to isolate areas that require high-flex RG-6 cable from areas that require standard RG-6 cable; this allows the high-flex RG-6 section to be replaced before flexture life is exceeded.
An allowable total length of RG-6 flex cable segment in your application can be determined using the equation below. Each additional tap decreases the maximum length of the segment. The maximum number of taps allowed on a segment is 48. Each additional tap decreases the maximum length of the segment by different lengths depending on the attenuation of your high-flex cable.
Maximum Allowable Segment Length of Cable =
(20.29 db - [Number of Taps in Segment * .32 db])
Cable Attenuation @ 10 MHz Per 304 m (1000 ft)
Cable attenuation is defined as the signal loss measured at 10 MHz per 1000 ft
(304 m) of cable.
EXAMPLE
If your segment requires 3 taps using 1786-RG6F/B
(1) cable, the maximum segment length is:
(20.29 db - [3 X.32 db]) / (13.5 db/1000)
(19.33 db) / (13.5 db/1000) = 1431.8 ft (436 m)
(1)
1786-RG6F/B cable has an attenuation of 13.5 db/1000 ft at 10 MHz. 1786-RG6 cable has an attenuation of
5.99 db/1000 ft at 10 MHz.
Publication CNET-UM001C-EN-P - November 2005
C-10 Determine Your ControlNet Media Requirements
Determine if You
Need Repeaters
You can install repeaters on a segment to increase the total trunk-cable length or number of taps. This creates another segment. You need to install repeaters if your system requires more than 48 taps per segment, or a longer trunk cable than the specifications allow.
1000 (3280)
750 (2460)
500 (1640)
250 (820)
Repeater Required
Repeater Not Required
2 32 16
Number of Taps
48
The maximum number of addressable nodes per network is 99. Since repeaters do not require an address, they do not count against the total of 99. Repeaters do require a tap and, therefore, can affect the length of the segment.
Segment 1
Repeater
Segment 2
43623
Publication CNET-UM001C-EN-P - November 2005
Determine How
Many Trunk Terminators
You Need
Determine Your ControlNet Media Requirements C-11
You must use 75 Ω trunk terminators (cat. nos. 1786-XT and 1797-XT) to terminate each segment for the ControlNet cable system. You need two XT terminators per segment because you need one for each end of the segment.
1786-XT
Intrinsically Safe Sheath
(1797-XT Only)
43625
After you have determined how many segments will be in your network, multiply this number by two to figure out how many terminators you will need for your network.
Be sure to cover the exposed metal using the intrinsically safe sheath provided with each terminator in order to comply with intrinsic safety standards. The
1786-XT and 1797-XT trunk terminators are the same mechanically and electrically. You can mix these terminators in non-intrinsically safe environments. However, you must only use the 1797-XT terminators in intrinsically safe environments to maintain your application’s Ex rating.
Configure Your Link With Repeaters
When you configure your link using repeaters, you can install them in one of three ways:
You Can Install
Repeaters In
Series
Parallel
A combination of series and parallel
Use a Maximum of See
20 repeaters
48 repeaters
20 repeaters in series; 48 repeaters in parallel
IMPORTANT
A repeater can be connected to a segment at any tap location.
Publication CNET-UM001C-EN-P - November 2005
C-12 Determine Your ControlNet Media Requirements
Install Repeaters In Series
When you install repeaters in series, you can install a maximum of 20 repeaters (or 21 segments) to form a link. In the link below:
• there are 3 repeaters in series (A, B and C)
• segments 1 and 4 each have 2 taps and each = 1000 m (3280 ft) maximum length
• segments 2 and 3 each have 3 taps and each = 983.7 m (3226.6 ft) maximum length
Figure C.5 Repeaters in Series
Device 1 Device 2 Device 3
Segment 1
Repeater A
Segment 2
Device 4
Segment 4
Repeater B Repeater C
Device 5
Segment 3
Device 6
42306
For any given architecture, the highest number of repeaters that a message might travel through to get from any single node to another determines the number of repeaters in series.
Publication CNET-UM001C-EN-P - November 2005
42307
Repeater A
Determine Your ControlNet Media Requirements C-13
Install Repeaters In Parallel
When you install repeaters in parallel, you can install a maximum of 48 repeaters (the maximum number of taps per 250 m segment) to form a link. shows an example of repeaters used in parallel.
Figure C.6
Repeater B Repeater C Repeater D
Segment 1 Segment 2 Segment 3
Device 1 Device 2 Device 3
Repeaters A and B are in parallel off of segment 1. This network also has a maximum of 2 repeaters in series because the highest number of repeaters a message can travel through between any two nodes is 2. For example: if a message travels from device 1 to device 2 or 3, it travels through 2 repeaters.
Publication CNET-UM001C-EN-P - November 2005
C-14 Determine Your ControlNet Media Requirements
Install Repeaters In A Combination Of Series And Parallel
You can install repeaters in a combination of series and parallel connections following the guidelines listed for each to form a link. For mixed topologies
(series and parallel) the maximum number of repeaters in series between any two nodes is twenty.
Figure C.7 Repeaters In A Combination Of Series And Parallel
Segment 3
Repeater D
Repeaters D, E and F are installed in parallel.
Device 1
Repeaters A, B and C are installed in series and connected to the repeaters in parallel via segment 6.
Device 4
Segment 1
Repeater A
Repeater E
Device 5
Device 2
Segment 2
Repeater B
Repeater F
Device 3
Segment 6
Repeater C
Device 6
Segment 4 Segment 5 Segment 7
42308
This network has a maximum of 5 repeaters in series because the highest number of repeaters a message can travel through between any two nodes is 5.
For example: if a message travels from device 1 or 2 to device 4, it travels through 5 repeaters.
Publication CNET-UM001C-EN-P - November 2005
Determine What Type of Connectors You
Need
Determine Your ControlNet Media Requirements C-15
Depending on the type of connection you need to make, you can select from multiple Rockwell Automation ControlNet connectors. The following are examples of connections you may need to make in your ControlNet application:
• IP20 BNC connections
• make ControlNet segments using copper coax media
• make water-tight (IP67), ruggedized TNC connections
• make pre-made, short-distance fiber media connections
• make connections to devices in your network in a hazardous environment
• isolate a ControlNet segment from a hazardous area to a non-hazardous area
To see a full list of the connectors available for these and any other connections in your ControlNet application, see the NetLinx Selection Guide, publication number NETS-SG001.
EXAMPLE
In this example, ControlNet cable:
• enters and exits the panel enclosure from the side using isolated-bulkhead connectors
• contains two adjacent taps connected by a barrel connector
• reserves one future tap location with a bullet connector
• makes a sharp bend with a right angle connector
Panel wall
Bullet Connector
Cable Enters and
Exits From the Side
Isolated Bulkhead
Connectors
Barrel
Connector
Right Angle
Connectors
Taps
20091-m
Publication CNET-UM001C-EN-P - November 2005
C-16 Determine Your ControlNet Media Requirements
ATTENTION
Do not let any metallic surfaces on the BNC connectors, plugs, or optional accessories touch grounded metallic surfaces. This contact could cause noise on the network.
All exposed metal must be covered with either intrinsically safe blue sheaths or another form of sufficient insulation.
IMPORTANT
If you are installing a bullet connector for future tap installations, count the bullet as one of the tap allotments on your segment (and decrease the maximum allowable cable length by 16.3 m [53.5 ft]).
This helps you avoid reconfiguring your network when you install the tap.
Publication CNET-UM001C-EN-P - November 2005
Use Redundant Media
Determine Your ControlNet Media Requirements C-17
You can run a second trunk cable between your ControlNet nodes for redundant media. With redundant media, nodes send signals on two separate segments. The receiving node compares the quality of the two signals and accepts the better signal to permit use of the best signal. This also provides a backup cable should one cable fail.
Trunk cables on a redundant cable link are defined by the segment number and the redundant trunk-cable letter.
Actual ControlNet products are labeled with these icons
(the shaded icon representing redundant media).
In this figure, the redundant cable trunk cable is trunk cable B.
Figure C.8 Redundant Media
Trunk Cable A =
Trunk Cable B =
Node Node
Node
To use redundant media, all nodes must support redundant media.
43629
Publication CNET-UM001C-EN-P - November 2005
C-18 Determine Your ControlNet Media Requirements
Observe these guidelines when planning a redundant media system in a hazardous area.
• Route the two trunk cables (trunk cable A and trunk cable B) differently to reduce the chance of both cables being damaged at the same time.
• Each node on a redundant-cable link must support redundant coax connections and be connected to both trunk cables at all times. Any nodes connected to only one side of a redundant-cable link will result in media errors on the unconnected trunk cable.
• Install the cable system so that the trunk cables at any physical device location can be easily identified and labeled with the appropriate icon or letter. Each redundant ControlNet device is labeled so you can connect it to the corresponding trunk cable.
• Both trunk cables (trunk cable A and trunk cable B) of a redundant-cable link must have identical configurations. Each segment must contain the same number of taps, nodes and repeaters. Connect nodes and repeaters in the same relative sequence on both trunk cables.
• Each side of a redundant-cable link may contain different lengths of cable. The total difference in length between the two trunk cables of a redundant-cable link must not exceed 800m (2640 ft).
Publication CNET-UM001C-EN-P - November 2005
Determine Your ControlNet Media Requirements C-19
Terminators
Figure C.9
Trunk Cable A =
Segment 1
Trunk Cable B =
Terminators
Repeater B
Repeater A
Node
Node
Terminators
To use redundant media, all nodes must support redundant media.
Trunk Cable B =
Trunk Cable A =
Segment 2
Node
Node
Terminators
43630
IMPORTANT
Make sure you do not mix A and B cable connections in a redundant operations. A node supporting redundant trunk-cable connections will function even if trunk cable A is connected to the B connector on the node and vice-versa. However, this makes cable fault indications (on the hardware or in software) difficult to interpret and makes locating a bad cable segment extremely difficult.
When in redundant cable mode, each node independently decides whether to use channel A or channel B. This decision is based on error counters internal to each node.
Redundant cabling is only valid if there is only one fault on the network. In other words, if you have a proper redundant cabling system and you remove node 3 on trunk
A and node 4 on trunk B the system will not operate correctly because a double failure has occurred.
Publication CNET-UM001C-EN-P - November 2005
C-20 Determine Your ControlNet Media Requirements
Application Considerations
The guidelines in this section coincide with the guidelines for “the installation of electrical equipment to minimize electrical noise inputs to controllers from external sources” in IEEE standard 518-1982. When planning your cable system there are certain installation considerations depending on your application. There are three categories of conductors:
Table C.3 Conductor Categories
Category
1
2
3
Includes
• ac power lines
• high-power digital ac I/O lines
• high-power digital dc I/O lines
• power connections (conductors) from motion drives to motors
• analog I/O lines and dc power lines for analog circuits
• low-power digital ac/dc I/O lines
• low-power digital I/O lines
•
ControlNet communication cables
• low-voltage dc power lines
• communication cables to connect between system components within the same enclosure
ATTENTION
These guidelines apply only to noise coupling. Intrinsic safety requirements for cable mounting are of the highest priority.
Publication CNET-UM001C-EN-P - November 2005
Determine Your ControlNet Media Requirements C-21
General Wiring Guidelines
Follow these guidelines with regard to noise coupling. Intrinsic safety requirements should prevent most or all of these situations from occurring.
They are provided as a general reference for wiring.
• If it must cross power feed lines, it should do so at right angles.
• Route at least 1.5 m (5 ft) from high-voltage enclosures, or sources of rf/microwave radiation.
• If the conductor is in a metal wireway or conduit, each section of that wireway or conduit must be bonded to each adjacent section so that it has electrical continuity along its entire length, and must be bonded to the enclosure at the entry point.
For more information on general wiring guidelines, see the Industrial
Automation Wiring and Grounding Guidelines, publication 1770-4.1.
Wire External To Enclosures
Cables that run outside protective enclosures are relatively long. To minimize cross-talk from nearby cables, it is good practice to maintain maximum separation between the ControlNet cable and other potential noise conductors. You should route your cable following these guidelines:
Table C.4
Is the cable in a contiguous metallic wireway or conduit?
Yes
Route Your
Cable at Least
0.08 m (3 in)
0.15 m (6 in)
From Noise Sources of This Strength
No
0.3 m (12 in)
0.15 m (6 in)
0.3 m (12 in)
0.6 m (24 in)
Category-1 conductors of less than 20 A ac power lines of 20 A or more, up to 100
KVA ac power lines greater than 100 KVA
Category-1 conductors of less than 20 A ac power lines of 20 A or more, up to 100
KVA ac power lines greater than 100 KVA
Publication CNET-UM001C-EN-P - November 2005
C-22 Determine Your ControlNet Media Requirements
Wire Inside Enclosures
Cable sections that run inside protective equipment enclosures are relatively short. As with wiring external to enclosures, you should maintain maximum separation between your ControlNet cable and Category-1 conductors.
When you are running cable inside an enclosure, route conductors external to all raceways in the same enclosure, or in a raceway separate from Category-1 conductors.
Table C.5 Cable Routing Distances
Route your cable at least this distance: From noise sources of this strength:
0.08 m (3 in)
0.15 m (6 in)
0.6 m (24 in)
Category 1 conductors of less than 20 A ac power lines of 20 A or more, up to 100
KVA ac power lines greater than 100 KVA
Surge Suppression
Transient electromagnetic interference (emi) can be generated whenever inductive loads such as relays, solenoids, motor starters, or motors are operated by “hard contacts” such as push-button or selector switches. These wiring guidelines assume you guard your system against the effects of transient emi by using surge-suppressors to suppress transient emi at its source.
Inductive loads switched by solid-state output devices alone do not require surge suppression. However, inductive loads of ac output modules that are in series or parallel with hard contacts require surge-suppression to protect the module output circuits as well as to suppress transient emi.
Ferrite Beads
Ferrite beads can provide additional suppression of transient emi. Fair-Rite
Products Corporation manufactures a ferrite bead
(part number 2643626502) which can be slipped over category-2 and category-3 (RG-6 type trunk cable) conductors. You can secure them with heat-shrink tubing or tie-wraps. A cable transient emi induced onto the cable can be suppressed by a ferrite bead located near the end of the cable. The ferrite bead will suppress the emi before it enters the equipment connected to the end of the cable.
Publication CNET-UM001C-EN-P - November 2005
Order Components
Determine Your ControlNet Media Requirements C-23
Now that you are ready to begin ordering components, use these guidelines to help you select components.
General Planning
The ControlNet cable system is isolated from earth and must be protected from inadvertent ground connections.
Segment Planning
• all connections to the trunk cable require a tap
• taps may be installed at any location on the trunk cable
• tap drop-cable length must not be changed (fixed at 1 meter)
• maximum number of taps = 48, with 250 m (820 ft) of standard RG6 trunk cable
• maximum trunk-cable length of standard RG6 trunk cable = 1000 m
(3280 ft), with 2 taps
• 75 Ω trunk terminators are required on both ends of a segment
• one tap with an unconnected drop cable may be installed for maintenance purposes
• use ControlNet tap terminators (1786-TCAP) for all other unconnected drop cables
• use BNC bullet connectors at future tap locations
• do not mix redundant and non-redundant nodes when redundant cabling is desired
• avoid high noise environments when routing cables
Link Planning
• maximum of 99 nodes (excluding repeaters)
• repeaters require a tap but are not counted as nodes — they are included in the number of devices allowed per segment (48)
• repeaters may be installed at any tap location along a segment
• there can only be one path between any two points on a link
• the configuration of both sides of a redundant segment must be the same
• the total cable difference between the two sides of a redundant link can not exceed 800 m (2640 ft)
Publication CNET-UM001C-EN-P - November 2005
C-24 Determine Your ControlNet Media Requirements
Notes:
Publication CNET-UM001C-EN-P - November 2005
1
Use This Appendix
Appendix
D
Control 1771 I/O Over ControlNet
Use this appendix to monitor and control I/O devices that are wired to 1771
I/O modules when a:
• 1756-CN2(R) or the 1756-CNB(R) module connects the local chassis to a ControlNet network.
• 1771-ACN(R)15 adapter connects the 1771 I/O modules to the same
ControlNet network.
ControlLogix Chassis with
1756-CN2(R) Module
1771-ACN(R)15 Adapter
42518
ControlNet Network
How to Use This Procedure
If you have not already done so in a previous procedure, do the following preliminary task:
•
Add the Local 1756-CN2(R) or 1756-CNB(R) Module
To complete this procedure, do the following tasks:
•
• Communicate with Block Transfer Modules, using either of these procedures:
–
Read or Write Data To or From a Block Transfer Module Via a
•
Publication CNET-UM001C-EN-P - November 2005
D-2 Control 1771 I/O Over ControlNet
Add the Local 1756-CN2(R) or 1756-CNB(R) Module
For more information on how to do this, see the section Add Local and
Remote ControlNet Modules in the chapter Control I/O.
Add the 1771-ACN(R)15
Module
To transfer discrete data between remote 1771 I/O and the ControlLogix controller in the local chassis (via the 1756-CN2(R), 1756-CNB(R) module), you need to add a remote 1771-ACN(R)15 ControlNet adapter to the I/O configuration.
1.
Add the 1771-ACN(R)15 module.
A.
Right-click on the local
1756-CNB(R) module.
B.
Click New Module.
C.
Select the 1771-ACN(R)15 module.
D.
Click OK.
Publication CNET-UM001C-EN-P - November 2005
A.
Name the module.
B.
Select a Comm Format. For more information on choosing a Comm Format, see section Communication Format.
C.
Select the module’s Revision level.
D.
Select an Electronic Keying level. For more information on choosing a keying level, see table Electronic Keying
Options.
2.
Configure the 1771-ACN(R)15 module.
Control 1771 I/O Over ControlNet D-3
E.
Select the module’s node number on ControlNet.
F.
Select the Input Size.
G.
Select the Output Size.
H.
Click Next.
I.
Set the RPI rate.
The RPI must be equal to or greater than the NUT. This parameter only applies if the module uses one of the Rack
Optimized communication formats.
J.
Inhibit the module, if necessary.
Initially, do you want the module to communicate with the controller?
Yes
Then
No
Leave the box unchecked
Check the box
(1)
(1)
When you test this portion of the system, clear the check box.
K.
Determine if you want a major fault on the controller if the connection to the PanelView fails in Run Mode.
Then If You Want The
Controller To fault (major fault) continue operating
Select the check box
Leave the check box unchecked
(1)
(1)
Monitor the connection using ladder logic.
L.
Click Finish.
Publication CNET-UM001C-EN-P - November 2005
D-4 Control 1771 I/O Over ControlNet
Read or Write Data To or
From a Block Transfer
Module Via a Message
Instruction
Use this procedure to transfer data to or from a module that requires block transfers. Use an INT buffer in the message and move the data into or out of the buffer as needed because DINTs can increase the program scan.
Read Data From a Block Transfer Module
1.
To read data from a block transfer module, enter the following rung of ladder logic:
Reads 16-bit integers (INTs) from the module and stores them in int_buffer_read . (Only include the msg_write.EN
tag and associated instruction if you also send a block transfer write message to the same module.) msg_read.EN
/ msg_write.EN
/
MSG
Type - Block Transfer Read
Message Control msg_read ...
EN
DN
ER
This table describes the tags used in this message
Table D.1 Tag Description
Tag Name: msg_read
Description: block transfer read message
Data Type:
MESSAGE
Scope: name_of_controller
(controller)
Publication CNET-UM001C-EN-P - November 2005
A.
Select a Block Transfer Read message type.
B.
Select the number of elements to read. In this case, the number of elements is the number of INTs to read.
C.
Select the tag to hold the data that is read.
Configure the Message
1.
In the MSG instruction, click .
2.
Configure the message as shown below.
Control 1771 I/O Over ControlNet D-5
D.
Use the Browse button to select a path for the message. To use this method, you must make sure the remote 1771 adapter was added to your project’s I/O configuration.
E.
Select ControlNet.
F.
Cache the connection if 16 or fewer devices require the block transfer instructions.
If more than 16 devices require the block transfer instructions, determine whether this message is for one of the 16 devices that require the most frequent updates and follow the guidelines below:
•
If the device for this message is among the
16 requiring most frequent updates, cache the connection.
•
If not, do not cache the connection, leave the box unchecked.
For more information on caching connections, see section Guidelines for
Caching Message Connections.
G.
Set the physical slot location in the
1771 chassis.
Publication CNET-UM001C-EN-P - November 2005
D-6 Control 1771 I/O Over ControlNet
Write Configuration or Output Data To a Block Transfer Module
1.
To read data from a block transfer module, enter the following rung of ladder logic:
The MSG instruction sends the data in int_buffer_write to the module.
This table describes the tags used in this message
Table D.2 Tag Descriptions
Tag Name msg_write
Description block transfer write message to the same module
Data Type
MESSAGE
Scope name_of_controller
(controller)
Publication CNET-UM001C-EN-P - November 2005
Configure the Message
1.
In the MSG instruction, click .
2.
Configure the message as shown below.
Control 1771 I/O Over ControlNet D-7
A.
Select a Block Transfer Write message type.
B.
Select the tag where the data is written from; the tag should be INT.
C.
Select the number of elements to write.
D.
Use the Browse button to select a path for the message. To use this method, you must make sure the remote 1771 adapter was added to your project’s I/O configuration.
E.
Select ControlNet.
F.
Cache the connection if 16 or fewer devices require the block transfer instructions.
If more than 16 devices require the block transfer instructions, determine whether this message is for one of the 16 devices that require the most frequent updates and follow the guidelines below:
•
If the device for this message is among the
16 requiring most frequent updates, cache the connection.
•
If not, do not cache the connection, leave the box unchecked.
For more information on caching connections, see section Guidelines for
Caching Message Connections.
G.
Set the physical slot location in the
1771 chassis.
Publication CNET-UM001C-EN-P - November 2005
D-8 Control 1771 I/O Over ControlNet
Address I/O
To monitor or control discrete 1771 I/O devices, assign the tag name of the device to an instruction in your logic:
• For step-by-step instructions on how to enter logic and tag names, refer to the Logix5000 Controllers Common Procedures, publication
1756-PM001.
• All the data for I/O modules is at the controller scope. As you assign addresses, click Controller Scoped Tags to see the I/O tags.
• Use the following table to select the address of an I/O device:
For a Digital Device Use This Address name:type.
Data [group].bit
Where name type group bit
Is the name of the remote I/O adapter, such as the user-defined remote_1771_adapter in the previous examples
•
Use the name for the rack that contains the module to which this device is wired.
•
Use the name from the I/O configuration folder of the controller.
type of device:
If input I
Then output O group number of the module to which this device is wired point (bit) number to which this device is wired
Publication CNET-UM001C-EN-P - November 2005
Control 1771 I/O Over ControlNet D-9
EXAMPLE
Address a digital device that is wired to a 1771 I/O module
−
I/O Configuration (Controller I/O tree)
−
[5] 1756-CNB(R)/D Local_CNB (local CNB in slot 5)
−
4 1771-ACN Remote_1771
( Remote_1771_adapter is the name assigned to the adapter)
Adapter Module for Node Number 4
Input Device
Group 2
Bit 0
Remote_1771:I.Data[2].0
42435
Publication CNET-UM001C-EN-P - November 2005
D-10 Control 1771 I/O Over ControlNet
Notes:
Publication CNET-UM001C-EN-P - November 2005
Index
Numerics
1734-ACNR module
additional documentation Preface-3
1756-CN2, 1756-CN2R modules
troubleshooting
1756-CNB, 1756-CNBR modules
additional documentation Preface-3
troubleshooting
1769-L32C, 1769-L35CR controllers
troubleshooting
1784-PCC card
additional documentation Preface-3
1784-PCIC, 1784-PCICS, 1784-PKTCS cards
additional documentation Preface-3
troubleshooting
1788-CN(x) cards
troubleshooting
1794-ACN15, 1794-ACNR15 modules
additional documentation Preface-3
troubleshooting
1797-ACNR15 module
troubleshooting
A
actual packet interval
B
bandwidth limitations
with produced and consumed tags
bridging messages across networks
C
determining cable section lengths
determining how many taps your network needs
determining how many trunk terminators
determining if your network needs repeaters
determining what type of cable your
determining what type of connectors
redundant media
caching message connections
capacity distance
number of nodes
of a ControlNet network
chassis monitor
1784-PCICS card
3-9, 4-3–4-9 listen-only rack optimized 3-9 rack optimized 3-9, 4-4–4-7
Communication Module
configuring a ControlNet module
configuring ControlNet communications driver
connecting a computer to the ControlNet
connecting a SoftLogix controller to
ControlNet
connections
connected messaging limits
determining for messages
determining for produced and consumed tags
direct connections 4-5–4-6, A-1
listen-only connections
rack-optimized scheduled connections
unconnected messaging limits
validating connections
connectors determining what type your network needs
consumed tags
Publication CNET-UM001C-EN-P - November 2005
2 Index
as they affect network update time
determining connections
organizing tag data
controlling I/O over ControlNet
accessing distributed I/O data
adding distributed I/O to an RSLogix 5000 project
validating connections 4-17–4-19
ControlNet overview
D
data types in produced or consumed tags direct connections
distributed I/O
adding to an RSLogix 5000 project
documentation related to ControlNet
downloading configuration in RSLogix 5000
E
electronic keying compatible match disable keying exact match
setting in RSLogix 5000 3-8, D-3
I
I/O accessing distributed I/O data in RSLogix
5000
adding distibuted I/O to an RSLogix 5000
listen-only connections
ownership in a Logix5000 system
selecting a communication format
inhibiting the connection to a ControlNet module
interlocking controllers
See produced tags or consumed tags
L
listen-only connections
listen-only rack optimized communication format
M
caching message connections
configuring a MSG to a Logix5000
configuring a MSG to a PLC-5 processor
configuring a MSG to an SLC 500
determining connections guidelines
mapping Logix tag names to memory locations from PLC/SLC data tables
message types
PLC2, PLC3, PLC5 or SLC (all types)
programming instruction in controller’s logic
receiving MSGs from PLC-5 or SLC 500 processors
routing PLC-5 messages between
ControlNet networks
staggering messages
N
network keeper
network update time
as it affects produced and consumed tags
scheduled portion
Publication CNET-UM001C-EN-P - November 2005
Index 3
O
overview
1734-ACNR module
1756-CNB, 1756-CNBR modules
1769-L32C, 1769-L35CR controllers
1784-PCC card
1784-PCIC, 1784-PCICS, 1784-PKTCS cards
1788-CNC, 1788-CNCR, 1788-CNF,
1794-ACN15, 1794-ACNR15 modules
of ControlNet communication modules
of the RSLogix 5000 configuration
ownership in a Logix5000 system
listen-only connection
P
peer-to-peer messaging
produced tags
as they affect network update time
bandwidth limitations
creating in RSLogix 5000
determining connections
organizing tag data
R
rack optimized communication format
related documentation. See documentation
repeaters
for a ControlNet network
installing in combination of series and
installing in parallel
requested packet interval
setting in RSLogix 5000
when organizing produced and consumed tag data
routing PLC-5 messages between
ControlNet networks
RSLinx configuring ControlNet communications
RSLogix 5000
accessing distributed I/O data 4-13–
adding distributed I/O to an RSLogix 5000 project
communication format 3-8–3-9, 4-3–
configuring a ControlNet module
configuring a message instruction
creating a produced tag 5-7–5-8
downloading configuration
programming message instructions in a
RSLogix5
RSNetWorx for ControlNet scheduling the network
S
scheduling a ControlNet network 3-12–
staggering messages in an RSLogix 5000
T
tags taps
See produced tags or consumed tags
determining how many your network
terminators determining how many your network
topology
example system star B-12 example system trunkline/dropline B-12
of a ControlNet network B-11–B-14
troubleshooting ControlNet
Publication CNET-UM001C-EN-P - November 2005
4 Index
1756-CNB, 1756-CNBR modules
1769-L32C, 1769-L35CR controllers
1784-PCIC, 1784-PCICS, 1784-PKTCS cards
1794-ACN15, 1794-ACNR15 modules
Publication CNET-UM001C-EN-P - November 2005
How Are We Doing?
Your comments on our technical publications will help us serve you better in the future.
Thank you for taking the time to provide us feedback.
You can complete this form and mail (or fax) it back to us or email us at
Pub. Title/Type ControlNet Modules in Logix5000 Control Systems
Cat. No.
Multiple ControlNet catalog numbers
Pub. No.
CNET-UM001C-EN-P Pub. Date November 2005 Part No.
957988-68
Please complete the sections below. Where applicable, rank the feature (1=needs improvement, 2=satisfactory, and 3=outstanding).
Overall Usefulness 1 2 3 How can we make this publication more useful for you?
Completeness
(all necessary information is provided)
1 2 3 Can we add more information to help you?
procedure/step illustration example explanation guideline definition feature other
Technical Accuracy
(all provided information is correct)
1 2 3 Can we be more accurate?
text illustration
Clarity
(all provided information is easy to understand)
1 2 3 How can we make things clearer?
Other Comments You can add additional comments on the back of this form.
Your Name
Your Title/Function
Location/Phone
Would you like us to contact you regarding your comments?
___No, there is no need to contact me
___Yes, please call me
___Yes, please email me at _______________________
___Yes, please contact me via _____________________
Return this form to: Rockwell Automation Technical Communications, 1 Allen-Bradley Dr., Mayfield Hts., OH 44124-9705
Fax: 440-646-3525 Email: [email protected]
Publication CIG-CO521C-EN-P- May 2003 PN 957988-68957782-91
Other Comments
PLEASE FASTEN HERE (DO NOT STAPLE)
PLEASE FOLD HERE
BUSINESS REPLY MAIL
FIRST-CLASS MAIL PERMIT NO. 18235 CLEVELAND OH
POSTAGE WILL BE PAID BY THE ADDRESSEE
1 ALLEN-BRADLEY DR
MAYFIELD HEIGHTS OH 44124-9705
NO POSTAGE
NECESSARY
IF MAILED
IN THE
UNITED STATES
ControlLogix, RSLogix 5000, RSView, RSNetWorx, RSNetWorx for
ControlNet, and RSLinx software are trademarks of Rockwell Automation,
Inc.
ControlNet is a trademark of ControlNet International, Ltd.
Trademarks not belonging to Rockwell Automation are property of their respective companies.
Rockwell Automation
Support
Rockwell Automation provides technical information on the web to assist you in using its 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 its 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
Outside 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.
Publication CNET-UM001C-EN-P - November 2005 2
Supersedes Publication CNET-UM001B-EN-P - May 2005
PN 957988-68
Copyright © 2005 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.
Advertisement
