Allen-Bradley L6x 1756-L61, L6x 1756-L62, L6x 1756-L63, L6x 1756-L63XT, L6x 1756-L64, L6x 1756-L65, L7x 1756-L72, L7x 1756-L73, L7x 1756-L74, L7x 1756-L75 ControlLogix Controller User Manual
Below you will find brief information for ControlLogix Controller L6x 1756-L61, ControlLogix Controller L6x 1756-L62, ControlLogix Controller L6x 1756-L63, ControlLogix Controller L6x 1756-L64, ControlLogix Controller L6x 1756-L65, ControlLogix Controller L7x 1756-L72, ControlLogix Controller L7x 1756-L73, ControlLogix Controller L7x 1756-L74, ControlLogix Controller L7x 1756-L75. The ControlLogix Controllers are industrial controllers capable of controlling a variety of industrial processes. The controllers offer a variety of programming languages as well as multiple communication options to connect to different networks. The controllers also include features for monitoring the status of the system and connections.
Advertisement
Advertisement
User Manual
ControlLogix System User Manual
Catalog Numbers 1756-L61, 1756-L62, 1756-L63, 1756-L63XT, 1756-L64, 1756-L65, 1756-L72, 1756-L73,
1756-L74, 1756-L75
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.
ATTENTION: 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 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 on or inside the equipment, for example, a drive or motor, to alert people that surfaces may reach dangerous temperatures.
IMPORTANT Identifies information that is critical for successful application and understanding of the product.
Allen-Bradley, CompactLogix, ControlLogix, DriveLogix, FLEX I/O, Kinetix, MessageView, MicroLogix, POINT I/O, PhaseManager, PowerFlex, RSFieldbus, RSLinx Classic, RSLinx Enterprise, RSLogix 5000,
RSNetWorx for ControlNet, RSNetWorx for DeviceNet, Rockwell Software, Rockwell Automation, Compact I/O, RediSTATION, Series 9000, FlexLogix, PowerFlex 4, PowerFlex 40, PowerFlex 40P, PowerFlex 70,
PowerFlex 700, PowerFlex 700H, PowerFlex 700S, PowerFlex 753, PowerFlex 755, PowerFlex 7000, PLC-2, PLC-3, PLC-5, PanelView, FactoryTalk, ArmorPOINT, Stratix 8000, RSLogix 500, SLC 5/03, RSLinx,
RSNetWorx for EtherNet/IP, SLC, SLC 500, FactoryTalk Live Data, ControlFLASH, DH+, Data Highway Plus, Integrated Architecture, Logix5000, ControlLogix-XT, GuardLogix, RSView, Encompass, 1336 FORCE,
1336 PLUS, 1336 IMPACT, SMC, SMC FLEX, SMC Dialog Plus, RSBizWare Batch, and TechConnect are trademarks of Rockwell Automation, Inc.
Trademarks not belonging to Rockwell Automation are property of their respective companies.
Summary of Changes
This manual contains new and updated information. Changes throughout this revision are marked by change bars, as shown to the right of this paragraph.
New and Updated
Information
This table contains the changes made to this revision.
Topic
Added information about new 1756-L72 and 1756-L74 controllers
Added series A information for version 19, or later, for the 1756-L72 and 1756-L74 controllers
Added 1756-L72 and 1756-L74 controller memory size information
Added 1756-L72 and 1756-L74 to list of controllers that support redundancy
Added information about redundant systems and the EtherNet/IP network
Added
Appendix C , History of Changes
, that describes changes made with each revision of this manual
Page
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 3
Summary of Changes
Notes:
4 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Preface
Install the 1756-L7x Controller
ControlLogix Controllers Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Traditional ControlLogix Controllers. . . . . . . . . . . . . . . . . . . . . . . . . . 11
Redundant ControlLogix Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Extreme Environment ControlLogix Controller . . . . . . . . . . . . . . . . 12
Chapter 1
Environment and Enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Prevent Electrostatic Discharge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Removal and Insertion Under Power (RIUP) . . . . . . . . . . . . . . . . . . . 18
European Hazardous Location Approval . . . . . . . . . . . . . . . . . . . . . 18
North American Hazardous Location Approval. . . . . . . . . . . . . . . . . 19
Parts Included with the 1756-L7x Controller . . . . . . . . . . . . . . . . . . . 20
Parts Available for Use with the 1756-L7x Controller . . . . . . . . . . . 21
Chapter 2
Install the 1756-L6x Controller
Environment and Enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Programmable Electronic Systems (PES) . . . . . . . . . . . . . . . . . . . . . . . 31
Preventing Electrostatic Discharge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Removing Module While Under Power (RIUP) . . . . . . . . . . . . . . . . 32
European Hazardous Location Approval . . . . . . . . . . . . . . . . . . . . . 32
North American Hazardous Location Approval. . . . . . . . . . . . . . . . . 33
Parts Included with the 1756-L6x Controller . . . . . . . . . . . . . . . . . . . 34
Parts Not Included with the 1756-L6x Controller. . . . . . . . . . . . . . . 35
CompactFlash Card Installation and Removal . . . . . . . . . . . . . . . . . . . . . . 36
Battery Connection and Replacement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 5
6
Table of Contents
Start Using the Controller
Remove the Controller from the Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Chapter 3
1756-L7x Connection Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
1756-L6x Connection Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Connect to the 1756-L7x Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Connect to the 1756-L6x Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Determine Required Controller Firmware . . . . . . . . . . . . . . . . . . . . . . 53
Obtain Controller Firmware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Use ControlFLASH Utility to Upgrade Firmware. . . . . . . . . . . . . . . 54
Use AutoFlash to Upgrade Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Use the Who Active Dialog Box to Download. . . . . . . . . . . . . . . . . . . 61
Use the Controller Status Menu to Download . . . . . . . . . . . . . . . . . . 62
Use the Who Active Dialog Box to Upload . . . . . . . . . . . . . . . . . . . . . 62
Use the Controller Status Menu to Upload . . . . . . . . . . . . . . . . . . . . . 63
Choose the Controller Operation Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Use the Keyswitch to Change the Operation Mode . . . . . . . . . . . . . . 64
Use RSLogix 5000 Software to Change the Operation Mode . . . . . 64
Load or Store to the Memory Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Store to the Memory Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Load from the Memory Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Other Memory Card Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Use ControlLogix Energy Storage Modules (ESMs) . . . . . . . . . . . . . . . . . 72
Save the Program to On-board NVS Memory . . . . . . . . . . . . . . . . . . . 73
Clear the Program from On-board NVS Memory . . . . . . . . . . . . . . . 73
Estimate the ESM Support of the WallClockTime . . . . . . . . . . . . . . . . . . 74
Maintain the Battery (1756-L6x controllers only) . . . . . . . . . . . . . . . . . . . 74
1756-BA1 or 1756-BATA Battery Life . . . . . . . . . . . . . . . . . . . . . . . . . 75
1756-BATM Battery Module and Battery Life . . . . . . . . . . . . . . . . . . 76
Estimate 1756-BA2 Battery Life . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Estimate 1756-BA2 Battery Life After Warnings . . . . . . . . . . . . . . . . 78
Battery Storage and Disposal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Table of Contents
ControlLogix System and
Controllers
Communication Networks
Chapter 4
System, Communication, and Programming Features. . . . . . . . . . . . 85
Controller Central-processing Unit (CPU) Resources . . . . . . . . . . . 87
Chapter 5
EtherNet/IP Network Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
ControlLogix EtherNet/IP Module Features . . . . . . . . . . . . . . . . . . . 90
ControlLogix EtherNet/IP Communication Modules. . . . . . . . . . . 91
Software for EtherNet/IP Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Connections Over an EtherNet/IP Network . . . . . . . . . . . . . . . . . . . 92
ControlNet Network Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
ControlLogix ControlNet Module Features . . . . . . . . . . . . . . . . . . . . 94
ControlLogix ControlNet Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Software for ControlNet Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Connections Over a ControlNet Network . . . . . . . . . . . . . . . . . . . . . 95
DeviceNet Network Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
ControlLogix DeviceNet Module Features . . . . . . . . . . . . . . . . . . . . . 96
ControlLogix DeviceNet Bridge Module and Linking Devices . . . 97
Software for DeviceNet Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Connections Over DeviceNet Networks . . . . . . . . . . . . . . . . . . . . . . . 97
ControlLogix DeviceNet Module Memory . . . . . . . . . . . . . . . . . . . . . 97
Data Highway Plus (DH+) Network Communication . . . . . . . . . . . . . . 98
Communicate Over a DH+ Network . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Universal Remote I/O (RIO) Communication . . . . . . . . . . . . . . . . . . . . . 99
Communicate Over a Universal Remote I/O Network . . . . . . . . . 100
Foundation Fieldbus Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Serial Communication
(1756-L6x controllers only)
Chapter 6
ControlLogix Chassis Serial Communication Options . . . . . . . . . 106
Communication with Serial Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
DF1 Radio Modem Advantages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
DF1 Radio Modem Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 7
Table of Contents
8
DF1 Radio Modem Protocol Parameters. . . . . . . . . . . . . . . . . . . . . . . 110
Configure the 1756-L6x Controller for Serial Communication. . . . . . 113
Broadcast Messages Over a Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Configure Controller Serial Port Properties . . . . . . . . . . . . . . . . . . . . 116
Program the Message Instruction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Manage Controller
Communication (connections)
Chapter 7
Produce and Consume (interlock) Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Connection Requirements of a Produced or Consumed Tag. . . . . 120
Determine Whether to Cache Message Connections . . . . . . . . . . . 122
I/O Modules
Chapter 8
Selecting ControlLogix I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Add Local I/O to the I/O Configuration . . . . . . . . . . . . . . . . . . . . . . 128
Add Remote I/O to the I/O Configuration . . . . . . . . . . . . . . . . . . . . 131
Add Distributed I/O to the I/O Configuration . . . . . . . . . . . . . . . . 135
Reconfigure an I/O Module via the Module Properties. . . . . . . . . . 137
Reconfigure an I/O Module via a Message Instruction . . . . . . . . . . 138
Add to the I/O Configuration While Online . . . . . . . . . . . . . . . . . . . . . . 138
Modules and Devices that Can be Added While Online. . . . . . . . . 139
Online Additions - ControlNet Considerations . . . . . . . . . . . . . . . . 141
Online Additions - EtherNet/IP Considerations . . . . . . . . . . . . . . . 144
Determine When Data is Updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Chapter 9
Develop Motion Applications
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Table of Contents
Develop Applications
Chapter 10
Elements of a Control Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Scheduled and Unscheduled Programs . . . . . . . . . . . . . . . . . . . . . . . . 159
Determine if I/O Communication has Timed Out . . . . . . . . . . . . . 165
Determine if I/O Communication to a Specific I/O Module has
Interrupt the Execution of Logic and Execute the Fault Handler. 166
Configure the System Overhead Time Slice. . . . . . . . . . . . . . . . . . . . 168
Sample Controller Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Chapter 11
Using the PhaseManager Tool
Minimum System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
How Equipment Changes States. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
PhaseManager Tool versus Other State Models . . . . . . . . . . . . . . . . . . . . 175
Redundant Systems
Chapter 12
ControlLogix Redundancy Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Enhanced versus Standard Redundancy . . . . . . . . . . . . . . . . . . . . . . . 181
ControlNet Considerations in Redundant Systems . . . . . . . . . . . . . . . . 182
EtherNet/IP Considerations in Redundant Systems. . . . . . . . . . . . . . . . 183
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 9
Table of Contents
SIL 2 Certification
Status Indicators
Using Electronic Keying
Chapter 13
Programming and Debugging Tool (PADT) . . . . . . . . . . . . . . . . . . . 187
High-availability Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Fault-tolerant Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Appendix A
1756-L7x Controller Status Display and Indicators. . . . . . . . . . . . . . . . . 193
1756-L7x Controller Status Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Major Recoverable Fault Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
1756-L7x Controller Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Appendix B
Appendix C
History of Changes
Index
10 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
ControlLogix Controllers
Overview
Preface
There are three types of ControlLogix controllers available. These types include the following:
• Traditional ControlLogix controllers
• Extreme environment ControlLogix controller
• Safety GuardLogix controllers
This manual explains how to use traditional and extreme environment
ControlLogix controllers.
For more information about using safety GuardLogix controllers, see the
GuardLogix Controller Systems Safety Reference Manual, publication
1756-RM093 .
Traditional ControlLogix Controllers
Two lines of traditional ControlLogix controllers are now available. These controllers are identified as 1756-L6 x controllers and 1756-L7x controllers according to abbreviations of their full catalog numbers.
Table 1 - ControlLogix Catalog Numbers
Abbreviated Cat. No.
1756-L6x
1756-L7x
Cat. No.
1756-L61, 1756-L62,
1756-L63, 1756-L64,
1756-L65
1756-L72, 1756-L73,
1756-L74, 1756-L75
The traditional ControlLogix controllers share many similar features, but also
have some differences. Table 2 provides a brief overview the differences between
the controllers. For further details about these features and differences, see the appropriate chapters of this manual.
Table 2 - Differences Between 1756-L7x and 1756-L6x Controllers
Feature
Clock support and backup used for memory retention at powerdown
Communication ports (built-in)
Connections, controller
Logix CPU (processor)
Memory, nonvolatile
Status display and status indicators
Unconnected buffer defaults
1756-L7x 1756-L6x
Energy Storage Module (ESM) Battery
USB
500
Dual-core
Secure Digital (SD) card
Scrolling status display and four status indicators
20 (40, max)
Serial
250
Single-core
CompactFlash card
Six status indicators
10 (40, max)
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 11
Preface
Before You Begin
Redundant ControlLogix Controllers
Certain ControlLogix controllers are also supported for use in redundant systems. For more information about controllers and redundant systems see
Chapter 12, Redundant Systems (on page 177 ).
Extreme Environment ControlLogix Controller
The extreme environment ControlLogix controller, catalog number
1756-L63XT, provides the same functionality as the 1756-L63 controller but is designed to withstand temperatures -25...70 °C (-13...158 °F).
Before you begin using your ControlLogix controller, verify that you have the software required to configure and program the controller.
Required Software
Use this table to identify the minimum software versions required to use your
ControlLogix controller.
Table 3 - Required Software for Controller Use
Cat. No.
1756-L61, Series A
1756-L61, Series B
1756-L62, Series A
1756-L62, Series B
1756-L63, Series A
1756-L63, Series B
1756-L63XT
1756-L64
1756-L65
1756-L72
1756-L73
1756-L74
1756-L75
RSLogix 5000 Software
Version 12
Version 12
Version 10
Version 12
Version 12
Version 16
Version 17
Version 19
Version 18
Version 19
Version 18
RSLinx Classic Software
Any version
Version 2.55, or later
Any version
Version 2.57,or later
Version 2.56, or later
Version 2.57, or later
Version 2.56, or later
12 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Preface
Additional Resources
Consult these resources for additional information related to ControlLogix controllers.
Table 4 - Additional Resources Related to ControlLogix Controllers and Systems
For more information about
Add-On Instructions
See This Resource
Add-On Instructions Programming Manual, publication
1756-PM010
Description
Explains Add-On Instructions and how to use them.
Batteries for use with controllers Guidelines for Handling Lithium Batteries, publication
AG-5.4
CIP Sync (time synchronization)
Programmable Controllers Battery Reference, http://www.ab.com/programmablecontrol/batteries.ht
ml
Integrated Architecture and CIP Sync Configuration
Application Technique, publication IA-AT003
Design and selection
Hardware installation
GuardLogix controllers
Logix5000 Controllers Design Considerations
Reference Manual, publication
ControlLogix Selection Guide, publication 1756-SG001 Provides a high-level selection process for ControlLogix system components, critical specifications information for making initial decisions, and links to complete specifications information.
Logix5000 Controllers Execution Time and Memory
Use Reference Manual, publication 1756-RM087
Assists in estimating the memory use and execution time of programmed logic and in selecting among different programming options.
ControlLogix Chassis Installation Instructions, publication 1756-IN080
1756-RM094
ControlLogix Power Supplies Installation Instructions, publication 1756-IN613
ControlLogix-XT Chassis Installation Instructions, publication 1756-IN637
ControlLogix-XT Power Supplies Installation
Instructions, publication 1756-IN639
GuardLogix Controller Systems Safety Reference
Manual, publication 1756-RM093
Provides information regarding storage, handling, transportation, and disposal of lithium batteries.
Provides Material Safety Data Sheets (MSDS) for individual replacement batteries.
Provides detailed and comprehensive information about how to apply CIP Sync technology to synchronize clocks in a Logix control system.
Provides advanced users with guidelines for system optimization and with system information to guide system design choices.
Describes how to install and ground a ControlLogix chassis.
Describes how to install and ground ControlLogix power supplies.
Describes how to install and ground a ControlLogix-XT chassis.
Describes how to install and ground ControlLogix-XT power supplies.
Describes how to use the GuardLogix controllers.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 13
Preface
Table 4 - Additional Resources Related to ControlLogix Controllers and Systems
For more information about
I/O
See This Resource
ControlLogix Remote I/O Communication Module User
Manual, publication 1756-UM534
Process Remote I/O Communication Interface Module
User Manual, publication 1757-UM007
ControlLogix Digital I/O Modules User Manual, publication 1756-UM058
ControlLogix Analog I/O Modules User Manual, publication 1756-UM009
ControlLogix Configurable Flowmeter Module User
Manual, publication 1756-UM010
ControlLogix HART Analog I/O Modules User Manual, publication 1756-UM533
ControlLogix High Speed Analog I/O Module User
Manual, publication 1756-UM005
ControlLogix High Speed Counter Module User
Manual, publication 1756-UM007
ControlLogix Programmable Limit Switch Module User
Manual, publication 1756-UM002
Runtime/On-line Addition of ControlLogix (1756) I/O over ControlNet and EtherNet/IP White Paper, publication LOGIX-WP006
Instructions (used in programming) Logix5000 Controllers General Instructions Reference
Manual, publication 1756-RM003
Motion
Logix5000 Controllers Motion Instructions Reference
Manual, publication MOTION-RM002
SERCOS Motion Configuration and Startup User
Manual, publication MOTION-UM001
Motion Coordinated Systems User Manual, publication MOTION-UM002
CIP Motion Configuration and Startup User Manual, publication MOTION-UM003
Logix5000 Controllers Motion Instructions Reference
Manual, publication MOTION-RM002
SERCOS Motion Configuration and Startup User
Manual, publication MOTION-UM001
Description
Describes how to configure and troubleshoot the
ControlLogix remote I/O (RIO) communication module.
Describes how to configure and troubleshoot process remote I/O (RIO) communication interface modules.
Describes how to install, configure, and troubleshoot
ControlLogix digital I/O modules.
Describes how to install, configure, and troubleshoot
ControlLogix analog I/O modules.
Describes how to install, configure, and troubleshoot
ControlLogix configurable flowmeter modules.
Describes how to install, configure, and troubleshoot
ControlLogix HART I/O modules.
Describes how to install, configure, and troubleshoot
ControlLogix high-speed analog I/O modules.
Describes how to install, configure, and troubleshoot
ControlLogix high-speed counter modules.
Describes how to install, configure, and troubleshoot
ControlLogix programmable limit switch modules.
Explains adding to the I/O Configuration while online with the controller.
Provides programmers with details about each available instruction for a Logix5000 controller.
Provides programmers with details about the motion instructions that are available for a Logix5000 controller.
Details how to configure a SERCOS motion application system.
Details how to create and configure a coordinated motion application system.
Details how to configure Integrated Motion on the
EtherNet/IP network.
Provides programmers with details about the motion instructions that are available for a Logix5000 controller.
Details how to configure a SERCOS motion application system.
14 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Preface
Table 4 - Additional Resources Related to ControlLogix Controllers and Systems
For more information about
Networks (ControlNet, DeviceNet
EtherNet/IP, serial, and others)
PhaseManager
Programming tasks and procedures
Redundancy
Serial communication
See This Resource
EtherNet/IP Modules in Logix5000 Control Systems
User Manual, publication ENET-UM001
ControlNet Modules in Logix5000 Control Systems
User Manual, publication CNET-UM001
DeviceNet Modules in Logix5000 Control Systems
User Manual, publication DNET-UM004
ControlLogix Data Highway Plus - Universal Remote
I/O Module User Manual, publication 1756-UM514
ControlLogix DH-485 Communication Module User
Manual, publication 1756-UM532
Foundation Fieldbus Linking Device User Manual, publication 1757-UM010
Using Logix5000 Controllers as Masters or Slaves on
Modbus Application Solution, publication CIG-AP129
Using Logix5000 Controllers as Masters or Slaves on
Modbus Application Solution, publication CIG-AP129
Description
Describes how to configure and operate EtherNet/IP modules in a Logix5000 control system.
Describes how to configure and operate ControlNet modules in a Logix5000 control system.
Describes how to configure and operate DeviceNet modules in a Logix5000 control system.
Describes how to configure and operate the ControlLogix
1756 DH+ remote I/O module.
Describes how to configure and operate the ControlLogix
1756 DH-485 module.
Describes how to install, configure, and operate the
1757-FFLD linking device.
Provides information to experienced Modbus users who are programming and troubleshooting applications that use
Logix5000 controllers on the Modbus network.
Provides information to experienced Modbus users who are programming and troubleshooting applications that use
Logix5000 controllers on the Modbus network.
PhaseManager User Manual, publication
LOGIX-UM001
Logix5000 Controllers Common Procedures
Programming Manual, publication 1756-PM001
Logix5000 Controllers Nonvolatile Memory
Programming Manual, publication 1756-PM017
Logix5000 Controllers Produced and Consumed Tags
Programming Manual, publication
1756-PM012
1756-PM011
Logix5000 Controllers Messages, publication
Provides steps, guidance, and examples for setting up and programming a Logix5000 controller to use equipment phases.
Provides links to programming manuals that explain common programming procedures.
Explains various procedures related to the use of memory cards.
Explains produced and consumed tags and information related to using them in your program.
Explains details about caching, managing multiple messages, and sending messages to multiple controllers.
Explains procedures for using and organizing I/O data tags.
Logix5000 Controllers and I/O Tag Data Programming
Manual, publication 1756-PM004
Major, Minor, and I/O Faults Programming Manual, publication 1756-PM014
Logix5000 Controllers Execution Time and Memory
Use Reference Manual, publication 1756-RM087
ControlLogix Redundancy System User Manual, publication 1756-UM523
ControlLogix Enhanced Redundancy System User
Manual, publication 1756-UM535
ControlLogix Enhanced Redundancy System, Revision
16.80 Release Notes, publication 1756-RN650
Using Logix5000 Controllers as Masters or Slaves on
Modbus Application Solution, publication CIG-AP129
Explains major, minor, and I/O faults as well as the
Controller Fault Handler.
Assists in estimating the memory use and execution time of programmed logic and in selecting among different programming options.
Guides the design, development, and implementation of a standard ControlLogix redundancy system.
Guides the design, development, and implementation of an enhanced ControlLogix redundancy system.
ControlLogix Standard Redundancy Firmware, Revision
16.56 Release Notes, publication 1756-RN628
Describes the enhancements, corrected anomalies, and known anomalies specific to the current firmware revision for a standard redundancy system.
Describes the enhancements, corrected anomalies, and known anomalies specific to the current firmware revision for an enhanced redundancy system.
Provides information to experienced Modbus users who are programming and troubleshooting applications that use
Logix5000 controllers on the Modbus network.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 15
Preface
Table 4 - Additional Resources Related to ControlLogix Controllers and Systems
For more information about
SIL2
See This Resource
Using ControlLogix in SIL 2 Applications Reference
Manual, publication 1756-RM001
ControlLogix SIL2 System Configuration Using
RSLogix 5000 Subroutines, publication 1756-AT010
ControlLogix SIL2 System Configuration Using
RSLogix 5000 Subroutines, publication 1756-AT012
Description
Provides list of ControlLogix system components that meet
SIL 2 requirements as well as programming requirements.
Explains how to use subroutines provided by Rockwell
Automation to configure a fault-tolerant system.
Explains how to use Add-On Instructions provided by
Rockwell Automation to configure a fault-tolerant system.
You can view or download publications at http://www.rockwellautomation.com/literature/ . To order paper copies of technical documentation, contact your local Rockwell Automation distributor or sales representative.
16 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Chapter
1
Install the 1756-L7x Controller
Topic
1756-L7x Controller Installation
Insert the Controller into the Chassis
Page
Environment and Enclosure
ATTENTION: This equipment is intended for use in a Pollution Degree 2 industrial environment, in overvoltage
Category II applications (as defined in IEC 60664-1), at altitudes up to 2000 m (6562 ft) without derating.
This equipment is considered Group 1, Class A industrial equipment according to IEC/CISPR 11. Without appropriate precautions, there may be difficulties with electromagnetic compatibility in residential and other environments due to conducted and radiated disturbances.
This equipment is supplied as open-type equipment. It must be mounted within an enclosure that is suitably designed for those specific environmental conditions that will be present and appropriately designed to prevent personal injury resulting from accessibility to live parts. The enclosure must have suitable flame-retardant properties to prevent or minimize the spread of flame, complying with a flame spread rating of 5VA, V2, V1, V0 (or equivalent) if non-metallic. The interior of the enclosure must be accessible only by the use of a tool. Subsequent sections of this publication may contain additional information regarding specific enclosure type ratings that are required to comply with certain product safety certifications.
In addition to this publication, see:
• Industrial Automation Wiring and Grounding Guidelines, Rockwell Automation publication 1770-4.1
, for additional installation requirements.
• NEMA Standard 250 and IEC 60529, as applicable, for explanations of the degrees of protection provided by different types of enclosure.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 17
Chapter 1 Install the 1756-L7x Controller
Prevent Electrostatic Discharge
ATTENTION: This equipment is sensitive to electrostatic discharge, which can cause internal damage and affect normal operation. Follow these guidelines when you handle this equipment:
•
Touch a grounded object to discharge potential static.
•
Wear an approved grounding wriststrap.
• Do not touch connectors or pins on component boards.
•
Do not touch circuit components inside the equipment.
•
Use a static-safe workstation, if available.
• Store the equipment in appropriate static-safe packaging when not in use.
Removal and Insertion Under Power (RIUP)
WARNING: When you insert or remove the module while backplane power is on, an electrical arc can occur. This could cause an explosion in hazardous location installations.
Be sure that power is removed or the area is nonhazardous before proceeding. Repeated electrical arcing causes excessive wear to contacts on both the module and its mating connector. Worn contacts may create electrical resistance that can affect module operation.
European Hazardous Location Approval
European Hazardous Location Approval
The following applies when the product bears the Ex Marking.
This equipment is intended for use in potentially explosive atmospheres as defined by European Union Directive 94/9/EC and has been found to comply with the Essential Health and Safety Requirements relating to the design and construction of Category 3 equipment intended for use in Zone 2 potentially explosive atmospheres, given in Annex II to this Directive.
Compliance with the Essential Health and Safety Requirements has been assured by compliance with EN 60079-15 and EN 60079-0.
ATTENTION: This equipment is not resistant to sunlight or other sources of UV radiation.
WARNING:
• This equipment must be installed in an enclosure providing at least IP54 protection when applied in Zone 2 environments.
• This equipment shall be used within its specified ratings defined by Rockwell Automation.
• This equipment must be used only with ATEX certified Rockwell Automation backplanes.
• Secure any external connections that mate to this equipment by using screws, sliding latches, threaded connectors, or other means provided with this product.
• Do not disconnect equipment unless power has been removed or the area is known to be nonhazardous.
18 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Install the 1756-L7x Controller Chapter 1
North American Hazardous Location Approval
The following information applies when operating this equipment in hazardous locations.
Products marked "CL I, DIV 2, GP A, B, C, D" are suitable for use in
Class I Division 2 Groups A, B, C, D, Hazardous Locations and nonhazardous locations only. Each product is supplied with markings on the rating nameplate indicating the hazardous location temperature code. When combining products within a system, the most adverse temperature code (lowest "T" number) may be used to help determine the overall temperature code of the system. Combinations of equipment in your system are subject to investigation by the local Authority Having Jurisdiction at the time of installation.
EXPLOSION HAZARD
•
Do not disconnect equipment unless power has been removed or the area is known to be nonhazardous.
• Do not disconnect connections to this equipment unless power has been removed or the area is known to be nonhazardous. Secure any external connections that mate to this equipment by using screws, sliding latches, threaded connectors, or other means provided with this product.
• Substitution of components may impair suitability for Class I, Division 2.
• If this product contains batteries, they must only be changed in an area known to be nonhazardous.
Informations sur l'utilisation de cet équipement en environnements dangereux.
Les produits marqués "CL I, DIV 2, GP A, B, C, D" ne conviennent qu'à une utilisation en environnements de Classe I
Division 2 Groupes A, B, C, D dangereux et non dangereux.
Chaque produit est livré avec des marquages sur sa plaque d'identification qui indiquent le code de température pour les environnements dangereux. Lorsque plusieurs produits sont combinés dans un système, le code de température le plus défavorable (code de température le plus faible) peut être utilisé pour déterminer le code de température global du système. Les combinaisons d'équipements dans le système sont sujettes à inspection par les autorités locales qualifiées au moment de l'installation.
RISQUE D’EXPLOSION –
•
Couper le courant ou s'assurer que l'environnement est classé non dangereux avant de débrancher l'équipement.
• Couper le courant ou s'assurer que l'environnement est classé non dangereux avant de débrancher les connecteurs. Fixer tous les connecteurs externes reliés à cet équipement à l'aide de vis, loquets coulissants, connecteurs filetés ou autres moyens fournis avec ce produit.
•
La substitution de composants peut rendre cet équipement inadapté à une utilisation en environnement de Classe I,
Division 2.
•
S'assurer que l'environnement est classé non dangereux avant de changer les piles.
Before You Begin
Complete these tasks using the appropriate resources listed as references before you install your controller.
Task
Install a ControlLogix chassis.
Install a ControlLogix power supply.
Resources
• ControlLogix Chassis, Series B Installation Instructions, publication 1756-IN080
• ControlLogix-XT Chassis Installation Instructions, publication
1756-IN637
• ControlLogix Power Supplies Installation Instructions, publication 1756-IN613
• ControlLogix-XT Power Supplies Installation Instructions, publication 1756-IN639
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 19
Chapter 1 Install the 1756-L7x Controller
1756-L7x Controller Parts
These sections describe parts that are included with the controller, as well as available accessory parts.
Parts Included with the 1756-L7x Controller
These parts are included with the controller:
• 1756-L72, 1756-L73, 1756-L74, or 1756-L75 controller
• 1756-ESMCAP capacitor-based energy storage module (ESM)
• 1784-SD1 Secure Digital (SD) card, 1 GB
• 1747-KY controller key
Figure 1 - Parts with the 1756-L7x Controller
1756-L7x Controller
SD Card (installed)
1756-ESMCAP
(installed)
1747-KY Key
32016-M
IMPORTANT The 1756-L7x controllers ship with an SD card installed. We recommend that you leave the SD card installed.
20 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Install the 1756-L7x Controller Chapter 1
Parts Available for Use with the 1756-L7x Controller
In addition to parts included with the controller, you may choose to use these parts specific to your application.
If your application requires
USB connection from a computer to the controller
Nonvolatile memory
ESM without WallClockTime backup power
Then use this part
SAMTEC RSP-119350 USB cable
1784-SD1 (1 GB) or 1784-SD2 (2 GB)
1756-ESMNSE
This ESM does not have WallClockTime back-up power.
Use this ESM if your application requires that the installed ESM deplete its residual stored energy to 200 µJoules or less before transporting it into or out of your application
(1)
Additionally, you can use this ESM with a
1756-L73 (8 MB) or smaller memory sized controller only.
1756-ESMNRM ESM that secures the controller by preventing the USB connection and
SD card use
(1)
This ESM provides your application an enhanced degree of security
1756-L7x Controller
Installation
These sections explain how to install the 1756-L7 x controller. To install the
1756-L7 x controller, complete the tasks summarized in this table.
Task
Insert the Controller into the Chassis
Page
Insert the Controller into the Chassis
When installing a ControlLogix controller, you can do the following:
• Place the controller in any slot.
• Use multiple controllers in the same chassis.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 21
Chapter 1 Install the 1756-L7x Controller
You can install or remove a ControlLogix controller while chassis power is on and the system is operating.
WARNING: When you insert or remove the module while backplane power is on, an electrical arc can occur. This could cause an explosion in hazardous location installations. Be sure that power is removed or the area is nonhazardous before proceeding.
Repeated electrical arcing causes excessive wear to contacts on both the controller and its mating connector on the chassis. Worn contacts may create electrical resistance that can affect controller operation.
IMPORTANT The ESM begins charging when one of these actions occurs:
• The controller and ESM are installed into a powered chassis.
• Power is applied to the chassis that contains a controller with the
ESM installed.
• An ESM is installed into a powered controller.
After power is applied, the ESM charges for up to two minutes as indicated by CHRG or ESM Charging on the status display.
1.
Align the circuit board with the top and bottom guides in the chassis.
Top Circuit Board
Aligned
Logix 55xx
RUN FORCESD OK
Bottom Circuit
Board Aligned
31997-M
2.
Slide the module into the chassis until it snaps into place.
3.
Verify that the controller is flush with the power supply or other installed modules.
After you have inserted the controller into the chassis, reference the Status
Indicators section on page 193 for information about interpreting the status
indicators.
22 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Insert the Key
After the controller is installed, insert the key.
Install the 1756-L7x Controller Chapter 1
Logix 55xx
RUN FORCESD OK
Remove the SD Card
The 1756-L7 x controller ships with an SD card installed. Complete these steps to remove the SD card from the 1756-L7 x controller.
WARNING: When you insert or remove the Secure Digital (SD) memory card while power is on, an electrical arc can occur. This could cause an explosion in hazardous location installations.
Be sure that power is removed or the area is nonhazardous before proceeding.
IMPORTANT
• Verify that the SD card status indicator is off and that the card is not in use before removing it.
• We recommend that you do the following:
Leave an SD card installed.
Use the SD cards available from Rockwell Automation (catalog number 1784-SD1 or 1784-SD2).
• While other SD cards may be used with the controller,
Rockwell Automation has not tested the use of those cards with the controller. If you use an SD card other than those available from
Rockwell Automation, you may experience data corruption or loss.
• Also, SD cards not provided by Rockwell Automation do not have the same industrial, environmental, and certification ratings as those available from Rockwell Automation.
1.
Verify that the SD card is not in use by checking to be sure the
SD indicator is off.
TIP You may also put the controller into Program mode to keep the controller from writing to the SD card while it is removed.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 23
Chapter 1 Install the 1756-L7x Controller
2.
Open the door to access the SD card.
Logix 55xx
RUN FORCESD OK
32015-M
3.
Press and release the SD card to eject it.
Logix 55xx
RUN FORCESD OK
Install the SD Card
24
32004-M
4.
Remove the SD card and close the door.
Complete these steps to install the SD card on the 1756-L7 x controllers.
1.
Verify that the SD card is locked or unlocked according to your preference.
Unlocked
Locked
32005-M
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Install the 1756-L7x Controller Chapter 1
For more information about the lock/unlock memory settings in
RSLogix 5000 software, see the Load or Store to the Memory Card section
on
2.
Open the door for the SD card.
Logix 55xx
RUN FORCESD OK
32002-M
3.
Insert the SD card into the SD card slot.
4.
Gently press the card until it clicks into place.
Logix 55xx
RUN FORCESD OK
32004-M
5.
Close the SD card door.
Logix 55xx
RUN FORCESD OK
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
32006-M
25
Chapter 1 Install the 1756-L7x Controller
Uninstall the ESM
Consider these points before removing the ESM:
• The 1756-L7x controllers come with the 1756-ESMCAP module installed. For more information on when you use a 1756-ESMNSE or
1756-ESMNRM module, see page 21
.
• After the 1756-L7x controllers lose power, either because the chassis power is turned off or the controller has been removed from a powered chassis, do not remove the ESM immediately.
Wait until the controller’s OK status indicator transitions from Green to
Solid Red to OFF before you remove the ESM.
• You can use the 1756-ESMNSE module with a 1756-L73 (8MB) or smaller memory-sized controller only.
• Use the 1756-ESMNSE module if your application requires that the installed ESM deplete its residual stored energy to 200 μjoules or less before transporting it into or out of your application.
• Once it is installed, you cannot remove the 1756-ESMNRM module from a 1756-L7 x controller.
IMPORTANT Before you remove an ESM, make necessary adjustments to your program to account for potential changes to the WallClockTime attribute.
Complete these steps to remove a 1756-ESMCAP or 1756-ESMNSE module currently installed in a 1756-L7 x controller.
WARNING: If your application requires the ESM to deplete its residual stored energy to 200 µjoules or less before you transport it into or out of the application, use the 1756-ESMNSE module only. In this case, complete these steps before you remove the ESM.
a. Turn power off to the chassis.
After you turn power off to the chassis, the controller’s OK status indicator transitions from Green to Solid Red to OFF.
b. Wait at least 15 minutes for the residual stored energy to decrease to
200 µjoules or less before you remove the ESM.
There is no visual indication of when the 15 minutes has expired. You
must track that time period.
c. Remove the 1756-ESMNSE module as described beginning on
.
WARNING: When you insert or remove the energy storage module while backplane power is on, an electrical arc can occur. This could cause an explosion in hazardous location installations.
Be sure that power is removed or the area is nonhazardous before proceeding. Repeated electrical arcing causes excessive wear to contacts on both the module and its mating connector.
26 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Install the 1756-L7x Controller Chapter 1
1.
Remove the key from the keyswitch.
IMPORTANT The next step depends on which of the following conditions applies to your application.
• If you are removing the ESM from a powered 1756-L7x controller,
• If you are removing the ESM from a 1756-L7x controller that is not powered, either because the chassis power is turned off or the controller has been removed from a powered chassis, do not
remove the ESM immediately.
Wait until the controller’s OK status indicator transitions from
Green to Solid Red to OFF before you remove the ESM.
After the OK status indicator transitions to Off, go to
.
2.
Use your thumb to press down on the black release and pull the ESM away from the controller.
Logix 55xx
RUN FORCESD OK
Logix 55xx
RUN FORCESD OK
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 27
Chapter 1 Install the 1756-L7x Controller
Install the ESM
To install an ESM in the 1756-L7 x controller, complete these steps.
1.
Align the tongue-and-groove slots of the ESM and controller.
Logix 55xx
RUN FORCESD OK
2.
Slide the ESM back until it snaps into place.
The ESM begins charging after installation. Charging status is indicated by one of these status messages:
• ESM Charging
• CHRG
After you install the ESM, it may take up to 15 seconds for the charging status messages to display.
IMPORTANT Allow the ESM to finish charging before removing power from the controller.
To verify that the ESM is fully charged, check the status display to confirm that messages CHRG or ESM charging are no longer indicated.
TIP We recommend that you check the WallClockTime object attributes after installing an ESM to verify that time of the controller is correct.
28 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Install the 1756-L7x Controller Chapter 1
Additional Resources
Consult these resources for additional information related to the installation of the ControlLogix system.
Resource
ControlLogix Chassis Installation Instructions, publication 1756-IN080
Description
Describes how to install and ground a ControlLogix chassis.
ControlLogix-XT Chassis Installation Instructions, publication 1756-IN637 Describes how to install and ground a ControlLogix-XT chassis.
ControlLogix Power Supplies Installation Instructions, publication
1756-IN613
Describes how to install and ground ControlLogix power supplies.
Logix5000 Controllers General Instruction Reference Manual, publication
1756-RM003
Provides details about the WallClockTime object and attributes.
You can view or download publications at http://www.rockwellautomation.com/literature/ . To order paper copies of technical documentation, contact your local Rockwell Automation distributor or sales representative.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 29
Chapter 1 Install the 1756-L7x Controller
Notes:
30 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Chapter
2
Install the 1756-L6x Controller
Topic
1756-L6x Controller Installation
CompactFlash Card Installation and Removal
Battery Connection and Replacement
Insert the Controller into the Chassis
Remove the Controller from the Chassis
Page
Precautions
Consider these precautions before installing or removing the ControlLogix controllers.
Environment and Enclosure
ATTENTION: This equipment is intended for use in a Pollution Degree 2 industrial environment, in overvoltage Category
II applications (as defined in IEC 60664-1), at altitudes up to 2000 m (6562 ft) without derating.
This equipment is considered Group 1, Class A industrial equipment according to IEC/CISPR 11. Without appropriate precautions, there may be difficulties with electromagnetic compatibility in residential and other environments due to conducted and radiated disturbances.
This equipment is supplied as open-type equipment. It must be mounted within an enclosure that is suitably designed for those specific environmental conditions that will be present and appropriately designed to prevent personal injury resulting from accessibility to live parts. The enclosure must have suitable flame-retardant properties to prevent or minimize the spread of flame, complying with a flame spread rating of 5VA, V2, V1, V0 (or equivalent) if non-metallic. The interior of the enclosure must be accessible only by the use of a tool. Subsequent sections of this publication may contain additional information regarding specific enclosure type ratings that are required to comply with certain product safety certifications.
In addition to this publication, see:
•
Industrial Automation Wiring and Grounding Guidelines, for additional installation requirements, Rockwell Automation publication 1770-4.1
.
•
NEMA Standard 250 and IEC 60529, as applicable, for explanations of the degrees of protection provided by different types of enclosure.
Programmable Electronic Systems (PES)
ATTENTION: Personnel responsible for the application of safety-related programmable electronic systems
(PES) shall be aware of the safety requirements in the application of the system and shall be trained in using the system.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 31
Chapter 2 Install the 1756-L6x Controller
Preventing Electrostatic Discharge
ATTENTION: This equipment is sensitive to electrostatic discharge, which can cause internal damage and affect normal operation. Follow these guidelines when you handle this equipment:
•
Touch a grounded object to discharge potential static.
•
Wear an approved grounding wriststrap.
• Do not touch connectors or pins on component boards.
•
Do not touch circuit components inside the equipment.
•
Use a static-safe workstation, if available.
• Store the equipment in appropriate static-safe packaging when not in use.
Removing Module While Under Power (RIUP)
ATTENTION: When you insert or remove the module while backplane power is on, an electrical arc can occur.
This could cause an explosion in hazardous location installations.
Be sure that power is removed or the area is nonhazardous before proceeding. Repeated electrical arcing causes excessive wear to contacts on both the module and its mating connector. Worn contacts may create electrical resistance that can affect module operation.
European Hazardous Location Approval
European Hazardous Location Approval
The following applies when the product bears the Ex Marking.
This equipment is intended for use in potentially explosive atmospheres as defined by European Union Directive 94/9/EC and has been found to comply with the Essential Health and Safety Requirements relating to the design and construction of Category 3 equipment intended for use in Zone 2 potentially explosive atmospheres, given in Annex II to this Directive.
Compliance with the Essential Health and Safety Requirements has been assured by compliance with EN 60079-15 and EN 60079-0.
ATTENTION: This equipment is not resistant to sunlight or other sources of UV radiation.
WARNING:
• This equipment must be installed in an enclosure providing at least IP54 protection when applied in Zone 2 environments.
• This equipment shall be used within its specified ratings defined by Rockwell Automation.
• This equipment must be used only with ATEX certified Rockwell Automation backplanes.
• Secure any external connections that mate to this equipment by using screws, sliding latches, threaded connectors, or other means provided with this product.
• Do not disconnect equipment unless power has been removed or the area is known to be nonhazardous.
32 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Install the 1756-L6x Controller Chapter 2
North American Hazardous Location Approval
The following information applies when operating this equipment in hazardous locations.
Products marked "CL I, DIV 2, GP A, B, C, D" are suitable for use in Class I Division 2 Groups A, B, C, D, Hazardous Locations and nonhazardous locations only. Each product is supplied with markings on the rating nameplate indicating the hazardous location temperature code. When combining products within a system, the most adverse temperature code (lowest "T" number) may be used to help determine the overall temperature code of the system. Combinations of equipment in your system are subject to investigation by the local Authority Having
Jurisdiction at the time of installation.
EXPLOSION HAZARD -
• Do not disconnect equipment unless power has been removed or the area is known to be nonhazardous.
• Do not disconnect connections to this equipment unless power has been removed or the area is known to be nonhazardous.
Secure any external connections that mate to this equipment by using screws, sliding latches, threaded connectors, or other means provided with this product.
• Substitution of components may impair suitability for Class I,
Division 2.
• If this product contains batteries, they must only be changed in an area known to be nonhazardous.
Informations sur l’utilisation de cet équipement en environnements dangereux.
Les produits marqués "CL I, DIV 2, GP A, B, C, D" ne conviennent qu'à une utilisation en environnements de Classe I Division 2
Groupes A, B, C, D dangereux et non dangereux. Chaque produit est livré avec des marquages sur sa plaque d'identification qui indiquent le code de température pour les environnements dangereux. Lorsque plusieurs produits sont combinés dans un système, le code de température le plus défavorable (code de température le plus faible) peut être utilisé pour déterminer le code de température global du système. Les combinaisons d'équipements dans le système sont sujettes à inspection par les autorités locales qualifiées au moment de l'installation.
RISQUE D’EXPLOSION –
• Couper le courant ou s'assurer que l'environnement est classé non dangereux avant de débrancher l'équipement.
• Couper le courant ou s'assurer que l'environnement est classé non dangereux avant de débrancher les connecteurs. Fixer tous les connecteurs externes reliés à cet équipement à l'aide de vis, loquets coulissants, connecteurs filetés ou autres moyens fournis avec ce produit.
• La substitution de composants peut rendre cet équipement inadapté à une utilisation en environnement de Classe I,
Division 2.
• S'assurer que l'environnement est classé non dangereux avant de changer les piles.
Lithium Batteries
ATTENTION: When you connect or disconnect the battery an electrical arc can occur. This could cause an explosion in hazardous location installations. Be sure that the area is nonhazardous before proceeding.
For safety information about handling lithium batteries, including handling and disposal of leaking batteries, see
Guidelines for Handling Lithium Batteries, publication AG 5-4 .
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 33
Chapter 2 Install the 1756-L6x Controller
Before You Begin
Complete these tasks using the appropriate resources listed as references before you install your controller.
Task
Install a ControlLogix chassis.
Install a ControlLogix power supply.
Resources
• ControlLogix Chassis, Series B Installation Instructions, publication 1756-IN080
• ControlLogix-XT Chassis Installation Instructions, publication
1756-IN637
• ControlLogix Power Supplies Installation Instructions, publication 1756-IN613
• ControlLogix-XT Power Supplies Installation Instructions, publication 1756-IN639
1756-L6x Controller Parts
These sections describe parts that are included with the 1756-L6 x controllers and parts that are not included with the controller and are optional.
Parts Included with the 1756-L6x Controller
These parts are included with your controller:
• Battery
– For series A controllers, catalog number 1756-BA1
– For series B controllers, catalog number 1756-BA2
• Key, catalog number 1747-KY
Figure 2 - Parts Included with the 1756-L6x Controller
1756-L6x Controller
1756-BA1 or 1756-BA2
Logix 5563
RUN
I/O
FORCE
BAT
RUN
RS232
OK
REM
PROG
1747-KY Key
34 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Install the 1756-L6x Controller Chapter 2
Parts Not Included with the 1756-L6x Controller
In addition to parts included with the controller, you may choose to use these parts specific to your application.
If your application requires
RS-232 connection to the controller
Nonvolatile memory
Expanded battery life for extended memory retention
Then use this component
1756-CP3 serial cable
1784-CF64 or 1784-CF128 CompactFlash card
1756-BATM battery module
IMPORTANT The 1756-BATM battery module supports memory retention only when the controller is in the chassis and the battery module is properly connected.
The 1756-BATM can be used with series A controllers, but it cannot be used with series B controllers. Series B controllers use battery power differently than previous controllers and therefore battery considerations for this series controller vary.
For more information about determining what battery to use, see the
ControlLogix Controllers Selection Guide, publication 1756-SG001 .
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 35
Chapter 2 Install the 1756-L6x Controller
1756-L6x Controller
Installation
These sections explain how to install a 1756-L6 x controller. To install the
1756-L6 x controller, complete the tasks summarized in this table.
Task
CompactFlash Card Installation and Removal
Battery Connection and Replacement
Insert the Controller into the Chassis
Remove the Controller from the Chassis
Page
CompactFlash Card
Installation and Removal
The installation and removal of a CompactFlash card depends on the controller.
WARNING: When you insert or remove the CompactFlash Card while power is on, an electrical arc can occur. This could cause an explosion in hazardous location installations.
Be sure that power is removed or the area is nonhazardous before proceeding.
• If you are using a series A controller, reference these sections:
– Install a CompactFlash Card in a Series A Controller, page 36 .
– Remove a CompactFlash Card from a Series A Controller, page 37 .
• If you are using a series B controller, reference these sections:
– Install a CompactFlash Card in a Series B Controller, page 37 .
– Remove a CompactFlash Card from a Series B Controller, page 38 .
Install a CompactFlash Card in a Series A Controller
Complete these steps to install a CompactFlash card in a series A controller.
2.
36
4.
1.
3.
1.
Lay the controller on its side with the front facing to the left.
2.
Raise the locking clip.
3.
Insert the CompactFlash card into the slot at the bottom of the controller.
4.
Pull the clip forward and then downward until it snaps into place over the card.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Install the 1756-L6x Controller Chapter 2
Remove a CompactFlash Card from a Series A Controller
Complete these steps to remove a CompactFlash card from a series A controller.
2.
1.
3.
1.
Lay the controller in its side with the keyswitch facing left.
2.
Raise the locking clip.
3.
Gently pull the card out of the slot.
Install a CompactFlash Card in a Series B Controller
Complete these steps to install a CompactFlash card in a series B controller.
1.
3.
2.
4.
1.
Open the door of the controller and push the CompactFlash latch to the left.
2.
Insert the CompactFlash card with the Allen-Bradley logo pointing left.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 37
Chapter 2 Install the 1756-L6x Controller
3.
Release the latch and secure it over the CompactFlash card.
Remove a CompactFlash Card from a Series B Controller
Complete these steps to remove a CompactFlash card from a series B controller.
1.
3.
2.
Battery Connection and
Replacement
1.
Verify that the OK indicator is solid green then open the door of the controller.
2.
Push and hold the CompactFlash latch to the left.
3.
Push the eject button and remove the card.
4.
Release the latch.
This product contains a hermetically-sealed lithium battery that may need to be replaced during the life of the product.
At the end of its life, the battery contained in this product should be collected separately from any unsorted municipal waste.
The collection and recycling of batteries helps protect the environment and contributes to the conservation of natural resources as valuable materials are recovered.
38 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Install the 1756-L6x Controller Chapter 2
WARNING: When you connect or disconnect the battery an electrical arc can occur. This could cause an explosion in hazardous location installations. Be sure that power is removed or the area is nonhazardous before proceeding.
For Safety information on the handling of lithium batteries, including handling and disposal of leaking batteries, see Guidelines for Handling
Lithium Batteries, publication AG-5.4
.
ATTENTION: To prevent program loss, replace a 1756-BA1 or
1756-BA2 battery according to the schedule below even if the
BAT status indicator is off.
If the temperature 2.54 cm
(1 in.) below the chassis is
-25…35 °C (-13…95
F)
36…40 °C (96.8…104
F)
41…45 °C (105.8…113
F)
46…50 °C (114.8…122
F)
51…55 °C (123.8…131
F)
56…70 °C (132.8…158
F)
Replace the battery within
No replacement required
3 years
2 years
16 months
11 months
8 months
ATTENTION: Store batteries in a cool, dry environment. We recommend 25 C (77 F) with 40…60% relative humidity. You may store batteries for up to 30 days between -45…85 C
(-49…185 F), such as during transportation. To avoid leakage or other hazards, do not store batteries above 60 C (140 F) for more than 30 days.
Connection of the battery varies depending on your controller series:
• If you are using a series A controller, see page 40 .
• If you are using a series B controller, see page 41 .
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 39
Chapter 2 Install the 1756-L6x Controller
Install the Battery on a Series A Controller
Complete these steps to install a 1756-BA1 battery on a series A controller.
For information about installing a 1756-BATM battery module or replacing a
1756-BATA assembly, see the ControlLogix Battery Module Installation
Instructions, publication 1756-IN578 .
ATTENTION: For a series A controller, connect only a 1756-BA1 battery or a 1756-BATM battery module. The use of other batteries may damage the controller.
DATE
Wire Terminal Location
Top
Middle
Bottom
Connected Wire
No Connection
Black Lead (-)
Red Lead (+)
1.
Connect the battery connector to the port to the right of the battery slot.
2.
Snap the battery into the battery slot.
3.
Write the date on the battery label.
4.
Attach the label to the inside of the controller door.
40 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Install the 1756-L6x Controller Chapter 2
Install the Battery on a Series B Controller
Complete these steps to install the battery on a series B controller.
ATTENTION: For a series B controller, connect only a 1756-BA2 battery. The use of other batteries may damage the controller.
DATE
DSR-6
RTS-7
CTS-8
N/C-9
RS232
1-DCD
2-RXD
3-TXD
4-DTR
5-GND
COMPACT
FLASH
1 To
Insert 1
2
To Eject
1 + 2
1
UP
BATTERY
DATE
2
BATTERY
PORT
1
2
1.
Insert the battery, with the arrow pointing up, into the battery slot.
2.
Plug the battery connector into the battery port (+ Red, - Black).
3.
Write the date on the battery label.
4.
Attach the label to the inside of the controller door.
30563-M
Insert the Controller into the Chassis
When installing a ControlLogix controller, you can do the following:
• Place the controller in any slot.
• Use multiple controllers in the same chassis.
You can install or remove a ControlLogix controller while chassis power is on and the system is operating.
WARNING: When you insert or remove the module while backplane power is on, an electrical arc can occur. This could cause an explosion in hazardous location installations. Be sure that power is removed or the area is nonhazardous before proceeding.
Repeated electrical arcing causes excessive wear to contacts on both the controller and its mating connector on the chassis. Worn contacts may create electrical resistance that can affect controller operation.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 41
Chapter 2 Install the 1756-L6x Controller
1.
Insert the key into the controller.
2.
Turn the key to the PROG position.
3.
Align the circuit board with the top and bottom guides in the chassis.
4.
Slide the module into the chassis.
5.
Verify that the controller is flush with the power supply or other installed modules.
6.
Verify that the top and bottom latches are engaged.
After you have inserted the controller into the chassis, you may need to reference
the Status Indicators section on page 193 for more information related to the
state of the controller.
Remove the Controller from the Chassis
You can install or remove a controller while chassis power is on and the system is operating. If you remove the controller, all of the devices owned by the controller go to their configured fault state.
WARNING: When you insert or remove the module while backplane power is on, an electrical arc can occur. This could cause an explosion in hazardous location installations. Be sure that power is removed or the area is nonhazardous before proceeding.
Repeated electrical arcing causes excessive wear to contacts on both the controller and its mating connector in the chassis. Worn contacts may create electrical resistance that can affect controller operation.
1.
Press the locking tabs on the top and bottom of the controller.
42 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
2.
Slide the controller out of the chassis.
Install the 1756-L6x Controller Chapter 2
1.
2.
20880
1.
Additional Resources
Consult these resources for additional information related to the installation of the ControlLogix system.
Resource
ControlLogix Chassis Installation Instructions, publication 1756-IN080
Description
Describes how to install and ground a ControlLogix chassis.
ControlLogix-XT Chassis Installation Instructions, publication 1756-IN637 Describes how to install and ground a ControlLogix-XT chassis.
ControlLogix Power Supplies Installation Instructions, publication
1756-IN613
Describes how to install and ground ControlLogix power supplies.
ControlLogix-XT Power Supplies Installation Instructions, publication
1756-IN639
Describes how to install and ground ControlLogix-XT power supplies.
You can view or download publications at http://www.rockwellautomation.com/literature/ . To order paper copies of technical documentation, contact your local Rockwell Automation distributor or sales representative.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 43
Chapter 2 Install the 1756-L6x Controller
Notes:
44 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Make Connections
Chapter
3
Start Using the Controller
Topic
Connect to the 1756-L7x Controller
Connect to the 1756-L6x Controller
Choose the Controller Operation Mode
Use the Keyswitch to Change the Operation Mode
Use RSLogix 5000 Software to Change the Operation Mode 64
Load or Store to the Memory Card 66
Use ControlLogix Energy Storage Modules (ESMs)
Estimate the ESM Support of the WallClockTime
Maintain the Battery (1756-L6x controllers only)
Page
Before you can begin using your controller, you must make a connection to the controller.
1756-L7x Connection Options
Connection options with the 1756-L7 x include the following:
• Connecting using a USB cable, see Connect to the 1756-L7x Controller
on
• Installing and configuring a communication module in the chassis with the controller, refer to the installation instructions of the communication module
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 45
Chapter 3 Start Using the Controller
1756-L6x Connection Options
Connection options with the 1756-L6 x include the following:
• Connecting using a serial cable, see Connect to the 1756-L6x Controller
on
• Installing and configuring a communication module in the chassis with the controller, refer to the installation instructions of the communication module
TIP When upgrading your 1756-L6x controller firmware, we recommend you use a network connection other than the serial cable. This is because serial connections are much slower than other communication connections.
Connect to the 1756-L7x
Controller
The controller has a USB port that uses a Type B receptacle. The port is USB
2.0-compatible and runs at 12 Mbps.
To use the USB port of the controller, you must have RSLinx software, version
2.56 or later, installed on your workstation. Use a USB cable to connect your workstation to the USB port. With this connection, you can upgrade firmware and download programs to the controller directly from your workstation.
ATTENTION: The USB cable is not to exceed 3.0 m (9.84 ft) and must not contain hubs.
WARNING: The USB port is intended for temporary local programming purposes only and not intended for permanent connection. If you connect or disconnect the USB cable with power applied to this module or any device on the USB network, an electrical arc can occur. This could cause an explosion in hazardous location installations.
Be sure that power is removed or the area is nonhazardous before proceeding.
A Samtec Inc. RSP-119350 USB cable is required to maintain hazardous location certifications.
46 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Start Using the Controller Chapter 3
Figure 3 - USB Connection
Logix 55xx
RUN FORCESD OK
32007-M
32007-M
Set Up the USB Driver
To configure RSLinx software to use a USB port, you need to first set up a USB driver. To set up a USB driver, perform this procedure.
1.
Connect your controller and workstation by using a USB cable.
The Found New Hardware Wizard dialog box appears.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 47
Chapter 3 Start Using the Controller
2.
Click any of the Windows Update connection options and click Next.
TIP If the software for the USB driver is not found and the installation is canceled, verify that you have installed RSLinx Classic software, version
2.56 or later.
3.
Click Install the software automatically (Recommended) and click Next.
The software is installed.
48
4.
Click Finish to set up your USB driver.
To browse to your controller in RSLinx software, click the RSWho icon.
The RSLinx Workstation organizer appears.
USB Port Driver
Virtual Chassis
Driver
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Start Using the Controller Chapter 3
Your controller appears under two different drivers, a virtual chassis and the USB port. You can use either driver to browse to your controller.
Connect to the 1756-L6x
Controller
The 1756-L6 x ControlLogix controller uses a serial port for workstation connections.
WARNING: If you connect or disconnect the serial cable with power applied to this module or the serial device on the other end of the cable, an electrical arc can occur. This could cause an explosion in hazardous location installations.
Be sure that power is removed or the area is nonhazardous before proceeding.
To connect a workstation to the serial port, you can make your own serial cable or use one of these cables:
• 1756-CP3 serial cable
• 1747-CP3 cable from the SLC product family (if you use this cable, the controller door may not close)
To Workstation
To Controller
42576
Follow these guidelines if you make your own serial cable:
• Limit the length to 15.2 m (50 ft).
• Wire the connectors as shown.
• Attach the shield to both connectors.
To Workstation To Controller
1 CD
2 RDX
3 TXD
4 DTR
COMMON
6 DSR
7 RTS
8 CTS
9
1 CD
2 RDX
3 TXD
4 DTR
COMMON
6 DSR
7 RTS
8 CTS
9
42231
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 49
Chapter 3 Start Using the Controller
Plug the workstation end of the serial cable into the RS-232 port on the front of the controller.
DSR-6
RTS-7
CTS-8
N/C-9
RS232
1-DCD
2-RXD
3-TXD
4-DTR
5-GND
1
To
Insert 1
2 To Eject
1 + 2
COMPACT
FLASH
1
2
UP
BATTERY
DATE
BATTERY
PORT
1
2
Configure the Serial Driver
Use RSLinx software to configure the RS232 DF1 device driver for serial communication.
To configure the driver, perform this procedure.
1.
In RSLinx software, from the Communications menu, choose Configure
Drivers.
50 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
The Configure Drivers dialog box appears.
Start Using the Controller Chapter 3
2.
From the Available Driver Types pull-down menu, choose the RS-232
DF1 device driver.
3.
Click Add New.
The Add New RSLinx Driver dialog box appears.
4.
Type the driver name and click OK.
5.
Specify the serial port settings.
a. From the Comm Port pull-down menu, choose the serial port on the workstation to which the cable is connected.
b. From the Device pull-down menu, choose Logix 5550/CompactLogix.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 51
Chapter 3 Start Using the Controller c. Click Auto-Configure.
Upgrade Controller
Firmware
6.
If the auto configuration is successful, click OK.
If the auto configuration is not successful, verify that the correct Comm
Port was selected.
7.
Click Close.
You may choose to upgrade controller firmware by using either of these tools:
• ControlFLASH software packaged with RSLogix 5000 software
• AutoFlash feature of RSLogix 5000 software
52 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Start Using the Controller Chapter 3
To upgrade your controller firmware, complete the appropriate tasks listed in this table.
Task
Determine Required Controller Firmware
Use ControlFLASH Utility to Upgrade
FirmwareUse ControlFLASH Utility to Upgrade
FirmwareUse ControlFLASH Utility to Upgrade
FirmwareUse ControlFLASH Utility to Upgrade
FirmwareUse ControlFLASH Utility to Upgrade
FirmwareUse ControlFLASH Utility to Upgrade
FirmwareUse ControlFLASH Utility to Upgrade
FirmwareUse ControlFLASH Utility to Upgrade
FirmwareUse ControlFLASH Utility to Upgrade
FirmwareUse ControlFLASH Utility to Upgrade
FirmwareUse ControlFLASH Utility to Upgrade
FirmwareUse ControlFLASH to Upgrade
FirmwareUse ControlFLASH to Upgrade
Use AutoFlash to Upgrade Firmware
Page
Determine Required Controller Firmware
Use this table to determine what firmware revision is required for your controller.
Table 5 - Firmware Required for Controllers
Controller
1756-L61
1756-L62
B
1756-L63 A
B
A
Series Use this firmware revision
A 12.x or later
13.40 or later
12.x or later
13.40 or later
• If not using a CompactFlash card, 10.x or later
• If using a CompactFlash card, 11.x or later
B
1756-L63XT B
1756-L64
1756-L65
B
B
13.40 or later
13.40 or later
16 or later
17 or later
1756-L72
1756-L73
1756-L74
1756-L75
A
A
A
A
19 or later
18 or later
19 or later
18 or later
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 53
Chapter 3 Start Using the Controller
Obtain Controller Firmware
Controller firmware is packaged with RSLogix 5000 programming software. In addition, controller firmware is also available for download from the Rockwell
Automation Technical Support website at http://www.rockwellautomation.com/support/ .
Use ControlFLASH Utility to Upgrade Firmware
To upgrade your controller firmware with ControlFLASH software, complete these steps.
IMPORTANT If the SD card is locked and the stored project’s Load Image option is set to On Power Up, the controller firmware is not updated as a result of these steps. The previously-stored firmware and project are loaded instead.
1.
Verify that the appropriate network connection is made and the network driver has been configured in RSLinx software.
2.
Launch ControlFLASH software and click Next to begin the upgrade process.
1756-L7x Controllers
3.
Select the catalog number of your controller and click Next.
1756-L6x Controllers
54 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Start Using the Controller Chapter 3
4.
Expand the network driver to locate your controller.
1756-L7x Controller with USB Network Driver
1756-L6x Controller with Ethernet Network Driver
1756-L7x Controller Upgrade
5.
Select your controller and click Next.
6.
Select the firmware revision you want to upgrade to and click Next.
1756-L6x Controller Upgrade
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 55
Chapter 3 Start Using the Controller
TIP If you are using a 1756-L7x controller and experience a Script File Error after selecting the firmware revision number
(see the example below), there is likely an anomaly with your firmware files.
To recover, take these actions:
•
Go to http://www.rockwellautomation.com/support/ and download the firmware revision you are trying to upload to. Replace the firmware revision you have previously installed with that posted on the Technical Support website.
•
If replacing your firmware revision does not resolve the anomaly, contact Rockwell Automation Technical Support.
7.
Click Finish.
1756-L7x Controller Progress
A confirmation dialog box opens.
8.
Click Yes.
The progress dialog box indicates the progress of the firmware upgrade.
The 1756-L7 x controllers indicate progress in updates and blocks, where the 1756-L6 x controllers indicate progress only in blocks.
1756-L6x Controller Progress
56
IMPORTANT Allow the firmware update to fully complete before cycling power or otherwise interrupting the upgrade.
TIP If the ControlFLASH upgrade of the controller is interrupted, the 1756-L7x controller reverts to boot firmware, that is firmware revision 1.xxx.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Start Using the Controller Chapter 3
When the upgrade is complete, the Update Status dialog box indicates that the upgrade is complete.
9.
Click OK.
10.
Close ControlFLASH software.
Use AutoFlash to Upgrade Firmware
To upgrade your controller firmware with the AutoFlash feature of RSLogix 5000 software, complete these steps.
1.
Verify that the appropriate network connection is made and your network driver is configured in RSLinx software.
2.
Use RSLogix 5000 programming software to create a controller project at the version you need.
3.
Click RSWho to specify the controller path.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 57
Chapter 3 Start Using the Controller
4.
Select your controller and click Update Firmware.
1756-L7x Controller with USB Driver
1756-L6x Controller with Ethernet Driver
5.
Select the firmware revision to upgrade to and click update.
58
6.
Click Yes.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
The firmware upgrade begins.
Start Using the Controller Chapter 3
Allow the firmware upgrade to complete without interruption.
When the firmware upgrade is complete, the Who Active dialog box opens. You may complete other tasks in RSLogix 5000 software.
Set the Communication
Path
To get online with the controller, you must specify a controller path in
RSLogix 5000 programming software. You can specify the controller path after you’ve created the RSLogix 5000 program.
Complete these steps to specify the controller path after you have created your program.
1.
Click Who Active.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 59
Chapter 3 Start Using the Controller
2.
Expand the network path and select the controller.
Go Online with the
Controller
3.
Click Set Project Path.
To download or upload a project for the controller, you must first be online with the controller. Use one of these methods to go online with the controller.
• After setting the communication path, click Go Online in the Who Active dialog box.
60
• From the Controller Status menu, choose Go Online.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Start Using the Controller Chapter 3
Download to the Controller
Downloading a project to the controller moves the project from RSLogix 5000 software and loads it onto the controller. To download a project, use one of these methods:
• Use the Who Active Dialog Box to Download, page 61
• Use the Controller Status Menu to Download, page 62
Use the Who Active Dialog Box to Download
You can use the features of the Who Active dialog box to download to your controller after you have set the communication path. Complete these steps to download to the controller.
1.
After setting the communication path, click Download in the Who Active dialog box.
2.
Click Download after reading the warnings in the Download dialog box.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 61
Chapter 3 Start Using the Controller
Use the Controller Status Menu to Download
After you have set a communication path in the RSLogix 5000 project, you can use the Controller Status menu to download to the controller. To download, from the Controller Status menu, choose Download.
Figure 4 - Download via the Controller Status Menu
TIP After the download completes on a 1756-L7x controller, the project name is indicated on the scrolling status display.
Upload From the Controller
Uploading a project to the controller copies the project from the controller to
RSLogix 5000 software. To upload a project, use one of these methods:
• Use the Who Active Dialog Box to Upload, page 62
• Use the Controller Status Menu to Upload, page 63
Use the Who Active Dialog Box to Upload
You can use the features of the Who Active dialog box to upload from your controller after you have set the communication path. Complete these steps to upload from the controller.
1.
After setting the communication path, click Upload in the Who Active dialog box.
62 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Start Using the Controller Chapter 3
2.
Click Upload after verifying the project you are uploading in the
Connected to Upload dialog box.
Use the Controller Status Menu to Upload
After you have set a communication path in the RSLogix 5000 project, you can use the Controller Status menu to upload from the controller. To upload, from the Controller Status menu, choose Upload.
Figure 5 - Upload via the Controller Status Menu
Choose the Controller
Operation Mode
Use this table as a reference when determining your controller Operation mode.
If you want to
Turn outputs to the state commanded by the logic of the project
Select one of these modes
Run Remote
Run Test Program
X X
Program
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 63
Chapter 3 Start Using the Controller
If you want to
Turn outputs to their configured state for
Program mode
Execute (scan) tasks
Change the mode of the controller through software
Download a project
Schedule a ControlNet network
While online, edit the project
Send messages
Send and receive data in response to a message from another controller
Produce and consume tags
Select one of these modes
Run Remote
Run Test Program
X X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Program
X
X
X
X
X
X
Use the Keyswitch to Change the Operation Mode
The keyswitch on the front of the controller can be used to change the controller to one of these modes:
• Program (PROG)
• Remote (REM)
• Run (RUN)
Figure 6 - 1756-L7x Controller Operation Mode via the Controller Keyswitch
1756-L7x
Logix557x
1756-L6x
Logix556x
RUN FORCE SD OK
RU
N REM PROG
Keyswitch
64
Use RSLogix 5000 Software to Change the Operation Mode
Depending on the mode of the controller you specify by using the keyswitch, you can change the Operation mode of the controller using RSLogix 5000 software.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Start Using the Controller Chapter 3
After you are online with the controller and the controller keyswitch is set to
Remote (REM or the center position), you can use the Controller Status menu in the upper-left corner of the RSLogix 5000 software window to specify these operation modes:
• Remote Program
• Remote Run
• Remote Test
Figure 7 - Operation Mode via RSLogix 5000 Software
TIP For this example, the controller keyswitch is set to Remote mode. If your controller keyswitch is set to Run or Program modes, the menu options change.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 65
Chapter 3 Start Using the Controller
Load or Store to the
Memory Card
The memory card that is compatible with your ControlLogix controller is used to load or store the contents of user memory for the controller.
Store to the Memory Card
After you are online with the controller and have changed the controller to
Program or Remote Program mode, complete these steps to store a project to the memory card.
1.
Open the Controller Properties dialog box and click the
Nonvolatile Memory tab.
2.
Click Load/Store.
TIP If Load/Store is dimmed (unavailable), verify the following:
• You have specified the correct communication path and are online with the controller.
• The memory card is installed.
If the memory card is not installed, the missing card is indicated by a message in the lower-left corner of the Nonvolatile Memory tab as shown here.
3.
Change the Load Image, Load Mode, and Automatic Firmware Update properties according to your application requirements.
66 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Start Using the Controller Chapter 3
The table below describes the Load Image options you can choose for the project.
IMPORTANT If the SD card is locked and the stored project’s Load Image option is set to On Power Up, the controller firmware is not updated as a result of conducting a firmware upgrade. The previously-stored firmware and project are loaded instead.
Table 6 - Load Image Options
If you want the image (project) to load when
Power to the controller is applied or cycled
The controller has lost the project and power has been cycled or applied
Initiated by using RSLogix 5000 software
Then choose
On Power Up
On Corrupt Memory
User Initiated
The table below describes the Load Mode options you can choose for the project.
Table 7 - Load Mode Options
If you want the controller to go to this mode after loading
Remote Program
Run
Then choose
Program (Remote Only)
Run (Remote Only)
The table below describes the Automatic Firmware Update options you can choose for the project. The Automatic Firmware Update property is also referred to as the Firmware Supervisor feature.
Table 8 - Automatic Firmware Update Options
If you want to
Enable automatic firmware updates so devices in the configuration tree of the controller that are configured to use Exact Match Keying are updated as required
Disable automatic firmware updates and remove any I/O firmware files that are stored with the image
Disable automatic firmware updates when there are no firmware files are stored with the image
Then choose
Enable and Store Files to Image
(1)
Disable and Delete Files from Image
Disable
(1) The devices used with this option must support the version of firmware being updated to.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 67
Chapter 3 Start Using the Controller
4.
Click Store, then click OK in the confirmation dialog box that appears.
Indication that the SD card is locked.
TIP With the 1756-L7x controllers, if the SD card is locked, Store is dimmed
(unavailable) and the locked status is indicated in the bottom-left corner of the Nonvolatile Memory/Load Store dialog box as shown here.
Store dimmed (unavailable).
68 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Start Using the Controller Chapter 3
After clicking Store, the project is saved to the memory card as indicated by the controller status indicators.
Table 9 - Store Project Status Indicators
With these controllers
1756-L6x
1756-L7x
These indications show the store status
While the store is in progress, the following occurs:
• OK indicator on the controller is solid red
• A dialog box in RSLogix 5000 software indicates the store is in progress
When the store is complete, the following occurs:
• OK indicator on the controller is momentarily red, then solid green
• CF indicator on the controller is off
While the store is in progress, the following occurs:
• OK indicator is flashing green
• SD indicator is flashing green
• SAVE is shown on the status display
• A dialog box in RSLogix 5000 software indicates the store is in progress
When the store is complete, the following occurs:
• OK indicator on the controller is solid green
• SD indicator on the controller is off
IMPORTANT Allow the store to complete without interruption. If you interrupt the store, data corruption or loss may occur.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 69
Chapter 3 Start Using the Controller
Load from the Memory Card
After you have set the communication path, are online with the controller, and have changed the controller to Program mode, complete these steps to load a project to the controller from the memory card.
1.
Open the Controller Properties and click the Nonvolatile Memory tab.
2.
Click Load/Store.
70
TIP If Load/Store is dimmed (unavailable), verify the following:
• You have specified the correct communication path and are online with the controller.
• The memory card is installed.
If the SD card is not installed, the missing card is indicated by a message in the lower-left corner of the Nonvolatile Memory tab as shown here.
3.
Verify that the image in nonvolatile memory (that is, the project on the memory card) is the project you want to load.
TIP If no project is stored on the memory card, a message in the lower-left corner of the Nonvolatile Memory tab indicates that an image (or project) is not available as shown here.
TIP For information about changing the project that is available to load from nonvolatile memory, see the Logix5000 Controllers Nonvolatile Memory
Programming Manual, publication 1756-PM017 .
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
4.
Click Load.
Start Using the Controller Chapter 3
After clicking Load, the project is loaded to the controller as indicated by the controller status indicators.
Table 10 - Load Project Status Indicators
With these controllers
1756-L6x
1756-L7x
These indications show the store status
While the load is in progress, the following occurs:
• OK indicator on the controller is flashing green
• A dialog box in RSLogix 5000 software indicates the store is in progress
When the load is complete, the following occurs:
• OK indicator on the controller is momentarily red, then solid green
• CF indicator on the controller is off
While the load is in progress, the following occurs:
• OK indicator is solid red
• SD indicator is flashing green
• LOAD is shown on the status display
• UPDT may be shown on the status display if the firmware is also updating with the load
• A dialog box in RSLogix 5000 software indicates the store is in progress
When the load is complete, the following occurs:
• OK indicator on the controller is solid green
• SD indicator on the controller is off
IMPORTANT Allow the load to complete without interruption. If you interrupt the load, data corruption or loss may occur.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 71
Chapter 3 Start Using the Controller
Other Memory Card Tasks
Other tasks that you may need to complete by using the memory cards of the controller include the following:
• Changing the image that is loaded from the card
• Checking for a load that was completed
• Clearing an image from the memory card
• Storing an empty image
• Changing load parameters.
• Reading/writing application data to the card
For more information about completing any of these tasks, see the Logix5000
Controllers Memory Card Programming Manual, publication 1756-PM017 .
Use ControlLogix Energy
Storage Modules (ESMs)
You can use the ControlLogix ESMs to execute either of the following tasks:
• Provide power to 1756-L7x controllers to save the program to the controller’s on-board nonvolatile storage (NVS) memory after power is removed from the chassis or the controller is removed from a powered chassis.
IMPORTANT When you are using an ESM to save the program to on-board NVS memory, you are not saving the program to the SD card installed in the controller.
• Clear the program from the 1756-L7x controller’s on-board NVS memory.
For more information, see Clear the Program from On-board NVS
The following table describes the ESMs.
Cat. No.
1756-ESMCAP
1756-ESMNSE
1756-ESMNRM
Description
Capacitor-based ESM
The 1756-L7x controllers come with this ESM installed.
Capacitor-based ESM without WallClockTime back-up power
Use this ESM if your application requires that the installed ESM deplete its residual stored energy to 200
joules or less before transporting it into or out of your application. Additionally, you can use this ESM with a 1756-L73 (8MB) or smaller memory-sized controller only.
Secure capacitor-based ESM (non-removable)
This ESM provides your application an enhanced degree of security by preventing physical access to the USB connector and the SD card.
72 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Start Using the Controller Chapter 3
Save the Program to On-board NVS Memory
Follow these steps to save the program to NVS memory when the controller loses power.
1.
Remove power from the controller.
You can remove power in either of two ways:
• Turn power off to the chassis while the controller is installed in the chassis.
• Remove the controller from a powered chassis.
Immediately after the controller is no longer powered, the program starts saving while the OK status indicator is green (this green is a dimmer green than normal operation), then turns red after program save is complete.
Once the ESM stops operating, it turns off.
The following graphic shows the controller’s OK status indicator.
Logix557x
RUN FORCE SD OK
RU
N REM PRO
G
2.
Leave the ESM on the controller until the OK status indicator is OFF.
3.
If necessary, remove the ESM from the controller after the OK status indicator transitions from Solid Red to Off.
Clear the Program from On-board NVS Memory
If your application allows it, follow these steps to clear the program from the
1756-L7 x controller’s on-board NVS memory.
1.
Remove the ESM from the controller.
2.
Remove power from the controller.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 73
Chapter 3 Start Using the Controller
You can remove power in either of the following two ways:
• Turn power off to the chassis while the controller is installed in the chassis.
• Remove the controller from a powered chassis.
3.
Reinstall the ESM into the controller.
4.
Restore power to the controller and Restore in one of these two ways:
• If the controller is already installed in the chassis, turn power back onto the chassis.
• If the controller is not installed into the chassis, reinstall the controller into the chassis and turn power back onto the chassis.
Estimate the ESM Support of the WallClockTime
The ESM provides support for the maintenance of the WallClockTime attribute of the controller when power is not applied. Use this table to estimate the hold-up time of the ESM based on the temperature of the controller and installed ESM.
Temperature
20
C (68
F)
40 °C (104
F)
60
C (140
F)
10
7
1756-ESMCAP
Hold-up Time (in days)
1756-ESMNRM 1756-ESMNSE
12 12 0
10
7
0
0
Maintain the Battery
(1756-L6x controllers only)
This explains how to monitor and maintain the lithium batteries supported by
ControlLogix controllers.
Table 11 - 1756-L6x Controllers and Compatible Batteries
Cat. No.
1756-L61
1756-L62
1756-L63
1756-L61
1756-L62
1756-L63
1756-L64
1756-L65
1756-L63XT
Series
A
B
B
Compatible Battery
1756-BA1 or
1756-BATA or
1756-BATM
1756-BA2
74 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Start Using the Controller Chapter 3
Check the Battery Status
When the battery is approximately 95% discharged, these low-battery warnings are indicated:
• The BAT is solid red.
• A minor fault (type 10, code 10) is logged.
ATTENTION: To prevent possible battery leakage, even if the BAT status indicator is off, replace a battery according to this schedule.
If the temperature 2.54 cm (1 in.) below the chassis is
-25…35
C (-13…95 F)
36…40
C (96.8…104 F)
41…45
C (105.8…113F)
46…50
C (114.8…122 F)
51…55
C (123.8…131 F)
56…70
C (132.8…158F)
Replace the battery within
No replacement required
3 years
2 years
16 months
11 months
8 months
1756-BA1 or 1756-BATA Battery Life
To estimate how long a 1756-BA1 or 1756-BATA battery will support controller memory on 1756-L6 x, series A controllers, perform this procedure.
1.
Determine the temperature 2.54 cm. (1 in.) below the chassis.
2.
Determine the weekly percentage of time that the controller is turned on.
EXAMPLE If a controller is off either one of these times:
• 8 hr/day during a 5-day work week
• All day Saturday and Sunday
Then the controller is off 52% of the time:
• Total hours per week = 7 x 24 = 168 hrs
• Total off hours per week = (5 days x 8 hr/day) + Saturday + Sunday =
88 hrs
• Percentage off time = 88/168 = 52%
3.
Determine the estimated worst-case battery life before and after the BAT status indicator turns on.
4.
For each year of battery life, decrease the time before the BAT status indicator turns on by the percentage that is shown in the table.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 75
Chapter 3 Start Using the Controller
Do not decrease the time after the BAT status indicator turns on.
IMPORTANT If the BAT status indicator turns on when you apply power to the controller, the remaining battery life may be less than this table indicates. Some of the battery life may have been used up while the controller was off and unable to turn on the BAT status indicator.
Table 12 - Worst-case Estimates of 1756-BA1 Battery Life
Temperature
60 °C (140 °F)
25 °C (77 °F)
0 °C (32 °F)
Battery Life Before BAT Status Indicator Turns On
Power Off 100% Power Off 50% Yearly Decrease
22 days
21 days
14 days
43 days
42 days
28 days
23%
17%
17%
Battery Life After BAT Status Indicator
Turns On and Power is Cut Off
6 hrs
28 hrs
2.5 days
Table 13 - Worst-case Estimates of 1756-BATA Battery Life
Temperature
60 °C (140 °F)
25 °C (77 °F)
0 °C (32 °F)
Battery Life Before BAT Status Indicator Turns On
Power Off 100% Power Off 50% Yearly Decrease
98 days
146 days
105 days
204 days
268 days
222 days
11%
5%
6%
Battery Life After BAT Status Indicator
Turns On and Power is Cut Off
104 days
157 days
113 days
1756-BATM Battery Module and Battery Life
Use the 1756-BATM battery module with any 1756-L6 x, series A controller. The battery module is highly recommended for the higher-memory controllers.
If your project is
Stored in nonvolatile memory via 1784-CF64
Industrial CompactFlash card
Not stored in nonvolatile memory
Then use of the 1756-BATM battery module is
Not required, but permitted
Highly recommended
When the 1756-BATA battery within the 1756-BATM module is approximately
50% discharged, these low-battery warnings are indicated:
• The BAT is solid red.
• A minor fault (type 10, code 10) is logged.
76 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Start Using the Controller Chapter 3
Estimate 1756-BA2 Battery Life
The 1756-BA2 batteries are for use in 1756-L6 x controllers, series B. Use this table to estimate how much time will elapse before the battery becomes low.
Table 14 - Worst-case Estimates of 1756-BA2 Life According to Temperatures and Power Cycles
Temperature 2.54 cm (1 in.)
Below the Chassis, Max
-25…35 °C (-13…95 °F)
41...45 °C (105.8...113 °F)
46...50 °C (105.8...113 °F)
51...55 °C (123.8...131 °F)
56…70 °C (132.8…158 °F)
Power Cycles
3 per day
2 per day or less
3 per day
2 per day or less
3 per day or less
3 per day or less
3 per day or less
Battery Life Before the BAT Status Indicator Turns Red
Project Size
1 MB
3 years
2 MB
3 years
4 MB
26 months
8 MB
20 months
3 years
2 years
2 years
16 months
11 months
8 months
3 years
2 years
2 years
16 months
11 months
8 months
3 years
2 years
2 years
16 months
11 months
8 months
31 months
20 months
2 years
16 months
11 months
8 months
16 MB
10 months
16 months
10 months
16 months
10 months
10 months
8 months
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 77
Chapter 3 Start Using the Controller
Estimate 1756-BA2 Battery Life After Warnings
Use this table to estimate the battery life after the low-battery warnings are indicated. Use these times even if the controller does not have power because there is always a small power-drain on the battery.
IMPORTANT When you power up the controller, see if there is a low-battery warning. If you get a low-battery warning for the first time, you have less battery life than this table shows. While powered down, the controller still drains the battery but it cannot give the low-battery warning.
Temperature 2.54 cm
(1 in.) Below the Chassis,
Max
Power Cycles
0...20 °C (32...68 °F)
21...40 °C (69.8...104 °F)
41...45 °C (105.8...113 °F)
46...50 °C (105.8...113 °F)
51...55 °C (123.8...131 °F)
56...60 °C (132.8...140 °F)
3 per day
1 per day
1 per month
3 per day
1 per day
1 per month
3 per day
1 per day
1 per month
3 per day
1 per day
1 per month
3 per day
1 per day
1 per month
3 per day
1 per day
1 per month
26 weeks
12 weeks
15 weeks
17 weeks
10 weeks
12 weeks
12 weeks
7 weeks
Battery Life After the BAT Status Indicator Turns Red (worst case)
Project Size
1 MB
26 weeks
2 MB
18 weeks
4 MB
12 weeks
8 MB
9 weeks
26 weeks
26 weeks
18 weeks
24 weeks
26 weeks
26 weeks
14 weeks
21 weeks
26 weeks
26 weeks
10 weeks
18 weeks
22 weeks
26 weeks
8 weeks
16 weeks
8 weeks
8 weeks
5 weeks
6 weeks
6 weeks
26 weeks
10 weeks
14 weeks
17 weeks
8 weeks
11 weeks
12 weeks
6 weeks
8 weeks
8 weeks
5 weeks
6 weeks
6 weeks
26 weeks
7 weeks
12 weeks
17 weeks
6 weeks
10 weeks
12 weeks
5 weeks
7 weeks
8 weeks
4 weeks
5 weeks
6 weeks
26 weeks
6 weeks
11 weeks
17 weeks
6 weeks
9 weeks
12 weeks
4 weeks
7 weeks
8 weeks
4 weeks
5 weeks
6 weeks
EXAMPLE Under these conditions, the battery will last at least 20 months before the BAT status indicator turns red:
• The maximum temperature 2.54 cm (1 in.) below the chassis =
45 °C (113 °F).
• You cycle power to the controller three times per day.
• The controller contains an 8 MB project.
8 weeks
16 weeks
3 weeks
7 weeks
12 weeks
3 weeks
5 weeks
8 weeks
16 MB
5 weeks
13 weeks
26 weeks
5 weeks
11 weeks
26 weeks
4 weeks
2 weeks
4 weeks
6 weeks
78 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Start Using the Controller Chapter 3
Battery Storage and Disposal
Follow these general rules to store your batteries:
•
Store batteries in a cool, dry environment. We recommend
25 °C (77 °F) with 40…60% relative humidity.
•
You may store batteries for up to 30 days in temperatures from
-45...85 °C (-49...185 °F), such as during transportation.
•
To avoid leakage or other hazards, do not store batteries above
60 °C (140 °F) for more than 30 days.
This product contains a sealed lithium battery that may need to be replaced during the life of the product.
At the end of its life, the battery contained in this product should be collected separately from any unsorted municipal waste.
The collection and recycling of batteries helps protect the environment and contributes to the conservation of natural resources as valuable materials are recovered.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 79
Chapter 3 Start Using the Controller
Additional Resources
These documents contain additional information concerning related Rockwell
Automation products.
Resource
Logix5000 Controllers Common Procedures Programming Manual, publication 1756-PM001
Logix5000 Controllers Nonvolatile Memory Programming Manual, publication 1756-PM017
Guidelines for Handling Lithium Batteries, publication AG-5.4
Programmable Controllers Battery Reference, http://www.ab.com/programmablecontrol/batteries.html
Description
Provides links to programming manuals that explain common programming procedures.
Explains various procedures related to the use of memory cards.
Provides information regarding storage, handling, transportation, and disposal of lithium batteries.
Provides Material Safety Data Sheets (MSDS) for individual replacement batteries.
You can view or download publications at http://www.rockwellautomation.com/literature . To order paper copies of technical documentation, contact your local Rockwell Automation distributor or sales representative.
80 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Chapter
4
ControlLogix System and Controllers
Topic
ControlLogix Controller Features
Page
The ControlLogix System
The ControlLogix system is chassis-based and provides the option to configure a control system that uses sequential, process, motion, and drive control in addition to communication and I/O capabilities.
Configuration Options
This section describes some of the many system configuration options that are available with ControlLogix controllers.
Standalone Controller and I/O
One of the simplest ControlLogix configurations is a standalone controller with
I/O assembled in one chassis.
Figure 8 - Standalone Controller and I/O
32044-MC
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 81
Chapter 4 ControlLogix System and Controllers
Multiple Controllers in One Chassis
For some applications, multiple controllers may be used in one ControlLogix chassis. For example, for better performance, multiple controllers can be used in motion applications.
Figure 9 - Multiple Controllers in One Chassis
Ethernet
FactoryTalk Server
Motor
Stratix 8000 Switch
Kinetix 6500 Drive
Kinetix 6500 Drive
Kinetix 6500 Drive
Motor
Motor
32045-MC
82 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
ControlLogix System and Controllers Chapter 4
Multiple Devices Connected via Multiple Networks
For some applications, a variety of devices may be connected to the ControlLogix chassis via multiple communication networks. For example, a system might be connected to the following:
• Distributed I/O via an Ethernet network
• A PowerFlex drive connected via a DeviceNet network
• Flowmeters connected via HART connection
Figure 10 - Multiple Devices Connected via Multiple Networks
HART
PowerFlex Drive
DeviceNet
FLEX I/O
Ethernet Device-level
Ring Network
POINT I/O
HART
FactoryTalk Server
Endress + Hauser
Flowmeters
32046-MC
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 83
Chapter 4 ControlLogix System and Controllers
Design a ControlLogix
System
When you design a ControlLogix system, there are several system components to consider for your application. Some of these components include all of the following:
• I/O devices
• Motion control and drive requirements
• Communication modules
• Controllers
• Chassis
• Power supplies
• Software
For more information about designing and selecting components for your
ControlLogix system, see the ControlLogix Selection Guide, publication
1756-SG001 .
In addition, if you are designing your ControlLogix System for any of the specific applications listed in this table, see the appropriate resources for more information.
For this type of application
Motion with Integrated Motion on the
EtherNet/IP network
Motion with the use of a coordinate system
Redundancy by using 1757-SRM modules. Also called standard redundancy
SIL2
See this publication
CIP Motion Configuration and Startup User Manual, publication MOTION-UM003
Motion Coordinated Systems User Manual, publication
MOTION-UM002
Motion with Sercos or analog motion SERCOS Motion Configuration and Startup User Manual, publication MOTION-UM001
Redundancy by using 1756-RM or
1756-RMXT modules. Also called enhanced redundancy
ControlLogix Enhanced Redundancy System User Manual, publication 1756-UM535
ControlLogix Redundancy System User Manual, publication
1756-UM523
SIL2 fault-tolerant I/O with
RSLogix 5000 subroutines
SIL2 fault-tolerant I/O with
RSLogix 5000 Add-On Instructions
Using ControlLogix in SIL2 Applications Safety Reference
Manual, publication 1756-RM001
ControlLogix SIL2 System Configuration Using RSLogix 5000
Subroutines Application Technique, publication 1756-AT010
ControlLogix SIL2 System Configuration Using SIL2 Add-On
Instructions Application Technique, publication 1756-AT012
84 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
ControlLogix Controller
Features
ControlLogix System and Controllers Chapter 4
The ControlLogix controllers are part of the Logix5000 family of controllers offered by Rockwell Automation. The sections that follow describe the differentiating features of the ControlLogix controllers.
System, Communication, and Programming Features
This table lists the system, communication, and programming features available with ControlLogix controllers.
Table 15 - ControlLogix Controller Features
Feature
Controller tasks
Built-in communication ports
Communication options
Serial port communication
1756-L61, 1756-L62, 1756-L63,
1756-L64, 1756-L65
• 32 tasks
• 100 programs/task
• Event tasks: all event triggers
1 port - RS-232 serial
1756-L72, 1756-L73,
1756-L74, 1756-L75
1 port - USB, 2.0 full-speed, Type B
• EtherNet/IP
• ControlNet
• DeviceNet
• Data Highway Plus
• Remote I/O
• SynchLink
• Third-party process and device networks
N/A • ASCII
• DF1 full/half-duplex
• DF1 radio modem
• DH-485
• Modbus via logic
Controller connections supported, max
Network connections, per network module
250
• 100 ControlNet (1756-CN2/A)
• 40 ControlNet (1756-CNB)
500
• 256 EtherNet/IP; 128 TCP (1756-EN2x)
• 128 EtherNet/IP; 64 TCP (1756-ENBT)
Controller redundancy Full support except for motion applications
Integrated motion
Programming languages
• Integrated Motion on the EtherNet/IP network
• SERCOS interface
• Analog options:
- Encoder input
- LDT input
- SSI input
• Relay ladder
• Structured text
• Function block
• Sequential Function Chart (SFC)
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 85
Chapter 4 ControlLogix System and Controllers
Memory Options
The ControlLogix controller is available in different combinations of user memory. Use this table to determine which controller meets your memory requirements.
Table 16 - ControlLogix Controller Memory Options
Controller
1756-L61
1756-L62
1756-L63,
1756-L63XT
1756-L64
1756-L65
1756-L72
1756-L73
1756-L74
1756-L75
Memory for Data and Logic
2 MB
4 MB
8 MB
16 MB
32 MB
4 MB
8 MB
16 MB
32 MB
I/O
478 KB
0.98 MB (1006 KB)
Back-up Memory
CompactFlash card
SD card
(1) These nonvolatile memory cards are optional and do not come with the controller.
(1)
IMPORTANT The 1756-L7x controllers ship with an SD card installed. We recommend that you leave the SD card installed because, if a fault occurs, diagnostic data is automatically written to the card and can be used by Rockwell
Automation to troubleshoot the anomaly.
IMPORTANT We recommend that you use the SD cards available from
Rockwell Automation (catalog numbers 1784-SD1 or 1784-SD2).
While other SD cards may be used with the controller,
Rockwell Automation has not tested the use of those cards with the controller. If you use an SD card other than those available from
Rockwell Automation, you may experience data corruption or loss.
Also, SD cards not provided by Rockwell Automation do not have the same industrial, environmental, and certification ratings as those available from Rockwell Automation.
86 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Logix557x
RUN FORCE SD OK
1756-L7x
ControlLogix System and Controllers Chapter 4
Controller Central-processing Unit (CPU) Resources
The ControlLogix controller divides processing resources between multiple
CPUs. With the 1756-L7 x controller, a dual-core CPU and backplane CPU are used to provide increased performance. With the 1756-L6 x controller, a single-core Logix CPU and a backplane CPU are used.
Figure 11 - 1756-L7x and 1756-L6x CPU Illustration
1756-L6x
Logix556x
Backplane
CPU
Backplane
CPU
I/O Data I/O Data
Logix CPU
Core
1
Core
2
Logix CPU
For both 1756-L6 x and 1756-L7x controllers, the Logix CPU executes application code and messages. The Logix CPU is responsible for logic and data memory, including the following:
• Program source code
• Tag data
• External communication (for example, FactoryTalk Live Data)
The backplane CPU communicates with I/O and sends and receives data from the backplane. This CPU operates independently from the Logix CPU, so it sends and receives I/O information asynchronous to program execution. The backplane CPU is responsible for I/O memory, including the following:
• I/O data
• I/O force tables
• Message buffers
• Produced/consumed tags
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 87
Chapter 4 ControlLogix System and Controllers
Additional Resources
These documents contain additional information specific to the ControlLogix system design and selection.
Resource
ControlLogix Selection Guide, publication 1756-SG001
SERCOS Motion Configuration and Startup User Manual, publication
MOTION-UM001
Motion Coordinated Systems User Manual, publication MOTION-UM002
CIP Motion Configuration and Startup User Manual, publication
MOTION-UM003
ControlLogix Enhanced Redundancy System User Manual, publication
1756-UM535
Description
Provides methods for determining what ControlLogix components are required for your system.
Explains the configuration of Sercos and analog motion applications.
Explains the configuration of coordinated motion applications.
Explains the configuration of Integrated Motion on the EtherNet/IP network.
Explains the design and configuration of enhanced redundancy systems.
ControlLogix Redundancy System User Manual, publication 1756-UM523 Explains the design and configuration of standard redundancy systems.
Using ControlLogix in SIL2 Applications Safety Reference Manual, publication 1756-RM001
Lists components for use in SIL2 applications and provides general configuration and application requirements.
ControlLogix SIL2 System Configuration Using RSLogix 5000 Subroutines
Application Technique, publication 1756-AT010
ControlLogix SIL2 System Configuration Using SIL2 Add-On Instructions
Application Technique, publication 1756-AT012
Explains the configuration of SIL2-certified fault-tolerant systems that are configured by using RSLogix 5000 subroutines.
Explains the configuration of SIL2-certified fault-tolerant systems that are configured by using RSLogix 5000 Add-On Instructions.
You can view or download publications at http://www.rockwellautomation.com/literature . To order paper copies of technical documentation, contact your local Rockwell Automation distributor or sales representative.
88 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Networks Available
Chapter
5
Communication Networks
Topic
EtherNet/IP Network Communication
ControlNet Network Communication
DeviceNet Network Communication
Data Highway Plus (DH+) Network Communication
Universal Remote I/O (RIO) Communication
Foundation Fieldbus Communication
Page
Several communication networks are available for use with ControlLogix systems. This table describes typical network applications used with
ControlLogix systems and lists the networks available to support such applications.
Table 17 - Applications and Supported Networks
Application Type Supported Networks
Integrated Motion on the EtherNet/IP network EtherNet/IP
CIP sync for time synchronization
Control of distributed I/O
Produce/consume (interlock) data between controllers
Messaging to and from other devices, including access to the controller via RSLogix 5000 software
EtherNet/IP
• ControlNet
• DeviceNet
• EtherNet/IP
• Foundation Fieldbus
• HART
• Universal remote I/O
• ControlNet
• EtherNet/IP
• EtherNet/ControlNet
• DeviceNet (only to devices)
• Data Highway Plus (DH+)
• DH-485
• EtherNet/IP
• Serial
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 89
Chapter 5 Communication Networks
EtherNet/IP Network
Communication
The EtherNet/IP network offers a full suite of control, configuration, and data collection services by layering the Common Industrial Protocol (CIP) over the standard Internet protocols, such as TCP/IP and UDP. This combination of well-accepted standards provides the capability required to both support information data exchange and control applications.
The EtherNet/IP network uses commercial, off-the-shelf Ethernet components and physical media, providing you with a cost-effective plant-floor solution.
Figure 12 - EtherNet/IP Network Example
FlexLogix Controller with
1788-ENBT Module
Distributed I/O
LINK NET OK
ControlLogix
Controller with
1756-ENBT
Module
LINK NET OK
1756-ENBT Module
(as an adapter) with 1756
I/O Modules
CompactLogix Controller with Integrated
EtherNet/IP Port
90
Switch
1794-AENT Adapter with
1794 I/O Modules
1734-AENT Adapter with
1734 I/O Modules
PowerFlex 700S AC
Drive with DriveLogix
Software
Workstation
For more information about using EtherNet/IP modules, see the EtherNet/IP
Modules in Logix5000 Control Systems User Manual, publication
ENET-UM001 .
ControlLogix EtherNet/IP Module Features
The ControlLogix EtherNet/IP communication modules provide these features:
• Support for messaging, produced/consumed tags, HMI, and distributed
I/O
• The ability to encapsulate messages within the standard TCP/UDP/IP protocol
• A common application layer with ControlNet and DeviceNet networks.
• Network connections via an RJ45 cable
• Support half/full duplex 10 MB or 100 MB operation
• Support standard switches
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Communication Networks Chapter 5
ControlLogix EtherNet/IP Communication Modules
For EtherNet/IP network communication in a ControlLogix system, you have several modules to choose from. This table lists modules and their primary features.
Table 18 - EtherNet/IP Communication Modules and Capabilities
Module
1756-ENBT
1756-EN2F
1756-EN2T
1756-EN2TR
1756-EN3TR
1756-EN2TXT
1756-EWEB
Is used to
• Connect controllers to I/O modules (requires an adapter for distributed I/O).
• Communicate with other EtherNet/IP devices (messages).
• Serve as a pathway for data sharing between Logix5000 controllers
(produce/consume).
• Bridge EtherNet/IP nodes to route messages to devices on other networks.
• Perform the same functions as a 1756-EN2T module.
• Connect fiber media by an LC fiber connector on the module.
• Perform the same functions as a 1756-ENBT module, with twice the capacity for more demanding applications.
• Provide a temporary configuration connection via the USB port.
• Configure IP addresses quickly by using rotary switches.
• Perform the same functions as a 1756-EN2T module.
• Support communication on a ring topology for a Device Level Ring (DLR) single-fault tolerant ring network.
• Perform the same functions as the 1756-EN2TR module.
• Three ports for DLR connection.
• Perform the same functions as a 1756-EN2T module.
• Operate in extreme environments with -25…70 °C (-13…158 °F) temperatures.
• Provide customizable web pages for external access to controller information.
• Provide remote access via an Internet browser to tags in a local
ControlLogix controller.
• Communicate with other EtherNet/IP devices (messages).
• Bridge EtherNet/IP nodes to route messages to devices on other networks.
• Support Ethernet devices that are not EtherNet/IP-based with a socket interface.
This module does not provide support for I/O or produced/consumed tags.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 91
Chapter 5 Communication Networks
ControlNet Network
Communication
Software for EtherNet/IP Networks
This table lists software that is used with the EtherNet/IP networks and modules.
Table 19 - Software for Use with EtherNet/IP Networks
Software
RSLogix 5000
RSLinx Classic or RSLinx
Enterprise
RSLogix 5000
BOOTP/DHCP Utility
RSNetWorx for
EtherNet/IP
Is used to
• Configure ControlLogix projects.
• Define EtherNet/IP communication.
• Configure communication devices.
• Provide diagnostics.
• Establish communication between devices.
Assign IP addresses to devices on an EtherNet/IP network.
• Configure EtherNet/IP devices by IP addresses and/or host names.
• Provide bandwidth status.
Required/Optional
Required
Required
Optional
Connections Over an EtherNet/IP Network
You indirectly determine the number of connections the controller uses by configuring the controller to communicate with other devices in the system.
Connections are allocations of resources that provide more reliable communication between devices compared to unconnected messages.
All EtherNet/IP connections are unscheduled. An unscheduled connection is triggered by the requested packet interval (RPI) for I/O control or the program, such as a MSG instruction. Unscheduled messaging lets you send and receive data when needed.
EtherNet/IP Module Connections
The 1756 EtherNet/IP communication modules support 128 CIP (Common
Industrial Protocol) connections over an EtherNet/IP network.
The ControlNet network is a real-time control network that provides high-speed transport of both time-critical I/O and interlocking data and messaging data.
This includes uploading and downloading of program 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.
The ControlNet network is highly deterministic and repeatable and is unaffected when devices are connected or disconnected from the network. This quality results in dependable, synchronized, and coordinated real-time performance.
92 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Communication Networks Chapter 5
CompactLogix Controller
The ControlNet network often functions as the following:
• A substitute/replacement for the remote I/O (RIO) network because the
ControlNet network adeptly handles large numbers of I/O points
• A backbone for multiple distributed DeviceNet networks
• A peer interlocking network
Figure 13 - ControlNet Network Overview
Workstation
Distributed I/O
PowerFlex 700S AC Drive with DriveLogix Software
1756-CNB Module
(as an adapter) with
1756 I/O Modules
ControlNet Network
1756-CNB Module Acting as Scanner
PanelView Terminal
1794-ACN15 Adapter with 1794 I/O Modules
1734-ACNR Adapter with
1734 I/O Modules
PLC-5/40C15 Controller
In this example, these actions occur via the ControlNet network:
• The controllers produce and consume tags.
• The controllers initiate MSG instructions that do the following:
– Send and receive data.
– Configure devices.
• The workstation is used to do the following:
– Configure both the ControlNet devices and the ControlNet network.
– Download and upload projects from the controllers.
For more information about using ControlNet modules, see ControlNet
Modules in Logix5000 Control Systems User Manual, publication
CNET-UM001 .
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 93
Chapter 5 Communication Networks
ControlLogix ControlNet Module Features
The ControlNet communication modules provide these features:
• Support for messaging, produced/consumed tags, and distributed I/O
• Use a common application layer with DeviceNet and EtherNet/IP networks
• Requires no routing tables
• Support the use of coax and fiber repeaters for isolation and increased distance
• Support redundant media (1756-CNBR, 1756-CN2R, and
1756-CN2RXT modules only)
ControlLogix ControlNet Modules
This table lists the available ControlLogix ControlNet modules and their primary features.
Table 20 - ControlNet Modules and Capabilities
Module
1756-CNB
1756-CNBR
1756-CN2
1756-CN2R
1756-CN2RXT
Is used to
• Control I/O modules.
• Communicate with other ControlNet devices (messages).
• Share data with other Logix5000 controllers (produce/consume).
• Bridge ControlNet links to route messages to devices on other networks.
• Perform the same functions as a 1756-CNB module.
• Support redundant ControlNet media.
• Perform the same functions as a 1756-CNB module.
• Provide high-speed I/O bridge functionality for applications that require higher performance.
• Perform the same functions as a 1756-CN2 module.
• Support redundant ControlNet media.
• Perform same functions as a 1756-CN2R module.
• Operate in extreme environments with -25…70 °C (-13…158 °F) temperatures.
94 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Communication Networks Chapter 5
Software for ControlNet Networks
This table lists software that is used with the ControlNet networks and modules.
Table 21 - Software for Use with ControlNet Networks
Software Is used to
RSLogix 5000 • Configure ControlLogix projects.
• Define ControlNet communication.
RSNetWorx for
ControlNet
RSLinx Classic or Enterprise
• Configure ControlNet devices.
• Schedule a network.
• Configure communication devices.
• Provide diagnostics.
• Establish communication between devices.
Required/Optional
Required
Connections Over a ControlNet Network
You indirectly determine the number of connections the controller uses by configuring the controller to communicate with other devices in the system.
Connections are allocations of resources that provide more reliable communication between devices compared to unconnected messages.
Table 22 - ControlNet Connections
Connection Definition
Scheduled
(unique to a
ControlNet network)
A scheduled connection is unique to ControlNet communication. A scheduled connection lets you send and receive data repeatedly at a predetermined interval, which is the requested packet interval (RPI). For example, a connection to an I/O module is a scheduled connection because you repeatedly receive data from the module at a specified interval.
Other scheduled connections include connections to the following:
• Communication devices
• Produced/consumed tags
On a ControlNet network, you must use RSNetWorx for ControlNet software to enable all scheduled connections and establish a network update time (NUT).
Scheduling a connection reserves network bandwidth specifically to handle the connection.
Unscheduled An unscheduled connection is a message transfer between devices that is triggered by the requested packet interval (RPI) or the program, such as a MSG instruction. Unscheduled messaging lets you send and receive data when you need to.
Unscheduled connections use the remainder of network bandwidth after scheduled connections are allocated.
ControlNet Module Connections
The 1756-CNB and 1756-CNBR communication modules support 64 CIP connections over a ControlNet network. However, for optimal performance, configure a maximum of 48 connections for each module.
The 1756-CN2, 1756-CN2R, and 1756-CN2RXT communication modules support 128 connections over a ControlNet network, all of which can be configured without risk of performance degradation.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 95
Chapter 5 Communication Networks
DeviceNet Network
Communication
96
Personal Computer
The DeviceNet network uses the Common Industrial Protocol (CIP) to provide the control, configuration, and data collection capabilities for industrial devices.
The DeviceNet network uses the proven Controller Area Network (CAN) technology, which lowers installation costs and decreases installation time and costly downtime.
A DeviceNet network provides access to the intelligence present in your devices by letting you connect devices directly to plant-floor controllers without having to hard wire each device into an I/O module.
With a ControlLogix system, DeviceNet communication requires the use of a
1756-DNB DeviceNet communication module.
Table 23 - ControlLogix DeviceNet Network Overview
ControlLogix Controller with 1756-ENBT Module
EtherNet/IP Network
FLEX I/O Adapter and Modules
1788-EN2DN
DeviceNet Network
CompactLogix Controller
Motor
Starter
PWR
STS
STS
PWR
Sensor
Pushbutton
Cluster
PORT
PORT MOD
MOD NET A
NET A NET B
NET B
Input/output
Devices
PowerFlex
AC Drive
Indicator
Lights
Bar Code
Scanner
In this example, the ControlLogix controller is connected to the DeviceNet network and devices via the 1788-EN2DN linking device.
For more information about using DeviceNet modules and devices, see
DeviceNet Modules in Logix5000 Control Systems User Manual, publication
DNET-UM004 .
ControlLogix DeviceNet Module Features
The DeviceNet communication module provides these features:
• Supports messaging to devices (not controller to controller)
• Shares a common application layer with ControlNet and EtherNet/IP networks
• Offers diagnostics for improved data collection and fault detection
• Requires less wiring than traditional, hard-wired systems
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Communication Networks Chapter 5
ControlLogix DeviceNet Bridge Module and Linking Devices
This table lists the available ControlLogix DeviceNet bridge module and linking devices that can be used with the DeviceNet network.
Table 24 - DeviceNet Communication Modules and Capabilities
Module/Device
1756-DNB
1788-EN2DN
1788-CN2DN
Is used to
• Control I/O modules.
• Communicate with other DeviceNet devices (via messages).
Link an EtherNet/IP network to a DeviceNet network.
Link a ControlNet network to a DeviceNet network.
Software for DeviceNet Networks
This table lists software that is used with the DeviceNet networks and modules.
Table 25 - Software for Use with DeviceNet Networks
Software
RSLogix 5000
RSNetWorx for
DeviceNet
RSLinx Classic or
Enterprise
Is used to
• Configure ControlLogix projects.
• Define DeviceNet communication.
• Configure DeviceNet devices.
• Define the scan list for those devices.
• Configure communication devices.
• Provide diagnostics.
• Establish communication between devices.
Required/Optional
Required
Connections Over DeviceNet Networks
The ControlLogix controller requires two connections for each 1756-DNB module. One connection is for module status and configuration. The other connection is a rack-optimized connection for the device data.
ControlLogix DeviceNet Module Memory
The 1756-DNB module has fixed sections of memory for the input and output data of the DeviceNet devices on the network. Each device on your network requires either some input or output memory of the scanner. Some devices both send and receive data, so they need both input and output memory. The
1756-DNB module supports up to add the following:
• 124 DINTs of input data
• 123 DINTs of output data
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 97
Chapter 5 Communication Networks
Data Highway Plus (DH+)
Network Communication
For DH+ network communication, use a 1756-DHRIO module in the
ControlLogix chassis to exchange information between these controllers:
• PLC and SLC controllers
• ControlLogix controllers and PLC or SLC controllers
• ControlLogix controllers
In addition to data exchange between controllers, the DH+ network also provides the ability to regularly share data both plant-wide and at a cellular level.
You can connect a maximum of 32 stations to a single DH+ link:
• Channel A supports 57.6 Kbps, 115.2 Kbps, and 230.4 Kbps.
• Channel B supports 57.6 Kbps and 115.2 Kbps.
Figure 14 - ControlLogix DH+ Network Communication Example
Data Collection and
Recipe Management
Workstation
EtherNet/IP Network
DH+ Network
ControlLogix
Controller
ControlLogix
Controller
DH+ Network
98
PLC-5 Controller SLC 500 Controller RSView Station PLC-5 Controller SLC 500 Controller RSView Station
Communicate Over a DH+ Network
For the controller to communicate to a workstation or other device over a DH+ network, use RSLinx Classic software to do the following:
• Specify a unique link ID for each ControlLogix backplane and additional network in the communication path.
• Configure the routing table for the 1756-DHRIO module.
The 1756-DHRIO module can route a message through up to four communication networks and three chassis. This limit applies only to the routing of a message and not to the total number of networks or chassis in a system.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Communication Networks Chapter 5
For more information about configuring and using a DH+ network via the
1756-DHRIO module, see the Data Highway Plus-Remote I/O
Communication Interface Module User Manual, publication 1756-UM514 .
Universal Remote I/O (RIO)
Communication
For universal remote I/O communication, you have two module options for use in the ControlLogix chassis. This table lists the RIO modules and capabilities.
Table 26 - RIO Modules and Capabilities
RIO Module
1756-RIO
1756-DHRIO
Is used to
• Function as an RIO scanner and adapter.
• Support connections to 32 racks in any combination of rack size or block transfers.
• Update data to the ControlLogix controller by using scheduled connections.
• Function as an RIO scanner.
• Support either 32 logical rack connections or 16 block-transfer connections per channel.
• Establish connections between controllers and I/O adapters.
• Distribute control so that each controller has its own I/O.
When a channel on the 1756-DHRIO module is configured for remote I/O, the module acts as a scanner for a universal remote I/O network. The controller communicates to the module to send and receive the I/O data on the universal remote I/O network.
The 1756-RIO module can act as a scanner or adapter on a remote I/O network.
In addition to digital and block-transfer data, the 1756-RIO module transfers analog and specialty data without message instructions.
Figure 15 - ControlLogix Universal Remote I/O Communication Example
ControlLogix Controller
1771-ASB and I/O Modules
1746-ASB and I/O Modules
Universal Remote I/O Network
PLC-5 Controller in Adapter Mode
1794-ASB and I/O Modules
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 99
Chapter 5 Communication Networks
Communicate Over a Universal Remote I/O Network
For the controller to control I/O over a universal remote I/O network, you must complete these tasks.
1.
Configure the remote I/O adapter.
2.
Lay out the remote I/O network cable.
3.
Connect the remote I/O network cable.
4.
Configure the scanner channel.
For more information about configuring a remote I/O network with the
1756-RIO or 1756-DHRIO modules, see these publications:
• Data Highway Plus-Remote I/O Communication Interface Module User
Manual, publication 1756-UM514
• ControlLogix Remote I/O Communication Module User Manual, publication 1756-UM534
As you design your remote I/O network, remember the following:
• All devices connected to a remote I/O network must communicate using the same communication rate. These rates are available for remote I/O:
– 57.6 Kbps
– 115.2 Kbps
– 230.4 Kbps
• You must assign unique partial and full racks to each channel used in
Remote I/O Scanner mode.
Both channels of a 1756-DHRIO module cannot scan the same partial or full rack address. Both module channels can communicate to 00...37 octal or 40...77 octal, but each channel can communicate only with one address at a time in whichever of these two ranges it falls.
100 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Foundation Fieldbus
Communication
Communication Networks Chapter 5
Foundation Fieldbus is an open interoperable fieldbus designed for process control instrumentation. The fieldbus devices described in the table can be connected to the ControlLogix controller via another network as shown in the example below.
Table 27 - Fieldbus Devices and Capabilities
Fieldbus Device
1757-FFLD
1788-CN2FF
Is used to
• Bridge an EtherNet/IP network to Foundation Fieldbus.
• Connect via a low-speed serial (H1) and high-speed Ethernet (HSE) network connections.
• Access devices directly via an OPC server.
• Connect via low-speed serial (H1) connections.
• Bridge a ControlNet network to a Foundation Fieldbus.
• Support redundant ControlNet media.
Foundation Fieldbus distributes and executes control in the device. The
Foundation Fieldbus linking device does the following:
• Bridges from an EtherNet/IP network to an H1 connection
• Accepts either HSE or EtherNet/IP messages and converts them to the H1 protocol
Figure 16 - Foundation Fieldbus Example
ControlLogix Controller with a 1756-ENBT Module
RSFieldbus Software
1757-FFLD Linking Device
24V DC
Power
Supply
Power
Conditioner
Field Device Field Device
For more information about using the Foundation Fieldbus devices available from Rockwell Automation, see these publications:
• Foundation Fieldbus Linking Device User Manual, publication
1757-UM010
• ControlNet Foundation Fieldbus Linking Device User Manual, publication 1757-UM011
• RSFieldbus User Manual, publication RSBUS-UM001
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 101
Chapter 5 Communication Networks
HART Communication
HART (Highway Addressable Remote Transducer) is an open protocol designed for process control instrumentation.
Device
1756 Analog I/O modules
• 1756-IF8H
• 1756-OF8H
ProSoft interface
• MVI56-HART
Is used to
• Act as HART master to allow communication with HART field devices.
• Interface directly with field devices (through built-in HART modems), eliminating need for external hardware and additional wiring.
• Provide access to more field device data, including voltage and current measurements.
• Directly connect asset management software to HART devices.
• Support differential wiring for environments where improved noise immunity is needed (input modules).
• Acquire data or control application with slow update requirements, such as a tank farm.
• Does not require external hardware to access HART signal.
• Does not provide a direct connection to asset management software.
The HART protocol combines digital signals with analog signals to ready the digital signal for the Process Variable (PV). The HART protocol also provides diagnostic data from the transmitter.
Figure 17 - HART Protocol Example
ControlLogix Controller with 1756-IF8H or
1756-OF8H Modules
HART Field Devices
For more information about using the HART I/O modules, see the
ControlLogix HART Analog I/O Modules User Manual, publication
1756-UM533 .
For more information about the ProSoft HART interface, see the
ProSoft Technologies website at http://www.prosoft-technology.com
.
102 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Communication Networks Chapter 5
Additional Resources
These documents contain additional information concerning related Rockwell
Automation products.
Resource
EtherNet/IP Modules in Logix5000 Control Systems User Manual, publication ENET-UM001
ControlNet Modules in Logix5000 Control Systems User Manual, publication CNET-UM001
DeviceNet Modules in Logix5000 Control Systems User Manual, publication
DNET-UM004
Logix5000 Controllers Design Considerations Reference Manual, publication 1756-RM094
Logix5000 Controllers General Instructions Reference Manual, publication
1756-RM003
Logix5000 Controllers Common Procedures Programming Manual, publication 1756-PM001
Using Logix5000 Controllers as Masters or Slaves on Modbus Application
Solution, publication CIG-AP129
Description
Describes how to configure and operate EtherNet/IP modules in a
Logix5000 control system.
Describes how to configure and operate ControlNet modules in a Logix5000 control system.
Describes how to configure and operate DeviceNet modules in a Logix5000 control system.
Provides advanced users with guidelines for system optimization and with system information to guide system design choices.
Provides programmers with details about each available instruction for a
Logix5000 controller.
Guides all user levels in developing projects for Logix5000 controllers and provides links to individual guides for information on topics such as import/export, messages, security, and programming in different languages.
Provides information to experienced Modbus users who are programming and troubleshooting applications that use Logix5000 controllers on the
Modbus network.
ControlLogix Data Highway Plus - Universal Remote I/O Module User
Manual, publication 1756-UM514
ControlLogix DH-485 Communication Module User Manual, publication
1756-UM532
ControlLogix Remote I/O Communication Module User Manual, publication
1756-UM534
Process Remote I/O Communication Interface Module User Manual, publication 1757-UM007
Describes how to configure and operate the ControlLogix 1756 DH+ / remote I/O module.
Describes how to configure and operate the ControlLogix 1756 DH-485 module.
Describes how to configure and troubleshoot the ControlLogix remote I/O
(RIO) communication module.
Describes how to configure and troubleshoot process remote I/O (RIO) communication interface modules.
Foundation Fieldbus Linking Device User Manual, publication 1757-UM010 Describes how to install, configure, and operate the 1757-FFLD linking device.
ControlNet Foundation Fieldbus Linking Device User Manual, publication
1757-UM011
RSFieldbus User Manual, publication RSFBUS-UM001
Describes how to install, configure, and operate the 1788-CN2FF linking device.
Describes how to install and use RSFieldbus Software to configure a
1757-FFLD linking device. Defines the available FOUNDATION Fieldbus function blocks for use with the 1757-FFLD linking device.
ControlLogix HART Analog I/O Modules User Manual, publication
1756-UM533
Encompass website available at http://www.rockwellautomation.com/encompass
ProSoft Technology website, available at http://www.prosoft-technology.com
Describes how to install, configure, and operate ControlLogix HART analog
I/O modules.
Assists in locating third-party products that best solve application challenges.
Provides information about ProSoft HART modules that can be used with a
ControlLogix system.
You can view or download publications at http://www.rockwellautomation.com/literature . To order paper copies of technical documentation, contact your local Rockwell Automation distributor or sales representative.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 103
Chapter 5 Communication Networks
Notes:
104 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Chapter
6
Serial Communication (1756-L6x controllers only)
Topic
1756-L6x Controller Serial Port
Communication with Serial Devices
Configure the 1756-L6x Controller for Serial Communication
Broadcast Messages Over a Serial Port
Page
1756-L6x Controller Serial
Port
The 1756-L6 x ControlLogix controllers have a built-in RS-232 port that can be used in a variety of serial-based applications. The potential serial communication applications include the following:
• DF1 modes (including broadcast message support)
• DF1 radio modem
• ASCII device communication
Figure 18 - ControlLogix DF1 Device Communication Example
EtherNet/IP
Network
DH+ Connection
RS-232 Connection
RS-232 Connection
RS-232 Connection
Modem
Modem
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Modem
105
Chapter 6 Serial Communication (1756-L6x controllers only)
ControlLogix Chassis Serial Communication Options
You can use the serial port of the ControlLogix controller and/or use ProSoft modules in the ControlLogix to achieve serial communication. Options specific to the ControlLogix controller serial port are described in this chapter.
For more information about ProSoft modules that can be used to establish serial communication, see the ProSoft Technology website at http://www.prosoft-technology.com
.
Communication with Serial
Devices
When configuring the controller for serial communication, you first specify a
Serial Port mode (System or User), then a protocol.
Figure 19 - Serial Port Mode in the Controller Properties
This table describes the serial communication protocols for use with each mode.
Table 28 - Serial Port Modes, Protocols, and Uses
Mode
System
User
Protocol
DF1 Master
Is used to
Control polling and message transmission between the master and slave nodes.
DF1 Point to Point • Communicate between the controller and one other DF1-protocol-compatible device.
• Program the controller via the serial port.
DF1 Radio Modem • Communication with SLC 500 and MicroLogix 1500 controllers.
• This protocol supports master/slave and store/forward configurations.
DF1 Slave
DH-485
Setup the controller as a slave station in a master/slave serial communication network.
Communication with other DH-485 devices via a multi-master and token-passing network that enables programming and peer-to-peer messaging.
ASCII • Communicate with ASCII devices.
• Use ASCII instructions to read and write data from and to an ASCII device.
See page
DF1 Master Protocol
The master/slave network includes one controller configured as the master node and up to 254 slave nodes. Link slave nodes by using modems or line drivers.
A master/slave network can have node numbers from 0...254. Each node must have a unique node address. Also, at least two nodes, one master and one slave, must exist to define your link as a network.
106 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Serial Communication (1756-L6x controllers only) Chapter 6
DF1 Point to Point Protocol
The DF1 Point to Point protocol is used when connecting from the controller to one DF1 device. This is the default System mode protocol. Default parameters are listed in this table.
Table 29 - Default DF1 Point to Point Parameters
Parameter
Baud Rate
Data Bits
Parity
Stop Bits
Control Line
RTS send Delay
RTS Off Delay
Value
19,200
8
None
0
0
1
No Handshake
DF1 Radio Modem Protocol
Your ControlLogix controller includes a driver that allows it to communicate over the DF1 Radio Modem protocol. This driver implements a protocol, optimized for use with radio modem networks, that is a hybrid between DF1 full-duplex protocol and DF1 half-duplex protocol, and therefore is not compatible with either of these protocols.
IMPORTANT The DF1 radio modem driver should be used only among devices that support and are configured for the DF1 Radio
Modem protocol.
Additionally, there are some radio modem network configurations that will not work with the DF1 radio modem driver. In these configurations, continue to use DF1 half-duplex protocol.
Figure 20 - DF1 Radio Modem Network Example
EtherNet/IP Network
Modem
RS-232
Modem
Modem
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Modem
Power
L1
L2/N
OUT
107
Chapter 6 Serial Communication (1756-L6x controllers only)
Like DF1 full-duplex protocol, the DF1 radio modem allows any node to initiate to any other node at any time (that is, if the radio modem network supports full-duplex data-port buffering and radio-transmission collision avoidance). Like
DF1 half-duplex protocol, a node ignores any packets received that have a destination address other than its own, with the exception of broadcast packets and passthru packets.
Unlike either DF1 full-duplex or DF1 half-duplex protocols, the DF1 radio modem protocol does not include ACKs, NAKs, ENQs, or poll packets. Data integrity is ensured by the CRC checksum.
DF1 Radio Modem Advantages
The primary advantage of using the DF1 radio modem protocol for radio modem networks is in transmission efficiency. Each read/write transaction
(command and reply) requires only one transmission by the initiator (to send the command) and one transmission by the responder (to return the reply). This minimizes the number of times the radios need to key-up to transmit, which maximizes radio life and minimizes radio power consumption.
In contrast, DF1 half-duplex protocol requires five transmissions for the DF1 master to complete a read/write transaction with a DF1 slave—three by the master and two by the slave.
The DF1 radio modem driver can be used in a pseudo master/slave mode with any radio modems, as long as the designated master node is the only node initiating MSG instructions, and as long as only one MSG instruction is triggered at a time.
For modern serial radio modems that support full-duplex data port buffering and radio transmission collision avoidance, the DF1 radio modem driver can be used to set up a masterless peer-to-peer radio network, where any node can initiate communication to any other node at any time, as long as all of the nodes are within radio range so that they receive each other’s transmissions.
108 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Serial Communication (1756-L6x controllers only) Chapter 6
DF1 Radio Modem Limitations
These considerations must be made if you can implement the new DF1 radio modem driver in your radio modem network:
• If all of the devices on the network are ControlLogix controllers, you must configure them with the DF1 radio modem driver by using RSLogix 5000 software, version 17 or later. If not, then make sure that all of the nodes can support the DF1 radio modem protocol.
• If each node receives the radio transmissions of every other node, being both within radio transmission/reception range and on a common receiving frequency (either via a Simplex radio mode or via a single, common, full-duplex repeater) the radio modems must handle full-duplex data port buffering and radio transmission collision avoidance.
If this is the case, you can take full advantage of the peer-to-peer message initiation capability in every node (for example, the ladder logic in any node can trigger a MSG instruction to any other node at any time).
If not all modems can handle full-duplex data port buffering and radio transmission collision avoidance, you may still be able to use the DF1 radio modem driver, but only if you limit MSG instruction initiation to a single master node whose transmission can be received by every other node.
• If not all nodes receive the radio transmission of every other node, you may still be able to use the DF1 radio modem driver, but only if you limit MSG instruction initiation to the node connected to the master radio modem whose transmissions can be received by every other radio modem in the network.
• You can take advantage of the ControlLogix controller channel-to-channel passthru to remotely program the other nodes by using RSLinx Classic software and RSLogix 5000 software running on a personal computer connected to a local ControlLogix controller via DH-485, DH+, or
Ethernet network.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 109
Chapter 6 Serial Communication (1756-L6x controllers only)
DF1 Radio Modem Protocol Parameters
Use this table as a reference when setting the parameters for the use of the DF1
Radio Modem Protocol.
Table 30 - DF1 Radio Protocol Parameters
Parameter
Station Address
Error Detection
Enable Store and Forward
Description
Specifies the node address of the controller on the serial network. Select a number 1…254 decimal, inclusive.
To optimize network performance, assign node addresses in sequential order. Initiators, such as personal computers, should be assigned the lowest address numbers to minimize the time required to initialize the network.
Click one of the radio buttons to specify the error detection scheme used for all messages.
• BCC - the processor sends and accepts messages that end with a BCC byte.
• CRC - the processor sends and accepts messages with a 2 byte CRC.
Check ’Enable Store and Forward’ if you want to enable the store and forward functionality. When enabled, the destination address of any received message is compared to the Store and Forward tag table. If there is a match, the message is then forwarded (re-broadcasted) out the port.
From the Store and Forward Tag pull-down menu, choose an integer (INT[16]) tag.
Each bit represents a station address. If this controller reads a message destined for a station that has its bit set in this table, it forwards the message.
DF1 Slave Protocol
With the DF1 slave protocol, a controller uses DF1 half-duplex protocol. One node is designated as the master and it controls who has access to the link. All the other nodes are slave stations and must wait for permission from the master before transmitting.
Make these considerations when using the DF1 Slave protocol:
• If multiple slave stations are used on the network, link slave stations by using modems or line drivers to the master.
• If you are using a single slave station on the network, you do not need a modem to connect the slave station to the master.
• Control parameters can be configured without handshaking.
• 2...255 nodes can be connected to a single link.
110 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
DH-485 Protocol
Serial Communication (1756-L6x controllers only) Chapter 6
The controller can send and receive messages to and from other controllers on a
DH-485 network. The DH-485 connection supports remote programming and monitoring via RSLogix 5000 programming software. However, excessive traffic over a DH-485 connection can adversely affect overall controller performance and lead to timeouts and decreased performance of the RSLogix 5000 configuration.
You can also use a 1756-DH485 module to connect the ControlLogix chassis to a
DH-485 network with multiple controllers. For more information, see the
ControlLogix DH-485 Communication Module User Manual, publication
1756-UM532 .
IMPORTANT Use Logix5000 controllers on DH-485 networks only when you want to add controllers to an existing DH-485 network.
For new applications with Logix5000 controllers, we recommend that you use networks in the NetLinx open architecture.
The DH-485 protocol uses RS-485 half-duplex as its physical interface. RS-485 is a definition of electrical characteristics, not a protocol. You can configure the
RS-232 port of the ControlLogix controller to act as a DH-485 interface.
To connect the controller to the DH-485 network, you must use these components:
• A 1761-NET-AIC converter (two controllers can be connected to one converter)
• An RS-232 cable (catalog number 1756-CP3 or 1747-CP3) for each controller to connect to the converter
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 111
Chapter 6 Serial Communication (1756-L6x controllers only)
Figure 21 - DH-485 Network Communication Overview
Computer with RSLogix 500 and RSLogix 5000 Software
ControlLogix Controller
ControlLogix Controller 1756-DH485 Module 1756-ENBT Module
AIC+ Link Coupler
AIC+ Link Coupler
DH-485 Network
AIC+ Link Coupler
TERM
AIC Link Coupler
MicroLogix
AIC Link Coupler
AIC Link Coupler
SLC 5/03 Controller
PanelView Display
SLC 5/03 Controller
IMPORTANT A DH-485 network consists of multiple cable segments. Limit the total length of all the segments to 1219 m (4000 ft).
112 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
ASCII Protocol
Configure the 1756-L6x
Controller for Serial
Communication
Serial Communication (1756-L6x controllers only) Chapter 6
When you configure the serial port for User mode and the ASCII protocol, you can use it to do the following:
• Read ASCII characters from a weigh scale module or bar code reader.
• Send and receive messages from an ASCII-triggered device, such as a
MessageView terminal.
After you configure the controller for use with the ASCII protocol, program the controller using the ASCII instructions. Reference the Logix5000 Controllers
General Instruction Reference Manual, publication 1756-RM003, for information about the ASCII instructions.
Complete these steps to configure your 1756-L6 x controller for serial communication after you have created a controller project in RSLogix 5000 programming software.
1.
Open the Controller Properties and click the Serial Port tab.
2.
From the Mode pull-down menu, choose the mode that corresponds to your intended protocol.
Use this table as a reference.
For this protocol
DF1 Master
DF1 Point to Point
DF1 Radio Modem
DF1 Slave
DH-485
ASCII
Choose this mode
System
User
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 113
Chapter 6 Serial Communication (1756-L6x controllers only)
3.
Specify the remaining properties in the Serial Port tab according to your communication preferences.
4.
If you are using the System mode protocols, click the System Protocol tab and specify the protocol parameters.
a. From the Protocol pull-down, choose the protocol you need.
b. Specify the parameters for the protocol.
114 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Serial Communication (1756-L6x controllers only) Chapter 6
5.
If you are using the User mode protocol (ASCII), click the User Protocol tab and specify the ASCII paramaters.
After you have configured the controller for ASCII protocol communication, reference the Logix5000 Controllers General Instruction
Reference Manual, publication 1756-RM003, for the available ASCII instructions.
Broadcast Messages Over a Serial Port
You can broadcast messages over a serial port connection from a master controller to all of its slave controllers by using several communication protocols. These protocols include the following:
• DF1 Master
• DF1 Radio Modem
• DF1 Slave
Broadcasting over a serial port is achieved by using the ‘message’ tag. Because messages are sent to receiving controllers, only the ‘write’ type messages can be used for broadcasting.
The broadcast feature can be set up by using ladder logic or structured text. The broadcast feature can also be set by modifying the path value of a message tag in the tag editor.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 115
Chapter 6 Serial Communication (1756-L6x controllers only)
To configure and program the controller to broadcast messages via the serial port, complete these procedures:
• Configure Controller Serial Port Properties, page 116
• Program the Message Instruction, page 117
For these procedure examples, ladder logic programming is used.
Configure Controller Serial Port Properties
First, set the System Protocol by following these steps.
1.
In the Controller Organizer, right-click the controller and choose
Properties.
2.
In the Controller Properties dialog box, from the System Protocol tab, choose the settings for the controller, then click OK.
116 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Serial Communication (1756-L6x controllers only) Chapter 6
Field
Station Address
Transmit Retries
ACK Timeout
Slave Poll Timeout
Reply Message Wait
Polling Mode
EOT Suppression
Error Detection
Duplicate Detection
Enable Store and Forward
Use this table as a reference when specifying settings for the protocols listed.
DF-1 Master Protocol
Controller station address number
3
50
N/A
5
Message: polls the slave by using the
Message instruction
Slave: initiates messages for slave-to-slave broadcast
Standard: schedules polling for the slave
N/A
BCC
Enabled
N/A
DF-1 Slave Protocol
Controller station address number
3
N/A
3000
N/A
N/A
Disable
BCC
Enabled
N/A
DF-1 Radio Modem Protocol
Controller station address number
N/A
N/A
N/A
N/A
N/A
N/A
BCC
N/A
Choose enable if you want to use the store and forward tag.
The last bit of the INT[16] Enable
Store and Forward array must be
’enabled.’ For example, say you create an INT[16] tag named EnableSandF.
Then EnableSandF[15].15 must be set to 1 for broadcast to work on radio modem.
Program the Message Instruction
Add and configure the Message instruction according to the protocol you are using. For more information about specifying the configuration details, see the
Logix5000 Controllers General Instruction Reference Manual, publication
1756-RM003 .
IMPORTANT When using structured text, broadcast over a serial port is set by typing
MSG(aMsg) and right-clicking on a MSG to display the
Message Configuration dialog box.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 117
Chapter 6 Serial Communication (1756-L6x controllers only)
Modbus Support
To use ControlLogix controllers with the Modbus protocol, establish a serial port connection and execute a specific ladder-logic routine.
Two controller projects specific to the Modbus network are available as sample programs with RSLogix 5000 software. These sample programs include the following:
• ModbusMaster.ACD
• ModbusSlave.ACD
For information about using these sample programs, see the Using Logix5000
Controllers as Masters or Slaves on Modbus Application Solution, publication
CIG-AP129 .
Additional Resources
Consult these resources for additional information related to serial communication and the ControlLogix system.
Resource
ProSoft Technology website, available at http://www.prosoft-technology.com
Logix5000 Controllers General Instruction Reference Manual, publication
1756-RM003
Using Logix5000 Controllers as Masters or Slaves on Modbus Application
Solution, publication CIG-AP129
Description
Provides information about multi-vendor modules that can be used to establish a serial communication network with a ControlLogix system.
Explains ASCII instructions and programming.
Explains how to apply the Modbus sample code in Logix5000 controller projects.
You can view or download publications at http://www.rockwellautomation.com/literature/ . To order paper copies of technical documentation, contact your local Rockwell Automation distributor or sales representative.
118 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Chapter
7
Manage Controller Communication
(connections)
Topic
Produce and Consume (interlock) Data
Page
Connection Overview
Produce and Consume
(interlock) Data
A Logix5000 system uses a connection to establish a communication link between two devices. The types of connections include the following:
• Controller-to-local I/O modules or local communication modules
• Controller-to-remote I/O or remote communication modules
• Controller-to-remote I/O (rack-optimized) modules
• Produced and consumed tags
• Messages
• Controller access by RSLogix 5000 programming software
• Controller access by RSLinx Classic or RSLinx Enterprise software for
HMI or other applications
ControlLogix controllers let you produce (broadcast) and consume (receive) system-shared tags.
Figure 22 - Illustration of Produced and Consumed Tags
Controller_1
Produced Tag
Controller_2
Consumed Tag
Controller_3
Consumed Tag
Controller_4
Consumed Tag
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 119
Chapter 7 Manage Controller Communication (connections)
The system-shared tags are explained in this table.
Table 31 - Produced and Consumed Tag Definitions
Tag Definition
Produced tag 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.
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 consumed tag determines the period at which the data updates.
For two controllers to share produced or consumed tags, both must be attached to the same network. You cannot bridge produced and consumed tags over two networks.
Produced and consumed tags use connections of both the controller and the communication modules being used. For a ControlNet network, produced and consumed tags use scheduled connections.
Connection Requirements of a Produced or Consumed Tag
Produced and consumed tags each require connections. 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.
IMPORTANT If a consumed-tag connection fails, all of the other tags being consumed from that remote controller stop receiving new data.
Each produced or consumed tag uses the number of connections listed in this table. Adding status information to a produced/consumed tag does not impact the number of connections used.
Table 32 - Produced and Consumed Tag Connections
This Type of Tag
Produced tag
Consumed tag 1
Produced or consumed tag 1
Uses This Many Connections Of This Module
number_of_consumers + 1 Controller
Communication
120 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Send and Receive
Messages
Manage Controller Communication (connections) Chapter 7
EXAMPLE Calculations of Connections for Produced or Consumed Tags
•
A ControlLogix controller producing 4 tags for 1 controller uses 8 connections:
– Each tag uses 2 connections (1 consumer + 1 = 2).
– 2 connections per tag x 4 tags = 8 connections.
•
Consuming 4 tags from a controller uses 4 connections (1 connection per tag x 4 tags = 4 connections).
The number of available connections limits the number of tags that can be produced or consumed. If the controller uses all of its connections for I/O and communication devices, no connections are left for produced and consumed tags.
Table 33 - ControlLogix Modules and Available Connections
Module Type
Controller
EtherNet/IP
ControlNet
Cat. No.
1756-L7x
1756-L6x
• 1756-EN2F
• 1756-EN2T
• 1756-EN2TXT
• 1756-EN2TR
• 1756-ENBT
• 1756-EWEB
• 1756-CN2
• 1756-CN2R
• 1756-CN2RXT
• 1756-CNB
• 1756-CNBR
Available Connections
500
250
256
128
128
64
For more information about produced/consumed tags, see the Logix5000
Controllers Produced and Consumed Tags Programming Manual, publication
1756-PM011 .
Messages transfer data to other devices, such as other controllers or operator interfaces. Some messages use unscheduled connections to send or receive data.
These connected messages can leave the connection open (cache) or closed when the message is done transmitting.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 121
Chapter 7 Manage Controller Communication (connections)
Each message uses one connection out of the controller, regardless of how many devices are in the message path. To conserve connections, configure one message to read from or write to multiple devices.
Table 34 - Message Types
Message Type
CIP data table read or write
PLC-2, PLC-3, PLC-5, or SLC
(all types)
CIP generic
Block-transfer read or write
Communication
Method
N/A
CIP
Connected
Message
Yes
No
CIP with Source ID No
DH+ Yes
N/A
N/A
Optional
Yes
(1)
Message Can Be
Cached
Yes
No
No
Yes
Yes
(2)
Yes
(1) You can connect CIP generic messages. However, for most applications we recommend you leave CIP generic messages unconnected.
(2) Consider caching only if the target module requires a connection.
Each message uses one connection, regardless of how many devices are in the message path. You can programmatically change the target of a MSG instruction to optimize message transfer time.
For more information about using messages, see these publications:
• Logix5000 Controllers Messages, publication 1756-PM012
• Logix5000 Controllers General Instructions, publication 1756-RM003
Determine Whether to Cache Message Connections
When you configure a MSG instruction, you can choose whether to cache the connection.
Use this table to determine if you should cache connections
.
Table 35 - Options for Caching Connections
If the message executes Then
Repeatedly Cache the connection.
This keeps the connection open and optimizes execution time.
Opening a connection each time the message executes increases execution time.
Infrequently Do not cache the connection.
This closes the connection upon completion of the message, which frees up that connection for other uses.
TIP Cached connections transfer data faster than uncached connections.
122 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Manage Controller Communication (connections) Chapter 7
Calculate Connection Use
The total connection requirements of a ControlLogix system include both local and remote connections.
Local Connections
Local connections refer to connections used to communicate between modules housed in the same ControlLogix chassis (that is, the local modules). Use this table to calculate the number of local connections based on the configuration of your local chassis.
Table 36 - Local Chassis Connections
Local Connection To
Local I/O module (always a direct connection)
1756-M16SE, 1756-M08SE, or 1756-M02AE servo module
• 1756-CN2, 1756-CN2R, 1756-CN2RXT ControlNet communication module
• 1756-CNB, 1756-CNBR ControlNet communication module
• 1756-EN2F, 1756-EN2T, 1756-EN2TXT, or 1756-EN2TR EtherNet/IP communication module
• 1756-ENBT EtherNet/IP communication module
1756-EWEB EtherNet/IP web server module
1756-DNB DeviceNet communication module
1756-RIO remote I/O communication module (Connection count depends on module configuration and could be as many as 10 per module.)
1756-DHRIO DH+/universal remote I/O communication module
Each adapter associated with the module
1756-DH485 DH-485 communication module
Device Quantity Connections per
Device
1
3
0
Total
Connections
0
0
2
1
1
1
1
Total
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 123
Chapter 7 Manage Controller Communication (connections)
Remote Connections
Use remote connections when the communication module is in a chassis that is remote from the controller. The number of connections a communication module supports determines how many remote connections the controller can access through that module.
Table 37 - Remote Connections
Remote Connection Type
Remote ControlNet communication module
I/O configured as direct connection (none)
I/O configured as rack-optimized connection
Remote I/O module over a ControlNet network (direct connection)
Remote EtherNet/IP communication module
I/O configured as direct connection (none)
I/O configured as rack-optimized connection
Remote I/O module over a EtherNet/IP network (direct connection)
Remote device over a DeviceNet network
(accounted for in rack-optimized connection for local 1756-DNB)
DeviceNet module in a remote chassis
Other remote communication adapter
Produced tag
Each consumer
Consumed tag
Message (depending on type)
Block-transfer message
Device Quantity Connections per
Device
Total
Connections
1
1
1
0
2
1
1
1
0 or
1
1
0 or
1
1
Total
124 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Manage Controller Communication (connections) Chapter 7
Connections Example
Series 9000
Photoeye
In this example system, the 1756 ControlLogix controller does the following:
• Controls local digital I/O modules in the same chassis
• Controls remote I/O devices on a DeviceNet network
• Sends and receives messages to and from a CompactLogix controller on an
EtherNet/IP network
• Produces one tag that the 1794 FlexLogix controller consumes
• Is programmed via RSLogix 5000 programming software
1769-ADN Adapter with Compact I/O Modules
RediSTATION
Operator
Interface
DeviceNet Network
1769-L35E CompactLogix with 1769-SDN Module
EtherNet/IP Network
ControlLogix Controller with 1756-ENBT and
1756-DNB Modules
FlexLogix Controller with 1788-DNBO Daughtercard
Workstation
The ControlLogix controller in this example uses these connections.
Table 38 - Connections Example Calculation
Connection Type
Controller to local I/O modules
Controller to 1756-ENBT module
Controller to 1756-DNB module
Controller to RSLogix 5000 programming software
Message to CompactLogix controller
Produced tag
Consumed by FlexLogix controller
2
1
1
1
1
4
1
Device Quantity Connections per
Device
1
0
2
1
1
1
1
2
1
2
1
1
Total 11
4
0
Total
Connections
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 125
Chapter 7 Manage Controller Communication (connections)
Additional Resources
These documents contain additional information concerning related Rockwell
Automation products.
Resource
Logix5000 Controllers Produced and Consumed Tags Programming Manual, publication 1756-PM011
Logix5000 Controllers Messages, publication 1756-PM012
Logix5000 Controllers Design Considerations Reference Manual, publication publication
1756-RM094
Logix5000 Controllers General Instructions Reference Manual, publication
1756-RM003
Logix5000 Controllers Common Procedures Programming Manual,
1756-PM001
Description
Explains produced and consumed tags and information related to using them in your program.
Explains details about caching, managing multiple messages, and sending messages to multiple controllers.
Provides advanced users with guidelines for system optimization and with system information to guide system design choices.
Provides programmers with details about each available instruction for a
Logix5000 controller. You should be familiar with how the Logix5000 controller stores and processes data before consulting this publication.
Guides all user levels in developing projects for Logix5000 controllers and provides links to individual guides for information on topics such as import/export, messages, security, producing/consuming data, and programming in different languages.
You can view or download publications at http://www.rockwellautomation.com/literature . To order paper copies of technical documentation, contact your local Rockwell Automation distributor or sales representative.
126 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Chapter
8
I/O Modules
Topic
Selecting ControlLogix I/O Modules
Determine When Data is Updated
Page
Selecting ControlLogix I/O
Modules
Rockwell Automation offers several ControlLogix I/O modules for use in
ControlLogix systems. When you select your I/O modules, remember the following:
• A wide variety of digital, analog, and specialty I/O modules are available from Rockwell Automation. Some features of these I/O modules include the following:
– Field-side diagnostics
– Electronic fusing
– Individually-isolated inputs/outputs
• Removable terminal blocks (RTBs) or 1492 wiring systems are required for use with I/O modules.
• 1492 PanelConnect modules and cables can be used to connect input modules to sensors.
For more information about ControlLogix I/O module features, specifications, and wiring options, see the ControlLogix Selection Guide, publication
1756-SG001 .
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 127
Chapter 8 I/O Modules
Local I/O Modules
The ControlLogix chassis you choose affects how many local I/O modules you can use. Several ControlLogix chassis sizes are available to suit your configuration requirements. You can fill the slots of your chassis with any combination of controllers, communication modules, and I/O modules.
This table lists the available ControlLogix chassis and the number of slots available with each.
Table 39 - ControlLogix and ControlLogix-XT Chassis and Slots
Chassis
1756-A4
1756-A4LXT
1756-A5XT
1756-A7
1756-A7LXT
1756-A10
1756-A13
1756-A17
5
7
Slots
4
10
13
17
If you have empty slots in your chassis, use the 1756-N2 or 1756-N2XT slot-filler module.
Add Local I/O to the I/O Configuration
If you are adding local I/O, add the I/O module to the backplane with the controller. To add an I/O module to the local chassis, complete these steps.
1.
Right-click the backplane and choose New Module.
128 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
I/O Modules Chapter 8
2.
Select the I/O module you want to add and click OK.
3.
Specify the configuration properties according to the module and network configuration you are using.
For more information about the module configuration properties, see the user manual for the I/O module you are adding.
For this type of module See this user manual
Analog I/O ControlLogix Analog I/O Modules User Manual, publication 1756-UM009
Configurable flowmeter
Digital I/O
ControlLogix Configurable Flowmeter Module
User Manual, publication 1756-UM010
ControlLogix Digital I/O Modules User Manual, publication 1756-UM058
HART analog I/O
High speed analog I/O
ControlLogix HART Analog I/O Modules User
Manual, publication 1756-UM533
ControlLogix High Speed Analog I/O Module
User Manual, publication 1756-UM005
High speed counter ControlLogix High Speed Counter Module User
Manual, publication 1756-UM007
Programmable limit switch ControlLogix Programmable Limit Switch Module
User Manual, publication 1756-UM002
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 129
Chapter 8 I/O Modules
Remote I/O Modules
Remote I/O refers to I/O that is not located in the local chassis and is connected to the controller via a communication network.
The ControlLogix controller supports the use of remote I/O via these networks:
• EtherNet/IP
• ControlNet
• DeviceNet
• Universal remote I/O
For more information about the network configurations that can be used to
connect remote I/O, see Chapter 5, Communication Networks (on page 89
).
Figure 23 - ControlLogix Controller and Remote I/O Example
ControlLogix Controller Chassis
ControlLogix Remote I/O
ControlNet
130 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
I/O Modules Chapter 8
Add Remote I/O to the I/O Configuration
If you are adding remote I/O, add the I/O modules to the backplane of the remote communication module that is connected to the controller. To add a remote I/O to the I/O Configuration folder in RSLogix 5000 software, complete these steps.
1.
Add a communication module to the backplane that contains the controller.
2.
Specify the communication module properties according to your network configuration.
For more information about the communication module and network properties, see the user manual for the network you are using:
– ControlNet Modules in Logix5000 Control Systems User Manual, publication CNET-UM001
– DeviceNet Modules in Logix5000 Control Systems User Manual, publication DNET-UM004
– EtherNet/IP Modules in Logix5000 Control Systems User Manual, publication ENET-UM001
3.
Right-click the communication network and choose New Module.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 131
Chapter 8 I/O Modules
4.
Add the remote communication module you are using.
5.
Specify the chassis and connection properties according to your network configuration.
6.
Right-click the backplane of the newly-added communication module and choose New Module.
7.
Select the I/O module you want to add and click OK.
132
8.
Specify the Module Properties according to your module and application.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
I/O Modules Chapter 8
For more information about the module configuration properties, see the user manual for the I/O module you are adding.
For this type of module See this user manual
Analog I/O ControlLogix Analog I/O Modules User Manual, publication 1756-UM009
Configurable flowmeter
Digital I/O
ControlLogix Configurable Flowmeter Module
User Manual, publication 1756-UM010
ControlLogix Digital I/O Modules User Manual, publication 1756-UM058
HART analog I/O
High speed analog I/O
ControlLogix HART Analog I/O Modules User
Manual, publication 1756-UM533
ControlLogix High Speed Analog I/O Module
User Manual, publication 1756-UM005
High speed counter ControlLogix High Speed Counter Module User
Manual, publication 1756-UM007
Programmable limit switch ControlLogix Programmable Limit Switch Module
User Manual, publication 1756-UM002
9.
Add any other I/O modules you are using in the remote chassis.
10.
until your remote I/O network and I/O modules are configured in RSLogix 5000 software.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 133
Chapter 8 I/O Modules
Distributed I/O
Distributed I/O refers to I/O that is located remote from the controller and is not designed for use with a specific controller. Examples of distributed I/O that can be used with Logix5000 controllers include the following:
• 1794 FLEX I/O modules
• 1734 POINT I/O modules
• 1732 ArmorPoint I/O modules
Distributed I/O is connected to the ControlLogix controller via a communication network. The ControlLogix controller supports the use of distributed I/O via these networks:
• EtherNet/IP
• ControlNet
• DeviceNet
Figure 24 - ControlLogix System with Distributed I/O Example
ControlLogix Controller Chassis
EtherNet/IP™ Logix5575
FORCE
RUN FORCE SD OK
EtherNet/IP
POINT I/O
FLEX I/O
A
COMM STATUS
B
REDUNDANT MEDIA
ADAPTER
1794-ACNR15
ControlNet
134 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
I/O Modules Chapter 8
Add Distributed I/O to the I/O Configuration
If you are adding distributed I/O, add the I/O modules to the communication adapter of the I/O. To add distributed I/O to the I/O Configuration folder for the ControlLogix controller, complete these steps.
1.
Add a communication module to the backplane that contains the controller.
2.
Specify the communication module properties according to your network configuration.
For more information about the communication module and network properties, see the user manual for the network you are using:
– ControlNet Modules in Logix5000 Control Systems User Manual, publication CNET-UM001
– DeviceNet Modules in Logix5000 Control Systems User Manual, publication DNET-UM004
– EtherNet/IP Modules in Logix5000 Control Systems User Manual, publication ENET-UM001
3.
Right-click the communication network and choose New Module.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 135
Chapter 8 I/O Modules
4.
Add the communication adapter for the distributed I/O platform you are using.
5.
Specify the module and connection properties according to your network configuration.
6.
Right-click the bus of the newly-added communication adapter and choose New Module.
7.
Select the I/O module you want to add and click OK.
136
8.
Specify the Module Properties according to your module and application.
For more information about the module configuration properties, see the user manual for the I/O module you are adding.
9.
Add any other I/O modules you are using in this bus.
10.
…
9 until your remote I/O network and distributed I/O
modules are configured in RSLogix 5000 software.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
I/O Modules Chapter 8
Reconfigure an I/O Module
If an I/O module supports reconfiguration, you can reconfigure the module via the following:
• The Module Properties dialog box in the I/O Configuration folder
• A MSG instruction in program logic.
IMPORTANT Use care when changing the configuration of an I/O module. You could inadvertently cause the I/O module to operate incorrectly.
Use a MSG instruction of type Module Reconfigure to send new configuration information to an I/O module. During the reconfiguration add the following:
• Input modules that continue to send input data to the controller
• Output modules that continue to control their output devices
Reconfigure an I/O Module via the Module Properties
To reconfigure an I/O module using the module properties, right-click the module in the I/O Configuration tree and choose Properties. Then, edit the properties you need to change and click Apply.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 137
Chapter 8 I/O Modules
EXAMPLE
Reconfigure an I/O Module via a Message Instruction
To reconfigure an I/O module via a message instruction, use this procedure.
1.
Set the required member of the configuration tag of the module to the new value.
2.
Send a Module Reconfigure message to the module.
Reconfigure an I/O module
When reconfigure[5] is on, the MOV instruction sets the high alarm to 60 for the local module in slot 4. The Module Reconfigure message then sends the new alarm value to the module. The ONS instruction prevents the rung from sending multiple messages to the module while the reconfigure[5] is on.
For more information about using Message instructions, see the Logix5000
Controllers General Instruction Reference Manual, publication 1756-RM003 .
Add to the I/O Configuration
While Online
With RSLogix 5000 programming software, versions 15 or later, you can add
I/O and other devices to the I/O Configuration for the controller while you are online and in Run mode.
The specific modules and devices you can add while online depends on the version of RSLogix 5000 software you are using. Later versions have more modules and devices that can be added while online.
You can add these modules and devices to the local or remote chassis via the unscheduled portion of a ControlNet network or via an EtherNet/IP network.
For more information about adding to the I/O Configuration while online, see the Runtime/On-line Addition of ControlLogix (1756) I/O over ControlNet and EtherNet/IP White Paper, publication LOGIX-WP006 .
138 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
I/O Modules Chapter 8
Modules and Devices that Can be Added While Online
These modules and devices can be added to the ControlLogix controller I/O
Configuration while online as of RSLogix 5000 software, version 18.
ControlLogix Modules that Can be Added While Online
• 1756 controllers
• 1756 ControlNet modules
• 1756 DeviceNet bridge modules
• 1756 EtherNet/IP modules
• 1756 I/O modules
IMPORTANT These ControlLogix modules cannot be added while online:
• Motion modules (1756-MO2AE, 1756-HYD02, 1756-MO2AS,
1756-MO3SE, 1756-MO8SE, 1756-MO8SEG, 1756-M16SE)
• 1756-RIO
• 1756-SYNCH
• 1756-ENBF
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 139
Chapter 8 I/O Modules
• PowerFlex 4 Class Multi-E
• PowerFlex 400-E
• PowerFlex 400P-E
• PowerFlex 40-E
• PowerFlex 40P-E
• PowerFlex 4-E
• PowerFlex 4M-E
• PowerFlex 70 EC-C
• PowerFlex 70 EC-C
• PowerFlex 70 EC-E
• PowerFlex 70 EC-E
• PowerFlex 70 EC-Q
• PowerFlex 70 EC-Q
• PowerFlex 700 AC-C
• PowerFlex 700 AC-E
• PowerFlex 700 AC-Q
• PowerFlex 700 Vector-200V-C
• PowerFlex 700 Vector-200V-E
• PowerFlex 700 Vector-200V-Q
• PowerFlex 700 Vector-400V-C
• PowerFlex 700 Vector-400V-E
• PowerFlex 700 Vector-400V-Q
• PowerFlex 700 Vector-600V-C
• PowerFlex 700 Vector-600V-E
• PowerFlex 700 Vector-600V-Q
• PowerFlex 7000 2-C
• PowerFlex 7000 2-E
• PowerFlex 7000 2-Q
• PowerFlex 7000-C
• PowerFlex 7000-E
PowerFlex Drives that Can be Added While Online
• PowerFlex 7000-Q
• PowerFlex 700-200V-C
• PowerFlex 700-200V-E
• PowerFlex 700-200V-Q
• PowerFlex 700-400V-C
• PowerFlex 700-400V-E
• PowerFlex 700-400V-Q
• PowerFlex 700-600V-C
• PowerFlex 700-600V-E
• PowerFlex 700-600V-Q
• PowerFlex 700AFE-C
• PowerFlex 700AFE-E
• PowerFlex 700AFE-Q
• PowerFlex 700H-C
• PowerFlex 700H-E
• PowerFlex 700H-Q
• PowerFlex 700S 2-200V
• PowerFlex 700S 2-400V
• PowerFlex 700S 2-600V
• PowerFlex 700S 2P-200V-C
• PowerFlex 700S 2P-200V-E
• PowerFlex 700S 2P-200V-Q
• PowerFlex 700S 2P-400V-C
• PowerFlex 700S 2P-400V-E
• PowerFlex 700S 2P-400V-Q
• PowerFlex 700S 2P-600V-C
• PowerFlex 700S 2P-600V-E
• PowerFlex 700S 2P-600V-Q
• PowerFlex 700S-200V-C
• PowerFlex 700S-200V-E
• PowerFlex 700S-200V-Q
• PowerFlex 700S-400V-C
• PowerFlex 700S-400V-E
• PowerFlex 700S-400V-Q
• PowerFlex 700S-600V-C
• PowerFlex 700S-600V-E
• PowerFlex 700S-600V-Q
• PowerFlex 70-C
• PowerFlex 70-E
• PowerFlex 70-E
• PowerFlex 70-Q
• PowerFlex 70-Q
• PowerFlex 753-CNETC
• PowerFlex 753-NET-C
• PowerFlex 753-NET-E
• PowerFlex 753-NET-Q
• PowerFlex 755-CNETC
• PowerFlex 755-EENET
• PowerFlex 755-NET-C
• PowerFlex 755-NET-E
• PowerFlex 755-NET-Q
• PowerFlex DC-200V-C
• PowerFlex DC-200V-E
• PowerFlex DC-200V-Q
• PowerFlex DC-400V-C
• PowerFlex DC-400V-E
• PowerFlex DC-400V-Q
• PowerFlex DC-600V-C
• PowerFlex DC-600V-E
• PowerFlex DC-600V-Q
140 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
I/O Modules Chapter 8
Other Devices that Can be Added While Online
• 1305-BAXXA drives
• 1336E-IMPACTDrive-EN1 drive
• 1336F-PLUSIIDrive-EN1drive
• 1336R-REGENBrake-EN1 brake
• 1336S-PLUSDriveLG-EN1 drive
• 1336S-PLUSDriveSM-EN1 drive
• 1336T-FORCEDriveCNA-EN1 drive
• 1336T-FORCEDrivePLC-EN1 drive
• 1336T-FORCEDriveStd-EN1 drive
• 1397DigitalDCDrive-EN1 drive
• 150 SMC FLEX motor controller
• 150-SMCDialogPlus-EN1 motor controller
• 1757-FFLDC ControlNet Foundation Fieldbus device
• 2364F RGU-EN1 bus supply
• 48MS-SN1PF1-M2 Multivision Sensor
• 5XRF RFID interface device
Online Additions - ControlNet Considerations
ControlNet considerations that must be made depend upon the ControlLogix
ControlNet modules you are using.
1756-CNB and 1756-CNBR Modules
When you add I/O to the ControlNet network via the 1756-CNB or
1756-CNBR modules while online, these considerations must be made:
• Digital I/O modules can be added as rack-optimized connections if the parent module is already configured with rack-optimized connections.
TIP While you can add a new digital I/O module to an existing rack-optimized connection, you cannot add rack-optimized connections while online.
• Digital I/O modules can also be added as direct connections.
• Analog I/O modules can be added only as direct connections.
• Disable the Change of State (COS) feature on digital input modules because it can cause inputs to be sent more quickly than the RPI.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 141
Chapter 8 I/O Modules
• If you plan to add large amounts of I/O to the ControlNet network, dedicate one ControlNet network for I/O. For the dedicated ControlNet network, verify that there is little or none of the following:
– HMI traffic
– MSG traffic
– Programming workstations
• Requested Packet Intervals (RPIs) faster than 25 ms for unscheduled modules can overload the 1756-CNB or 1756-CNBR communication module. To avoid the overload, make these considerations:
– Use a NUT if 10 ms or more.
– Keep the SMAX and UMAX values as small as possible.
• If the module has a Real Time Sample (RTS), it should be disabled or set to a rate that is greater than the RPI.
• You can add I/O modules until you reach these limits:
– 75% of CPU utilization of the 1756-CNB or 1756-CNBR communication module.
– Plan for a CPU-use increase of 1...4% of the 1756-CNB or
1756-CNBR module for each I/O module you add, depending on the
RPI.
– 48 connections on the 1756-CNB or 1756-CNBR communication module.
– Less than 400,000 unscheduled bytes per second are displayed in
RSNetWorx for ControlNet software after the network has been scheduled.
1756-CN2, 1756-CN2R, 1756-CN2RXT Modules
The use of 1756-CN2/B, 1756-CN2R/B, and 1756-CN2RXT modules provides increased capacity for adding I/O while online compared to 1756-CNB or 1756-CNBR modules. With this increased capacity, you can easily add I/O and increase ControlNet connections used with significantly less impact on the overall system.
142 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
I/O Modules Chapter 8
This table demonstrates the performance factors of the 1756-CN2/B,
1756-CN2R/B, and 1756-CN2RXT modules when adding I/O online.
Table 40 - 1756-CN2, 1756-CN2R, and 1756-CN2RXT Performance Example
(1)
10
11
12
13
8
9
6
7
14
15
4
5
2
3
0
1
No. of Direct
Analog I/O
Connections
Added
Online
RPI = 2 ms
CPU %
(2) Avg.
API
(3)
15.10%
15.00%
15.60%
16.40%
17.00%
17.80%
18.50%
19.40%
1.50%
4.80%
7.00%
9.00%
11.20%
11.50%
12.80%
13.80%
3.8
3.7
3.7
3.9
3.4
3.3
3.6
3.8
2.2
3.3
3.3
3.4
N/A
2.0
2.0
2.0
RPI = 4 ms
CPU %
(2) Avg.
API
1.50%
3.70%
5.00%
6.10%
7.40%
8.70%
4.0
4.0
9.70% 4.0
10.80% 4.0
N/A
4.0
4.0
4.0
11.90% 4.0
13.20% 4.0
13.20% 4.0
13.50% 4.0
14.00% 4.0
14.60% 4.0
15.20% 4.0
15.80% 4.0
(3)
RPI = 10 ms
CPU %
(1) Example assumes that adequate unscheduled bandwidth is available.
(2) Approximate use of the module’s central-processing unit (CPU) in percent.
(3) The average Actual Packet Interval with 2000 samples (shown in ms).
(2) Avg.
API
(3)
RPI = 20 ms
CPU %
1.50%
2.50%
3.30%
3.80%
4.40%
5.00%
5.50%
5.90%
N/A 1.50%
10.0
2.30%
10.0
2.70%
10.0
3.00%
10.0
3.40%
10.0
3.70%
10.0
4.00%
10.0
4.30%
6.40%
7.00%
7.50%
8.20%
10.0
4.50%
10.0
4.80%
10.0
5.20%
10.0
5.50%
8.80%
9.30%
10.0
5.80%
10.0
6.10%
9.90% 10.0
6.40%
10.50% 10.0
6.70%
(2) Avg.
API
(3)
RPI = 50 ms
CPU %
N/A 1.50%
20.0
1.90%
20.0
2.10%
20.0
2.20%
20.0
2.40%
20.0
2.60%
20.0
2.70%
20.0
2.90%
20.0
3.00%
20.0
3.20%
20.0
3.40%
20.0
3.50%
20.0
3.70%
20.0
3.80%
20.0
4.00%
20.0
4.10%
(2) Avg.
API
(3)
50.0
50.0
50.0
50.0
50.0
50.0
50.0
50.0
50.0
50.0
50.0
50.0
N/A
50.0
50.0
50.0
RPI = 100 ms
CPU %
(2) Avg.
API
(3)
2.50%
2.60%
2.70%
2.70%
2.80%
2.90%
2.90%
3.00%
1.50%
1.70%
1.90%
2.00%
2.10%
2.20%
2.30%
2.30%
100.0
100.0
100.0
100.0
100.0
100.0
100.0
100.0
N/A
100.0
100.0
100.0
100.0
100.0
100.0
100.0
Because of the increased performance provided by the 1756-CN2, 1756-CN2R, and 1756-CN2RXT modules, many of the considerations that must be made with the 1756-CNB and 1756-CNBR modules are not applicable. With the
1756-CN2, 1756-CN2R, and 1756-CN2RXT modules, you can add I/O while online as long as you use reasonable RPI settings and remain within the CPU limitations of the ControlNet module.
When adding to the I/O Configuration with 1756-CN2, 1756-CN2R, and
1756-CN2RXT modules, make these considerations:
• Digital I/O modules can be added as rack-optimized connections if the parent module is already configured with rack-optimized connections.
TIP While you can add a new digital I/O module to an existing rack-optimized connection, you cannot add rack-optimized connections while online.
• Digital I/O modules can also be added as direct connections.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 143
Chapter 8 I/O Modules
• Analog I/O modules can be added only as direct connections.
• Disable the Change of State (COS) feature on digital input modules because it can cause inputs to be sent more quickly than the RPI.
• If you plan to add large amounts of I/O to the ControlNet network, dedicate one ControlNet network for I/O. For the dedicated ControlNet network, verify that there is little or none of the following:
– HMI traffic
– MSG traffic
– Programming workstations
• If the module has a Real Time Sample (RTS), it should be disabled or set to a rate that is greater than the RPI.
• You can add I/O modules until you reach these limits:
– 80% of CPU utilization of the 1756-CN2, 1756-CN2R, or
1756-CN2RXT communication module.
– Less than 400,000 unscheduled bytes per second are displayed in
RSNetWorx for ControlNet software after the network has been scheduled.
Online Additions - EtherNet/IP Considerations
When you add I/O modules to the EtherNet/IP network, make these considerations:
• The EtherNet/IP I/O modules you add can be added as these connection types:
– Rack-optimized connections, including new and existing connections
– Direct connections
• You can add I/O modules until you reach the limits of the communication module.
For EtherNet/IP module limitations, see the EtherNet/IP Modules in
Logix5000 Control Systems User Manual, publication ENET-UM001 .
144 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
I/O Modules Chapter 8
Determine When Data is
Updated
Input or Output Data?
Input
Output
ControlLogix controllers update date asynchronously with the execution of logic.
Use this flowchart to determine when a producer, such as a controller, input module, or bridge module, will send data.
Figure 25 - Data Update Flowchart
Digital Analog or Digital?
Analog
Digital
Analog or Digital?
Analog
Remote or Local?
Remote Local
RTS
RPI?
No
COS for Any Point on the
Module?
Yes
No
Yes
Data is sent to the backplane at the RTS.
Data is sent to the backplane at the RTS and RPI.
Data is sent to the backplane at the RPI and at the change of a specified point.
·
Over a ControlNet network, remote data is sent at the actual packet interval.
·
Over an EtherNet/IP network, remote data is usually sent close to the RPI.
Data is sent to the backplane at the
RPI.
Data is sent to the backplane at the RPI and at the end of every task.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 145
Chapter 8 I/O Modules
Additional Resources
These documents contain additional information concerning related Rockwell
Automation products.
Resource
ControlLogix Selection Guide, publication 1756-SG001
Description
Provides a high-level selection process for ControlLogix system components, critical specifications information for making initial decisions, and links to complete specifications information.
ControlLogix Digital I/O Modules User Manual, publication 1756-UM058 Describes how to install, configure, and troubleshoot ControlLogix digital
I/O modules.
ControlLogix Analog I/O Modules User Manual, publication 1756-UM009 Describes how to install, configure, and troubleshoot ControlLogix analog
I/O modules.
ControlLogix Configurable Flowmeter Module User Manual, publication
1756-UM010
Describes how to install, configure, and troubleshoot ControlLogix configurable flowmeter modules.
ControlLogix HART Analog I/O Modules User Manual, publication
1756-UM533
ControlLogix High Speed Analog I/O Module User Manual, publication
1756-UM005
Describes how to install, configure, and troubleshoot ControlLogix HART
I/O modules.
Describes how to install, configure, and troubleshoot ControlLogix high-speed analog I/O modules.
ControlLogix High Speed Counter Module User Manual, publication
1756-UM007
Logix5000 Controllers Common Procedures Programming Manual, publication 1756-PM001
Describes how to install, configure, and troubleshoot ControlLogix high-speed counter modules.
ControlLogix Programmable Limit Switch Module User Manual, publication
1756-UM002
Describes how to install, configure, and troubleshoot ControlLogix programmable limit switch modules.
Guides all user levels in developing projects for Logix5000 controllers and provides links to individual guides for information on topics such as import/export, messages, security, and programming in different languages.
Explains adding to the I/O Configuration while online with the controller.
Runtime/On-line Addition of ControlLogix (1756) I/O over ControlNet and
EtherNet/IP White Paper, publication LOGIX-WP006
EtherNet/IP Communication Modules in Logix5000 Control Systems User
Manual, publication ENET-UM001
ControlNet Modules in Logix5000 Control Systems User Manual, publication CNET-UM001
Describes how to configure and operate EtherNet/IP modules in a
Logix5000 control system.
Describes how to configure and operate ControlNet modules in a Logix5000 control system.
DeviceNet Communication Modules in Logix5000 Control Systems User
Manual, publication DNET-UM004
Describes how to configure and operate DeviceNet modules in a Logix5000 control system.
You can view or download publications at http://www.rockwellautomation.com/literature . To order paper copies of technical documentation, contact your local Rockwell Automation distributor or sales representative.
146 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Chapter
9
Develop Motion Applications
Topic
Page
Motion Control Options
Motion Overview
ControlLogix controllers support digital and analog interfaces:
• Digital drive interfaces include EtherNet/IP connected drives and
SERCOS interface connected drives.
• Analog drives support ±10 voltage analog output and can interface with a variety of feedback device types including quadrature encoder, SSI, and
LVDT feedback.
The configuration process varies, depending on your application and your drive selection. The following are general steps to configure a motion application.
1.
Create a controller project.
2.
Select the type of drive.
Drive Type
Integrated motion on an EtherNet/IP network
SERCOS interface
Analog interface
Requirements
• EtherNet/IP communication module
• Digital drive with an EtherNet/IP connection
Select a SERCOS interface module:
• 1756-M03SE
• 1756-M08SE
• 1756-M16SE
Select an analog interface module:
• 1756-HYD02
• 1756-M02AE
• 1756-M02AS
3.
Create axis tags as needed.
4.
Configure the drive.
5.
Create axes as needed.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 147
Chapter 9 Develop Motion Applications
Obtain Axis Information
You can obtain axis information by using these methods:
• Double-click the axis to open the Axis Properties dialog box.
• Use a Get System Value (GSV) or Set System Value (SSV) instruction to read or change the configuration at run-time.
• View the Quick View pane to see the state and faults of an axis.
• Use an axis tag for status and faults.
Figure 26 - Obtain Axis Information
Axis Properties Dialog Box
SSV (or GSV) Instruction
Axis Tag
Quick View Pane
Program Motion Control
The controller provides a set of motion control instructions for your axes:
• The controller uses these instructions just like the rest of the Logix5000 instructions.
• Each motion instruction works on one or more axes.
• Each motion instruction needs a motion control tag. The tag uses a
MOTION_INSTRUCTION data type and stores the instruction’s information status.
• You can program using motion control instructions in these programming languages:
– Ladder Diagram (LD)
– Structured Text (ST)
– Sequential Function Chart (SFC)
148 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Develop Motion Applications Chapter 9
Figure 27 - Motion Control Instruction
Motion Control Tag
ATTENTION: Use the tag for the motion control operand of motion instruction only once. Unintended operation of the control variables may happen if you reuse of the same motion control tag in other instructions.
Example
Here’s an example of a simple ladder diagram that homes, jogs, and moves an axis.
If Initialize_Pushbutton = on and the axis = off (My_Axis_X.ServoActionStatus = off) then the MSO instruction turns on the axis.
If Home_Pushbutton = on and the axis hasn’t been homed (My_Axis_X.AxisHomedStatus = off) then the MAH instruction homes the axis.
If Jog_Pushbutton = on and the axis = on (My_Axis_X.ServoActionStatus = on) then the MAJ instruction jogs the axis forward at 8 units/second.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 149
Chapter 9 Develop Motion Applications
If Jog_Pushbutton = off then the MAS instruction stops the axis at 100 units/.second
2
.
Make sure that Change Decel is Yes. Otherwise, the axis decelerates at its maximum speed.
If Move_Command = on and the axis = on (My_Axis_X.ServoActionStatus = on) then the MAM instruction moves the axis. The axis moves to the position of 10 units at 1 unit/second.
150 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Develop Motion Applications Chapter 9
Additional Resources
These documents contain additional information concerning related Rockwell
Automation products.
Resource
SERCOS Motion Configuration and Startup User Manual, publication
MOTION-UM001
Motion Coordinated Systems User Manual, publication MOTION-UM002
Description
Details how to configure a SERCOS motion application system.
Details how to create and configure a coordinated motion application system.
Details how to configure a Integrated Motion on the EtherNet/IP network.
CIP Motion Configuration and Startup User Manual, publication
MOTION-UM003
Logix5000 Controllers Motion Instructions Reference Manual, publication
MOTION-RM002
ControlLogix Selection Guide, publication 1756-SG001
Motion Analyzer Selection Guide, publication PST-SG003
Logix5000 Controllers General Instructions Reference Manual, publication
1756-RM003
Logix5000 Controllers Common Procedures Programming Manual, publication 1756-PM001
Provides programmers with details about the motion instructions that are available for a Logix5000 controller.
Provides a high-level selection process for ControlLogix system components, critical specifications information for making initial decisions, and links to complete specifications information.
Provides motion selection and configuration tools via CD-ROM.
Provides programmers with details about each available instruction for a
Logix5000 controller. You should be familiar with how the Logix5000 controller stores and processes data before consulting this publication.
Guides all user levels in developing projects for Logix5000 controllers and provides links to individual guides for information on topics such as import/export, messages, security, and programming in different languages.
You can view or download publications at http://www.rockwellautomation.com/literature . To order paper copies of technical documentation, contact your local Rockwell Automation distributor or sales representative.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 151
Chapter 9 Develop Motion Applications
Notes:
152 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Elements of a Control
Application
Chapter
10
Develop Applications
Topic
Elements of a Control Application
Page
A control application is comprised of several elements that require planning for efficient application execution. Application elements include the following:
• Tasks
• Programs
• Routines
• Tags
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 153
Chapter 10 Develop Applications
Tasks
Figure 28 - Elements of a Control Program
RSLogix 5000 Control Application
Task 8
Task 1
Configuration
Status
Watchdog
Program 32
Program 1
Main
Routine
Fault
Routine
Program
(local) Tags
Other
Routines
Controller (global)
Tags
I/O Data System-shared Data
A Logix5000 controller lets you use multiple tasks to schedule and prioritize the execution of your programs based on specific criteria. This multitasking allocates the controller’s processing time among the different operations in your application:
• The controller executes only one task at a time.
• One task can interrupt another’s execution and take control.
• In any given task, multiple programs may be used. However, only one program executes at a time.
154 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Develop Applications Chapter 10
Figure 29 - Task Within a Control Application
RSLogix 5000 Control Application
Controller Fault Handler
Task 8
Task 1
Configuration
Status
Watchdog
Program 32
Program 1
Main
Routine
Fault
Routine
Program
(local) Tags
Other
Routines
Controller (global)
Tags
I/O Data System-shared Data
Figure 30 - Tasks in RSLogix 5000 Software
Main Task
(Continuous)
Task 2
(Periodic)
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 155
Chapter 10 Develop Applications
A task provides scheduling and priority information for a set of one or more programs. Configure tasks as continuous, periodic, or event using the Task
Properties dialog box.
Figure 31 - Configuring the Task Type
This table explains the types of tasks you can configure.
Table 41 - Task Types and Execution Frequency
Task Type Task Execution
Continuous All of the time
Periodic
Event
• At a set interval, such as every 100 ms
• Multiple times within the scan of your other logic
Immediately when an event occurs
Description
The continuous task runs in the background. Any CPU time not allocated to other operations (such as motion, communication, and other tasks) is used to execute the programs in the continuous task.
• The continuous task runs constantly. When the continuous task completes a full scan, it restarts immediately.
• A project does not require a continuous task. If used, there can be only one continuous task.
A periodic task performs a function at a specific interval.
• Whenever the time for the periodic task expires, the task interrupts any lower priority tasks, executes once, and then returns control to where the previous task left off.
• You can configure the time period from 0.1...2000
s. The default is 10 ms. It is also controller and configuration dependent.
• The performance of a periodic task depends on the type of Logix5000 controller and on the logic in the task.
An event task performs a function only when a specific event (trigger) occurs. The trigger for the event task can be the following:
• A consumed tag trigger
• An EVENT instruction
• An axis trigger
• A motion event trigger
The ControlLogix controller supports up to 32 tasks, only one of which can be continuous.
A task can have up to 100 separate Programs
, each with its own executable routines and program-scoped tags. Once a task is triggered (activated), all the programs assigned to the task execute in the order in which they are grouped.
Programs can appear only once in the Controller Organizer and cannot be shared by multiple tasks.
156 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Develop Applications Chapter 10
Task Priority
Each task in the controller has a priority level. The operating system uses the priority level to determine which task to execute when multiple tasks are triggered. A higher priority task will interrupt any lower priority task. The continuous task has the lowest priority and is always interrupted by a periodic or event task.
You can configure periodic tasks to execute from the lowest priority of 15 up to the highest priority of 1. Configure the task priority using the Task Properties dialog box.
Figure 32 - Configure Task Priority
Programs
The controller operating system is a preemptive multitasking system that is IEC
1131-3 compliant. This system provides the following:
• Programs to group data and logic
• Routines to encapsulate executable code written in a single programming language
Each program contains the following:
• Program tags
• A main executable routine
• Other routines
• An optional fault routine
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 157
Chapter 10 Develop Applications
Figure 33 - Program Within a Control Application
RSLogix 5000 Control Application
Controller Fault Handler
Task 8
Task 1
Configuration
Status
Watchdog
Program 32
Program 1
Main Routine
Program (local)
Tags
Fault Routine
Other Routines
Controller (global) Tags I/O Data
Figure 34 - Programs in RSLogix 5000 Software
System-shared Data
158 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Develop Applications Chapter 10
Scheduled and Unscheduled Programs
The scheduled programs within a task execute to completion from first to last.
Programs that aren’t attached to any task show up as unscheduled programs.
Unscheduled programs within a task are downloaded to the controller with the entire project. The controller verifies unscheduled programs but does not execute them.
You must schedule a program within a task before the controller can scan the program. To schedule an unscheduled program, use the Program/Phase Schedule tab of the Task Properties dialog box.
Figure 35 - Scheduling an Unscheduled Program
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 159
Chapter 10 Develop Applications
Routines
A routine is a set of logic instructions in a single programming language, such as
Ladder Diagram (ladder logic). Routines provide the executable code for the project in a controller. A routine is similar to a program file or subroutine in a
PLC or SLC processor.
Each program has a main routine. This is the first routine to execute when the controller triggers the associated task and calls the associated program. Use logic, such as the Jump to Subroutine ( JSR) instruction, to call other routines.
You can also specify an optional program fault routine. The controller executes this routine if it encounters an instruction-execution fault within any of the routines in the associated program.
Figure 36 - Routines in a Control Application
RSLogix 5000 Control Application
Controller Fault Handler
Task 8
Task 1
Configuration
Status
Watchdog
Program 32
Program 1
Main Routine
Program (local)
Tags
Fault Routine
Other Routines
Controller (global)
Tags
I/O Data System-shared Data
Figure 37 - Routines in RSLogix 5000 Software
160
Routine
Routine
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Develop Applications Chapter 10
Tags
Controller Organizer - Main Program Tags
With a Logix5000 controller, you use a tag (alphanumeric name) to address data
(variables). In Logix5000 controllers, there is no fixed, numeric format. The tag name itself identifies the data. This lets you do the following:
• Organize your data to mirror your machinery.
• Document your application as you develop it.
This example shows data tags created within the scope of the Main Program of the controller.
Figure 38 - Tags Example
Program Tags Window - Main Program Tags
Analog I/O Device
Integer Value
Storage Bit
Counter
Timer
Digital I/O Device
There are several guidelines for creating and configuring program tags for optimal task and program execution. For more information, see the Logix5000
Controllers and I/O Tag Data Programming Manual, publication 1756-PM004 .
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 161
Chapter 10 Develop Applications
Programming Languages
The ControlLogix controller supports these programming languages, both online and offline.
Table 42 - ControlLogix Controller Programming Languages
Language
Relay ladder
Is best-used in programs with
Continuous or parallel execution of multiple operations (not sequenced)
Boolean or bit-based operations
Complex logical operations
Message and communication processing
Machine interlocking
Operations that service or maintenance personnel may have to interpret in order to troubleshoot the machine or process
Function block diagram Continuous process and drive control
Loop control
Calculations in circuit flow
Sequential function chart (SFC) High-level management of multiple operations
Repetitive sequence of operations
Batch process
Motion control using structured text
State machine operations
Structured text Complex mathematical operations
Specialized array or table loop processing
ASCII string handling or protocol processing
For information about programming in these languages, see the Logix5000
Controllers Common Procedures Programming Manual, publication
1756-PM001 .
162 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Develop Applications Chapter 10
Add-On Instructions
With version 16, or later, of RSLogix 5000 programming software, you can design and configure sets of commonly used instructions to increase project consistency. Similar to the built-in instructions contained in Logix5000 controllers, these instructions you create are called Add-On Instructions.
Add-On Instructions reuse common control algorithms. With them, you can do the following:
• Ease maintenance by animating logic for a single instance.
• Protect intellectual property with locking instructions.
• Reduce documentation development time.
You can use Add-On Instructions across multiple projects. You can define your instructions, obtain them from somebody else, or copy them from another project.
This table explains some of the capabilities and advantages of use Add-On
Instructions.
Table 43 - Add-On Instruction Capabilities
Capability
Save Time
Use Standard Editors
Export Add-On Instructions
Use Context Views
Create Custom Help
Apply Source Protection
Description
With Add-On Instructions, you can combine your most commonly used logic into sets of reusable instructions. You save time when you create instructions for your projects and then share them with others. Add-On Instructions increase project consistency because commonly used algorithms all work in the same manner, regardless of who implements the project.
You create Add-On Instructions by using one of three RSLogix 5000 software programming editors.
• Relay Ladder
• Function Block Diagram
• Structured Text
Once you have created instructions, you can use them in any RSLogix 5000 editor.
You can export Add-On Instructions to other projects as well as copy and paste them from one project to another.
Give each instruction a unique name so that you don’t accidentally overwrite another instruction of the same name.
Context views let you visualize an instruction’s logic for a specific instant, simplifying online troubleshooting of your Add-On Instructions. Each instruction contains a revision, a change history, and an auto-generated help page.
When you create an instruction, you enter information for the description fields in software dialogs, information that becomes what is known as Custom Help. Custom Help makes it easier for you to get the help you need when implementing the instructions.
As the creator of Add-On Instructions, you can limit users of your instructions to read-only access, or you can bar access to the internal logic or local parameters used by the instructions. This source protection lets you prevent unwanted changes to your instructions and protects your intellectual property.
Once defined in a project, Add-On Instructions behave similarly to the built-in instructions in Logix5000 controllers. They appear on the instruction tool bar for easy access, as do internal RSLogix 5000 software instructions.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 163
Chapter 10 Develop Applications
Controller Organizer
Figure 39 - Add-On Instructions in RSLogix 5000 Software
Instruction Toolbar
Monitoring Controller
Status
For more information about using Add-On Instructions, see the
Add-On Instructions Programming Manual, publication 1756-PM010 .
The ControlLogix controller uses Get System Value (GSV) and Set System Value
(SSV) instructions to get and set (change) controller data. The controller stores system data in objects. There is no status file, as in the PLC-5 processor.
The GSV instruction retrieves the specified information and places it in the destination. The SSV instruction sets the specified attribute with data from the source. Both instructions are available from the Input/Output tab of the
Instruction toolbar.
Figure 40 - GSV and SSV Instructions for Monitoring
164 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Develop Applications Chapter 10
When you add a GSV/SSV instruction to the program, the programming software displays the valid object classes, object names, and attribute names for each instruction. For the GSV instruction, you can get values for all the available attributes. For the SSV instruction, the software displays only those attributes you are allowed to set.
Some object types appear repeatedly, so you may have to specify the object name.
For example, there can be several tasks in your application. Each task has its own
TASK object that you access by the task name.
There are several objects and attributes that you can use the GSV and SSV instructions to monitor and set the system. For more information about GSV instructions, SSV instructions, objects, and attributes see the Logix5000
Controllers General Instructions Reference Manual, publication 1756-RM003 .
Monitoring I/O Connections
If communication with a device in the I/O configuration of the controller does not occur for 100 ms or 4 times the RPI, whichever is less, communication times out and the controller produces these warnings:
• An I/O fault status code is indicated on the status display of the 1756-L7x controller.
• The I/O status indicator on the front of the 1756-L6x controller flashes green.
• A
!
shows over the I/O configuration folder and over the devices that have timed out.
• A module fault code is produced, which you can access via the following:
– The Module Properties dialog box
– A GSV instruction
For more information about I/O faults, see the Major, Minor, and I/O Faults
Programming Manual, publication 1756-PM014 .
Determine if I/O Communication has Timed Out
In the programming example, the instructions are used to complete these tasks.
This example could be used with either the 1756-L7 x or 1756-L6x controllers:
• The GSV instruction gets the status of the I/O status indicator (via the
LEDStatus attribute of the Module object) and stores it in the
IO_LED tag.
• IO_LED is a DINT tag that stores the status of the I/O status indicator or status display on the front of the controller.
• If IO_LED equals 2, than at least one I/O connection has been lost and the Fault_Alert is set.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 165
Chapter 10 Develop Applications
Figure 41 - GSV Used to Identify I/O Timeout
For more information about attributes available with the Module object, see the
Logix5000 Controllers General Instructions Reference Manual, publication
1756-RM003 .
Determine if I/O Communication to a Specific I/O Module has
Timed Out
If communication times out with a device (module) in the I/O configuration of the controller, the controller produces a fault code and fault information for the module. You can use GSV instructions to get fault code and information via the
FaultCode and FaultInfo attributes of the Module object.
For more information about attributes available with the Module object, see the
Logix5000 Controllers General Instructions Reference Manual, publication
1756-RM003 .
Interrupt the Execution of Logic and Execute the Fault Handler
Depending on your application, you might want an I/O connection error to cause the Controller Fault Handler to execute. To do so, set the module property that causes a major fault to result from an I/O connection error. The major fault then causes the execution of the Controller Fault Handler.
First, develop a routine in the Controller Fault Handler that can respond to I/O connection faults. Then, in the Module Properties dialog box of the I/O module or parent communication module, check Major Fault On Controller If
Connection Fails While in Run Mode.
166 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
I/O Module Properties
Figure 42 - I/O Connection Fault Causes Major Fault
Develop Applications Chapter 10
Parent Communication Module Properties
For more information about programming the Controller Fault Handler, see the
Major, Minor, and I/O Faults Programming Manual, publication 1756-PM014 .
System Overhead Time
Slice
The controller communicates with other devices at either a specified rate
(scheduled) or when there is processing time available to service the communication (service).
Service communication is any communication that you do not configure through the I/O configuration folder of the project.
The system overhead time slice specifies the percentage of time a controller devotes to service communication. However, if there is no continuous task, the overhead time slice has no affect. If you have both a periodic and continuous task, the System Overhead Time Slice entered in the Advanced tab of the Controller
Properties dialog box specifies continuous task/service communication ratio.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 167
Chapter 10 Develop Applications
The table shows the ratio between the continuous task and service communication at various system overhead time slices.
Ratio between Continuous Task and Service Communication
At this time slice
50%
66%
75%
80%
90%
10%
20%
25%
33%
The continuous task runs
1 ms
1 ms
1 ms
1 ms
1 ms
9 ms
4 ms
3 ms
2 ms
Service communication occurs for up to
1 ms
1 ms
1 ms
1 ms
1 ms
2 ms
3 ms
4 ms
9 ms
As shown in the table, for RSLogix 5000 version 16 and later, the system overhead time slice at 50% will stay fixed at 1 ms. The same applies for 66% and higher, except there are multiple 1 ms intervals. For example, at 66% there are two
1 ms intervals of consecutive time and at 90% there are nine 1 ms intervals of consecutive time.
Configure the System Overhead Time Slice
To configure the system overhead time slice, perform this procedure.
1.
In the Controller Organizer of RSLogix 5000 programming software, right-click the controller and choose Properties.
The Controller Properties dialog box appears.
168
2.
Click the Advanced tab.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Develop Applications Chapter 10
3.
Enter a numeric value in the System Overhead Time Slice box.
4.
Use either Run Continuous Task (default) or Reserve for System Tasks.
– The Run Continue Task radio button is used when there is no communication or background tasks to process; controller immediately returns to the continuous task.
– The Reserve for System Task radio button allocates the entire 1 ms of the system overhead time slice whether the controller has communication or background tasks to perform before returning back to the continuous task. This lets you simulate a communication load on the controller during design and programming before HMIs, controller to controller messaging, and so forth, are set up.
5.
Click OK.
Sample Controller Projects
RSLogix 5000 Enterprise programming software includes sample projects that you can copy and modify to fit your application. To access the sample projects, either choose Open Sample Project in the RSLogix 5000 Quick Start menu or use the menu commands (File > Open > Projects > Samples).
Figure 43 - Opening Sample Projects in RSLogix 5000 Software
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 169
Chapter 10 Develop Applications
Additional Resources
These documents contain additional information concerning related Rockwell
Automation products.
Resource
Logix5000 Controllers and I/O Tag Data Programming Manual, publication
1756-PM004
Logix5000 Controllers Common Procedures Programming Manual, publication 1756-PM001
Add-On Instructions Programming Manual, publication 1756-PM010
Logix5000 Controllers General Instructions Reference Manual, publication
1756-RM003
Description
Explains procedures for using and organizing I/O data tags.
Guides all user levels in developing projects for Logix5000 controllers and provides links to individual guides for information on topics such as import/export, messages, security, and programming in different languages.
Explains Add-On Instructions and how to use them.
Provides details about instructions for programming a Logix5000 controller.
Major, Minor, and I/O Faults Programming Manual, publication 1756-PM014 Explains major, minor, and I/O faults as well as the Controller Fault Handler.
Logix5000 Controllers Design Considerations Reference Manual, publication 1756-RM094
Provides advanced users with guidelines for system optimization and with system information to guide system design choices.
Logix5000 Controllers Execution Time and Memory Use Reference Manual, publication 1756-RM087
Assists in estimating the memory use and execution time of programmed logic and in selecting among different programming options.
You can view or download publications at http://www.rockwellautomation.com/literature . To order paper copies of technical documentation, contact your local Rockwell Automation distributor or sales representative.
170 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Chapter
11
Using the PhaseManager Tool
Topic
PhaseManager Tool versus Other State Models
Page
PhaseManager Overview
The PhaseManager tool lets you add equipment phases to your controller. An equipment phase helps you lay out your code in sections that are easier to write, find, follow, and change.
Table 44 - PhaseManager Terminology
Term
Equipment phase
State model
State machine
PHASE tag
Description
• As with a program, an equipment phase is run in a task and is given a set of routines and tags.
• Unlike a program, an equipment phase runs by a state model and lets you do one activity.
• A state model divides the operating cycle of your equipment into a series of states. Each state is an instant in the operation of the equipment, the actions, or conditions of the equipment at a given time.
• The state model of an equipment phase resembles that of the S88 and PackML state models.
An equipment phase includes an embedded state machine that does the following:
• Calls the routine associated with an active state
• Manages the transitions between states with minimal coding
• Makes sure that the equipment goes from state to state along an allowable path
When you add an equipment phase, RSLogix 5000 programming software makes a tag for the equipment phase. The tag uses the
PHASE data type.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 171
Chapter 11 Using the PhaseManager Tool
Figure 44 - PhaseManager Overview
A PHASE tag gives you the status of an equipment phase.
Controller
Controller Tags
Tasks
MainTask
Add Water Phase
Mix Phase
Drain Phase
Space Parts Phase
MainProgram
An equipment phase directs one activity of your equipment.
A state model divides the activity into a series of states.
Running State Routine
How to add water
My Equipment Program
Equipment phase instructions control the transitions between states and handle faults.
PSC POVR PCLF PRNP PATT
PCMD PFL PXRQ PPD PDET
Other code controls the specific actions of your equipment.
Water Feed Conveyor Enable Axes
Minimum System
Requirements
172
To develop PhaseManager programs, you need the following:
• A ControlLogix controller at firmware revision 16.0, or later
• A communication path to the controller
• RSLogix 5000 software, version 16.0 or later
To enable PhaseManager support, you need either the Full or Professional edition of RSLogix 5000 programming software, or RSLogix 5000 with PhaseManager software (catalog number 9324-RLDPMENE).
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Using the PhaseManager Tool Chapter 11
State Model Overview
Idle
Resetting
Reset
Start
Running
Complete
Reset
A state model defines what your equipment does under different conditions, and how the states relate to each other. Each state can be described as either an Acting state or Waiting state.
Table 45 - States in PhaseManager Software
State
Acting
Waiting
Description
Does something or several things for a certain time or until certain conditions are met.
An acting state runs once or repeatedly.
Shows that certain conditions are met and the equipment is waiting for the signal to go to the next state.
Hold
Figure 45 - PhaseManager State Transitions
Holding Held
Hold
Restart
Restarting
Your equipment can go from any state in the box to the stopping or aborting state.
Stop
Abort
Stopping
Abort
Aborting
Acting
Acting states represent the things your equipment does at a given time.
Stopped Aborted
Waiting
Waiting states represent the condition of your equipment when it is between acting states.
With a state model, you define the behavior of your equipment during Acting states.
Table 46 - Acting States in the PhaseManager State Model
State
Resetting
Running
Holding
Restarting
Stopping
Aborting
Question to be asked
How does the equipment get ready to run?
What does the equipment do to make product?
How does the equipment temporarily stop making product without making scrap?
How does the equipment resume production after holding?
What happens during a normal shutdown?
How does the equipment shut down if a fault or failure occurs?
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 173
Chapter 11 Using the PhaseManager Tool
How Equipment Changes States
The state model’s arrows show the states through which your equipment progresses:
• Each arrow is called a transition.
• A state model lets the equipment make only certain transitions. This restriction standardizes the equipment’s behavior so that other equipment using the same model will behave the same way.
Figure 46 - PhaseManager Transition Commands
= Transition
Command
Idle
Resetting
Start
Running
Hold
Done — No command. Use PSC instruction instead.
Your equipment can go from any state in the box when it receives a stop or abort commend.
Holding
Hold
Restarting
Restart
Held
Reset
Complete
Stop
Abort
Stopping
Abort
Aborting
Reset Stopped Aborted
Table 47 - PhaseManager Transitions
Type of Transition
Command
Done
Fault
Description
A command tells the equipment to do something. For example, the operator pushes the start button to begin production and the stop button to halt production.
The PhaseManager tool uses these commands:
Reset
Start
Stop
Hold
Restart
Abort
Equipment goes to a waiting state when it is finished with what it is doing. You do not give the equipment a command. Instead, you set up your code to signal when the phase state is finished.
A fault tells you that something out of the ordinary has happened. You set up your code to look for faults and take action if it finds any. If you want to shut down your equipment as quickly as possible when it detects a fault, set up your code to look for that fault and give the abort command if it finds it.
174 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Using the PhaseManager Tool Chapter 11
Manually Change States
With RSLogix 5000 programming software, you can manually change an equipment phase. To manually change a PhaseManager state, perform this procedure.
1.
Open the Equipment Phase Monitor.
2.
Take ownership of the equipment phase by clicking Owners and clicking
Yes.
3.
Click the command that initiates the state you need (for example, Start or
Reset).
4.
After you have finished manually changing the state, clicks Owners to release your ownership.
PhaseManager Tool versus
Other State Models
This table compares PhaseManager state models to other state models.
Table 48 - PhaseManager Tool and Other State Models
PhaseManager Tool
Resetting…Idle
Running…Complete
Subroutines or breakpoints
Holding…Held
Restarting
Stopping…Stopped
Aborting…Aborted
S88
Idle
Running…Complete
Pausing…Paused
Holding…Held
Restarting
Stopping…Stopped
Aborting…Aborted
PackML
Starting…Ready
Producing
Standby
Holding…Held
None
Stopping…Stopped
Aborting…Aborted
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 175
Chapter 11 Using the PhaseManager Tool
Equipment Phase
Instructions
The controller supports several equipment-phase relay ladder and structured text instructions.
PCMD
PFL
PCLF
PXRQ
PRNP
PPD
PATT
Table 49 - Instructions for Use with PhaseManager Tool
Instruction
PSC
PDET
POVR
Instruction Function
Signal a phase that the state routine is complete and to proceed to the next state.
Change the state or substate of a phase.
Signal a failure for a phase.
Clear the failure code of a phase.
Initiate communication with RSBizWare Batch software.
Clear the NewInputParameters bit of a phase.
Set up breakpoints within the logic of a phase.
Take ownership of a phase to either of the following:
• Prevent another program or RSBizWare Batch software from commanding a phase.
• Make sure another program or RSBizWare Batch software does not already own a phase.
Relinquish ownership of a phase.
Override a command.
For more information about instructions for use with equipment phases, see the
PhaseManager User Manual, publication LOGIX-UM001 .
Additional Resources
These documents contain additional information concerning related Rockwell
Automation products.
Resource
PhaseManager User Manual, publication LOGIX-UM001
Description
Provides steps, guidance, and examples for setting up and programming a
Logix5000 controller to use equipment phases.
You can view or download publications at http://www.rockwellautomation.com/literature . To order paper copies of technical documentation, contact your local Rockwell Automation distributor or sales representative.
176 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Chapter
12
Redundant Systems
Topic
ControlLogix Redundancy Overview
ControlNet Considerations in Redundant Systems
EtherNet/IP Considerations in Redundant Systems
Page
ControlLogix Redundancy
Overview
Redundancy provides more system availability by switching control to a secondary controller chassis if a fault occurs in the primary controller chassis.
The redundant system switches control from the primary to the secondary when these faults occur:
• Power loss to primary chassis
• Hardware or firmware failure of any module in the primary chassis
• A major fault in the user program on the primary controller
• Loss of communication between the primary chassis and remote
ControlNet or EtherNet/IP modules
• Disconnection of an Ethernet patch cable from an EtherNet/IP communication module in the primary chassis
• Removal or insertion of any module in the primary chassis
• A user command that causes a switchover
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 177
Chapter 12 Redundant Systems
Workstation
Figure 47 - ControlLogix Enhanced Redundancy System
HMI
Ethernet
Switch
Redundant Chassis
Primary
Logix5563
Redundancy Module EtherNet/IP
ControlNet
PRI COM OK
Secondary
Logix5563
Redundancy Module EtherNet/IP ControlNet
PRI COM OK
178
I/O Connected via
ControlNet
ControlNet
DC INPUT
ST
AT
ST
AT
Diagnostic
ST
AT
ST
AT
DC OUTPUT
Diagnostic
ST
AT
ST
AT
Analog Input
Diagnostic
Analog Output
ST
AT
ST
AT
Diagnostic
Relay Module ControlNet
I/O can be connected via an EtherNet/IP network beginning with Enhanced Redundancy System revision 19.50.
Redundancy requires no additional programming and is transparent to any devices connected over an EtherNet/IP or ControlNet network.
Redundancy modules placed in each redundant chassis maintain the communication between the redundant chassis.
Depending on how you organize your RSLogix 5000 project, outputs may or may not experience a change in state (bump) during a switchover:
• During the switchover, outputs that are controlled by the highest priority task will experience a bumpless switchover. For example, outputs will not revert to a previous state.
• Outputs in lower priority tasks may experience a change of state.
For detailed information about ControlLogix redundancy systems, see the
ControlLogix Redundancy System User Manual, publication 1756-UM523 .
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
System Requirements
Redundant Systems Chapter 12
Most redundant systems must use at least these system components. For some applications, the ControlNet and EtherNet/IP modules are optional.
Table 50 - System Requirements
Quantity Item
2 ControlLogix chassis
2
2
ControlLogix power supply
ControlLogix controller
2
2
2
1
2
Notes
Both chassis must be the same size.
Must be the same in each chassis.
ControlLogix ControlNet communication module
ControlLogix EtherNet/IP communication modules
Redundancy module
Redundancy module cable (fiber-optic)
Additional ControlNet nodes
• Use either 1756-L6x or 1756-L7x controllers.
• Use the same catalog number, series, firmware revision, and memory size controllers in each chassis.
• Same slot placement.
• Use 1756-CN2/B, 1756-CN2R/B, or 1756-CN2RXT modules.
• ControlNet modules in both chassis must be identical in firmware revision, in series, slot placement, and module type.
• You must use enhanced ControlNet communication modules in an enhanced redundancy system. Enhanced communication modules contain a ’2’ in their catalog number. For example, the 1756-EN2T module.
• Use the 1756-EN2T, 1756-EN2TXT, or 1756-EN2TR modules.
• Must be identical in firmware revision, slot placement and module type.
• You must use enhanced EtherNet/IP communication modules in an enhanced redundancy system. Enhanced communication modules contain a ’2’ in their catalog number. For example, the 1756-EN2T module.
• Use 1756-RM or 1756-RMXT modules.
• Redundancy modules in both chassis must be identical in firmware revision and slot placement.
• For L7x high performance systems, RM modules must be
RM/B (series B) and must have the same series and firmware revision in both chassis.
• Use the 1756-RMCx cable.
• Standard lengths are available.
• Place all I/O in remote chassis or DIN rails.
• Add at least two nodes to each ControlNet network in addition to the redundant chassis pair.
• For enhanced redundancy, you must have one other keeper-capable ControlNet device at a node address lower than the node addresses of the ControlNet modules in the redundant chassis.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 179
Chapter 12 Redundant Systems
System Considerations
When you are configuring a redundant ControlLogix system, these considerations specific to modules in the redundant chassis must be made.
Items in Primary and
Secondary Chassis
ControlLogix controller
Consideration
Communication modules
I/O modules
• When configured for redundancy, the secondary controller automatically receives and buffers data.
• A redundant controller uses twice as much data memory and I/O memory space as a nonredundant controller.
• A redundant controller has a significantly longer scan time than a nonredundant controller.
• The ControlLogix Enhanced Redundancy User Manual, publication 1756-UM535 , provides detailed information about minimizing the scan time impact.
• You do not need a redundancy-specific version of RSLogix 5000 programming software, but it must match your
Enhanced Redundancy System revision level.
• As many as seven communication modules can reside in a redundant controller chassis, in any combination of
EtherNet/IP modules and ControlNet modules.
• To connect to other networks, bridge through another ControlLogix chassis outside the redundant system.
• For best results, use a separate networks for HMI and I/O communication.
• All I/O is remote from the redundant controller chassis.
• Beginning with Enhanced Redundancy System revision 19.50, EtherNet/IP networks in redundant systems can be used for remote I/O or produced/consumed data.
Redundant power supplies The 1756-PA75R and 1756-PB75R redundant power supplies provide reliable chassis power.
Redundant ControlNet media Redundant media provide more reliable ControlNet communication.
For complete information about designing and planning modules for use in your redundant ControlLogix chassis, see the ControlLogix Enhanced Redundancy
User Manual, publication 1756-UM535 .
180 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Redundant Systems Chapter 12
Enhanced versus Standard Redundancy
While the enhanced and standard redundancy systems operate in a similar manner, there are some key differences between the two platforms. This table compares the enhanced and standard redundancy system features.
Table 51 - Comparison of Enhanced Redundancy to Standard Redundancy
Feature
Supports enhanced ControlLogix ControlNet and EtherNet/IP communication modules, for example, the 1756-CN2/B or 1756-EN2T modules
Supports standard ControlLogix ControlNet and EtherNet/IP communication modules, for example, the 1756-CNB/D or
1756-ENBT modules
Compatible with the single-slot 1756-RM redundancy modules
Enhanced
System
(1)
Compatible with the double-slot 1757-SRM redundancy modules
Support for all 1756-L6x and 1756-L7x ControlLogix controllers
Use of ControlLogix-XT system components, for example, the
1756-L63XT controller and the 1756-CN2XT module
Availability of I/O over an EtherNet/IP network, including Redundant
I/O systems
Standard
System
(1) Availability of some features supported in enhanced redundancy are dependent on the system revision used.
For more information, see ControlLogix Enhanced Redundancy System User Manual, publication 1756-UM535.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 181
Chapter 12 Redundant Systems
Build a Redundant System
To build a typical redundant system, perform this procedure.
1.
Install a ControlLogix chassis and power supply.
2.
To the primary chassis, add 1756-L6 x or 1756-L7x controllers.
Please note that you cannot mix 1756-L6x and 1756-L7x controllers in the same chassis.
3.
Add one or more ControlNet or EtherNet/IP communication modules.
4.
Add one redundancy module.
5.
Set up a secondary chassis that is identical to the primary chassis.
IMPORTANT Components in the redundant chassis pair must be identical in module configuration.
6.
Connect the redundancy modules in both chassis.
7.
Add I/O modules to ControlNet or EtherNet/IP networks.
8.
Add operator interfaces to ControlNet or EtherNet/IP networks.
For detailed information on designing and building an enhanced redundant system, refer to the ControlLogix Enhanced Redundancy System User Manual, publication 1756-UM535 .
ControlNet Considerations in Redundant Systems
You can have as many as seven ControlNet communication modules in a redundant chassis.
IMPORTANT With each ControlNet network, you must have at least two nodes external to the redundant controller chassis to avoid timeouts on switchover.
The lowest node of each ControlNet network must be outside the redundant controller chassis.
For information on ControlNet considerations for enhanced redundant systems, refer to the ControlLogix Enhanced Redundancy System User Manual, publication 1756-UM535 .
182 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Redundant Systems Chapter 12
EtherNet/IP Considerations in Redundant Systems
You can have as many as seven EtherNet/IP modules in the redundant chassis.
In a redundant system, use EtherNet/IP for HMI communication or inter-controller messaging only. HMI can communicate directly to with the primary controller. You no longer need RSLinx Alias Topics.
ControlLogix redundancy supports EtherNet/IP for I/O control or producing and consuming data beginning with Enhanced Redundancy System revision
19.50, and can be used for the following:
• 1715 Redundant I/O
• Remote I/O modules
• HMI connections to the primary controller
• Producing and consuming data
For information on EtherNet/IP considerations for enhanced redundant systems, refer to the ControlLogix Enhanced Redundancy System User Manual, publication 1756-UM535 .
IP Address Swapping
Firmware revision 13, and later, supports IP address swapping in redundant systems. With IP address swapping, you configure the primary and secondary
EtherNet/IP modules with the same IP address. The primary EtherNet/IP module takes the IP address; the secondary module takes that address plus one in the last address segment.
On a switchover, the EtherNet/IP modules swap IP addresses. HMI devices automatically continue to communicate with the new primary controller because the IP addresses were swapped. Because of the way EtherNet/IP modules work, during a switchover, communication between the controller and an HMI device halts for several seconds, typically less than a minute.
For bumpless HMI connection, use either of the following:
• A dedicated ControlNet network
• A bridged connection from an EtherNet/IP network to a ControlNet network
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 183
Chapter 12 Redundant Systems
Redundancy and Scan Time
At the end of every program, the primary controller synchronizes and crossloads fresh data to the secondary controller. This keeps the secondary controller up-to-date and ready to take over. It also increases the scan time when compared to a nonredundant system.
The amount of time a crossload consumes depends on how much data the primary controller has to crossload:
• The primary controller synchronizes and crossloads any tag to which an instruction wrote a value, even the same value, since the last crossload.
• Crossloading also requires a small amount of overhead time (1 ms per crossload) to tell the secondary controller which program the primary controller is executing.
Redundancy firmware revision 16.53, or later, provides the ability to limit which programs are followed by synchronization and data crossloading. In many applications, changing this can reduce the overall impact to the task scan time by reducing the number of times a data area is synchronized. Removing a synchronization point results in 1 ms of overhead time saved, in addition to any time that was used to crossload the data.
For complete details about the scan time of a redundant system, see the
ControlLogix Enhanced Redundancy System User Manual, publication
1756-UM535 .
184 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Redundant Systems Chapter 12
Additional Resources
These documents contain additional information concerning related Rockwell
Automation products.
Resource Description
ControlLogix Redundancy System User Manual, publication 1756-UM523 Guides the design, development, and implementation of a standard
ControlLogix redundancy system.
ControlLogix Enhanced Redundancy System User Manual, publication
1756-UM535
ControlLogix Enhanced Redundancy System, Revision 19.50 Release Notes, publication 1756-RN684 .
Guides the design, development, and implementation of an enhanced
ControlLogix redundancy system.
Describes the enhancements, corrected anomalies, and known anomalies specific to the current firmware revision for an enhanced redundancy system, revision 19.50.
ControlLogix Enhanced Redundancy System, Revision 16.81 Release Notes, publication 1756-RN650
Integrated Architecture and CIP Sync Configuration Application Technique, publication IA-AT003
Describes the enhancements, corrected anomalies, and known anomalies specific to the current firmware revision for an enhanced redundancy system, revision 16.81 or later.
Provides detailed and comprehensive information about how to apply CIP
Sync technology to synchronize clocks in a Logix control system.
You can view or download publications at http://www.rockwellautomation.com/literature . To order paper copies of technical documentation, contact your local Rockwell Automation distributor or sales representative.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 185
Chapter 12 Redundant Systems
Notes:
186 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Introduction to SIL
Chapter
13
SIL 2 Certification
Topic
Page
Programming and Debugging Tool (PADT) 187
Typical SIL2 Configurations 188
Certain catalog numbers of the ControlLogix system are type-approved and certified for use in SIL2 applications according to these standards:
• IEC 61508
• IEC 61511
Approval requirements are based on the standards current at the time of certification.
These requirements consist of mean time between failures (MTBF), probability of failure, failure rates, diagnostic coverage and safe failure fractions that fulfill
SIL2 criteria. The results make the ControlLogix system suitable up to, and including, SIL2. When the ControlLogix system is in the Maintenance or
Programming mode, the user is responsible for maintaining a safe state.
The TÜV Rheinland Group has approved the ControlLogix system for use in up to, and including, SIL 2 safety related applications in which the de-energized state is typically considered to be the safe state.
In addition, specific configuration and programming considerations described in the Using ControlLogix in SIL2 Applications Safety Reference Manual, publication 1756-RM001 , must be made.
Programming and Debugging Tool (PADT)
For support in creation of programs, the Programming and Debugging Tool
(PADT) is required. The PADT for the ControlLogix system is RSLogix 5000 software, per IEC 61131-3, and the Using ControlLogix in SIL2 Applications
Safety Reference Manual, publication 1756-RM001 .
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 187
Chapter 13 SIL 2 Certification
Typical SIL2 Configurations
SIL2-certified ControlLogix systems can be used in non-redundancy or redundancy configurations. For the purposes of documentation, the various levels of availability that can be achieved by using various ControlLogix system configurations are referred to as fail-safe, high-availability, or fault-tolerant.
This table lists each system configuration and the hardware that is part of the system’s safety loop.
Table 52 - SIL2 Configurations and Hardware Summary
With this system configuration
Fail-safe Configuration, page 189
The safety loop includes
• Nonredundant controller
• Nonredundant communication modules
• Nonredundant remote I/O
High-availability Configuration, page 190
• Redundant controllers
• Redundant communication modules
• Nonredundant remote I/O
Fault-tolerant Configuration, page 191
• Redundant controllers
• Redundant communication modules
• Redundant remote I/O
• I/O termination boards
IMPORTANT Note that the system user is responsible the tasks listed here when any of the ControlLogix SIL2 system configurations are used:
• The setup, SIL rating, and validation of any sensors or actuators connected to the ControlLogix control system.
• Project management and functional testing.
• Programming the application software and the module configuration according to the descriptions in the following chapters.
The SIL2 portion of the certified system excludes the development tools and display/human machine interface (HMI) devices; these tools and devices are not part of the safety loop.
188 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Overall Safety Loop
Sensor
SIL 2 Certification Chapter 13
Fail-safe Configuration
In a fail-safe configuration, the hardware used in the safety loop is not redundant.
Therefore, if a fault occurs anywhere in the SIL2 system, the system is programmed to fail to safe.
The failure to safe is typically an emergency shutdown where all outputs are de-energized.
Figure 48 - Fail-safe ControlLogix Configuration
Controller Chassis
E
N
B
T
B
R
C
N
ControlNet
SIL2-certified ControlLogix Safety Loop
Remote I/O Chassis
I/O
C
N
B
R
Actuator
I/O
B
T
E
N
EtherNet/IP
This figure shows a typical SIL loop that does not use redundancy. This figure shows the following:
• Overall safety loop
• ControlLogix portion of the overall safety loop
TIP When certain considerations are made, it possible to connect to remote I/O via an EtherNet/IP network. To connect to remote I/O using an EtherNet/IP network, you must make considerations similar to those required for a SIL2-certified ControlNet network.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 189
Chapter 13 SIL 2 Certification
High-availability Configuration
In the high-availability configuration, redundant controller chassis are used to increase the availability of the control system. The modules in the redundant controller chassis include the redundancy modules and ControlNet modules for redundant communication, as well as the ControlLogix controllers.
Figure 49 - Typical SIL Loop with Controller Chassis Redundancy
Programming Software
For SIL applications, a programming terminal is not normally connected.
HMI
For Diagnostics and Visualization (read-only access to controllers in the safety loop).
Overall Safety Loop
Sensor
Plant-wide Ethernet/Serial
Primary Chassis
E
N
2
T
C
N
2
C
N
2
SIL2-certified ControlLogix components’ portion of the overall safety loop.
Remote I/O Chassis
R
M
I/O
C
N
2
Actuator
ControlNet
Secondary chassis
E
N
2
T
C
N
2
C
N
2
R
M
To other safety related
ControlLogix and remote
I/O chassis.
190
ControlNet
To nonsafety related systems outside the ControlLogix portion of the SIL2-certified loop.
IMPORTANT The high-availability ControlLogix system is fault-tolerant only for the devices in the primary/secondary controller chassis. The rest of the high-availability system is not considered to be fault-tolerant.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
SIL 2 Certification Chapter 13
Figure 49 on page 190 shows a typical SIL loop that uses redundancy, including the following:
• The overall safety loop
• The ControlLogix portion of the overall safety loop
• How other devices (for example, HMI) connect to the loop, while operating outside the loop
Fault-tolerant Configuration
The most recently-certified ControlLogix SIL2 configuration is the fault-tolerant configuration. The fault-tolerant configuration of the
ControlLogix system uses fully-redundant controllers, communication modules, and remote I/O.
Figure 50 - Fault-tolerant Configuration
Primary Chassis
SIL2-certified ControlLogix safety loop
Secondary Chassis
PRI COM OK
PRI COM OK
I/O Chassis A
DC OUTPUT
ST
ST 8 9
2 3 5 6 7 O
K
10 1112 13 14 15
DIAGNOSTIC
DC INTPUT
ST
ST 8 9
2 3
10
5 6 7
1112 13 14 15
O
K
DIAGNOSTIC
ANALOG INTPUT
CAL
OK
DC OUTPUT
ST
ST
2 3 5 6 7 O
K
8 9 10 1112 13 14 15
DIAGNOSTIC
ANALOG INTPUT
CAL
OK
DC INTPUT
ST
ST 8 9
2 3
10
5 6 7
1112 13 14 15
O
K
DIAGNOSTIC
I/O Chassis B
ST
ST 8 9 10
DC OUTPUT
2 3 5 6 7
1112 13 14 15
DIAGNOSTIC
O
K
DC INTPUT
ST
ST 8 9
2 3
10
5 6 7
1112 13 14 15
O
K
DIAGNOSTIC
ANALOG INTPUT
CAL
OK
DC OUTPUT
ST
ST 8 9
2 3
10
5 6 7
1112 13 14 15
O
K
DIAGNOSTIC
ANALOG INTPUT
CAL
OK
DC INTPUT
ST
ST 8 9
2 3
10
5 6 7
1112 13 14 15
O
K
DIAGNOSTIC
Analog Input
Termination
Board
Field
Device
Digital Input
Termination
Board
Field
Device
Digital Output
Termination
Board
Field
Device
The fault-tolerant configuration uses safety and programming principles described in this manual, as well as programming and hardware described in the application technique manuals.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 191
Chapter 13 SIL 2 Certification
For more information about the ControlLogix SIL2- certified fault-tolerant system, see the application technique manual that corresponds with your application.
Table 53 - ControlLogix SIL2 System Configuration Manuals
If using
SIL2 Fault-tolerant I/O subroutines
(available for use with RSLogix 5000 software, version 15 and later)
SIL2 Fault-tolerant I/O Add-On Instructions (available for use with
RSLogix 5000 software, version 16 and later)
Then reference this manual
ControlLogix SIL2 System Configuration Using RSLogix 5000 Subroutines, publication 1756-AT010
ControlLogix SIL2 System Configuration Using RSLogix 5000 Subroutines, publication 1756-AT012
Additional Resources
These documents contain additional information concerning related Rockwell
Automation products.
Resource
Using ControlLogix in SIL 2 Applications Reference Manual, publication 1756-RM001
ControlLogix SIL2 System Configuration Using RSLogix 5000 Subroutines, publication 1756-AT010
ControlLogix SIL2 System Configuration Using RSLogix 5000 Subroutines, publication 1756-AT012
Description
Provides list of ControlLogix system components that meet SIL 2 requirements as well as programming requirements.
Explains how to use subroutines provided by Rockwell Automation to configure a fault-tolerant system.
Explains how to use Add-On Instructions provided by Rockwell Automation to configure a fault-tolerant system.
You can view or download publications at http://www.rockwellautomation.com/literature . To order paper copies of technical documentation, contact your local Rockwell Automation distributor or sales representative.
192 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Appendix
A
Status Indicators
Topic Page
1756-L7x Controller Status Display and Indicators 193
1756-L7x Controller Status Display
1756-L7x Controller Status Indicators
1756-L7x Controller Status
Display and Indicators
The 1756-L7 x controllers have four status indicators and one four-character scrolling status display.
Figure 51 - 1756-L7x Status Display and Indicators
Logix557x
Scrolling Status Display, see
Status Indicators, see
RUN FORCE SD OK
RU
N REM PROG
32009-MC
1756-L7x Controller Status
Display
The 1756-L7 x controller status display scrolls messages that provide information about the controller’s firmware revision, ESM status, project status, and major faults.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 193
Appendix A Status Indicators
General Status Messages
The messages described in this table are typically indicated upon powerup, powerdown, and while the controller is running to show the status of the controller and the ESM.
Table 54 - General Status Messages
Message
No message is indicated
TEST
PASS
SAVE
LOAD
UPDT
CHRG
1756-L7x/X
Rev XX.xxx
No Project
Project Name
BUSY
Corrupt Certificate
Received
Corrupt Image
Received
ESM Not Present
ESM Incompatible
ESM Hardware
Failure
Interpretation
Either of the following conditions are true:
• The controller is off
• A major nonrecoverable fault (MNRF) has occurred
Check the OK indicator to determine if the controller is powered and determine the state of the controller.
Power-up tests are being conducted by the controller.
Power-up tests have been successfully completed.
A project is being saved to the SD card at powerdown. You can also view the SD Indicator (see page 202 ) for additional status information.
Allow the save to complete before:
• removing the SD card.
• disconnecting power.
A project is being loaded from the SD card at controller powerup. You can also view the SD Indicator (see page 202 ) for additional status information.
Allow the load to complete before doing the following:
• Removing the SD card
• Disconnecting power
• Removing the ESM module
A firmware upgrade is being conducted from the SD card upon powerup. You can also view the SD Indicator (see page 202 ) for additional status information.
If you do not want the firmware to update upon powerup, change the controller’s Load Image property.
The capacitor-based ESM is being charged.
The controller catalog number and series.
The major and minor revision of the controller’s firmware.
No project is loaded on the controller.
To load a project, do one of the following:
• Use RSLogix 5000 programming software to download the project to the controller
• Use a SD card to load a project to the controller
The name of the project that is currently loaded on the controller. The name indicated is based on the project name specified in
RSLogix 5000 software.
The I/O modules associated with the controller are not yet fully-powered.
Allow time for powerup and I/O module self-testing.
The security certificate associated with the firmware is corrupted.
Go to http://www.rockwellautomation.com/support/ and download the firmware revision you are trying to upgrade to. Replace the firmware revision you have previously installed with that posted on the Technical Support website.
The firmware file is corrupted.
Go to http://www.rockwellautomation.com/support/ and download the firmware revision you are trying to upgrade to. Replace the firmware revision you have previously installed with that posted on the Technical Support website.
An ESM is not present and the controller cannot save the application at powerdown.
Insert a compatible ESM, and, if using a capacitor-based ESM, do not remove power until the ESM is charged.
The ESM is incompatible with the memory size of the controller.
Replace the incompatible ESM with a compatible ESM.
A failure with the ESM has occurred and the controller is incapable of saving of the program in the event of a powerdown.
Replace the ESM before removing power to the controller so the controller program is saved.
194 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Status Indicators Appendix A
Table 54 - General Status Messages
Message
ESM Energy Low
ESM Charging
Flash in Progress
Firmware Installation
Required
SD Card Locked
Interpretation
The capacitor-based ESM does not have sufficient energy to enable the controller to save the program in the event of a powerdown.
Replace the ESM.
The capacitor-based ESM is charging.
Do not remove power until charging is complete.
A firmware upgrade initiated via ControlFLASH or AutoFlash utilities is in progress.
Allow the firmware upgrade to complete without interruption.
The controller is using boot firmware (that is revision 1.xxx) and requires a firmware upgrade.
Upgrade controller firmware.
An SD card that is locked is installed.
Fault Messages
If the controller is faulted, these messages may be indicated on the status display.
Table 55 - Fault Messages
Message
Major Fault TXX:CXX message
Interpretation
A major fault of Type XX and Code XX has been detected.
For example, if the status display indicates Major Fault T04:C42 Invalid JMP Target, then a JMP instruction is programmed to jump to an invalid LBL instruction.
For details about major recoverable faults, see the Logix5000 Major, Minor, and I/O Fault Codes Programming
Manual, publication 1756-PM014 .
I/O Fault Local:X #XXXX message An I/O fault has occurred on a module in the local chassis. The slot number and fault code are indicated along with a brief description.
For example, I/O Fault Local:3 #0107 Connection Not Found indicates that a connection to the local I/O module in slot three is not open.
Take corrective action specific to the type of fault indicated.
For details about each I/O fault code, see the Logix5000 Major, Minor, and I/O Fault Codes Programming Manual, publication 1756-PM014 .
I/O Fault ModuleName #XXXX message
An I/O fault has occurred on a module in a remote chassis. The name of the faulted module, as configured in the I/O
Configuration tree of RSLogix 5000 software, is indicated with the fault code and brief description of the fault.
For example, I/O Fault My_Module #0107 Connection Not Found indicates that a connection to the module named
’My_Module’ is not open.
Take corrective action specific to the type of fault indicated.
For details about each I/O fault code, see the Logix5000 Major, Minor, and I/O Fault Codes Programming Manual, publication 1756-PM014 .
I/O Fault ModuleParent:X #XXXX message
X I/O Faults
An I/O fault has occurred on a module in a remote chassis. The module’s parent name is indicated because no module name is configured in the I/O Configuration tree of RSLogix 5000 software. In addition, the fault code is indicated with a brief description of the fault.
For example, I/O Fault My_CNet:3 #0107 Connection Not Found indicates that a connection to a module in slot 3 of the chassis with the communication module named ’My_CNet’ is not open.
Take corrective action specific to the type of fault indicated.
For details about each I/O fault code, see the Logix5000 Major, Minor, and I/O Fault Codes Programming Manual, publication 1756-PM014 .
I/O faults are present and X = the number of I/O faults present.
In the event of multiple I/O faults, the controller indicates the first fault reported. As each I/O fault is resolved, the number of faults indicated decreases and the next fault reported is indicated by the I/O Fault message.
Take corrective action specific to the type of fault indicated.
For details about each I/O fault code, see the Logix5000 Major, Minor, and I/O Fault Codes Programming Manual, publication 1756-PM014 .
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 195
Appendix A Status Indicators
Major Recoverable Fault Messages
Major recoverable faults are indicated by Major Fault T XX:CXX message on the controller status display. This table lists specific fault types, codes, and the associated messages as they are shown on the status display.
For detailed descriptions and suggested recovery methods for major recoverable faults, see the Logix5000 Major, Minor, and I/O Fault Codes Programming
Manual, publication 1756-PM014
.
Table 56 - Major Recoverable Fault Status Messages
4
4
4
4
4
4
3
4
3
3
1
3
1
1
Type
1
4
4
4
4
4
4
31
34
42
82
23
16
20
21
62
16
20
21
Code
1
60
61
83
84
89
90
91
92
Message
Run Mode Powerup
Non-recoverable
Non-recoverable – Diagnostics Saved
Non-recoverable – Program Saved
I/O Connection Failure
Chassis Failure
Connection Failure
Unknown Instruction
Invalid Array Subscript
Control Structure LEN or POS < 0
Invalid JSR Parameter
Timer Failure
Invalid JMP Target
SFC Jump Back Failure
Value Out of Range
Stack Overflow
Invalid Target Step
Invalid Instruction
Invalid Context
Invalid Action
196 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Table 56 - Major Recoverable Fault Status Messages
11
11
11
11
11
11
11
11
11
11
11
11
7
8
11
11
18
18
18
18
11
11
11
11
7
7
6
7
4
4
4
4
4
4
4
4
Type
4
4
Message
User-defined
11
12
13
14
7
8
9
10
5
6
3
4
1
2
43
1
3
4
1
2
15
16
32
33
1
40
41
42
996
997
998
999
992
993
994
995
Code
990
991
Task Watchdog Expired
Save Failure
Bad Restore Type
Bad Restore Revision
Bad Restore Checksum
Keyswitch Change Ignored
Positive Overtravel Limit Exceeded
Negative Overtravel Limit Exceeded
Position Error Tolerance Exceeded
Encoder Channel Connection Fault
Encoder Noise Event Detected
SERCOS Drive Fault
Synchronous Connection Fault
Servo Module Fault
Asynchronous Connection Fault
Motor Fault
Motor Thermal Fault
Drive Thermal Fault
SERCOS Communications Fault
Inactive Drive Enable Input Detected
Drive Phase Loss Detected
Drive Guard Fault
Motion Task Overlap Fault
CST Reference Loss Detected
CIP Motion Initialization Fault
CIP Motion Initialization Fault Mfg
CIP Motion Axis Fault
CIP Motion Axis Fault Mfg
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Status Indicators Appendix A
197
Appendix A Status Indicators
198
Table 56 - Major Recoverable Fault Status Messages
18
18
18
18
18
Type
18
18
7
8
9
10
128
Code
5
6
Message
CIP Motion Fault
CIP Module Fault
Motion Group Fault
CIP Motion Configuration Fault
CIP Motion APR Fault
CIP Motion APR Fault Mfg
CIP Motion Guard Fault
I/O Fault Codes
I/O faults indicated by the controller are indicated on the status display in one of these formats:
• I/O Fault Local:X #XXXX message
• I/O Fault ModuleName #XXXX message
• I/O Fault ModuleParent:X #XXXX message
The first part of the format is used to indicate the location of the faulted module.
How the location is indicated depends on your I/O configuration and the module’s properties specified in RSLogix 5000 software.
The latter part of the format, #XXXX message, can be used to diagnose the type of I/O fault and potential corrective actions. For details about each I/O fault code, see the Logix5000 Major, Minor, and I/O Fault Codes Programming
Manual, publication 1756-PM014 .
Table 57 - I/O Fault Messages
Code
#0001
#0002
#0003
#0004
#0005
#0006
#0007
Message
Connection Failure
Insufficient Resource
Invalid Value
IOI Syntax
Destination Unknown
Partial Data Transferred
Connection Lost
#0008
#0009
Service Unsupported
Invalid Attribute Value
#000A Attribute List Error
#000B State Already Exists
#000C Object Mode Conflict
#000D Object Already Exists
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Table 57 - I/O Fault Messages
Code Message
#000E Attribute Not Settable
#000F Permission Denied
#0010 Device State Conflict
#0011 Reply Too Large
#0012 Fragment Primitive
#0013 Insufficient Command Data
#0014 Attribute Not Supported
#0015 Data Too Large
#0100 Connection In Use
#0103 Transport Not Supported
#0106 Ownership Conflict
#0107 Connection Not Found
#0108 Invalid Connection Type
#0109 Invalid Connection Size
#0110 Module Not Configured
#0111 RPI Out of Range
#0113 Out of Connections
#0114 Wrong Module
#0115 Wrong Device Type
#0116 Wrong Revision
#0117 Invalid Connection Point
#0118 Invalid Configuration Format
#0119 Module Not Owned
#011A Out of Connection Resources
#0203 Connection Timeout
#0204 Unconnected Message Timeout
#0205 Invalid Parameter
#0206 Message Too Large
#0301 No Buffer Memory
#0302 Bandwidth Not Available
#0303 No Bridge Available
#0304 ControlNet Schedule Error
#0305 Signature Mismatch
#0306 CCM Not Available
#0311 Invalid Port
#0312 Invalid Link Address
#0315 Invalid Segment Type
#0317 Connection Not Scheduled
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Status Indicators Appendix A
199
Appendix A Status Indicators
200
Table 57 - I/O Fault Messages
Code
#0318
#0319
#031E
#031F
#0800
#0801
Message
Invalid Link Address
No Secondary Resources Available
No Available Resources
No Available Resources
Network Link Offline
Incompatible Multicast RPI
#0814 Data Type Mismatch
#FD01 Bad Backplane EEPROM
#FD02 No Error Code
#FD03 Missing Required Connection
#FD04 No CST Master
#FD05 Axis or GRP Not Assigned
#FD06 SERCOS Transition Fault
#FD07 SERCOS Init Ring Fault
#FD08 SERCOS Comm Fault
#FD09 SERCOS Init Node Fault
#FD0A Axis Attribute Reject
#FD1F Safety I/O
#FD20 No Safety Task
#FE01 Invalid Connection Type
#FE02
#FE03
Invalid Update Rate
Invalid Input Connection
#FE04
#FE05
#FE06
#FE07
Invalid Input Data Pointer
Invalid Input Data Size
Invalid Input Force Pointer
Invalid Output Connection
#FE08
#FE09
Invalid Output Data Pointer
Invalid Output Data Size
#FE0A Invalid Output Force Pointer
#FE0B Invalid Symbol String
#FE0C Invalid Scheduled P/C Instance
#FE0D Invalid Symbol Instance
#FE0E
#FE0F
Module Firmware Updating
Invalid Firmware File Revision
#FE10
#FE11
#FE12
#FE13
Firmware File Not Found
Firmware File Invalid
Automatic Firmware Update Failed
Update Failed - Active Connection
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Status Indicators Appendix A
Table 57 - I/O Fault Messages
Code
#FE14
#FE22
#FE23
#FF00
#FF01
#FF04
#FF08
#FF0B
#FF0E
Message
Searching Firmware File
Invalid Connection Type
Invalid Unicast Allowed
No Connection Instance
Path Too Long
Invalid State
Invalid Path
Invalid Config
No Connection Allowed
1756-L7x Controller Status
Indicators
The status indicators are below the status display on the controller. They indicate the state of the controller as described in these tables.
RUN Indicator
To change the controller mode indicated by the RUN indicator, either use the keyswitch on the front of the controller or use the Controller Status menu in
RSLogix 5000 software .
Table 58 - RUN Indicator
State
Off
Description
The controller is either in Program or Test mode.
Steady green The controller is in Run mode.
FORCE Indicator
The Force indicator shows if I/O forces are enabled on the controller.
Table 59 - FORCE Indicator
State
Off
Description
No tags contain I/O force values.
Solid amber I/O forces are active (enabled) though I/O force values may or may not be configured.
Use caution if you install (add) a force. If you install (add) a force, it immediately takes effect.
Flashing amber One or more input or output addresses have been forced to an On or Off state, but the forces have not been enabled.
Use caution if you enable I/O forces. If you enable I/O forces, all existing
I/O forces also take effect.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 201
Appendix A Status Indicators
SD Indicator
The SD indicator shows if the Secure Digital (SD) card is in use.
Table 60 - SD Indicator
State
Off
Description
No activity is occurring with the SD card.
Flashing green The controller is reading from or writing to the SD card.
Solid green
Do not remove the SD card while the controller is reading or writing.
Flashing red
Solid red
The SD card does not have a valid file system.
The SD card is not recognized by the controller.
OK Indicator
The OK indicator shows the state of the controller.
Table 61 - OK Indicator
State
Off
Flashing red
Solid red
Solid green
Description
No power is applied to the controller.
Either of the following is true:
• It is a new controller, just out of the box, and it requires a firmware upgrade. If a firmware upgrade is required, the status display indicates Firmware
Installation Required. To upgrade firmware, see Upgrade Controller Firmware
on
.
• It is a previously-used or in-use controller and a major fault has occurred. For details about major recoverable faults, see the Logix5000 Major, Minor, and
I/O Fault Codes Programming Manual, publication 1756-PM014 .
One of the following is true:
• The controller is completing power-up diagnostics
• A nonrecoverable major fault occurred and the program was cleared from memory.
• The charge of the capacitor in the ESM is being discharged upon powerdown.
• The controller is powered, but is inoperable.
• The controller is loading a project to nonvolatile memory.
The controller is operating normally.
202 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Status Indicators Appendix A
1756-L6x Status Indicators
The 1756-L6 x controllers have status indicators on the front of the controller at show the state of the controller.
Status Indicators
RUN Indicator
To change the controller mode indicated by the RUN indicator, either use the keyswitch on the front of the controller or use the Controller Status menu in
RSLogix 5000 software.
Table 62 - RUN Indicator
State
Off
Steady green
Description
The controller is either in Program or Test mode.
The controller is in Run mode.
I/O Indicator
The I/O indicator shows the status of I/O modules in the controller’s project.
Table 63 - I/O Indicator
State
Off
Description
Either of the following is true:
• There are no devices are in the I/O configuration of the controller. If needed, add the required devices to the I/O configuration of the controller.
• The controller does not contain a project (controller memory is empty). If prepared, download the project to the controller.
The controller is communicating with all of the devices in its I/O configuration Solid green
Flashing green One or more devices in the I/O configuration of the controller are not responding.
For more information, go online with RSLogix 5000 software to check the I/O configuration of the controller.
Flashing red A chassis fault exists. Troubleshoot the chassis and replace it if necessary.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 203
Appendix A Status Indicators
204
FORCE Indicator
The FORCE indicator shows if I/O forces are active or enabled.
Table 64 - FORCE Indicator
State
Off
Steady amber
Flashing amber
Description
Either of the following is true:
• No tags contain I/O force values.
• I/O forces are inactive (disabled).
I/O forces are active (enabled) though I/O force values may or may not be configured.
Use caution if you install (add) a force. If you install (add) a force, it immediately takes effect.
One or more input or output addresses have been forced to an On or Off state, but the forces have not been enabled.
Use caution if you enable I/O forces. If you enable I/O forces, all existing I/O forces also take effect.
RS232 Indicator
The RS232 indicator shows if the serial port is in use.
Table 65 - RS232 Status Indicator
State
Off
Description
There is no serial connection activity.
Steady green Data is being received or transmitted via the RS-232 serial port.
BAT Indicator
The BAT indicator shows the charge of the battery and if the program is being saved.
Table 66 - BAT Indicator
State Controller
Series
Off N/A
Solid green A
B
Solid red N/A
Description
The controller is able to support memory.
The series A controllers do not use this state.
The series B controller is conducting a save of the program to internal-nonvolatile memory during a controller power down.
Either of the following is true:
• A battery is not installed.
• The battery is 95% discharged and should be replaced.
Note that if the indicator is solid red before a power down, the indicator remains red while the controller is completing a program save to internal-nonvolatile memory.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Status Indicators Appendix A
OK Indicator
The OK indicator shows the state of the controller.
Table 67 - OK Indicator
State
Off
Flashing red
Steady red
Steady green
Flashing green
Description
No power is applied to the controller.
Either of the following is true:
• It is a new controller, just out of the box, and it requires a firmware upgrade.
• It is a previously-used or in-use controller and a major fault has occurred.
A nonrecoverable major fault occurred and the program was cleared from memory.
The controller is operating normally.
The controller is storing or loading a project to or from nonvolatile memory.
If using a CompactFlash card, leave the card in the controller until the OK status indicator turns solid green.
Additional Resources
Consult these resources for additional information related to the status and programming of the ControlLogix controllers.
Resource
Logix5000 Controllers Major and Minor Faults Programming Manual, publication 1756-PM014
Logix5000 Controllers Nonvolatile Memory Programming Manual, publication 1756-PM017
Description
Explains major and minor faults of the controller and how to handle them.
Describes nonvolatile memory options and their use with Logix5000 controllers.
You can view or download publications at http://www.rockwellautomation.com/literature/ . To order paper copies of technical documentation, contact your local Rockwell Automation distributor or sales representative.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 205
Appendix A Status Indicators
Notes:
206 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Appendix
B
Using Electronic Keying
Topic
Page
Electronic Keying
The electronic keying feature automatically compares the expected module, as shown in the RSLogix 5000 I/O Configuration tree, to the physical module before I/O communication begins. You can use electronic keying to help prevent communication to a module that does not match the type and revision expected.
For each module in the I/O Configuration tree, the user-selected keying option determines if, and how, an electronic keying check is performed. Typically, three keying option are available:
• Exact Match
• Compatible Keying
• Disable Keying
You must carefully consider the benefits and implications of each keying option when selecting between them. For some specific module types, fewer options are available.
Electronic keying is based on a set of attributes unique to each product revision.
When a Logix5000 controller begins communicating with a module, this set of keying attributes is considered.
Table 68 - Keying Attributes
Attribute
Vendor
Product Type
Product Code
Major Revision
Minor Revision
Description
The manufacturer of the module, for example, Rockwell
Automation/Allen-Bradley.
The general type of the module, for example, communication adapter, AC drive, or digital I/O.
The specific type of module, generally represented by its catalog number, for example, 1756-IB16I.
A number that represents the functional capabilities and data exchange formats of the module. Typically, although not always, a later, that is higher, Major Revision supports at least all of the data formats supported by an earlier, that is lower, Major Revision of the same catalog number and, possibly, additional ones.
A number that indicates the module’s specific firmware revision. Minor
Revisions typically do not impact data compatibility but may indicate performance or behavior improvement.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 207
Appendix B Using Electronic Keying
You can find revision information on the General tab of a module’s Properties dialog box.
Figure 52 - General Tab
Exact Match
IMPORTANT Changing electronic keying selections online may cause the I/O communication connection to the module to be disrupted and may result in a loss of data.
Exact Match keying requires all keying attributes, that is, Vendor, Product Type,
Product Code (catalog number), Major Revision, and Minor Revision, of the physical module and the module created in the software to match precisely to establish communication. If any attribute does not match precisely, I/O communication is not permitted with the module or with modules connected through it, as in the case of a communication module.
Use Exact Match keying when you need the system to verify that the module revisions in use are exactly as specified in the project, such as for use in highly-regulated industries. Exact Match keying is also necessary to enable
208 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Using Electronic Keying Appendix B
EXAMPLE
Automatic Firmware Update for the module via the Firmware Supervisor feature from a Logix5000 controller.
In the following scenario, Exact Match keying prevents I/O communication.
The module configuration is for a 1756-IB16D module with module revision 3.1. The physical module is a 1756-IB16D module with module revision 3.2. In this case, communication is prevented because the Minor Revision of the module does not match precisely.
Module Configuration
Vendor = Allen-Bradley
Product Type = Digital Input
Module
Catalog Number = 1756-IB16D
Major Revision = 3
Minor Revision = 1
Communication is prevented.
Physical Module
Vendor = Allen-Bradley
Product Type = Digital Input
Module
Catalog Number = 1756-IB16D
Major Revision = 3
Minor Revision = 2
IMPORTANT Changing electronic keying selections online may cause the I/O
Communication connection to the module to be disrupted and may result in a loss of data.
Compatible Keying
Compatible Keying indicates that the module determines whether to accept or reject communication. Different module families, communication adapters, and module types implement the compatibility check differently based on the family capabilities and on prior knowledge of compatible products.
Compatible Keying is the default setting. Compatible Keying allows the physical module to accept the key of the module configured in the software, provided that the configured module is one the physical module is capable of emulating. The exact level of emulation required is product and revision specific.
With Compatible Keying, you can replace a module of a certain Major Revision with one of the same catalog number and the same or later, that is higher, Major
Revision. In some cases, the selection makes it possible to use a replacement that is a different catalog number than the original. For example, you can replace a
1756-CNBR module with a 1756-CN2R module.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 209
Appendix B Using Electronic Keying
The release notes for individual modules indicate the specific compatibility details.
When a module is created, the module developers consider the module’s development history to implement capabilities that emulate those of the previous module. However, the developers cannot know future developments. Because of this, when a system is configured, we recommend that you configure your module using the earliest, that is, lowest, revision of the physical module that you believe will be used in the system. By doing this, you can avoid the case of a physical module rejecting the keying request because it is an earlier revision than the one configured in the software.
EXAMPLE In the following scenario, Compatible Keying prevents I/O communication:
The module configuration is for a 1756-IB16D module with module revision 3.3. The physical module is a 1756-IB16D module with module revision 3.2. In this case, communication is prevented because the minor revision of the module is lower than expected and may not be compatible with 3.3.
Module Configuration
Vendor = Allen-Bradley
Product Type = Digital Input
Module
Catalog Number = 1756-IB16D
Major Revision = 3
Minor Revision = 3
Communication is prevented.
Physical Module
Vendor = Allen-Bradley
Product Type = Digital Input
Module
Catalog Number = 1756-IB16D
Major Revision = 3
Minor Revision = 2
210 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Using Electronic Keying Appendix B
Disabled Keying
EXAMPLE In the following scenario, Compatible Keying allows I/O communication:
The module configuration is for a 1756-IB16D module with module revision 2.1. The physical module is a 1756-IB16D module with module revision 3.2. In this case, communication is allowed because the major revision of the physical module is higher than expected and the module determines that it is compatible with the prior major revision.
Module Configuration
Vendor = Allen-Bradley
Product Type = Digital Input
Module
Catalog Number = 1756-IB16D
Major Revision = 2
Minor Revision = 1
Communication is allowed.
Physical Module
Vendor = Allen-Bradley
Product Type = Digital Input
Module
Catalog Number = 1756-IB16D
Major Revision = 3
Minor Revision = 2
IMPORTANT Changing electronic keying selections online may cause the I/O communication connection to the module to be disrupted and may result in a loss of data.
Disabled Keying indicates the keying attributes are not considered when attempting to communicate with a module. Other attributes, such as data size and format, are considered and must be acceptable before I/O communication is established. With Disabled Keying, I/O communication may occur with a module other than the type specified in the I/O Configuration tree with unpredictable results. We generally do not recommend using Disabled Keying.
ATTENTION: Be extremely cautious when using Disabled Keying; if used incorrectly, this option can lead to personal injury or death, property damage, or economic loss.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 211
Appendix B Using Electronic Keying
EXAMPLE
If you use Disabled Keying, you must take full responsibility for understanding whether the module being used can fulfill the functional requirements of the application.
In the following scenario, Disable Keying prevents I/O communication:
The module configuration is for a 1756-IA16 digital input module. The physical module is a 1756-IF16 analog input module. In this case, communication is prevented because the analog module rejects the data formats that the digital module
configuration requests.
Module Configuration
Vendor = Allen-Bradley
Product Type = Digital Input
Module
Catalog Number = 1756-IA16
Major Revision = 3
Minor Revision = 1
Communication is prevented.
Physical Module
Vendor = Allen-Bradley
Product Type = Analog Input
Module
Catalog Number = 1756-IF16
Major Revision = 3
Minor Revision = 2
212 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Using Electronic Keying Appendix B
EXAMPLE In the following scenario, Disable Keying allows I/O communication:
The module configuration is for a 1756-IA16 digital input module. The physical module is a 1756-IB16 digital input module. In this case, communication is allowed because the two digital modules share common data formats.
Module Configuration
Vendor = Allen-Bradley
Product Type = Digital Input
Module
Catalog Number = 1756-IA16
Major Revision = 2
Minor Revision = 1
Communication is allowed.
Physical Module
Vendor = Allen-Bradley
Product Type = Digital Input
Module
Catalog Number = 1756-IB16
Major Revision = 3
Minor Revision = 2
IMPORTANT Changing electronic keying selections online may cause the I/O communication connection to the module to be disrupted and may result in a loss of data.
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 213
Appendix B Using Electronic Keying
Notes:
214 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Appendix
C
History of Changes
Changes to This Manual
With the availability of new controllers, modules, applications, and
RSLogix 5000 software features, this manual has been revised to include updated information. This appendix briefly summarizes changes that have been made with each revision of this manual.
Reference this appendix if you need information to determine what changes have been made across multiple revisions. This may be especially useful if you are deciding to upgrade your hardware or software based on information added with previous revisions of this manual.
This table lists the publication revision, publication date, and changes made with the revision.
Table 69 - History of Changes
Publication Revision and Date Topic
1758-UM001J-EN-P, July 2010 Added 1756-L6x and 1756-L7x installation information
Added information in Chapter 3 to identify and describe common start-up tasks completed with ControlLogix controllers
Updated the ControlLogix example configurations, system design information, controller features descriptions to include the 1756-L7x controllers, available memory options to include the 1756-L7x information, and ControlLogix controller CPU resources in Chapter 4
Reformatted information for clarity on communication networks, and updated the Additional Resources in Chapter 5
Placed and reformatted information specific to the use of serial communication in Chapter 6
Reformatted information about controller connections in
Chapter 7
Added a list of modules and devices that can be added while online with RSLogix 5000 software, updated ControlNet network considerations that must be made when adding modules or devices while online, and updated EtherNet/IP network considerations that must be made when adding modules or devices while online in Chapter 8
Updated motion information and references with regard to the
1756-L60M03SE combination controller and reformatted and added graphics in Chapters 9 and 10
Made redundancy information corrections, and updated and added information about SIL2 certification and configurations in Chapters 12 and 13
Added 1756-L7x status display and status indicator information in Appendix A
Added information to the History of Changes that describes changes made with each revision of this manual
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 215
Appendix C History of Changes
216
Table 69 - History of Changes
Publication Revision and Date Topic
1756-UM001I-EN-P, October 2009 Added new information about broadcasting over serial port
Updated redundancy information
1756-UM001H-EN-P, July 2008
Updated battery information
Added new and updated EtherNet/IP motion information
Added new information about the 1756-L65 controller
Added new information about the 1784-CF128 CompactFlash card
1756-UM001G-EN-P, January 2007 Added information about the 1756-L64 ControlLogix controller
Added information about Add-On Instructions
Updated the section titled Select a System Overhead
Percentage
Updated the section titled Add Your Axes
Updated the section titled Obtain Axis Information
1756-UM001F-EN-P, May 2005 No changes documented
1756-UM001E-EN-P, August 2002 Added information about the battery life of the 1756-BA1 battery when you use it in a ControlLogix5563 controller
Added information about the 1756-BATM ControlLogix battery module
1756-UM001D-EN-P
1756-UM001C-EN-P, June 2001
Revision not published
Updated the Preface
Added the section titled Configure an EtherNet/IP Module
Added the section titled Download and Go Online over an
EtherNet/IP Network
Added the section titled Communicate with 1756 I/O over an
EtherNet/IP Network
Added the section titled Communicate with 1794 I/O Over an
EtherNet/IP Network
Added the section titled Communicate with Another
Controller over an EtherNet/IP Network
Added the section titled Communicate with a PanelView
Terminal Over a EtherNet/IP Network
Added the section titled Communicate with an RSView32
Project over an EtherNet/IP Network
Added the section titled Add I/O Modules
Added the section titled Create Aliases
Added the section titled Schedule the ControlNet Network
Added the section titled Communicate with Another
Controller Over a DH+ Network
Added the section titled Route PLC-5 or SLC 500 Messages
From a DH+ Network
Added the section titled Estimate Execution Time
Added the section titled Estimate Memory Use
Added the section titled Determine When Data Is Updated
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
History of Changes Appendix C
Table 69 - History of Changes
Publication Revision and Date Topic
1756-UM001B-EN-P, November
2000
Added the section titled Configure a 1756-ENET Module
Added the section titled Download and Go Online over an
Ethernet Network
Added the section titled Communicate with 1756 I/O over an
Ethernet Network
Added the section titled Communicate with Another
Controller over an Ethernet Network
Added the section titled Communicate with Another
Controller over a DH-485 Network
Added the section titled Estimate Battery Life
Added the section titled Estimate Execution Time (updated numbers)
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 217
Appendix C History of Changes
Notes:
218 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Index
Numerics
1747-KY controller parts
,
1756-BA1 check level
controller compatiblity
controller parts
estimate life
storage
1756-BA2 check level
controller compatibility
controller parts
estimate life
life after warning
storage
1756-BATA controller compatibility
estimate life
1756-BATM controller compatibility
controller parts
use and life
1756-CN2 uses
1756-CN2R uses
1756-CN2RXT uses
1756-CNB uses
1756-CNBR uses
1756-CP3 controller parts
1756-DHRIO communication via
uses remote I/O
1756-EN2F uses
1756-EN2T uses
1756-EN2TR uses
1756-EN2TXT uses
1756-EN3TR uses
1756-ENBT uses
1756-ESMCAP controller parts
1756-ESMNRM controller parts
1756-ESMNSE controller parts
1756-EWEB uses
1756-IF8H uses
1756-L6x add while online
BAT indicator
configure serial communication
CPU
FORCE indicator
I/O indicator
installation battery, install
battery, uninstall
CompactFlash card, removal
into chassis
precautions
memory options
OK indicator
parts included
not included
RS232 indicator
RS232 serial port
RUN indicator
serial connection
serial driver
serial port
1756-L6x, included controller
1756-L7x add while online
CPU
FORCE indicator
installation
ESM, install
ESM, uninstall
into chassis
key
SD card, install
SD card, removal
memory options
OK indicator
parts not included
parts, included
RUN indicator
SD indicator
status display
status indicators
USB driver
1756-N2
1756-N2XT
1756-OF8H uses
1756-RIO uses
1784-CF64 controller parts
1784-SD1 controller parts
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 219
Index
220 load from
store to
1784-SD2 controller parts
load from
store to
A
add distributed I/O
local I/O
remote I/O
Add-On Instructions in project
application elements
networks and
ASCII
attributes keying
AutoFlash, upgrade
axis obtain information
B
BAT indicator
1756-L6x
battery
1756-BA1 estimate
1756-BA2 estimate
life after warning
1756-BATA estimate
1756-BATM
catalog number
check if low
compatibility
install
replacement
schedule
storage
uninstall
battery module catalog number
broadcast messages
C
cache message options
messages calculate about
connection use
catalog numbers controller
change equipment phase
chassis
ControlLogix list
insert controller
check
WallClockTime
ComapactFlash card catalog number
communication
Data Highway Plus
DH-485 network
Foundation Fieldbus
HART
network options
path set
ports
serial configure
universal remote I/O
CompactFlash card installation
load from
other tasks
removal
store to
comparision
PhaseManager
compatibility battery
compatible keying
configurations fail-safe
fault-tolerant
high-availability
configure motion
serial communication
serial driver
system overhead time slice
connect
DH-485 network
connection calculate use
ControlNet
network
DeviceNet network
EtherNet/IP
network
example
local
message, required
produce/consume data and
required
remote
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Index scheduled
ControlNet
serial
unscheduled
ControlNet
USB, make
considerations redundancy
consume data
continuous task
ControlFLASH utility
controller
1756-L6x battery and
battery, install
battery, uninstall
CompactFlash card, installation
CompactFlash card, removal
insert into chassis
parts not included
RS-232
serial connection
serial driver
serial port
1756-L7x battery and
communication options
ESM, install
ESM, uninstall
insert into chassis
key, insert
parts included
not included
SD card, install
SD card, removal
status display
status indicators
,
USB driver
battery check
battery module
communication path set
communication ports
configure serial communication
connections calculate
CPU resources
design system with
download
estimate battery life
estimate battery life
extreme environment
feature differences
firmware obtain
revision
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
53 go online
memory options
monitor connections
status
overview
program
routine
software minimum
tags
tasks
types
upload
controller parts
1747-KY
1756-BA1
1756-BA2
1756-BATM
1756-CP3
1756-ESMCAP
1756-ESMNRM
1756-ESMNSE
1784-CF64
1784-SD1
1784-SD2
battery
battery module
CompactFlash card
energy storage module catalog number
21 catalog number ESM. See energy storage module.
key
SAMTEC RSP-119350
SD card
serial cable
USB cable
ControlLogix chassis list
configuration options
controller add while online
catalog numbers
differences
extreme environment
overview
traditional
design system
I/O remote
selection
modules online addition
motion options
redundancy about
remote I/O local
slot filler
221
Index
222
ControlLogix-XT chassis list
controller about
ControlNet
CPU connection
module capability
module features
module list
network
redundancy system and
scheduled connection scheduled connection
software for
unscheduled connection unscheduled connection
controller
D
Data Highway Plus network
design system
determine firmware revision
develop applications
motion applications
DeviceNet connection use
module memory
module features
network
software for
devices add while online
DF1 master
point to point
radio modem
slave
DH-485 network example configuration
overview
disabled keying
display
1756-L7x
distributed
I/O
add
download drive project
add while online
E
electronic keying about
elements control application
enhanced redundancy. See redundancy.
equipment phase error change manually
instructions
ESM script file
install
uninstall
EtherNet/IP add while online
connections
module features
module list
network
redundancy system and
software for
event task
exact match keying
example configuration
DH-485 network
extreme environment controller
about
F
fail-safe configruation about
fault code use GSV to get
fault handler execute at I/O fault
fault messages
I/O
Major Recoverable Fault
fault-tolerant configruation about
features
controller communication
programming
filler slot slot filler
firmware determine revision
obtain
security certificate, error
upgrade
AutoFlash, use
FORCE indicator
1756-L6x
1756-L7x
Foundation Fieldbus
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Index
G
general status messages
GSV fault code
monitor connection
monitor controller
H
hardware configuration options
HART. See Highway Addressable Remote
high-availability configruation about
Highway Addressable Remote Transducer
hold-up time
ESM WallClockTime
I
I/O connection error
ControlLogix remote
selection
determine data update
distributed
fault codes
reconfigure
remote
I/O configuration add distributed I/O
local I/O
remote I/O
while online
I/O indicator
1756-L6x
indicator
BAT
1756-L6x
FORCE
1756-L6x
1756-L7x
I/O
1756-L6x
OK
RS232
1756-L6x
RUN
1756-L6x
1756-L7x
1756-L6x
1756-L7x
SD
1756-L7x
install
1756-L6x battery
CompactFlash card
insert into chassis
precautions
1756-L7x
ESM
insert into chassis
key, insert
SD card
battery
CompactFlash card
ESM
SD card
instruction
ASCII
motion
IP address swapping
K
key catalog number
insert
keying about
attributes
compatible
disabled
exact match
L
load local from memory card
status indicators during
connection
I/O add
remote I/O
M
Major Recoverable Fault messages
memory
DeviceNet module
options
memory card load from
other tasks
store to
message about
broadcast over serial
cache
determine if
fault
reconfigure I/O module
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 223
Index
224 status display
Modbus network
mode serial port
module
ControlNet
DeviceNet
EtherNet/IP
motion about
application
instructions
options
program
MVI56-HART uses
N
network application and
controller options
ControlNet
ControlNet redundancy
Data Highway Plus
Data Highway Plus DH+. See Data Highway
DeviceNet
EtherNet/IP
EtherNet/IP redundancy
Foundation Fieldbus
HART
universal remote I/O
nonvolatile memory
O
obtain axis information
firmware
OK indicator
1756-L6x
1756-L7x
online add go
options
EtherNet/IP
to I/O configuration
memory
motion
P
parts
1756-L6x not included
1756-L7x included
not included
path set communication
periodic task
PhaseManager about
change states
comparison
equipment phase instructions
state model
system requirements
terminology
transition
port communication
PowerFlex add while online
precautions
priority task
produce data
produce/consume connections required
data
program in project
scheduled
system overhead time slice
unscheduled
programming languages
project
Add-On Instructions
download
elements
go online
load status indicators during
program
routine
samples
store status indicators during
tags
tasks
upload
protocol
ASCII
DF1 master
point to point
radio modem
slave
DH-485
Modbus network
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Index
R
receive messages
redundancy about
build system
considerations
ControlNet network
EtherNet/IP network
scan time
system requirements
remote connection
I/O
remote I/O add
ControlLogix local
universal
remove
1756-L6x
CompactFlash card
1756-L7x
SD card
CompactFlash card
SD card
replace battery schedule
required connections messages
software
requirement
PhaseManager system
redundancy
revision firmware determine
routine in project
RS232
DF1 device driver
indicator
1756-L6x
RSLinx Classic version required
RSLogix 5000
Add-On Instructions
program
routine
sample projects
tags
tasks
version required
RSWho set path
RUN indicator
1756-L6x
1756-L7x
S
safety integration level, see SIL 2
sample projects
SAMTEC RSP-119350 controller parts
scan time redundancy and
scheduled program
script file error
SD card catalog number
install
load from
other tasks
removal
store to
SD indicator
1756-L7x
security certificate error
selection send
I/O
messages
serial broadcast
cable catalog number
configure controller
connection
DH-485 network configuration
driver
Modbus network
serial port
ASCII
DF1 master
point to point
radio modem
slave
DH-485
mode
protocols
service communication
set up serial driver
USB driver
SIL 2 certification overview
software
ControlNet and
DeviceNet and
EtherNet/IP and
Rockwell Automation Publication 1756-UM001K-EN-P - November 2010 225
Index minimum required
required
USB
SSV monitor controller
standard redundancy. See redundancy.
state equipment phase change
state model overview
status battery
display
1756-L7x
fault messages
indicators
1756-L7x
load
messages display
monitor connections
controller
status indicators store
storage store battery
to memory card
store project status indicators during
swapping IP address
system
configuration options
system overhead time slice
configure
system requirements
PhaseManager
redundancy
T
tag consume
in project
produce
task continuous
event
in project
periodic
priority
time slice
traditional controller
transistion type
PhaseManager
USB
U
uninstall
1756-L6x battery
1756-L7x
ESM
battery
ESM
universal remote I/O
communicate via
unscheduled program
update determine frequency
upgrade firmware
AutoFlash, use
upload
USB project
cable catalog number
connection
driver
software required
type
W
WallClockTime object check
226 Rockwell Automation Publication 1756-UM001K-EN-P - November 2010
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products.
At http://www.rockwellautomation.com/support/ , 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://www.rockwellautomation.com/support/ .
Installation Assistance
If you experience a problem within the first 24 hours of installation, review the information that is contained in this manual.
You can contact Customer Support for initial help in getting your product up and running.
United States or Canada
Outside United States or
Canada
1.440.646.3434
Use the Worldwide Locator at http://www.rockwellautomation.com/support/americas/phone_en.html
, or contact your local Rockwell Automation representative.
New Product Satisfaction Return
Rockwell Automation 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, follow these procedures.
United States
Outside United States
Contact your distributor. You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor to complete the return process.
Please contact your local Rockwell Automation representative for the return procedure.
Documentation Feedback
Your comments will help us serve your documentation needs better. If you have any suggestions on how to improve this document, complete this form, publication RA-DU002 , available at http://www.rockwellautomation.com/literature/ .
Rockwell Otomasyon Ticaret A.Ş., Kar Plaza İş Merkezi E Blok Kat:6 34752 İçerenköy, İstanbul, Tel: +90 (216) 5698400
Publication 1756-UM001K-EN-P - November 2010 228
Supersedes Publication 1756-UM001J-EN-P - July 2010 Copyright © 2010 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.

Public link updated
The public link to your chat has been updated.
Advertisement
Key features
- Industrial Controller
- Variety of Programming Languages
- Multiple Communication Options
- System and Connection Status Monitoring
- High-Performance Processing
- Extensive I/O Capabilities
- Redundancy Support
- Motion Control Features
- Safety Features
- Extreme Environment Version