AB Compact Logix User Manual
AB Compact Logix User Manual
In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the
use or application of this equipment.
The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and
requirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or
liability for actual use based on the examples and diagrams.
No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or
software described in this manual.
Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation,
Inc., is prohibited.
Throughout this manual, when necessary, we use notes to make you aware of safety considerations.
WARNING: Identifies information about practices or circumstances that can cause an explosion in a hazardous environment,
which may lead to personal injury or death, property damage, or economic loss.
ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or death, property
damage, or economic loss. Attentions help you identify a hazard, avoid a hazard, and recognize the consequence.
SHOCK HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that dangerous
voltage may be present.
BURN HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that surfaces may
reach dangerous temperatures.
IMPORTANT Identifies information that is critical for successful application and understanding of the product.
Allen-Bradley, CompactLogix, Rockwell Software, Rockwell Automation, and TechConnect are trademarks of Rockwell Automation, Inc.
Trademarks not belonging to Rockwell Automation are property of their respective companies.
Summary of Changes
This manual contains new and updated information. Changes throughout this
revision are marked by change bars, as shown to the right of this paragraph.
Topic Page
Updated embedded input point wiring diagrams on a CompactLogix™ 5370 L1 147
controller
Updated embedded output point wiring diagrams on a CompactLogix 5370 L1 150…151
controller
Use the Event Task 161
Addition of Develop Applications chapter 267
Addition of History of Changes appendix 315
Notes:
Chapter 1
Install the CompactLogix 5370 Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
L1 Controller CompactLogix 5370 L1 Controller Parts . . . . . . . . . . . . . . . . . . . . . . . 19
Installation Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Install the Secure Digital Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Install the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Mount the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Ground the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Install the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Connect Power to the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Connect to the Controller via a USB Cable . . . . . . . . . . . . . . . . . . . . . . . . 31
Connect the Controller to an EtherNet/IP Network. . . . . . . . . . . . . . . . 32
Connecting to Different EtherNet/IP
Network Topologies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Chapter 2
Install the CompactLogix 5370 Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
L2 Controller CompactLogix 5370 L2 Controller Parts . . . . . . . . . . . . . . . . . . . . . . . 38
Installation Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Install the Secure Digital Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Install the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Mount the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Ground the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Install the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Connect Power to the Control System . . . . . . . . . . . . . . . . . . . . . . . . . 48
Connect to the Controller via a USB Cable . . . . . . . . . . . . . . . . . . . . . . . . 52
Connect the Controller to an EtherNet/IP Network. . . . . . . . . . . . . . . . 53
Connecting to Different EtherNet/IP
Network Topologies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Chapter 3
Install the CompactLogix 5370 Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
L3 Controller CompactLogix 5370 L3 Controller Parts . . . . . . . . . . . . . . . . . . . . . . . 60
Installation Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Install the Secure Digital Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Install the System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Assemble the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Mount the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Ground the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Connect Power to the Control System . . . . . . . . . . . . . . . . . . . . . . . . . 71
Connect to the Controller via a USB Cable. . . . . . . . . . . . . . . . . . . . . . . . . 72
Connect the Controller to an EtherNet/IP Network . . . . . . . . . . . . . . . . 73
Connecting to Different EtherNet/IP
Network Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Chapter 4
Complete Software Tasks Required Set a Controller’s IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
at CompactLogix 5370 Controller Use the BOOTP Server to Set the Controller’s IP Address . . . . . . . 78
Use the DHCP Server to Set the Controller’s IP Address . . . . . . . . 82
Installation
Use RSLinx Classic Software to Set the Controller’s IP Address . . 83
Use Logix Designer Application to Set the C
ontroller’s IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Use the SD Card to Set the Controller’s IP Address . . . . . . . . . . . . . 88
Change a Controller’s IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Change the Network IP Address with RSLinx
Classic Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Change the Network IP Address with Logix
Designer Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Change the Network IP Address with an SD Card . . . . . . . . . . . . . . 92
Load the Controller Firmware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Use the ControlFLASH Utility to Load Firmware . . . . . . . . . . . . . . 95
Use AutoFlash to Load Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Use the Secure Digital Card to Load Firmware . . . . . . . . . . . . . . . . . 102
Select the Controller’s Operating Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Chapter 5
CompactLogix 5370 CompactLogix 5370 Control System Components . . . . . . . . . . . . . . . . 108
Controllers Overview Controller Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Support for Integrated Motion over an EtherNet/IP Network . . 110
Example System Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
EtherNet/IP Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
DeviceNet Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Chapter 6
Communicate over Networks EtherNet/IP Network Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Available Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
EtherNet/IP Network Functionality on
CompactLogix 5370 Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Nodes on an EtherNet/IP Network. . . . . . . . . . . . . . . . . . . . . . . . . . . 118
EtherNet/IP Network Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Socket Interface with CompactLogix 5370 Controllers . . . . . . . . . 126
MSG Source Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Quality of Service (QoS) and I/O Module Connections . . . . . . . . 130
DeviceNet Network Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Available Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Compact I/O 1769-SDN DeviceNet Scanner Module. . . . . . . . . . 133
Power Supply Distance Rating. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Current Capacity in CompactLogix 5370 L3 Control Systems . . 138
Chapter 7
Use I/O Modules with Select I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
CompactLogix 5370 L1 Controllers Connect Power to I/O Devices Connected to a
CompactLogix 5730 L1 Control System . . . . . . . . . . . . . . . . . . . . . . 140
Embedded I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Local Expansion Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Distributed I/O Modules over an EtherNet/IP Network . . . . . . . 155
Validate I/O Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Set the Number of Local Expansion Modules . . . . . . . . . . . . . . . . . . 156
Empty Slots and Removal and Insertion Under
Power Situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Estimate Requested Packet Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Module Faults Related to RPI Estimates. . . . . . . . . . . . . . . . . . . . . . . 159
Calculate System Power Consumption . . . . . . . . . . . . . . . . . . . . . . . . 160
Physical Placement of I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Use the Event Task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Configure I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Common Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 166
I/O Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Chapter 8
Use I/O Modules with CompactLogix Select I/O Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
5370 L2 Controllers Embedded I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Determine Embedded Module Update Time . . . . . . . . . . . . . . . . . . . . . . 193
Channel Update Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Embedded Analog I/O Modules Data Arrays . . . . . . . . . . . . . . . . . . . . . . 199
Input Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Output Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Configuration Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Local Expansion Modules - Optional . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Distributed I/O Modules over an EtherNet/IP Network. . . . . . . . 211
Distributed I/O Modules over a DeviceNet Network . . . . . . . . . . . 212
Validate I/O Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Estimate Requested Packet Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Module Fault Related to RPI Estimates . . . . . . . . . . . . . . . . . . . . . . . . 215
System Power Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Power Supply Distance Rating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Configure Local I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Configure Embedded I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Configure Local Expansion Modules . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Common Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 221
I/O Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Electronic Keying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Exact Match. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Compatible Keying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Disabled Keying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Configure Distributed I/O Modules on an
EtherNet/IP Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Configure Distributed I/O Modules on a DeviceNet Network . . . . . . 232
Monitor I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
End-cap Detection and Module Faults. . . . . . . . . . . . . . . . . . . . . . . . . 236
Chapter 9
Use I/O Modules with CompactLogix Select I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
5370 L3 Controllers Local Expansion Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Distributed I/O Modules over an EtherNet/IP Network . . . . . . . 240
Distributed I/O Modules over a DeviceNet Network. . . . . . . . . . . 241
Validate I/O Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Estimate Requested Packet Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Module Fault Related to RPI Estimates . . . . . . . . . . . . . . . . . . . . . . . 243
Calculate System Power Consumption . . . . . . . . . . . . . . . . . . . . . . . . 244
Physical Placement of I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Power Supply Distance Rating. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Configure I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Common Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 253
I/O Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Electronic Keying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Exact Match . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Compatible Keying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Disabled Keying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Configure Distributed I/O Modules on an
EtherNet/IP Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Configure Distributed I/O Modules on a DeviceNet Network. . . . . . 263
Monitor I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
End-cap Detection and Module Faults . . . . . . . . . . . . . . . . . . . . . . . . 266
Chapter 10
Develop Applications Elements of a Control Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Task Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Scheduled and Unscheduled Programs . . . . . . . . . . . . . . . . . . . . . . . . 273
Routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Extended Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Access Extended Properties in Logic . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Programming Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Add-On Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Monitoring Controller Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Monitoring I/O Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Determine if I/O Communication has Timed Out . . . . . . . . . . . . . 282
Determine if I/O Communication to a Specific I/O
Module has Timed Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Interrupt the Execution of Logic and Execute the
Fault Handler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Chapter 11
Develop Integrated Motion over an Motion Axes Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
EtherNet/IP Network Applications AXIS_VIRTUAL Axis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
AXIS_CIP_DRIVE Axis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Maximum Number of Position Loop-configured Drives . . . . . . . . . . . . 291
Position Loop-configured Drive Limits . . . . . . . . . . . . . . . . . . . . . . . . 291
Time Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
Configure Integrated Motion on the EtherNet/IP Network . . . . . . . . 293
Enable Time Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Add a Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Scalability in Applications Using Integrated Motion on
EtherNet/IP Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
1769-L30ERM, 1769-L33ERM, and
1769-L36ERM Controllers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
1769-L18ERM-BB1B Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
1769-L27ERM-QBFC1B Controller. . . . . . . . . . . . . . . . . . . . . . . . . . 300
Chapter 12
Use a Secure Digital Card Store or Load a Project with the Secure Digital Card . . . . . . . . . . . . . . . 303
Store a Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Load a Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Appendix A
Status Indicators Use the CompactLogix 5370 Controllers Status Indicators . . . . . . . . . 309
Appendix B
Connections over an . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
EtherNet/IP Network
Appendix C
History of Changes Changes to the Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
This manual describes the necessary tasks to install, configure, program, and
operate a CompactLogix 5370 controller. This manual is intended for
automation engineers and control system developers.
CompactLogix 5370 controllers are designed to provide solution for small and
medium-sized applications.
Studio 5000 Environment The Studio 5000™ Engineering and Design Environment combines engineering
and design elements into a common environment. The first element in the
Studio 5000 environment is the Logix Designer application. The Logix Designer
application is the rebranding of RSLogix™ 5000 software and will continue to be
the product to program Logix5000™ controllers for discrete, process, batch,
motion, safety, and drive-based solutions.
Additional Resources These documents contain additional information that may assist you when using
Rockwell Automation products.
Resource Description
CompactLogix Selection Guide, publication Describes information about products used in a CompactLogix
1769-SG001 control system to assist you in designing a control solution.
CompactLogix Controllers Specifications Technical Provides CompactLogix controller specifications.
Data, publication 1769-TD005
CompactLogix 5370 L1 Controllers Quick Start, Describes basic tasks to design, install and start a CompactLogix
publication IASIMP-QS024 5370 L1 control system.
CompactLogix 5370 L2 Controllers Quick Start, Describes basic tasks to design, install and start a CompactLogix
publication IASIMP-QS025 5370 L1 control system.
CompactLogix 5370 L3 Controllers Quick Start, Describes basic tasks to design, install and start a CompactLogix
publication IASIMP-QS023 5370 L3 control system.
Integrated Architecture and CIP Sync Configuration Describes CIP Sync technology and how to synchronize clocks in
Application Technique, publication IA-AT003 the Rockwell Automation Integrated Architecture™ system.
CIP Motion Configuration and Startup User Manual, Describes basic tasks you can use to quickly and easily
publication MOTION-UM003 understand how best to create an Integrated Motion over an
EtherNet/IP network control solution.
Kinetix 350 Single-axis EtherNet/IP Servo Drive Describes how to install, use and troubleshoot Kinetix® 350
User Manual, publication 2097-UM002 drives.
PowerFlex 755 Drive Embedded EtherNet/IP Describes how to install, use and troubleshoot PowerFlex® 755
Adapter User Manual, publication 750COM-UM001 drives.
Kinetix 6200 and Kinetix 6500 Modular Multi-axis Describes how to install, use and troubleshoot Kinetix 6500
Servo Drives User Manual, publication 2094-UM002 drives.
Logix5000 Controllers Common Procedures Describes how to create and edit a program, communicate with
Programming Manual, publication 1756-PM001 and configure modules.
Ethernet Design Considerations Reference Manual, Describes the following concepts that you should consider when
publication ENET-RM002 designing a control system that includes an EtherNet/IP
network:
• EtherNet/IP overview
• Ethernet infrastructure
• EtherNet/IP protocol
Logix5000 Controllers Execution Time and Memory Details how to estimate the execution time and memory use of
Use Reference Manual, publication 1756-RM087 the controller’s logic.
Logix5000 Controllers General Instruction Set Details how to program the controller for sequential
Reference Manual, publication 1756-RM003 applications.
Logix5000 Controllers Process Control/Drives Details how to program the controller for process or drives
Instruction Set Reference Manual, publication applications.
1756-RM006
Logix5000 Controllers Motion Instructions Details how to program the controllers for motion applications.
Reference Manual, publication MOTION-RM002
CIP Motion Configuration and Start-up User Describes how to configure an Integrated Motion over EtherNet/
Manual, publication MOTION-UM003 IP motion application and to start up that motion solution in a
Logix5000 control system.
Industrial Automation Wiring and Grounding Provides general guidelines for installing a Rockwell Automation
Guidelines, publication 1770-4.1 industrial system.
Product Certifications website, http://www.ab.com Provides declarations of conformity, certificates, and other
certification details.
Topic Page
Before You Begin 16
Install the Secure Digital Card 20
Install the System 22
Connect to the Controller via a USB Cable 31
Connect the Controller to an EtherNet/IP Network 32
Before You Begin Consider the following before installing a CompactLogix 5370 L1 controller:
• The controller has sixteen embedded digital input points and sixteen
embedded digital output points. You wire the input and output points via
a removable connector.
• The controller supports the use of 1734 POINT I/O™ modules on the
POINTBus™ backplane as local expansion modules.
IMPORTANT We strongly recommend that you use the latest series and firmware
revision for all 1734 POINT I/O modules in the local expansion slots to
make sure your application will operate as expected.
• You can use up to the maximum number of 1734 POINT I/O modules
with the CompactLogix 5370 L1 controllers listed in Table 1, as long as
the total current drawn by the embedded I/O and local expansion modules
does not exceed the available POINTBus backplane current of 1 A and/or
field power current of 3 A.
The field power distributor module breaks the available field power
current between the modules to its left and right. With the field power
distributor module installed, the modules to its left can draw up 3 A of
field power current, and the modules to its right can draw as much field
power current as allowed by the field power distributor.
IMPORTANT Remember, the field power distributor module only changes the level
of field power current available in the system. It does not affect the
level of POINTBus backplane current available.
ATTENTION: Do not discard the end cap. Use this end cap to cover the
exposed interconnections on the last mounting base on the DIN rail.
Failure to do so could result in equipment damage or injury from
electric shock.
For more information on how to terminate the end of your system, see
page 25.
• 1734 POINT I/O modules support removal and insertion under power.
These parts are included in the box when you order your controller:
• Controller - Specific catalog number varies by order
• An end cap protective covering that slides onto the right side of the
CompactLogix 5370 L1 control system.
Install the Secure The CompactLogix 5370 L1 controller is shipped from the factory with the
1784-SD1 SD card installed.
Digital Card
Complete these steps to re-install an SD card that has been removed from the
controller back into the controller or if installing a new SD card into the
controller.
WARNING: When you insert or remove the SD 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.
Unlocked Locked
32005-M
32225-M
You can install the SD card in one orientation only. The beveled corner
should be at the top.
If you feel resistance when inserting the SD card, pull it out and change the
orientation.
32226-M
32227-M
We recommend you keep the SD card door closed during normal system
operation. For more information on using the SD card, see Use a Secure
Digital Card on page 301.
Install the System Complete the following steps to install the CompactLogix 5370 L1
control system.
• Mount the System
• Ground the System
• Install the Controller
• Connect Power to the Controller
You mount a CompactLogix 5370 L1 control system on a DIN rail. Before you
complete the steps required to installing the system, install a DIN rail.
ATTENTION: This product is grounded through the DIN rail to chassis ground.
Use zinc-plated yellow-chromate steel DIN rail to assure proper grounding.
The use of other DIN rail materials (for example, aluminum or plastic) that
can corrode, oxidize, or are poor conductors, can result in improper or
intermittent grounding. Secure DIN rail to mounting surface approximately
every 200 mm (7.8 in.) and use end-anchors appropriately.
IMPORTANT You must install bumpers on the back of your CompactLogix 5370 L1
controller before mounting it on the EN 50022 - 35 x 15 mm
(1.38 x 0.59 in.) DIN rail.
For more information about the required bumper (PN-83094), contact
your local Allen-Bradley distributor or Rockwell Automation sales
representative.
Minimum Spacing
Maintain spacing from enclosure walls, wireways, and adjacent equipment. Allow
50 mm (2 in.) of space on all sides, as shown. This provides ventilation and
electrical isolation.
50 mm
Top (2 in.)
50 mm 50 mm
Embedded Power
Controller with
End Cap
Side Side
Bottom 50 mm
(2 in.)
System Dimensions
130.00 mm
00:00:BC:2E:69:F6
(5.11 in.)
144.00 mm
(5.67 in.)
00:00:BC:2E:69:F6
2. Slide the controller into position on the DIN rail and push the locking
tabs in.
00:00:BC:2E:69:F6
3. If you are not using local expansion modules, use the tongue-and-groove
slots on the right side of the controller to slide a protective covering onto
the controller. The protective cover ships with the controller.
The covering covers the exposed interconnections on the right side of the
controller. Failure to use a protective covering could result in equipment
damage or injury from electric shock.
If you are using local expansion modules, see Local Expansion Modules on
page 152 for more information on installing them in a
CompactLogix 5370 L1 control system.
IMPORTANT This section describes how to power the controller via the VDC+ and VDC-
terminals.
Connections to the VDC+ and VDC- terminals do not provide power to input or
output devices connected to the controller’s embedded I/O modules or local
expansion modules.
For more information on how to provide power to input or output devices that
are connected to the controller’s embedded I/O modules and local
expansion modules, see page 140.
You must connect a dedicated Class 2/SELV-listed external power supply to the
controller’s embedded power supply. The external power supply converts 115/
230V AC power to 24V DC or other application-required DC voltage that is
within the controller’s operating range.
IMPORTANT The CG terminal on the removable connector connects to the DIN rail via a
grounding clip on the back of the controller. The controller is grounded once it
is installed on a DIN rail as described in Mount the System on page 22.
You should not make any connections to the CG terminal.
• Use a power source that most effectively meets your application needs.
That is, calculate your application’s power requirements before choosing a
power source to avoid using a power source that far exceeds your
application requirements.
• The external 24V DC power source connected to the VDC+ and VDC-
terminals on the removable connector must reside in the same enclosure as
the CompactLogix 5370 L1 controller.
• This section assumes that any DIN rail you use has been grounded
following Industrial Automation Wiring and Grounding Guidelines,
publication 1770-4.1
• Not all Class 2/SELV-listed power supplies are certified for use in all
applications, for example, use in both nonhazardous and hazardous
environments.
The external 24V DC power source can be installed on the same DIN rail
as the controller or a separate DIN rail.
3. Connect wires to the appropriate 24V DC+ and 24V DC- connections on
the external 24V DC power source.
WARNING: If you connect or disconnect wiring while the field-side 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.
NCok
DC 24-28V 50W max.
DC
ok
24-
28V
NEC Class 2
P S l
00:00:BC:2E:69:F6
5. Connect the wire connected to the 24V DC+ terminal on the external
24V DC power source to the VDC+ terminal, that is, the top terminal, on
the removable connector.
32240-M
6. Connect the wire connected to the 24V DC- terminal on the external 24V
DC power source to the VDC- terminal, that is, the terminal that is
second from the top, on the removable connector.
32240-M
DC ok
DC 24-28V 50W max.
DC 00:00:BC:2E:69:F6
ok
24-
28V
NEC Class 2
Power Supply
Connect to the Controller via The controller has a USB port that uses a Type B receptacle. The port is USB
2.0-compatible and operates at 12 Mbps.
a USB Cable
Use a USB cable to connect your computer to the USB port. With this
connection, you can upgrade firmware and download programs to the controller
directly from your computer.
32234-M
Connect the Controller to an WARNING: If you connect or disconnect the communications cable with
EtherNet/IP Network power applied to this module or any device on the network, an electrical arc
can occur. This could cause an explosion in hazardous location installations.
Be sure that power is removed or the area is nonhazardous before proceeding.
Connect the RJ45 connector of the Ethernet cable to one of the Ethernet ports
on the controller. The ports are on the bottom of the controller.
Bottom of Controller
Port 1 - Front
Port 2 - Back
32235-M
IMPORTANT This example shows how to connect the controller to the network through one
port. Depending on your application’s network topology, you might connect
both ports of the controller to the EtherNet/IP network.
For more information on EtherNet/IP network topologies, see page 120.
Topic Page
Before You Begin 36
Install the Secure Digital Card 39
Install the System 41
Connect to the Controller via a USB Cable 52
Connect the Controller to an EtherNet/IP Network 53
Before You Begin Consider the following before installing a CompactLogix 5370 L2 controller:
• The controllers have embedded I/O points. You wire the input and output
points via a removable connector.
• You must terminate the end of the CompactBus via a 1769-ECR right end
cap as shown in step 6 on page 47.
• You cannot remove nor install Compact I/O modules while the controller
is powered.
SOURCE
24VDC
SINK\
INPUT
DC
8 9 10 11 12 13 14 15
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7
8 9 10 11 12 13 14 15
DC IN
00 08
01 09
02 10
03 11
04 12
05 13
06 14
07 15
COM COM
0 1
+V +V
Local Expansion Modules
00 08
01 09
02 10
03 11
04 12
00:00:BC:2E:69:F6 05 13
06 14
07 15
+24VDC COM FG
Supply Terminals
L24ER 0 1 2 3 4 5 6 7 A0 B0 Z0
SOURCE
IN
24VDC
0 1 2 3 4 5 6 7 A0 B0 Z0
SINK\
INPUT
DC
HIGH SPEED
QBFC1B A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
SOURCE
IN
24VDC
SINK\
INPUT
DC
HIGH SPEED
A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
8 9 10 11 12 13 14 15 1 3 OK
8 9 10 11 12 13 14 15 1 3 OK
DC IN HSC
00 08 A0+ A0-
01 09 B0+ B0-
02 10 Z0+ Z0-
03 11 A1+ A1-
04 12 B1+ B1-
05 13 Z1+ Z1-
06 14 +V +V
OUT OUT
07 15 0 2
+24VDC COM FG
Supply Terminals
IN
24VDC
0 1 2 3 4 5 6 7 A0 B0 Z0
SINK\
INPUT
DC
HIGH SPEED
QBFC1B A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
SOURCE
IN
24VDC
SINK\
INPUT
DC
HIGH SPEED
A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
8 9 10 11 12 13 14 15 1 3 OK
8 9 10 11 12 13 14 15 1 3 OK
DC IN HSC
00 08 A0+ A0-
01 09 B0+ B0-
02 10 Z0+ Z0-
03 11 A1+ A1-
04 12 B1+ B1-
05 13 Z1+ Z1-
06 14 +V +V
OUT OUT
07 15 0 2
COM COM OUT 0UT
V
Local Expansion Modules
+V +V in in
0+ 2+
I I
00 08 in in
0+ 2+
V/I V/I
01 09 in in
0- 2-
CJC inV
02 10 + 3+
CJC inI
03 11 - 3+
V V/I
04 12 in in
1+ 3-
00:00:BC:2E:69:F6 05 13
I
in
V/I
in
1+ 1-
V V
06 14 OUT OUT
0+ 1+
I I
07 15 OUT in
0+ 1+
+24VDC
+24VDC COM
COM FG
FG
Supply Terminals
These parts are included in the box when you order your controller:
• Controller - Specific catalog number varies by order
Install the Secure The CompactLogix 5370 L2 controller is shipped from the factory with the
1784-SD1 SD card installed.
Digital Card
Complete these steps to re-install an SD card that has been removed from the
controller back into the controller or if installing a new SD card into the
controller.
WARNING: When you insert or remove the SD 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.
Unlocked Locked
32005-M
32253-M
You can install the SD card in one orientation only. The beveled corner
should be at the bottom.
If you feel resistance when inserting the SD card, pull it out and change the
orientation.
32254-M
32255-M
We recommend you keep the SD card door closed during normal system
operation. For more information on using the SD card, see Use a Secure
Digital Card on page 301.
Install the System Complete the following tasks to install the CompactLogix 5370 L2
control system:
• Mount the System
• Ground the System
• Install the Controller
• Connect Power to the Control System
ATTENTION: This product is grounded through the DIN rail to chassis ground.
Use zinc-plated yellow-chromate steel DIN rail to assure proper grounding.
The use of other DIN rail materials (for example, aluminum or plastic) that
can corrode, oxidize, or are poor conductors, can result in improper or
intermittent grounding. Secure DIN rail to mounting surface approximately
every 200 mm (7.8 in.) and use end-anchors appropriately.
Minimum Spacing
Maintain spacing from enclosure walls, wireways, and adjacent equipment. Allow
50 mm (2 in.) of space on all sides, as shown. This provides ventilation and
electrical isolation.
50 mm
Top (2 in.)
50 mm 50 mm
CompactLogix 5370 L2
Embedded Power
End Cap
Side Side
Bottom 50 mm
(2 in.)
System Dimensions
L24ER
0 1 2 3 4 5 6 7
SOURCE
QB1B
24VDC
SINK\
INPUT
DC
8 9 10 11 12 13 14 15
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7
8 9 10 11 12 13 14 15
DC IN
00 08
01 09
02 10
03 11
04 12
05 13
118.00 mm 06 14
07 15
+V +V
00 08
01 09
02 10
03 11
04 12
00:00:BC:2E:69:F6 05 13
06 14
07 15
COM COM
0 1
DC OUT
+24VDC COM FG
32260-M
0 1 2 3 4 5 6 7 A0 B0 Z0
QBFC1B
SOURCE
IN
24VDC
SINK\
INPUT
DC
HIGH SPEED
A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
8 9 10 11 12 13 14 15 1 3 OK
DC IN HSC
00 08 A0+ A0-
01 09 B0+ B0-
02 10 Z0+ Z0-
03 11 A1+ A1-
04 12 B1+ B1-
05 13 Z1+ Z1-
118.00 mm 06 14
07 15
+V
OUT
0
+V
OUT
2
OUT 0UT
V
+V +V in in
0+ 2+
I I
00 08 in in
0+ 2+
V/I V/I
01 09 in in
0- 2-
CJC inV
02 10 + 3+
CJC inI
03 11 - 3+
V V/I
04 12 in in
1+ 3-
00:00:BC:2E:69:F6 05 13
I V/I
in in
1+ 1-
V V
06 14 OUT OUT
0+ 1+
I I
07 15 OUT in
0+ 1+
COM COM COM COM
0 1
DC OUT ANALOG
+24VDC COM FG
32260-M
IN
24VDC
SINK\
INPUT
DC
HIGH SPEED
A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
8 9 10 11 12 13 14 15 1 3 OK
DC IN HSC
00 08 A0+ A0-
01 09 B0+ B0-
02 10 Z0+ Z0-
03 11 A1+ A1-
04 12 B1+ B1-
05 13 Z1+ Z1-
118.00 mm 06 14
07 15
+V
OUT
0
+V
OUT
2
COM COM OUT 0UT
(4.65 in.) 0 1
NC NC
1
COM COM
V V
3
+V +V in in
0+ 2+
I I
00 08 in in
0+ 2+
V/I V/I
01 09 in in
0- 2-
V
CJC in
02 10 + 3+
CJC inI
03 11 - 3+
V V/I
04 12 in in
1+ 3-
00:00:BC:2E:69:F6 05 13
I
in
V/I
in
1+ 1-
V V
06 14 OUT OUT
0+ 1+
I I
07 15 OUT in
0+ 1+
COM COM COM COM
0 1
DC OUT ANALOG
+24VDC COM FG
32260-M
Use two M4 or #8 panhead screws to mount the controller. Mounting screws are
required on every module. Use this procedure to use the assembled modules as a
template for drilling holes in the panel.
TIP The grounding plate, that is, where you install the mounting screws,
grounds the module when it is panel-mounted.
ATTENTION: This product is grounded through the DIN rail to chassis ground.
Use zinc plated yellow-chromate steel DIN rail to assure proper grounding.
The use of other DIN rail materials (for example, aluminum or plastic) that
can corrode, oxidize, or are poor conductors, can result in improper or
intermittent grounding. Secure DIN rail to mounting surface approximately
every 200 mm (7.8 in.) and use end-anchors appropriately.
1. Hook the DIN rail latch at the top of the back of the controller on the
DIN rail.
2. Swing the controller downward until it touches the DIN rail and press the
controller against the DIN rail until it clicks in place.
L27ERM
0 1 2 3 4 5 6 7 A0 B0 Z0
QBFC1B
SOURCE
IN
24VDC
SINK\
INPUT
DC
HIGH SPEED
A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
8 9 10 11 12 13 14 15 1 3 OK
DC IN HSC
00 08 A0+ A0-
01 09 B0+ B0-
02 10 Z0+ Z0-
03 11 A1+ A1-
04 12 B1+ B1-
05 13 Z1+ Z1-
06 14 +V +V
OUT OUT
07 15 0 2
COM COM OUT 0UT
0 1 1 3
NC NC COM COM
V V
+V +V in in
0+ 2+
I I
00 08 in in
0+ 2+
V/I V/I
01 09 in in
0- 2-
CJC V
02 10 + in
3+
CJC inI
03 11 - 3+
V V/I
04 12 in in
1+ 3-
00:00:BC:2E:69:F6 05 13
I V/I
in in
1+ 1-
V V
06 14 OUT OUT
0+ 1+
I I
07 15 OUT in
0+ 1+
COM COM COM COM
0 1
DC OUT ANALOG
+24VDC COM FG
32256-M
L27ERM
0 1 2 3 4 5 6 7 A0 B0 Z0
SOURCE
QBFC1B
IN
24VDC
SINK\
INPUT
DC
HIGH SPEED
A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
8 9 10 11 12 13 14 15 1 3 OK
DC IN HSC
00 08 A0+ A0-
01 09 B0+ B0-
02 10 Z0+ Z0-
03 11 A1+ A1-
04 12 B1+ B1-
05 13 Z1+ Z1-
06 14 +V +V
OUT OUT
07 15 0 2
COM COM OUT 0UT
0 1 1 3
NC NC COM COM
V V
+V +V in in
0+ 2+
I I
00 08 in in
0+ 2+
V/I V/I
01 09 in in
0- 2-
CJC inV
02 10 + 3+
CJC inI
03 11 - 3+
V V/I
04 12 in in
1+ 3-
00:00:BC:2E:69:F6 05 13
I
in
V/I
in
1+ 1-
V V
06 14 OUT OUT
0+ 1+
I I
07 15 OUT in
0+ 1+
COM COM COM COM
0 1
DC OUT ANALOG
+24VDC COM FG
32257-M
6. If you are not using local expansion modules, slide the 1769-ECR end cap
onto the right side of the controller.
IMPORTANT You must install an end cap onto the right side of the
CompactLogix 5370 L2 controller system either at the end of the
controller or at the end of any local expansion modules that may be
installed onto the controller.
The covering covers the exposed interconnections on the right side of
the controller. Failure to use a protective covering could result in
equipment damage or injury from electric shock.
32258-M
7. Push the end cap locking mechanism to the right to lock it onto
the controller.
32267-M
If you are using local expansion modules, see Local Expansion Modules -
Optional on page 210 for more information on installing them in a
CompactLogix 5370 L2 control system.
• Not all Class 2 or SELV-listed power supplies are certified for use in all
applications, for example, use in both nonhazardous and hazardous
environments.
• This section describes how to wire terminals +24VDC and COM on the
CompactLogix 5370 L2 controller. They are the only terminals you wire
to power the CompactLogix 5370 L2 control system.
IMPORTANT The 1606-XLDNET4 power supply is not certified for use in all applications, for
example, you cannot use it in hazardous locations. Read the points in Connect
Power to the Control System on page 48 before choosing the external power
supply for your application.
The external 24V DC power source can be installed on the same DIN rail
as the controller or a separate DIN rail.
3. Connect wires to the appropriate 24V DC+ and 24V DC- connections on
the external 24V DC power source.
WARNING: If you connect or disconnect wiring while the field-side 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.
4. Strip 8 mm (0.31 in) insulation from the end of the wire that you will
connect to the +24VDC terminal on the controller.
5. Connect the wire from the 24V DC+ terminal on the external 24V DC
power source to the +24VDC terminal on the controller.
L27ERM 0 1 2 3 4 5 6 7 A0 B0 Z0
SOURCE
IN
24VDC
0 1 2 3 4 5 6 7 A0 B0 Z0
SINK\
INPUT
DC
HIGH SPEED
QBFC1B A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
SOURCE
IN
24VDC
SINK\
INPUT
DC
HIGH SPEED
A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
8 9 10 11 12 13 14 15 1 3 OK
8 9 10 11 12 13 14 15 1 3 OK
DC IN HSC
00 08 A0+ A0-
01 09 B0+ B0-
02 10 Z0+ Z0-
03 11 A1+ A1-
04 12 B1+ B1-
05 13 Z1+ Z1-
06 14 +V +V
OUT OUT
07 15 0 2
COM COM OUT 0UT
0 1 1 3
NC NC COM COM
+24VDC COM FG +V +V
V V
in in
0+ 2+
I I
00 08 in in
0+ 2+
V/I V/I
01 09 in in
0- 2-
CJC inV
02 10 + 3+
CJC inI
03 11 - 3+
V V/I
04 12 in in
1+ 3-
00:00:BC:2E:69:F6 05 13
I
in
V/I
in
1+ 1-
V V
06 14 OUT OUT
0+ 1+
I I
07 15 OUT in
0+ 1+
COM COM COM COM
0 1
DC OUT ANALOG
+24VDC
+24VDC COM
COM FG
FG
6. Strip 8 mm (0.31 in) insulation from the end of the wire that you will
connect to the COM terminal on the controller.
7. Connect the wire from the 24V DC- terminal on the external 24V DC
power source to the COM terminal on the controller.
L27ERM 0 1 2 3 4 5 6 7 A0 B0 Z0
SOURCE
IN
24VDC
0 1 2 3 4 5 6 7 A0 B0 Z0
SINK\
INPUT
DC
HIGH SPEED
QBFC1B A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
SOURCE
IN
24VDC
SINK\
INPUT
DC
HIGH SPEED
A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
8 9 10 11 12 13 14 15 1 3 OK
8 9 10 11 12 13 14 15 1 3 OK
DC IN HSC
00 08 A0+ A0-
01 09 B0+ B0-
02 10 Z0+ Z0-
03 11 A1+ A1-
04 12 B1+ B1-
05 13 Z1+ Z1-
06 14 +V +V
OUT OUT
07 15 0 2
COM COM OUT 0UT
0 1 1 3
NC NC COM COM
V V
+V +V in in
0+ 2+
I I
00 08 in in
0+ 2+
V/I V/I
01 09 in in
0- 2-
CJC inV
02 10 + 3+
CJC inI
03 11 - 3+
V V/I
04 12 in in
1+ 3-
00:00:BC:2E:69:F6 05 13
I
in
V/I
in
1+ 1-
V V
06 14 OUT OUT
0+ 1+
I I
07 15 OUT in
0+ 1+
COM COM COM COM
0 1
DC OUT ANALOG
+24VDC
+24VDC COM
COM FG
FG
IMPORTANT If your application requires a power control device, for example, a switch or
relay, between the external power supply and the CompactLogix 5370 L2
controller’s embedded power supply to control when the controller is powered,
you must install the power control device at the +24VDC terminal on the
controller.
If you install the power control device at the COM terminal, the
CompactLogix 5370 L2 controller may not power up or power down properly.
L27ERM 0 1 2 3 4 5 6 7 A0 B0 Z0
SOURCE
IN
24VDC
0 1 2 3 4 5 6 7 A0 B0 Z0
SINK\
INPUT
DC
HIGH SPEED
QBFC1B
A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
SOURCE
IN
24VDC
SINK\
INPUT
DC
HIGH SPEED
A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
8 9 10 11 12 13 14 15 1 3 OK
8 9 10 11 12 13 14 15 1 3 OK
DC IN HSC
00 08 A0+ A0-
01 09 B0+ B0-
02 10 Z0+ Z0-
03 11 A1+ A1-
04 12 B1+ B1-
05 13 Z1+ Z1-
06 14 +V +V
OUT OUT
07 15 0 2
COM COM OUT 0UT
NEC Class 2 0 1 1 3
Power Supply NC NC COM COM
V V
+V +V in in
0+ 2+
I I
US LISTED 00 08 in in
0+ 2+
18WM
V/I V/I
IND.CONT.EO. 01 09 in in
0- 2-
CJC inV
02 10 + 3+
CJC inI
03 11 - 3+
V V/I
04 12 in in
1+ 3-
00:00:BC:2E:69:F6 05 13
I V/I
in in
1+ 1-
V V
06 14 OUT OUT
0+ 1+
N L 07 15
I I
OUT in
0+ 1+
COM COM COM COM
0 1
DC OUT ANALOG
+24VDC
+24VDC COM
COM FG
FG
IMPORTANT When you remove power from the CompactLogix 5370 L2 controller to cycle
power, the controller’s OK status indicator remains lit briefly as the controller
passes through its shutdown sequence.
Do not reapply power from the external power supply to the
CompactLogix 5370 L2 controller’s embedded power supply until after the
controller’s OK status indicator is off.
Connect to the Controller via The controller has a USB port that uses a Type B receptacle. The port is USB
2.0-compatible and operates at 12 Mbps.
a USB Cable
Use a USB cable to connect your computer to the USB port. With this
connection, you can upgrade firmware and download programs to the controller
directly from your computer.
32259-M
Connect the Controller to an WARNING: If you connect or disconnect the communication cable with
EtherNet/IP Network power applied to this module or any device on the network, an electrical arc
can occur. This could cause an explosion in hazardous location installations.
Be sure that power is removed or the area is nonhazardous before proceeding.
Connect the RJ45 connector of the Ethernet cable to one of the Ethernet ports
on the controller. The ports are on the bottom of the controller.
ATTENTION: Do not plug a DH-485 network cable or a NAP cable into the
Ethernet port. Undesirable behavior and/or damage to the port may result.
Bottom of Controller
Port 1 - Front
Port 2 - Back
32261-M
IMPORTANT This example shows how to connect the controller to the network through one
port. Depending on your application’s network topology, you might connect
both ports of the controller to the EtherNet/IP network.
For more information on EtherNet/IP network topologies, see page 120.
Notes:
Topic Page
Before You Begin 58
Install the Secure Digital Card 61
Install the System 63
Connect to the Controller via a USB Cable 72
Connect the Controller to an EtherNet/IP Network 73
Before You Begin Consider the following when planning your CompactLogix 5370 L3
control system:
• The controller has a power supply distance rating of four. This rating
means the controller must be within four slots of the power supply, that is,
you can install as many as three modules between the power supply and the
controller, as shown below.
00:00:BC:2E:69:F6
1 (Front)
2 (Rear)
• The controllers support this many local expansion modules across multiple
I/O banks.
• You must terminate the end of the last bank in a CompactLogix 5370 L3
control system. Depending on your system design, you may need to
terminate a bank at the left or right end of the bank.
A 1769-ECx end cap is required to terminate the end of the last bank in
the control system.
These parts are included in the box when you order your controller:
• Controller - Specific catalog number varies by order
Install the Secure The CompactLogix 5370 L3 controllers ship from the factory with the
1784-SD1 SD card installed.
Digital Card
Complete these steps to re-install an SD card that has been removed from the
controller back into the controller or if installing a new SD card into the
controller.
WARNING: When you insert or remove the Secure Digital (SD) 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.
Unlocked Locked
32005-M
32163-M
You can install the SD card in one orientation only. The beveled corner
should be at the top. An orientation logo is printed on the card.
If you feel resistance when inserting the SD card, pull it out and change the
orientation.
32164-M
32165-M
We recommend you keep the SD card door closed during normal system
operation. For more information on using the SD card, see Use a Secure Digital
Card on page 301.
Install the System Complete the following steps to install the CompactLogix 5370 L3
control system.
• Assemble the System
• Mount the System
• Ground the System
• Connect Power to the Control System
You can attach an adjacent Compact I/O module or 1769 Compact I/O power
supply to a CompactLogix 5370 L3 controller before or after mounting. For
mounting instructions, see Ground the System on page 69 or Mount the
Controller on a Panel on page 70.
Complete these steps to install the controller. This example describes how to
attach a 1769 Compact I/O power supply to the controller.
t)
on
1 (Fr ear)
2 (R
3. Use the upper and lower tongue-and-groove slots to secure the controller
and power supply together.
Tongue-and-groove Slots
)
ront
1 (F ear)
2 (R
4. Move the power supply back along the tongue-and-groove slots until the
bus connectors line up with each other.
5. Use your fingers or a small screwdriver to push the power supply’s bus lever
back slightly to clear the positioning tab.
6. Move the power supply’s bus lever fully to the left until it clicks; making
sure it locks.
1 (Front)
2 (Rear)
7. If your system does not use any local expansion modules, use the tongue-
and-groove slots described earlier to attach a 1769-ECR Compact I/O end
cap terminator to the last module in the system.
IMPORTANT You must install an end cap onto the right side of the
CompactLogix 5370 L2 controller system either at the end of the
controller or at the end of any local expansion modules that may be
installed onto the controller.
The covering covers the exposed interconnections on the right side of
the controller. Failure to use a protective covering could result in
equipment damage or injury from electric shock.
8. Wire the 1769 Compact I/O power supply according to the directions in
the Compact I/O Expansion Power Supplies installation instructions,
publication 1769-IN028.
If you are using local expansion modules, see Local Expansion Modules on
page 238.
ATTENTION: During panel or DIN rail mounting of all devices, be sure that all
debris (such as metal chips or wire strands) is kept from falling into the
controller. Debris that falls into the controller could cause damage while the
controller is energized.
Horizontal Orientation
00:00:BC:2E:69:F6
1 (Front)
2 (Rear)
Bank 1
00:00:BC:2E:69:F6
1 (Front)
2 (Rear)
1769-CRRx Cable
Vertical Orientation
Bank 2
Minimum Spacing
Maintain spacing from enclosure walls, wireways, and adjacent equipment. Allow
50 mm (2 in.) of space on all sides, as shown. This provides ventilation and
electrical isolation.
Top 50 mm
(2 in.)
50 mm 50 mm
Power Supply
End Cap
Side Side
Bottom 50 mm
(2 in.)
System Dimensions
55 mm 70 mm 35 mm
(2.17 in.) (2.76 in.) (1.38 in.)
132 mm
(5.20 in.)
118 mm
(4.65 in.)
00:00:BC:2E:69:F6
1 (Front)
2 (Rear)
52.5 mm 35 mm 35 mm 35 mm 35 mm
(2.07 in.) (1.38 in.) (1.38 in.) (1.38 in.) (1.38 in.) 32150-M
105 mm
(4.13 in.)
32247-M
For example, a product with a power supply distance rating of four can only have
up to three slots between it and the power supply.
Device Power Supply Distance Rating
CompactLogix 5370 L3 controller
4
1769 Compact I/O DeviceNet scanner
Compact I/O module 4…8, depending on module
For more information about the power supply distance
rating for a Compact I/O module, see CompactLogix
Selection Guide, publication 1769-SG001
For more information, refer to the Industrial Automation Wiring and Grounding
Guidelines, publication 1770-4.1.
Use two M4 or #8 panhead screws to mount the controller. Mounting screws are
required on every module. Use this procedure to use the assembled modules as a
template for drilling holes in the panel.
TIP The grounding plate, that is, where you install the mounting screws,
grounds the module when it is panel-mounted.
ATTENTION: This product is grounded through the DIN rail to chassis ground.
Use zinc plated yellow-chromate steel DIN rail to assure proper grounding.
The use of other DIN rail materials (for example, aluminum or plastic) that
can corrode, oxidize, or are poor conductors, can result in improper or
intermittent grounding. Secure DIN rail to mounting surface approximately
every 200 mm (7.8 in.) and use end-anchors appropriately.
1. Before mounting the controller on a DIN rail, close the controller’s DIN
rail latches.
2. Press the DIN rail mounting area of the controller against the DIN rail.
Connect to the Controller The controller has a USB port that uses a Type B receptacle. The port is USB
2.0-compatible and operates at 12 Mbps.
via a USB Cable
Use a USB cable to connect your computer to the USB port. With this
connection, you can upgrade firmware and download programs to the controller
directly from your computer.
Plug the USB cable into the CompactLogix 5370 L3 controller as shown.
32152-M
Connect the Controller to an WARNING: If you connect or disconnect the communications cable with
EtherNet/IP Network power applied to this module or any device on the network, an electrical arc
can occur. This could cause an explosion in hazardous location installations.
Be sure that power is removed or the area is nonhazardous before proceeding.
Connect the RJ45 connector of the Ethernet cable to one of the Ethernet ports
on the controller. The ports are on the bottom of the controller.
ATTENTION: Do not plug a DH-485 network cable or a NAP cable into the
Ethernet port. Undesirable behavior and/or damage to the port may result.
Bottom of Controller
Port 1 - Front
Port 2 - Rear
1 (Front)
2 (Rear)
IMPORTANT This example shows how to connect the controller to the network through one
port. Depending on your application’s EtherNet network topology, you might
connect both ports of the controller to the EtherNet/IP network.
For more information on EtherNet/IP network topologies, see page 120.
Topic Page
Set a Controller’s IP Address 77
Change a Controller’s IP Address 89
Load the Controller Firmware 93
Select the Controller’s Operating Mode 103
To complete the tasks described in this chapter, you must have the software
described in the following table installed on your computer.
The IP address uniquely identifies the controller. The IP address is in the form
xxx.xxx.xxx.xxx where each xxx is a number from 000…254 with some
exceptions for reserved values. These numbers are examples of reserved values
you cannot use:
• 000.xxx.xxx.xxx
• 127.xxx.xxx.xxx
• 224 to 255.xxx.xxx.xxx
Depending on system conditions, you may need to complete one of these tasks:
• Set the IP address for a controller that does not have one assigned.
Set a Controller’s IP Address You must set a CompactLogix 5370 controller’s IP address when the controller
powers up for the first time, that is, when commissioning the controller for the
first time. You are not required to set an IP address each time power is cycled to
the controller.
You can use these tools to set a CompactLogix 5370 controller’s IP address:
• Bootstrap Protocol (BOOTP) server
• Dynamic Host Configuration Protocol (DHCP) server
• RSLinx Classic software
• Logix Designer application
• SD card
IMPORTANT Each tool has connection requirements to set the controller’s IP address via that
tool. For example, your computer must be connected to the controller via a USB
cable to set the controller’s initial IP address with RSLinx Classic software or the
application.
No
Is controller Is controller
DHCP- enabled? BOOTP- enabled?
Yes
Yes Yes
• To use the BOOTP server, your computer and the controller must be
connected to the same EtherNet/IP network.
There are two conditions in which the CompactLogix 5370 controllers use the
BOOTP servers to set the controller’s IP address:
IMPORTANT Before you start the BOOTP/DHCP utility, make sure you have the controller’s hardware (MAC) address. The hardware address is on
the front of the controller and uses an address in a format similar to the following:
00:00:BC:2E:69:F6
L24ER
0 1 2 3 4 5 6 7
QB1B
SOURCE
24VDC
SINK\
INPUT
DC
8 9 10 11 12 13 14 15
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7
8 9 10 11 12 13 14 15
00:00:BC:2E:69:F6
00:00:BC:2E:69:F6
00:00:BC:2E:69:F6
1 (Front)
(Front)
+24VDC COM FG 2 (Rear)
The Request History panel appears with the hardware addresses of all
devices issuing BOOTP or DHCP requests.
5. Select the line with the same MAC address as your controller.
8. Click OK.
9. To permanently assign this configuration to the controller, wait for the
controller to appear in the Relation List panel and select it.
10. Click Disable BOOTP/DHCP.
When power is cycled, the controller uses the assigned configuration and
does not issue a BOOTP request.
IMPORTANT If you do not click Disable BOOTP/DHCP, on a power cycle, the host
controller clears the current IP configuration and begins sending
BOOTP requests again.
You can use RSLinx Classic software to set the CompactLogix 5370 controller’s
IP address.
IMPORTANT To set the IP address, that is, assign an IP address to a controller that does not
have one, for a CompactLogix 5370 controller via RSLinx Classic software, you
must be connected to your controller via the USB port.
IMPORTANT These steps show a 1769-L36ERM controller. The same steps apply to other
CompactLogix 5370 controllers with slight variations in screens.
1. Make sure a USB cable is connected to your computer and the controller.
2. Start RSLinx Classic software.
The RSWho dialog box appears and includes the USB driver.
4. Navigate to the USB network.
5. Right-click the controller and choose Module Configuration.
IMPORTANT If you click Dynamic, on a power cycle, the controller clears the
current IP configuration and resumes sending BOOTP requests or
DHCP requests, depending on the controller configuration.
9. Click OK.
As with all configuration changes, if desired, make sure you are using the SD card
in a way that it will not overwrite the IP address at the next controller power
cycle.
For more information on using the SD card, see Chapter 12, Use a Secure Digital
Card on page 301.
You can use Logix Designer application to set a CompactLogix 5370 controller’s
IP address. To set the IP address via the application, you must be connected to
your controller via the USB port.
IMPORTANT These steps show a 1769-L18ERMBB1B controller. The same steps apply to
other CompactLogix 5370 controllers with slight variations in screens.
3. Click Download.
The new project is downloaded to the controller and the project goes
online, in either Remote Program or Program mode.
5. Right-click the controller name and choose Properties.
6. On the Controller Properties dialog box, click the Internet Protocol tab.
You can use an SD card to set the IP address for a CompactLogix 5370 controller.
Using the SD card to set the IP address eliminates the need for software to
complete this task.
IMPORTANT Setting the IP address from an SD card does not require software during the
power-up process. However, you must have previously saved the project to the
SD card.
The option to set a CompactLogix 5370 controller’s IP address via an SD card at
power-up is only one part of loading an entire project to the controller from the
SD card.
Use this option carefully. For example, the SD card may contain a desirable IP
address as part of an undesirable project, for example, a project that is older
than the project currently used on the controller.
These requirements apply when using the SD card to set the IP address on a
CompactLogix 5370 controller:
• The project stored on the SD card is configured with the Load Image
parameter set to On Power Up.
For more information on using the SD card, see Chapter 12, Use a Secure Digital
Card on page 301.
Change a Controller’s You may need to change a CompactLogix 5370 controller’s IP address after
system operation has begun. In this case, the controller already has a valid IP
IP Address address assigned to it but you need to change that IP address.
IMPORTANT You cannot use any of these tools to change a controller’s IP address:
• Bootstrap Protocol (BOOTP) server
• Dynamic Host Configuration Protocol (DHCP) server
Consider these factors when you determine how to change the controller’s
IP address:
• Network isolation from, or integration into, the plant/enterprise network
However, you can use the BOOTP/DHCP server only to set the
controller’s IP address and not to change it. If you decide to change the
controller’s IP address and want to use a BOOTP/DHCP server so as to
limit the possibility of assigning duplicate IP addresses, you must first clear
the IP address.
After clearing the IP address, use the steps described at Use the BOOTP
Server to Set the Controller’s IP Address on page 78 or Use the DHCP
Server to Set the Controller’s IP Address on page 82 to set the controller’s
IP address.
IMPORTANT The steps in Use RSLinx Classic Software to Set the Controller’s IP Address on
page 83 describe how to assign an IP address for a CompactLogix 5370
controller that does not have a valid IP address.
The steps in this section describe how to change the IP address on a
CompactLogix 5370 controller that already has a valid IP address assigned to it.
The graphics in this section show how to change the IP address for a
1769-L36ERM controller. The same steps apply to other CompactLogix 5370
controllers with slight variations in screens.
2. Click the Port Configuration tab when the Module Configuration dialog
box appears.
IMPORTANT If you click Dynamic, on a power cycle, the controller clears the
current IP configuration and resumes sending BOOTP or DHCP
requests, depending on the controller configuration.
5. Click OK.
IMPORTANT The steps in Use Logix Designer Application to Set the Controller’s IP Address on
page 85 describe how to assign an IP address for a CompactLogix 5370
controller that does not have a valid IP address.
The steps in this section describe how to change the IP address on a
CompactLogix 5370 controller that already has a valid IP address assigned to it.
You can change a CompactLogix 5370 controller’s IP address via Logix Designer
application over a USB or EtherNet/IP network connection.
The graphics in this section show how to change the IP address for a
1769-L18ERM-BB1B controller over a USB connection. The same steps apply
to other CompactLogix 5370 controllers with slight variations in screens.
You could also right-click the Ethernet node in the I/O Configuration
section and choose Properties. The Controller Properties dialog box
appears on the Internet Protocol tab.
6. Click OK.
You can use an SD card to change the IP address for a CompactLogix 5370
controller when controller power is cycled. Using the SD card to change the IP
address eliminates the need for software to complete this task.
IMPORTANT Setting the IP address from an SD card does not require software during the
power-up process. However, you must have previously saved the project to the
SD card.
These requirements apply when using the SD card to change the IP address on a
CompactLogix 5370 controller:
• The project stored on the SD card includes a different IP address for the
CompactLogix 5370 controller than the IP address currently in use on the
physical controller housing the SD card.
• The project stored on the SD card is configured with the Load Image
parameter set to On Power Up.
For more information on using the SD card, see Chapter 12, Use a Secure Digital
Card on page 301.
Load the Controller Firmware You must download the current firmware before you can use the
CompactLogix 5370 controller.
IMPORTANT Do not interrupt a firmware upgrade while it is in process. Doing so may cause
the CompactLogix 5370 controller’s firmware revision to revert to its
out-of-the-box revision level, that is, 1.xxx.
IMPORTANT Be aware that the controller firmware revision loaded via the ControlFLASH
utility or the AutoFlash option may be overwritten after future controller
power cycles if the conditions described in Use the Secure Digital Card to Load
Firmware on page 102 exist.
The firmware is available with the application or you can download it from the
support website. Go to http://www.rockwellautomation.com/support.
You can use the ControlFLASH utility to load firmware through a USB or
EtherNet/IP network connection. We recommend the following when you load
firmware via the ControlFLASH utility:
• Use a USB connection to load the firmware.
• Remove the SD card, if one is installed in the controller.
IMPORTANT These steps show a 1769-L36ERM controller. The same steps apply to other
CompactLogix 5370 controllers with slight variations in screens.
IMPORTANT If you expand the controller, that is, expand the network beyond the
first instance in which it appears on the left side of the screen, you may
experience issue when performing the firmware update.
7. Choose the revision level to which you want to update the controller and
click Next.
8. To start the update of the controller, click Finish and then click Yes.
Before the firmware upgrade begins, you see the following dialog box. Take
the appropriate action for your application. In this example, the upgrade
continues when OK is clicked.
After the controller is updated, the status dialog box displays the message
Update complete.
9. Click OK.
10. To close the ControlFLASH utility, click Cancel and then click Yes.
After the controller firmware upgrade process is complete, the controller may
execute a firmware upgrade for its embedded I/O module.
Remember these points regarding the automatic firmware upgrade for the
embedded I/O module:
• The firmware upgrade occurs on the embedded I/O module only, not the
local expansion modules.
If you need to update the firmware revision on any 1734 POINT I/O
modules that will be used as local expansion modules, you must do so
before installing them in the CompactLogix 5370 L1 control system.
• Do not cycle power to the controller while the firmware upgrade for
embedded I/O module is taking place.
IMPORTANT These steps show a 1769-L36ERM controller. The same steps apply to other
CompactLogix 5370 controllers with slight variations in screens.
1. Make sure the appropriate network connection is made and your network
driver is configured in RSLinx Classic software.
2. Create a controller project.
3. Click RSWho to specify the controller path.
You may also choose to click Update Firmware to complete this process. If
you do so, skip to step step 6.
A dialog box appears indicating that the project revision and controller
firmware revision are different.
6. Use the checkbox and pull-down menu to choose your controller and
firmware revision.
7. Click Update.
Before the firmware upgrade begins, you may be warned about your
controller missing its SD card. Take the appropriate action, typically
clicking OK.
• You must have saved the project to the SD card before the power cycle.
For more information on using the SD card, see Chapter 12, Use a Secure Digital
Card on page 301.
Select the Controller’s CompactLogix 5370 controllers have slightly different front designs and mode
switch placements.
Operating Mode
WARNING: When you change switch settings 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.
RUN
RUN
REM
PROG
REM
PROG
L27ERM
0 1 2 3 4 5 6 7 A0 B0 Z0
QBFC1B
SOURCE
IN
24VDC
SINK\
INPUT
DC
HIGH SPEED
A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
8 9 10 11 12 13 14 15 1 3 OK
DC IN HSC
00 08 A0+ A0-
01 09 B0+ B0-
02 10 Z0+ Z0-
A1+ A1-
RUN
03 11
04 12 B1+ B1-
RUN
05 13 Z1+ Z1- REM
REM +V +V
06 14
PROG 07 15
OUT
0
OUT
2 PROG
COM COM OUT 0UT
0 1 1 3
NC NC COM COM
V V
+V +V in in
0+ 2+
I I
00 08 in in
0+ 2+
V/I V/I
01 09 in in
0- 2-
CJC V
02 10 + in
3+
CJC I
03 11 - in
3+
V V/I
04 12 in in
1+ 3-
I V/I
05 13 in in
1+ 1-
V V
06 14 OUT OUT
0+ 1+
I I
07 15 OUT in
0+ 1+
COM COM COM COM
0 1
DC OUT ANALOG
+24VDC COM FG
L33ER
RUN NS
FORCE LINK 1
I/O LINK 2
OK SD
RUN
REM RUN
PROG
REM
PROG
00:00:BC:2E:69:F6
1 (Front)
2 (Rear)
Use the controller’s mode switch to set the CompactLogix 5370 controller’s
operating mode.
Mode Switch Description
Position
Run You can perform these tasks:
• Upload projects.
• Run the program and enable outputs.
You cannot perform these tasks:
• Update controller firmware.
• Create or delete tasks, programs, or routines.
• Create or delete tags or edit online.
• Import a program to the controller.
• Change the controller’s port configuration, advanced port configuration, nor network configuration settings.
• Change controller configuration parameters directly set for operation on a device-level ring (DLR) network topology.
Prog You can perform these tasks:
• Update controller firmware.
• Disable outputs.
• Upload/download projects.
• Create, modify, and delete tasks, programs, or routines.
• Change the controller’s port configuration, advanced port configuration, nor network configuration settings.
You cannot perform these tasks:
• Use the controller to execute (scan) tasks.
Notes:
Topic Page
CompactLogix 5370 Control System Components 108
Controller Functionality 109
Example System Configurations 111
Among the features the CompactLogix 5370 controllers support are dual
EtherNet/IP ports on each controller and support for Integrated Motion over an
EtherNet/IP network on some CompactLogix 5370 controllers.
CompactLogix 5370 Control Table 2 describes components a CompactLogix 5370 controller uses in a typical
control system.
System Components
Table 2 - CompactLogix 5370 Control System Components
System Component Product Family
CompactLogix 5370 L1 Controllers CompactLogix 5370 L2 Controllers CompactLogix 5370 L3 Controllers
Controller One of the controllers documented in this publication
Power supply External power supply connected to the External power supply connected to the One of the following 1769 Compact I/O power
controller’s embedded 24V DC nominal input, controller’s embedded 24V DC Input, isolated supplies:
nonisolated power supply. The power supply power supply • 1769-PA2
has a 10…28.8 input range.
• 1769-PB2
• 1769-PA4
• 1769-PB4
Communication networks Any of the following: Any of the following:
components • EtherNet/IP network via built-in EtherNet/ • EtherNet/IP network via built-in EtherNet/IP network ports
IP network ports • DeviceNet network via a 1769-SDN module
• USB connection for programming and • USB connection for programming and firmware upgrades only
firmware upgrades only
Software • One of the following:
– RSLogix 5000 software, version 20.xx.xx, - For CompactLogix 5370 controllers using firmware revision 20.xxx
– Logix Designer application, version 21.00.00 or later, - For CompactLogix 5370 controllers using firmware revision 21.000 or later
• RSLinx Classic software, version 2.59.xx or later
• RSNetWorx™ for DeviceNet software, version 11.00.00 or later
IMPORTANT: This software is not used with CompactLogix 5370 L1 controllers because they do not offer DeviceNet connectivity.
Secure Digital (SD) card for • 1784-SD1 card - Ships with CompactLogix 5370 controller and offers 1 GB of memory
external nonvolatile memory • 1784-SD2 card - Available for separate purchase and offers 2 GB of memory
I/O modules • 16 embedded 24V DC digital input points - • 16 embedded 24V DC digital input points • Local expansion modules- 1769 Compact
The nominal input voltage is 24V DC but the • 16 embedded 24V DC digital output points I/O modules
operating range is 10…28.8V DC. • Distributed I/O - Multiple I/O module
• 1769-L24ER-QBFC1B and
• 16 embedded 24V DC digital output points - 1769-L27ERM-QBFC1B controllers only product lines over DeviceNet and
The nominal input voltage is 24V DC but the – Four embedded high-speed counters EtherNet/IP networks
operating range is 10…28.8V DC. – Four embedded universal analog input
• Local expansion modules- 1734 POINT I/O points
modules – Two embedded analog output points
• Distributed I/O - Multiple I/O module • Local expansion modules- 1769 Compact
product lines over an EtherNet/IP network I/O modules
• Distributed I/O - Multiple I/O module
product lines over DeviceNet and
EtherNet/IP networks
Reset button If held in during controller powerup, it will clear the user program from the controller’s internal memory.
Controller Functionality Table 3 describes functionality available with CompactLogix 5370 controllers.
Table 3 - CompactLogix 5370 Controller Functionality
Cat. No. Controller Tasks Programs Internal Energy EtherNet/IP Power Supply On-board User Local I/O Module
Supported Supported Per Storage Solution Network Distance Rating Memory Size Support
Task Topology
Support
1769-L16ER-BB1B As many as six
384 KB 1734 POINT I/O
modules(2)
NA
1769-L18ER-BB1B As many as eight
512 KB 1734 POINT I/O
1769-L18ERM-BB1B modules(2)
1769-L24ER-QB1B
Support the 768 KB As many as four
1769-L24ER-QBFC1B following See footnote Compact I/O
topologies: below(1) modules
1769-L27ERM-QBFC1B Yes - Eliminating 1 MB
32 100 the need for a • Device-level
1769-L30ER battery ring (DLR)
As many as eight
1769-L30ER-NSE • Linear 1 MB Compact I/O
• Traditional star modules
1769-L30ERM
1769-L33ER 4 As many as 16
2 MB Compact I/O
1769-L33ERM modules
1769-L36ERM As many as 30
3 MB Compact I/O
modules
(1) CompactLogix 5370 L2 controllers have an embedded power supply. Therefore, you do not need to consider power supply distance rating when installing the controller. The Compact I/O modules used
as local expansion modules in a CompactLogix 5370 L2 control systems operate on a CompactBus and do have a power supply distance rating you must consider when installing those modules.
For more information on power supply distance rating with respect to using Compact I/O modules in a CompactLogix 5370 L2 control system, see page 134 and page 216.
(2) IMPORTANT: You can use up to the maximum number of 1734 POINT I/O modules with the CompactLogix 5370 L1 controllers listed in Table 1, as long as the total current drawn by the modules does not
exceed the available POINTBus backplane current of 1 A. If you need to use more local expansion modules than the POINTBus backplane current supports, you can install a 1734-EP24DC POINT I/O
expansion power supply between local expansion modules to increase the POINTBus backplane power and meet your system requirements.
After you turn off power, the controller’s OK status indicator transitions from Green to
Solid Red to OFF.
There is no visual indication of when the 15 minutes has expired. You must track that
time period.
Some applications that require the installed controller deplete its residual stored
energy to specific levels before transporting it into or out of your application.
This may include other devices that also require a wait time before removing
them. See those products’ documentation for more information.
EtherNet/IP Network
IMPORTANT Figure 4 and figure 2 show CompactLogix 5370 controllers used in a DLR
network topology on an EtherNet/IP network. You can also use
CompactLogix 5370 controllers in linear or star EtherNet/IP network
topologies.
For more information on the other EtherNet/IP network topologies, see
Communicate over Networks on page 115.
Some of the CompactLogix 5370 controllers support Integrated Motion over an
EtherNet/IP network, if desired. For more information on using Integrated
Motion over an EtherNet/IP network, see Chapter 11, Develop Integrated
Motion over an EtherNet/IP Network Applications on page 289.
002 1734-AENTR
POINT I O
Module
Status
Network
Activity
Network
Status
Point Bus
Link 1 Status
Activity/
Status System
Power
Field
Power
IP ADDRESS
Link 2
Activity/
Status
Kinetix 350 Drive Connected Via a 1734-AENTR POINT I/O Adapter 1794-AENTR FLEX™ I/O Adapter
1783-ETAP EtherNet/IP Tap with POINT I/O Modules with FLEX I/O Modules
SOURCE
IN
24VDC
0 1 2 3 4 5 6 7 A0 B0 Z0
SINK\
INPUT
DC
HIGH SPEED
A1 B1 Z1
QBFC1B
COUNTER
8 9 10 11 12 13 14 15
SOURCE
IN
24VDC
SINK\
INPUT
DC
HIGH SPEED
A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
8 9 10 11 12 13 14 15 1 3 OK
8 9 10 11 12 13 14 15 1 3 OK
DC IN HSC
00 08 A0+ A0-
01 09 B0+ B0-
02 10 Z0+ Z0-
03 11 A1+ A1-
04 12 B1+ B1-
05 13 Z1+ Z1-
06 14 +V +V
OUT OUT
07 15 0 2
COM COM OUT 0UT
0 1 1 3
NC NC COM COM
V V
+V +V in in
0+ 2+
I I
00 08 in in
0+ 2+
V/I V/I
01 09 in in
0- 2-
CJC inV
02 10 + 3+
CJC inI
03 11 - 3+
V V/I
04 12 in in
1+ 3-
00:00:BC:2E:69:F6 05 13
I V/I
in in
1+ 1-
V V
06 14 OUT OUT
0+ 1+
I I
07 15 OUT in
0+ 1+
COM COM COM COM
0 1
DC OUT ANALOG
+24VDC
+24VDC COM
COM FG
FG
002 1734-AENTR
POINT I O
Module
Status
Network
Activity
Network
Status
Point Bus
Link 1 Status
Activity/
Status System
Power
Field
Power
IP ADDRESS
Link 2
Activity/
Status
Kinetix 350 Drive Connected Via a 1734-AENTR POINT I/O™ Adapter 1794-AENTR FLEX I/O Adapter with
1783-ETAP EtherNet/IP Tap with POINT I/O Modules FLEX I/O Modules
00:00:BC:2E:69:F6
1 (Front)
(Front)
2 (Rear)
002 1734-AENTR
POINT I O
Module
Status
Network
Activity
Network
Status
Point Bus
Link 1 Status
Activity/
Status System
Power
Field
Power
IP ADDRESS
Link 2
Activity/
Status
Kinetix 6500 Drives 1734-AENTR POINT I/O Adapter 1794-AENT FLEX I/O Adapter Connected Via
with Motors with POINT I/O Modules a 1783-ETAP EtherNet/IP Tap
DeviceNet Network
IMPORTANT CompactLogix 5370 L2 and L3 controllers can send messages to devices on the
DeviceNet network; however, these controllers cannot receive messages
from those devices on the DeviceNet network.
Computer with DeviceNet Connection 1769-L24ER-QB1B Control System with 1769-SDN Scanner Module
L24ER
0 1 2 3 4 5 6 7
QB1B
SOURCE
24VDC
SINK\
INPUT
DC
8 9 10 11 12 13 14 15
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7
8 9 10 11 12 13 14 15
DC IN
00 08
01 09
02 10
03 11
04 12
05 13
06 14
07 15
COM COM
0 1
NC NC
+V +V
00 08
01 09
02 10
03 11
04 12
00:00:BC:2E:69:F6 05 13
06 14
07 15
COM COM
0 1
DC OUT
+24VDC COM FG
Adapter
Status
DeviceNet
Status
PointBus
Status
1734-ADN
System
Power
DeviceNet
Power
00:00:BC:2E:69:F6
1 (Front)
(Front)
2 (Rear)
Adapter
Status
DeviceNet
Status
PointBus
Status
1734-ADN
System
Power
DeviceNet
Power
Notes:
Topic Page
EtherNet/IP Network Communication 116
DeviceNet Network Communication 131
EtherNet/IP Network The EtherNet/IP network offers a full suite of control, configuration and data
collection services by layering the Common Industrial Protocol (CIP) over the
Communication 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.
For more information on socket interface transactions, see Socket Interface with
CompactLogix 5370 Controllers on page 126.
Available Software
You use the software listed in the following table with a CompactLogix 5370
controller on an EtherNet/IP network.
Software Required Version Functions Required
RSLogix 5000 Version 20.xx.xx - For CompactLogix • Configure the CompactLogix
5370 controllers using firmware project.
revision 20.xxx. • Define EtherNet/IP communication.
Studio 5000 Version 21.00.00 or later - For • Change IP address for devices on
environment CompactLogix 5370 controllers using network, including the
firmware revision 21.000 or later. CompactLogix 5370 controller.
Yes
RSLinx Classic Version 2.59 or later • Assign or change IP addresses to
devices on an EtherNet/IP network.
• Configure communication devices.
• Provide diagnostics.
• Establish communication between
devices.
BOOTP/DHCP Most current version is installed with Assign IP addresses to devices on an No
utility RSLinx Classic software installation EtherNet/IP network.
When configuring your CompactLogix 5370 control system, you must account
for the number of Ethernet nodes you include in the I/O configuration section of
your project. CompactLogix 5370 controllers have limits on the number of nodes
they support in the I/O configuration section.
IMPORTANT While CompactLogix 5370 controllers offer the option of using Ethernet node
count to effectively and efficiently design a control system, the controllers do
have connection limits on an EtherNet/IP network.
For more information on how to design EtherNet/IP network use in your
CompactLogix 5370 control system, see these resources:
• The EtherNet/IP Capacity Tool available at http://
www.rockwellautomation.com/solutions/integratedarchitecture/
resources3.html#enetpredict.
The EtherNet/IP Capacity Tool helps you in the initial layout of your
EtherNet/IP network.
Any devices you add directly to the local Ethernet I/O configuration are counted
toward the controller’s node limitation. The following are example devices that
are added to the I/O configuration section in your project and must be counted:
• Remote communication adapters
• I/O modules directly connected to the EtherNet/IP network, for example
the 1732E-IB16M12R ArmorBlock® EtherNet/IP module
• Motion devices, such as drives
• Remote controllers
• HMI devices that are included in the I/O configuration section, for
example, PanelView Plus terminals
• Linking devices, such as the 1788-EN2DN, Ethernet-to-DeviceNet
linking device
• Third-party devices that are directed connected to the
EtherNet/IP network
The following devices are not added to the I/O configuration section in your
project and are not counted among the total number of nodes:
• Computer
• HMI that are not added to the I/O configuration section, for example,
PanelView Plus terminals
• MSG instructions
A DLR network topology is a single-fault tolerant ring network intended for the
interconnection of automation devices. A DLR network is comprised of
Supervisor (Active and Backup) nodes and Ring nodes.
T
IMPORTANT The topology graphics shown in this section are examples of applications that
use DLR network topologies only.
We recommend you exercise caution if you consider designing an application
that includes connecting a DLR topology with a linear or star network topology.
For more information on using a DLR network topology, see the EtherNet/IP
Embedded Switch Technology Application Guide, publication ENET-AP005.
002 1734-AENTR
POINT I O
Module
Status
Network
Activity
Network
Status
Point Bus
Link 1 Status
Activity/
Status System
Power
Field
Power
IP ADDRESS
Link 2
Activity/
Status
Kinetix 350 Drive Connected Via a 1734-AENTR POINT I/O Adapter 1794-AENTR FLEX I/O Adapter with
1783-ETAP EtherNet/IP Tap with POINT I/O Modules FLEX I/O Modules
IN
24VDC
0 1 2 3 4 5 6 7 A0 B0 Z0
SINK\
INPUT
DC
HIGH SPEED
A1 B1 Z1
QBFC1B
COUNTER
8 9 10 11 12 13 14 15
SOURCE
IN
24VDC
SINK\
INPUT
DC
HIGH SPEED
A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
8 9 10 11 12 13 14 15 1 3 OK
8 9 10 11 12 13 14 15 1 3 OK
DC IN HSC
00 08 A0+ A0-
01 09 B0+ B0-
02 10 Z0+ Z0-
03 11 A1+ A1-
04 12 B1+ B1-
05 13 Z1+ Z1-
06 14 +V +V
OUT OUT
07 15 0 2
COM COM OUT 0UT
0 1 1 3
NC NC COM COM
V V
+V +V in in
0+ 2+
I I
00 08 in in
0+ 2+
V/I V/I
01 09 in in
0- 2-
CJC inV
02 10 + 3+
CJC inI
03 11 - 3+
V V/I
04 12 in in
1+ 3-
00:00:BC:2E:69:F6 05 13
I V/I
in in
1+ 1-
V V
06 14 OUT OUT
0+ 1+
I I
07 15 OUT in
0+ 1+
COM COM COM COM
0 1
DC OUT ANALOG
+24VDC
+24VDC COM
COM FG
FG
002 1734-AENTR
POINT I O
Module
Status
Network
Activity
Network
Status
Point Bus
Link 1 Status
Activity/
Status System
Power
Field
Power
IP ADDRESS
Link 2
Activity/
Status
Kinetix 350 Drive Connected Via a 1734-AENTR POINT I/O Adapter 1794-AENTR FLEX I/O Adapter with
1783-ETAP EtherNet/IP Tap with POINT I/O Modules FLEX I/O Modules
00:00:BC:2E:69:F6
1 (Front)
(Front)
2 (Rear)
002 1734-AENTR
POINT I O
Module
Status
Network
Activity
Network
Status
Point Bus
Link 1 Status
Activity/
Status System
Power
Field
Power
IP ADDRESS
Link 2
Activity/
Status
Kinetix 6500 Drives 1734-AENTR POINT I/O Adapter 1794-AENT FLEX I/O Adapter Connected Via
with Motors with POINT I/O Modules a 1783-ETAP EtherNet/IP Tap
002 1734-AENTR
POINT I O
Module
Status
IP ADDRESS
Computer with Ethernet Port
Link 2
Activity/
Status
1769-L18ERM-BB1B Kinetix 350 Drive Connected via Kinetix 350 Drive Connected via
Control System a 1783-ETAP EtherNet/IP Tap a 1783-ETAP EtherNet/IP Tap
002 1734-AENTR
POINT I O
Module
Status
QB1B
SINK\
INPUT
DC
8 9 10 11 12 13 14 15
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7
8 9 10 11 12 13 14 15
DC IN
00 08
01 09
02 10
03 11
04 12
05 13
06 14
07 15
COM COM
0 1
NC NC
+V +V
00 08
01 09
02 10
03 11
04 12
00:00:BC:2E:69:F6 05 13
06 14
07 15
COM COM
0 1
DC OUT
+24VDC COM FG
POINT I O
Module
Status
Network
Activity
Network
Status
Point Bus
Link 1 Status
Activity/
Status System
Power
Field
Power
IP ADDRESS
Computer Link 2
Activity/
Status
Computer 1769-L18ERM-BB1B
Control System
EtherNet/IP Module 4 3
2 1
L27ERM 0 1 2 3 4 5 6 7 A0 B0 Z0
SOURCE
IN
24VDC
0 1 2 3 4 5 6 7 A0 B0 Z0
SINK\
INPUT
DC
HIGH SPEED
A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
SOURCE
QBFC1B
IN
24VDC
SINK\
INPUT
DC
HIGH SPEED
A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
8 9 10 11 12 13 14 15 1 3 OK
8 9 10 11 12 13 14 15 1 3 OK
DC IN
Computer
HSC
00 08 A0+ A0-
1769-L27ERM-QBFC1B
01 09 B0+ B0-
02 10 Z0+ Z0-
03 11 A1+ A1-
04 12 B1+ B1-
05 13 Z1+ Z1-
06 14 +V +V
Control System
OUT OUT
07 15 0 2
COM COM OUT 0UT
0 1 1 3
NC NC COM COM
V V
+V +V in in
0+ 2+
I I
00 08 in in
0+ 2+
V/I V/I
01 09 in in
0- 2-
CJC inV
02 10 + 3+
CJC inI
03 11 - 3+
V V/I
04 12 in in
1+ 3-
00:00:BC:2E:69:F6 05 13
I V/I
in in
1+ 1-
V V
06 14 OUT OUT
0+ 1+
I I
07 15 OUT in
0+ 1+
COM COM COM COM
0 1
DC OUT ANALOG
+24VDC
+24VDC COM
COM FG
FG
Computer 1769-L33ERM
Control System
00:00:BC:2E:69:F6
1 (Front)
(Front)
2 (Rear)
The socket interface is implemented via the Socket Object. CompactLogix 5370
controllers communicate with the Socket Object via MSG instructions. All
CompactLogix 5370 controllers must use unconnected MSG instructions with
socket interfaces.
The Socket Object services lets the controller perform these actions:
• Open connections
• Accept incoming connections
• Send data
• Receive data
To communicate with another device, you must understand the other device’s
application protocol. The CompactLogix 5370 controller has no application
protocol knowledge. The controller makes the socket services available to its
program.
The options available for UDP and TCP send and receive services are described
in this table.
Type Communication Send (Write) Receive (Read)
UDP Unicast Yes Yes
Multicast Yes Yes
Broadcast Yes Yes
TCP Unicast Yes Yes
Multicast N/A N/A
Broadcast N/A N/A
You must have a listen socket for each TCP port number that accepts
connections. Multiple TCP server sockets can share a listen socket if the
connections are made to the same port number.
You can partition the available socket instances between UDP and TCP sockets
in these ways:
• Use all instances for client TCP connections.
• Use one instance to listen for incoming TCP connections and then accept
the remaining connections from other devices.
• Perform both TCP client and server operations.
• Perform both TCP and UDP operations.
Once you open a connection on a client socket instance, you cannot use the same
socket instance to accept incoming connections. Similarly, if you accept
connections on a socket instance, you cannot then use the instance to open
outgoing connections. This behavior is consistent with standard socket API
behavior.
IMPORTANT This section describes only one of the socket service available with your
CompactLogix 5370 controller.
For more information on all socket services, see the EtherNet/IP Socket
Interface Application Technique, publication ENET-AT002.
IMPORTANT Before you can configure the MSG instruction, you must create a user-defined
data type (UDT) that is available in the Source Element parameter. See MSG
Source Element for more information on how to create a UDT.
You must also create a user-defined data type (UDT) to use this service. This
example graphic shows the UDT screen. The parameter values for this MSG type
are defined in Table 6 on page 130.
Some EtherNet/IP devices do not support QoS technology unless the device’s
firmware is upgraded to a required minimum firmware revision level. For
example, the ControlLogix® 1756-ENBT communication module must use
firmware revision 4.005 or later to support QoS technology.
DeviceNet Network The CompactLogix 5370 L2 and L3 controllers communicate with other devices
over the DeviceNet network via a Compact I/O 1769-SDN DeviceNet scanner
Communication module. The DeviceNet network uses the Common Industrial Protocol (CIP) to
provide the control, configuration, and data collection capabilities for industrial
devices.
Available Software
The software applications listed in this table are required when using a
CompactLogix 5370 L2 or L3 controller on a DeviceNet network.
Software Required Version Functions
RSLogix 5000 20.xx.xx - For CompactLogix 5370 controllers
using firmware revision 20.xxx.
Studio 5000 21.00.00 or later - For CompactLogix 5370 Configure the CompactLogix project
environment controllers using firmware revision 21.000 or
later.
RSLinx Classic 2.59.00 or later(1), (2) • Configure communication devices
• Provide diagnostics
• Establish communication between devices
RSNetWorx for One of the following: • Configure DeviceNet devices
DeviceNet • 11.00.00 or later if used with RSLogix • Define the scanlist for the
5000 software, version 20.xx.xx DeviceNet network
• 21.00.00 or later if used with RSLogix
5000 software, version 21.00.00 or later
(1) CompactLogix 5370 L2 controllers require RSLinx Classic software, version 2.59.01 or later.
(2) We recommend that you use RSLinx Classic software, version 3.51.00 or later, with Studio 5000 environment, version 21.00.00
or later.
Computer with DeviceNet Connection 1769-L24ER-QB1B Control System with 1769-SDN Scanner Module
L24ER
0 1 2 3 4 5 6 7
QB1B
SOURCE
24VDC
SINK\
INPUT
DC
8 9 10 11 12 13 14 15
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7
8 9 10 11 12 13 14 15
DC IN
00 08
01 09
02 10
03 11
04 12
05 13
06 14
07 15
COM COM
0 1
NC NC
+V +V
00 08
01 09
02 10
03 11
04 12
00:00:BC:2E:69:F6 05 13
06 14
07 15
COM COM
0 1
DC OUT
+24VDC COM FG
Adapter
Status
DeviceNet
Status
PointBus
Status
1734-ADN
System
Power
DeviceNet
Power
00:00:BC:2E:69:F6
1 (Front)
(Front)
2 (Rear)
Adapter
Status
DeviceNet
Status
PointBus
Status
1734-ADN
System
Power
DeviceNet
Power
1606-XLDNET DeviceNet Power Supply E3 Overload Relay 1734-ADN POINT I/O DeviceNet
Adapter with POINT I/O Modules
Power supply distance rating is the number of slots a 1769-SDN scanner module
can be installed away from the power supply. The 1769-SDN scanner module has
a power supply distance rating of four. Therefore, your CompactLogix 5370 L2
or L3 control system can include up to three modules between the 1769-SDN
scanner module and the power supply.
Using the 1769-SDN scanner module’s power supply distance rating as a design
consideration differs by CompactLogix L2 controller catalog number.
Additionally, the controller has embedded I/O modules that prevent installation
of the 1769-SDN scanner module directly to the right of the embedded power
supply. CompactLogix 5370 L2 control systems have one or two embedded I/O
modules as described below:
While the embedded I/O modules are not considered local expansion modules,
you still must include each embedded I/O module in the module slot count when
determining where to install the 1769-SDN scanner module as a local expansion
module.
The farthest local expansion module slot where you can install the 1769-SDN
scanner module in a CompactLogix 5370 L2 control system is module slot
number two or three as determined by the controller catalog number used in the
control system.
Table 7 describes the farthest local expansion module slot where you can install a
1769-SDN scanner module and meet its power supply distance rating
requirement.
Table 7 - Example CompactLogix 5370 L2 Control Systems with a 1769-SDN Scanner Module
Controller Cat. No. Number of Embedded 1769-SDN Scanner Module Power Supply Distance Rating Calculation Impact
I/O Modules
1769-L24ER-QB1B 1 The embedded I/O module is the first module in the module count. At its maximum power supply distance rating, the
1769-SDN scanner module can be installed in slot 3 of the local expansion modules, as shown below.
L24ER
0 1 2 3 4 5 6 7
QB1B
SOURCE
24VDC
SINK\
INPUT
DC
8 9 10 11 12 13 14 15
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7
8 9 10 11 12 13 14 15
DC IN
00 08
01 09
02 10
03 11
04 12
05 13
06 14
07 15
COM COM
0 1
NC NC
+V +V
00 08
01 09
02 10
03 11
04 12
00:00:BC:2E:69:F6 05 13
06 14
07 15
COM COM
0 1
DC OUT
+24VDC COM FG
Three modules between the power supply and the 1769-SDN scanner module.
With this controller catalog number, you can only install up to two local expansion modules
between the controller and the 1769-SDN scanner module.
Table 7 - Example CompactLogix 5370 L2 Control Systems with a 1769-SDN Scanner Module
Controller Cat. No. Number of Embedded 1769-SDN Scanner Module Power Supply Distance Rating Calculation Impact
I/O Modules
1769-L24ER-QBFC1B 2 The embedded I/O modules are the first two modules in the module count. At its maximum power supply distance rating,
1769-L27ERM-QBFC1B the 1769-SDN scanner module can be installed in slot 2 of the local expansion modules, as shown below.
L27ERM 0 1 2 3 4 5 6 7 A0 B0 Z0
SOURCE
IN
24VDC
0 1 2 3 4 5 6 7 A0 B0 Z0
SINK\
INPUT
DC
HIGH SPEED
QBFC1B A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
SOURCE
IN
24VDC
SINK\
INPUT
DC
HIGH SPEED
A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
8 9 10 11 12 13 14 15 1 3 OK
8 9 10 11 12 13 14 15 1 3 OK
DC IN HSC
00 08 A0+ A0-
01 09 B0+ B0-
02 10 Z0+ Z0-
03 11 A1+ A1-
04 12 B1+ B1-
05 13 Z1+ Z1-
06 14 +V +V
OUT OUT
07 15 0 2
COM COM OUT 0UT
0 1 1 3
NC NC COM COM
V V
+V +V in in
0+ 2+
I I
00 08 in in
0+ 2+
V/I V/I
01 09 in in
0- 2-
CJC inV
02 10 + 3+
CJC inI
03 11 - 3+
V V/I
04 12 in in
1+ 3-
00:00:BC:2E:69:F6 05 13
I V/I
in in
1+ 1-
V V
06 14 OUT OUT
0+ 1+
I I
07 15 OUT in
0+ 1+
COM COM COM COM
0 1
DC OUT ANALOG
+24VDC
+24VDC COM
COM FG
FG
Three modules between the power supply and the 1769-SDN scanner module.
With this controller catalog number, you can only install one local expansion modules
between the controller and the 1769-SDN scanner module.
IMPORTANT When counting I/O modules to determine the 1769-SDN scanner module
placement in a 1769-L24ER-QBFC1B or 1769-L27ERM-QBFC1B control system,
the embedded I/O module appearance is different between the physical
appearance and the modules’ appearance the application.
The physical appearance is shown above. The second module is two rows of
termination points below a single set of status indicators.
In the application, the second embedded I/O module appears as two modules
in the Controller Organizer each with their own slot number, that is [2] and [3].
When the 1769-SDN scanner module is installed in the farthest local expansion
module slot possible, that is the fourth module in the control system, it
appears with a [5] designation in the Controller Organizer, as shown below.
1769-SDN scanner module is shown as module [5] in this location but considered the fourth
module when counting modules to meet power supply distance rating requirements.
In the local bank, the controller must be the leftmost device in the system and
you can only install up to three modules between the controller and the power
supply. Therefore, any 1769-SDN scanner modules that are installed to the left of
the power supply in the local bank, are in a module slot that meets the module’s
power supply distance rating requirements.
CompactLogix 5370 L3 control systems also support the use of additional banks
for the system’s local expansion modules. Every additional bank requires a 1769
Compact I/O power supply. The bank can be designed with local expansion
modules on either side of the power supply.
In this case, you must install the 1769-SDN scanner module with no more three
Compact I/O modules between the scanner module and the power, regardless of
whether the modules are installed to the left or right of the power supply.
Local Bank
00:00:BC:2E:69:F6
1 (Front)
2 (Rear)
Additional Bank
In a local or additional bank, the modules installed on either side of the power
supply cannot draw more current than the power supply can supply. This
requirement partially dictates module placement on the bank.
For example, if a bank uses a 1769-PA2 Compact I/O power supply, each side of
the bank has a current capacity of 1A at 5 V DC and 0.4A at 24 V DC. Because a
1769-SDN scanner module has a current draw of 440 mA at 5 V DC and 0 mA
at 24 V DC, you can only install up to two scanner modules on each side of the
power supply in the bank in this case.
For more information on 1769 Compact I/O power supply maximum current
capacity and calculations you can use to design the modules used in local or
additional banks, see Calculate System Power Consumption on page 244.
Topic Page
Select I/O Modules 139
Validate I/O Layout 156
Use the Event Task 161
Configure I/O 165
Electronic Keying 167
Configure Distributed I/O Modules on an EtherNet/IP Network 173
Monitor I/O Modules 176
Select I/O Modules CompactLogix 5370 L1 control systems offer these I/O module options:
• Embedded I/O Modules
• Local Expansion Modules
• Distributed I/O Modules over an EtherNet/IP Network
You must connect a separate external power source to the FP+ and FP- terminals
on the controller’s removable connector to power the field-side circuitry of the
embedded I/O modules and the local expansion modules.
That is, power connections to the FP+ and FP- terminals provides power to input
and output devices connected to the controller’s embedded I/O modules or local
expansion modules. For example, input or output devices, such as a bar code
scanner.
The controller’s embedded I/O and local expansion modules’ field-side power is
24V DC nominally with an input range of 10…28.8V DC.
IMPORTANT The CG terminal on the removable connector connects to the DIN rail via a
grounding clip on the back of the controller. The controller is grounded once it
is installed on a DIN rail as described in Mount the System on page 22.
• The external 24V DC power source that is connected to the FP+ and FP-
terminals must be separate from the power source dedicated to powering
the controller via the VDC+ and VDC- terminals.
• You can use the external 24V DC power source that provides power to the
FP+ and FP- terminals to power other components or devices in the
application.
• The external 24V DC power source that provides power to the FP+ and
FP- terminals can be installed on the same DIN rail as the external 24V
DC power source that provides power to the VDC+ and VDC- terminals
or you can install the external 24V DC power sources on separate
DIN rails.
• Use a power source that most effectively meets your application needs.
That is, calculate your application’s power requirements before choosing a
power source to avoid using a power source that far exceeds your
application requirements.
• This section assumes that any DIN rail you use has been grounded
following Industrial Automation Wiring and Grounding Guidelines,
publication 1770-4.1
1. Verify that the separate external 24V DC power source powering the
CompactLogix 5370 L1 controller is not powered.
2. Verify that the external 24V DC power source that will be connected to
the FP+ and FP- terminals is not powered.
3. Mount the external power supply that will connect to the FP+ and FP-
terminals on a DIN rail.
The external power supply can be installed on the same DIN rail as the
controller or a separate DIN rail.
WARNING: If you connect or disconnect wiring while the field-side 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.
00:00:BC:2E:69:F6
10. Turn power on to the separate external 24V DC power source connected
to the removable connector’s VDC+ and VDC- terminals.
11. Turn power on to the external 24V DC power source connected to the
removable connector’s FP+ and FP- terminals.
DC ok
DC 24-28V 50W max.
DC
ok
00:00:BC:2E:69:F6
24-
28V
NEC Class 2
Power Supply
DC DC
INPUT OUTPUT
IP Address:
ENET Address: 00:00:BC:66:0F:C7
24 VDC 24 VDC
SINK SOURCE
• You must connect an external 24V DC power source to the FP+ and FP-
terminals on the controller’s removable connector to power input and
output devices connected to the controller’s embedded I/O modules.
• The I/O points’ available RPI range is 1.0 ms…750.0 ms and can be
changed by 0.5 ms increments. The default setting is 20 ms.
IMPORTANT • If you attempt to use an RPI value that is not valid, the application
automatically rounds the value down to the closest 0.5 ms
increment when you apply the change.
For example, if you set the RPI = 1.75 ms, when you click Apply or
OK, the value is rounded down to 1.5 ms and then applied.
• The RPI value for embedded I/O module is intended to establish a
specific time interval at which data is transmitted. However, the
actual time interval of data transmission may be affected by the
configuration of your CompactLogix 5370 L1 control system.
For more information, see Estimate Requested Packet Interval on
page 158.
Complete these steps to wire the input and output points on the
CompactLogix 5370 L1 controller.
3. With the wire in place, pull the screwdriver off the spring release clip.
4. Repeat step 2 for all embedded I/O wires needed in your application.
This method is required if you need to continue reading data from the
input devices when the embedded output terminals are disabled, for
example, output power is interrupted by the use of a Master Control Relay
(MCR).
Figure 18 shows examples of how to power 2-wire and 3-wire input devices in
your application.
DC DC
INPUT OUTPUT
Power
Supply 1
MCR
24 VDC 24 VDC
SINK SOURCE
Figure 19 shows examples of how to power 2-wire and 3-wire input devices in
your application with connections to a V terminal.
DC DC
INPUT OUTPUT
Power
Supply 1
MCR
24 VDC 24 VDC
SINK SOURCE
Power
2-wire Prox 3-wire Prox
Supply 2
IMPORTANT Do not exceed the per point output current rating or total output module
current rating.
Figure 20 - CompactLogix 5370 L1 Controllers Embedded Digital Output Point Wiring Diagram
DC
OUTPUT
Load
Load
Load
Load
Load
Load
Load
Load
24 VDC
SOURCE
IMPORTANT Do not exceed the per point output current rating or total output module
current rating.
Figure 21 - CompactLogix 5370 L1 Controllers Embedded Digital Output Point Wiring Diagram
DC
OUTPUT
Load
Load
Load
Load
Load
24 VDC
SOURCE
IMPORTANT For a full description of how to use 1734 POINT I/O modules, see the POINT I/O
Digital and Analog Modules and POINTBlock I/O Modules, publication
1734-UM001.
• You can use up to the maximum number of 1734 POINT I/O modules
with the CompactLogix 5370 L1 controllers listed in Table 8, as long as
the total current drawn by the embedded I/O and local expansion modules
does not exceed the available POINTBus backplane current of 1 A and/or
field power current of 3 A.
The field power distributor module breaks the available field power
current between the modules to its left and right. With the field power
distributor module installed, the modules to its left can draw up 3 A of
field power current, and the modules to its right can draw as much field
power current as allowed by the field power distributor.
IMPORTANT Remember, the field power distributor module only changes the level
of field power current available in the system. It does not affect the
level of POINTBus backplane current available.
• You must connect an external 24V DC power source to the FP+ and FP-
terminals on the controller’s removable connector to provide power to
input and output devices connected to the local expansion modules.
For more information on how to connect a power source to the FP+ and
FP- terminals, see page 140.
• We recommend that you make sure all of the 1734 POINT I/O modules
that you intend as local expansion modules are upgraded to the most
current firmware revision before installing them in a CompactLogix 5370
L1 control system.
You can configure specific RPI values for each local expansion module in
your control system. However, the complete I/O configuration has an
impact on the rate at which data is actually transmitted in a CompactLogix
5370 L1 control system. For more information, see Estimate Requested
Packet Interval on page 158.
If you need to return a 1734 POINT I/O module to Autobaud, see the
POINT I/O Digital and Analog Modules and POINTBlock I/O
Modules, publication 1734-UM001.
• When possible, use specialty 1734 POINT I/O modules to meet unique
application requirements.
• Make sure that there are no empty slots between the controller and local
expansion modules or between local expansion modules.
• The Expansion I/O parameter in the controller’s project must match the
number of local expansion modules installed in the system exactly or the
controller will not establish connections to the local expansion modules.
You can include distributed I/O modules over an EtherNet/IP network in your
CompactLogix 5370 L1 control system.
The following graphic shows a CompactLogix 5370 L1 control system that uses
all three I/O module options.
Embedded I/O Module Local Expansion Modules
8 7
6 5
4 3
2 1
Validate I/O Layout You must validate the layout of 1734 POINT I/O modules in your
CompactLogix 5370 L1 control system. Consider these points when validating
I/O layout placement:
• Set the Number of Local Expansion Modules
• Empty Slots and Removal and Insertion Under Power Situations
• Estimate Requested Packet Interval
• Module Faults Related to RPI Estimates
• Physical Placement of I/O Modules
Each time the controller is powered up, it compares the number of local
expansion modules present on the POINTBus backplane to the Expansion I/O
value. The controller does not allow any I/O connections until the number of
local expansion modules present equals the Expansion I/O value.
The POINT I/O system cannot detect an empty terminal base. For this reason,
there are numerous situations in which you can potentially configure a system
that is unusable or one that exercises unintended control.
Follow these rules for I/O system configuration and RIUP of I/O modules.
IMPORTANT 1734 POINT I/O modules support RIUP in CompactLogix 5370 L1 control
systems.
• A correct I/O system does not have any empty terminal bases. If necessary,
you can use a 1734-ARM POINT I/O Address Reserve module to
temporarily replace a 1734 POINT I/O module in a CompactLogix 5370
control system.
• After you cycle power, the controller only allows I/O connections if the
number of local expansion modules present on POINTBus matches the
value used for the Expansion I/O parameter in the project.
• When you remove an I/O module that has an active connection from the
controller, the controller I/O status indicator flashes green to indicate the
condition.
IMPORTANT If you enabled the 'Major Fault On Controller If Connection Fails While
in Run Mode' parameter when configuring the module in the
RSLogix 5000 project, removal of the module causes the controller to
transition to a major fault condition.
• If modules of the same type are removed and returned to the wrong
locations, they accept connections from the controller and reconfigure
with the correct data once they pass their electronic keying check.
The requested packet interval (RPI) defines the frequency at which the
controller sends data to and receives data from I/O modules. You set an RPI rate
for each I/O module in your system.
IMPORTANT When considering digital I/O modules, remember that they can be the
embedded I/O module on the controller or 1734 POINT I/O modules
used as Local Expansion Modules. Therefore, the consideration for
using two modules can be the embedded I/O module and a 1734
POINT I/O module or two 1734 POINT I/O modules.
• For 1734-485ASC modules, the sum total data size for all ASC modules
determines the RPI rates:
– For total data size less than 20 bytes, each module can be scanned
in 20 ms.
– For data size greater than 20 bytes, use the size value as the RPI.
For example, if the total data size is 40 bytes, each ASC module can be
scanned in 40 ms.
You are not required to set individual 1734 POINT I/O modules’ RPI values to
the values listed above. For example, if your application scans one or two
modules, you do not have to use RPI rates of 2 ms. Remember, though, that
higher RPI rates result in scanning the data less frequently.
The RPI shows how quickly modules can be scanned, not how quickly an
application can use the data. The RPI is asynchronous to the program scan.
Other factors, such as program execution duration, affect I/O throughput.
Some systems that follow the guidelines may experience minor faults described in
the following table.
Name Fault Condition In Which Fault Occurs
Information
Module (Type 03) I/O fault This fault is logged when an I/O module's current RPI update overlaps with its
RPI (Code 94) Module previous RPI update. The Minor Faults tab in the Controller Properties dialog box
Overlap RPI overlap indicates which module's RPI is overlapping.
detected If multiple I/O modules experience the fault, the application indicates the fault
Module Slot = x, occurred on the first such I/O module. Typically, it is an I/O module with a lower RPI
where x is the slot rate and/or an I/O module with large input/output data sizes. For example, the
number of the I/O 1734-232ASC and 1734-485ASC modules use large input/output data sizes.
module in the I/O Once the fault is cleared from the first I/O module, the application indicates the
Configuration next module experiencing the fault.This pattern continues until the fault is cleared
section from all affected I/O modules.
To avoid this fault, set the I/O modules’ RPI rate to a higher numerical value.
In some circumstances, you might configure a system that requires more current
than the system’s embedded power supply provides. This type of configuration
results from using a combination of local expansion modules that, when
combined with current consumption of the rest of the system, exceeds 1 A @ 5V
DC.
In this case, you can take any of the following actions to make sure your system
configuration has enough power:
IMPORTANT The 1734-FPD POINT I/O Field Power Distributor is required if the
devices connected to the local expansion modules consume more
than 3 A.
Use the Event Task The CompactLogix 5370 L1 controllers support the use of an Event task with
their embedded input points. You can configure embedded input point terminals
to trigger an Event task if a change of state (COS) occurs.
IMPORTANT When using the Event task with the CompactLogix 5370 L1 controllers,
consider these points:
• You can use the Event task only with Logix Designer application, version
21.00.00 and later.
• You can use the Event task only with the controller’s embedded input
points. You cannot use the Event task with input points in the local
expansion modules, for example, a 1734-IB4 module.
• You can use the Event task only if the input point has an input data
state change.
• An event is recognized only when it maintains the same state for at least
the duration of the input filter time specified.
• Configure the Event task at a rate that prevents task overlap conditions.
• Configure the Event task at a rate that is likely to succeed.
A 2 ms signal width is the minimum pulse width that can be used at which
the Event task always succeeds.
You can configure more than one embedded input point to trigger an Event task.
However, we recommend you enable COS for only one point. If you enable COS
for multiple points, a task overlap of the Event task can occur.
You can configure an Event task to trigger if either of these events occur:
• A specific event occurs on a single point on an input module.
• A trigger event does not occur in a specific time interval.
You configure whether the task updates output modules at the end of the task.
After the task executes, it does not execute again until the event occurs again.
Each Event task requires a specific trigger.
The following table describes the triggers for an Event task available in a
CompactLogix 5370 L1 control system.
Trigger Description
Input Data State Change The input point triggers the Event task based on the change of state (COS)
configuration for the point. The COS configuration is set on the Module Definition
dialog box.
Consumed Tag Only one consumed tag can trigger a specific Event task. Use an Immediate Output
(IOT) instruction in the producing controller to signal the production of new data.
Axis Registration 1 or 2 A registration input triggers the Event task.
Axis Watch A watch position triggers the Event task.
Motion Group Execution The coarse update period for the motion group triggers the execution of both the
motion planner and the Event task. Because the motion planner interrupts all other
tasks, it executes first.
EVENT Instruction Multiple EVENT instructions can trigger the same task.
IMPORTANT An event is recognized only when it maintains the same state for at
least the duration of the input filter time specified.
d. Click OK.
Configure I/O Complete these steps to add a 1734 POINT I/O module to your
CompactLogix 5370 L1 control system.
While the configuration options vary from module to module, there are some
common options you typically configure when using 1734 POINT I/O modules
in a CompactLogix 5370 L1 control system, as described in Table 9.
Table 9 - Common Configuration Parameters
Configuration Option Description
Requested packet interval (RPI) The RPI specifies the interval at which data is transmitted or received over a connection. For POINTBus backplane local expansion
modules, data is transmitted to the controller at the RPI.
When scanned on the local bus or over an EtherNet/IP network, I/O modules are scanned at the RPI specified in the module
configuration. Typically, you configure an RPI in milliseconds (ms).
• For local expansion modules, the range is 1.0…750 ms and the RPI must be configured in 0.5 ms increments. That is, you cannot set
the RPI to a value of 2.3 ms. It must be 2.0 or 2.5.
• For remote I/O modules over an EtherNet/IP network, the range is 2.0…750 ms and the RPI must be configured in 1.0 ms
increments. That is, you cannot set the RPI to a value of 2.3 ms. It must be 2.0 or 3.0.
Module definition Set of configuration parameters that affects data transmission between the controller and the I/O module. The parameters include the
following:
• Series - Module’s hardware series.
• Revision - Major and minor firmware revision levels used on the module.
• Electronic keying - See page 167.
• Connection - Type of connection between the controller writing the configuration and the I/O module, such as Output.
• Data format - Type of data transferred between the controller and I/O module and what tags are generated when the configuration is
complete.
Major Fault on Controller If Connection This option determines how the controller is affected if the connection to an I/O module fails in Run mode or if the controller is unable to
Fails While in Run Mode establish a connection to the module. You can configure the project so that a connection failure causes a major fault on the controller or
not. The default setting is for the option to be disabled.
For example, if this option is enabled and an I/O module is removed while in Run mode, a major fault occurs on the controller. The default
setting for the embedded I/O module is that this option is enabled. The default setting for local expansion modules is that this option is
disabled.
I/O Connections
A CompactLogix 5370 L1 control system uses connections to transmit I/O data.
Table 10 describes the connection types.
IMPORTANT You can only use direct connections with the local expansion modules in a
CompactLogix 5370 L1 control system.
Electronic Keying The electronic keying feature automatically compares the expected module, as
shown in the I/O Configuration tree, to the physical module before I/O
communication begins. You can use electronic keying to help prevent
communication to a module that does not match the type and revision expected.
For each module in the I/O Configuration tree, the user-selected keying option
determines if, and how, an electronic keying check is performed. Typically, three
keying options are available:
• Exact Match
• Compatible Keying
• Disabled Keying
You must carefully consider the benefits and implications of each keying option
when selecting between them. For some specific module types, fewer options are
available.
You can find revision information on the General tab of a module’s Properties
dialog box.
IMPORTANT Changing electronic keying selections online may cause the I/O
communication connection to the module to be disrupted and may result in a
loss of data.
Exact Match
Exact Match keying requires all keying attributes, that is, Vendor, Product Type,
Product Code (catalog number), Major Revision, and Minor Revision, of the
physical module and the module created in the software to match precisely to
establish communication. If any attribute does not match precisely, I/O
communication is not permitted with the module or with modules connected
through it, as in the case of a communication module.
Use Exact Match keying when you need the system to verify that the module
revisions in use are exactly as specified in the project, such as for use in highly-
regulated industries. Exact Match keying is also necessary to enable Automatic
Firmware Update for the module via the Firmware Supervisor feature from a
Logix5000 controller.
Communication is prevented.
Physical Module
Vendor = Allen-Bradley
Product Type = Digital Output Module
Catalog Number = 1734-OB4E
Major Revision = 3
Minor Revision = 2
IMPORTANT Changing electronic keying selections online may cause the I/O
Communication connection to the module to be disrupted and may result in a
loss of data.
Compatible Keying
Compatible Keying indicates that the module determines whether to accept or
reject communication. Different module families, communication adapters, and
module types implement the compatibility check differently based on the family
capabilities and on prior knowledge of compatible products. Release notes for
individual modules indicate the specific compatibility details.
Compatible Keying is the default setting. Compatible Keying allows the physical
module to accept the key of the module configured in the software, provided that
the configured module is one the physical module is capable of emulating. The
exact level of emulation required is product and revision specific.
With Compatible Keying, you can replace a module of a certain Major Revision
with one of the same catalog number and the same or later, that is higher, Major
Revision. In some cases, the selection makes it possible to use a replacement that
is a different catalog number than the original.
Communication is prevented.
Physical Module
Vendor = Allen-Bradley
Product Type = Digital Output Module
Catalog Number = 1734-OB4E
Major Revision = 3
Minor Revision = 2
Communication is allowed.
Physical Module
Vendor = Allen-Bradley
Product Type = Digital Output Module
Catalog Number = 1734-OB4E
Major Revision = 3
Minor Revision = 2
IMPORTANT Changing electronic keying selections online may cause the I/O
communication connection to the module to be disrupted and may result in a
loss of data.
Disabled Keying
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.
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.
Communication is prevented.
Physical Module
Vendor = Allen-Bradley
Product Type = Digital Thermocouple
input module
Catalog Number = 1734-IT2I
Major Revision = 3
Minor Revision = 2
Communication is allowed.
Physical Module
Vendor = Allen-Bradley
Product Type = Digital Output Module
Catalog Number = 1734-OB4E
Major Revision = 3
Minor Revision = 2
IMPORTANT Changing electronic keying selections online may cause the I/O
communication connection to the module to be disrupted and may result in a
loss of data.
Configure Distributed I/O Your CompactLogix 5370 L1 control system can use distributed I/O modules on
an EtherNet/IP network.
Modules on an EtherNet/IP
Network IMPORTANT When adding distributed I/O modules, remember to count the remote Ethernet
adapter to remain within the maximum number of EtherNet/IP network nodes
limitation for your specific controller.
The distributed I/O modules connected to the controller via the remote
Ethernet adapter are not counted toward the maximum Ethernet node limit for
the controller.
For example, a 1769-L16ER-BB1B controller supports up to four Ethernet
nodes. You can add up to four remote Ethernet adapters to the I/O
Configuration section because each remote adapter counts against the node
count. However, you can add as many remote I/O modules to the adapter’s
chassis as necessary. Remote I/O modules do not count against the node count.
For more information on node limitations, see Nodes on an EtherNet/IP
Network on page 118.
7. Repeat these steps to add all of the desired distributed I/O modules to
the project.
002 1734-AENTR
POINT I O
Computer
IP ADDRESS
Monitor I/O Modules With CompactLogix 5370 L1 controllers, you can use the following options to
monitor I/O modules:
The following graphic shows the Quick View Pane indicating the type of fault.
To see the fault description on the Connection tab in Module Properties dialog
box, complete these steps.
2. Click the Connection tab and use the fault description, in the Module
Fault section, to diagnose the issue.
Complete these steps to identify the source of the BUS OFF minor fault.
1. Make sure the number of local expansion modules in the project matches
the number of modules physically installed in the system.
2. Make sure all mounting bases are locked and I/O modules are securely
installed on mounting bases.
3. Make sure all 1734 POINT I/O modules are configured to use the
Autobaud rate.
IMPORTANT You cannot change a 1734 POINT I/O module’s Autobaud setting when
the module is installed in a CompactLogix 5370 L1 control system.
If you need to return a 1734 POINT I/O module to Autobaud, see the
POINT I/O Digital and Analog Modules and POINTBlock I/O Modules,
publication 1734-UM001.
If these steps do not remedy the fault condition, contact Rockwell Automation
technical support.
Topic Page
Select I/O Modules 179
Embedded Analog I/O Modules Data Arrays 199
Validate I/O Layout 213
Configure Local I/O Modules 219
Electronic Keying 222
Configure Distributed I/O Modules on an EtherNet/IP Network 229
Monitor I/O Modules 234
Select I/O Modules CompactLogix 5370 L2 control systems offer these I/O module options:
• Embedded I/O Modules
• Local Expansion Modules - Optional
• Distributed I/O Modules over an EtherNet/IP Network
IMPORTANT Remember the following when using the embedded I/O modules on
CompactLogix 5370 L2 controllers:
• 1769-L24ER-QB1B controller - The digital input points and digital output
points are located on a single embedded I/O module. Therefore, the
1769-L24ER-QB1B controller is considered to have one embedded
I/O module.
You configure an RPI rate for the embedded I/O modules to establish specific
time intervals at which data is transmitted between the controller and each
embedded I/O point. The embedded I/O points’ available RPI range is
0.5…750.0 ms and can be changed by 0.5 ms increments. The default setting
is 20 ms.
IMPORTANT • If you attempt to use an RPI value that is not valid, the application
automatically rounds the value down to the closest 0.5 ms increment when
you apply the change.
For example, if you set the RPI = 1.75 ms, when you click Apply or OK, the
value is rounded down to 1.5 ms and then applied.
IMPORTANT Figure 23 shows the embedded digital I/O points on the 1769-L24ER-QB1B
controller. The embedded digital I/O points on the 1769-L24ER-QBFC1B and
1769-L27ERM-QBFC1B controllers are organized and wired the same.
DC IN
00 08
01 09
02 10
03 11
L24ER
0 1 2 3 4 5 6 7
Digital Input 04 12
QB1B
SOURCE
24VDC
SINK\
INPUT
DC
Points
8 9 10 11 12 13 14 15
05 13
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7
8 9 10 11 12 13 14 15
DC IN 06 14
00 08
01 09
02 10
07 15
03 11
04 12
COM COM
05 13
0 1
06 14
07 15
NC NC
COM COM
0 1
NC NC +V +V
+V +V
00 08
01 09
00 08
02 10
03 11 01 09
00:00:BC:2E:69:F6
04 12
05 13
06 14
Digital Output 02 10
Points
07 15
COM COM
0 1 03 11
DC OUT
+24VDC COM FG
04 12
05 13
06 14
07 15
COM COM
0 1
DC OUT
Figure 24 - CompactLogix 5370 L2 Controllers Embedded Digital Input Point Wiring Diagram
+ DC (Sinking)
- DC (Sourcing)
DC IN
00
01
02
03
24V DC
04
05
06
07
COM
0
- DC (Sinking)
+ DC (Sourcing) NC
Figure 25 - CompactLogix 5370 L2 Controllers Embedded Digital Output Point Wiring Diagram
+ DC +V
CR 00
01
CR 02
03
24V DC
04
CR 05
06
CR 07
- DC COM
0
DC OUT
IMPORTANT The embedded analog I/O points are available on the 1769-L24ER-QBFC1B and
1769-L27ERM-QBFC1B controllers only.
Table 12 lists the available embedded analog input channel types and ranges for
the channel type. The configuration choices are made on the Input
Configuration tab of the Module Properties dialog box, as shown in the table.
Table 12 - Input Types
Input Type Input Ranges Project Configuration
Voltage • Type -50 mV…50 mV
• Type -100 mV…100 mV
• 0…5V
• 1…5V
• 0…10V
• -10V…10V
Current • 0…20 mA
• 4…20 mA
Thermocouple • J
• K at 1370…1372 °C
(2498…2501.6 °F)
• K at -200…1370 °C
(-328…2498 °F)
• T
• E
• S and R at 0…1768 °C
(32…3214.4 °F)
• S and R at -50…0 °C
(-58…32 °F)
• B at 300…1820 °C
(572…3308 °F)
• B at 250…300 °C (482…572 °F)
• N
• C
RTD • 100 Ω Platinum 385
• 200 Ω Platinum 385
• 500 Ω Platinum 385
• 1000 Ω Platinum 385
• 100 Ω Platinum 3916
• 200 Ω Platinum 3916
• 500 Ω Platinum 3916
• 1000 Ω Platinum 3916
• 10 Ω Copper 426
• 120 Ω Nickel 618
• 120 Ω Nickel 672
• 604 Ω Nickel-Iron 518
Resistance • 0…150 Ω
• 0…500 Ω
• 0…1000 Ω
• 0…3000 Ω
Figure 26 shows the embedded analog I/O points and how each termination
point is used with different analog input types.
V V
in in
0+ 2+
I I
in in
0+ 2+
V/I V/I
L27ERM
A0 B0 Z0
in in
0- 2-
0 1 2 3 4 5 6 7
SOURCE
IN
QBFC1B
HIGH SPEED
24VDC
SINK\
INPUT
DC
COUNTER
8 9 10 11 12 13 14 15 A1 B1 Z1
V
OUT
SOURCE
OUTPUT
24VDC
CJC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
8 9 10 11 12 13 14 15 1 3 OK
+ in
DC IN
A0+ A0-
HSC
3+
00 08
01 09 B0+ B0-
CJC inI
02 10 Z0+ Z0-
- 3+
03 11 A1+ A1-
06 14 +V +V
1+ 3-
07 15
OUT OUT
0 2 I V/I
COM COM
0 1
OUT 0UT
1 3 in in
NC NC COM COM 1+ 1-
+V +V
V V
in in
0+ 2+ V V
00 08
I
in in
0+ 2+
I
OUT OUT
01 09
V/I V/I
in in
0- 2-
0+ 1+
02 10 CJC inV
+ 3+ I I
03 11 CJC inI
- 3+ OUT OUT
04 12
V V/I
in in
1+ 3-
0+ 1+
00:00:BC:2E:69:F6 05 13
I V/I
in in
1+ 1-
V V
06 14
07 15
OUT OUT
0+ 1+
I I
OUT in
0+ 1+
COM COM
COM COM COM COM
0 1
DC OUT ANALOG
ANALOG
+24VDC COM FG
In V V In V V
in in EXC 0 in in EXC 1
0+ 0+ 2+ 2+ 0+ 2+
I I I I
N.C. in in N.C. N.C. in in N.C.
0+ 2+ 0+ 2+
In V/I V/I In V/I V/I
in in SEN 01 in in SEN 11
0- 0- 2- 2- 0- 2-
CJC CJC V In CJC CJC V
+ + in 3+ + + in SEN 12
3+ 3+
CJC I CJC I
CJC in N.C. CJC in N.C.
- - 3+ - - 3+
In V V/I In V V/I
in in 3- SEN 02 in in RTN 1
1+ 1+ 3- 1+ 3-
I V/I In I V/I
N.C. in in N.C. in in RTN 0
1+ 1- 1- 1+ 1-
V V V V
OUT OUT OUT OUT
0+ 1+ 0+ 1+
I I I I
OUT OUT OUT OUT
0+ 1+ 0+ 1+
COM COM COM COM
Thermocouple Input Type Connections RTD and Resistance Input Type Connections
+ V V + V V
in in in in
0+ 2+ 0+ 2+
I I I I
- in in
0+ 2+ - in in
0+ 2+
V/I V/I V/I V/I
in in in in
0- 2- 0- 2-
CJC inV CJC inV
+ 3+ + 3+
CJC inI CJC inI
- 3+ - 3+
V V/I V V/I
in in in in
1+ 3- 1+ 3-
Earth Ground I V/I
in in
Earth Ground I V/I
in in
1+ 1- 1+ 1-
V V V V
OUT OUT OUT OUT
0+ 1+ 0+ 1+
I I I I
OUT OUT OUT OUT
0+ 1+ 0+ 1+
COM COM COM COM
ANALOG ANALOG
Differential
+ V V + Differential
IMPORTANT: For both in
0+
in
2+
Voltage Current
input types, we I I
V V EXC 1
in in
0+ 2+
I I
in in
0+ 2+
V/I V/I
in in
0- 2-
CJC V
+ in
2-wire Device 3+
I
CJC
Wiring Diagram - in
3+
V V/I RTN 1
in in
1+ 3-
I V/I
in in
1+ 1-
V V
OUT OUT
0+ 1+
I I
OUT OUT
0+ 1+ Earth
COM COM
IMPORTANT: For all ANALOG
wiring diagrams, we
recommend that you
use Belden #83503 or
9533 cable.
V V EXC 1
in in
0+ 2+
I I
in in
0+ 2+
V/I V/I
in in
0- 2-
SEN 12
CJC inV
+ 3+
CJC inI
3-wire Device - 3+
V V/I RTN 1
Wiring Diagram in in
1+ 3-
I V/I
in in
1+ 1-
V V
OUT OUT
0+ 1+
I I
OUT OUT
Earth
0+ 1+
COM COM
ANALOG
V V EXC 1
in in
0+ 2+
I I
in in
0+ 2+
V/I V/I SEN 11
in in
0- 2-
CJC V SEN 12
+ in
3+
4-wire Device CJC in
I
- 3+
Wiring Diagram V V/I RTN 1
in in
1+ 3-
I V/I
in in
1+ 1-
V V
OUT OUT
0+ 1+
I I
OUT OUT
0+ 1+
COM COM
ANALOG
Table 13 lists the available embedded analog output channel types and ranges for
the channel type. The configuration choices are made on the Output
Configuration tab of the Module Properties dialog box, as shown in the table.
Table 13 - Output Types
Output Type Output Project Configuration
Ranges
Voltage • -10…10V
• 0…5V
• 0…10V
• 1…5V
Current • 4…20 mA
• 0…20 mA
Figure 31 shows an example of wiring input devices to the analog output points
on the 1769-L27ERM-QBFC1B controller when it is operating in voltage or
current mode.
Each counter uses differential inputs that are compatible with standard
differential-line driver output devices as well as single-ended devices. Figure 32
shows the embedded high-speed counter input points.
HSC
A0+ A0-
B0+ B0-
L27ERM
0 1 2 3 4 5 6 7 A0 B0 Z0
SOURCE
QBFC1B
IN
24VDC
SINK\
INPUT
DC
HIGH SPEED
A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
Z0+ Z0-
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
8 9 10 11 12 13 14 15 1 3 OK
DC IN HSC
00 08
01 09
A0+ A0-
B0+ B0-
A1+ A1-
02 10 Z0+ Z0-
03 11
04 12
A1+ A1-
B1+ B1-
B1+ B1-
05 13 Z1+ Z1-
+V +V
06 14
07 15
OUT OUT
0 2
Z1+ Z1-
COM COM OUT 0UT
0 1 1 3
NC NC COM COM
+V +V
V V
in in
0+ 2+
I I
+V +V
00 08 in in
0+ 2+
01 09
V/I V/I
in in
0- 2- OUT OUT
02 10
03 11
CJC in
+ 3+
V
CJC inI
- 3+
0 2
00:00:BC:2E:69:F6
04 12
V V/I
in in
1+ 3-
I V/I
OUT 0UT
05 13
06 14
in in
1+ 1-
V V
OUT OUT
0+ 1+
1 3
I I
07 15 OUT in
0+ 1+
COM COM
0 1
COM COM
ANALOG
COM COM
DC OUT
+24VDC COM FG
Cable
A0- HSC
+V +V
OUT OUT
0 2
OUT 0UT
1 3
Shield/Housing COM COM
Connect only if housing is electronically
isolated from the motor and ground.
Cable
A0- HSC
A1+ A1-
Shield
External +VDC VS
B1+ B1-
Power COM GND Z1+ Z1-
Supply
Earth +V +V
OUT OUT
0 2
OUT 0UT
1 3
COM COM
Shield/Housing
Connect only if housing is electronically
isolated from the motor and ground.
The embedded high-speed counter also supports four output points. Figure 35
shows a wiring diagram for the embedded high-speed counter output points.
IMPORTANT Figure 35 shows the embedded high-speed counter output points on the
1769-L27ER-QB1B controller. The embedded high-speed counter points on the
1769-L24ER-QBFC1B and 1769-L27ERM-QBFC1B controllers are organized and
wired the same.
HSC
A0+ A0-
B0+ B0-
Z0+ Z0-
A1+ A1-
B1+ B1-
Z1+ Z1-
+V +V +DC
CR OUT OUT
0 2 CR
-DC
Complete these steps to wire the input and output points on the
CompactLogix 5370 L2 controller.
If your wire is too thin to push into the connector hole for secure
placement, we recommend that you connect the wire to a ferrule and then
insert it into the connector hole.
L27ERM
0 1 2 3 4 5 6 7 A0 B0 Z0
QBFC1B
SOURCE
IN
24VDC
SINK\
INPUT
DC
HIGH SPEED
A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
8 9 10 11 12 13 14 15 1 3 OK
DC IN HSC
00 08 A0+ A0-
01 09 B0+ B0-
02 10 Z0+ Z0-
03 11 A1+ A1-
04 12 B1+ B1-
05 13 Z1+ Z1-
06 14 +V +V
OUT OUT
07 15 0 2
COM COM OUT 0UT
0 1 1 3
NC NC COM COM
V V
+V +V in in
0+ 2+
I I
00 08 in in
0+ 2+
V/I V/I
01 09 in in
0- 2-
CJC inV
02 10 + 3+
CJC inI
03 11 - 3+
V V/I
04 12 in in
1+ 3-
I V/I
05 13 in in
1+ 1-
V V
06 14 OUT OUT
0+ 1+
I I
07 15 OUT in
0+ 1+
COM COM COM COM
0 1
DC OUT ANALOG
+24VDC COM FG
4. Repeat step 3 for all embedded I/O wires needed in your application.
L27ERM
0 1 2 3 4 5 6 7 A0 B0 Z0
QBFC1B
SOURCE
IN
24VDC
SINK\
INPUT
DC
HIGH SPEED
A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
8 9 10 11 12 13 14 15 1 3 OK
DC IN HSC
00 08 A0+ A0-
01 09 B0+ B0-
02 10 Z0+ Z0-
03 11 A1+ A1-
04 12 B1+ B1-
05 13 Z1+ Z1-
06 14 +V +V
OUT OUT
07 15 0 2
COM COM OUT 0UT
0 1 1 3
NC NC COM COM
V V
+V +V in in
0+ 2+
I I
00 08 in in
0+ 2+
V/I V/I
01 09 in in
0- 2-
CJC inV
02 10 + 3+
CJC inI
03 11 - 3+
V V/I
04 12 in in
1+ 3-
I V/I
05 13 in in
1+ 1-
V V
06 14 OUT OUT
0+ 1+
I I
07 15 OUT in
0+ 1+
COM COM COM COM
0 1
DC OUT ANALOG
+24VDC COM FG
If any issues arise with a removable connector and you suspect a connection point
may no longer be functioning as a complete circuit, you can use a continuity
tester to determine if the connection point is operating correctly, that is, the
connection point is a complete circuit.
The indication mechanism, for example, a light illuminating on the tester, varies
by specific continuity tester. The example graphic below shows a continuity tester
with a single connection point. In this case, if the circuit is operating correctly, the
indicator light turns on.
Insert a continuity tester into the suspected I/O connection point as shown in
the following graphic.
Continuity Tester
Small hole on
opposite from
termination point
in removable
connector.
Determine Embedded IMPORTANT This section applies to the 1769-L24ER-QBFC1B and 1769-L27ERM-QBFC1B
Module Update Time because only those controllers have and embedded universal analog
input points.
The module update time is the time required for the module to sample and
convert the input signals of all enabled analog input channels and provide the
resulting data values to the controller.
The module update time is calculated by adding the update times for each
enabled analog input channel on the module. Each channel update time
calculation is the result of several configuration choices described in the
following section.
The channel update time for an enabled analog input channel is determined by
some combination of the following times:
• Open Circuit Detection Update Time - Optional for channel update time
calculation time
When you enable an embedded analog input channel, you must select an input
type and a filter frequency for that input. The selections made determine the
value that is required when calculating channel update time.
IMPORTANT Each channel input type has multiple ranges or types. For example, a voltage
input type can use one of six voltage ranges, as listed in Table 12 on page 183.
Regardless of which voltage range the channel uses, the channel update time
remains the same. For more information, see Table 14.
Table 14 shows the channel update times for each channel input type and filter
frequency selection.
Table 14 - Channel Update Times
Channel Update Times Based on Input Type Selection
Filter Frequency Voltage, Current or Resistance or RTD Input
Selection(1) Thermocouple Input Type Type
10 Hz 307 ms 614 ms
50 Hz 67 ms 134 ms
60 Hz 57 ms 114 ms
250 Hz 19 ms 38 ms
500 Hz 13 ms 26 ms
1 kHz 11 ms 22 ms
(1) Filter frequency selections are made on the Input Configuration tab of the Module Properties dialog box.
When you use any of the thermocouple input types on your embedded analog
input, you might need to account for additional voltage at the junction of the
thermocouple field wires and the input point. Additional voltage can alter the
input signal on that point and, therefore, affect that channel’s update time.
By default, CJC is disabled. You must clear the Disable Cold Junction
Compensation checkbox to use CJC for a given channel.
You are not required to enable CJC for a channel using the thermocouple input
type. If you enable CJC and select Update Cold Junction Compensation every
other scan, an additional update time exists on the channel. This additional
update time increases the overall channel update time.
The CJC update time is determined by the filter frequency selection for the
channel. Table 15 shows the CJC update times based on filter
frequency selections.
Table 15 - Channel Update Times
Filter Frequency Selection(1) CJC Update Time
10 Hz 614 ms
50 Hz 134 ms
60 Hz 114 ms
250 Hz 38 ms
500 Hz 26 ms
1 kHz 22 ms
(1) Filter frequency selections are made on the Input Configuration tab of the Module Properties dialog box.
IMPORTANT Keep the following in mind when calculating the CJC update time:
• If multiple input channels are configured to use a thermocouple input type
and a different filter value is selected for each, the CJC update time is
determined by the filter frequency selection with the slowest update time.
For example, if one input channel uses a thermocouple input with a 50 Hz
filter frequency and another input channel uses a thermocouple input with
a 60 Hz filter frequency, the CJC channel update time is 134 ms.
• The CJC update time that increases overall module update time is only used
once regardless of the number of input channels on a module that have CJC
enabled to scan every other scan.
In other words, if your module uses a filter frequency selection of 250 Hz
and includes three channels with CJC enabled to scan every other scan, you
only add one instances of CJC update time to the overall equation. Instead
of including 38 ms for each channel, you include 38 ms once.
Open circuit detection is used to verify that the field wiring is physically
connected to the embedded analog input point. If this feature is enabled and field
wiring is disconnected from the input, the application alerts you to the condition
and an open wire bit is set in the project’s tags for the respective input channel.
Open circuit detection can be enabled or disabled on any channel input type with
the exception of an input channel configured to use the 0...20 mA input range.
The configuration selection is made on the Input Configuration tab on the
Module Properties dialog box, as shown in the following graphic. The
configuration choice, that is, enabled or disabled, is the result of selecting an
Open Circuit Response for the channel.
Table 16 describes the module response associated with each enable selection.
Table 16 - Open Circuit Detection Response Definitions
Response Option Definition
Upscale Sets the input data value to full upper scale value of channel data word. The full-scale value is
determined by the selected input type and data format.
Downscale Sets the input data value to full lower scale value of channel data word. The low scale value is
determined by the selected input type and data format.
Last State Sets the input data value to the last input value prior to the detection of the open-circuit.
Zero Sets the input data value to 0 to force the channel data word to 0.
When you enable open circuit detection for an input channel, an additional
update time is used to calculate the overall channel type. The increase in channel
update time is 11 ms for each channel that enables open circuit detection
response.
Embedded Analog I/O The section describes the data table structures for the embedded analog I/O
modules on the CompactLogix 5370 L2 controllers. The embedded analog I/O
Modules Data Arrays modules have arrays for the following data:
• Input data
• Output data
• Configuration data
You can access the data via the tags in the application.
IMPORTANT The analog I/O modules data structures apply to the 1769-L24ER-QBFC1B and
1769-L27ERM-QBFC1B controllers only.
The 1769-L24ER-QB1B controller does not have an embedded analog
I/O module.
Input Array
The embedded analog I/O module’s input data array contains eleven words as
described in Table 18. This array is read-only and the default value for all bits is 0.
Table 18 - CompactLogix 5370 L2 Controllers’ Embedded Analog I/O Module’s Input Data Array
Bit
Word 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
0 S Analog Read (Input) Data Value Channel 0
1 S Analog Read (Input) Data Value Channel 1
2 S Analog Read (Input) Data Value Channel 2
3 S Analog Read (Input) Data Value Channel 3
4 Nu Timestamp Value
5 Nu UI4 OI4 OC4 OC3 OC2 OC1 OC0 Nu SI4 SI3 SI2 SI1 SI0
6 LI3 HI3 UI3 OI3 LI2 HI2 UI2 OI2 LI1 HI1 UI1 OI1 LI0 HI0 UI0 OI0
7 S Cold Junction Compensation Value
8 S Output Data Loopback/Echo Channel 0
9 S Output Data Loopback/Echo Channel 1
10 Nu UO1 OO1 Nu UO0 OO0 Nu SO1 SO0
Table 18 - CompactLogix 5370 L2 Controllers’ Embedded Analog I/O Module’s Input Data Array
Bit
Word 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Where: Analog Read (Input) Data Value Channel x is the data read from the field device connected to the channel.
Timestamp Value is the timestamp of when data was received at the corresponding channel.
Cold Junction Compensation value is the converted CJC data The data is calculated in the following manner:
• If the CJC is open, the converted value is 25 °C (77 °F).
• If the CJC is not opened and the Update CJC sensor every other scan option is disabled, the converted value is 25 °C (77 °F).
• If the CJC is not opened and the Update CJC sensor every other scan option is enabled, the converted value is the measured temperature.
S Sign bit
Nu Bit not used
SIx General status bit for an input channel. Bits 0…3 are for input channels. Bit 4 is for CJC. If the bit is 0, the channel is operating normally. If the bit is 1, a fault has occurred
on the channel.
Output Array
The embedded analog I/O module’s output image array contains four words as
described in Table 19. This array is write-only and the default value for all bits
is 0.
Table 19 - CompactLogix 5370 L2 Controllers’ Embedded Analog I/O Module’s Output Data Array
Bit
Word 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
0 S Analog Output Data Value Channel 0
1 S Analog Output Data Value Channel 1
2 Nu CL CH CL CH CL CH CL CH
I3 I3 I2 I2 I1 I1 I0 I0
3 Nu CL CH CL CH
O1 O1 O0 O0
Where: Analog Output Data Value Channel x is the data written to the channel.
S Sign bit
Nu Bit not used
CH Use this bit to cancel High Process Alarm Latch functionality for an input.
Ix 0 = Do not cancel
1 = Cancel the alarm latch
CL Use this bit to cancel Low Process Alarm Latch functionality for an input.
Ix 0 = Do not cancel
1 = Cancel the alarm latch
CH Use this bit to cancel High Process Alarm Latch functionality for an output.
Ox 0 = Do not cancel
1 = Cancel the alarm latch
CL Use this bit to cancel Low Process Alarm Latch functionality for an output.
Ox 0 = Do not cancel
1 = Cancel the alarm latch
Configuration Array
The embedded analog I/O module’s configuration image array contains 43 words
as described in Table 20.
Table 20 - CompactLogix 5370 L2 Controllers Embedded Analog I/O Module’s Configuration Image Array
Word Bit
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
0 Real Time Sample Value
1 ETS Nu
2 EC Nu EA AL EI EO Open Circuit Ch0 0V Adj Filter Setting ChI0
3 Wire & CLCD TU ChIo Nu Inpt Dta Fm ChI0 Nu Inpt Tp/RngeSel ChI0
4 S Process Alarm High Data Value Universal Input Channel 0
5 S Process Alarm Low Data Value Universal Input Channel 0
6 S Alarm Dead Band Value Universal Input Channel 0
7 Nu
8 EC Nu EA AL EI EO Open Circuit ChI 1 0V Adj Filter Setting ChI1
9 Nu TU ChI1 Nu Inpt Dta Fm ChI1 Nu Inpt Tp/RngeSel ChI1
10 S Process Alarm High Data Value Universal Input Channel 1
11 S Process Alarm Low Data Value Universal Input Channel 1
12 S Alarm Dead Band Value Universal Input Channel 1
13 Nu
14 EC Nu EA AL EI EO Open Circuit ChI 2 0V Adj Filter Setting ChI2
15 Wire & CLCD TU ChI1 Nu Inpt Dta Fm ChI2 Nu Inpt Tp/RngeSel ChI2
16 S Process Alarm High Data Value Universal Input Channel 2
17 S Process Alarm Low Data Value Universal Input Channel 2
18 S Alarm Dead Band Value Universal Input Channel 2
19 Nu
20 EC Nu EA AL EI EO Open Circuit ChI 3 0V Adj Filter Setting ChI3
21 Nu TU ChI1 Nu Inpt Dta Fm ChI3 Nu Inpt Tp/RngeSel ChI3
22 S Process Alarm High Data Value Universal Input Channel 3
23 S Process Alarm Low Data Value Universal Input Channel 3
24 S Alarm Dead Band Value Universal Input Channel 3
25 Nu
26 CJC Ses Cycle Nu CJC WP Nu TU CJC
Calib
27 Nu
28 EC NU EHI ELI LC ER FM PM Nu PFE
29 Nu Outpt Fm ChI0 Nu Outpt Tp/RngeSel Ch0
30 S Fault Value Channel 0
31 S Program (Idle) Value Channel 0
32 S Clamp High Data Value Channel 0
33 S Clamp Low Data Value Channel 0
Table 20 - CompactLogix 5370 L2 Controllers Embedded Analog I/O Module’s Configuration Image Array
Word Bit
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
34 S Ramp Rate Channel 0
35 Nu
36 EC Nu EHI ELI LC ER FM PM Nu PFE
37 Nu Outpt Fm ChI1 Nu Outpt Tp/RngeSel ChI1
38 S Fault Value Channel 1
39 S Program (Idle) Value Channel 1
40 S Clamp High Data Value Channel 1
41 S Clamp Low Data Value Channel 1
42 S Ramp Rate Channel 1
Where: EC Use to enable or disable a channel. Each channel can be individually enabled.
0 = Disable
1 = Enable
Inpt Use this bit to select the form in which the analog data is returned to the controller and used in the control program.
Dta FM
CHIx
EA Use this bit to enable or disable a channel’s process alarms.
0 = Disable
1 = Enable
AL Use this bit to enable or disable alarm latching on a channel’s process alarm.
0 = No latch
1 = Latch
EI Use this bit to enable or disable interrupts on a channel’s process alarms.
0 = Disable
1 = Enable
EO Use this bit to enable or disable Open Circuit functionality on a channel.
0 = Disable
1 = Enable
Open Use to set the Open Circuit Response for a channel.
Circuit 0 = Upscale
Chx 1 = Downscale
2 = Last State
3 = Zero
OV CJC is performed by default by taking the CJC sensor temperature value for a given channel, converting that to a thermocouple voltage, and adding that
adjust voltage from the measured value prior to converting to a user value. If this bit is set for a given channel, the signal value is directly converted to a user value
(No cold junction compensation performed).
Wire & Use to set the wire mode. The mode is determined by the combination of values in bits 14 and 15, as listed in the following table.
CLCD
Bit 15 Value Bit 14 Value Mode
0 0 3-wire and cycle lead compensation - Enable
0 1 3-wire and cycle lead compensation - Disable
1 0 2-wire (No lead compensation)
1 1 4-wire (No lead compensation)
Table 20 - CompactLogix 5370 L2 Controllers Embedded Analog I/O Module’s Configuration Image Array
Word Bit
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Where Inpt Use these bits to select the form the analog input data is presented to the controller and then used by the controller. This value is determined by the
(cont.) Dta Fm combination of multiple selections in specific words and bits.
ChIx For more information on what selections determine the input data form that is used, see Table 22 on page 207.
Inpt Tp Use these bits to select the input type and operating range for a channel. For more information on what selections determine the input type and operating
/ Rnge range for a channel, see Table 23 on page 207.
Sel
ChIx
Filter Use these bits to select the filter setting for a channel. For more information on what selections determine the filter settings for a channel, see Table 21 on
Setting page 206.
Chx
Process Use to configure the Process Alarm High value for a channel. Configuration is done using words 4, 10, 16, and 22 to set the Alarm High value.
Alarm
High
Data
Value
Channel
x
Process Use to configure the Process Alarm Low value for a channel. Configuration is done using words 5, 11, 17, and 23 to set the Low High value.
Alarm
Low
Data
Value
Channel
x
Alarm Use to configure the Alarm Deadband value for a channel. Configuration is done using words 6, 12, 18, and 24 to set the deadband alarm value.
Dead
Band
Data
Value
Channel
x
ETS Use to enable or disable the timestamping function on the module.
0 = Disable
1 = Enable
Real Use to set the Real Time Sample value. The available range = 0…5000 ms.
Time
Stamp
Value
Update Use this bit to enable or disable a CJC sensor.
CJCCo • If enabled, the CJC is read once every other module scan, and its value updated in the CJC status word. This value is also used for thermocouple cold
mpens junction compensation.
ationE
n • If disabled, the CJC sensor value is not acquired, and the CJC temperature is fixed at 25 °C (77 °F) for all channels. The CJC will also be fixed at 25 °C
(77 °F) for all channels if it is determined to be broken (short or open circuit).
0 = Disable
1 = Enable
Cycle Use this bit to enable Cycle Calibration.
Calib • If enabled, the module's internal calibration occurs once every 5 minutes.
• If disabled, the module’s internal calibration occurs only once at power on/ reset.
Cycle Calibration allows the module to readjust for environmental changes such as variations in temperature. However, the module throughput is slightly
reduced during the calibration operation.
0 = Disable
1 = Enable
Table 20 - CompactLogix 5370 L2 Controllers Embedded Analog I/O Module’s Configuration Image Array
Word Bit
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Where CJC WP Use this bit to enable or disable the CJC Weighted Profile.
(cont.) • If enabled, the CJC temperature for each channel is scaled by multiplying the single CJC reading by a predefined scale factor derived from lab
measurements of each terminal block pin's stable temperature. In this condition, all channel data is overridden with that channel's CJC temperature.
• If disabled, the single CJC reading is applied directly to all channels. If the CJC sensors are installed in a remote terminal block, the weighted profile must
be disabled. In this condition, channel data is presented in the input table as normal.
0 = Disable
1 = Enable
PFE Use this bit to select whether data from the Program/Idle m ode or the Fault Enable mode is applied.
0 = Program/Idle mode data applied
1 = Fault mode data applied
ER Use this bit to enable or disable ramping for each channel.
0 = Disable
1 = Enable
EHI Use this bit to enable or disable the output channel interrupt function when a High Clamp alarm is set.
0 = Disable
1 = Enable
ELI Use this bit to enable or disable the output channel interrupt function when a Low Clamp alarm is set.
0 = Disable
1 = Enable
PM Use this bit to set data a channel uses when it is in Program/Idle mode.
0 = Hold Last State value
1 = User-defined value
FM Use this bit to set data a channel uses when it is in Fault mode.
0 = Hold Last State value
1 = User-defined value
LC Use this bit to enable or disable latch functionality when Low/High clamp and Under/Over range alarm conditions exist on a channel.
0 = Disable
1 = Enable
Outpt Use these bits to select the form the analog output data is presented to the controller and then used by the controller. This value is determined by the
Dta Fm combination of multiple selections in specific words and bits.
ChIx For more information on what selections determine the output data form that is used, see Table 24 on page 209.
Outpt Use these bits to select the output type and operating range for a channel. For more information on what selections determine the input type and operating
Tp / range for a channel, see Table 25 on page 209.
Rnge
Sel
ChIx
Fault Use this bit to configure the Fault mode value for a channel.
Value
Channel
x
Program Use this bit to configure the Program/Idle mode value for a channel.
(Idle)
Value
Channel
x
Table 20 - CompactLogix 5370 L2 Controllers Embedded Analog I/O Module’s Configuration Image Array
Word Bit
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Where Clamp Use this bit to configure the Clamp High data value for a channel.
(cont.) High
Data
Value
Channel
x
Clamp Use this bit to configure the Clamp Low data value for a channel.
Low
Data
Value
Channel
x
Ramp Use this bit to set the Ramp Rate value for a channel.
Rate
Channel
x
Table 21 lists the bit value combinations you can use to select a filter setting for a
channel. You use bits 0…3 in words 2, 8, 14, and 20 to make this selection.
Table 21 - Input Filter Selections
Bit Settings
(Words 3, 9, 15, and 21)
Filter Value Bit 03 Bit 02 Bit 01 Bit 00
60 Hz 0 0 0 0
50 Hz 0 0 0 1
10 Hz 0 0 1
250 Hz 0 0 1 1
500 Hz 0 1 0 0
1 kHz 0 1 0 1
Spare(1) Values 6…15
(1) An attempt to write a non-valid (any Spare value) or Not Used bit configuration into the Input Filter Response Select field will cause
a Module Configuration Error (contained in the Mod_Condition Array).
Table 22 lists the bit value combinations you can use to select the output data
format for analog data that is sent to the controller for a channel. You use bits 8…10
in words 3, 9, 15, and 21 to make this selection.
Table 22 - Analog Input Data Format
Bit Settings
(Words 3, 9, 15, and 21)
Analog Output Data Format Bit 10 Bit 09 Bit 08
Raw/Proportional Data 0 0 0
Engineering Units 0 0 1
Engineering Units x 10 0 1 0
Scaled for PID 0 1 1
Percent Range 1 0 0
Spare(1) Values 5…7
(1) An attempt to write a non-valid (any Spare value) bit configuration into the Input/Output Data Format Select field will cause a
Module Configuration Error (contained in Mod_Condition Array). All bits shown as 0 above shall always be set to 0.
Table 23 lists the bit value combinations you can use to select the input type and
operating range for a channel. You use bits 0…5 in words 3, 9, 15, 21, 29, and 37 to
make the selections.
Table 23 - Analog Input Type and Operating Range
Bit Settings
(Words 3, 9, 15, and 21)
Input Type and Normal
Operating Range Bit 05 Bit 04 Bit 03 Bit 02 Bit Bit 00
-10…10V DC 0 0 0 0 0 0
0…5V DC 0 0 0 0 0 1
0…10V DC 0 0 0 0 1 0
4…20 mA 0 0 0 0 1 1
1…5V DC 0 0 0 1 0 0
0…20 mA 0 0 0 1 0 1
-50 mV…50 mv 0 0 0 1 1 0
-100 mV…100 mV 0 0 0 1 1 1
Thermocouple J 0 0 1 0 0 0
Thermocouple K 0 0 1 0 0 1
Thermocouple T 0 0 1 0 1 0
Thermocouple E 0 0 1 0 1 1
Thermocouple R 0 0 1 1 0 0
Thermocouple S 0 0 1 1 0 1
Thermocouple B 0 0 1 1 1 0
Thermocouple N 0 0 1 1 1 1
Table 24 lists the bit value combinations you can use to select the output data
format for analog data that is sent to the controller for a channel. You use bits 8…10
in words 29 and 37 to make this selection.
Table 24 - Analog Output Data Format
Bit Settings
(Words 29 and 37)
Analog Output Data Format Bit 10 Bit 09 Bit 08
Raw/Proportional Data 0 0 0
Engineering Units 0 0 1
Scaled for PID 0 1 0
Percent Range 0 1 1
Spare(1) Values 4…7
(1) An attempt to write a non-valid (any Spare value) bit configuration into the Input/Output Data Format Select field will cause a
Module Configuration Error (contained in Mod_Condition Array). All bits shown as 0
Table 25 lists the bit value combinations you can use to select the input type and
operating range for a channel. You use bits 0…5 in words 29 and 37 to make the
selections.
Table 25 - Analog Output Type and Operating Range
Bit Settings
(Words 29 and 37)
Output Type and Normal
Operating Range Bit 05 Bit 04 Bit 03 Bit 02 Bit Bit 00
-10…10V DC 0 0 0 0 0 0
0…5V DC 0 0 0 0 0 1
0…10V DC 0 0 0 0 1 0
4…20 mA 0 0 0 0 1 1
1…5V DC 0 0 0 1 0 0
0…20 mA 0 0 0 1 0 1
• Consider using a 1492 wiring system for each I/O module as an alternative
to the terminal block that comes with the module.
• Use 1492 PanelConnect™ modules and cables if you are connecting input
modules to sensors.
Wire each Compact I/O module used as a local expansion module according to
the technical documentation for that module.
You can include distributed I/O modules over an EtherNet/IP network in your
CompactLogix 5370 L2 control system.
L27ERM 0 1 2 3 4 5 6 7 A0 B0 Z0
SOURCE
IN
24VDC
0 1 2 3 4 5 6 7 A0 B0 Z0
SINK\
INPUT
DC
HIGH SPEED
QBFC1B A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
SOURCE
IN
24VDC
SINK\
INPUT
DC
HIGH SPEED
A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
8 9 10 11 12 13 14 15 1 3 OK
8 9 10 11 12 13 14 15 1 3 OK
DC IN HSC
00 08 A0+ A0-
01 09 B0+ B0-
02 10 Z0+ Z0-
03 11 A1+ A1-
04 12 B1+ B1-
05 13 Z1+ Z1-
06 14 +V +V
OUT OUT
07 15 0 2
COM COM OUT 0UT
0 1 1 3
NC NC COM COM
V V
+V +V in in
0+ 2+
I I
00 08 in in
0+ 2+
V/I V/I
01 09 in in
0- 2-
CJC inV
02 10 + 3+
CJC inI
03 11 - 3+
V V/I
04 12 in in
1+ 3-
00:00:BC:2E:69:F6 05 13
I V/I
in in
1+ 1-
V V
06 14 OUT OUT
0+ 1+
I I
07 15 OUT in
0+ 1+
COM COM COM COM
0 1
DC OUT ANALOG
+24VDC
+24VDC COM
COM FG
FG
8 7
6 5
4 3
2 1
LINK 1 LINK 2
You can include distributed I/O modules over a DeviceNet network in your
CompactLogix 5370 L2 control system.
You must use the following to use distributed I/O modules over a DeviceNet
network in your CompactLogix 5370 L2 control system:
L27ERM 0 1 2 3 4 5 6 7 A0 B0 Z0
SOURCE
IN
24VDC
0 1 2 3 4 5 6 7 A0 B0 Z0
SINK\
INPUT
DC
HIGH SPEED
A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
SOURCE
QBFC1B
IN
24VDC
SINK\
INPUT
DC
HIGH SPEED
A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
8 9 10 11 12 13 14 15 1 3 OK
8 9 10 11 12 13 14 15 1 3 OK
DC IN HSC
00 08 A0+ A0-
01 09 B0+ B0-
02 10 Z0+ Z0-
03 11 A1+ A1-
04 12 B1+ B1-
05 13 Z1+ Z1-
06 14 +V +V
OUT OUT
07 15 0 2
COM COM OUT 0UT
0 1 1 3
NC NC COM COM
V V
+V +V in in
0+ 2+
I I
00 08 in in
0+ 2+
V/I V/I
01 09 in in
0- 2-
CJC inV
02 10 + 3+
CJC inI
03 11 - 3+
V V/I
04 12 in in
1+ 3-
00:00:BC:2E:69:F6 05 13
I V/I
in in
1+ 1-
V V
06 14 OUT OUT
0+ 1+
I I
07 15 OUT in
0+ 1+
COM COM COM COM
0 1
DC OUT ANALOG
+24VDC
+24VDC COM
COM FG
FG
Adapter
Status
DeviceNet
Status
PointBus
Status
1734-ADN
System
Power
DeviceNet
Power
Validate I/O Layout You must validate the layout of I/O modules in your CompactLogix 5370 L2
control system. Consider these points when validating I/O layout placement:
• Estimate Requested Packet Interval
• Module Fault Related to RPI Estimates
• System Power Availability
• Power Supply Distance Rating
The requested packet interval (RPI) defines the frequency at which the
controller sends data to and receives data from I/O modules. You set an RPI rate
for each I/O module in your system, including embedded I/O modules, local
expansion modules or distributed I/O modules over an EtherNet/IP network.
With embedded I/O modules and local expansion modules, however, some
specific system configuration parameters determine the actual rate at which the
controller scans the modules. That is, the controller may be configured to scan an
I/O module at one rate but actually scan the module at a different rate.
For individual I/O modules, a Module RPI Overlap minor fault occurs if there is
at least one I/O module that cannot be serviced within its RPI time.
IMPORTANT When considering the number of I/O modules, remember that they can be the embedded I/O
modules on the controller or Compact I/O modules used as local expansion modules.
Therefore, the consideration for using modules can be any of the following system
configurations:
• Embedded I/O modules only
• Compact I/O modules only
• Some combination of embedded I/O modules and Compact I/O modules
You can set individual Compact I/O modules’ RPI rates higher than those listed
in Table 26. The RPI shows how quickly modules can be scanned, not how
quickly an application can use the data. The RPI is asynchronous to the program
scan. Other factors, such as program execution duration, affect I/O throughput.
When following the guidelines described in Table 26, most CompactLogix 5370
L2 control systems operate as expected. Some systems that follow the guidelines
may experience a Module RPI Overlap minor fault described in the
following table.
Name Fault Condition in Which Fault Occurs
Information
Module (Type 03) I/O fault This fault is logged when an I/O module's current RPI update overlaps with its
RPI (Code 94) Module previous RPI update. The Minor Faults tab in the Controller Properties dialog box
Overlap RPI overlap indicates which module's RPI is overlapping.
detected If multiple I/O modules experience the fault, the application indicates the fault
Module Slot = x, occurred on the first such I/O module. Typically, it is an I/O module with a large
where x is the slot Input/Output array sizes. Example modules that use large Input/Output array sizes
number of the I/O include the 1769-SDN and 1769-HSC modules. In these cases, we recommend you
module in the I/O adjust the module’s RPI to eliminate the fault.
Configuration Once the fault is cleared from the first I/O module, the application indicates the
section next module experiencing the fault.This pattern continues until the fault is cleared
from all affected I/O modules.
To avoid this fault, set the I/O modules’ RPI rate to higher numerical values. We
recommend you use an RPI value that is not a common multiple of other module
RPI values, such as 2.5 ms, 5.5 ms, or 7 ms:
• We recommend you do not run CompactLogix 5370 L2 control systems with
Module RPI Overlap faults.
• A system that experiences many Module RPI Overlap faults may not operate
optimally because I/O data is not sampled at the expected rate determined by
RPI settings.
• When the project is downloaded or an I/O module’s RPI value is adjusted, it is
expected to have a minor fault. Faults under these conditions are transitionary.
Clear the fault and wait for the fault to reappear before adjusting the RPI value
or the task priorities.
The embedded power supply provides the following power to the CompactBus:
• 1769-L24ER-QB1B controller:
– 1.54 A @ 5V DC
– 0.95 mA @ 24V DC
Power supply distance rating is the number of slots a Compact I/O module can
be installed away from the power supply. If a Compact I/O modules has a
distance rating of three, you can include up to two modules between the
Compact I/O module and the power supply.
Additionally, the controller has embedded I/O modules that prevent installation
of a Compact I/O module directly to the right of the embedded power supply.
CompactLogix 5370 L2 control systems have embedded I/O modules in the
controller. CompactLogix 5370 L2 control systems have one or two embedded
I/O modules as described below:
While the embedded I/O modules are not considered local expansion modules,
you still must include each embedded I/O module in the module slot count when
determining where to install Compact I/O module as a local expansion module.
Table 27 describes the farthest local expansion module slot where you can install
a 1769-HSC high-speed counter module and meet its power supply distance
rating requirement.
Table 27 - Example CompactLogix 5370 L2 Control Systems with a 1769-HSC High-speed Counter Module
Controller Cat. No. Number of Embedded 1769-HSC High-speed Counter Module Power Supply Distance Rating Calculation Impact
I/O Modules
1769-L24ER-QB1B 1 The embedded I/O module is the first module in the module count. At its maximum power supply distance rating, the
1769-HSC high-speed counter module can be installed in slot 3 of the local expansion modules, as shown below.
L24ER
0 1 2 3 4 5 6 7
SOURCE
24VDC
SINK\
INPUT
DC
8 9 10 11 12 13 14 15
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7
8 9 10 11 12 13 14 15
DC IN
00 08
01 09
02 10
03 11
04 12
05 13
06 14
07 15
COM COM
0 1
NC NC
1769-HSC Module
+V +V
00 08
01 09
02 10
03 11
04 12
00:00:BC:2E:69:F6 05 13
06 14
07 15
COM COM
0 1
DC OUT
+24VDC COM FG
Three modules between the power supply and the 1769-HSC high-speed counter module.
With this controller catalog number, you can only install up to two local expansion modules
between the controller and the 1769-HSC high-speed counter module.
Table 27 - Example CompactLogix 5370 L2 Control Systems with a 1769-HSC High-speed Counter Module
Controller Cat. No. Number of Embedded 1769-HSC High-speed Counter Module Power Supply Distance Rating Calculation Impact
I/O Modules
1769-L24ER-QBFC1B 2 The embedded I/O modules are the first two modules in the module count. At its maximum power supply distance rating,
1769-L27ERM-QBFC1B the 1769-HSC high-speed counter module can be installed in slot 2 of the local expansion modules, as shown below.
L27ERM 0 1 2 3 4 5 6 7 A0 B0 Z0
SOURCE
IN
24VDC
0 1 2 3 4 5 6 7 A0 B0 Z0
SINK\
INPUT
DC
HIGH SPEED
A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
SOURCE
IN
24VDC
SINK\
INPUT
DC
HIGH SPEED
A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
8 9 10 11 12 13 14 15 1 3 OK
8 9 10 11 12 13 14 15 1 3 OK
DC IN HSC
00 08 A0+ A0-
01 09 B0+ B0-
02 10 Z0+ Z0-
03 11 A1+ A1-
04 12 B1+ B1-
05 13 Z1+ Z1-
06 14 +V +V
OUT OUT
07 15 0 2
COM COM
0 1
NC NC
+V +V
OUT 0UT
1 3
COM COM
V V
in in
0+ 2+
1769-HSC High-speed
00 08
01 09
02 10
I
in in
0+ 2+
I
V/I V/I
in in
0- 2-
CJC inV
Module
+ 3+
CJC inI
03 11 - 3+
V V/I
04 12 in in
1+ 3-
00:00:BC:2E:69:F6 05 13
I
in
V/I
in
1+ 1-
V V
06 14 OUT OUT
0+ 1+
I I
07 15 OUT in
0+ 1+
COM COM COM COM
0 1
DC OUT ANALOG
+24VDC
+24VDC COM
COM FG
FG
Three modules between the power supply and the 1769-HSC high-speed counter module.
With this controller catalog number, you can only install one local expansion modules
between the controller and the 1769-HSC high-speed counter.
IMPORTANT When counting I/O modules to determine the 1769-HSC high-speed counter
module placement in a 1769-L24ER-QBFC1B or 1769-L27ERM-QBFC1B control
system, the embedded I/O module appearance is different between the
physical appearance and the modules’ appearance in the application.
The physical appearance is a shown above. The second module is two rows of
termination points below a single set of status indicators.
In the application, the second embedded I/O module appears as two modules
in the Controller Organizer each with their own slot number, that is [2] and [3].
1769-HSC high-speed counter module is shown as module [5] in this location but considered the
fourth module when counting modules to meet power supply distance rating requirements.
For more information about the power supply distance rating for a Compact I/O
module, see CompactLogix Selection Guide, publication 1769-SG001.
Configure Local I/O Modules You can configure either of these types of local I/O modules in your
RSLogix 5000 project:
• Configure Embedded I/O Modules
• Configure Local Expansion Modules
2. Click the appropriate tab, make the necessary changes, and click OK.
IMPORTANT You can also use the tags to configure the CompactLogix 5370 L2 controllers’
embedded I/O modules. When attempting to use the tags to make analog I/O
module selections in the input, output and configuration data arrays, the
options are complicated.
While the configuration options vary from module to module, there are some
common options you typically configure when using Compact I/O modules in a
CompactLogix 5370 L2 control system, as described in Table 28.
Table 28 - Common Configuration Parameters
Configuration Option Description
Requested packet interval (RPI) The RPI specifies the interval at which data is transmitted or received over a connection. For 1769 Compact Local I/O modules, data is
transmitted to the controller at the RPI.
When scanned on the local bus or over an EtherNet/IP network, input modules are scanned at the RPI specified in the module
configuration. Typically, you configure an RPI in milliseconds (ms). For I/O modules, the range is 0.5…750 ms.
When scanned over a DeviceNet network via a 1769-SDN scanner module in the CompactLogix 5370 L2 control system, distributed input
modules are scanned at the rate supported by the DeviceNet adapter module connecting the input modules to the network. For
example, if your system includes a remote system of 1734 POINT I/O modules on a DeviceNet network, the 1769-SDN scanner module
can only scan the distributed 1734 POINT I/O modules as quickly as the 1734-ADN DeviceNet adapter can transmit the data.
Module definition Set of configuration parameters that affect data transmission between the controller and the I/O module. The parameters include the
following:
• Series - Module’s hardware series.
• Revision - Major and minor firmware revision levels used on the module.
• Electronic keying - See page 222.
• Connection - Type of connection between the controller writing the configuration and the I/O module, such as Output.
• Data format - Type of data transferred between the controller and I/O module and what tags are generated when the configuration is
complete.
Module Fault on Controller If Connection This option determines how the controller is affected if the connection to an I/O module fails in Run mode. You can configure the project
Fails While in Run Mode so that a connection failure causes a major fault on the controller or not.
The default setting is for the option to be enable, that is, if the connection to an I/O module fails in Run mode, a major fault will occur on
the controller.
I/O Connections
IMPORTANT You can only use direct connections with the local expansion modules in a
CompactLogix 5370 L2 control system.
Electronic Keying The electronic keying feature automatically compares the expected module, as
shown in the I/O Configuration tree, to the physical module before I/O
communication begins. You can use electronic keying to help prevent
communication to a module that does not match the type and revision expected.
For each module in the I/O Configuration tree, the user-selected keying option
determines if, and how, an electronic keying check is performed. Typically, three
keying options are available:
• Exact Match
• Compatible Keying
• Disable Keying
You must carefully consider the benefits and implications of each keying option
when selecting between them. For some specific module types, fewer options are
available.
You can find revision information on the General tab of a module’s Properties
dialog box.
IMPORTANT Changing electronic keying selections online may cause the I/O
communication connection to the module to be disrupted and may result in a
loss of data.
Exact Match
Exact Match keying requires all keying attributes, that is, Vendor, Product Type,
Product Code (catalog number), Major Revision, and Minor Revision, of the
physical module and the module created in the software to match precisely to
establish communication. If any attribute does not match precisely, I/O
communication is not permitted with the module or with modules connected
through it, as in the case of a communication module.
Use Exact Match keying when you need the system to verify that the module
revisions in use are exactly as specified in the project, such as for use in highly-
regulated industries. Exact Match keying is also necessary to enable Automatic
Firmware Update for the module via the Firmware Supervisor feature from a
Logix5000 controller.
Communication is prevented.
Physical Module
Vendor = Allen-Bradley QB1B
L24ER
0 1 2 3 4 5 6 7
SOURCE
24VDC
SINK\
INPUT
DC
8 9 10 11 12 13 14 15
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7
DC IN
00 08
01 09
02 10
04 12
05 13
06 14
Major Revision = 3 07 15
COM COM
0 1
NC NC
+V +V
Minor Revision = 2
00 08
01 09
02 10
03 11
04 12
00:00:BC:2E:69:F6 05 13
06 14
07 15
COM COM
0 1
DC OUT
+24VDC COM FG
IMPORTANT Changing electronic keying selections online may cause the I/O
Communication connection to the module to be disrupted and may result in a
loss of data.
Compatible Keying
Compatible Keying indicates that the module determines whether to accept or
reject communication. Different module families, communication adapters, and
module types implement the compatibility check differently based on the family
capabilities and on prior knowledge of compatible products. Release notes for
individual modules indicate the specific compatibility details.
Compatible Keying is the default setting. Compatible Keying allows the physical
module to accept the key of the module configured in the software, provided that
the configured module is one the physical module is capable of emulating. The
exact level of emulation required is product and revision specific.
With Compatible Keying, you can replace a module of a certain Major Revision
with one of the same catalog number and the same or later, that is higher, Major
Revision. In some cases, the selection makes it possible to use a replacement that
is a different catalog number than the original.
Communication is prevented.
Physical Module
Vendor = Allen-Bradley QB1B
L24ER
0 1 2 3 4 5 6 7
SOURCE
24VDC
SINK\
INPUT
DC
8 9 10 11 12 13 14 15
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7
DC IN
9 10 11 12 13 14 15
03 11
04 12
05 13
Major Revision = 3
06 14
07 15
COM COM
0 1
NC NC
+V +V
Minor Revision = 2 00 08
01 09
02 10
03 11
04 12
00:00:BC:2E:69:F6 05 13
06 14
07 15
COM COM
0 1
DC OUT
+24VDC COM FG
Communication is allowed.
Physical Module
Vendor = Allen-Bradley QB1B
L24ER
0 1 2 3 4 5 6 7
SOURCE
24VDC
SINK\
INPUT
DC
8 9 10 11 12 13 14 15
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7
DC IN
00 08
01 09
02 10
04 12
05 13
06 14
Major Revision = 3 07 15
COM COM
0 1
NC NC
+V +V
Minor Revision = 2
00 08
01 09
02 10
03 11
04 12
00:00:BC:2E:69:F6 05 13
06 14
07 15
COM COM
0 1
DC OUT
+24VDC COM FG
IMPORTANT Changing electronic keying selections online may cause the I/O
communication connection to the module to be disrupted and may result in a
loss of data.
Disabled Keying
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.
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.
Communication is prevented.
Physical Module
Vendor = Allen-Bradley QB1B
L24ER
0 1 2 3 4 5 6 7
SOURCE
24VDC
SINK\
INPUT
DC
8 9 10 11 12 13 14 15
DC
0 1 2 3 4 5 6 7
8 9 10 11 12 13 14 15
DC IN
00 08
01 09
03 11
04 12
05 13
Major Revision = 3 06 14
07 15
COM COM
0 1
NC NC
Minor Revision = 2 +V +V
00 08
01 09
02 10
03 11
04 12
00:00:BC:2E:69:F6 05 13
06 14
07 15
COM COM
0 1
DC OUT
+24VDC COM FG
Communication is allowed.
Physical Module
Vendor = Allen-Bradley QB1B
L24ER
0 1 2 3 4 5 6 7
SOURCE
24VDC
SINK\
INPUT
DC
8 9 10 11 12 13 14 15
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7
DC IN
9 10 11 12 13 14 15
03 11
04 12
05 13
Major Revision = 3
06 14
07 15
COM COM
0 1
NC NC
+V +V
Minor Revision = 2 00 08
01 09
02 10
03 11
04 12
00:00:BC:2E:69:F6 05 13
06 14
07 15
COM COM
0 1
DC OUT
+24VDC COM FG
IMPORTANT Changing electronic keying selections online may cause the I/O
communication connection to the module to be disrupted and may result in a
loss of data.
Configure Distributed I/O Your CompactLogix 5370 L2 control system can use distributed I/O modules on
an EtherNet/IP network.
Modules on an EtherNet/IP
Network IMPORTANT When adding distributed I/O modules, remember to count the remote Ethernet
adapter to remain within the maximum number of EtherNet/IP network nodes
limitation for your specific controller.
The distributed I/O modules connected to the controller via the remote
Ethernet adapter are not counted toward the maximum Ethernet node limit for
the controller.
For example, a 1769-L27ERM-QBFC1B controller supports up to 16 Ethernet
nodes. You can add up to 16 remote Ethernet adapters to the I/O Configuration
section because each remote adapter counts against the node count. However,
you can add as many remote I/O modules to the adapter’s chassis as necessary.
Remote I/O modules do not count against the node count.
For more information on node limitations, see Nodes on an EtherNet/IP
Network on page 118.
7. Repeat these steps to add all of the desired distributed I/O modules.
POINT I O
Module
Status
Network
Activity
Network
Status
Point Bus
Link 1 Status
Activity/
Status System
Power
Field
Computer Link 2
Activity/
Status
L27ERM 0 1 2 3 4 5 6 7 A0 B0 Z0
SOURCE
IN
24VDC
0 1 2 3 4 5 6 7 A0 B0 Z0
SINK\
INPUT
DC
HIGH SPEED
A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
SOURCE
IN
24VDC
SINK\
INPUT
DC
HIGH SPEED
A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
8 9 10 11 12 13 14 15 1 3 OK
8 9 10 11 12 13 14 15 1 3 OK
DC IN HSC
00 08 A0+ A0-
01 09 B0+ B0-
02 10 Z0+ Z0-
03 11 A1+ A1-
04 12 B1+ B1-
05 13 Z1+ Z1-
06 14 +V +V
OUT OUT
07 15 0 2
COM COM OUT 0UT
0 1 1 3
NC NC COM COM
V V
+V +V in in
0+ 2+
I I
00 08 in in
0+ 2+
V/I V/I
01 09 in in
0- 2-
CJC inV
02 10 + 3+
CJC inI
03 11 - 3+
V V/I
04 12 in in
1+ 3-
00:00:BC:2E:69:F6 05 13
I V/I
in in
1+ 1-
V V
06 14 OUT OUT
0+ 1+
I I
07 15 OUT in
0+ 1+
COM COM COM COM
0 1
DC OUT ANALOG
+24VDC
+24VDC COM
COM FG
FG
1769-L27ERM-QBFC1B Control System Kinetix 350 Drive Connected via a Kinetix 350 Drive Connected via a
1783-ETAP EtherNet/IP Tap 1783-ETAP EtherNet/IP Tap
Configure Distributed I/O Your CompactLogix 5370 L2 control system can use distributed I/O modules on
a DeviceNet network.
Modules on a DeviceNet
Network Complete these steps to configure distributed I/O modules on a
DeviceNet network.
5. Configure the new 1769-SDN scanner module as necessary and click OK.
IN
24VDC
0 1 2 3 4 5 6 7 A0 B0 Z0
SINK\
INPUT
DC
HIGH SPEED
A1 B1 Z1
COUNTER
QBFC1B 8 9 10 11 12 13 14 15
SOURCE
IN
24VDC
SINK\
INPUT
DC
HIGH SPEED
8 9 10 11 12 13 14 15 COUNTER A1 B1 Z1
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
8 9 10 11 12 13 14 15 1 3 OK
8 9 10 11 12 13 14 15 1 3 OK
DC IN HSC
00 08 A0+ A0-
01 09 B0+ B0-
02 10 Z0+ Z0-
03 11 A1+ A1-
04 12 B1+ B1-
05 13 Z1+ Z1-
06 14 +V +V
OUT OUT
07 15 0 2
COM COM OUT 0UT
0 1 1 3
NC NC COM COM
V V
+V +V in in
0+ 2+
I I
00 08 in in
0+ 2+
V/I V/I
01 09 in in
0- 2-
CJC inV
02 10 + 3+
CJC inI
03 11 - 3+
V V/I
04 12 in in
1+ 3-
00:00:BC:2E:69:F6 05 13
I V/I
in in
1+ 1-
V V
06 14 OUT OUT
0+ 1+
I I
07 15 OUT in
0+ 1+
COM COM COM COM
0 1
DC OUT ANALOG
+24VDC
+24VDC COM
COM FG
FG
Adapter
Status
DeviceNet
Status
PointBus
Status
1734-ADN
System
Power
DeviceNet
Power
1734-ADN POINT I/O Adapter 1606-XLDNET DeviceNet 1794-ADN FLEX I/O DeviceNet
with POINT I/O Modules Power Supply Adapter with FLEX I/O Modules
Monitor I/O Modules With CompactLogix 5370 L2 controllers, you can use the following options to
monitor I/O modules:
The following graphic shows the Quick View Pane indicating the type of fault.
To see the fault description on the Connection tab in Module Properties dialog
box, complete these steps.
2. Click the Connection tab and use the fault description, in the Module
Fault section, to diagnose the issue.
End-cap detection is performed through the last module on a 1769 Bus. If that
module experiences a fault such that it cannot communicate on the 1769 Bus, the
following events occur:
• Controller faults
Topic Page
Select I/O Modules 237
Validate I/O Layout 242
Configure I/O 252
Electronic Keying 254
Configure Distributed I/O Modules on an EtherNet/IP Network 260
Configure Distributed I/O Modules on a DeviceNet Network 263
Monitor I/O Modules 265
Select I/O Modules CompactLogix 5370 L3 control systems offer these I/O module options:
• Local Expansion Modules
• Distributed I/O Modules over an EtherNet/IP Network
• Configure Distributed I/O Modules on a DeviceNet Network
• The controllers support this many local Compact I/O modules across up
to three I/O banks, that is, the local bank and two additional banks.
• Consider using a 1492 wiring system for each I/O module as an alternative
to the terminal block that comes with the module.
• Use 1492 PanelConnect™ modules and cables if you are connecting input
modules to sensors.
That is, the expansion cable installed at the end of the local bank is
determined by how you connect to the first additional bank—on the
right or left side of the bank. See Figure 37 on page 239 for examples of
how to connect a local bank to additional banks.
c. Complete the installation of the remaining banks in your system.
IMPORTANT Make sure you install an end cap at the end of the last bank in
your system.
Horizontal Orientation
00:00:BC:2E:69:F6
1 (Front)
2 (Rear)
Bank 1
00:00:BC:2E:69:F6
1 (Front)
2 (Rear)
1769-CRRx Cable
Vertical Orientation
Bank 2
Wire each Compact I/O module used as a local expansion module according to
the technical documentation for that module.
You can include distributed I/O modules over an EtherNet/IP network in your
CompactLogix 5370 control system. Consider the following when using
distributed I/O modules over an EtherNet/IP network:
The following graphic shows an example 1769-L33ERM control system that uses
local expansion modules and distributed I/O modules over an EtherNet/IP
network.
002 1734-AENTR
POINT I O
Module
Status
Network
Activity
Network
Status
Point Bus
Link 1 Status
Activity/
Status System
Power
Field
Power
IP ADDRESS
Link 2
Activity/
Status
00:00:BC:2E:69:F6
1 (Front)
(Front)
2 (Rear)
You can include distributed I/O modules over a DeviceNet network in your
CompactLogix 5370 L3 control system. Consider the following when using
distributed I/O modules over a DeviceNet network:
You must use the following to use distributed I/O modules over a DeviceNet
network in your CompactLogix 5370 L3 control system:
The following graphic shows an example 1769-L33ERM control system that uses
local expansion modules and distributed I/O modules over a DeviceNet
network.
Local Expansion Modules Distributed I/O Modules
00:00:BC:2E:69:F6
1 (Front)
(Front)
2 (Rear)
Adapter
Status
DeviceNet
Status
PointBus
Status
1734-ADN
System
Power
DeviceNet
Power
Validate I/O Layout After you have selected your I/O modules, you must validate the system you want
to design. Consider these points when validating I/O layout placement:
• Estimate Requested Packet Interval
• Module Fault Related to RPI Estimates
• Calculate System Power Consumption
• Power Supply Distance Rating
• Physical Placement of I/O Modules
You can set individual Compact I/O modules’ RPI rates higher than those listed
in Table 31. The RPI shows how quickly modules can be scanned, not how
quickly an application can use the data. The RPI is asynchronous to the program
scan. Other factors, such as program execution duration, affect I/O throughput.
The 1769 Compact I/O power supplies provide power to CompactLogix local
and additional banks. The power provided is measured in current capacity.
• 1769 Compact I/O power supplies have two maximum current capacity
requirements that affect how you design and configure a single bank.
Current Capacity for Side of Bank Current Capacity for Side of Bank
00:00:BC:2E:69:F6
1 (Front)
2 (Rear)
Power Supply Current Capacity, max for Single Bank Current Capacity, max for Each Side of
Cat. No. Bank(1)
1769-PA2
2 A at 5V DC and 0.8 A at 24V DC 1 A at 5V DC and 0.4 A at 24V DC
1769-PB2
1769-PA4
4 A at 5V DC and 2 A at 24V DC 2 A at 5V DC and 1 A at 24V DC
1769-PB4
(1) Specification for banks with devices on both left and right sides of the power supply.
IMPORTANT A single bank, requires the CompactLogix 5370 L3 controllers to reside in the
leftmost slot. At minimum, you must calculate the controller’s power
consumption on the left side of the power supply.
If additional modules are exist on the left side of the power supply, you must
calculate the power consumption for those modules as well.
If additional modules are installed to the right of the power supply, you must
calculate the power consumption for that side separately.
Total Current Required for Single Bank if Modules Are Installed on Both Sides of the Power Supply(1):
(1) This number must not exceed the power supply current capacity for the bank.
(2) This number must not exceed the power supply current capacity for this side of the bank.
(3) In the local bank, you can only install up to three modules to the left of the power supply because the CompactLogix 5370 L3 controllers have a power supply distance rating of four and must be within
four slots of the Compact I/O power supply. On the right side of the power supply in the local bank and both sides of the power supply in additional banks, you can install up to eight modules if power
supply distance ratings for the modules validate the system design.
IMPORTANT In additional banks, you can install I/O modules to the left side, right side or
both sides of the power supply.
The system design determines how to use the table below.
Total Current Required for Bank if Modules Are Installed on Both Sides of the Power Supply(1):
(1) This number must not exceed the power supply current capacity for the bank.
(2) This number must not exceed the power supply current capacity for this side of the bank.
(3) You can install up to eight modules in additional banks if the power supply distance ratings for the modules validate the system design.
• You can install I/O modules to the left and right of the power supply.
• When a system requires more than one bank, you can install the additional
banks horizontally or vertically, as shown in this graphic.
Horizontal Orientation
00:00:BC:2E:69:F6
1 (Front)
2 (Rear)
Local Bank
00:00:BC:2E:69:F6
1 (Front)
2 (Rear)
Additional Bank
• Each I/O module also has a power supply distance rating and specific
maximum current draw. Considered jointly, distance ratings and current
draw determine where I/O modules can be placed in a bank and what
configuration of modules may be installed in the bank.
For more information on power supply distance ratings, see Power Supply
Distance Rating on page 69. For more information on system power
consumption, see Calculate System Power Consumption on page 244.
Local Bank
To validate the local bank design, confirm the design meets these requirements:
• No more than three modules are installed between the controller and the
left side of the power supply.
• No more than eight modules are installed to the right of the power supply.
• The modules’ power consumption on each side of the power supply does
not exceed the power supply’s capacity for that side.
• The total power consumption by all modules in the bank does not exceed
the power supply’s capacity for the entire bank.
• Modules are installed such that all power supply distance rating and system
power consumption requirements are met.
For example, the 1769-SDN scanner module has a power supply distance
rating of four. If the design includes the installation of a 1769-SDN
scanner with greater than three modules between it and the power supply,
the design is invalid.
IMPORTANT With respect to power supply distance ratings, if you install a module that
violates its power supply distance rating specification, the system may appear
to operate normally for a period of time but could experience operational
issues over time, such as I/O faults.
00:00:BC:2E:69:F6
1 (Front)
2 (Rear)
Additional Banks
If your application calls for twelve or more I/O modules, at minimum, you must
install the modules in multiple banks additional banks. The number of additional
banks is determined by the specific conditions of each application.
Once the local bank design is validated, you must validate the design for any
additional banks. To validate additional bank designs, confirm the design meets
these requirements:
TIP Compact I/O expansion cables have the same dimensions as the end
caps regardless of whether they are installed at the right or left side of
the communication bus.
• No more than eight modules are installed on either side of the power
supply.
• The modules’ power consumption on each side of the power supply does
not exceed the power supply’s capacity for that side.
• Modules are installed such that all power supply distance rating
requirements are met.
Local Bank
00:00:BC:2E:69:F6
1 (Front)
2 (Rear)
1769-CRRx Cables
Additional Bank
End Cap
Local Bank
In the local bank, the controller must be the leftmost device in the system and
you can only install up to three modules between the controller and the power
supply. Therefore, any Compact I/O modules that are installed to the left of the
power supply in the local bank, are in a module slot that meets the module’s
power supply distance rating requirements.
Additional Banks
CompactLogix 5370 L3 control systems also support the use of additional banks
for the system’s local expansion modules. Every additional bank requires a 1769
Compact I/O power supply. The bank can be designed with local expansion
modules on either side of the power supply.
Most Compact I/O modules have power supply distance rating values that allow
you to install them in any slot on either side of the power supply in additional
banks. Some Compact I/O modules have power supply distance ratings that
affect where you can install them in the CompactLogix 5370 L3 control system.
In this case, you must install the 1769-ASCII module and 1769-HSC high-speed
counter module with no more three Compact I/O modules between the module
and the power, regardless of whether the modules are installed to the left or right
of the power supply.
Local Bank
00:00:BC:2E:69:F6
1 (Front)
2 (Rear)
Additional Bank
IMPORTANT The previous table shows example systems with 1769-HSC high-speed counter
modules in each control system because it has a power supply distance rating
of four and cannot be installed as far from the Compact I/O power supply. Most
Compact I/O modules have power supply distance ratings that allow you to
install them anywhere in the local expansion slots of a CompactLogix 5370 L2
control system.
For more information about the power supply distance rating for a Compact I/O
module, see CompactLogix Selection Guide, publication 1769-SG001.
Configure I/O Complete these steps to add a Compact I/O module to your
CompactLogix 5370 L3 control system and configure it.
While the configuration options vary from module to module, there are some
common options you typically configure when using Compact I/O modules in a
CompactLogix 5370 L3 control system, as described in Table 34.
Table 34 - Common Configuration Parameters
Configuration Option Description
Requested packet interval (RPI) The RPI specifies the interval at which data is transmitted or received over a connection. For 1769 Compact Local I/O modules, data is
transmitted to the controller at the RPI.
When scanned on the local bus or over an EtherNet/IP network, input modules are scanned at the RPI specified in the module
configuration. Typically, you configure an RPI in milliseconds (ms). For I/O modules, the range is 0.5…750 ms.
When scanned over a DeviceNet network, distributed input modules are scanned at the rate supported by the DeviceNet adapter module
connecting the input modules to the network. For example, the scan rate for distributed 1734 POINT I/O over DeviceNet can occur only as
quickly as the 1734-ADN DeviceNet adapter can transmit the data.
Module definition Set of configuration parameters that affect data transmission between the controller and the I/O module. The parameters include the
following:
• Series - Module’s hardware series.
• Revision - Major and minor firmware revision levels used on the module.
• Electronic keying - See page 254.
• Connection - Type of connection between the controller writing the configuration and the I/O module, such as Output.
• Data format - Type of data transferred between the controller and I/O module and what tags are generated when the configuration is
complete.
Module Fault on Controller If Connection This option determines how the controller is affected if the connection to an I/O module fails in Run mode. You can configure the project
Fails While in Run Mode so that a connection failure causes a major fault on the controller or not.
The default setting is for the option to be enable, that is, if the connection to an I/O module fails in Run mode, a major fault will occur on
the controller.
I/O Connections
Electronic Keying The electronic keying feature automatically compares the expected module, as
shown in the I/O Configuration tree, to the physical module before I/O
communication begins. You can use electronic keying to help prevent
communication to a module that does not match the type and revision expected.
For each module in the I/O Configuration tree, the user-selected keying option
determines if, and how, an electronic keying check is performed. Typically, three
keying options are available:
• Exact Match
• Compatible Keying
• Disable Keying
You must carefully consider the benefits and implications of each keying option
when selecting between them. For some specific module types, fewer options are
available.
You can find revision information on the General tab of a module’s Properties
dialog box.
IMPORTANT Changing electronic keying selections online may cause the I/O
communication connection to the module to be disrupted and may result in a
loss of data.
Exact Match
Exact Match keying requires all keying attributes, that is, Vendor, Product Type,
Product Code (catalog number), Major Revision, and Minor Revision, of the
physical module and the module created in the software to match precisely to
establish communication. If any attribute does not match precisely, I/O
communication is not permitted with the module or with modules connected
through it, as in the case of a communication module.
Use Exact Match keying when you need the system to verify that the module
revisions in use are exactly as specified in the project, such as for use in highly-
regulated industries. Exact Match keying is also necessary to enable Automatic
Firmware Update for the module via the Firmware Supervisor feature from a
Logix5000 controller.
Communication is prevented.
Physical Module
Vendor = Allen-Bradley
Product Type = Digital Output Module
Catalog Number = 1769-OB32
Major Revision = 3
Minor Revision = 2
00:00:BC:2E:69:F6
1 (Front)
2 (Rear)
IMPORTANT Changing electronic keying selections online may cause the I/O
Communication connection to the module to be disrupted and may result in a
loss of data.
Compatible Keying
Compatible Keying indicates that the module determines whether to accept or
reject communication. Different module families, communication adapters, and
module types implement the compatibility check differently based on the family
capabilities and on prior knowledge of compatible products. Release notes for
individual modules indicate the specific compatibility details.
Compatible Keying is the default setting. Compatible Keying allows the physical
module to accept the key of the module configured in the software, provided that
the configured module is one the physical module is capable of emulating. The
exact level of emulation required is product and revision specific.
With Compatible Keying, you can replace a module of a certain Major Revision
with one of the same catalog number and the same or later, that is higher, Major
Revision. In some cases, the selection makes it possible to use a replacement that
is a different catalog number than the original.
Communication is prevented.
Physical Module
Vendor = Allen-Bradley
Product Type = Digital Output Module
Catalog Number = 1769-OB32
Major Revision = 3
Minor Revision = 2
00:00:BC:2E:69:F6
1 (Front)
2 (Rear)
Communication is allowed.
Physical Module
Vendor = Allen-Bradley
Product Type = Digital Output Module
Catalog Number = 1769-OA16
Major Revision = 3
Minor Revision = 2
00:00:BC:2E:69:F6
1 (Front)
2 (Rear)
IMPORTANT Changing electronic keying selections online may cause the I/O
communication connection to the module to be disrupted and may result in a
loss of data.
Disabled Keying
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.
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.
Communication is prevented.
Physical Module
Vendor = Allen-Bradley
Product Type = Digital Output Module
Catalog Number = 1769-IT6
Major Revision = 3
Minor Revision = 2
00:00:BC:2E:69:F6
1 (Front)
2 (Rear)
Communication is allowed.
Physical Module
Vendor = Allen-Bradley
Product Type = Digital Output Module
Catalog Number = 1769-OB16
Major Revision = 3
Minor Revision = 2
00:00:BC:2E:69:F6
1 (Front)
2 (Rear)
IMPORTANT Changing electronic keying selections online may cause the I/O
communication connection to the module to be disrupted and may result in a
loss of data.
Configure Distributed I/O Your CompactLogix 5370 L3 control system can use distributed I/O modules on
an EtherNet/IP network.
Modules on an EtherNet/IP
Network IMPORTANT When adding distributed I/O modules, remember to count the remote Ethernet
adapter to remain within the maximum number of EtherNet/IP network nodes
limitation for your specific controller.
The remote I/O modules connected to the controller via the Ethernet adapter
are not counted toward the maximum Ethernet node limit for the controller.
For more information on node limitations, see Nodes on an EtherNet/IP
Network on page 118.
7. Repeat these steps to add all the desired distributed I/O modules.
Computer 00:00:BC:2E:69:F6
1 (Front)
(Front)
2 (Rear)
LINK 1 LINK 2
Configure Distributed I/O Your CompactLogix 5370 L3 control system can use distributed I/O modules on
a DeviceNet network.
Modules on a DeviceNet
Network Complete these steps to configure distributed I/O modules on a
DeviceNet network.
5. Configure the new 1769-SDN scanner module as necessary and click OK.
00:00:BC:2E:69:F6
1 (Front)
(Front)
2 (Rear)
Adapter
Status
DeviceNet
Status
PointBus
Status
1734-ADN
System
Power
DeviceNet
Power
1734-ADN POINT I/O Adapter 1606-XLDNET DeviceNet 1794-ADN FLEX I/O DeviceNet
with POINT I/O Modules Power Supply Adapter with FLEX I/O Modules
Monitor I/O Modules With CompactLogix 5370 L3 controllers, you can monitor I/O modules in the
following ways:
The following graphic shows the Quick View Pane indicating the type of fault.
To see the fault description on the Connection tab in Module Properties dialog
box, complete these steps.
2. Click the Connection tab and use the fault description, in the Module
Fault section, to diagnose the issue.
• Controller faults
Develop Applications
Topic Page
Elements of a Control Application 267
Tasks 268
Programs 272
Routines 274
Tags 275
Programming Languages 278
Add-On Instructions 279
Monitoring Controller Status 280
Monitoring I/O Connections 281
System Overhead Time Slice 284
Additional Resources 287
Elements of a Control A control application is comprised of several elements that require planning for
efficient application execution. Application elements include the following:
Application
• Tasks
• Programs
• Routines
• Tags
Task 32
Task 1
Configuration
Status
Watchdog
Program 100
Program 1
Program
Main Routine (local) Tags
Fault Routine
Other
Routines
Controller (global)
Tags I/O Data System-shared Data
Tasks A Logix5000 controller lets you use multiple tasks to schedule and prioritize the
execution of your programs based on specific criteria. This multitasking allocates
the controller’s processing time among the different operations in your
application:
• The controller executes only one task at a time.
• One task can interrupt another’s execution and take control.
• In any given task, multiple programs may be used. However, only one
program executes at a time.
Control Application
Task 32
Task 1 Task 1
Contains the following: Configuration
• Configuration Data
Status
• Status Data
• Watchdog Data Watchdog
• Programs Program 100
Program 1
Program
Main Routine (local) Tags
Fault Routine
Other Routines
Controller (global)
I/O Data System-shared Data
Tags
Main Task
(continuous)
Task 2
(periodic)
Task 3
(event)
A task provides scheduling and priority information for a set of one or more
programs. Configure tasks as continuous, periodic, or event by using the Task
Properties dialog box.
A task can have up to 100 separate Programs per task, each with its own
executable routines and program-scoped tags. Once a task is triggered (activated),
all of the programs assigned to the task execute in the order in which they are
grouped. Programs can appear only once in the Controller Organizer and cannot
be shared by multiple tasks.
Task Priority
Each task in the controller has a priority level. The operating system uses the
priority level to determine which task to execute when multiple tasks are
triggered. A higher priority task will interrupt any lower priority task. The
continuous task has the lowest priority and is always interrupted by a periodic or
event task.
You can configure periodic tasks to execute from the lowest priority of 15 up to
the highest priority of 1. Configure the task priority using the Task Properties
dialog box.
Programs The controller operating system is a preemptive multitasking system that is IEC
1131-3 compliant. This system provides the following:
• Programs to group data and logic
• Routines to encapsulate executable code written in a single programming
language
Task 32
Task 1
Configuration
Status
Watchdog
Program 100
Program 1
Program 1
Program (local)
Contains the following:
Main Routine Tags
• Main Routine
• Fault Routine
• Other Routines Fault Routine
• Program Tags
Other Routines
Program
Program
Unscheduled programs in a task are downloaded to the controller with the entire
project. The controller verifies unscheduled programs but does not execute them.
You must schedule a program in a task before the controller can scan the
program. To schedule an unscheduled program, use the Program/Phase Schedule
tab of the Task Properties dialog box.
You can also specify an optional program fault routine. The controller executes
this routine if it encounters an instruction-execution fault in any of the routines
in the associated program.
Task 32
Task 1
Configuration
Status
Watchdog
Program 100
Program 1
Program (local)
Main Routine Tags
Fault Routine
Other Routines
Controller (global)
Tags I/O Data System-shared Data
Routine
Routine
Tags With a Logix5000 controller, you use a tag (alphanumeric name) to address data
(variables). In Logix5000 controllers, there is no fixed, numeric format. For
example, as shown below, you can use the tag name north_tank_mix instead of a
numeric format, such as N7:0.0.
The tag name itself identifies the data. This lets you do the following:
• Organize your data to mirror your machinery.
• Document your application as you develop it.
This example shows data tags created in the scope of the Main Program of the
controller.
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.
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 In the Tag Editor, add extended properties to a tag.
User-defined data type In the Data Type Editor, add extended properties to data types.
Add-On Instructions In the properties associated with the Add-On Instruction definition, add
extended properties to Add-On Instructions.
You need to know which tags have limits associated with them as there is no
indication in the tag browser that extended properties are defined for a tag. If,
however, you try to use extended properties that have not been defined for a tag,
the editors show a visual indication and the routine does not verify.
You can access limits defined on tags by using the .@Min and .@Max syntax:
• You cannot write to extended properties values in logic.
• To use extended tag properties in an Add-On Instruction, you must pass
them in as input operands to the Add-On Instruction.
• Aliases to tags that have extended properties cannot access the extended
properties in logic.
• Limits can be configured for input and output parameters in Add-On
Instructions. However, limits cannot be defined on an InOut parameter of
an Add-On Instruction.
• Limits cannot be accessed inside Add-On Instruction logic. Limits are for
use by HMI applications only.
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 have 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.
Programming Languages The CompactLogix controller supports these programming languages, both
online and offline.
Add-On Instructions 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 Source Protection.
• Reduce documentation development time.
You can use Add-On Instructions across multiple projects. You can define your
instructions, obtain them from somebody else, or copy them from another
project.
This table explains some of the capabilities and advantages of use Add-On
Instructions.
Monitoring Controller Status The CompactLogix 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 tool bar.
When you add a GSV/SSV instruction to the program, the valid object classes,
object names, and attribute names for each instruction are displayed. For the
GSV instruction, you can get values for all the available attributes. For the SSV
instruction, only those attributes you are allowed to set are displayed.
Some object types appear repeatedly, so you may have to specify the object name.
For example, there can be several tasks in your application. Each task has its own
Task object that you access by the task name.
There are several objects and attributes that you can use the GSV and SSV
instructions to monitor and set the system. For more information about GSV
instructions, SSV instructions, objects, and attributes see the Logix5000
Controllers General Instructions Reference Manual, publication 1756-RM003.
Monitoring I/O Connections If communication with a device in the controller’s I/O configuration does not
occur in an application-specific period of time, the communication times out and
the controller produces warnings.
The minimum timeout period that, once expired without communication, causes
a timeout is 100 ms. The timeout period may be greater, depending on the
application’s RPI. For example, if your application uses the default RPI = 20 ms,
the timeout period is 160 ms.
For more information on how to determine the time for your application, see
Rockwell Automation Knowledgebase Tech Note 38535. The document is
available at http://www.rockwellautomation.com/knowledgebase/.
• A ! shows over the I/O configuration folder and over the devices that
have timed out.
• A module fault code is produced, which you can access via the following:
– The Module Properties dialog box
– A GSV instruction
For more information about I/O faults, see the Major, Minor, and I/O Faults
Programming Manual, publication 1756-PM014.
For more information about attributes available with the Module object, see the
Logix5000 Controllers General Instructions Reference Manual, publication
1756-RM003.
For more information about attributes available with the Module object, see the
Logix5000 Controllers General Instructions Reference Manual, publication
1756-RM003.
First, develop a routine in the Controller Fault Handler that can respond to I/O
connection faults. Then, in the Module Properties dialog box of the I/O module
or parent communication module, check Major Fault On Controller If
Connection Fails While in Run Mode.
For more information about programming the Controller Fault Handler, see the
Major, Minor, and I/O Faults Programming Manual, publication 1756-PM014.
System Overhead Time Slice The controller communicates with other devices at either a specified rate
(scheduled) or when there is processing time available to service the
communication.
The system overhead time slice specifies the percentage of time a controller
devotes to service communication. If you have a continuous task, the System
Overhead Time Slice entered in the Advanced tab of the Controller Properties
dialog box specifies continuous task/service communication ratio. However, if
there is no continuous task, the overhead time slice has no affect.
The table shows the ratio between the continuous task and service
communication at various system overhead time slices.
As shown in Table 40, if the system overhead time slice is less than or equal to
50%, the duration stays 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.
The application includes sample projects that you can copy and modify to fit
your application. To access the sample projects, complete these steps.
Additional Resources These documents contain additional information concerning products from
Rockwell Automation.
Resource Description
Logix5000 Controllers and I/O Tag Data Programming Manual, publication 1756-PM004 Explains procedures for using and organizing I/O data tags.
Logix5000 Controllers Common Procedures Programming Manual, publication Guides all user levels in developing projects for Logix5000 controllers and provides links to
1756-PM001 individual guides for information on topics such as import/export, messages, security,
and programming in different languages.
Add-On Instructions Programming Manual, publication 1756-PM010 Explains Add-On Instructions and how to use them.
Logix5000 Controllers General Instructions Reference Manual, publication 1756-RM003 Provides details about instructions for programming a Logix5000 controller.
Major, Minor, and I/O Faults Programming Manual, publication 1756-PM014 Explains major, minor, and I/O faults as well as the Controller Fault Handler.
Logix5000 Controllers Design Considerations Reference Manual, publication 1756-RM094 Provides advanced users with guidelines for system optimization and with system
information to guide system design choices.
Logix5000 Controllers Execution Time and Memory Use Reference Manual, publication Assists in estimating the memory use and execution time of programmed logic and in
1756-RM087 selecting among different programming options.
Notes:
Topic Page
Motion Axes Support 290
Maximum Number of Position Loop-configured Drives 291
Time Synchronization 292
Configure Integrated Motion on the EtherNet/IP Network 293
Scalability in Applications Using Integrated Motion on EtherNet/IP Networks 297
AXIS_VIRTUAL Axis
The AXIS_VIRTUAL axis is an internal axis representation that is not
associated with any physical drives. That is, you can configure the axis but it does
not cause any physical motion in your system.
AXIS_CIP_DRIVE Axis
The AXIS_CIP_DRIVE axis is a motion axis used with physical drives to cause
physical motion in your system as determined by your application.
Configuration Types
When adding an axis to your project, you must associate the axis to a drive.
Among other configuration parameters, you must select a configuration type.
The axis configuration type is also considered the drive configuration type.
Drives are counted among the number of nodes in the I/O Configuration section
of an RSLogix 5000 project. If you use the maximum number of drives that a
1769-L18ERM-BB1B, 1769-L27ERM-QBFC1B, 1769-L30ERM,
1769-L33ERM, or 1769-L36ERM controller supports in a single system, you
cannot add other EtherNet/IP devices to that project.
Time Synchronization Integrated Motion over an EtherNet/IP network requires Time Synchronization,
also known as CIP Sync. CIP Sync provides accurate real-time (real-world time)
or Coordinated Universal Time (UTC) synchronization of CompactLogix 5370
controllers and devices connected over an EtherNet/IP network.
IMPORTANT While all CompactLogix 5370 controllers are CIP Sync-capable, not all
of the controllers support Integrated Motion over an EtherNet/IP
network.
A controller must be CIP Sync-capable and synchronized with other
devices on the EtherNet/IP network to support Integrated Motion over
an EtherNet/IP network. However, the condition of being CIP
Sync-capable does not exclusively qualify a CompactLogix 5370
controller to support Integrated Motion over an EtherNet/IP network.
Table 41 on page 291 lists the CompactLogix 5370 controllers that
support Integrated Motion over an EtherNet/IP network.
CIP Sync requires that devices in the system function in the following roles:
Configure Integrated Motion To use Integrated Motion on the EtherNet/IP network, complete these steps.
on the EtherNet/IP Network
IMPORTANT These steps show a 1769-L36ERM controller. The same steps apply to other
CompactLogix 5370 controllers that support Integrated Motion over an
EtherNet/IP network with slight variations in screens.
IMPORTANT This section assumes you have previously created a project for your
1769-L36ERM controller. If you have not, do so before continuing.
4. Click OK.
Add a Drive
You can use these drives only in an application that uses Integrated Motion over
an EtherNet/IP network:
• Kinetix 350 drive
• Kinetix 6500 drive
• PowerFlex 755 AC drive
IMPORTANT These steps show a Kinetix 350 drive in a 1769-L36ERM control system. The
same steps apply to other CompactLogix 5370 controllers that support
Integrated Motion over an EtherNet/IP network with slight variations in
screens.
1. In the I/O configuration tree, right-click the Ethernet network and choose
New Module.
For information on setting the IP addresses, see the publications for each
drive type listed on page 12.
Scalability in Applications CompactLogix 5370 controllers offer varying levels of flexibility and scalability
to operate in control systems using Integrated Motion on EtherNet/IP networks.
Using Integrated Motion on
EtherNet/IP Networks
1769-L30ERM, 1769-L33ERM, and 1769-L36ERM Controllers
You can use the following controllers in control systems requiring simpler
configuration and complex configuration of Integrated Motion on EtherNet/IP
networks parameters:
• 1769-L30ERM
• 1769-L33ERM
• 1769-L36ERM
00:00:BC:2E:69:F6
1 (Front)
2 (Rear)
1
P
W
R
Terminal
00:00:BC:2E:69:F6
1 (Front)
2 (Rear)
4 3
2 1
Kinetix 6500
Drives
POINT I/O
Modules PowerFlex 755 Drive
1769-L18ERM-BB1B Controller
IP Address:
ENET Address: 00:00:BC:66:0F:C7
Computer 1769-L18ERM-BB1B
Controller
P
W
R
1769-L27ERM-QBFC1B Controller
The simpler control system often includes unmanaged switches, such a Stratix
2000 switch, and Kinetix 350 drives, as shown in this example.
L27ERM 0 1 2 3 4 5 6 7 A0 B0 Z0
SOURCE
IN
24VDC
0 1 2 3 4 5 6 7 A0 B0 Z0
SINK\
INPUT
DC
HIGH SPEED
A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
SOURCE
IN
24VDC
QBFC1B
SINK\
INPUT
DC
HIGH SPEED
A1 B1 Z1
COUNTER
8 9 10 11 12 13 14 15
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
OUT
OUTPUT
SOURCE
24VDC
DC
0 1 2 3 4 5 6 7 0 2 FUSE
8 9 10 11 12 13 14 15 1 3 OK
8 9 10 11 12 13 14 15 1 3 OK
DC IN HSC
00 08 A0+ A0-
01 09 B0+ B0-
02 10 Z0+ Z0-
03 11 A1+ A1-
Computer 1769-L27ERM-QBFC1B
04 12 B1+ B1-
05 13 Z1+ Z1-
06 14 +V +V
OUT OUT
07 15 0 2
COM COM OUT 0UT
1 3
Controller
0 1
NC NC COM COM
V V
+V +V in in
0+ 2+
I I
00 08 in in
0+ 2+
V/I V/I
01 09 in in
0- 2-
CJC inV
02 10 + 3+
CJC inI
03 11 - 3+
V V/I
04 12 in in
1+ 3-
00:00:BC:2E:69:F6 05 13
I V/I
in in
1+ 1-
V V
06 14 OUT OUT
0+ 1+
I I
07 15 OUT in
0+ 1+
COM COM COM COM
0 1
DC OUT ANALOG
This chapter describes the primary tasks required to store a project on an SD card
or load a project from an SD card to the CompactLogix 5370 controller.
Topic Page
Store or Load a Project with the Secure Digital Card 303
Store a Project 304
Load a Project 307
IMPORTANT The life expectancy of flash media is strongly dependent on the number of
write cycles that are performed. Flash media uses wear leveling but users
should avoid frequent writes.
Avoiding frequent writes is particularly important when logging data. We
recommend that you log data to a buffer in your controller’s memory and limit
the number of times data is written to removable media.
IMPORTANT We recommend that you leave the SD card installed in the controller and the
card unlocked. The SD card saves extended diagnostic information you can
send to Rockwell Automation that provides enhanced diagnostics of your
application and firmware revision should circumstances require this data.
This section briefly describes how to use the SD card when installed in a
CompactLogix 5370 controller, that is, how to store a project from the
controller to the SD card and how to load a project from the SD card to the
controller.
However, you may need to complete other tasks using the SD card, such as
the following:
• Change the image that is loaded from the card
• Check for a load that was completed
• Clear an image from the memory card
• Store an empty image
• Change load parameters
• Read/write application data to the card
For more detailed information about using an SD card, see the Logix5000
Controllers Nonvolatile Memory Card Programming Manual, publication
1756-PM017.
Store or Load a Project with There are several options for when to load the project back into the
CompactLogix 5370 controller’s user memory (RAM). The option used is
the Secure Digital Card determined by the controller configuration.
The following table describes the conditions in which a project is loaded from as
described in the following table.
Condition to Load Required Setting in Notes
Project From an SD Controller
Card into Controller Configuration
RAM
Controller power-up On Power Up • During a power cycle, you lose any online changes and tag
values you have not stored on the memory card.
• A load from a memory card may also change the firmware of
the controller.
• For more information, see the Logix5000 Controllers
Nonvolatile Memory Card Programming Manual, publication
1756-PM017.
• You can always use the application to load the project.
No project in the On Corrupt Memory • During a power cycle, you lose any online changes and tag
controller and you values you have not stored on the memory card.
power-up the • A load from a memory card may also change the firmware of
controller the controller.
• For more information, see the Logix5000 Controllers
Nonvolatile Memory Card Programming Manual, publication
1756-PM017.
• You can always use the application to load the project.
Only through User Initiated You lose any online changes and tag values you have not stored on
application the memory card.
Store a Project Follow these steps to store a project. These steps show a 1769-L18ERM-BB1B
controller. The same steps apply for other CompactLogix 5370 controllers.
6. Choose under what conditions to load the project into the user memory of
the controller.
Project that is currently on the memory card of Project that is currently in the user memory of
the controller (if any project is there). the controller.
After you click Store, the project is saved to the SD card as indicated by the
controller status indicators. These conditions may exist:
– After the controller fully resets itself, the OK indicator is solid green.
IMPORTANT Allow the store to complete without interruption. If you interrupt the
store, data corruption or loss may occur.
Load a Project Follow these steps to use the application to load the project from an SD card.
These steps show a 1769-L18ERM-BB1B controller. The same steps apply for
other CompactLogix 5370 controllers.
6. Click Load.
Project that is currently on the memory card of the Project that is currently in the user memory of
controller (if any project is there). the controller.
After you click Load, the project is loaded into the controller as indicated by the
controller status indicators. These conditions may exist:
– After the controller fully resets itself, the OK indicator is solid green.
Status Indicators
Use the CompactLogix 5370 The following graphic shows the controller status indicators for all of the
CompactLogix 5370 controllers.
Controllers Status Indicators
Notes:
IMPORTANT Before using this section, first use the information at Nodes on an EtherNet/IP
Network on page 118 when designing and configuring your CompactLogix
5370 control system.
For more information on how to best design EtherNet/IP network use in your
CompactLogix 5370 control system, see these resources:
• The EtherNet/IP Capacity Tool available at http://
www.rockwellautomation.com/solutions/integratedarchitecture/
resources3.html#enetpredict.
The EtherNet/IP Capacity Tool helps you in the initial layout of your
EtherNet/IP network.
History of Changes
Changes to the Manual With the availability of new controllers, modules, applications, and
programming software features, this manual has been revised to include updated
information. This appendix briefly summarizes changes that have been made with
previous revisions of this manual.
IMPORTANT This appendix does not list the changes that have been implemented with this
revision of the publication.
For a list of changes made in this revision of the publication, see Summary of
Changes on page 3.
Reference this appendix if you need information to determine what changes have
been made across multiple revisions. This may be especially useful if you are
deciding to upgrade your hardware or software based on information added with
previous revisions of this manual.
This table lists the publication revision, publication date, and changes made with
the revision.
Table 50 - History of Changes
Publication Revision and Date Topic
1769-UM021C-EN-P, May 2012 Added the description of CompactLogix 5370 L2 controllers, including the
following content:
• Installing the controller
• Control system components
• Controller functionality
• Example system configurations on an EtherNet/IP network
• Example system configurations on a DeviceNet network
• Using I/O modules with the controller 169
• Motion support with the 1769-L27ERM-QBFC1B controller
• EtherNet/IP network connection specifications
1769-UM021B-EN-P, February 2012 Removed the descriptions of the I/O Event Task and its use with the
CompactLogix 5370 L1 controllers.
In RSLogix 5000 software, version 20.xx.xx, you can configure the I/O Event
Task for your CompactLogix 5370 L1 controller’s project. However, the task
will never be triggered because the functionality has been disabled in the
controller.
Notes:
S
sample projects 286
For an additional level of technical phone support for installation, configuration, and troubleshooting, we offer
TechConnectSM support programs. For more information, contact your local distributor or Rockwell Automation
representative, or visit http://www.rockwellautomation.com/support/.
Installation Assistance
If you experience a problem within the first 24 hours of installation, review the information that is contained in this
manual. You can contact Customer Support for initial help in getting your product up and running.
United States or Canada 1.440.646.3434
Outside United States or Canada Use the Worldwide Locator at http://www.rockwellautomation.com/support/americas/phone_en.html, or contact your local Rockwell
Automation representative.
Rockwell Automation tests all of its products to ensure that they are fully operational when shipped from the
manufacturing facility. However, if your product is not functioning and needs to be returned, follow these procedures.
United States Contact your distributor. You must provide a Customer Support case number (call the phone number above to obtain one) to your
distributor to complete the return process.
Outside United States Please contact your local Rockwell Automation representative for the return procedure.
Documentation Feedback
Your comments will help us serve your documentation needs better. If you have any suggestions on how to improve this
document, complete this form, publication RA-DU002, available at http://www.rockwellautomation.com/literature/.
Rockwell Otomasyon Ticaret A.Ş., Kar Plaza İş Merkezi E Blok Kat:6 34752 İçerenköy, İstanbul, Tel: +90 (216) 5698400