Allen-Bradley 1756-L71, 1756-L72, 1756-L74, 1756-L75 User Manual

Below you will find brief information for 1756-L61, 1756-L62, 1756-L63, 1756-L63XT, 1756-L64, 1756-L65, 1756-L71, 1756-L72, 1756-L73, 1756-L73XT. These ControlLogix controllers offer robust control for various applications. They support communication networks like EtherNet/IP, ControlNet, and DeviceNet. Some models include features like USB ports, memory card support, and extreme temperature operation. With options for redundancy, motion control, and safety, the ControlLogix system provides flexible and scalable solutions for industrial automation.

PDF

Document

User Manual
ControlLogix System User Manual
Catalog Numbers 1756-L61, 1756-L62, 1756-L63, 1756-L63XT, 1756-L64, 1756-L65, 1756-L71, 1756-L72, 1756-L73,
1756-L73XT, 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&reg; 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, Kinetix, MessageView, MicroLogix, POINT I/O, PhaseManager, PowerFlex, RSFieldbus, RSLinx, RSLogix, RSNetWorx, Rockwell Software, Rockwell
Automation, Compact I/O, RediSTATION, Series 9000, FlexLogix, PanelView, FactoryTalk, ArmorPOINT, Stratix 8000, SLC, ControlFLASH, DH+, Data Highway Plus, Integrated Architecture, Logix5000,
ControlLogix-XT, GuardLogix, RSView, Encompass, 1336 FORCE, 1336 PLUS, 1336 IMPACT, SMC, RSBizWare, FLEX Ex, ArmorBlock, ArmorBlock MaXum, Guard PLC, 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
Page
Added 1756-L73XT controller and GuardLogix User Manual reference
11
USB Cable Text
19
Added energy storage module information relating to safety and extreme temperature
controllers.
26
Parts Not Included with the 1756-L6x Controller
33
Added double data rate (DDR) communication reference for 1756-L7x controller
43
Added 1756-L71, 1756-L73XT controllers and chassis, and changed version information for
1756-L72, 1756-L73, 1756-L74, and 1756-L75 controllers
51
Added upgrade restrictions
52
Added information about mode switch operation on the controller
63
Controller mode can be changed in RSLogix 5000 software.
64
1756-ESMNSE &micro;joules correction from 200…40
72
Added 1756-L71 information to ControlLogix controller features
87
Added 1756-L71 and 1756-L73XT memory options
88
Added double data rate (DDR) communication information
95
Added 1756-A7XT chassis information
132
Added information about the ‘Flashing Red’ OK status indicator for nonrecoverable faults
208
History for 1756-UM001L-EN-P publication
221
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
3
Summary of Changes
Notes:
4
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Table of Contents
Preface
ControlLogix Controllers Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Traditional ControlLogix Controllers . . . . . . . . . . . . . . . . . . . . . . . . . 11
Redundant ControlLogix Controllers. . . . . . . . . . . . . . . . . . . . . . . . . . 12
Extreme Environment ControlLogix Controllers . . . . . . . . . . . . . . . 12
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Required Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Chapter 1
Install the 1756-L7x Controller
Environment and Enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Prevent Electrostatic Discharge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Removal and Insertion Under Power (RIUP) . . . . . . . . . . . . . . . . . . . 18
European Hazardous Location Approval . . . . . . . . . . . . . . . . . . . . . 18
CompactFlash/SD Card Capability. . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
USB Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
North American Hazardous Location Approval . . . . . . . . . . . . . . . . 19
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
1756-L7x Controller Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Parts Included with the 1756-L7x Controller . . . . . . . . . . . . . . . . . . . 20
Parts Available for Use with the 1756-L7x Controller . . . . . . . . . . . 21
1756-L7x Controller Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Insert the Controller into the Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Insert the Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Remove the SD Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Install the SD Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Uninstall the ESM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Install the ESM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Chapter 2
Install the 1756-L6x Controller
Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Environment and Enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Programmable Electronic Systems (PES) . . . . . . . . . . . . . . . . . . . . . . . 30
Preventing Electrostatic Discharge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Removing Module While Under Power (RIUP) . . . . . . . . . . . . . . . . 30
European Hazardous Location Approval . . . . . . . . . . . . . . . . . . . . . 30
USB Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
North American Hazardous Location Approval . . . . . . . . . . . . . . . . 31
Lithium Batteries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
1756-L6x Controller Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Parts Not Included with the 1756-L6x Controller. . . . . . . . . . . . . . . 33
1756-L6x Controller Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
CompactFlash Card Installation and Removal . . . . . . . . . . . . . . . . . . . . . . 34
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
5
Table of Contents
Battery Connection and Replacement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Insert the Controller into the Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Remove the Controller from the Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Chapter 3
Start Using the Controller
6
Make Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
1756-L7x Connection Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
1756-L6x Connection Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Connect to the 1756-L7x Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Set Up the USB Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Connect to the 1756-L6x Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Configure the Serial Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Upgrade Controller Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Determine Required Controller Firmware . . . . . . . . . . . . . . . . . . . . . . 52
Obtain Controller Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Use ControlFLASH Utility to Upgrade Firmware. . . . . . . . . . . . . . . 53
Use AutoFlash to Upgrade Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Set the Communication Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Go Online with the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Download to the Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Use the Who Active Dialog Box to Download . . . . . . . . . . . . . . . . . . 60
Use the Controller Status Menu to Download . . . . . . . . . . . . . . . . . . 61
Upload from the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Use the Who Active Dialog Box to Upload . . . . . . . . . . . . . . . . . . . . . 61
Use the Controller Status Menu to Upload . . . . . . . . . . . . . . . . . . . . . 62
Choose the Controller Operation Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Use the Mode Switch to Change the Operation Mode . . . . . . . . . . . 63
Use RSLogix 5000 Software to Change the Operation Mode . . . . . 65
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 . . . . . . . . . . . . . . . 74
Estimate the ESM Support of the WallClockTime . . . . . . . . . . . . . . . . . . 74
Maintain the Battery
(1756-L6x controllers only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Check the Battery Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
1756-BA1 or 1756-BATA Battery Life . . . . . . . . . . . . . . . . . . . . . . . . . 76
1756-BATM Battery Module and Battery Life . . . . . . . . . . . . . . . . . . 77
Estimate 1756-BA2 Battery Life . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Estimate 1756-BA2 Battery Life after Warnings. . . . . . . . . . . . . . . . . 79
Battery Storage and Disposal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Table of Contents
Chapter 4
ControlLogix System and Controllers The ControlLogix System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Design a ControlLogix System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
ControlLogix Controller Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
System, Communication, and Programming Features . . . . . . . . . . . 87
Memory Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Chapter 5
Communication Networks
Networks Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
EtherNet/IP Network Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
ControlLogix EtherNet/IP Module Features . . . . . . . . . . . . . . . . . . . 92
ControlLogix EtherNet/IP Communication Modules. . . . . . . . . . . 93
Software for EtherNet/IP Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Connections Over an EtherNet/IP Network . . . . . . . . . . . . . . . . . . . 94
Double Data Rate (DDR) Backplane Communication . . . . . . . . . . 95
ControlNet Network Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
ControlLogix ControlNet Module Features . . . . . . . . . . . . . . . . . . . . 97
ControlLogix ControlNet Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Software for ControlNet Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Connections Over a ControlNet Network . . . . . . . . . . . . . . . . . . . . . 98
DeviceNet Network Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
ControlLogix DeviceNet Module Features . . . . . . . . . . . . . . . . . . . . . 99
ControlLogix DeviceNet Bridge Module and Linking Devices . . 100
Software for DeviceNet Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Connections Over DeviceNet Networks . . . . . . . . . . . . . . . . . . . . . . 100
ControlLogix DeviceNet Module Memory . . . . . . . . . . . . . . . . . . . . 100
Data Highway Plus (DH+) Network Communication . . . . . . . . . . . . . 101
Communicate Over a DH+ Network . . . . . . . . . . . . . . . . . . . . . . . . . 102
Universal Remote I/O (RIO) Communication . . . . . . . . . . . . . . . . . . . . 102
Communicate Over a Universal Remote I/O Network . . . . . . . . . 104
Foundation Fieldbus Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
HART Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
7
Table of Contents
Chapter 6
Serial Communication (1756-L6x
controllers only)
1756-L6x Controller Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
ControlLogix Chassis Serial Communication Options. . . . . . . . . . 110
Communication with Serial Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
DF1 Master Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
DF1 Point to Point Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
DF1 Radio Modem Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
DF1 Radio Modem Advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
DF1 Radio Modem Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
DF1 Radio Modem Protocol Parameters. . . . . . . . . . . . . . . . . . . . . . . 114
DF1 Slave Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
DH-485 Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
ASCII Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Configure the 1756-L6x Controller for Serial Communication. . . . . . 117
Broadcast Messages Over a Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Configure Controller Serial Port Properties. . . . . . . . . . . . . . . . . . . . 120
Program the Message Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Modbus Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Chapter 7
Manage Controller Communication
(connections)
Connection Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Produce and Consume (interlock) Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Connection Requirements of a Produced or Consumed Tag . . . . 124
Send and Receive Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Determine Whether to Cache Message Connections . . . . . . . . . . . 126
Calculate Connection Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Local Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Remote Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Connections Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Chapter 8
I/O Modules
8
Selecting ControlLogix I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Local I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Add Local I/O to the I/O Configuration . . . . . . . . . . . . . . . . . . . . . . 132
Remote I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Add Remote I/O to the I/O Configuration . . . . . . . . . . . . . . . . . . . . 135
Distributed I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Add Distributed I/O to the I/O Configuration . . . . . . . . . . . . . . . . 139
Reconfigure an I/O Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Reconfigure an I/O Module via the Module Properties . . . . . . . . . 141
Reconfigure an I/O Module via a Message Instruction . . . . . . . . . . 142
Add to the I/O Configuration While Online . . . . . . . . . . . . . . . . . . . . . . 142
Modules and Devices that Can be Added While Online. . . . . . . . . 143
Online Additions - ControlNet Considerations . . . . . . . . . . . . . . . . 145
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Table of Contents
Online Additions - EtherNet/IP Considerations . . . . . . . . . . . . . . . 148
Determine When Data is Updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Chapter 9
Develop Motion Applications
Motion Control Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Motion Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Obtain Axis Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Program Motion Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Chapter 10
Develop Applications
Elements of a Control Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Task Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Scheduled and Unscheduled Programs . . . . . . . . . . . . . . . . . . . . . . . . 163
Routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Programming Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Add-On Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Monitoring Controller Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Monitoring I/O Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Determine if I/O Communication has Timed Out . . . . . . . . . . . . . 169
Determine if I/O Communication to a Specific I/O Module has
Timed Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Interrupt the Execution of Logic and Execute the Fault Handler 170
System Overhead Time Slice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Configure the System Overhead Time Slice. . . . . . . . . . . . . . . . . . . . 172
Sample Controller Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Chapter 11
Using the PhaseManager Tool
PhaseManager Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Minimum System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
State Model Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
How Equipment Changes States. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Manually Change States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
PhaseManager Tool versus Other State Models . . . . . . . . . . . . . . . . . . . . 180
Equipment Phase Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
9
Table of Contents
Chapter 12
Redundant Systems
ControlLogix Redundancy Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
System Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Enhanced versus Standard Redundancy. . . . . . . . . . . . . . . . . . . . . . . . 187
Build a Redundant System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
ControlNet Considerations in Redundant Systems. . . . . . . . . . . . . . . . . 188
EtherNet/IP Considerations in Redundant Systems . . . . . . . . . . . . . . . . 189
IP Address Swapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Redundancy and Scan Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Chapter 13
SIL 2 Certification
Introduction to SIL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Programming and Debugging Tool (PADT) . . . . . . . . . . . . . . . . . . . 193
Typical SIL2 Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Fail-safe Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
High-availability Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Fault-tolerant Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Appendix A
Status Indicators
10
1756-L7x Controller Status Display and Indicators . . . . . . . . . . . . . . . . 199
1756-L7x Controller Status Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
General Status Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Fault Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Major Recoverable Fault Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
I/O Fault Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
1756-L7x Controller Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
RUN Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
FORCE Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
SD Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
OK Indicator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
1756-L6x Status Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
RUN Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
I/O Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
FORCE Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
RS232 Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
BAT Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
OK Indicator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Table of Contents
Appendix B
Using Electronic Keying
Electronic Keying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Exact Match . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Compatible Keying. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Disabled Keying. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Appendix C
History of Changes
Changes to This Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Index
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
11
Table of Contents
Notes:
12
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Preface
ControlLogix Controllers
Overview
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, or the GuardLogix Controllers User Manual, publication
1756-UM020.
Traditional ControlLogix Controllers
Two lines of traditional ControlLogix controllers are now available. These
controllers are identified as 1756-L6x controllers and 1756-L7x controllers
according to abbreviations of their full catalog numbers.
Table 1 - ControlLogix Catalog Numbers
Abbreviated Cat. No.
Cat. No.
1756-L6x
1756-L61, 1756-L62,
1756-L63, 1756-L64,
1756-L65
1756-L7x
1756-L71, 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
1756-L7x
1756-L6x
Clock support and backup used for
memory retention at powerdown
Energy Storage Module (ESM)
Battery
Communication ports (built-in)
USB
Serial
Connections, controller
500
250
Logix CPU (processor)
Dual-core
Single-core
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
11
Preface
Feature
1756-L7x
1756-L6x
Memory, nonvolatile
Secure Digital (SD) card
CompactFlash card
Status display and status indicators
Scrolling status display and
four status indicators
Six status indicators
Unconnected buffer defaults
20 (40, max)
10 (40, max)
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 183).
Extreme Environment ControlLogix Controllers
The extreme environment ControlLogix controllers, catalog numbers 1756L73XT and 1756-L63XT, provide the same functionality as the 1756-L73 and
1756-L63 controllers, but are designed to withstand temperatures -25...70 &deg;C
(-13...158 &deg;F).
Before You Begin
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
12
Cat. No.
RSLogix 5000 Software
RSLinx Classic Software
1756-L61, Series A
Version 12.x or later
Any version
1756-L61, Series B
Version 13.40 or later
1756-L62, Series A
Version 12.x or later
1756-L62, Series B
13.40 or later
1756-L63, Series A
• If not using a CompactFlash
card, 10.x or later
• If using a CompactFlash card,
11.x or later
1756-L63, Series B
Version 13.40 or later
1756-L63XT, Series B
Version 13.40 or later
Version 2.55, or later
1756-L64, Series B
Version 16 or later
Any version
1756-L65, Series B
Version 17 or later
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Preface
Additional Resources
Cat. No.
RSLogix 5000 Software
RSLinx Classic Software
1756-L71, Series A
Version 20
Version 2.6, or later
1756-L72, Series A
Version 19 or later
1756-L73, Series A
Version 19 or later
1756-L73XT, Series A
Version 19 or later
1756-L74, Series A
Version 19 or later
1756-L75, Series A
Version 19 or later
Consult these resources for additional information related to ControlLogix
controllers.
Table 4 - Additional Resources Related to ControlLogix Controllers and Systems
For more information about
See This Resource
Description
Add-On Instructions
Add-On Instructions Programming Manual, publication
1756-PM010
Explains Add-On Instructions and how to use them.
Batteries for use with controllers
Guidelines for Handling Lithium Batteries, publication
AG-5.4
Provides information regarding storage, handling, transportation, and
disposal of lithium batteries.
Programmable Controllers Battery Reference,
http://www.ab.com/programmablecontrol/batteries.html
Provides Material Safety Data Sheets (MSDS) for individual
replacement batteries.
Power supplies and chassis for use with
controllers
ControlLogix Chasis and Power Supplies, publication 1756-IN005 Provides information about installing standard and XT ControlLogix
chassis and power supplies; and redundant power supplies.
CIP Sync (Time Synchronization)
Integrated Architecture and CIP Sync Configuration Application
Technique, publication IA-AT003
Provides detailed and comprehensive information about how to apply
CIP Sync technology to synchronize clocks in a Logix control system.
Design and selection
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.
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
Describes how to install and ground a ControlLogix chassis.
ControlLogix Power Supplies Installation Instructions,
publication 1756-IN613
Describes how to install and ground ControlLogix power supplies.
ControlLogix-XT Chassis Installation Instructions, publication
1756-IN637
Describes how to install and ground a ControlLogix-XT chassis.
ControlLogix-XT Power Supplies Installation Instructions,
publication 1756-IN639
Describes how to install and ground ControlLogix-XT power supplies.
GuardLogix Controller Systems Safety Reference Manual,
publication 1756-RM093
Describes how to use the GuardLogix controllers.
Hardware installation
GuardLogix controllers
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
13
Preface
For more information about
See This Resource
Description
I/O
ControlLogix Remote I/O Communication Module User Manual,
publication 1756-UM534
Describes how to configure and troubleshoot the ControlLogix remote
I/O (RIO) communication module.
Process Remote I/O Communication Interface Module User
Manual, publication 1757-UM007
Describes how to configure and troubleshoot process remote I/O (RIO)
communication interface modules.
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
Describes how to install, configure, and troubleshoot ControlLogix
HART I/O modules.
ControlLogix High Speed Analog I/O Module User Manual,
publication 1756-UM005
Describes how to install, configure, and troubleshoot ControlLogix
high-speed analog I/O modules.
ControlLogix High Speed Counter Module User Manual,
publication 1756-UM007
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.
Runtime/On-line Addition of ControlLogix (1756) I/O over
ControlNet and EtherNet/IP White Paper, publication
LOGIX-WP006
Explains adding to the I/O Configuration while online with the
controller.
Logix5000 Controllers General Instructions Reference Manual,
publication 1756-RM003
Provides programmers with details about each available instruction
for a Logix5000 controller.
Logix5000 Controllers Motion Instructions Reference Manual,
publication MOTION-RM002
Provides programmers with details about the motion instructions that
are available for a Logix5000 controller.
SERCOS Motion Configuration and Startup User Manual,
publication MOTION-UM001
Details how to configure a SERCOS motion application system.
Motion Coordinated Systems User Manual, publication
MOTION-UM002
Details how to create and configure a coordinated motion application
system.
CIP Motion Configuration and Startup User Manual, publication
MOTION-UM003
Details how to configure a CIP motion application system.
Logix5000 Controllers Motion Instructions Reference Manual,
publication MOTION-RM002
Provides programmers with details about the motion instructions that
are available for a Logix5000 controller.
SERCOS Motion Configuration and Startup User Manual,
publication MOTION-UM001
Details how to configure a SERCOS motion application system.
Instructions (used in programming)
Motion
14
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Preface
For more information about
See This Resource
Description
Networks (ControlNet, DeviceNet
EtherNet/IP, serial, and others)
EtherNet/IP Modules in Logix5000 Control Systems User Manual,
publication ENET-UM001
Describes how to configure and operate EtherNet/IP modules in a
Logix5000 control system.
ControlNet Modules in Logix5000 Control Systems User Manual,
publication CNET-UM001
Describes how to configure and operate ControlNet modules in a
Logix5000 control system.
DeviceNet Modules in Logix5000 Control Systems User Manual,
publication DNET-UM004
Describes how to configure and operate DeviceNet modules in a
Logix5000 control system.
ControlLogix Data Highway Plus - Universal Remote I/O Module
User Manual, publication 1756-UM514
Describes how to configure and operate the ControlLogix 1756 DH+
remote I/O module.
ControlLogix DH-485 Communication Module User Manual,
publication 1756-UM532
Describes how to configure and operate the ControlLogix 1756 DH-485
module.
Foundation Fieldbus Linking Device User Manual, publication
1757-UM010
Describes how to install, configure, and operate the 1757-FFLD linking
device.
Using Logix5000 Controllers as Masters or Slaves on Modbus
Application Solution, publication CIG-AP129
Provides information to experienced Modbus users who are
programming and troubleshooting applications that use Logix5000
controllers on Modbus.
Using Logix5000 Controllers as Masters or Slaves on Modbus
Application Solution, publication CIG-AP129
Provides information to experienced Modbus users who are
programming and troubleshooting applications that use Logix5000
controllers on Modbus.
PhaseManager
PhaseManager User Manual, publication LOGIX-UM001
Provides steps, guidance, and examples for setting up and
programming a Logix5000 controller to use equipment phases.
Programming tasks and procedures
Logix5000 Controllers Common Procedures Programming
Manual, publication 1756-PM001
Provides links to programming manuals that explain common
programming procedures.
Logix5000 Controllers Nonvolatile Memory Programming
Manual, publication 1756-PM017
Explains various procedures related to the use of memory cards.
Logix5000 Controllers Produced and Consumed Tags
Programming Manual, publication 1756-PM011
Explains produced and consumed tags and information related to
using them in your program.
Logix5000 Controllers Messages, publication 1756-PM012
Explains details about caching, managing multiple messages, and
sending messages to multiple controllers.
Logix5000 Controllers and I/O Tag Data Programming Manual,
publication 1756-PM004
Explains procedures for using and organizing I/O data tags.
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 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 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
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.
ControlLogix Enhanced Redundancy System, Revision 16.80
Release Notes, publication 1756-RN650
Describes the enhancements, corrected anomalies, and known
anomalies specific to the current firmware revision for an enhanced
redundancy system.
Using Logix5000 Controllers as Masters or Slaves on Modbus
Application Solution, publication CIG-AP129
Provides information to experienced Modbus users who are
programming and troubleshooting applications that use Logix5000
controllers on Modbus.
Redundancy
Serial communication
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
15
Preface
For more information about
See This Resource
Description
SIL2
Using ControlLogix in SIL 2 Applications Reference Manual,
publication 1756-RM001
Provides list of ControlLogix system components that meet SIL 2
requirements as well as programming requirements.
ControlLogix SIL2 System Configuration Using RSLogix 5000
Subroutines, publication 1756-AT010
Explains how to use subroutines provided by Rockwell Automation to
configure a fault-tolerant system.
ControlLogix SIL2 System Configuration Using RSLogix 5000
Subroutines, publication 1756-AT012
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 Allen-Bradley™ distributor or
Rockwell Automation sales representative.
16
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Chapter
1
Install the 1756-L7x Controller
Topic
Page
Before You Begin
20
1756-L7x Controller Parts
20
1756-L7x Controller Installation
21
Insert the Controller into the Chassis
21
Insert the Key
22
Install the SD Card
24
Remove the SD Card
23
Uninstall the ESM
25
Install the ESM
28
Additional Resources
30
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 or be approved for the application if nonmetallic. 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 the following:
• 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 enclosure
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
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
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.
CompactFlash/SD Card Capability
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.
18
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Install the 1756-L7x Controller
Chapter 1
USB Port
WARNING: Do not use the USB port in hazardous locations.
ATTENTION: The USB cable is not to exceed 3.0 m (9.84 ft) and must not contain hubs.
North American Hazardous Location Approval
The following information applies when operating this equipment in hazardous
locations.
Products marked &quot;CL I, DIV 2, GP A, B, C, D&quot; 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 &quot;T&quot; 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.
Informations sur l'utilisation de cet &eacute;quipement en environnements
dangereux.
Les produits marqu&eacute;s &quot;CL I, DIV 2, GP A, B, C, D&quot; ne conviennent qu'&agrave;
une utilisation en environnements de Classe I Division 2 Groupes A,
B, C, D dangereux et non dangereux. Chaque produit est livr&eacute; avec
des marquages sur sa plaque d'identification qui indiquent le code
de temp&eacute;rature pour les environnements dangereux. Lorsque
plusieurs produits sont combin&eacute;s dans un syst&egrave;me, le code de
temp&eacute;rature le plus d&eacute;favorable (code de temp&eacute;rature le plus faible)
peut &ecirc;tre utilis&eacute; pour d&eacute;terminer le code de temp&eacute;rature global du
syst&egrave;me. Les combinaisons d'&eacute;quipements dans le syst&egrave;me sont
sujettes &agrave; inspection par les autorit&eacute;s locales qualifi&eacute;es au moment
de l'installation.
EXPLOSION HAZARD
RISQUE D’EXPLOSION –
• 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.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
• Couper le courant ou s'assurer que
l'environnement est class&eacute; non
dangereux avant de d&eacute;brancher
l'&eacute;quipement.
• Couper le courant ou s'assurer que
l'environnement est class&eacute; non
dangereux avant de d&eacute;brancher les
connecteurs. Fixer tous les
connecteurs externes reli&eacute;s &agrave; cet
&eacute;quipement &agrave; l'aide de vis, loquets
coulissants, connecteurs filet&eacute;s ou
autres moyens fournis avec ce
produit.
• La substitution de composants peut
rendre cet &eacute;quipement inadapt&eacute; &agrave;
une utilisation en environnement de
Classe I, Division 2.
• S'assurer que l'environnement est
class&eacute; non dangereux avant de
changer les piles.
19
Chapter 1
Install the 1756-L7x Controller
Before You Begin
1756-L7x Controller Parts
Complete these tasks using the appropriate resources listed as references before
you install your controller and power supply.
Task
Resources
Install a ControlLogix Chasis and Power
Supply
Refer to ControlLogix Chasis and Power Supplies, publication 1756-IN005
These sections describe parts that are included with the L7x controllers, as well as
available accessory parts.
Parts Included with the 1756-L7x Controller
These parts are included with the 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
Logix 5575
RUN FORCESD
OK
SD Card (installed)
1756-ESMCAP
(installed)
1747-KY Key
IMPORTANT
20
32016-M
The 1756-L7x controllers ship with an SD card installed. We recommend that
you leave the SD card installed.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
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
Then use this part
USB connection from a computer to the controller
USB cable(1)
Nonvolatile memory
1784-SD1 (1 GB) or 1784-SD2 (2 GB)
ESM without WallClockTime back-up power
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 40 μJoule or less before transporting it into or out of your application.(2)
Additionally, you can use this ESM with a 1756-L73
(8 MB) or smaller memory-sized controller only.
ESM that secures the controller by preventing the USB connection and SD card use(2)
This ESM provides your application an enhanced degree of security
1756-ESMNRM
(1) The USB port is intended for temporary local programming purposes only and not intended for permanent connection. The USB cable is not to exceed 3.0 m (9.84 ft) and must not contain hubs.
(2) For information about the hold-up time of the ESMs, see the section Hold-up Time (in days)on page 74. and stored energy depletion rate on page 26.
These sections explain how to install the 1756-L7x controller. To install the
1756-L7x controller, complete the tasks summarized in this table.
1756-L7x Controller
Installation

Insert the Controller into the
Chassis
Task
Page
Insert the Controller into the Chassis
21
Insert the Key
22
Remove the SD Card
24
Install the SD Card
24
Uninstall the ESM
25
Install the ESM
28
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-UM001M-EN-P - February 2012
21
Chapter 1
Install the 1756-L7x Controller
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
Bottom Circuit Board
Aligned
OK
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 on page 199 for information about interpreting the status indicators.
Insert the Key
After the controller is installed, insert the key.
Logix 55xx
RUN FORCESD
22
OK
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Install the 1756-L7x Controller
Remove the SD Card
Chapter 1
The 1756-L7x controller ships with an SD card installed. Complete these steps to
remove the SD card from the 1756-L7x 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 1784SD1 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.
2. Open the door to access the SD card.
Logix 55xx
RUN FORCESD
OK
32015-M
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
23
Chapter 1
Install the 1756-L7x Controller
3. Press and release the SD card to eject it.
Logix 55xx
RUN FORCESD
OK
32004-M
4. Remove the SD card and close the door.
Install the SD Card
Complete these steps to install the SD card in the 1756-L7x controllers.
1. Verify that the SD card is locked or unlocked according to your preference.
Unlocked
Locked
32005-M
For more information about the lock/unlock memory settings in
RSLogix 5000™ software, see the Load or Store to the Memory Card
section on page 66.
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.
24
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Install the 1756-L7x Controller
Chapter 1
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
32006-M
Uninstall the ESM
Consider these points before removing the ESM:
WARNING: If your application requires the ESM to deplete its residual stored
energy to 40 μJoule or less before you transport it into or out of the application,
use the 1756-(SP)ESMNSE(XT) module only. In this case, complete these steps
before you remove the ESM.
1. 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.
2. Wait at least 20 minutes for the residual stored energy to decrease to 40 μJoule or less before you
remove the ESM.
There is no visual indication of when the 20 minutes has expired. You must track that
time period.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
25
Chapter 1
Install the 1756-L7x Controller
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.
• The following ESM modules may be currently installed in your 1756-L7x
or 1756-L7xXT controller:
• 1756-ESMCAP
• 1756-ESMNSE
• 1756-ESMCAPXT
• 1756-ESMNSEXT
• The 1756-L7x controllers come with the 1756-ESMCAP module already
installed. The 1756-L7xXT extreme temperature controller ships with a
1756-ESMCAPXT module already installed. For more information on
how to use a 1756-ESMNSE, 1756-ESMNRM, 1756-ESMNSEXT, or
1756-ESMNRMXT module, see page 28.
• After the 1756-L7x or 1756-L7xXT 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 40 μJoule or less before
transporting it into or out of your application.
• Once it is installed, you cannot remove the 1756-ESMNRM or 1756ESMNRMXT module from a 1756-L7x or 1756-L7xXT controller.
IMPORTANT
26
Before you remove an ESM, make necessary adjustments to your program
to account for potential changes to the WallClockTime attribute.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Install the 1756-L7x Controller
Chapter 1
Complete these steps to remove an ESM module from the controller.
1. Remove the key from the mode switch.
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, go to
step 2.
• 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 step 2.
2. Use your thumb to press down on the black release and pull the ESM away
from the controller.
Logix 55xx
RUN FORCESD
OK
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Logix 55xx
RUN FORCESD
OK
27
Chapter 1
Install the 1756-L7x Controller
Install the ESM
To install an ESM in the 1756-L7x 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
TIP
28
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.
We recommend that you check the WallClockTime object attributes after
installing an ESM to verify that time of the controller is correct.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Chapter
2
Install the 1756-L6x Controller
Precautions
Topic
Page
Precautions
29
Before You Begin
32
1756-L6x Controller Parts
32
1756-L6x Controller Installation
34
CompactFlash Card Installation and Removal
34
Battery Connection and Replacement
36
Insert the Controller into the Chassis
39
Remove the Controller from the Chassis
40
Additional Resources
43
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 or be approved for the application if nonmetallic. 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 the following:
• 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 enclosure
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
29
Chapter 2
Install the 1756-L6x Controller
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.
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.
30
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Install the 1756-L6x Controller
Chapter 2
USB Port
WARNING: Do not use the USB port in hazardous locations.
ATTENTION: The USB port is intended for temporary local programming purposes only and not intended for permanent
connection. The USB cable is not to exceed 3.0 m (9.84 ft) and must not contain hubs.
North American Hazardous Location Approval
The following information applies when operating this equipment in
hazardous locations.
Products marked &quot;CL I, DIV 2, GP A, B, C, D&quot; 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 &quot;T&quot; 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.
Informations sur l’utilisation de cet &eacute;quipement en environnements
dangereux.
Les produits marqu&eacute;s &quot;CL I, DIV 2, GP A, B, C, D&quot; ne conviennent qu'&agrave;
une utilisation en environnements de Classe I Division 2 Groupes A, B,
C, D dangereux et non dangereux. Chaque produit est livr&eacute; avec des
marquages sur sa plaque d'identification qui indiquent le code de
temp&eacute;rature pour les environnements dangereux. Lorsque plusieurs
produits sont combin&eacute;s dans un syst&egrave;me, le code de temp&eacute;rature le
plus d&eacute;favorable (code de temp&eacute;rature le plus faible) peut &ecirc;tre utilis&eacute;
pour d&eacute;terminer le code de temp&eacute;rature global du syst&egrave;me. Les
combinaisons d'&eacute;quipements dans le syst&egrave;me sont sujettes &agrave;
inspection par les autorit&eacute;s locales qualifi&eacute;es au moment de
l'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.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
RISQUE D’EXPLOSION –
• Couper le courant ou s'assurer que
l'environnement est class&eacute; non
dangereux avant de d&eacute;brancher
l'&eacute;quipement.
• Couper le courant ou s'assurer que
l'environnement est class&eacute; non
dangereux avant de d&eacute;brancher les
connecteurs. Fixer tous les connecteurs
externes reli&eacute;s &agrave; cet &eacute;quipement &agrave;
l'aide de vis, loquets coulissants,
connecteurs filet&eacute;s ou autres moyens
fournis avec ce produit.
• La substitution de composants peut
rendre cet &eacute;quipement inadapt&eacute; &agrave; une
utilisation en environnement de Classe
I, Division 2.
• S'assurer que l'environnement est
class&eacute; non dangereux avant de changer
les piles.
31
Chapter 2
Install the 1756-L6x Controller
Lithium Batteries
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 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.
Before You Begin
1756-L6x Controller Parts
Complete these tasks using the appropriate resources listed as references
beforeyou install your controller and power supply.
Task
Resources
Install a ControlLogix&reg; Chasis and
Power Supply
Refer to ControlLogix Chasis and Power Supplies, publication 1756-IN005
These sections describe parts that are included with the 1756-L6x controllers, as
well as available accessory parts.
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
RS232
BAT
RUN
OK
REM
PROG
1747-KY Key
32
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
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
Then use this component
RS-232 connection to the controller
1756-CP3 serial cable
Nonvolatile memory
1784-CF128 CompactFlash card
Expanded battery life for extended memory retention
1756-BATM battery module(1)
(1) 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.
IMPORTANT
The 1756-BATM battery module supports memory retention only when the
controller is in the chassis and the battery module is properly connected.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
33
Chapter 2
Install the 1756-L6x Controller
1756-L6x Controller
Installation
CompactFlash Card
Installation and Removal
These sections explain how to install a 1756-L6x controller. To install the 1756L6x controller, complete the tasks summarized in this table.

Task
Page
CompactFlash Card Installation and Removal
34
Battery Connection and Replacement
36
Insert the Controller into the Chassis
39
Remove the Controller from the Chassis
40
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 34.
– Remove a CompactFlash Card from a Series A Controller, page 35.
• If you are using a series B controller, reference these sections:
– Install a CompactFlash Card in a Series B Controller, page 35.
– Remove a CompactFlash Card from a Series B Controller, page 36.
Install a CompactFlash Card in a Series A Controller
Complete these steps to install a CompactFlash card in a series A controller.
2.
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.
34
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
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 mode switch 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&reg; logo pointing left.
3. Release the latch and secure it over the CompactFlash card.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
35
Chapter 2
Install the 1756-L6x Controller
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.
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.
Battery Connection and
Replacement
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.
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.
36
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Install the 1756-L6x Controller
Chapter 2
IMPORTANT: 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
Replace the battery within
-25…35 &deg;C (-13…95 &deg;F)
No replacement required
36…40 &deg;C (96.8…104 &deg;F)
3 years
41…45 &deg;C (105.8…113 &deg;F)
2 years
46…50 &deg;C (114.8…122 &deg;F)
16 months
51…55 &deg;C (123.8…131 &deg;F)
11 months
56…70 &deg;C (132.8…158 &deg;F)
8 months
ATTENTION: Store batteries in a cool, dry environment. We
recommend 25 &deg;C (77 &deg;F) with 40…60% relative humidity. You may
store batteries for up to 30 days between -45…85 &deg;C
(-49…185 &deg;F), such as during transportation. To avoid leakage or
other hazards, do not store batteries above 60 &deg;C (140 &deg;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 38.
• If you are using a series B controller, see page 39.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
37
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-BATM 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
Connected Wire
Top
No Connection
Middle
Black Lead (-)
Bottom
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.
38
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
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.
COMPACT
FLASH
1-DCD
2-RXD
3-TXD
4-DTR
5-GND
DSR-6
RTS-7
CTS-8
N/C-9
RS232
1 To
Insert 1
2 To Eject
1+2
1
2
UP
BATTERY
DATE
1
DATE
2
BATTERY
PORT
30563-M
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.
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-UM001M-EN-P - February 2012
39
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 199 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.
40
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Install the 1756-L6x Controller
Chapter 2
1. Press the locking tabs on the top and bottom of the controller.
2. Slide the controller out of the chassis.
1.
2.
20880
1.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
41
Chapter 2
Install the 1756-L6x Controller
Notes:
42
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Chapter
3
Start Using the Controller
Make Connections
Topic
Page
Make Connections
43
Connect to the 1756-L7x Controller
45
Connect to the 1756-L6x Controller
48
Upgrade Controller Firmware
51
Set the Communication Path
58
Go Online with the Controller
59
Download to the Controller
60
Upload from the Controller
61
Choose the Controller Operation Mode
63
Use the Mode Switch to Change the Operation Mode
63
Use RSLogix 5000 Software to Change the Operation Mode
65
Load or Store to the Memory Card
66
Use ControlLogix Energy Storage Modules (ESMs)
72
Estimate the ESM Support of the WallClockTime
74
Maintain the Battery (1756-L6x controllers only)
75
Additional Resources
81
Before you can begin using your controller, you must make a connection to the
controller.
1756-L7x Connection Options
Connection options with the 1756-L7x include the following:
• Connecting using a USB cable, see Connect to the 1756-L7x Controller
on page 45
• Installing and configuring a communication module in the chassis with
the controller, refer to the installation instructions of the communication
module
For information on Double Data Rate (DDR) backplane communication usage,
see Double Data Rate (DDR) Backplane Communication on page 95.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
43
Chapter 3
Start Using the Controller
1756-L6x Connection Options
Connection options with the 1756-L6x include the following:
• Connecting using a serial cable, see Connect to the 1756-L6x Controller
on page 48
• Installing and configuring a communication module in the chassis with
the controller, refer to the installation instructions of the communication
module
TIP
44
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.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Start Using the Controller
Connect to the 1756-L7x
Controller
Chapter 3
The controller has a USB port that uses a Type B receptacle. The port is USB 2.0compatible and runs at 12 Mbps.
To use the USB port of the controller, you must have RSLinx&reg; 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 port is intended for temporary local programming
purposes only and not intended for permanent connection. The USB cable is
not to exceed 3.0 m (9.84 ft) and must not contain hubs.
WARNING: Do not use the USB port in hazardous locations.
USB Connection
Logix 55xx
RUN FORCESD
OK
32007-M
32007-M
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
45
Chapter 3
Start Using the Controller
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.
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&reg; Classic software, version 2.56 or later.
3. Click Install the software automatically (Recommended) and click Next.
46
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Start Using the Controller
Chapter 3
The software is installed.
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.
Virtual Chassis Driver
USB Port Driver
Your controller appears under two different drivers, a virtual chassis and the USB
port. You can use either driver to browse to your controller.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
47
Chapter 3
Start Using the Controller
Connect to the 1756-L6x
Controller
The 1756-L6x 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
48
To Controller
1 CD
1 CD
2 RDX
2 RDX
3 TXD
3 TXD
4 DTR
4 DTR
COMMON
COMMON
6 DSR
6 DSR
7 RTS
7 RTS
8 CTS
8 CTS
9
9
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
42231
Start Using the Controller
Chapter 3
Plug the workstation end of the serial cable into the RS-232 port on the front of
the controller.
COMPACT
FLASH
DSR-6
RTS-7
CTS-8
N/C-9
1-DCD
2-RXD
3-TXD
4-DTR
5-GND
RS232
1 To
Insert 1
2 To Eject
1+2
1
2
UP
BATTERY
DATE
1
2
BATTERY
PORT
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.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
49
Chapter 3
Start Using the Controller
The Configure Drivers dialog box appears.
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.
50
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Start Using the Controller
Chapter 3
c. Click Auto-Configure.
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.
Upgrade Controller Firmware 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
To upgrade your controller firmware, complete the appropriate tasks listed in this
table.

Task
Page
Determine Required Controller Firmware
52
Obtain Controller Firmware
53
Use ControlFLASH Utility to Upgrade Firmware
53
Use AutoFlash to Upgrade Firmware
56
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
51
Chapter 3
Start Using the Controller
Determine Required Controller Firmware
The controller must be in Remote Program or Program mode and all major
recoverable faults cleared to accept upgrades.
IMPORTANT
Use this table to determine what firmware revision is required for your controller.
Table 5 - Firmware Required For Controllers
Controller
Series
Use this firmware revision
1756-L61
A
12.x or later
B
13.40 or later
A
12.x or later
B
13.40 or later
A
• If not using a CompactFlash card, 10.x or later
• If using a CompactFlash card, 11.x or later
B
13.40 or later
1756-L63XT
B
13.40 or later
1756-L64
B
16 or later
1756-L65
B
17 or later
1756-L71
A
20 or later
1756-L72
A
19 or later
1756-L73
A
19 or later
1756-L73XT
A
19 or later
1756-L74
A
19 or later
1756-L75
A
19 or later
1756-L62
1756-L63
52
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Start Using the Controller
Chapter 3
Obtain Controller Firmware
Controller firmware is packaged with RSLogix 5000 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.
3. Select the catalog number of your controller and click Next.
1756-L7x Controllers
1756-L6x Controllers
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
53
Chapter 3
Start Using the Controller
4. Expand the network driver to locate your controller.
1756-L7x Controller with USB Network Driver
1756-L6x Controller with Ethernet Network Driver
5. Select your controller and click Next.
6. Select the firmware revision you want to upgrade to and click Next.
1756-L7x Controller Upgrade
54
1756-L6x Controller Upgrade
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Start Using the Controller
TIP
Chapter 3
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 upgrade. 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.
A confirmation dialog box opens.
8. Click Yes.
The progress dialog box indicates the progress of the firmware upgrade.
The 1756-L7x controllers indicate progress in updates and blocks, where
the 1756-L6x controllers indicate progress only in blocks.
1756-L7x Controller Progress
1756-L6x Controller Progress
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-L6x and
1756-L7x controllers revert to boot firmware, that is firmware revision 1.xxx.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
55
Chapter 3
Start Using the Controller
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 software to create a controller project at the version you
need.
3. Click RSWho to specify the controller path.
56
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Start Using the Controller
Chapter 3
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.
6. Click Yes.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
57
Chapter 3
Start Using the Controller
The firmware upgrade begins.
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 communication path in
RSLogix 5000 software. You can specify the communication path after you’ve
created the RSLogix 5000 program.
Complete these steps to specify the communication path after you have created
your program.
1. Click Who Active.
58
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Start Using the Controller
Chapter 3
2. Expand the communication path and select the controller.
3. Click Set Project Path.
Go Online with the Controller 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.
• From the Controller Status menu, choose Go Online.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
59
Chapter 3
Start Using the Controller
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 60
• Use the Controller Status Menu to Download, page 61
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.
60
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Start Using the Controller
Chapter 3
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.
Download via the Controller Status Menu
TIP
Upload from the Controller
After the download completes on a 1756-L7x controller, the project name is
indicated on the scrolling status display.
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 61
• Use the Controller Status Menu to Upload, page 62
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.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
61
Chapter 3
Start Using the Controller
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.
Upload via the Controller Status Menu
62
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Start Using the Controller
Choose the Controller
Operation Mode
Chapter 3
Use this table as a reference when determining your controller Operation mode.
Table 6 - Controller Operation Modes and Meanings
Select one of these modes
If you want to
Run
Remote
Turn outputs to the state commanded by the
logic of the project
X
X
Run
Turn outputs to their configured state for
Program mode
Execute (scan) tasks
X
Program
Test
Program
X
X
X
X
X
Change the mode of the controller through
software
X
X
X
Download a project
X
X
X
X
X
X
X
X
Schedule a ControlNet network
While online, edit the project
X
X
Send messages
X
X
X
Send and receive data in response to a message
from another controller
X
X
X
X
X
Produce and consume tags
X
X
X
X
X
Use the Mode Switch to Change the Operation Mode
Use the mode switch to change the operation mode. The controller mode switch
provides a mechanical means to enhance controller and control system security.
You must physically move the controller’s mode switch to change its operating
mode from RUN, to REM, or to PROG. When the controller’s mode switch is
set to RUN mode, features like online editing, program downloads, and firmware
upgrades will be prohibited. See Table 6 for a complete list of prohibited features.
The physical mode switch can complement other authorization and
authentication methods that similarly control user-access to the controller, such
as the following:
• Logix CPU Security tool
• FactoryTalk Security service
IMPORTANT
During runtime, we recommend that you place the controller mode switch in
RUN mode and remove the key (if applicable) from the switch. This can help
discourage unauthorized access to the controller or potential tampering with
the controller’s program, configuration, or device firmware. Place the mode
switch in REM or PROG mode during controller commissioning and
maintenance and whenever temporary access is necessary to change the
product’s program, configuration, or firmware.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
63
Chapter 3
Start Using the Controller
The mode switch on the front of the controller can be used to change the
controller to one of these modes:
• Run (RUN)
• Remote (REM)
• Program (PROG)
1756-L7x
1756-L6x
Logix556x
Logix557x
RUN FORCE SD
OK
REM PR
OG
RUN
Mode Switch
Mode Switch Position
Available Controller Modes
RUN
Run mode - The controller is actively controlling the
process/machine. Projects cannot be edited in RSLogix
5000 software when in Run mode.
Run mode should only be used when all conditions are
safe.
REM
Remote Run mode - This mode is identical to Run mode
except you can edit the project online.
Users are able to modify a project file online in Remote
Run mode.
Be sure to control outputs with care to avoid injury to
personnel and damage to equipment.
Remote Program mode - This mode is identical to
Program mode.
Remote Test mode - The controller mode during which
code is executing. I/O is not controlled, and limited editing
operations are available.
Output modules are commanded to their Program mode
state (on, off, or hold).
ATTENTION:
Outputs are commanded to their Program mode state,
which could cause a dangerous situation.
Note: The mode of the controller can be changed from
within RSLogix 5000 software.
PROG
Program mode - The controller mode during which
programming language is not executing.
I/O is not controlled, and limited editing operations are
available.
Do not use Program mode as an emergency stop (E-stop).
Program mode is not a safety device.
Outputs are commanded to their Program mode state,
which could cause a dangerous situation.
Output modules are commanded to their Program mode
state (on, off, or hold).
In this position, controller modes cannot be changed
through RSLogix 5000 software.
64
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Start Using the Controller
Chapter 3
Use RSLogix 5000 Software to Change the Operation Mode
Depending on the mode of the controller you specify by using the mode switch,
you can change the Operation mode of the controller using RSLogix 5000
software.
After you are online with the controller and the controller mode switch 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
Operation Mode via RSLogix 5000 Software
TIP
For this example, the controller mode switch is set to Remote mode. If your
controller mode switch is set to Run or Program modes, the menu options
change.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
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.
• 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. See step 4.
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.
The table below describes the Load Image options you can choose for the
project.
IMPORTANT
66
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.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Start Using the Controller
Chapter 3
Table 7 - Load Image Options
If you want the image (project) to load when
Then choose
Power to the controller is applied or cycled
On Power Up
The controller has lost the project and power has been cycled
or applied
On Corrupt Memory
Initiated by using RSLogix 5000 software
User Initiated
The table below describes the Load Mode options you can choose for the
project.
Table 8 - Load Mode Options
If you want the controller to go to this mode after
loading
Then choose
Program
Program (Remote Only)
Run
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.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
67
Chapter 3
Start Using the Controller
Table 9 - Automatic Firmware Update Options
If you want to
Then choose
Enable automatic firmware updates so I/O devices in the
configuration tree of the controller that are configured to
use Exact Match Keying are updated as required
Enable and Store Files to Image(1)
Disable automatic firmware updates and remove any I/O
firmware files that are stored with the image
Disable and Delete Files from Image
Disable automatic firmware updates when there are no
firmware files are stored with the image
Disable
(1) The devices used with this option must support the version of firmware being updated to.
4. Click Store, then click OK in the confirmation dialog box that appears.
Indicates the SD card is locked.
68
Store Dimmed (Unavailable).
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
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 10 - Store Project Status Indicators
With these controllers
These indications show the store status
1756-L6x
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
1756-L7x
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-UM001M-EN-P - February 2012
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.
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. Verify that the image in nonvolatile memory (that is, the project on the
memory card) is the project you want to load.
70
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-UM001M-EN-P - February 2012
Start Using the Controller
Chapter 3
4. Click Load.
After clicking Load, the project is loaded to the controller as indicated by
the controller status indicators.
Table 11 - Load Project Status Indicators
With these controllers
These indications show the store status
1756-L6x
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
1756-L7x
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-UM001M-EN-P - February 2012
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
Memory.
The following table describes the ESMs.
Cat. No.
1756-ESMCAP
1756-ESMNSE
1756-ESMNRM
72
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 40&micro;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.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
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
N REM PRO
RU
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.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
73
Chapter 3
Start Using the Controller
Clear the Program from On-board NVS Memory
If your application allows it, follow these steps to clear the program from the
1756-L7x controller’s on-board NVS memory.
1. Remove the ESM from the controller.
2. Remove power from 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 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 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.
Hold-up Time (in days)
Temperature
1756-ESMCAP
1756-ESMNRM
1756-ESMNSE
20 &deg;C (68 &deg;F)
12
12
0
40 &deg;C (104 &deg;F)
10
10
0
60 &deg;C (140 &deg;F)
7
7
0
IMPORTANT
74
Any action causing the 1756-L7x controller to reset (hard or soft), without an
ESM installed, will result in the controller’s wall clock time being reset to the
factory default of 01/01/1998.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Start Using the Controller
Maintain the Battery
(1756-L6x controllers only)
Chapter 3
This explains how to monitor and maintain the lithium batteries supported by
ControlLogix controllers.
Table 12 - 1756-L6x Controllers and Compatible Batteries
Cat. No.
Series
Compatible Battery
1756-L61
1756-L62
1756-L63
A
1756-BA1 or
1756-BATA or
1756-BATM
1756-L61
1756-L62
1756-L63
1756-L64
1756-L65
B
1756-BA2
1756-L63XT
B
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
75
Chapter 3
Start Using the Controller
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.
IMPORTANT: 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
Replace the battery within
-25…35 &deg;C (-13…95 &deg;F)
No replacement required
36…40 &deg;C (96.8…104 &deg;F)
3 years
41…45 &deg;C (105.8…113 &deg;F)
2 years
46…50 &deg;C (114.8…122 &deg;F)
16 months
51…55 &deg;C (123.8…131 &deg;F)
11 months
56…70 &deg;C (132.8…158 &deg;F)
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-L6x, 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.
76
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Start Using the Controller
Chapter 3
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 13 - Worst-case Estimates of 1756-BA1 Battery Life
Temperature
Battery Life Before BAT Status Indicator Turns On
Battery Life After BAT Status Indicator Turns On
and Power is Cut Off
Power Off 100%
Power Off 50%
Yearly Decrease
60 &deg;C (140 &deg;F)
22 days
43 days
23%
6 hrs
25 &deg;C (77 &deg;F)
21 days
42 days
17%
28 hrs
0 &deg;C (32 &deg;F)
14 days
28 days
17%
2.5 days
Table 14 - Worst-case Estimates of 1756-BATA Battery Life
Temperature
Battery Life Before BAT Status Indicator Turns On
Battery Life After BAT Status Indicator Turns On
and Power is Cut Off
Power Off 100%
Power Off 50%
Yearly Decrease
60 &deg;C (140 &deg;F)
98 days
204 days
11%
104 days
25 &deg;C (77 &deg;F)
146 days
268 days
5%
157 days
0 &deg;C (32 &deg;F)
105 days
222 days
6%
113 days
1756-BATM Battery Module and Battery Life
Use the 1756-BATM battery module with any 1756-L6x, series A controller. The
battery module is highly recommended for the higher-memory controllers.
If your project is
Then use of the 1756-BATM battery module is
Not stored in nonvolatile memory
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.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
77
Chapter 3
Start Using the Controller
Estimate 1756-BA2 Battery Life
The 1756-BA2 batteries are for use in 1756-L6x controllers, series B. Use this
table to estimate how much time will elapse before the battery becomes low.
Table 15 - Worst-case Estimates of 1756-BA2 Life According to Temperatures and Power Cycles
Temperature 2.54 cm (1 in.) Below
the Chassis, max
Power Cycles
Battery Life Before the BAT Status Indicator Turns Red
Project Size
1 MB
2 MB
4 MB
8 MB
16 MB
3 per day
3 years
3 years
26 months
20 months
10 months
2 per day or less
3 years
3 years
3 years
31 months
16 months
3 per day
2 years
2 years
2 years
20 months
10 months
2 per day or less
2 years
2 years
2 years
2 years
16 months
46...50 &deg;C (105.8...113 &deg;F)
3 per day or less
16 months
16 months
16 months
16 months
10 months
51...55 &deg;C (123.8...131 &deg;F)
3 per day or less
11 months
11 months
11 months
11 months
10 months
56…70 &deg;C (132.8…158 &deg;F)
3 per day or less
8 months
8 months
8 months
8 months
8 months
-25…35 &deg;C (-13…95 &deg;F)
41...45 &deg;C (105.8...113 &deg;F)
78
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Start Using the Controller
Chapter 3
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
Temperature 2.54 cm (1 in.)
Below the Chassis, max
0...20 &deg;C (32...68 &deg;F)
21...40 &deg;C (69.8...104 &deg;F)
41...45 &deg;C (105.8...113 &deg;F)
46...50 &deg;C (105.8...113 &deg;F)
51...55 &deg;C (123.8...131 &deg;F)
56...60 &deg;C (132.8...140 &deg;F)
Power Cycles
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.
Battery Life After the BAT Status Indicator Turns Red (worst case)
Project Size
1 MB
2 MB
4 MB
8 MB
16 MB
3 per day
26 weeks
18 weeks
12 weeks
9 weeks
5 weeks
1 per day
26 weeks
26 weeks
26 weeks
22 weeks
13 weeks
1 per month
26 weeks
26 weeks
26 weeks
26 weeks
26 weeks
3 per day
18 weeks
14 weeks
10 weeks
8 weeks
5 weeks
1 per day
24 weeks
21 weeks
18 weeks
16 weeks
11 weeks
1 per month
26 weeks
26 weeks
26 weeks
26 weeks
26 weeks
3 per day
12 weeks
10 weeks
7 weeks
6 weeks
4 weeks
1 per day
15 weeks
14 weeks
12 weeks
11 weeks
8 weeks
1 per month
17 weeks
17 weeks
17 weeks
17 weeks
16 weeks
3 per day
10 weeks
8 weeks
6 weeks
6 weeks
3 weeks
1 per day
12 weeks
11 weeks
10 weeks
9 weeks
7 weeks
1 per month
12 weeks
12 weeks
12 weeks
12 weeks
12 weeks
3 per day
7 weeks
6 weeks
5 weeks
4 weeks
3 weeks
1 per day
8 weeks
8 weeks
7 weeks
7 weeks
5 weeks
1 per month
8 weeks
8 weeks
8 weeks
8 weeks
8 weeks
3 per day
5 weeks
5 weeks
4 weeks
4 weeks
2 weeks
1 per day
6 weeks
6 weeks
5 weeks
5 weeks
4 weeks
1 per month
6 weeks
6 weeks
6 weeks
6 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 &deg;C
(113 &deg;F).
• You cycle power to the controller three times per day.
• The controller contains an 8 MB project.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
79
Chapter 3
Start Using the Controller
Battery Storage and Disposal
Follow these general rules to store your batteries:
• Store batteries in a cool, dry environment. We recommend
25 &deg;C (77 &deg;F) with 40…60% relative humidity.
• You may store batteries for up to 30 days in temperatures from -45...85
&deg;C (-49...185 &deg;F), such as during transportation.
• To avoid leakage or other hazards, do not store batteries above
60 &deg;C (140 &deg;F) for more than 30 days.
This product contains a sealed lithium battery that needs 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.
80
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Start Using the Controller
Additional Resources
Chapter 3
These documents contain additional information concerning related Rockwell
Automation products.
Resource
Description
Logix5000 Controllers Common Procedures Programming Manual, publication
1756-PM001
Provides links to programming manuals that explain common programming procedures.
Logix5000 Controllers Nonvolatile Memory Programming Manual, publication
1756-PM017
Explains various procedures related to the use of memory cards.
Guidelines for Handling Lithium Batteries, publication AG-5.4
Provides information regarding storage, handling, transportation, and disposal of lithium
batteries.
Programmable Controllers Battery Reference, http://www.ab.com/
programmablecontrol/batteries.html
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.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
81
Chapter 3
Start Using the Controller
Notes:
82
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Chapter
4
ControlLogix System and Controllers
The ControlLogix System
Topic
Page
The ControlLogix System
83
Design a ControlLogix System
86
ControlLogix Controller Features
87
Additional Resources
89
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 3 - Standalone Controller and I/O
Output
Output
Input
L75
32044-MC
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
83
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 4 - Multiple Controllers in One Chassis
EN2T
EN2T
L75
L75
FactoryTalk &reg;Server
Ethernet
Ethernet
Stratix 8000™ Switch
Kinetix 6500 Drive
Kinetix&reg; 6500 Drive
Motor
Motor
Motor
Kinetix 6500 Drive
84
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
32045-MC
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&reg; drive connected via a DeviceNet network
• Flowmeters connected via a HART connection
Figure 5 - Multiple Devices Connected via Multiple Networks
HART
IF8H
EN2T
EN2T
CN2
DNB
L75
HART
Endress + Hauser Flowmeter
DeviceNet
Ethernet
ControlNet
PowerFlex Drive
FactoryTalk Server
FLEX™ I/O
Ethernet Device-level Ring
Network
POINT I/O™
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
32046-MC
85
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.
86
For this type of application
See this publication
Motion with Integrated Motion on the
EtherNet/IP network
CIP Motion Configuration and Startup User Manual, publication
MOTION-UM003
Motion with the use of a coordinate system
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 1756RMXT modules. Also called enhanced
redundancy
ControlLogix Enhanced Redundancy System User Manual, publication
1756-UM535
Redundancy by using 1757-SRM modules.
Also called standard redundancy
ControlLogix Redundancy System User Manual, publication
1756-UM523
SIL2
Using ControlLogix in SIL2 Applications Safety Reference Manual,
publication 1756-RM001
SIL2 fault-tolerant I/O with RSLogix 5000
subroutines
ControlLogix SIL2 System Configuration Using RSLogix 5000
Subroutines Application Technique, publication 1756-AT010
SIL2 fault-tolerant I/O with RSLogix 5000
Add-On Instructions
ControlLogix SIL2 System Configuration Using SIL2 Add-On Instructions
Application Technique, publication 1756-AT012
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
ControlLogix System and Controllers
ControlLogix Controller
Features
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 16 - ControlLogix Controller Features
Feature
1756-L61, 1756-L62, 1756-L63,
1756-L64, 1756-L65
1756-L71, 1756-L72, 1756L73, 1756-L74, 1756-L75
Controller tasks
• 32 tasks
• 100 programs/task
• Event tasks: all event triggers
Communication ports
1port - RS-232 serial
Communication options
•
•
•
•
•
•
•
EtherNet/IP
ControlNet
DeviceNet
Data Highway Plus™
Remote I/O
SynchLink
Third-party process and device networks
Serial port communication
•
•
•
•
•
ASCII
DF1 full/half-duplex
DF1 radio modem
DH-485
Modbus via logic
Controller connections supported, max
250
Network connections, per network
module
•
•
•
•
Controller redundancy
Full support except for motion applications
Integrated motion
• Integrated Motion on the EtherNet/IP network
• SERCOS interface
• Analog options:
– Encoder input
– LDT input
– SSI input
Programming languages
•
•
•
•
1 port - USB, 2.0 full-speed,
Type B
N/A
500
100 ControlNet (1756-CN2/A)
40 ControlNet (1756-CNB)
256 EtherNet/IP; 128 TCP (1756-EN2x)
128 EtherNet/IP; 64 TCP (1756-ENBT)
Relay ladder
Structured text
Function block
Sequential Function Chart (SFC)
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
87
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 17 - ControlLogix Controller Memory Options
Controller
Memory for Data and
Logic
I/O
Back-up Memory
1756-L61
2 MB
478 KB
CompactFlash card(1)
1756-L62
4 MB
1756-L63, 1756-L63XT
8 MB
1756-L64
16 MB
1756-L65
32 MB
1756-L71
2 MB
0.98 MB (1006 KB)
SD card
1756-L72
4 MB
1756-L73, 1756-L73XT
8 MB
1756-L74
16 MB
1756-L75
32 MB
(1) These nonvolatile memory cards are optional and do not come with the controller.
88
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.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
ControlLogix System and Controllers
Chapter 4
These documents contain additional information specific to the ControlLogix
system design and selection.
Additional Resources
Resource
Description
ControlLogix Selection Guide, publication 1756-SG001
Provides methods for determining what ControlLogix components are required for your
system.
SERCOS Motion Configuration and Startup User Manual, publication
MOTION-UM001
Explains the configuration of Sercos and analog motion applications.
Motion Coordinated Systems User Manual, publication MOTION-UM002
Explains the configuration of coordinated motion applications.
CIP Motion Configuration and Startup User Manual, publication MOTION-UM003
Explains the configuration of Integrated Motion on the EtherNet/IP network.
ControlLogix Enhanced Redundancy System User Manual, publication 1756-UM535
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
Explains the configuration of SIL2-certified fault-tolerant systems that are configured by
using RSLogix 5000 subroutines.
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 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.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
89
Chapter 4
ControlLogix System and Controllers
Notes:
90
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Chapter
5
Communication Networks
Networks Available
Topic
Page
Networks Available
91
EtherNet/IP Network Communication
92
ControlNet Network Communication
95
DeviceNet Network Communication
98
Data Highway Plus (DH+) Network Communication
101
Universal Remote I/O (RIO) Communication
102
Foundation Fieldbus Communication
105
HART Communication
106
Additional Resources
107
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 18 - Applications and Supported Networks
Application Type
Supported Networks
Integrated Motion
EtherNet/IP
Integrated Motion on EtherNet/IP for time
synchronization
EtherNet/IP
Control of distributed I/O
•
•
•
•
•
•
Produce/consume data between controllers
• ControlNet
• EtherNet/IP
Messaging to and from other devices, including access to
the controller via RSLogix 5000 software
•
•
•
•
•
•
•
ControlNet
DeviceNet
EtherNet/IP
Foundation Fieldbus
HART
Universal remote I/O
EtherNet/ControlNet
DeviceNet (only to devices)
Data Highway Plus (DH+)
DH-485
EtherNet/IP
Serial
USB
For additional information about network design for your system,
See publication ENET-RM002.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
91
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 6 - EtherNet/IP Network Example
Distributed I/O
LINK NET OK
ControlLogix
Controller with
1756-EN2T Module
LINK NET OK
1756-EN2T Module
(as an adapter) with 1756 I/O
Modules
CompactLogix™ Controller
with Integrated EtherNet/IP
Port
1794-AENT Adapter with 1794
I/O Modules
Switch
1734-AENT Adapter with 1734
I/O Modules
PowerFlex&reg; 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
92
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
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 19 - EtherNet/IP Communication Modules and Capabilities
Module
Is used to
1756-ENBT
•
•
•
•
1756-EN2T
• 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.
1756-EN2F
• Perform the same functions as a 1756-EN2T module.
• Connect fiber media by an LC fiber connector on the module.
1756-EN2TR
• 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.
1756-EN3TR
•
•
•
•
1756-EN2TXT
• Perform the same functions as a 1756-EN2T module.
• Operate in extreme environments with -25…70 &deg;C (-13…158 &deg;F) temperatures.
1756-EWEB
• 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.
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 the 1756-EN2TR module.
Three ports for DLR connection.
Extended Integrated Motion on EtherNet/IP network
Up to 128 axis
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
93
Chapter 5
Communication Networks
Software for EtherNet/IP Networks
This table lists software that is used with the EtherNet/IP networks and modules.
Table 20 - Software for Use with EtherNet/IP Networks
Software
Is used to
Required/Optional
RSLogix 5000
• Configure ControlLogix projects.
• Define EtherNet/IP communication.
Required
RSLinx Classic or RSLinx&reg;
Enterprise
• Configure communication devices.
• Provide diagnostics.
• Establish communication between devices.
Required
RSLogix 5000 BOOTP/DHCP
Utility
Assign IP addresses to devices on an EtherNet/IP network.
Optional
RSNetWorx™ for EtherNet/IP • Configure EtherNet/IP devices by IP addresses and/or
host names.
• Provide bandwidth status.
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.
94
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Communication Networks
Chapter 5
Double Data Rate (DDR) Backplane Communication
DDR communication can be achieved with the 1756-L7x controller. These
communication modules support DDR when used in conjunction with the
1756-L7x controller:
• 1756-EN2T/C
• 1756-EN2TR/B
• 1756-EN2TF/B
• 1756-EN2TXT/C
• 1756-EN3TR/A
• 1756-RM/B
DDR communication is achieved most efficiently when all modules in the
communication path are DDR modules, or, in other words, as a single
conversation (connection) only between DDR modules.
DDR communication is achievable in a chassis with a mix of DDR and nonDDR modules. The DDR communication occurs between the modules that
support it. If non-DDR modules are also in the chassis, communication between
those modules will be at the non-DDR rate.
For example, you could have a chassis with two 1756-L7x controllers in slots 0
and 1 communicating with each other using DDR, and two 1756-L6x controllers
in slots 2 and 3 communicating using non-DDR.
When multicast communication is used within a chassis to multiple modules, the
transmission rate is limited to the slowest module—or at the non-DDR rate.
For example, if a 1756-L7x controller is producing a tag to a 1756-L7x controller
and a 1756-L6x controller on the same multicast connection, it must use the nonDDR rate.
ControlNet Network
Communication
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.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
95
Chapter 5
Communication Networks
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 7 - ControlNet Network Overview
Workstation
Distributed I/O
CompactLogix Controller
PowerFlex 700S AC Drive with
DriveLogix Software
1756-CNB Module (as an
adapter) with 1756 I/O
Modules
ControlNet Network
1794-ACN15 Adapter with
1794 I/O Modules
PanelView Terminal
FlexLogix Module
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.
96
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Communication Networks
Chapter 5
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 21 - ControlNet Modules and Capabilities
Module
Is used to
1756-CNB
•
•
•
•
1756-CNBR
• Perform the same functions as a 1756-CNB module.
• Support redundant ControlNet media.
1756-CN2
• Perform the same functions as a 1756-CNB module.
• Provide high-speed I/O bridge functionality; twice the capacity for more demanding
applications.
1756-CN2R
• Perform the same functions as a 1756-CN2 module.
• Support redundant ControlNet media.
1756-CN2RXT
• Perform same functions as a 1756-CN2R module.
• Operate in extreme environments with -25…70 &deg;C (-13…158 &deg;F) temperatures.
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.
Software for ControlNet Networks
This table lists software that is used with the ControlNet networks and modules.
Table 22 - Software for Use with ControlNet Networks
Software
Is used to
Required/Optional
RSLogix 5000
• Configure ControlLogix projects.
• Define ControlNet communication.
Required
RSNetWorx™ for
ControlNet™
• Configure ControlNet devices.
• Schedule a network.
RSLinx Classic or
Enterprise
• Configure communication devices.
• Provide diagnostics.
• Establish communication between devices.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
97
Chapter 5
Communication Networks
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 23 - 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.
DeviceNet Network
Communication
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.
98
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Communication Networks
Chapter 5
Figure 8 - ControlLogix DeviceNet Network Overview
ControlLogix Controller with
1756-ENBT Module
EtherNet/IP Network
CompactLogix Controller
FLEX I/O Adapter and
Modules
1788-EN2DN
DeviceNet Network
Personal Computer
Sensor
Pushbutton
Cluster
PWR
PWR
STS
Motor
Starter
STS
PORT
MOD
PORT
NET A
MOD
NET B
NET A
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-UM001M-EN-P - February 2012
99
Chapter 5
Communication Networks
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
Is used to
1756-DNB
• Control I/O modules.
• Communicate with other DeviceNet devices (via messages).
1788-EN2DN
Link an EtherNet/IP network to a DeviceNet network.
1788-CN2DN
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
Is used to
Required/Optional
RSLogix 5000
• Configure ControlLogix projects.
• Define DeviceNet communication.
Required
RSNetWorx™ for
DeviceNet™
• Configure DeviceNet devices.
• Define the scan list for those devices.
RSLinx Classic or Enterprise
• Configure communication devices.
• Provide diagnostics.
• Establish communication between devices.
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 1756DNB module supports up to add the following:
• 124 DINTs of input data
• 123 DINTs of output data
100
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Communication Networks
Data Highway Plus (DH+)
Network Communication
Chapter 5
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 9 - ControlLogix DH+ Network Communication Example
Data Collection and Recipe
Management
Workstation
EtherNet/IP Network
ControlLogix
Controller
ControlLogix
Controller
DH+ Network
DH+ Network
PLC-5 Controller
SLC™ 500 Controller
RSView&reg; Station
PLC-5 Controller
SLC 500 Controller
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
RSView Station
101
Chapter 5
Communication Networks
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.
For more information about configuring and using a DH+ network via the 1756DHRIO 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
Is used to
1756-RIO
• 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.
1756-DHRIO
•
•
•
•
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.
102
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Communication Networks
Chapter 5
Figure 10 - 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-UM001M-EN-P - February 2012
103
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.
104
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Communication Networks
Foundation Fieldbus
Communication
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
Is used to
1757-FFLD
• 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.
1788-CN2FF
• 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 11 - 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-UM001M-EN-P - February 2012
105
Chapter 5
Communication Networks
HART Communication
HART (Highway Addressable Remote Transducer) is an open protocol designed
for process control instrumentation.
Device
Is used to
1756 Analog I/O modules
• 1756-IF8H
• 1756-OF8H
• 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).
ProSoft interface
• MVI56-HART
• 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 12 - 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.
106
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Communication Networks
Additional Resources
Chapter 5
These documents contain additional information concerning products from
Rockwell Automation.
Resource
Description
EtherNet/IP Modules in Logix5000 Control Systems User Manual, publication ENET-UM001 Describes how to configure and operate EtherNet/IP modules in a Logix5000 control
system.
ControlNet Modules in Logix5000 Control Systems User Manual, publication CNET-UM001
Describes how to configure and operate ControlNet modules in a Logix5000 control
system.
DeviceNet Modules in Logix5000 Control Systems User Manual, publication DNET-UM004
Describes how to configure and operate DeviceNet modules in a Logix5000 control
system.
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 General Instructions Reference Manual, publication 1756-RM003
Provides programmers with details about each available instruction for a Logix5000
controller.
Logix5000 Controllers Common Procedures Programming Manual, publication
1756-PM001
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.
Using Logix5000 Controllers as Masters or Slaves on Modbus Application Solution,
publication CIG-AP129
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
Describes how to configure and operate the ControlLogix 1756 DH+ / remote I/O module.
ControlLogix DH-485 Communication Module User Manual, publication 1756-UM532
Describes how to configure and operate the ControlLogix 1756 DH-485 module.
ControlLogix Remote I/O Communication Module User Manual, publication 1756-UM534
Describes how to configure and troubleshoot the ControlLogix remote I/O (RIO)
communication module.
Process Remote I/O Communication Interface Module User Manual, publication
1757-UM007
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
Describes how to install, configure, and operate the 1788-CN2FF linking device.
RSFieldbus User Manual, publication RSFBUS-UM001
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 1757FFLD linking device.
ControlLogix HART Analog I/O Modules User Manual, publication 1756-UM533
Describes how to install, configure, and operate ControlLogix HART analog I/O modules.
Encompass™ website available at http://www.rockwellautomation.com/encompass
Assists in locating third-party products that best solve application challenges.
ProSoft Technology website, available at http://www.prosoft-technology.com
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-UM001M-EN-P - February 2012
107
Chapter 5
Communication Networks
Notes:
108
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Chapter
6
Serial Communication (1756-L6x controllers
only)
1756-L6x Controller Serial
Port
Topic
Page
1756-L6x Controller Serial Port
109
Communication with Serial Devices
110
DF1 Master Protocol
110
DF1 Point to Point Protocol
111
DF1 Radio Modem Protocol
111
DF1 Slave Protocol
114
DH-485 Protocol
115
ASCII Protocol
117
Configure the 1756-L6x Controller for Serial Communication
117
Broadcast Messages Over a Serial Port
119
Modbus Support
122
Additional Resources
122
The 1756-L6x 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 13 - ControlLogix DF1 Device Communication Example
DH+ Connection
EtherNet/IP
Network
RS-232 Connection
RS-232 Connection
RS-232 Connection
Modem
Modem
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Modem
109
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.prosofttechnology.com.
When configuring the controller for serial communication, you first specify a
Serial Port mode (System or User), then a protocol.
Communication with Serial
Devices
Figure 14 - 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
Protocol
Is used to
See page
System
DF1 Master
Control polling and message transmission between the master and slave nodes.
110
DF1 Point to Point
• Communicate between the controller and one other DF1-protocol-compatible device.
• Program the controller via the serial port.
111
DF1 Radio Modem
• Communication with SLC 500 and MicroLogix™ 1500 controllers.
• This protocol supports master/slave and store/forward configurations.
111
DF1 Slave
Setup the controller as a slave station in a master/slave serial communication network.
114
DH-485
Communication with other DH-485 devices via a multi-master and token-passing network that enables
programming and peer-to-peer messaging.
115
ASCII
• Communicate with ASCII devices.
• Use ASCII instructions to read and write data from and to an ASCII device.
117
User
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.
110
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Serial Communication (1756-L6x controllers only)
DF1 Point to Point Protocol
Chapter 6
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
DF1 Radio Modem Protocol
Parameter
Value
Baud Rate
19,200
Data Bits
8
Parity
None
Stop Bits
1
Control Line
No Handshake
RTS send Delay
0
RTS Off Delay
0
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 fullduplex protocol and DF1 half-duplex protocol, and therefore is not compatible
with either of these protocols.
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.
IMPORTANT
Figure 15 - DF1 Radio Modem Network Example
EtherNet/IP Network
RS-232
Modem
Power
OUT
L1
L2/N
Modem
Modem
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Modem
111
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 fullduplex 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.
112
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
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-UM001M-EN-P - February 2012
113
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
Description
Station Address
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.
Error Detection
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.
Enable Store and Forward
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.
114
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Serial Communication (1756-L6x controllers only)
DH-485 Protocol
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 software. However, excessive traffic over a DH485 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-UM001M-EN-P - February 2012
115
Chapter 6
Serial Communication (1756-L6x controllers only)
Figure 16 - DH-485 Network Communication Overview
Computer with RSLogix&reg; 500
and RSLogix 5000 Software
ControlLogix Controller
ControlLogix Controller
1756-ENBT Module
1756-DH485 Module
AIC+ Link Coupler
AIC+ Link Coupler
EXTERNAL
TE
EXTERNAL
TE
DH-485 Network
AIC+ Link Coupler
AIC Link Coupler
T
TERM
A
AIC Link Coupler
AIC Link Coupler
MicroLogix
PanelView Display
SLC™ 5/03 Controller
SLC 5/03 Controller
IMPORTANT
116
A DH-485 network consists of multiple cable segments. Limit the total length
of all the segments to 1219 m (4000 ft).
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Serial Communication (1756-L6x controllers only)
ASCII Protocol
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.
Configure the 1756-L6x
Controller for Serial
Communication
Complete these steps to configure your 1756-L6x controller for serial
communication after you have created a controller project in RSLogix 5000
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
Choose this mode
DF1 Master
System
DF1 Point to Point
DF1 Radio Modem
DF1 Slave
DH-485
ASCII
User
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
117
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.
118
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
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-UM001M-EN-P - February 2012
119
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 120
• Program the Message Instruction, page 121
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.
120
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Serial Communication (1756-L6x controllers only)
Chapter 6
Use this table as a reference when specifying settings for the protocols
listed.
Field
DF-1 Master Protocol
DF-1 Slave Protocol
DF-1 Radio Modem Protocol
Station Address
Controller station address number
Controller station address number
Controller station address number
Transmit Retries
3
3
N/A
ACK Timeout
50
N/A
N/A
Slave Poll Timeout
N/A
3000
N/A
Reply Message Wait
5
N/A
N/A
Polling Mode
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
N/A
EOT Suppression
N/A
Disable
N/A
Error Detection
BCC
BCC
BCC
Duplicate Detection
Enabled
Enabled
N/A
Enable Store and Forward
N/A
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 a MSG to display the Message Configuration
dialog box.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
121
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
Description
ProSoft Technology website, available at http://www.prosoft-technology.com
Provides information about multi-vendor modules that can be used to establish a serial
communication network with a ControlLogix system.
Logix5000 Controllers General Instruction Reference Manual, publication 1756-RM003
Explains ASCII instructions and programming.
Using Logix5000 Controllers as Masters or Slaves on Modbus Application Solution,
publication CIG-AP129
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
Allen-Bradley distributor or Rockwell Automation sales representative.
122
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Chapter
7
Manage Controller Communication
(connections)
Topic
Page
Connection Overview
123
Produce and Consume (interlock) Data
123
Send and Receive Messages
125
Calculate Connection Use
127
Additional Resources
130
Connection Overview
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 software
• Controller access by RSLinx Classic or RSLinx Enterprise software for
HMI or other applications
Produce and Consume
(interlock) Data
ControlLogix controllers let you produce (broadcast) and consume (receive)
system-shared tags.
Figure 17 - Illustration of Produced and Consumed Tags
Controller_1
Controller_2
Produced Tag
Consumed Tag
Controller_3
Consumed Tag
Controller_4
Consumed Tag
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
123
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.
If a consumed-tag connection fails, all of the other tags being consumed
from that remote controller stop receiving new data.
IMPORTANT
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
Uses This Many Connections
Of This Module
Produced tag
number_of_configuredconsumers + 1
Controller
Consumed tag
1
Produced or consumed tag
1
EXAMPLE
124
Communication
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).
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Manage Controller Communication (connections)
Chapter 7
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
Cat. No.
Available Connections
Controller
1756-L7x
500
1756-L6x
250
•
•
•
•
1756-EN2F
1756-EN2T
1756-EN2TXT
1756-EN2TR
256
• 1756-ENBT
• 1756-EWEB
128
• 1756-CN2
• 1756-CN2R
• 1756-CN2RXT
128
• 1756-CNB
• 1756-CNBR
64
EtherNet/IP
ControlNet
For more information about produced/consumed tags, see the Logix5000
Controllers Produced and Consumed Tags Programming Manual, publication
1756-PM011.
Send and Receive Messages
Messages transfer data to other devices, such as other controllers or operator
interfaces. The MSG instruction is a ladder logic output instruction that
asynchronously reads or writes a block of data to or from another module over
the backplane or a network. The size of the instruction depends on the data types
and message command programmed by the user.
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-UM001M-EN-P - February 2012
125
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
Communication
Method
Connected Message
Message Can Be
Cached
CIP data table read or write
N/A
Configurable
Yes
PLC-2&reg;, PLC-3&reg;, PLC-5&reg;, or SLC
(all types)
CIP
No
No
CIP with Source ID
No
No
DH+
Yes
Yes
CIP generic
N/A
Optional (1)
Yes(2)
Block-transfer read or write
N/A
Yes
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.
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
126
Cached connections transfer data faster than uncached connections.The
controller only supports 32 cached messages.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Manage Controller Communication (connections)
Chapter 7
The total connection requirements of a ControlLogix system include both local
and remote connections.
Calculate Connection Use
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
Device Quantity
Connections per
Device
Local I/O module (always a direct connection)
1
1756-M16SE, 1756-M08SE, or 1756-M02AE servo module
3
• 1756-CN2, 1756-CN2R, 1756-CN2RXT ControlNet communication module
• 1756-CNB, 1756-CNBR ControlNet communication module
0
• 1756-EN2F, 1756-EN2T, 1756-EN2TXT, or 1756-EN2TR EtherNet/IP communication module
• 1756-ENBT EtherNet/IP communication module
0
1756-EWEB EtherNet/IP web server module
0
1756-DNB DeviceNet communication module
2
1756-RIO remote I/O communication module (Connection count depends on module configuration
and could be as many as 10 per module.)
1
1756-DHRIO DH+/universal remote I/O communication module
Each adapter associated with the module
1
1
1756-DH485 DH-485 communication module
1
Total Connections
Total
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
127
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
Device Quantity
Connections per
Device
Remote ControlNet communication module
I/O configured as direct connection (none)
I/O configured as rack-optimized connection
0 or
1
Remote I/O module over a ControlNet network (direct connection)
1
Remote EtherNet/IP communication module
I/O configured as direct connection (none)
I/O configured as rack-optimized connection
0 or
1
Remote I/O module over a EtherNet/IP network (direct connection)
1
Remote device over a DeviceNet network
(accounted for in rack-optimized connection for local 1756-DNB)
0
DeviceNet module in a remote chassis
2
Other remote communication adapter
1
Produced tag
Each consumer
1
1
Consumed tag
1
Message (depending on type)
1
Block-transfer message
1
Total
128
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Total Connections
Manage Controller Communication (connections)
Chapter 7
Connections Example
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 software
RediSTATION™
Operator Interface
1769-ADN Adapter with Compact I/O™ Modules
Series 9000™
Photoeye
DeviceNet Network
ControlLogix Controller with
1756-ENBT and 1756-DNB
Modules
1769-L35E CompactLogix
with 1769-SDN Module
EtherNet/IP Network
FlexLogix Controller with 1788-DNBO Daughtercard
Workstation
The ControlLogix controller in this example uses these connections.
Table 38 - Connections Example Calculation
Connection Type
Device Quantity
Connections per
Device
Total Connections
Controller to local I/O modules
4
1
4
Controller to 1756-ENBT module
1
0
0
Controller to 1756-DNB module
1
2
2
Controller to RSLogix 5000 software
1
1
1
Message to CompactLogix controller
2
1
2
Produced tag
Consumed by FlexLogix controller
1
1
1
1
1
1
Total 11
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
129
Chapter 7
Manage Controller Communication (connections)
These documents contain additional information concerning related Rockwell
Automation products.
Additional Resources
Resource
Description
Logix5000 Controllers Produced and Consumed Tags Programming Manual, publication
1756-PM011
Explains produced and consumed tags and information related to using them in your
program.
Logix5000 Controllers Messages, publication 1756-PM012
Explains details about caching, managing multiple messages, and sending messages to
multiple controllers.
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 General Instructions Reference Manual, publication 1756-RM003
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.
Logix5000 Controllers Common Procedures Programming Manual, publication
1756-PM001
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.
130
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Chapter
8
I/O Modules
Selecting ControlLogix I/O
Modules
Topic
Page
Selecting ControlLogix I/O Modules
131
Local I/O Modules
132
Remote I/O Modules
134
Distributed I/O
138
Reconfigure an I/O Module
141
Reconfigure an I/O Module
141
Determine When Data is Updated
149
Additional Resources
150
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-UM001M-EN-P - February 2012
131
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- Chassis and Slots
Chassis
Slots
1756-A4
4
1756-A4LXT
1756-A5XT
5
1756-A7
7
1756-A7LXT
1756-A7XT
1756-A10
10
1756-A13
13
1756-A17
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.
132
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
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
ControlLogix Configurable Flowmeter Module User
Manual, publication 1756-UM010
Digital I/O
ControlLogix Digital I/O Modules User Manual, publication
1756-UM058
HART analog I/O
ControlLogix HART Analog I/O Modules User Manual,
publication 1756-UM533
High speed analog I/O
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-UM001M-EN-P - February 2012
133
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 91).
Figure 18 - ControlLogix Controller and Remote I/O Example
ControlLogix Controller Chassis
ControlLogix Remote I/O
ControlNet
134
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
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-UM001M-EN-P - February 2012
135
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.
8. Specify the Module Properties according to your module and application.
136
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
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
ControlLogix Configurable Flowmeter Module User
Manual, publication 1756-UM010
Digital I/O
ControlLogix Digital I/O Modules User Manual, publication
1756-UM058
HART analog I/O
ControlLogix HART Analog I/O Modules User Manual,
publication 1756-UM533
High speed analog I/O
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. Complete steps 1…9 until your remote I/O network and I/O modules are
configured in RSLogix 5000 software.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
137
Chapter 8
I/O Modules
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
• 1797 FLEX Ex™ I/O modules
• 1738 ArmorPOINT&reg; I/O modules
• 1732 ArmorBlock&reg; I/O modules
• 1753 GuardPLC™ Safety I/O modules
• 1790 CompactBlock™ LDX I/O modules
• 1791 CompactBlock Guard Safety I/O modules
• 1791 CompactBlock I/O modules
• 1732DS ArmorBlock Guard Safety I/O modules
• 1792 ArmorBlock&reg; MaXum™ I/O modules
Distributed I/O
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 19 - 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
COMM
A
STATUS
REDUNDANT MEDIA
ADAPTER
1794-ACNR15
B
ControlNet
138
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
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-UM001M-EN-P - February 2012
139
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.
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. Complete steps 1…9 until your remote I/O network and distributed I/O
modules are configured in RSLogix 5000 software.
140
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
I/O Modules
Reconfigure an I/O Module
Chapter 8
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, consider the
following:
• Input modules continue to send input data to the controller
• Output modules 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-UM001M-EN-P - February 2012
141
Chapter 8
I/O Modules
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.
EXAMPLE
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 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.
142
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
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 19.
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-UM001M-EN-P - February 2012
143
Chapter 8
I/O Modules
PowerFlex Drives that Can be Added While Online
144
• PowerFlex&reg; 4 Class Multi-E
• PowerFlex&reg; 7000-Q
• PowerFlex 700S-200V-Q
• PowerFlex 400-E
• PowerFlex&reg; 700-200V-C
• PowerFlex 700S-400V-C
• PowerFlex 400P-E
• PowerFlex 700-200V-E
• PowerFlex 700S-400V-E
• PowerFlex&reg; 40-E
• PowerFlex 700-200V-Q
• PowerFlex 700S-400V-Q
• PowerFlex&reg; 40P-E
• PowerFlex 700-400V-C
• PowerFlex 700S-600V-C
• PowerFlex 4-E
• PowerFlex 700-400V-E
• PowerFlex 700S-600V-E
• PowerFlex 4M-E
• PowerFlex 700-400V-Q
• PowerFlex 700S-600V-Q
• PowerFlex 70&reg; EC-C
• PowerFlex 700-600V-C
• PowerFlex 70-C
• PowerFlex 70 EC-C
• PowerFlex 700-600V-E
• PowerFlex 70-E
• PowerFlex 70 EC-E
• PowerFlex 700-600V-Q
• PowerFlex 70-E
• PowerFlex 70 EC-E
• PowerFlex 700AFE-C
• PowerFlex 70-Q
• PowerFlex 70 EC-Q
• PowerFlex 700AFE-E
• PowerFlex 70-Q
• PowerFlex 70 EC-Q
• PowerFlex 700AFE-Q
• PowerFlex&reg; 753-CNETC
• PowerFlex 700 AC-C
• PowerFlex&reg; 700H-C
• PowerFlex 753-NET-C
• PowerFlex 700 AC-E
• PowerFlex 700H-E
• PowerFlex 753-NET-E
• PowerFlex 700 AC-Q
• PowerFlex 700H-Q
• PowerFlex 753-NET-Q
• PowerFlex 700 Vector-200V-C
• PowerFlex 700S 2-200V
• PowerFlex&reg; 755-CNETC
• PowerFlex 700 Vector-200V-E
• PowerFlex 700S 2-400V
• PowerFlex 755-EENET
• PowerFlex 700 Vector-200V-Q
• PowerFlex 700S 2-600V
• PowerFlex 755-NET-C
• PowerFlex 700 Vector-400V-C
• PowerFlex 700S 2P-200V-C
• PowerFlex 755-NET-E
• PowerFlex 700 Vector-400V-E
• PowerFlex 700S 2P-200V-E
• PowerFlex 755-NET-Q
• PowerFlex 700 Vector-400V-Q
• PowerFlex 700S 2P-200V-Q
• PowerFlex DC-200V-C
• PowerFlex 700 Vector-600V-C
• PowerFlex 700S 2P-400V-C
• PowerFlex DC-200V-E
• PowerFlex 700 Vector-600V-E
• PowerFlex 700S 2P-400V-E
• PowerFlex DC-200V-Q
• PowerFlex 700 Vector-600V-Q
• PowerFlex 700S 2P-400V-Q
• PowerFlex DC-400V-C
• PowerFlex 7000 2-C
• PowerFlex 700S 2P-600V-C
• PowerFlex DC-400V-E
• PowerFlex 7000 2-E
• PowerFlex 700S 2P-600V-E
• PowerFlex DC-400V-Q
• PowerFlex 7000 2-Q
• PowerFlex 700S 2P-600V-Q
• PowerFlex DC-600V-C
• PowerFlex 7000-C
• PowerFlex 700S-200V-C
• PowerFlex DC-600V-E
• PowerFlex 7000-E
• PowerFlex 700S-200V-E
• PowerFlex DC-600V-Q
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
I/O Modules
Chapter 8
Other Devices that Can be Added While Online
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
1305-BAXXA drives
1336E-IMPACT™Drive-EN1 drive
1336F-PLUS™IIDrive-EN1drive
1336R-REGENBrake-EN1 brake
1336S-PLUSDriveLG-EN1 drive
1336S-PLUSDriveSM-EN1 drive
1336T-FORCE™DriveCNA-EN1 drive
1336T-FORCEDrivePLC-EN1 drive
1336T-FORCEDriveStd-EN1 drive
1397DigitalDCDrive-EN1 drive
150 SMC™ FLEX motor controller
150-SMC™DialogPlus-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-UM001M-EN-P - February 2012
145
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 of 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 1756CNBR 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.
146
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
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)
No. of Direct
Analog I/O
Connections
Added Online
RPI = 2 ms
RPI = 4 ms
RPI = 10 ms
RPI = 20 ms
RPI = 50 ms
RPI = 100 ms
CPU %(2)
Avg.
API(3)
CPU %(2)
Avg.
API(3)
CPU %(2)
Avg.
API(3)
CPU %(2)
Avg.
API(3)
CPU %(2)
Avg.
API(3)
CPU %(2)
Avg.
API(3)
0
1.50%
N/A
1.50%
N/A
1.50%
N/A
1.50%
N/A
1.50%
N/A
1.50%
N/A
1
4.80%
2.0
3.70%
4.0
2.50%
10.0
2.30%
20.0
1.90%
50.0
1.70%
100.0
2
7.00%
2.0
5.00%
4.0
3.30%
10.0
2.70%
20.0
2.10%
50.0
1.90%
100.0
3
9.00%
2.0
6.10%
4.0
3.80%
10.0
3.00%
20.0
2.20%
50.0
2.00%
100.0
4
11.20%
2.2
7.40%
4.0
4.40%
10.0
3.40%
20.0
2.40%
50.0
2.10%
100.0
5
11.50%
3.3
8.70%
4.0
5.00%
10.0
3.70%
20.0
2.60%
50.0
2.20%
100.0
6
12.80%
3.3
9.70%
4.0
5.50%
10.0
4.00%
20.0
2.70%
50.0
2.30%
100.0
7
13.80%
3.4
10.80%
4.0
5.90%
10.0
4.30%
20.0
2.90%
50.0
2.30%
100.0
8
15.10%
3.4
11.90%
4.0
6.40%
10.0
4.50%
20.0
3.00%
50.0
2.50%
100.0
9
15.00%
3.3
13.20%
4.0
7.00%
10.0
4.80%
20.0
3.20%
50.0
2.60%
100.0
10
15.60%
3.6
13.20%
4.0
7.50%
10.0
5.20%
20.0
3.40%
50.0
2.70%
100.0
11
16.40%
3.8
13.50%
4.0
8.20%
10.0
5.50%
20.0
3.50%
50.0
2.70%
100.0
12
17.00%
3.8
14.00%
4.0
8.80%
10.0
5.80%
20.0
3.70%
50.0
2.80%
100.0
13
17.80%
3.7
14.60%
4.0
9.30%
10.0
6.10%
20.0
3.80%
50.0
2.90%
100.0
14
18.50%
3.7
15.20%
4.0
9.90%
10.0
6.40%
20.0
4.00%
50.0
2.90%
100.0
15
19.40%
3.9
15.80%
4.0
10.50%
10.0
6.70%
20.0
4.10%
50.0
3.00%
100.0
(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).
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-UM001M-EN-P - February 2012
147
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.
148
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
I/O Modules
Chapter 8
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.
Determine When Data is
Updated
Figure 20 - Data Update Flowchart
Output
Input or Output Data?
Input
Analog or Digital?
Digital
Analog or Digital?
Analog
Digital
Remote or Local?
Analog
Remote
COS for Any Point on the Module?
Local
No
No
RTS ≤ RPI?
Yes
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.
Data is sent to the backplane at the RPI.
• 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.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Data is sent to the backplane at the RPI and at
the end of every task.
149
Chapter 8
I/O Modules
Additional Resources
These documents contain additional information concerning related Rockwell
Automation products.
Resource
Description
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.
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
Describes how to install, configure, and troubleshoot ControlLogix HART I/O modules.
ControlLogix High Speed Analog I/O Module User Manual, publication 1756-UM005
Describes how to install, configure, and troubleshoot ControlLogix high-speed analog I/O
modules.
ControlLogix High Speed Counter Module User Manual, publication 1756-UM007
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.
Logix5000 Controllers Common Procedures Programming Manual, publication 1756PM001
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.
Runtime/On-line Addition of ControlLogix (1756) I/O over ControlNet and EtherNet/IP
White Paper, publication LOGIX-WP006
Explains adding to the I/O Configuration while online with the controller.
EtherNet/IP Communication Modules in Logix5000 Control Systems User Manual,
publication ENET-UM001
Describes how to configure and operate EtherNet/IP modules in a Logix5000 control
system.
ControlNet Modules in Logix5000 Control Systems User Manual, publication CNET-UM001 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.
150
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Chapter
9
Develop Motion Applications
Topic
Page
Motion Control Options
151
Motion Overview
151
Obtain Axis Information
152
Program Motion Control
152
Additional Resources
155
Motion Control Options
ControlLogix controllers support digital and analog interfaces:
• Digital drive interfaces include EtherNet/IP connected drives and
SERCOS interface connected drives.
• Analog drives support &plusmn;10 voltage analog output and can interface with a
variety of feedback device types including quadrature encoder, SSI, and
LVDT feedback.
Motion Overview
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
Requirements
CIP Sync
• EtherNet/IP communication module
• Digital drive with an EtherNet/IP connection
SERCOS interface
Select a SERCOS interface module:
• 1756-M03SE
• 1756-M08SE
• 1756-M16SE
Analog interface
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-UM001M-EN-P - February 2012
151
Chapter 9
Develop Motion Applications
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.
Obtain Axis Information
Figure 21 - Obtain Axis Information
Axis Properties Dialog Box
SSV (or GSV) Instruction
Axis Tag
Quick View Pane
Program Motion Control
152
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)
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Develop Motion Applications
Chapter 9
Figure 22 - 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-UM001M-EN-P - February 2012
153
Chapter 9
Develop Motion Applications
If Jog_Pushbutton = off then
the MAS instruction stops the axis at 100 units/.second2.
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.
154
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Develop Motion Applications
Chapter 9
These documents contain additional information concerning related Rockwell
Automation products.
Additional Resources
Resource
Description
SERCOS Motion Configuration and Startup User Manual, publication MOTION-UM001
Details how to configure a SERCOS motion application system.
Motion Coordinated Systems User Manual, publication MOTION-UM002
Details how to create and configure a coordinated motion application system.
CIP Motion Configuration and Startup User Manual, publication MOTION-UM003
Details how to configure a Integrated Motion on the EtherNet/IP network.
Logix5000 Controllers Motion Instructions Reference Manual, publication
MOTION-RM002
Provides programmers with details about the motion instructions that are available for a
Logix5000 controller.
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.
Motion Analyzer Selection Guide, publication PST-SG003
Provides motion selection and configuration tools via CD-ROM.
Logix5000 Controllers General Instructions Reference Manual, publication 1756-RM003
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.
Logix5000 Controllers Common Procedures Programming Manual, publication
1756-PM001
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-UM001M-EN-P - February 2012
155
Chapter 9
Develop Motion Applications
Notes:
156
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Chapter
10
Develop Applications
Elements of a Control
Application
Topic
Page
Elements of a Control Application
157
Tasks
158
Programs
161
Routines
164
Tags
165
Programming Languages
166
Add-On Instructions
167
Monitoring Controller Status
168
Monitoring I/O Connections
169
System Overhead Time Slice
171
Additional Resources
174
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-UM001M-EN-P - February 2012
157
Chapter 10
Develop Applications
Figure 23 - Elements of a Control Program
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
Tasks
158
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.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Develop Applications
Chapter 10
Figure 24 - 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
Program
(local) Tags
Fault Routine
Other
Routines
Controller (global)
Tags
I/O Data
System-shared Data
Figure 25 - Tasks in RSLogix 5000 Software
Main Task
(Continuous)
Task 2
(Periodic)
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
159
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 26 - 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
Description
Continuous
All of the time
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.
Periodic
• At a set interval, such as every
100 ms
• Multiple times within the scan
of your other logic
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...2,000,000.00 ms. 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.
Event
Immediately when an event occurs
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.
160
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
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 27 - 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-UM001M-EN-P - February 2012
161
Chapter 10
Develop Applications
Figure 28 - 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 29 - Programs in RSLogix 5000 Software
162
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
System-shared Data
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 30 - Scheduling an Unscheduled Program
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
163
Chapter 10
Develop Applications
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.
Routines
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 31 - 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
Figure 32 - Routines in RSLogix 5000 Software
Routine
Routine
164
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
System-shared Data
Develop Applications
Chapter 10
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.
Tags
This example shows data tags created within the scope of the Main Program of
the controller.
Figure 33 - Tags Example
Controller Organizer - Main Program Tags
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-UM001M-EN-P - February 2012
165
Chapter 10
Develop Applications
Programming Languages
The ControlLogix controller supports these programming languages, both
online and offline.
Table 42 - ControlLogix Controller Programming Languages
Language
Is best-used in programs with
Relay ladder
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.
166
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Develop Applications
Chapter 10
With version 16, or later, of RSLogix 5000 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.
Add-On Instructions
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
Description
Save Time
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.
Use Standard Editors
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.
Export Add-On Instructions
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.
Use Context Views
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.
Create Custom Help
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.
Apply Source Protection
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-UM001M-EN-P - February 2012
167
Chapter 10
Develop Applications
Figure 34 - Add-On Instructions in RSLogix 5000 Software
Controller Organizer
Instruction Toolbar
For more information about using Add-On Instructions, see the AddOn Instructions Programming Manual, publication 1756-PM010.
Monitoring Controller Status
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 35 - GSV and SSV Instructions for Monitoring
When you add a GSV/SSV instruction to the program, the 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.
168
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Develop Applications
Chapter 10
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-L7x 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-UM001M-EN-P - February 2012
169
Chapter 10
Develop Applications
Figure 36 - 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.
170
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Develop Applications
Chapter 10
Figure 37 - I/O Connection Fault Causes Major Fault
I/O Module Properties
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-UM001M-EN-P - February 2012
171
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
The continuous task runs
Service communication occurs for up to
10%
9 ms
1 ms
20%
4 ms
1 ms
25%
3 ms
1 ms
33%
2 ms
1 ms
50%
1 ms
1 ms
66%
1 ms
2 ms
75%
1 ms
3 ms
80%
1 ms
4 ms
90%
1 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 software, right-click the
controller and choose Properties.
The Controller Properties dialog box appears.
2. Click the Advanced tab.
3. Enter a numeric value in the System Overhead Time Slice box.
172
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Develop Applications
Chapter 10
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 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 &gt; Open &gt; Projects &gt; Samples).
Figure 38 - Opening Sample Projects in RSLogix 5000 Software
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
173
Chapter 10
Develop Applications
Additional Resources
These documents contain additional information concerning related Rockwell
Automation products.
Resource
Description
Logix5000 Controllers and I/O Tag Data Programming Manual, publication 1756-PM004
Explains procedures for using and organizing I/O data tags.
Logix5000 Controllers Common Procedures Programming Manual, publication
1756-PM001
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.
Add-On Instructions Programming Manual, publication 1756-PM010
Explains Add-On Instructions and how to use them.
Logix5000 Controllers General Instructions Reference Manual, publication 1756-RM003
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.
174
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Chapter
11
Using the PhaseManager Tool
PhaseManager Overview
Topic
Page
PhaseManager Overview
175
Minimum System Requirements
177
State Model Overview
178
PhaseManager Tool versus Other State Models
180
Equipment Phase Instructions
181
Additional Resources
181
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
Description
Equipment phase
• 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.
State model
• 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.
State machine
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
PHASE tag
When you add an equipment phase, RSLogix 5000 software makes a tag for the equipment phase. The tag uses the PHASE data type.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
175
Chapter 11
Using the PhaseManager Tool
Figure 39 - PhaseManager Overview
A PHASE tag gives you the status of an equipment phase.
Controller
Controller Tags
Tasks
MainTask
An equipment phase directs one activity of your equipment.
A state model divides the activity into a series of states.
Add Water Phase
Mix Phase
Running State Routine
How to add water
Drain Phase
Space Parts Phase
MainProgram
Equipment phase instructions control the transitions between states and handle faults.
PSC
POVR
PCLF
PRNP
PATT
PCMD
PFL
PXRQ
PPD
PDET
My Equipment Program
Other code controls the specific actions of your equipment.
Water Feed
176
Conveyor
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Enable Axes
Using the PhaseManager Tool
Minimum System
Requirements
Chapter 11
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 software, or RSLogix 5000 with PhaseManager software
(catalog number 9324-RLDPMENE).
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
177
Chapter 11
Using the PhaseManager Tool
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.
State Model Overview
Table 45 - States in PhaseManager Software
State
Description
Acting
Does something or several things for a certain time or until certain conditions are met. An acting state
runs once or repeatedly.
Waiting
Shows that certain conditions are met and the equipment is waiting for the signal to go to the next
state.
Figure 40 - PhaseManager State Transitions
Start
Idle
Your equipment can go from any state in the box
to the stopping or aborting state.
Hold
Running
Holding
Held
Hold
Restart
Resetting
Acting
Restarting
Stop
Abort
Acting states represent the things
your equipment does at a given
time.
Abort
Reset
Complete
Stopping
Aborting
Waiting
Reset
Stopped
Aborted
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
178
State
Question to be asked
Resetting
How does the equipment get ready to run?
Running
What does the equipment do to make product?
Holding
How does the equipment temporarily stop making product without making scrap?
Restarting
How does the equipment resume production after holding?
Stopping
What happens during a normal shutdown?
Aborting
How does the equipment shut down if a fault or failure occurs?
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Using the PhaseManager Tool
Chapter 11
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 41 - PhaseManager Transition Commands
= Transition
Command
Done — No command. Use PSC instruction instead.
Start
Idle
Your equipment can go from any state in the box
when it receives a stop or abort commend.
Hold
Running
Holding
Held
Hold
Restart
Resetting
Restarting
Stop
Abort
Abort
Reset
Complete
Reset
Stopping
Aborting
Stopped
Aborted
Table 47 - PhaseManager Transitions
Type of Transition
Description
Command
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
Stop
Restart
Start
Hold
Abort
Done
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.
Fault
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.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
179
Chapter 11
Using the PhaseManager Tool
Manually Change States
With RSLogix 5000 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, click Owners to
release your ownership.
PhaseManager Tool versus
Other State Models
180
This table compares PhaseManager state models to other state models.
Table 48 - PhaseManager Tool and Other State Models
PhaseManager Tool
S88
PackML
Resetting…Idle
Idle
Starting…Ready
Running…Complete
Running…Complete
Producing
Subroutines or breakpoints
Pausing…Paused
Standby
Holding…Held
Holding…Held
Holding…Held
Restarting
Restarting
None
Stopping…Stopped
Stopping…Stopped
Stopping…Stopped
Aborting…Aborted
Aborting…Aborted
Aborting…Aborted
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Using the PhaseManager Tool
Chapter 11
The controller supports several equipment-phase relay ladder and structured text
instructions.
Equipment Phase
Instructions
Table 49 - Instructions for Use with PhaseManager Tool
Instruction
Instruction Function
PSC
Signal a phase that the state routine is complete and to proceed to the next state.
PCMD
Change the state or substate of a phase.
PFL
Signal a failure for a phase.
PCLF
Clear the failure code of a phase.
PXRQ
Initiate communication with RSBizWare™ Batch software.
PRNP
Clear the NewInputParameters bit of a phase.
PPD
Set up breakpoints within the logic of a phase.
PATT
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.
PDET
Relinquish ownership of a phase.
POVR
Override a command.
For more information about instructions for use with equipment phases, see the
PhaseManager User Manual, publication LOGIX-UM001.
These documents contain additional information concerning related Rockwell
Automation products.
Additional Resources
Resource
Description
PhaseManager User Manual, publication LOGIX-UM001
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.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
181
Chapter 11
Using the PhaseManager Tool
Notes:
182
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Chapter
12
Redundant Systems
ControlLogix Redundancy
Overview
Topic
Page
ControlLogix Redundancy Overview
183
System Requirements
185
System Considerations
186
Build a Redundant System
188
ControlNet Considerations in Redundant Systems
188
EtherNet/IP Considerations in Redundant Systems
189
Redundancy and Scan Time
190
Additional Resources
191
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-UM001M-EN-P - February 2012
183
Chapter 12
Redundant Systems
Figure 42 - ControlLogix Enhanced Redundancy System
Workstation
HMI
Ethernet
Switch
Primary
Secondary
EtherNet/IP
DC OUTPUT
Diagnostic
Analog Input
ST
AT
ST
AT
Analog Output
ST
AT
ST
AT
Diagnostic
Diagnostic
Analog Output
ST
AT
ST
AT
Digital Ouput
ControlNet Scanner
I/O Connected via ControlNet
Diagnostic
Digital Input
ST
AT
ST
AT
Analog Input
DC INPUT
ControlNet
1756-CN2R
1756-RM
1756-L6x
1756-CN2R
1756-EN2T
1756-RM
ControlNet
PRI COM OK
PRI COM OK
1756-L6x
EtherNet/IP
Redundancy Module
Logix5563
ControlNet
1756-EN2T
Redundancy Module
Relay Module
ControlNet
ControlNet Scanner
Logix5563
Relay Ouput
Redundant Chassis
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.
184
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Redundant Systems
System Requirements
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
Notes
2
ControlLogix chassis
Both chassis must be the same size.
2
ControlLogix power supply
Must be the same in each chassis.
2
ControlLogix controller
• 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.
2
ControlLogix ControlNet
communication module
• 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.
2
ControlLogix EtherNet/IP
communication modules
• 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.
2
Redundancy 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.
1
Redundancy module cable
(fiber-optic)
• Use the 1756-RMCx cable.
• Standard lengths are available.
2
Additional ControlNet nodes
• 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-UM001M-EN-P - February 2012
185
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
Consideration
ControlLogix controller
•
•
•
•
Communication modules
• 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.
I/O modules
• 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.
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 software, but it must match your Enhanced Redundancy System revision
level.
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.
186
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
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
Enhanced
System(1)


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
Standard
System



Compatible with the double-slot 1757-SRM redundancy modules
Support for all 1756-L6x and 1756-L7x ControlLogix controllers

Use of ControlLogix- 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

(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-UM001M-EN-P - February 2012
187
Chapter 12
Redundant Systems
To build a typical redundant system, perform this procedure.
Build a Redundant System
1. Install a ControlLogix chassis and power supply.
2. To the primary chassis, add 1756-L6x 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.
188
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Redundant Systems
EtherNet/IP Considerations
in Redundant Systems
Chapter 12
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 intercontroller 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-UM001M-EN-P - February 2012
189
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-todate 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.
190
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Redundant Systems
Additional Resources
Chapter 12
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
Guides the design, development, and implementation of an enhanced ControlLogix
redundancy system.
ControlLogix Enhanced Redundancy System, Revision 19.50 Release Notes, publication
1756-RN684.
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
Describes the enhancements, corrected anomalies, and known anomalies specific to the
current firmware revision for an enhanced redundancy system, revision 16.81 or later.
Integrated Architecture™ and CIP Sync Configuration Application Technique, publication
IA-AT003
Provides detailed and comprehensive information about how to apply CIP Sync
technology to synchronize clocks in a Logix control system.
Redundant I/O System User Manual, publication 1715-UM001
Guides the design, development, and implementation of a Redundant I/O System used in
conjunction with a ControlLogix redundancy 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-UM001M-EN-P - February 2012
191
Chapter 12
Redundant Systems
Notes:
192
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Chapter
13
SIL 2 Certification
Introduction to SIL
Topic
Page
Introduction to SIL
193
Programming and Debugging Tool (PADT)
193
Typical SIL2 Configurations
194
Additional Resources
198
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&Uuml;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-UM001M-EN-P - February 2012
193
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
The safety loop includes
Fail-safe Configuration, page 195
• Nonredundant controller
• Nonredundant communication modules
• Nonredundant remote I/O
High-availability Configuration, page 196
• Redundant controllers
• Redundant communication modules
• Nonredundant remote I/O
Fault-tolerant Configuration, page 197
•
•
•
•
IMPORTANT
Redundant controllers
Redundant communication modules
Redundant remote I/O
I/O termination boards
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.
194
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
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 deenergized.
Figure 43 - Fail-safe ControlLogix Configuration
Overall Safety Loop
SIL2-certified ControlLogix Safety Loop
Controller Chassis
Sensor
Remote I/O Chassis
EN
BT
CN
BR
I/O
CN
BR
Actuator
ControlNet
I/O
EN
BT
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 SIL2certified ControlNet network.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
195
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 44 - Typical SIL Loop with Controller Chassis Redundancy
HMI
For Diagnostics and Visualization (read-only access to controllers in the safety
loop).
Software
For SIL applications, a programming
terminal is not normally connected.
Plant-wide Ethernet/Serial
Overall Safety Loop
SIL2-certified ControlLogix components’ portion of the overall safety loop.
Primary Chassis
Remote I/O Chassis
Sensor
EN CN CN
2T 2 2
R
M
I/O
CN
2
Actuator
ControlNet
Secondary Chassis
EN CN CN
2T 2 2
To other safety
related
ControlLogix and
remote
I/O chassis.
To nonsafety related systems outside the ControlLogix portion of the SIL2certified loop.
ControlNet
IMPORTANT
196
R
M
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 faulttolerant.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
SIL 2 Certification
Chapter 13
Figure 44 on page 196 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 faulttolerant configuration. The fault-tolerant configuration of the ControlLogix
system uses fully-redundant controllers, communication modules, and remote
I/O.
Figure 45 - Fault-tolerant Configuration
SIL2-certified ControlLogix Safety Loop
Secondary Chassis
Primary Chassis
PRI
PRI
COM
I/O Chassis A
DC OUTPUT
DC INTPUT
ANALOG INTPUT
ANALOG INTPUT
DC INTPUT
DC OUTPUT
ST 0 1 2 3 4 5 6 7 O
ST 8 9 10 11121314 15 K
ST 8 9 10 11121314 15 K
CAL
DIAGNOSTIC
DIAGNOSTIC
ST 0 1 2 3 4 5 6 7 O
OK
ST 8 9 10 11121314 15 K
OK
DIAGNOSTIC
ST 8 9 10 11121314 15 K
ANALOG INTPUT
DC OUTPUT
ST 0 1 2 3 4 5 6 7 O
ST 8 9 10 11121314 15 K
ST 8 9 10 11121314 15 K
ANALOG INTPUT
CAL
CAL
ST 0 1 2 3 4 5 6 7 O
ST 0 1 2 3 4 5 6 7 O
OK
ST 8 9 10 11121314 15 K
OK
DC INTPUT
ST 0 1 2 3 4 5 6 7 O
ST 8 9 10 11121314 15 K
DIAGNOSTIC
DIAGNOSTIC
DIAGNOSTIC
DIAGNOSTIC
Digital Output
Termination Board
Digital Input
Termination
Board
Field Device
DC INTPUT
ST 0 1 2 3 4 5 6 7 O
DIAGNOSTIC
Analog Input
Termination
Board
OK
I/O Chassis B
DC OUTPUT
CAL
ST 0 1 2 3 4 5 6 7 O
COM
OK
Field Device
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-UM001M-EN-P - February 2012
197
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
Then reference this manual
SIL2 Fault-tolerant I/O subroutines
(available for use with RSLogix 5000 software, version 15 and later)
ControlLogix SIL2 System Configuration Using RSLogix 5000 Subroutines, publication
1756-AT010
SIL2 Fault-tolerant I/O Add-On Instructions (available for use with
RSLogix 5000 software, version 16 and later)
ControlLogix SIL2 System Configuration Using RSLogix 5000 Subroutines, publication
1756-AT012
Additional Resources
These documents contain additional information concerning related Rockwell
Automation products.
Resource
Description
Using ControlLogix in SIL 2 Applications Reference Manual, publication 1756-RM001
Provides list of ControlLogix system components that meet SIL 2 requirements as well as
programming requirements.
ControlLogix SIL2 System Configuration Using RSLogix 5000 Subroutines, publication
1756-AT010
Explains how to use subroutines provided by Rockwell Automation to configure a faulttolerant system.
ControlLogix SIL2 System Configuration Using RSLogix 5000 Subroutines, publication
1756-AT012
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.
198
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Appendix
A
Status Indicators
1756-L7x Controller Status
Display and Indicators
Topic
Page
1756-L7x Controller Status Display and Indicators
199
1756-L7x Controller Status Display
199
1756-L7x Controller Status Indicators
206
1756-L6x Status Indicators
208
Additional Resources
211
The 1756-L7x controllers have four status indicators and one four-character
scrolling status display.
Figure 46 - 1756-L7x Status Display and Indicators
Logix557x
Scrolling Status Display, see page 200
Status Indicators, see page 206
RUN FORCE SD
OK
REM PR
OG
RUN
32009-MC
1756-L7x Controller Status
Display
The 1756-L7x 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-UM001M-EN-P - February 2012
199
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
Interpretation
No message is indicated
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.
TEST
Power-up tests are being conducted by the controller.
PASS
Power-up tests have been successfully completed.
SAVE
A project is being saved to the SD card. You can also view the SD Indicator (see page 207) for additional status information.
Allow the save to complete before:
• removing the SD card.
• disconnecting power.
LOAD
A project is being loaded from the SD card at controller powerup. You can also view the SD Indicator (see page 207) for additional status information.
Allow the load to complete before doing the following:
• Removing the SD card
• Disconnecting power
• Removing the ESM module
UPDT
A firmware upgrade is being conducted from the SD card upon powerup. You can also view the SD Indicator (see page 207) for additional status
information.
If you do not want the firmware to update upon powerup, change the controller’s Load Image property.
CHRG
The capacitor-based ESM is being charged.
1756-L7x/X
The controller catalog number and series.
Rev XX.xxx
The major and minor revision of the controller’s firmware.
No Project
No project is loaded on the controller.
To load a project, do one of the following:
• Use RSLogix 5000 software to download the project to the controller
• Use a SD card to load a project to the controller
Project Name
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.
BUSY
The I/O modules associated with the controller are not yet fully-powered.
Allow time for powerup and I/O module self-testing.
Corrupt Certificate
Received
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.
Corrupt Image Received
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.
ESM Not Present
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.
ESM Incompatible
The ESM is incompatible with the memory size of the controller.
Replace the incompatible ESM with a compatible ESM.
ESM Hardware Failure
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.
ESM Energy Low
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.
200
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Status Indicators
Appendix A
Table 54 - General Status Messages
Message
Interpretation
ESM Charging
The capacitor-based ESM is charging.
Do not remove power until charging is complete.
Flash in Progress
A firmware upgrade initiated via ControlFLASH or AutoFlash utilities is in progress.
Allow the firmware upgrade to complete without interruption.
Firmware Installation
Required
The controller is using boot firmware (that is revision 1.xxx) and requires a firmware upgrade.
Upgrade controller firmware.
SD Card Locked
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
Interpretation
Major Fault TXX:CXX message
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 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.
X I/O Faults
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.
Major Recoverable Fault Messages
Major recoverable faults are indicated by Major Fault TXX: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.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
201
Appendix A Status Indicators
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
202
Type
Code
Message
1
1
Run Mode Powerup
1
60
Non-recoverable
1
61
Non-recoverable – Diagnostics Saved
1
62
Non-recoverable – Program Saved
3
16
I/O Connection Failure
3
20
Chassis Failure
3
21
3
23
Connection Failure
4
16
Unknown Instruction
4
20
Invalid Array Subscript
4
21
Control Structure LEN or POS &lt; 0
4
31
Invalid JSR Parameter
4
34
Timer Failure
4
42
Invalid JMP Target
4
82
SFC Jump Back Failure
4
83
Value Out of Range
4
84
Stack Overflow
4
89
Invalid Target Step
4
90
Invalid Instruction
4
91
Invalid Context
4
92
Invalid Action
4
990
User-defined
4
991
4
992
4
993
4
994
4
995
4
996
4
997
4
998
4
999
6
1
Task Watchdog Expired
7
40
Save Failure
7
41
Bad Restore Type
7
42
Bad Restore Revision
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Status Indicators
Appendix A
Table 56 - Major Recoverable Fault Status Messages
Type
Code
Message
7
43
Bad Restore Checksum
8
1
Keyswitch Change Ignored
11
1
Positive Overtravel Limit Exceeded
11
2
Negative Overtravel Limit Exceeded
11
3
Position Error Tolerance Exceeded
11
4
Encoder Channel Connection Fault
11
5
Encoder Noise Event Detected
11
6
SERCOS Drive Fault
11
7
Synchronous Connection Fault
11
8
Servo Module Fault
11
9
Asynchronous Connection Fault
11
10
Motor Fault
11
11
Motor Thermal Fault
11
12
Drive Thermal Fault
11
13
SERCOS Communications Fault
11
14
Inactive Drive Enable Input Detected
11
15
Drive Phase Loss Detected
11
16
Drive Guard Fault
11
32
Motion Task Overlap Fault
11
33
CST Reference Loss Detected
18
1
CIP Motion Initialization Fault
18
2
CIP Motion Initialization Fault Mfg
18
3
CIP Motion Axis Fault
18
4
CIP Motion Axis Fault Mfg
18
5
CIP Motion Fault
18
6
CIP Module Fault
18
7
Motion Group Fault
18
8
CIP Motion Configuration Fault
18
9
CIP Motion APR Fault
18
10
CIP Motion APR Fault Mfg
18
128
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
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
203
Appendix A Status Indicators
• 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
204
Code
Message
#0001
Connection Failure
#0002
Insufficient Resource
#0003
Invalid Value
#0004
IOI Syntax
#0005
Destination Unknown
#0006
Partial Data Transferred
#0007
Connection Lost
#0008
Service Unsupported
#0009
Invalid Attribute Value
#000A
Attribute List Error
#000B
State Already Exists
#000C
Object Mode Conflict
#000D
Object Already Exists
#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
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Status Indicators
Appendix A
Table 57 - I/O Fault Messages
Code
Message
#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
#0318
Invalid Link Address
#0319
No Secondary Resources Available
#031E
No Available Resources
#031F
No Available Resources
#0800
Network Link Offline
#0801
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
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
205
Appendix A Status Indicators
Table 57 - I/O Fault Messages
1756-L7x Controller Status
Indicators
206
Code
Message
#FD0A
Axis Attribute Reject
#FD1F
Safety I/O
#FD20
No Safety Task
#FE01
Invalid Connection Type
#FE02
Invalid Update Rate
#FE03
Invalid Input Connection
#FE04
Invalid Input Data Pointer
#FE05
Invalid Input Data Size
#FE06
Invalid Input Force Pointer
#FE07
Invalid Output Connection
#FE08
Invalid Output Data Pointer
#FE09
Invalid Output Data Size
#FE0A
Invalid Output Force Pointer
#FE0B
Invalid Symbol String
#FE0C
Invalid Scheduled P/C Instance
#FE0D
Invalid Symbol Instance
#FE0E
Module Firmware Updating
#FE0F
Invalid Firmware File Revision
#FE10
Firmware File Not Found
#FE11
Firmware File Invalid
#FE12
Automatic Firmware Update Failed
#FE13
Update Failed - Active Connection
#FE14
Searching Firmware File
#FE22
Invalid Connection Type
#FE23
Invalid Unicast Allowed
#FF00
No Connection Instance
#FF01
Path Too Long
#FF04
Invalid State
#FF08
Invalid Path
#FF0B
Invalid Config
#FF0E
No Connection Allowed
The status indicators are below the status display on the controller. They indicate
the state of the controller as described in these tables.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Status Indicators
Appendix A
RUN Indicator
To change the controller mode indicated by the RUN indicator, either use the
mode switch on the front of the controller or use the Controller Status menu in
RSLogix 5000 software.
Table 58 - RUN Indicator
State
Description
Off
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
Description
Off
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.
SD Indicator
The SD indicator shows if the Secure Digital (SD) card is in use.
Table 60 - SD Indicator
State
Description
Off
No activity is occurring with the SD card.
Flashing green
The controller is reading from or writing to the SD card.
Do not remove the SD card while the controller is reading or writing.
Solid green
Flashing red
The SD card does not have a valid file system.
Solid red
The SD card is not recognized by the controller.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
207
Appendix A Status Indicators
OK Indicator
The OK indicator shows the state of the controller.
Table 61 - OK Indicator
1756-L6x Status Indicators
State
Description
Off
No power is applied to the controller.
Flashing red
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 page 51.
• It is a previously-used or in-use controller and a major fault has occurred. For details about
major recoverable and nonrecoverable faults, see the Logix5000 Major, Minor, and I/O Fault
Codes Programming Manual, publication 1756-PM014.
Solid red
One of the following is true:
• The controller is completing power-up diagnostics
• 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.
Solid green
The controller is operating normally.
The 1756-L6x controllers have status indicators on the front of the controller at
show the state of the controller.
Status Indicators
208
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Status Indicators
Appendix A
RUN Indicator
To change the controller mode indicated by the RUN indicator, either use the
mode switch on the front of the controller or use the Controller Status menu in
RSLogix 5000 software.
Table 62 - RUN Indicator
State
Description
Off
The controller is either in Program or Test mode.
Steady green
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
Description
Off
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.
Solid green
The controller is communicating with all of the devices in its I/O configuration.
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.
FORCE Indicator
The FORCE indicator shows if I/O forces are active or enabled.
Table 64 - FORCE Indicator
State
Description
Off
Either of the following is true:
• No tags contain I/O force values.
• I/O forces are inactive (disabled).
Steady 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-UM001M-EN-P - February 2012
209
Appendix A Status Indicators
RS232 Indicator
The RS232 indicator shows if the serial port is in use.
Table 65 - RS232 Status Indicator
State
Description
Off
There is no serial connection activity.
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
Description
Off
N/A
The controller is able to support memory.
Solid green
A
The series A controllers do not use this state.
B
The series B controller is conducting a save of the program to internal-nonvolatile
memory during a controller power down.
N/A
Either of the following is true:
• A battery is not installed.
• The battery is 95% discharged and should be replaced.
Solid red
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.
OK Indicator
The OK indicator shows the state of the controller.
Table 67 - OK Indicator
210
State
Description
Off
No power is applied to the controller.
Flashing red
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.
• The controller is experiencing a non-recoverable, major fault.
Steady red
• A nonrecoverable major fault occurred and the program was cleared from memory.
• The controller is completely powered up, in diagnostics mode.
• The controller is powered, but inoperable.
Steady green
The controller is operating normally.
Flashing green
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.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Status Indicators
Additional Resources
Appendix A
Consult these resources for additional information related to the status and
programming of the ControlLogix controllers.
Resource
Description
Logix5000 Controllers Major and Minor Faults Programming Manual, publication
1756-PM014
Explains major and minor faults of the controller and how to handle them.
Logix5000 Controllers Nonvolatile Memory Programming Manual, publication
1756-PM017
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
Allen-Bradley distributor or Rockwell Automation sales representative.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
211
Appendix A Status Indicators
Notes:
212
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Appendix
B
Using Electronic Keying
Electronic Keying
Topic
Page
Electronic Keying
213
Exact Match
214
Compatible Keying
215
Disabled Keying
217
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
Description
Vendor
The manufacturer of the module, for example, Rockwell Automation/Allen-Bradley.
Product Type
The general type of the module, for example, communication adapter, AC drive, or digital
I/O.
Product Code
The specific type of module, generally represented by its catalog number, for example,
1756-IB16I.
Major Revision
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.
Minor Revision
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-UM001M-EN-P - February 2012
213
Appendix B Using Electronic Keying
You can find revision information on the General tab of a module’s Properties
dialog box.
Figure 47 - General Tab
IMPORTANT
Exact Match
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 highlyregulated industries. Exact Match keying is also necessary to enable Automatic
214
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Using Electronic Keying
Appendix B
Firmware Update for the module via the Firmware Supervisor feature from a
Logix5000 controller.
EXAMPLE
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
Compatible Keying
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 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.
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
215
Appendix B Using Electronic Keying
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.
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
216
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Using Electronic Keying
EXAMPLE
Appendix B
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
Disabled Keying
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-UM001M-EN-P - February 2012
217
Appendix B Using Electronic Keying
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.
EXAMPLE
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
218
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Using Electronic Keying
EXAMPLE
Appendix B
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-UM001M-EN-P - February 2012
219
Appendix B Using Electronic Keying
Notes:
220
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
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
1756-UM001L-EN-P, November 2011
Added 1756-ESMNSE stored energy depletion rate
Added how to uninstall the ESM
1756-UM001K-EN-P, May 2011
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 Chapter 3, History of Changes, that describes changes made with
each revision of this manual
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
221
Appendix C History of Changes
Table 69 - History of Changes
Publication Revision and Date
Topic
1756-UM001J-EN-P, July 2010
Added 1756-L6x and 1756-L7x installation information
Added information in Chapter 3 to identify and describe common startup 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 1756L60M03SE 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
1756-UM001I-EN-P, October 2009
Added new information about broadcasting over serial port
Updated redundancy information
Updated battery information
Added new and updated EtherNet/IP motion information
1756-UM001H-EN-P, July 2008
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
222
Revision not published
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
History of Changes
Appendix C
Table 69 - History of Changes
Publication Revision and Date
Topic
1756-UM001C-EN-P, June 2001
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 RSView™32 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
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-UM001M-EN-P - February 2012
223
Appendix C History of Changes
Notes:
224
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Index
Numerics
1747-KY controller key
key 22
1756-BA1
check level 78, 77, 34
storage 82
1756-BA2
check level 78, 77, 34
estimate life 80
life after warning 81
storage 82
1756-BATA
controller compatibility 77
1756-BATM
battery 79
controller compatibility 77, 35
1756-CN2
uses 99
1756-CN2R
uses 99
1756-CN2RXT
uses 99
1756-CNB
uses 99
1756-CNBR
uses 99
1756-CP3
controller parts 35
1756-DHRIO
communication via 104
uses
remote I/O 104
1756-EN2F
uses 95
1756-EN2T
uses 95
1756-EN2TR
uses 95
1756-EN2TXT
uses 95
1756-EN3TR
uses 95
1756-ENBT
uses 95
1756-ESMCAP
controller parts 22
ESM 28
1756-ESMCAPXT
ESM 28
1756-ESMNRM 28
controller parts 23
ESM 28
1756-ESMNRMXT
ESM 28
1756-ESMNSE
controller parts 23
ESM 28
1756-ESMNSEXT
ESM 28
1756-EWEB
uses 95
1756-IF8H
uses 108
1756-L6x
add
while online 145
BAT indicator 212
CPU 91
FORCE indicator 211
I/O indicator 211
installation
battery, install 38
CompactFlash card, removal 36
into chassis 41
precautions 31
memory options 90
OK indicator 212
RS232
indicator 212
port 111
RUN indicator 211
serial driver 51, 50
1756-L7x
add
while online 145
CPU 91
double data rate (DDR) 45, 97
FORCE indicator 209
installation
ESM, install 29, 27
into chassis 23
key 24
SD card, install 26, 25
memory options 90
OK indicator 210
parts
included 22
RUN indicator 209
SD indicator 209
status display 201, 208, 210
USB driver 48
1756-L7xXT
extreme temperature controller 28
1756-N2 134
1756-N2XT 134
1756-OF8H
uses 108
1756-RIO
uses 104
1784-SD1 23
load from 72
SD card 22
store to 68
1784-SD2
controller parts 23
load from 72
store to 68
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
225
Index
A
add
distributed I/O 141
local I/O 134
remote I/O 137
Add-On Instructions
in project 169
application
elements 159
networks and 93
ASCII 119
attributes
keying 215
AutoFlash
upgrade 58
axis
obtain information 154
B
BAT indicator
1756-L6x 212
battery
1756-BA2
estimate 80
life after warning 81
catalog number 34, 78, 77
install 38
life and use 79
replacement 78
schedule 78, 82
uninstall 38
broadcast
messages 121
C
cache
message options 128
about 127
calculate
connection use 129
change
equipment phase 182
chassis
ControlLogix
list 134
insert controller 23, 41
check
WallClockTime 30
communication
Data Highway Plus 103, 104, 117
Foundation Fieldbus 107
HART 108
network options 89
path
set 60
universal remote I/O 104
226
CompactFlash card
installation 36
load from 72
other tasks 74
removal 36
store to 68
comparision
PhaseManager 182
compatibility
battery 77
compatible keying 217
configurations
fail-safe 197, 199
high-availability 198
configure
motion 153
serial driver 51, 174
connect
DH-485 network 117
connection
calculate use 129
DeviceNet
network 102
EtherNet/IP 96
network 96
example 131
local 129
message, required 127
produce/consume
data and 126
required 126
remote 130
scheduled
ControlNet 100
unscheduled
ControlNet 100
considerations
redundancy 188
consume
data 125
continuous task 162
ControlFLASH utility 55
controller
1756-L6x
battery and 77, 38
CompactFlash card, installation 36
insert into chassis 41
serial driver 51
battery and 77
communication options 89
ESM, install 29, 27
insert into chassis 23
key, insert 24
SD card, install 26, 25
status display 201, 208, 210
USB driver 48
battery
check 78
communication path
set 60
calculate 129
CPU resources 91
design system with 88, 62
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Index
estimate
battery life 80
firmware 53
obtain 55
go online 61
memory options 90
connections 171
parts included 23, 163
routine 166
tags 167, 160
upload 63
controller parts
1756-BA1 34, 35, 22, 23
battery 34
energy storage module
catalog number 22, 23
SAMTEC RSP-119350 23
serial cable 35
USB cable 23
ControlLogix
chassis
list 134
add while online 145
design system 88
I/O
remote 136
selection 133
modules
online addition 145
redundancy
about 185
local 134
slot filler 134
ControlLogix-XT
chassis
list 134
ControlNet
module capability 99
network 97
redundancy system and 190
scheduled connection
scheduled connection 100
unscheduled connection
unscheduled connection 100
CPU
controller 91
D
Data Highway Plus network 103
design
system 88
develop
applications 159
motion applications 153
DeviceNet
connection use 102
module
memory 102
network 100
software for 102
devices
add while online 147
DF1
master 112
point to point 113
radio modem 113
slave 116
DH-485 network
example configuration 117
overview 117
disabled keying 219
display
1756-L7x 201
distributed
I/O 140
add 141
double data rate (DDR)
1756-L7x 45, 97
download
project 62
drive
add while online 146
E
electronic keying
about 215
elements
control application 159
enhanced redundancy. See redundancy.
equipment phase
change manually 182
instructions 183
error
script file 57
ESM 28
1756-ESMCAP 28
install 29
uninstall 27
EtherNet/IP
add while online 150
connections 96
module features 94, 95
network 94
redundancy system and 191
software for 96
event task 162
exact match keying 216
example configuration
DH-485 network 117
extreme temperature controller
1756-L7xXT 28
F
fail-safe configruation
about 197
fault code
use GSV to get 172
fault handler
execute at I/O fault 172
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
227
Index
fault messages 203
I/O 205
Major Recoverable Fault 203
fault-tolerant configruation
about 199
features 89
controller
communication 89
programming 89
filler slot
slot filler 134
firmware
controller 53
determine 54
obtain 55
security certificate, error 57
upgrade
AutoFlash, use 58
FORCE indicator
1756-L6x 211, 209
Foundation Fieldbus 107
G
general status messages 202
GSV
fault code 172
monitor
connection 172
1756-L6x 212
FORCE
1756-L6x 211, 209
I/O
1756-L6x 211
OK
1756-L6x 212, 210
RS232
1756-L6x 212, 209
SD
1756-L7x 209
install
1756-L6x
battery 38
CompactFlash card 36
insert into chassis 41
precautions 31
ESM 29
insert into chassis 23
key, insert 24
SD card 26
battery 38
CompactFlash card 36
ESM 29
SD card 26
instruction
ASCII 119
motion 154
IP address swapping 191
K
H
HART. See Highway Addressable Remote
Transducer.
high-availability configruation
about 198
Highway Addressable Remote Transducer 108
hold-up time
ESM WallClockTime 76
I
key
1747-KY controller key 22
insert 24
keying
about 215
compatible 217
disabled 219
exact match 216
L
load
I/O
connection error 172
ControlLogix
remote 136
selection 133
determine data update 151, 140
fault codes 205
reconfigure 143, 136
I/O configuration
add
distributed I/O 141
local I/O 134
remote I/O 137
while online 144
I/O indicator
1756-L6x 211
indicator 208
BAT
228
from memory card 72
status indicators during 73
local
connection 129
I/O
add 134
remote I/O 134
M
Major Recoverable Fault
messages 203
memory
DeviceNet module 102
options 90
memory card
load from 72
other tasks 74
store to 68
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Index
message
about 127
broadcast over serial 121
cache 128
determine if 128
fault 203
reconfigure I/O module 143
status display 202
Modbus network 124
mode
serial port 112
module
ControlNet 99
EtherNet/IP 94, 95
motion
about 153
instructions 154
program 154
MVI56-HART
uses 108
N
network
application and 93
controller options 89
ControlNet 97, 190
Data Highway Plus 104, 100
EtherNet/IP 94, 191
Foundation Fieldbus 107
HART 108
universal remote I/O 104
nonvolatile memory 90
O
obtain
axis information 154
firmware 55
OK indicator
1756-L6x 212, 210
online
add
EtherNet/IP 150
to I/O configuration 144
go 61
options
memory 90
P
path
set
communication 60
periodic task 162
PhaseManager
about 177
change states 182
equipment phase instructions 183
state model 180, 179
terminology 177, 181
port
communication 89
PowerFlex
add
while online 146
precautions 31
priority
task 163
produce
data 125
produce/consume
connections
required 126
data 125
program
in project 163
scheduled 165, 173
unscheduled 165
programming languages 168
project
Add-On Instructions 169
download 62
elements 159
go online 61
load
status indicators during 73
program 163
routine 166
samples 175
status indicators during 71
tags 167, 160
upload 63
protocol
ASCII 119
DF1
master 112
point to point 113
radio modem 113
slave 116
Modbus network 124
serial port 112
R
receive
messages 127
redundancy
about 185
build system 190
considerations 188
ControlNet network 190
EtherNet/IP network 191
scan time 192, 187
remote
connection 130
I/O 136
remote I/O
add 137
ControlLogix
local 134
universal 104
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
229
Index
remove
1756-L6x
CompactFlash card 36
SD card 25
CompactFlash card 36
SD card 25
replace
battery
schedule 78
required
connections
messages 126, 127
requirement
PhaseManager
system 179
redundancy 187
RIO. See universal remote I/O
routine
in project 166
RS232
DF1 device driver 51
indicator
1756-L6x 212
RSLogix 5000
Add-On Instructions 169
program 163
routine 166
sample projects 175
tags 167, 160
RSWho
set
path 60
RUN indicator
1756-L7x 209
S
safety integration level, see SIL 2 195
sample projects 175
SAMTEC RSP-119350
controller parts 23
scan time
redundancy and 192
scheduled
program 165
script file
error 57
SD card
1784-SD1 22
install 26
load from 72
other tasks 74
removal 25
store to 68
SD indicator
1756-L7x 209
security certificate
error 57
selection
I/O 133
send
messages 127
230
serial
broadcast 121
cable
catalog number 35
DH-485 network configuration 117
driver 51
Modbus network 124
serial port
1756-L6x 50
ASCII 119
DF1
master 112
point to point 113
radio modem 113
slave 116
mode 112
protocols 112
service communication 173
set up
serial driver 51
USB driver 48
SIL 2 certification
overview 195
software
DeviceNet and 102
EtherNet/IP and 96
required
USB 47
standard redundancy. See redundancy.
state
equipment phase
change 182
state model
overview 180
status
battery 78
display
1756-L7x 201
fault messages 203
indicators
1756-L7x 208, 210
load 73
messages
display 202
connections 171
status indicators
store 71
storage
battery 82
store
to memory card 68
store project
status indicators during 71
swapping IP address 191
system 89
system overhead time slice 173
configure 174
system requirements
PhaseManager 179
redundancy 187
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
Index
T
tag
consume 125
in project 167
produce 125
task
continuous 162
event 162
in project 160
periodic 162, 163
time slice 173
transistion
PhaseManager 181
type
USB 47
universal remote I/O 104
communicate via 106
unscheduled
program 165
update
determine frequency 151
upgrade
firmware
AutoFlash, use 58
upload
project 63
USB
cable
catalog number 23
driver 48
software required 47
type 47
U
uninstall
1756-L6x
battery 38
ESM 27
battery 38
ESM 27
W
WallClockTime object
check 30
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
231
Index
Notes:
232
Rockwell Automation Publication 1756-UM001M-EN-P - February 2012
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
TechConnectSM 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
1.440.646.3434
Outside United States or Canada
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
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.
Outside United States
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 İ&ccedil;erenk&ouml;y, İstanbul, Tel: +90 (216) 5698400
www.rockwel lautomation.com
Power, Control and Information Solutions Headquarters
Americas: Rockwell Automation, 1201 South Second Street, Milwaukee, WI 53204-2496 USA, Tel: (1) 414.382.2000, Fax: (1) 414.382.4444
Europe/Middle East/Africa: Rockwell Automation NV, Pegasus Park, De Kleetlaan 12a, 1831 Diegem, Belgium, Tel: (32) 2 663 0600, Fax: (32) 2 663 0640
Asia Pacific: Rockwell Automation, Level 14, Core F, Cyberport 3, 100 Cyberport Road, Hong Kong, Tel: (852) 2887 4788, Fax: (852) 2508 1846
Publication 1756-UM001M-EN-P - February 2012
Supersedes Publication 1756-UM001L-EN-P - May 2011
Copyright &copy; 2012 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.
ControlLogix System User Manual
User Manual
">

Hello! I've analyzed the Allen-Bradley ControlLogix 1756-L61, 1756-L62, 1756-L63, 1756-L63XT, 1756-L64, 1756-L65, 1756-L71, 1756-L72, 1756-L73, and 1756-L73XT Controller User Manual and I am ready to answer your questions about installation, features, and usage. Ask me anything!

Show related prompts

Assistant typing

Assistant is out of keyboard. Please, try again later.

Key features

Supports multiple communication networks (EtherNet/IP, ControlNet, DeviceNet)
Offers optional redundant configurations
Includes models for extreme temperature environments (-25...70°C)
Provides motion control capabilities
Supports memory expansion via SD or CompactFlash card
Features USB port for connectivity
Offers SIL 2 certified models for safety applications

Frequently asked questions

The 1756-L7x controllers have built-in USB ports and support communication via EtherNet/IP, ControlNet, and DeviceNet.

The 1756-L7x controllers use an Energy Storage Module (ESM) for memory retention at powerdown.

Yes, the ControlLogix system supports motion control applications.

The extreme environment ControlLogix controllers, such as the 1756-L73XT and 1756-L63XT, are designed to withstand temperatures -25...70 °C (-13...158 °F).

What are the communication options for the 1756-L7x controllers?

What type of memory backup do 1756-L7x controller use?

Does the controller support motion control applications?

What is the operating temperature for the extreme environment controllers?

Related

ControlLogix Controller User Manual L6x 1756-L61, L6x 1756-L62, L6x 1756-L63, L6x 1756-L63XT, L6x 1756-L64, L6x 1756-L65, L7x 1756-L72

ControlLogix Controller User Manual - Allen-Bradley

Allen-Bradley 1756-L6 Series, 1756-L7 Series Reference Manual

ControlLogix 1756-L6x, ControlLogix 1756-L7x Safety Reference Manual

ControlLogix 1756-L6x, 1756-L7x Safety Reference Manual

Allen-Bradley Controller Manual: AI Chat & PDF Access

Manuale dell'utente ControlLogix 1756-L61, 1756-L62, 1756-L63, 1756-L63XT, 1756-L64, 1756-L65, 1756-L71, 1756-L72, 1756-L73, 1756-L73XT, 1756-L74, 1756-L75

Rockwell Automation Allen-Bradley 1756-EN2TSC Installation Instructions Manual

Logix5000 Controllers Guide: AI Chat & PDF Access

Allen-Bradley 1756-EN2T Installation Instructions Manual

Controladores ControlLogix Manual del Usuario