02 - 1756-L72 ControlLogix System
02 - 1756-L72 ControlLogix System
02 - 1756-L72 ControlLogix System
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
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.
Page
Studio 5000 Logix Designer application is the rebranding of RSLogix 5000 software
11
25
141
154
Summary of Changes
Notes:
Table of Contents
Preface
11
11
12
12
12
13
13
14
Chapter 1
Install the 1756-L7x Controller
17
17
17
18
18
19
20
21
23
25
26
Chapter 2
Install the 1756-L6x Controller
31
31
31
32
32
36
39
41
Chapter 3
Start Using the Controller
Make Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1756-L7x Connection Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1756-L6x Connection Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connect to the 1756-L7x Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Set Up the USB Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connect to the 1756-L6x Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configure the Serial Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Upgrade Controller Firmware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Determine Required Controller Firmware. . . . . . . . . . . . . . . . . . . . . .
Obtain Controller Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Use ControlFLASH Utility to Upgrade Firmware . . . . . . . . . . . . . .
43
43
44
44
45
47
48
50
50
51
51
Table of Contents
54
56
57
58
58
59
59
59
60
61
61
63
64
64
67
69
69
70
71
71
72
72
73
74
74
75
76
Chapter 4
ControlLogix System and Controllers ControlLogix System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Configuration Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Design a ControlLogix System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ControlLogix Controller Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System, Communication, and Programming Features . . . . . . . . . . . .
Memory Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
77
80
81
81
82
Chapter 5
Communication Networks
Networks Available. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EtherNet/IP Network Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ControlLogix EtherNet/IP Module Features. . . . . . . . . . . . . . . . . . . .
ControlLogix EtherNet/IP Communication Modules . . . . . . . . . . .
Software for EtherNet/IP Networks. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connections over an EtherNet/IP Network . . . . . . . . . . . . . . . . . . . .
Double Data Rate (DDR) Backplane Communication. . . . . . . . . . .
ControlNet Network Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ControlLogix ControlNet Module Features . . . . . . . . . . . . . . . . . . . .
Rockwell Automation Publication 1756-UM001N-EN-P - November 2012
83
84
84
85
86
86
87
87
89
Table of Contents
89
89
90
90
91
91
92
92
92
92
93
94
95
96
97
Chapter 6
Serial Communication
on 1756-L6x Controllers
100
100
101
101
101
102
103
103
104
104
105
107
107
109
110
111
111
Chapter 7
Manage Controller Communication
Connection Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Produce and Consume (interlock) Data. . . . . . . . . . . . . . . . . . . . . . . . . . .
Connection Requirements of a Produced or Consumed Tag . . . .
Send and Receive Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Determine Whether to Cache Message Connections . . . . . . . . . . .
Calculate Connection Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Local Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Remote Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connections Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
113
114
114
116
116
117
117
118
119
Table of Contents
Chapter 8
I/O Modules
121
122
123
124
125
128
129
131
131
132
132
133
135
138
139
Chapter 9
Develop Motion Applications
141
142
142
143
143
144
Chapter 10
Develop Applications
145
146
149
149
151
152
153
154
154
156
157
158
159
160
160
161
162
163
164
Table of Contents
Chapter 11
Using the PhaseManager Tool
PhaseManager Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Minimum System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
State Model Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How Equipment Changes States. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Manually Change States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PhaseManager Tool versus Other State Models . . . . . . . . . . . . . . . . . . . .
Equipment Phase Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
165
167
167
168
169
170
170
Chapter 12
Redundant Systems
171
173
174
175
175
176
176
176
177
Chapter 13
SIL 2 Certification
Introduction to SIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Programming and Debugging Tool (PADT). . . . . . . . . . . . . . . . . . .
Typical SIL2 Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fail-safe Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
High-availability Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault-tolerant Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
179
179
180
181
182
183
Appendix A
Status Indicators
185
185
186
187
188
190
193
193
193
193
194
194
194
195
195
195
Table of Contents
Appendix B
Using Electronic Keying
Electronic Keying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exact Match . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Compatible Keying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disabled Keying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
197
198
199
201
Appendix C
History of Changes
Index
10
206
206
206
207
207
207
207
207
208
208
208
208
Preface
ControlLogix Controllers
Overview
There are three types of ControlLogix controllers available. These types include
the following:
Standard ControlLogix controllers
Extreme environment ControlLogix controller
Safety GuardLogix controllers
This manual explains how to use standard 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.
11
Preface
Cat. No.
1756-L6x
1756-L7x
The standard 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
Battery
USB
Serial
Connections, controller
500
250
Memory, nonvolatile
CompactFlash card
20 (40, max)
10 (40, max)
12
Preface
Before you begin using your ControlLogix controller, verify that you have the
applications required to configure and program the controller.
Required Software
Use this table to identify the minimum software versions required to use your
ControlLogix controller.
Table 3 - Required Software for Controller Use
Cat. No.
RSLinx Classic
1756-L61/A
Any version
1756-L61/B
1756-L62/A
1756-L62/B
1756-L63/A
1756-L63/B
1756-L63XT/B
1756-L64/B
Any version
1756-L65/B
1756-L71/A
Version 20.01.02
1756-L72/A
1756-L73/A
1756-L73XT/A
1756-L74/A
1756-L75/A
13
Preface
Additional Resources
Description
14
Chapter
Topic
Page
17
17
18
19
20
21
23
25
26
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.
15
Chapter 1
Products marked "CL I, DIV 2, GP A, B, C, D" are suitable for use in Class I Division 2 Groups
A, B, C, D, Hazardous Locations and nonhazardous locations only. Each product is supplied
with markings on the rating nameplate indicating the hazardous location temperature
code. When combining products within a system, the most adverse temperature code
(lowest "T" number) may be used to help determine the overall temperature code of the
system. Combinations of equipment in your system are subject to investigation by the
local Authority Having Jurisdiction at the time of installation.
Les produits marqus "CL I, DIV 2, GP A, B, C, D" ne conviennent qu' une utilisation en
environnements de Classe I Division 2 Groupes A, B, C, D dangereux et non dangereux.
Chaque produit est livr avec des marquages sur sa plaque d'identification qui indiquent
le code de temprature pour les environnements dangereux. Lorsque plusieurs produits
sont combins dans un systme, le code de temprature le plus dfavorable (code de
temprature le plus faible) peut tre utilis pour dterminer le code de temprature
global du systme. Les combinaisons d'quipements dans le systme sont sujettes
inspection par les autorits locales qualifies au moment de l'installation.
WARNING:
This equipment shall be mounted in an ATEX certified enclosure with a minimum ingress protection rating of at least IP54
(as defined in IEC60529) and used in an environment of not more than Pollution Degree 2 (as defined in IEC 60664-1) when
applied in Zone 2 environments. The enclosure must utilize a tool removable cover or door.
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.
16
Chapter 1
Complete these tasks using the appropriate resources listed as references before
you install your controller and power supply.
Task
Install a ControlLogix Chassis and Power Supply
Resources
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.
Logix 5575
RUN FORCESD
OK
SD Card (installed)
1756-ESMCAP
(installed)
1747-KY Key
IMPORTANT
32016-M
17
Chapter 1
USB cable(1)
Nonvolatile memory
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.
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 Hold-up Time (in days) on page 71 and stored energy depletion rate on
page 26.
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.
1756-L7x Controller
Installation
These sections explain how to install the 1756-L7x controller. To install the
1756-L7x controller, complete the tasks summarized in this table.
Task
Insert the Controller into the Chassis
19
20
21
21
18
Page
25
Chapter 1
IMPORTANT
19
Chapter 1
1. Align the circuit board with the top and bottom guides in the chassis.
Top Circuit Board
Aligned
Logix 55xx
RUN FORCE
SD
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 185 for information about interpreting the status indicators.
Logix 55xx
RUN FORCE
SD
20
OK
Chapter 1
Unlocked
Locked
32005-M
For more information about the lock/unlock memory settings, see the
Load or Store to the Memory Card on page 64.
2. Open the door for the SD card.
Logix 55xx
RUN FORCE
SD
OK
32002-M
21
Chapter 1
Logix 55xx
RUN FORCE
SD
OK
32004-M
Logix 55xx
RUN FORCE
SD
OK
32006-M
22
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
1784-SD1 or 1784-SD2).
Logix 55xx
RUN FORCE
SD
OK
32015-M
23
Chapter 1
Logix 55xx
RUN FORCE
SD
OK
32004-M
24
Chapter 1
Logix 55xx
RUN FORCE
SD
OK
TIP
Allow the ESM to finish charging before removing power from the controller.
Failure to do so can result in the loss of the application program. A type 1,
code 40 major fault will be logged on powerup.
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.
The ESM contains a real-time clock. If the ESM is new or came from another
controller, your controllers WallClockTime object attributes may change.
25
Chapter 1
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 controllers 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.
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.
IMPORTANT
1756-ESMCAP
1756-ESMNSE
1756-ESMCAPXT
1756-ESMNSEXT
26
Chapter 1
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 controllers 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 FORCE
SD
OK
Logix 55xx
RUN FORCE
SD
OK
27
Chapter 1
Notes:
28
Chapter
Topic
Page
31
31
32
32
36
39
41
29
Chapter 2
Products marked "CL I, DIV 2, GP A, B, C, D" are suitable for use in Class I Division 2 Groups
A, B, C, D, Hazardous Locations and nonhazardous locations only. Each product is supplied
with markings on the rating nameplate indicating the hazardous location temperature
code. When combining products within a system, the most adverse temperature code
(lowest "T" number) may be used to help determine the overall temperature code of the
system. Combinations of equipment in your system are subject to investigation by the
local Authority Having Jurisdiction at the time of installation.
Les produits marqus "CL I, DIV 2, GP A, B, C, D" ne conviennent qu' une utilisation en
environnements de Classe I Division 2 Groupes A, B, C, D dangereux et non dangereux.
Chaque produit est livr avec des marquages sur sa plaque d'identification qui indiquent
le code de temprature pour les environnements dangereux. Lorsque plusieurs produits
sont combins dans un systme, le code de temprature le plus dfavorable (code de
temprature le plus faible) peut tre utilis pour dterminer le code de temprature
global du systme. Les combinaisons d'quipements dans le systme sont sujettes
inspection par les autorits locales qualifies au moment de l'installation.
WARNING:
This equipment shall be mounted in an ATEX certified enclosure with a minimum ingress protection rating of at least IP54
(as defined in IEC60529) and used in an environment of not more than Pollution Degree 2 (as defined in IEC 60664-1) when
applied in Zone 2 environments. The enclosure must utilize a tool removable cover or door.
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.
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.
30
Chapter 2
Complete these tasks using the appropriate resources listed as references before
you install your controller and power supply.
Task
Install a ControlLogix Chassis and
Power Supply
Resources
Refer to ControlLogix Chassis and Power Supplies, publication 1756-IN005
These sections describe parts that are included with the 1756-L6x controllers, as
well as available accessory parts:
One of the following batteries is included with your controller:
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
Nonvolatile memory
(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.
31
Chapter 2
1756-L6x Controller
Installation
Page
32
36
CompactFlash Card
Installation and Removal
39
41
32
Chapter 2
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.
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.
33
Chapter 2
1
3
1. Open the door of the controller and push the CompactFlash latch to the
left.
2. Insert the CompactFlash card with the Allen-Bradley logo pointing left.
3. Release the latch and secure it over the CompactFlash card.
34
Chapter 2
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.
35
Chapter 2
Battery Connection
and Replacement
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.
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
-2535 C (-1395 F)
No replacement required
3640 C (96.8104 F)
3 years
4145 C (105.8113 F)
2 years
4650 C (114.8122 F)
16 months
5155 C (123.8131 F)
11 months
5670 C (132.8158 F)
8 months
36
Chapter 2
DATE
Connected Wire
Top
No connection
Middle
Bottom
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.
37
Chapter 2
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
To Eject
1+2
UP
BATTERY
DATE
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.
38
Chapter 2
39
Chapter 2
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 on page 185 for more information related to the state of the
controller.
40
Chapter 2
You can 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.
Complete these steps to remove the controller from the chassis.
1. Press the locking tabs on the top and bottom of the controller.
2. Slide the controller out of the chassis.
20880
41
Chapter 2
Notes:
42
Chapter
Topic
Page
Make Connections
43
44
47
50
56
58
59
61
61
63
64
69
71
Make Connections
57
72
Before you can begin using your controller, you must make a connection to the
controller.
43
Chapter 3
Connect to the
1756-L7x Controller
The controller has a USB port that uses a Type B receptacle. The port is USB 2.0
compatible and runs at 12 Mbps.
To use the USB port of the controller, you must have RSLinx software,
version 2.56 or later, installed on your workstation. Use a USB cable to connect
your workstation to the USB port. With this connection, you can upgrade
firmware and download programs to the controller directly from your
workstation.
ATTENTION: The USB 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.
Logix 55xx
RUN FORCE
SD
OK
32007-M
32007-M
44
Chapter 3
2. Click any of the Windows Update connection options and click Next.
If the software for the USB driver is not found and the installation is
TIP
canceled, verify that you have installed RSLinx Classic software,
version 2.57 or later.
45
Chapter 3
Your controller appears under two different drivers, a virtual chassis and the USB
port. You can use either driver to browse to your controller.
46
Connect to the
1756-L6x Controller
Chapter 3
42576
To Controller
1 CD
1 CD
2 RDX
2 RDX
3 TXD
3 TXD
4 DTR
COMMON
4 DTR
COMMON
6 DSR
6 DSR
7 RTS
7 RTS
8 CTS
8 CTS
42231
47
Chapter 3
Plug the controller end of the serial cable into the RS-232 port on the front of 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
To Eject
1+2
UP
BATTERY
DATE
1
2
BATTERY
PORT
48
Chapter 3
2. From the Available Driver Types pull-down menu, choose the RS-232
DF1 device driver.
49
Chapter 3
You may choose to upgrade controller firmware by using either of these tools:
ControlFLASH software packaged with the Studio 5000 environment
AutoFlash feature of the Logix Designer application
To upgrade your controller firmware, complete the tasks listed in this table.
Task
Page
50
51
51
54
The controller must be in Remote Program or Program mode and all major
recoverable faults cleared to accept upgrades.
Use this table to determine what firmware revision is required for your controller.
Table 4 - Firmware Required For Controllers
Controller
Series
1756-L61
12.x or later
13.40 or later
12.x or later
13.40 or later
13.40 or later
1756-L63XT
13.40 or later
1756-L64
16 or later
1756-L65
17 or later
1756-L71
20 or later
1756-L72
19 or later
1756-L73
19 or later
1756-L73XT
19 or later
1756-L74
19 or later
1756-L75
19 or later
1756-L62
1756-L63
50
Chapter 3
If the SD card is locked and the stored projects 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. Start ControlFLASH software and click Next to begin the upgrade
process.
1756-L6x Controllers
51
Chapter 3
52
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.
WARNING: Allow the firmware update to fully complete before cycling power
or otherwise interrupting the upgrade.
TIP
53
Chapter 3
When the upgrade is complete, the Update Status dialog box indicates that
the upgrade is complete.
9. Click OK.
10. Close ControlFLASH software.
If the SD card is locked and the stored projects 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 your network
driver is configured in RSLinx software.
2. Use the Logix Designer application to create a controller project at the
version you need.
54
Chapter 3
55
Chapter 3
6. Click Yes.
The firmware upgrade begins.
To get online with the controller, you must specify a communication path in the
Logix Designer application. You specify the communication path after you create
a controller program.
Complete these steps to specify the communication path after you have created
your program.
1. Click Who Active.
56
Chapter 3
57
Chapter 3
Downloading a project to the controller moves the project from the Logix
Designer application onto the controller. You can download a project in two
ways:
Use the Who Active Dialog Box to Download on page 58
Use the Controller Status Menu to Download on page 59
2. Click Download after reading the warnings in the Download dialog box.
58
Chapter 3
TIP
Uploading a project to the controller copies the project from the controller to the
Logix Designer application. To upload a project, use one of these methods:
Use the Who Active Dialog Box to Upload, page 59
Use the Controller Status Menu to Upload, page 60
59
Chapter 3
2. Click Upload after verifying the project you are uploading in the
Connected to Upload dialog box.
60
Chapter 3
Use this table as a reference when determining your controller Operation mode.
Table 5 - Controller Operation Modes and Meanings
Select one of these modes
If you want to
Run
Remote
Run
Test
Program
Program
Download a project
Send messages
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 controllers 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
products program, configuration, or firmware.
61
Chapter 3
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
Logix557x
Logix556x
RUN FORCE SD
OK
REM PR
OG
RUN
Mode Switch
ATTENTION:
Mode Switch
Position
RUN
REM
62
Chapter 3
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.
63
Chapter 3
The memory card that is compatible with your ControlLogix controller is used to
load or store the contents of user memory for the controller.
TIP
3. Change the Load Image, Load Mode, and Automatic Firmware Update
properties according to your application requirements.
64
Chapter 3
The table below describes the Load Image options you can choose for the
project.
IMPORTANT
If the SD card is locked and the stored projects 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.
Then choose
On Power Up
The controller has lost the project and power has been cycled or
applied
On Corrupt Memory
User Initiated
The table below describes the Load Mode options you can choose for the
project.
If you want the controller to go to this mode after
loading
Then choose
Program
Run
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.
If you want to
Then choose
Disable
(1) The devices used with this option must support the version of firmware being updated to.
65
Chapter 3
4. Click Store, then click OK in the confirmation dialog box that appears.
After clicking Store, the project is saved to the memory card as indicated
by the controller status indicators.
With these controllers
1756-L6x
1756-L7x
IMPORTANT
66
Chapter 3
TIP
3. Verify that the image in nonvolatile memory (that is, the project on the
memory card) is the project you want to load.
TIP
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.
67
Chapter 3
4. Click Load.
1756-L6x
1756-L7x
IMPORTANT
68
Chapter 3
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
controllers 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 controllers on-board NVS memory.
For more information, see Clear the Program from On-board NVS
Memory.
The following table describes the ESMs.
Cat. No.
Description
1756-ESMCAP
Capacitor-based ESM
The 1756-L7x controllers come with this ESM installed.
1756-ESMNSE
1756-ESMNRM
69
Chapter 3
RUN FORCE SD
OK
N REM PRO
RU
2. Leave the ESM on the controller until the OK status indicator is Off.
70
Chapter 3
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 C (68 F)
12
12
40 C (104 F)
10
10
60 C (140 F)
IMPORTANT
Any action causing the 1756-L7x controller to reset (hard or soft), without an
ESM installed, will result in the controllers wall clock time being reset to the
factory default of 01/01/1998.
To check the status of the ESM, refer to General Status Messages on page 186.
71
Chapter 3
This section explains how to monitor and maintain the lithium batteries
supported by ControlLogix controllers.
Table 6 - 1756-L6x Controllers and Compatible Batteries
Cat. No.
Series
Compatible Battery
1756-L61
1756-L62
1756-L63
1756-BA1
or
1756-BATA
or
1756-BATM
1756-L61
1756-L62
1756-L63
1756-L64
1756-L65
1756-BA2
1756-L63XT
Description
No replacement required
3640 C (96.8104 F)
3 years
4145 C (105.8113 F)
2 years
4650 C (114.8122 F)
16 months
5155 C (123.8131 F)
11 months
5670 C (132.8158 F)
72
8 months
Chapter 3
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.
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.
60 C (140 F)
22 days
43 days
23%
6 hrs
25 C (77 F)
21 days
42 days
17%
28 hrs
0 C (32 F)
14 days
28 days
17%
2.5 days
60 C (140 F)
98 days
204 days
11%
104 days
25 C (77 F)
146 days
268 days
5%
157 days
0 C (32 F)
105 days
222 days
6%
113 days
73
Chapter 3
If your project is not stored in nonvolatile memory, the use of the battery
module is highly recommended.
Power Cycles
2 MB
4 MB
8 MB
16 MB
3 per day
3 years
3 years
26 months
20 months
10 months
3 years
3 years
3 years
31 months
16 months
3 per day
2 years
2 years
2 years
20 months
10 months
2 years
2 years
2 years
2 years
16 months
46...50 C (105.8...113 F)
16 months
16 months
16 months
16 months
10 months
51...55 C (123.8...131 F)
11 months
11 months
11 months
11 months
10 months
5670 C (132.8158 F)
8 months
8 months
8 months
8 months
8 months
-2535 C (-1395 F)
41...45 C (105.8...113 F)
74
Chapter 3
Power Cycles
Battery Life After the BAT Status Indicator Turns Red (worst case)
Project Size
1 MB
18 weeks
12 weeks
9 weeks
5 weeks
26 weeks
26 weeks
26 weeks
22 weeks
13 weeks
26 weeks
26 weeks
26 weeks
26 weeks
26 weeks
3 per day
18 weeks
14 weeks
10 weeks
8 weeks
5 weeks
24 weeks
21 weeks
18 weeks
16 weeks
11 weeks
26 weeks
26 weeks
26 weeks
26 weeks
26 weeks
3 per day
12 weeks
10 weeks
7 weeks
6 weeks
4 weeks
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
56...60 C (132.8...140 F)
26 weeks
1 per day
51...55 C (123.8...131 F)
3 per day
1 per month
46...50 C (105.8...113 F)
16 MB
1 per day
41...45 C (105.8...113 F)
8 MB
1 per month
21...40 C (69.8...104 F)
4 MB
1 per day
0...20 C (32...68 F)
2 MB
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 C
(113 F).
You cycle power to the controller three times per day.
The controller contains an 8 MB project.
75
Chapter 3
76
Chapter
Topic
ControlLogix System
77
80
ControlLogix System
Page
81
Configuration Options
This section describes some of the many system configuration options that are
available with ControlLogix controllers.
Output
Output
Input
Input
Input
L75
L75
32044-MC
77
Chapter 4
EN2T
EN2T
L75
L75
FactoryTalk Server
Ethernet
Ethernet
Motor
Motor
Kinetix 6500 Drive
78
32045-MC
Chapter 4
HART
IF8H
EN2T
EN2T
CN2
DNB
L75
HART
DeviceNet
Ethernet
ControlNet
PowerFlex Drive
FactoryTalk Server
FLEX I/O
Ethernet Device-level
Ring Network
POINT I/O
32046-MC
79
Chapter 4
When you design a ControlLogix system, there are several system components to
consider for your application. Some of these components include the following:
I/O devices
Motion control and drive requirements
Communication modules
Controllers
Chassis
Power supplies
Studio 5000 environment
For more information about designing and selecting components for your
ControlLogix system, see the ControlLogix Selection Guide, publication
1756-SG001.
In addition, if you are designing your ControlLogix System for any of the specific
applications listed in this table, see the appropriate resources for more
information.
For this type of application
Enhanced redundancy
Standard redundancy
SIL2
80
ControlLogix Controller
Features
Chapter 4
Controller tasks
32 tasks
100 programs/task
Event tasks: all event triggers
Communication ports
Communication options
EtherNet/IP
ControlNet
DeviceNet
Data Highway Plus
Remote I/O
SynchLink
Third-party process and device networks
ASCII
DF1 full/half-duplex
DF1 radio modem
DH-485
Modbus via logic
250
Controller redundancy
Integrated motion
Programming languages
N/A
500
Relay ladder
Structured text
Function block
Sequential Function Chart (SFC)
81
Chapter 4
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 12 - ControlLogix Controller Memory Options
Controller
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
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.
IMPORTANT
IMPORTANT
82
Chapter
Communication Networks
Topic
Networks Available
83
84
87
90
92
94
96
HART Communication
Networks Available
Page
97
Supported Networks
Integrated Motion
EtherNet/IP
EtherNet/IP
ControlNet
EtherNet/IP
ControlNet
DeviceNet
EtherNet/IP
Foundation Fieldbus
HART
Universal remote I/O
ControlNet
DeviceNet (only to devices)
Data Highway Plus (DH+)
DH-485
EtherNet/IP
Serial
For additional information about network design for your system, see the
Ethernet Design Considerations Reference Manual, publication ENET-RM002.
83
Chapter 5
Communication Networks
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.
EtherNet/IP Network
Communication
ControlLogix
Controller with
1756-EN2T Module
Distributed I/O
LINK NET OK
LINK NET OK
Switch
Workstation
For more information about using EtherNet/IP modules, see the EtherNet/IP
Modules in Logix5000 Control Systems User Manual, publication
ENET-UM001.
84
Communication Networks
Chapter 5
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
1756-EN2TR
1756-EN3TR
1756-EN2TXT
1756-EWEB
85
Chapter 5
Communication Networks
Is used to
Required or Optional
Required
Required
BOOTP/DHCP Utility
Optional
86
Communication Networks
Chapter 5
ControlNet Network
Communication
87
Chapter 5
Communication Networks
1756-CNB Module
(as an adapter) with
1756 I/O Modules
ControlNet Network
1794-ACN15 Adapter
with 1794 I/O Modules
FlexLogix Module
PanelView Terminal
88
Communication Networks
Chapter 5
Is used to
1756-CNB
1756-CNBR
1756-CN2
1756-CN2R
1756-CN2RXT
Is used to
Required or Optional
Required
89
Chapter 5
Communication Networks
Definition
Scheduled
(unique to a
ControlNet
network)
Unscheduled
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.
90
Communication Networks
Chapter 5
CompactLogix Controller
FLEX I/O Adapter
and Modules
1788-EN2DN
DeviceNet Network
Personal Computer
Sensor
Pushbutton
Cluster
PWR
PWR
STS
Motor
Starter
Input/output Devices
STS
PORT
MOD
PORT
NET
MOD A
NET B
NET A
NET B
PowerFlex AC
Drive
Indicator
Lights
Bar Code
Scanner
Is used to
1756-DNB
1788-EN2DN
1788-CN2DN
91
Chapter 5
Communication Networks
Is used to
Required or Optional
Required
92
Communication Networks
Chapter 5
Workstation
EtherNet/IP Network
ControlLogix
Controller
ControlLogix
Controller
DH+ Network
DH+ Network
PLC-5 Controller
RSView Station
PLC-5 Controller
RSView Station
93
Chapter 5
Communication Networks
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 21 - RIO Modules and Capabilities
RIO Module
Is used to
1756-RIO
1756-DHRIO
When a channel on the 1756-DHRIO module is configured for remote I/O, the
module acts as a scanner for a universal remote I/O network. The controller
communicates to the module to send and receive the I/O data on the universal
remote I/O network.
The 1756-RIO module can act as a scanner or adapter on a remote I/O network.
In addition to digital and block-transfer data, the 1756-RIO module transfers
analog and specialty data without message instructions.
Figure 14 - ControlLogix Universal Remote I/O Communication Example
ControlLogix Controller
1771-ASB and I/O Modules
94
Communication Networks
Chapter 5
95
Chapter 5
Communication Networks
Foundation Fieldbus
Communication
Is used to
1757-FFLD
1788-CN2FF
RSFieldbus Software
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
96
Communication Networks
HART Communication
Chapter 5
Is used to
ProSoft interface
MVI56-HART
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 16 - HART Protocol Example
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.
97
Chapter 5
Communication Networks
Notes:
98
Chapter
Topic
Page
100
101
101
101
102
104
DH-485 Protocol
105
ASCII Protocol
107
107
109
Modbus Support
111
99
Chapter 6
1756-L6x Controller
Serial Port
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 17 - ControlLogix DF1 Device Communication Example
DH+ Connection
EtherNet/IP
Network
RS-232 Connection
RS-232 Connection
RS-232 Connection
Modem
Modem
Modem
100
Chapter 6
When configuring the controller for serial communication, you first specify a
Serial Port mode (System or User), then a protocol.
Communication with
Serial Devices
This table describes the serial communication protocols for use with each mode.
Table 23 - 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.
101
101
102
DF1 Slave
104
DH-485
Communication with other DH-485 devices via a multi-master and token-passing network that enables
programming and peer-to-peer messaging.
105
ASCII
107
User
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.
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 24 - Default DF1 Point to Point Parameters
Parameter
Value
Baud Rate
19,200
Data Bits
Parity
None
Stop Bits
Control Line
No Handshake
101
Chapter 6
IMPORTANT
EtherNet/IP Network
RS-232
Modem
Power
OUT
L1
L2/N
Modem
Modem
Modem
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.
102
Chapter 6
103
Chapter 6
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 via RSLinx Classic and
Logix Designer applications running on a personal computer connected to
a local ControlLogix controller via DH-485, DH+, or Ethernet network.
Description
Station Address
Specifies the node address of the controller on the serial network. Select a number 1254 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.
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.
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.
104
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 the Logix Designer application. However, excessive traffic over a
DH-485 connection can adversely affect overall controller performance and lead
to timeouts and decreased performance of the 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
105
Chapter 6
ControlLogix Controller
ControlLogix Controller
1756-DH485 Module
1756-ENBT Module
EXTERNAL
TE
EXTERNAL
TE
DH-485 Network
T
TERM
A
PanelView Display
SLC 5/03 Controller
IMPORTANT
106
A DH-485 network consists of multiple cable segments. Limit the total length
of all the segments to 1219 m (4000 ft).
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.
2. From the Mode pull-down menu, choose the mode that corresponds to
your intended protocol.
Use this table as a reference.
For this protocol
DF1 Master
System
User
107
Chapter 6
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.
108
Chapter 6
5. If you are using the User mode protocol (ASCII), click the User Protocol
tab and specify the ASCII parameters.
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.
To configure and program the controller to broadcast messages via the serial port,
complete these procedures:
Configure Controller Serial Port Properties on page 110
Program the Message Instruction on page 111
For these procedure examples, ladder logic programming is used.
109
Chapter 6
110
Chapter 6
Use this table when specifying settings for the protocols listed.
Field
Station Address
Transmit Retries
N/A
ACK Timeout
50
N/A
N/A
N/A
3000
N/A
N/A
N/A
Polling Mode
N/A
N/A
EOT Suppression
N/A
Disable
N/A
Error Detection
BCC
BCC
BCC
Duplicate Detection
Enabled
Enabled
N/A
N/A
N/A
Modbus Support
When using structured text, broadcast over a serial port is set by typing
MSG(aMsg) and right-clicking an MSG to display the Message Configuration
dialog box.
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 within the Logix Designer application:
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.
111
Chapter 6
Notes:
112
Chapter
Topic
Connection Overview
113
114
116
Connection Overview
Page
117
113
Chapter 7
Controller_2
Produced Tag
Consumed Tag
Controller_3
Consumed Tag
Controller_4
Consumed 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.
114
If a consumed-tag connection fails, all of the other tags being consumed from
that remote controller stop receiving new data.
Chapter 7
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 27 - Produced and Consumed Tag Connections
This Type of Tag
Of This Module
Produced tag
number_of_configuredconsumers + 1
Controller
Consumed tag
EXAMPLE
Communication
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 28 - ControlLogix Modules and Available Connections
Module Type
Cat. No.
Available Connections
Controller
1756-L7x
500
1756-L6x
250
256
EtherNet/IP
1756-EN2F
1756-EN2T
1756-EN2TXT
1756-EN2TR
1756-ENBT
1756-EWEB
1756-CN2
1756-CN2R
1756-CN2RXT
128
1756-CNB
1756-CNBR
ControlNet
128
64
115
Chapter 7
Communication
Method
Connected Message
Message Can Be
Cached
N/A
Configurable
Yes
CIP
No
No
No
No
DH+
Yes
Yes
CIP generic
N/A
Optional (1)
Yes(2)
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.
Then
Repeatedly
Infrequently
TIP
116
Chapter 7
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 31 - Local Chassis Connections
Local Connection To
Device Quantity
Connections per
Device
1756-RIO remote I/O communication module (Connection count depends on module configuration
and could be as many as 10 per module.)
1
1
Total Connections
1
Total
117
Chapter 7
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 32 - Remote Connections
Remote Connection Type
Device Quantity
Connections per
Device
0
1
0
1
Produced tag
Each consumer
1
1
Consumed tag
1
0
Block-transfer message
1
Total
118
Total 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 the Logix Designer application
RediSTATION
Operator Interface
Series 9000
Photoeye
DeviceNet Network
1769-L35E CompactLogix
with 1769-SDN Module
EtherNet/IP Network
Device Quantity
Connections per
Device
Total Connections
Produced tag
Consumed by FlexLogix controller
1
1
1
1
1
1
Total 11
119
Chapter 7
Notes:
120
Chapter
I/O Modules
Topic
Selecting ControlLogix I/O Modules
121
122
124
Distributed I/O
128
131
131
Selecting ControlLogix
I/O Modules
Page
139
121
Chapter 8
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 34 - ControlLogix and ControlLogix- Chassis and Slots
Chassis
Slots
1756-A4
1756-A4LXT
1756-A5XT
1756-A7
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.
122
I/O Modules
Chapter 8
2. Select the I/O module you want to add and click OK.
Analog I/O
Configurable flowmeter
Digital I/O
High-speed counter
Low-speed counter
123
Chapter 8
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 Communication Networks on page 83.
Figure 22 - ControlLogix Controller and Remote I/O Example
ControlLogix Controller Chassis
ControlNet Network
124
I/O Modules
Chapter 8
125
Chapter 8
I/O Modules
7. Select the I/O module you want to add and click OK.
126
I/O Modules
Chapter 8
Analog I/O
Configurable flowmeter
Digital I/O
Low-speed counter
9. Add any other I/O modules you are using in the remote chassis.
10. Complete steps 19 until your remote I/O network and I/O modules are
configured.
127
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 I/O modules
1732 ArmorBlock 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 MaXum I/O modules
Distributed I/O
Logix5575
FORCE
RUN FORCE SD
OK
EtherNet/IP
POINT I/O
FLEX I/O
COMM
A
STATUS
REDUNDANT MEDIA
ADAPTER
1794-ACNR15
ControlNet
128
I/O Modules
Chapter 8
129
Chapter 8
I/O Modules
4. Add the communication adapter for the distributed I/O platform you are
using.
7. Select the I/O module you want to add and click OK.
130
I/O Modules
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.
131
Chapter 8
I/O Modules
For more information about using Message instructions, see the Logix5000
Controllers General Instruction Reference Manual, publication 1756-RM003.
With RSLogix 5000 software, version 15.02.00 or later, and Logix Designer
application, version 21.00.00 or later, you can add I/O and other devices to the
controller configuration while you are online and in Run mode.
The specific modules and devices you can add while online depends on the
version of the 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.
132
I/O Modules
Chapter 8
1756 controllers
1756 ControlNet modules
1756 DeviceNet bridge modules
1756 EtherNet/IP modules
1756 I/O and speciality modules
1756-DHRIO
IMPORTANT
133
Chapter 8
I/O Modules
PowerFlex 700S-200V-Q
PowerFlex 400-E
PowerFlex 700-200V-C
PowerFlex 700S-400V-C
PowerFlex 400P-E
PowerFlex 700-200V-E
PowerFlex 700S-400V-E
PowerFlex 40-E
PowerFlex 700-200V-Q
PowerFlex 700S-400V-Q
PowerFlex 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 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 753-CNETC
PowerFlex 700H-C
PowerFlex 753-NET-C
PowerFlex 700H-E
PowerFlex 753-NET-E
PowerFlex 700H-Q
PowerFlex 753-NET-Q
PowerFlex 755-CNETC
PowerFlex 755-EENET
PowerFlex 755-NET-C
PowerFlex 755-NET-E
PowerFlex 755-NET-Q
PowerFlex DC-200V-C
PowerFlex DC-200V-E
PowerFlex DC-200V-Q
PowerFlex DC-400V-C
PowerFlex DC-400V-E
PowerFlex DC-400V-Q
PowerFlex DC-600V-C
PowerFlex 7000-C
PowerFlex 700S-200V-C
PowerFlex DC-600V-E
PowerFlex 7000-E
134
PowerFlex 7000-Q
PowerFlex 700S-200V-E
PowerFlex DC-600V-Q
I/O Modules
Chapter 8
1305-BAXXA drives
1336E-IMPACTDrive-EN1 drive
1336F-PLUSIIDrive-EN1drive
1336R-REGENBrake-EN1 brake
1336S-PLUSDriveLG-EN1 drive
1336S-PLUSDriveSM-EN1 drive
1336T-FORCEDriveCNA-EN1 drive
1336T-FORCEDrivePLC-EN1 drive
1336T-FORCEDriveStd-EN1 drive
1397DigitalDCDrive-EN1 drive
150 SMC FLEX motor controller
150-SMCDialogPlus-EN1 motor controller
1757-FFLDC ControlNet Foundation Fieldbus device
2364F RGU-EN1 bus supply
48MS-SN1PF1-M2 Multivision Sensor
5XRF RFID interface device
While you can add a new digital I/O module to an existing rack-optimized
connection, you cannot add rack-optimized connections while online.
135
Chapter 8
I/O Modules
136
I/O Modules
Chapter 8
RPI = 2 ms
CPU %(2)
RPI = 4 ms
Avg.
API(3)
CPU %
Avg.
API(3)
CPU %
Avg.
API(3)
CPU %
1.50%
N/A
1.50%
N/A
1.50%
N/A
4.80%
2.0
3.70%
4.0
2.50%
7.00%
2.0
5.00%
4.0
9.00%
2.0
6.10%
11.20%
2.2
11.50%
(2)
RPI = 10 ms
(2)
RPI = 20 ms
(2)
RPI = 50 ms
(2)
RPI = 100 ms
Avg.
API(3)
CPU %
Avg.
API(3)
CPU %(2)
Avg.
API(3)
1.50%
N/A
1.50%
N/A
1.50%
N/A
10.0
2.30%
20.0
1.90%
50.0
1.70%
100.0
3.30%
10.0
2.70%
20.0
2.10%
50.0
1.90%
100.0
4.0
3.80%
10.0
3.00%
20.0
2.20%
50.0
2.00%
100.0
7.40%
4.0
4.40%
10.0
3.40%
20.0
2.40%
50.0
2.10%
100.0
3.3
8.70%
4.0
5.00%
10.0
3.70%
20.0
2.60%
50.0
2.20%
100.0
12.80%
3.3
9.70%
4.0
5.50%
10.0
4.00%
20.0
2.70%
50.0
2.30%
100.0
13.80%
3.4
10.80%
4.0
5.90%
10.0
4.30%
20.0
2.90%
50.0
2.30%
100.0
15.10%
3.4
11.90%
4.0
6.40%
10.0
4.50%
20.0
3.00%
50.0
2.50%
100.0
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
While you can add a new digital I/O module to an existing rackoptimized connection, you cannot add rack-optimized connections
while online.
137
Chapter 8
I/O Modules
138
I/O Modules
Chapter 8
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
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.
139
Chapter 8
I/O Modules
Notes:
140
Chapter
Topic
Motion Control Options
141
Motion Overview
142
142
143
Additional Resources
Page
144
141
Chapter 9
The configuration process varies, depending on your application and your drive
selection. The following are general steps to configure a motion application.
Motion Overview
Requirements
CIP Sync
SERCOS interface
Analog interface
142
Chapter 9
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 instructions
information status.
You can program using motion control instructions in these programming
languages:
Ladder Diagram (LD)
Structured Text (ST)
Sequential Function Chart (SFC)
Figure 26 - Motion Control Instruction
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
In this example, 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 hasnt been homed (My_Axis_X.AxisHomedStatus = off) then
the MAH instruction homes the axis.
143
Chapter 9
Additional Resources
144
Description
Chapter
10
Develop Applications
Topic
Elements of a Control Application
145
Tasks
146
Programs
149
Routines
152
Tags
153
Programming Languages
156
Add-On Instructions
157
158
159
Elements of a
Control Application
Page
162
145
Chapter 10
Develop Applications
Program 100
Program 1
Program
(local) Tags
Main Routine
Fault Routine
Other
Routines
Tasks
146
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 controllers processing time among the different operations in your
application:
The controller executes only one task at a time.
One task can interrupt anothers execution and take control.
In any given task, multiple programs may be used. However, only one
program executes at a time.
Develop Applications
Chapter 10
Configuration
Status
Watchdog
Program 100
Program 1
Program
(local) Tags
Main Routine
Fault Routine
Other
Routines
I/O Data
System-shared Data
Figure 29 - Tasks
Main Task
(continuous)
Task 2
(periodic)
147
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 30 - Configuring the Task Type
Task Execution
Description
Continuous
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
Event
An event task performs a function only when a specific event (trigger) occurs. The trigger for the event task can be the
following:
Module input data change of state
A consumed tag trigger
An EVENT instruction
An axis trigger
A motion event trigger
148
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 and event 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 31 - Configure Task Priority
Programs
149
Chapter 10
Develop Applications
Task 1
Configuration
Status
Watchdog
Program 100
Program 1
Main Routine
Program (local)
Tags
Fault Routine
Other Routines
I/O Data
Figure 33 - Programs
150
System-shared Data
Develop Applications
Chapter 10
151
Chapter 10
Develop Applications
Routines
Task 1
Configuration
Status
Watchdog
Program 100
Program 1
Program (local)
Tags
Main Routine
Fault Routine
Other Routines
I/O Data
Figure 36 - Routines
Routine
Routine
152
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 identifies the data and 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 37 - Tags Example
Controller Organizer Main Program Tags
Program Tags WindowMain Program Tags
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.
153
Chapter 10
Develop Applications
Extended Properties
The Extended Properties feature lets you define additional information, such as
limits, engineering units, or state identifiers, for various components within your
controller project.
Component
Extended Properties
Tag
Add-On Instructions
154
Develop Applications
Chapter 10
If an array tag is using indirect addressing to access limits in logic, the following
conditions apply:
If the array tag has limits configured, the extended properties are applied to
any array element that does not explicitly have that particular extended
property configured. For example, if the array tag MyArray has Max
configured to 100, then any element of the array that does not have Max
configured inherits the value of 100 when being used in logic. However, it
will not be visible to you that the value inherited from MyArray is
configured in the tag properties.
At least one array element must a limit configured for indirectly referenced
array logic to verify. For example, if MyArray[x].@Max is being used in
logic, at least one array element of MyArray[] must have Max extended
property configured if Max is not configured by MyArray.
Under the following circumstances a data type default value is used:
Array is accessed programmatically with indirect reference.
Array tag does not have the extended property configured.
A member of an array does not have the extended property configured.
For example, for an array of SINT type, when max limit is called in logic
for a member, the value 127 will be used.
If an array element is directly accessed, the element has to have the extended
property defined. If not verification will fail.
155
Chapter 10
Develop Applications
Programming Languages
Relay ladder
Structured text
156
Develop Applications
Chapter 10
With RSLogix 5000 software, version 16.03.00 or later, and Logix Designer
application, version 21.00.00 or later, 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 38 - 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.
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 dont accidentally overwrite another instruction of the same name.
Context views let you visualize an instructions logic for a specific instant, simplifying online troubleshooting of your Add-On
Instructions. Each instruction contains a revision, a change history, and an auto-generated help page.
When you create an instruction, you enter information for the description fields. This information then becomes custom Help.
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.
157
Chapter 10
Develop Applications
Instruction Toolbar
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 39 - GSV and SSV Instructions for Monitoring and Setting Attributes
158
Develop Applications
Chapter 10
When you add a GSV/SSV instruction to the program, the valid object classes,
object names, and attribute names for the instruction are shown. For the GSV
instruction, you can get values for all the available attributes. For the SSV
instruction, only the attributes you can set are shown.
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.
159
Chapter 10
Develop Applications
For more information about attributes available with the Module object, see the
Logix5000 Controllers General Instructions Reference Manual, publication
1756-RM003.
160
Develop Applications
Chapter 10
For more information about programming the Controller Fault Handler, see the
Major, Minor, and I/O Faults Programming Manual, publication 1756-PM014.
161
Chapter 10
Develop Applications
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, if the system overhead time slice is less than or equal to
50%, the duration 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.
162
Develop Applications
Chapter 10
163
Chapter 10
Develop Applications
164
Chapter
11
Topic
PhaseManager Overview
165
167
167
170
PhaseManager Overview
Page
170
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 39 - 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 instance 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, the application creates a tag for the equipment phase.
The tag uses the PHASE data type.
165
Chapter 11
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
166
Conveyor
Enable Axes
Chapter 11
Minimum System
Requirements
To enable PhaseManager support, you need either the Full or Professional edition
of the software, or the software with PhaseManager software (catalog number
9324-RLDPMENE).
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.
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.
Hold
Running
Holding
Held
Hold
Restart
Resetting
Acting
Restarting
Stop
Abort
Abort
Reset
Complete
Stopping
Aborting
Waiting
Reset
Stopped
Aborted
167
Chapter 11
With a state model, you define the behavior of your equipment during Acting
states.
Table 41 - Acting States in the PhaseManager State Model
State
Question to Ask
Resetting
Running
Holding
How does the equipment temporarily stop making product without making scrap?
Restarting
Stopping
Aborting
Start
Idle
Hold
Running
Holding
Held
Hold
Restart
Resetting
Restarting
Stop
Abort
Reset
Complete
Reset
168
Abort
Stopping
Aborting
Stopped
Aborted
Chapter 11
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.
169
Chapter 11
S88
PackML
ResettingIdle
StartingReady
RunningComplete
Producing
Subroutines or breakpoints
PausingPaused
Standby
HoldingHeld
HoldingHeld
HoldingHeld
Restarting
Restarting
None
StoppingStopped
StoppingStopped
StoppingStopped
AbortingAborted
Equipment Phase
Instructions
Idle
RunningComplete
AbortingAborted
AbortingAborted
The controller supports several equipment-phase relay ladder and structured text
instructions.
Table 44 - 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
PFL
PCLF
PXRQ
PRNP
PPD
PATT
PDET
POVR
Override a command.
For more information about instructions for use with equipment phases, see the
PhaseManager User Manual, publication LOGIX-UM001.
170
Chapter
12
Redundant Systems
Topic
ControlLogix Redundancy Overview
171
System Requirements
173
System Considerations
174
175
176
176
ControlLogix Redundancy
Overview
Page
177
171
Chapter 12
Redundant Systems
Workstation
HMI
Ethernet
Ethernet
Switch
Switch
Primary
Secondary
EtherNet/IP
Diagnostic
Analog Input
ST
AT
ST
AT
Diagnostic
Analog Output
ST
AT
ST
AT
Relay Module
ControlNet
Diagnostic
Analog Output
DC OUTPUT
ST
AT
ST
AT
Digital Ouput
ControlNet Scanner
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
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.
172
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 45 - System Requirements
Quantity
Item
Notes
ControlLogix chassis
ControlLogix controller
ControlLogix ControlNet
communication module
ControlLogix EtherNet/IP
communication modules
Redundancy module
173
Chapter 12
Redundant Systems
System Considerations
Consideration
ControlLogix controller
Communication modules
I/O modules
The 1756-PA75R and 1756-PB75R redundant power supplies provide reliable chassis
power.
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.
174
Redundant Systems
Chapter 12
Enhanced
System(1)
Standard
System
175
Chapter 12
Redundant Systems
ControlNet Considerations
in Redundant Systems
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.
EtherNet/IP Considerations
in Redundant Systems
You can have as many as seven EtherNet/IP modules in the redundant chassis.
In a redundant system, you can use EtherNet/IP for HMI communication or
inter-controller messaging. 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.
176
Redundant Systems
Chapter 12
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 1ms 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.
177
Chapter 12
Redundant Systems
Notes:
178
Chapter
13
SIL 2 Certification
Topic
Introduction to SIL
179
179
Introduction to SIL
Page
180
179
Chapter 13
SIL 2 Certification
Nonredundant controller
Nonredundant communication modules
Nonredundant remote I/O
Redundant controllers
Redundant communication modules
Nonredundant remote I/O
IMPORTANT
180
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 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.
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 47 - Fail-safe ControlLogix Configuration
Overall Safety Loop
SIL2-certified ControlLogix Safety Loop
Controller Chassis
Sensor
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
181
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 48 - Typical SIL Loop with Controller Chassis Redundancy
Studio 5000 Environment
For SIL applications, a programming
terminal is not normally connected.
HMI
For Diagnostics and Visualization
(read-only access to controllers in the safety loop)
Plant-wide Ethernet/Serial
Overall Safety Loop
Primary Chassis
Sensor
R
M
I/O
CN
2
Actuator
ControlNet Network
Secondary Chassis
EN CN CN
2T 2 2
R
M
To other
safety-related
ControlLogix and
remote I/O
chassis
To nonsafety related systems outside the ControlLogix portion of the SIL2-certified loop.
ControlNet Network
IMPORTANT
182
SIL 2 Certification
Chapter 13
Figure 48 on page 182 shows a typical SIL loop that uses redundancy, including
the following:
The overall safety loop
The ControlLogix portion of the overall safety loop
How other devices (for example, HMI) connect to the loop, while
operating outside the loop
Fault-tolerant Configuration
The most recently-certified ControlLogix SIL2 configuration is the
fault-tolerant configuration. The fault-tolerant configuration of the
ControlLogix system uses fully-redundant controllers, communication modules,
and remote I/O.
Figure 49 - Fault-tolerant Configuration
SIL2-certified ControlLogix Safety Loop
Secondary Chassis
Primary Chassis
PRI
PRI
COM
DC OUTPUT
DC INTPUT
ANALOG INTPUT
DC OUTPUT
ANALOG INTPUT
DC INTPUT
DC OUTPUT
CAL
CAL
ST 0 1 2 3 4 5 6 7 O
ST 0 1 2 3 4 5 6 7 O
ST 8 9 10 11121314 15 K
ST 0 1 2 3 4 5 6 7 O
ST 8 9 10 11121314 15 K
DC INTPUT
ST 0 1 2 3 4 5 6 7 O
ST 8 9 10 11121314 15 K
DIAGNOSTIC
OK
OK
DIAGNOSTIC
Digital Input
Termination Board
Field Device
DC OUTPUT
ANALOG INTPUT
CAL
ST 0 1 2 3 4 5 6 7 O
ST 8 9 10 11121314 15 K
ST 0 1 2 3 4 5 6 7 O
ST 8 9 10 11121314 15 K
OK
OK
DC INTPUT
ST 0 1 2 3 4 5 6 7 O
ST 8 9 10 11121314 15 K
DIAGNOSTIC
DIAGNOSTIC
Analog Input
Termination
Board
ANALOG INTPUT
CAL
ST 0 1 2 3 4 5 6 7 O
ST 8 9 10 11121314 15 K
DIAGNOSTIC
OK
I/O Chassis B
I/O Chassis A
ST 8 9 10 11121314 15 K
COM
OK
DIAGNOSTIC
DIAGNOSTIC
DIAGNOSTIC
Digital Output
Termination Board
Field Device
Field Device
183
Chapter 13
SIL 2 Certification
184
Appendix
Status Indicators
Topic
1756-L7x Controller Status Display and Indicators
185
185
193
Page
194
The 1756-L7x controllers have four status indicators and one four-character
scrolling status display.
Figure 50 - 1756-L7x Status Display and Indicators
Logix557x
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 controllers firmware revision, ESM status, project status, and major
faults.
185
Appendix A
Status Indicators
Interpretation
No message is indicated
TEST
PASS
SAVE
A project is being saved to the SD card. You can also view the SD Indicator (see page 193) 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 193) 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 193) for additional status
information.
If you do not want the firmware to update upon powerup, change the controllers Load Image property.
CHRG
1756-L7x/X
Rev XX.xxx
No Project
Project Name
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
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
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.
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.
ESM Charging
186
Status Indicators
Appendix A
Interpretation
Flash in Progress
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
Fault Messages
If the controller is faulted, these messages may be indicated on the status display.
Table 50 - Fault Messages
Message
Interpretation
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.
An I/O fault has occurred on a module in a remote chassis. The name of the faulted module 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 modules parent name is indicated because no module name is configured in
the I/O Configuration tree of Logix Designer application. 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.
187
Appendix A
Status Indicators
Message
60
Non-recoverable
61
62
16
20
Chassis Failure
21
23
Connection Failure
16
Unknown Instruction
20
21
31
34
Timer Failure
42
82
83
84
Stack Overflow
89
90
Invalid Instruction
91
Invalid Context
92
Invalid Action
990
User-defined
991
992
993
994
995
996
997
998
188
Code
999
Status Indicators
Appendix A
Code
Message
40
Save Failure
41
42
43
11
11
11
11
11
11
11
11
11
11
10
Motor Fault
11
11
11
12
11
13
11
14
11
15
11
16
11
32
11
33
18
18
18
18
18
18
18
18
18
18
10
18
128
189
Appendix A
Status Indicators
Message
#0001
Connection Failure
#0002
Insufficient Resource
#0003
Invalid Value
#0004
IOI Syntax
#0005
Destination Unknown
#0006
#0007
Connection Lost
#0008
Service Unsupported
#0009
#000A
#000B
#000C
#000D
#000E
#000F
Permission Denied
#0010
#0011
#0012
Fragment Primitive
#0013
#0014
#0015
#0100
Connection In Use
#0103
Ownership Conflict
#0107
190
#0106
Status Indicators
Appendix A
Message
#0108
#0109
#0110
#0111
#0113
Out of Connections
#0114
Wrong Module
#0115
#0116
Wrong Revision
#0117
#0118
#0119
#011A
#0203
Connection Timeout
#0204
#0205
Invalid Parameter
#0206
#0301
No Buffer Memory
#0302
#0303
No Bridge Available
#0304
#0305
Signature Mismatch
#0306
#0311
Invalid Port
#0312
#0315
#0317
#0318
#0319
#031E
No Available Resources
#031F
No Available Resources
#0800
#0801
#0814
#FD01
#FD02
No Error Code
#FD03
#FD04
No CST Master
#FD05
#FD06
191
Appendix A
Status Indicators
#FD08
#FD09
#FD0A
#FD1F
Safety I/O
#FD20
No Safety Task
#FE01
#FE02
#FE03
#FE04
#FE05
#FE06
#FE07
#FE08
#FE09
#FE0A
#FE0B
#FE0C
#FE0D
#FE0E
#FE0F
#FE10
#FE11
#FE12
#FE13
#FE14
#FE22
#FE23
#FF00
No Connection Instance
#FF01
#FF04
Invalid State
#FF08
Invalid Path
#FF0B
Invalid Config
#FF0E
192
Message
No Connection Allowed
Status Indicators
1756-L7x Controller
Status Indicators
Appendix A
The status indicators are below the status display on the controller. They indicate
the state of the controller as described in these tables.
RUN Indicator
To change the controller mode indicated by the RUN indicator, either use the
mode switch on the front of the controller or use the Controller Status menu in
the Logix Designer application.
Table 53 - RUN Indicator
State
Description
Off
Steady green
FORCE Indicator
The Force indicator shows if I/O forces are enabled on the controller.
Table 54 - FORCE Indicator
State
Description
Off
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 55 - SD Indicator
State
Description
Off
Flashing green
Solid green
Flashing red
Solid red
193
Appendix A
Status Indicators
OK Indicator
The OK indicator shows the state of the controller.
Table 56 - OK Indicator
State
Off
Flashing red
Solid red
Solid green
Description
The 1756-L6x controllers have status indicators on the front of the controller at
show the state of the controller.
Status Indicators
RUN Indicator
To change the controller mode indicated by the RUN indicator, either use the
mode switch on the front of the controller or use the Controller Status menu in
the Logix Designer application.
Table 57 - RUN Indicator
State
Off
Steady green
194
Description
Status Indicators
Appendix A
I/O Indicator
The I/O indicator shows the status of I/O modules in the controllers project.
Table 58 - I/O Indicator
State
Description
Off
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 the Logix Designer application to check the I/O configuration of the
controller.
Flashing red
FORCE Indicator
The FORCE indicator shows if I/O forces are active or enabled.
Table 59 - FORCE Indicator
State
Description
Off
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.
RS232 Indicator
The RS232 indicator shows if the serial port is in use.
Table 60 - RS232 Status Indicator
State
Description
Off
Flashing green
195
Appendix A
Status Indicators
BAT Indicator
The BAT indicator shows the charge of the battery and if the program is being
saved.
Table 61 - BAT Indicator
State
Controller
Series
Description
Off
N/A
Solid green
N/A
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 62 - OK Indicator
State
Off
Flashing red
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
Flashing green
196
Description
Appendix
Topic
Electronic Keying
197
Exact Match
198
Compatible Keying
199
Disabled Keying
Electronic Keying
Page
201
197
Appendix B
Description
Vendor
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 modules specific firmware revision. Minor Revisions
typically do not impact data compatibility but may indicate performance or behavior
improvement.
You can find revision information on the General tab of a modules Properties
dialog box.
Figure 51 - General Tab
IMPORTANT
Exact Match
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
198
Appendix B
Firmware Update for the module via the Firmware Supervisor feature from a
Logix5000 controller.
EXAMPLE
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
199
Appendix B
Communication is prevented.
Physical Module
Vendor = Allen-Bradley
Product Type = Digital Input Module
Catalog Number = 1756-IB16D
Major Revision = 3
Minor Revision = 2
200
EXAMPLE
Appendix B
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
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.
201
Appendix B
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
Communication is prevented.
Physical Module
Vendor = Allen-Bradley
Product Type = Analog Input Module
Catalog Number = 1756-IF16
Major Revision = 3
Minor Revision = 2
202
EXAMPLE
Appendix B
Communication is allowed.
Physical Module
Vendor = Allen-Bradley
Product Type = Digital Input Module
Catalog Number = 1756-IB16
Major Revision = 3
Minor Revision = 2
IMPORTANT
203
Appendix B
Notes:
204
Appendix
History of Changes
Topic
Page
206
206
206
207
207
207
207
207
208
1756-UM001D-EN-P
208
208
208
This appendix summarizes the revisions to 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.
205
Appendix C
History of Changes
1756-UM001M-EN-P,
February 2012
Change
Added USB cable text.
Added energy storage module information relating to safety and extreme temperature controllers.
Added parts not included with the 1756-L6x controller.
Added double data rate (DDR) communication reference for 1756-L7x controller.
Added 1756-L71, 1756-L73XT controllers and chassis and changed version information for 1756-L72, 1756-L73,
1756-L74, and 1756-L75 controllers.
Added upgrade restrictions.
Added information about mode switch operation on the controller.
Controller mode can be changed in the Logix Designer application.
Changed 1756-ESMNSE joules from 20040.
Added 1756-L71 information to ControlLogix controller features.
Added 1756-L71 and 1756-L73XT memory options.
Added double data rate (DDR) communication information.
Added 1756-A7XT chassis information.
Added information about the flashing red OK status indicator for nonrecoverable faults.
1756-UM001L-EN-P,
November 2011
Change
Added 1756-ESMNSE stored energy depletion rate.
Added how to uninstall the ESM.
1756-UM001K-EN-P,
May 2011
Change
Added information about new 1756-L72 and 1756-L74 controllers.
Added series A information 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.
206
History of Changes
Appendix C
Change
Added 1756-L6x and 1756-L7x installation information.
Added information to identify and describe common start-up tasks completed with ControlLogix controllers.
Updated the ControlLogix example configurations, system design information, controller features descriptions to
include the 1756-L7x controllers, available memory options to include the 1756-L7x information, and ControlLogix
controller CPU resources.
Reformatted information for clarity on communication networks and updated the additional resources.
Placed and reformatted information specific to the use of serial communication.
Reformatted information about controller connections.
Added a list of modules and devices that can be added while online with the Logix Designer application, 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.
Updated motion information and references with regard to the 1756-L60M03SE combination controller and
reformatted and added graphics.
Made redundancy information corrections and updated information about SIL2 certification and configurations.
Added 1756-L7x status display and status indicator information.
1756-UM001I-EN-P,
January 2007
Change
Added new information about broadcasting over serial ports.
Updated redundancy information.
Updated battery information.
Added new and updated EtherNet/IP motion information.
1756-UM001H-EN-P,
July 2008
Change
Added new information about the 1756-L65 controller .
Added new information about the 1784-CF128 CompactFlash card.
1756-UM001G-EN-P,
January 2007
Change
Added information about the 1756-L64 ControlLogix controller.
Added information about Add-On Instructions.
Updated the Select a System Overhead Percentage section.
Updated the Add Your Axes section.
Updated the Obtain Axis Information section.
1756-UM001F-EN-P,
May 2005
No changes documented.
207
Appendix C
History of Changes
1756-UM001E-EN-P,
August 2002
Change
Added information about the battery life of the 1756-BA1 battery when you use it in a ControlLogix5563 controller.
Added information about the 1756-BATM ControlLogix battery module.
1756-UM001D-EN-P
1756-UM001C-EN-P,
June 2001
Change
Added the Configure an EtherNet/IP Module section.
Added the Download and Go Online over an EtherNet/IP Network section.
Added the Communicate with 1756 I/O over an EtherNet/IP Network section.
Added the Communicate with 1794 I/O over an EtherNet/IP Network section.
Added the Communicate with Another Controller over an EtherNet/IP Network section.
Added the Communicate with a PanelView Terminal over a EtherNet/IP Network section.
Added the Communicate with an RSView32 Project over an EtherNet/IP Network section.
Added the Add I/O Modules section.
Added the Create Aliases section.
Added the Schedule the ControlNet Network section.
Added the Communicate with Another Controller over a DH+ Network section.
Added the Route PLC-5 or SLC 500 Messages From a DH+ Network section.
Added the Estimate Execution Time section.
Added the Estimate Memory Use section.
Added the Determine When Data Is Updated section.
1756-UM001B-EN-P,
November 2000
Change
Added the Configure a1756-ENET Module section.
Added the Download and Go Online over an Ethernet Network section.
Added the Communicate with 1756 I/O over an Ethernet Network section.
Added the Communicate with Another Controller over an Ethernet Network section.
Added the Communicate with Another Controller over a DH-485 Network section.
Added the Estimate Battery Life section.
Added the Estimate Execution Time (updated numbers) section.
208
Index
Numerics
1747-KY controller key
key 17
1756-BA1
check level 72
controller compatiblity 72
controller parts 31
storage 76
1756-BA2
check level 72
controller compatibility 72
controller parts 31
estimate life 74
life after warning 75
storage 76
1756-BATA
controller compatibility 72
1756-BATM
battery 74
controller compatibility 72
controller parts 31
1756-CN2
uses 89
1756-CN2R
uses 89
1756-CN2RXT
uses 89
1756-CNB
uses 89
1756-CNBR
uses 89
1756-CP3
controller parts 31
1756-DHRIO
communication via 93
uses
remote I/O 94
1756-EN2F
uses 85
1756-EN2T
uses 85
1756-EN2TR
uses 85
1756-EN2TXT
uses 85
1756-EN3TR
uses 85
1756-ENBT
uses 85
1756-ESMCAP
controller parts 17
ESM 26
1756-ESMCAPXT
ESM 26
1756-ESMNRM 26
controller parts 18
ESM 26
1756-ESMNRMXT
ESM 26
1756-ESMNSE
controller parts 18
ESM 26
1756-ESMNSEXT
ESM 26
1756-EWEB
uses 85
1756-IF8H
uses 97
1756-L6x
add
while online 133
BAT indicator 196
CPU 82
FORCE indicator 195
I/O indicator 195
installation
battery, install 36
battery, uninstall 36
CompactFlash card, removal 32
into chassis 39
memory options 82
OK indicator 196
RS232
indicator 195
port 100
RUN indicator 194
serial driver 48
serial port 47
1756-L7x
add
while online 133
CPU 82
double data rate (DDR) 43, 87
FORCE indicator 193
installation
ESM, uninstall 25
into chassis 19
key 20
SD card, install 21
SD card, removal 23
memory options 82
OK indicator 194
parts
included 17
RUN indicator 193
SD indicator 193
status display 185
status indicators 193, 194
USB driver 45
1756-L7xXT
extreme temperature controller 26
1756-N2 122
1756-N2XT 122
1756-OF8H
uses 97
1756-RIO
uses 94
1784-SD1 18
load from 67
SD card 17
store to 64
209
Index
1784-SD2
controller parts 18
load from 67
store to 64
A
add
distributed I/O 129
local I/O 123
remote I/O 125
Add-On Instructions
in project 157
application
elements 145
networks and 83
ASCII 107
attributes
keying 198
AutoFlash
upgrade 54
axis
obtain information 142
B
BAT indicator
1756-L6x 196
battery
1756-BA2
estimate 74
life after warning 75
catalog number 31
check if low 72
compatibility 72
install 36
life and use 74
replacement 72
schedule 72
storage 76
uninstall 36
broadcast
messages 109
C
cache
message options 116
messages
about 116
calculate
connection use 117
change
equipment phase 169
chassis
ControlLogix
list 122
insert controller 19, 39
210
communication
Data Highway Plus 92, 93
DH-485 network 105
Foundation Fieldbus 96
HART 97
network options 81
path
set 56
universal remote I/O 94
CompactFlash card
installation 32
load from 67
other tasks 69
removal 32
store to 64
comparision
PhaseManager 170
compatibility
battery 72
compatible keying 199
configurations
fail-safe 181
fault-tolerant 183
high-availability 182
configure
motion 142
serial driver 48
system overhead time slice 163
connect
DH-485 network 105
connection
calculate use 117
DeviceNet
network 92
EtherNet/IP 86
network 86
example 119
local 117
message, required 116
produce/consume
data and 114
required 115
remote 118
scheduled
ControlNet 90
unscheduled
ControlNet 90
considerations
redundancy 174
consume
data 114
continuous task 148
ControlFLASH utility 51
controller
1756-L6x
battery and 72
battery, install 36
battery, uninstall 36
CompactFlash card, installation 32
CompactFlash card, removal 32
insert into chassis 39
serial driver 48
Index
1756-L7x
battery and 72
communication options 81
ESM, uninstall 25
insert into chassis 19
key, insert 20
SD card, install 21
SD card, removal 23
status display 185
status indicators 193, 194
USB driver 45
battery
check 72
communication path
set 56
connections
calculate 117
CPU resources 82
design system with 80
download 58
estimate
battery life 74
firmware 50
obtain 51
go online 57
memory options 82
monitor
connections 159
parts included 18
program 149
routine 152
tags 153
tasks 146
upload 59
controller parts
1756-BA1 31
1756-BA2 31
1756-BATM 31
1756-CP3 31
1756-ESMCAP 17
1756-ESMNRM 18
1756-ESMNSE 18
1784-SD2 18
battery 31
energy storage module
catalog number 17, 18
catalog number ESM. See energy storage module.
SAMTEC RSP-119350 18
serial cable 31
USB cable 18
ControlLogix
chassis
list 122
controller
add while online 133
design system 80
I/O
remote 124
selection 121
modules
online addition 133
redundancy
about 171
remote I/O
local 122
slot filler 122
ControlLogix-XT
chassis
list 122
ControlNet
module capability 89
module features 89
module list 89
network 87
redundancy system and 176
scheduled connection
scheduled connection 90
unscheduled connection
unscheduled connection 90
CPU
controller 82
D
Data Highway Plus network 92
design
system 80
develop
applications 145
motion applications 141
DeviceNet
connection use 92
module
memory 92
network 90
software for 92
devices
add while online 135
DF1
master 101
point to point 101
radio modem 102
slave 104
DH-485 network
example configuration 105
overview 105
disabled keying 201
display
1756-L7x 185
distributed
I/O 128
add 129
double data rate (DDR)
1756-L7x 43, 87
download
project 58
drive
add while online 134
E
electronic keying
about 197
electrostatic discharge 19, 39
211
Index
elements
control application 145
enhanced redundancy. See redundancy.
equipment phase
instructions 170
error
script file 53
ESM 26
1756-ESMCAP 26
1756-ESMCAPXT 26
1756-ESMNRMXT 26
1756-ESMNSE 26
1756-ESMNSEXT 26
uninstall 25
EtherNet/IP
add while online 138
connections 86
module features 84
module list 85
network 84
redundancy system and 176
software for 86
event task 148
exact match keying 198
example configuration
DH-485 network 105
extreme temperature controller
1756-L7xXT 26
F
fail-safe configruation
about 181
fault code
use GSV to get 160
fault handler
execute at I/O fault 161
fault messages 187
I/O 190
Major Recoverable Fault 188
fault-tolerant configruation
about 183
features 81
controller
communication 81
programming 81
filler slot
slot filler 122
firmware
controller 50
determine 50
obtain 51
security certificate, error 53
upgrade
AutoFlash, use 54
FORCE indicator
1756-L6x 195
1756-L7x 193
Foundation Fieldbus 96
212
G
general status messages 186
GSV
fault code 160
monitor
connection 160
H
HART. See Highway Addressable Remote
Transducer.
high-availability configruation
about 182
Highway Addressable Remote Transducer 97
hold-up time
ESM WallClockTime 71
I
I/O
connection error 161
ControlLogix
remote 124
selection 121
determine data update 139
distributed 128
fault codes 190
reconfigure 131
remote 124
I/O configuration
add
distributed I/O 129
local I/O 123
remote I/O 125
while online 132
I/O indicator
1756-L6x 195
indicator 193
BAT
1756-L6x 196
FORCE
1756-L6x 195
1756-L7x 193
I/O
1756-L6x 195
OK
1756-L6x 196
1756-L7x 194
RS232
1756-L6x 195
RUN
1756-L7x 193
SD
1756-L7x 193
install
1756-L6x
battery 36
CompactFlash card 32
insert into chassis 39
1756-L7x
insert into chassis 19
key, insert 20
Index
SD card 21
battery 36
CompactFlash card 32
SD card 21
instruction
ASCII 107
motion 143
IP address swapping 176
module
ControlNet 89
EtherNet/IP 84, 85
motion
about 142
application 141
instructions 143
program 143
MVI56-HART
uses 97
key
1747-KY controller key 17
insert 20
keying
about 197
attributes 198
compatible 199
disabled 201
exact match 198
L
load
from memory card 67
local
connection 117
I/O
add 123
remote I/O 122
Logix Designer application
Add-On Instructions 157
program 149
rebranding of RSLogix 5000 11
routine 152
tags 153
tasks 146
M
Major Recoverable Fault
messages 188
memory
DeviceNet module 92
options 82
memory card
load from 67
other tasks 69
store to 64
message
about 116
broadcast over serial 109
cache 116
determine if 116
fault 187
reconfigure I/O module 131
status display 186
Modbus network 111
mode
serial port 101
N
network
application and 83
controller options 81
ControlNet 87
ControlNet redundancy 176
Data Highway Plus 93
Data Highway Plus DH+. See Data Highway
Plus.
DeviceNet 90
EtherNet/IP 84
EtherNet/IP redundancy 176
Foundation Fieldbus 96
HART 97
universal remote I/O 94
nonvolatile memory 82
O
obtain
axis information 142
firmware 51
OK indicator
1756-L6x 196
1756-L7x 194
online
add
EtherNet/IP 138
to I/O configuration 132
go 57
options
memory 82
P
path
set
communication 56
periodic task 148
PhaseManager
about 165
change states 169
comparison 170
equipment phase instructions 170
state model 167
system requirements 167
terminology 165
transition 168
port
communication 81
213
Index
PowerFlex
add while online 134
prevent electrostatic discharge 19, 39
priority
task 149
produce
data 114
produce/consume
connections
required 114
data 114
program
in project 149
scheduled 151
system overhead time slice 162
unscheduled 151
programming languages 156
project
Add-On Instructions 157
download 58
elements 145
go online 57
program 149
routine 152
tags 153
tasks 146
upload 59
protocol
ASCII 107
DF1
master 101
point to point 101
radio modem 102
slave 104
Modbus network 111
serial port 101
R
receive
messages 116
redundancy
about 171
build system 175
considerations 174
ControlNet network 176
EtherNet/IP network 176
scan time 177
system requirements 173
remote
connection 118
I/O 124
remote I/O
add 125
ControlLogix
local 122
universal 94
remove
1756-L6x
CompactFlash card 32
214
1756-L7x
SD card 23
CompactFlash card 32
SD card 23
replace
battery
schedule 72
required
connections
messages 115, 116
requirement
PhaseManager
system 167
redundancy 173
RIO. See universal remote I/O
routine
in project 152
RS232
DF1 device driver 48
indicator
1756-L6x 195
RSWho
set
path 56
RUN indicator
1756-L7x 193
S
safety integration level, see SIL 2 179
SAMTEC RSP-119350
controller parts 18
scan time
redundancy and 177
scheduled
program 151
script file
error 53
SD card
1784-SD1 17
install 21
load from 67
other tasks 69
removal 23
store to 64
SD indicator
1756-L7x 193
security certificate
error 53
selection
I/O 121
send
messages 116
serial
broadcast 109
cable
catalog number 31
DH-485 network configuration 105
driver 48
Modbus network 111
Index
serial port
1756-L6x 47
ASCII 107
DF1
master 101
point to point 101
radio modem 102
slave 104
mode 101
protocols 101
service communication 162
set up
serial driver 48
USB driver 45
SIL 2 certification
overview 179
software
DeviceNet and 92
EtherNet/IP and 86
required
USB 44
specifications 14
standard redundancy. See redundancy.
state model
overview 167
status
battery 72
display
1756-L7x 185
fault messages 187
indicators
1756-L7x 193, 194
messages
display 186
monitor
connections 159
storage
battery 76
store
to memory card 64
Studio 5000 environment 11
swapping IP address 176
system 81
system overhead time slice 162
configure 163
system requirements
PhaseManager 167
redundancy 173
transistion
PhaseManager 168
type
USB 44
U
uninstall
1756-L6x
battery 36
1756-L7x
ESM 25
battery 36
ESM 25
universal remote I/O 94
communicate via 95
unscheduled
program 151
update
determine frequency 139
upgrade
firmware
AutoFlash, use 54
upload
project 59
USB
cable
catalog number 18
driver 45
software required 44
type 44
T
tag
consume 114
in project 153
produce 114
task
continuous 148
event 148
in project 146
periodic 148
priority 149
time slice 162
215
Index
Notes:
216
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
Contact your distributor. You must provide a Customer Support case number (call the phone number above to obtain one) to your
distributor to complete the return process.
Please contact your local Rockwell Automation representative for the return procedure.
Documentation Feedback
Your comments will help us serve your documentation needs better. If you have any suggestions on how to improve this
document, complete this form, publication RA-DU002, available at http://www.rockwellautomation.com/literature/.
Rockwell Otomasyon Ticaret A.., Kar Plaza Merkezi E Blok Kat:6 34752 erenky, stanbul, Tel: +90 (216) 5698400
Copyright 2012 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.