Allen Bradley User Manual 1769-Um021 PDF
Allen Bradley User Manual 1769-Um021 PDF
Allen Bradley User Manual 1769-Um021 PDF
Activities including installation, adjustments, putting into service, use, assembly, disassembly, and maintenance are required
to be carried out by suitably trained personnel in accordance with applicable code of practice.
If this equipment is used in a manner not specified by the manufacturer, the protection provided by the equipment may be
impaired.
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.
IMPORTANT Identifies information that is critical for successful application and understanding of the product.
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.
ARC FLASH HAZARD: Labels may be on or inside the equipment, for example, a motor control center, to alert people to
potential Arc Flash. Arc Flash will cause severe injury or death. Wear proper Personal Protective Equipment (PPE). Follow ALL
Regulatory requirements for safe work practices and for Personal Protective Equipment (PPE).
Allen-Bradley, Rockwell Software, Rockwell Automation, ArmorBlock, CompactLogix, Compact I/O, ControlFLASH, ControlLogix, DriveLogix, FLEX, FlexLogix, Kinetix, PanelView, POINTBus, POINT I/O,
PowerFlex, QuickView, RSLinx, RSLogix, RSNetWorx, SoftLogix, Stratix, Stratix 5700, Stratix 6000, Studio 5000, and Studio 5000 Logix Designer 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
Added 1769-L19ER-BB1B information Throughout
document
Added section Install the Removable Terminal Block 25
Added section Install the Removable Terminal Block 49
Added section Install the Removable Terminal Block 64
Updated the information on depleting stored energy from the 1769-L30ER-NSE 118
Notes:
Chapter 1
Install the CompactLogix 5370 L1 Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Controller CompactLogix 5370 L1 Controller Parts . . . . . . . . . . . . . . . . . . . . . . . 18
Installation Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Install the Secure Digital Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Install the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Mount the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Ground the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Install the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Install the Removable Terminal Block. . . . . . . . . . . . . . . . . . . . . . . . . . 25
Connect Power to the Controller (Series B) . . . . . . . . . . . . . . . . . . . . 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 L2 Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Controller CompactLogix 5370 L2 Controller Parts . . . . . . . . . . . . . . . . . . . . . . . 37
Installation Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Install the Secure Digital Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Install the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Mount the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Ground the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Install the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Install the Removable Terminal Block. . . . . . . . . . . . . . . . . . . . . . . . . . 49
Wire the Terminal Block. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Wire Size and Terminal Screw Torque . . . . . . . . . . . . . . . . . . . . . . . . . 50
Connect Power to the Control System . . . . . . . . . . . . . . . . . . . . . . . . . 50
Connect to the Controller via a USB Cable . . . . . . . . . . . . . . . . . . . . . . . . 53
Connect the Controller to an EtherNet/IP Network. . . . . . . . . . . . . . . . 54
Connecting to Different EtherNet/IP Network Topologies. . . . . . 54
Chapter 3
Install the CompactLogix 5370 L3 Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Controller CompactLogix 5370 L3 Controller Parts . . . . . . . . . . . . . . . . . . . . . . . 59
Installation Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Install the Secure Digital Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Install the System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Assemble the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Install the Removable Terminal Block . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Wire the Terminal Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Wire Size and Terminal Screw Torque . . . . . . . . . . . . . . . . . . . . . . . . . 65
Mount the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
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 at Set the IP Address of a Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
CompactLogix 5370 Controller Use the BOOTP Server to Set the IP Address of the Controller . . 79
Use the DHCP Server to Set the IP Address of the Controller . . . . 86
Installation
Use RSLinx Software to Set the IP Address of the Controller . . . . . 87
Use the Studio 5000 Environment to Set the IP Address of the
Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Use the SD Card to Set the IP Address of the Controller. . . . . . . . . 93
Change the IP Address of a Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Change the Network IP Address with RSLinx Classic Software. . . 95
Change the Network IP Address with an SD Card . . . . . . . . . . . . . . 97
Load the Controller Firmware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Use the ControlFLASH Software to Load Firmware . . . . . . . . . . . 104
Use AutoFlash to Load Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Use the Secure Digital Card to Load Firmware . . . . . . . . . . . . . . . . . 111
Select the Operating Mode of the Controller . . . . . . . . . . . . . . . . . . . . . . 112
Chapter 5
CompactLogix 5370 Controllers CompactLogix 5370 Control System Components. . . . . . . . . . . . . . . . . 116
Overview Controller Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Support for Integrated Motion over an EtherNet/IP Network. . . 118
Electronic Keying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Example System Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
EtherNet/IP Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
DeviceNet Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Chapter 6
Communicate over Networks EtherNet/IP Network Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Available Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
EtherNet/IP Network Functionality on CompactLogix 5370
Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Nodes on an EtherNet/IP Network. . . . . . . . . . . . . . . . . . . . . . . . . . . 125
EtherNet/IP Network Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Socket Interface with CompactLogix 5370 Controllers . . . . . . . . . 133
Quality of Service (QoS) and I/O Module Connections . . . . . . . . 133
EtherNet/IP Network Connections . . . . . . . . . . . . . . . . . . . . . . . . . . 134
DeviceNet Network Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Available Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Compact I/O 1769-SDN DeviceNet Scanner. . . . . . . . . . . . . . . . . . 137
Power Supply Distance Rating. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Current Capacity in CompactLogix 5370 L3 Control Systems . . 142
Chapter 7
Use I/O Modules with CompactLogix Select I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
5370 L1 Controllers Connect Field Power to I/O Devices Connected to a CompactLogix
5730 L1 Control System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Embedded I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Local Expansion Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Distributed I/O Modules over an EtherNet/IP Network . . . . . . . 162
Validate I/O Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Set the Number of Local Expansion Modules . . . . . . . . . . . . . . . . . . 164
Empty Slots and Removal and Insertion Under Power Situations 165
Estimate Requested Packet Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Module Faults Related to RPI Estimates. . . . . . . . . . . . . . . . . . . . . . . 168
Calculate System Power Consumption . . . . . . . . . . . . . . . . . . . . . . . . 168
Physical Placement of I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Use the Event Task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Configure I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Common Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 175
I/O Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Configure Distributed I/O Modules on an EtherNet/IP Network . . 176
Monitor I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Bus Off Detection and Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Chapter 8
Use I/O Modules with CompactLogix Select I/O Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
5370 L2 Controllers Embedded I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Determine Embedded Module Update Time . . . . . . . . . . . . . . . . . . . . . . 198
Channel Update Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Embedded Analog I/O Modules Data Arrays . . . . . . . . . . . . . . . . . . . . . . 204
Input Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Output Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Configuration Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Local Expansion Modules - Optional . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Distributed I/O Modules over an EtherNet/IP Network. . . . . . . . 216
Distributed I/O Modules over a DeviceNet Network . . . . . . . . . . . 217
Validate I/O Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Estimate Requested Packet Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Module Fault Related to RPI Estimates . . . . . . . . . . . . . . . . . . . . . . . . 220
System Power Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Power Supply Distance Rating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Configure Local I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Configure Embedded I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Configure Local Expansion Modules . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Common Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 226
I/O Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Configure Distributed I/O Modules on an EtherNet/IP Network. . . 227
Configure Distributed I/O Modules on a DeviceNet Network . . . . . . 231
Monitor I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
End Cap Detection and Module Faults . . . . . . . . . . . . . . . . . . . . . . . . 235
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 . . . . . . . . . . . . . . . . . . . . . . . . 244
Calculate System Power Consumption . . . . . . . . . . . . . . . . . . . . . . . . 245
Physical Placement of I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Power Supply Distance Rating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Configure I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Common Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 254
I/O Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Configure Distributed I/O Modules on an EtherNet/IP Network. . . 255
Configure Distributed I/O Modules on a DeviceNet Network . . . . . . 258
Monitor I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
End Cap Detection and Module Faults . . . . . . . . . . . . . . . . . . . . . . . . 262
Chapter 10
Develop Applications Elements of a Control Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Task Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Scheduled and Unscheduled Programs . . . . . . . . . . . . . . . . . . . . . . . . 269
Routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Extended Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Access Extended Properties in Logic . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Programming Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Add-On Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Access the Module Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Create the Add-On Instruction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Monitoring Controller Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Monitoring I/O Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Determine if I/O Communication has Timed Out . . . . . . . . . . . . . 280
Determine if I/O Communication to a Specific I/O Module has
Timed Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Interrupt the Execution of Logic and Execute the Fault Handler 281
System Overhead Time Slice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Configure the System Overhead Time Slice. . . . . . . . . . . . . . . . . . . . 283
Sample Controller Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Chapter 11
Develop Integrated Motion over an Motion Axes Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
EtherNet/IP Network Application AXIS_VIRTUAL Axis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
AXIS_CIP_DRIVE Axis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Maximum Number of Position Loop-configured Drives . . . . . . . . . . . . 287
Position Loop-configured Drive Limits. . . . . . . . . . . . . . . . . . . . . . . . 287
Time Synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Configure Integrated Motion on the EtherNet/IP Network . . . . . . . . 289
Enable Time Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Add a Drive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Scalability in Applications Using Integrated Motion on EtherNet/IP
Networks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
1769-L30ERM, 1769-L33ERM, and 1769-L36ERM Controllers 293
1769-L18ERM-BB1B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
1769-L27ERM-QBFC1B Controller . . . . . . . . . . . . . . . . . . . . . . . . . 296
Chapter 12
Use a Secure Digital Card Store or Load a Project with the Secure Digital Card . . . . . . . . . . . . . . . 299
Store a Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Load a Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Appendix A
Troubleshoot the Module Use Logix Designer Application for Troubleshooting. . . . . . . . . . . . . . . 305
Fault Type Determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Use the CompactLogix 5370 Controllers Status Indicators . . . . . . . . . 308
Appendix B
Replacement Considerations Product Comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Power Supply Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Appendix C
Connect Power to the Series A L1 CompactLogix 5370 L1, Series A, Controller Power Connection. . . . 315
CompactLogix 5370 Controllers CompactLogix 5370 L1, Series A, Controller Field Power to I/O Devices
Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Appendix D
History of Changes Changes to the Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Index
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.
Additional Resources These resources contain information about related products from Rockwell
Automation.
Resource Description
CompactLogix Controllers Specifications Technical Data, Provides CompactLogix controller specifications for all CompactLogix controllers.
publication 1769-TD005
1769-SDN DeviceNet Scanner Module User Manual, publication 1769-UM009 Describes how to use the 1769-SDN to back up your CompactLogix 5370 L2 or L3 controller.
Compact High-speed Counter Module User Manual, publication 1769-UM006 Describes high-speed counter operation for standalone 1769-HSC when used with L2 and L3
Compact controllers as well as embedded high-speed counters in L2 embedded controllers.
Compact I/O DeviceNet Scanner Module Installation Instructions, Describes how to install the Compact I/O™ modules.
publication 1769-IN060
Compact I/O Expansion Power Supplies Installation Instructions, publication Describes how to wire the 1769 Compact I/O power supply.
1769-IN028
CompactLogix 5370 L1 Controllers Quick Start, publication IASIMP-QS024 Describes basic tasks to design, install and start a CompactLogix 5370 L1 control system.
CompactLogix 5370 L2 Controllers Quick Start, publication IASIMP-QS025 Describes basic tasks to design, install and start a CompactLogix 5370 L2 control system.
CompactLogix 5370 L3 Controllers Quick Start, publication IASIMP-QS023 Describes basic tasks to design, install and start a CompactLogix 5370 L3 control system.
Ethernet Design Considerations Reference Manual, publication ENET-RM002 Describes the following concepts that you must consider when designing a control system that
includes an EtherNet/IP network:
• EtherNet/IP overview
• Ethernet infrastructure
• EtherNet/IP protocol
EtherNet/IP Embedded Switch Technology Application Guide, Describes how to use a DLR network topology.
publication ENET-AP005
Execution Time and Memory Use for Logix5000 Controller Instructions Assists in estimating the memory use and execution time of programmed logic and in selecting
Reference Manual, publication 1756-RM087 among different programming options.
Integrated Motion on the EtherNet/IP Network Configuration and Startup User Describes how to configure an Integrated Motion over
Manual, publication MOTION-UM003 EtherNet/IP motion application and to start up that motion solution in a Logix5000 control system.
POINT I/O 24V dc Expansion Power Supply Installation Instructions, Describes the 1734-EP24DC expansion power supply.
publication 1734-IN058
POINT I/O Digital and Analog Modules and POINTBlock I/O Modules User Describes how to return a 1734 POINT I/O module to Autobaud.
Manual, publication 1734-UM001
POINT I/O Field Potential Distributor Modules Installation Instructions, Describes the 1734-FPD POINT I/O Field Power Distributor module.
publication 1734-IN059
Industrial Automation Wiring and Grounding Guidelines, publication 1770-4.1 Provides general guidelines for installing a Rockwell Automation industrial system.
Product Certifications website, http://www.ab.com Provides declarations of conformity, certificates, and other certification details.
Notes:
Topic Page
Before You Begin 16
Install the Secure Digital Card 19
Install the System 21
Connect to the Controller via a USB Cable 31
Connect the Controller to an EtherNet/IP Network 32
Before You Begin The CompactLogix™ 5370 L1, series B, controller redesign occurred to provide
an option to use one external power supply for system power and field side power.
There are differences between the CompactLogix 5370 L1, series A and B,
controllers, which are detailed throughout the sections of this manual.
• The embedded power supply for the series A L16ER, L18ER or L18ERM
controller is a 24V DC nominal, non-isolated power supply with an input
range of 10…28.8V DC. You wire the embedded power supply via a
removable connector.
• The embedded power supply for the series B L16ER, L18ER, L18ERM
and series A L19ER controller is a 24V DC nominal, isolated
power supply with an input range of 10…28.8V DC. You wire the
embedded power supply via a removable connector.
• Power for other components can be provided from the external power
supply that is used to provide power to the system for only series B L16ER,
L18ER, L18ERM Controllers, and series A L19ER Controllers.
IMPORTANT You must use the latest series and firmware revision for all 1734
POINT I/O™ modules in the local expansion slots to make sure that your
application operates as expected. Use of an older firmware revision
renders the entire 1734 bus inoperable.
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 cover 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 reinstall an SD card that has been removed from the
controller back into the controller or to install a new SD card into the controller.
We recommend that you leave the SD card in the controller, even when it is not
used. If the controller experiences a major non-recoverable fault, extended fault
information is saved to the card.
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
You can install the SD card in only one orientation. The beveled corner is
at the top.
If you feel resistance when inserting the SD card, pull it out and change the
orientation.
4. Gently press the card until it clicks into place.
We recommend that 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 297.
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 (Series B) L16 ER, L18ER, L18ERM
series B controllers, and series A L19ER
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.
Bumper Selection:
• For more information on Bumper Selection, see Rockwell
Automation® Knowledgebase article #591565. You can access the
article at: (Login required)
https://rockwellautomation.custhelp.com/
Minimum Spacing
Maintain spacing from enclosure walls, wireways, and adjacent equipment. Allow
50 mm (2 in.) of space on all sides, as shown. This spacing provides ventilation
and electrical isolation.
50 mm
Top (2 in.)
50 mm 50 mm
(2 in.) (2 in.)
Embedded Power
Controller with
End Cap
Side Side
Bottom 50 mm
(2 in.)
System Dimensions
130.00 mm
(5.11 in.)
144.00 mm
(5.67 in.)
This graphic shows the system dimensions with Expansion I/O modules
installed.
12.00 mm
(0.47 in.)
105 mm 100.00 mm
(4.13 in.) (3.94 in.)
130.00 mm
(5.11 in.)
144.00 mm
(5.67 in.)
2. Slide the controller into position on the DIN rail and push the locking
tabs in.
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 can result in equipment
damage or injury from electric shock.
If you are using local expansion modules, see Local Expansion Modules on
page 158 for more information on how to install them in a
CompactLogix 5370 L1 control system.
A removable terminal block (RTB) is supplied with your wiring base assembly. To
remove, pull up on the RTB handle. This allows the mounting base to be
removed and replaced as necessary without removing any of the wirings. To
reinsert the removable terminal block, proceed as follows:
1. Insert the end opposite the handle into the base unit. This end has a curved
section that engages with the wiring base.
2. Rotate the RTB into the wiring base until it locks itself in place.
3. If an I/O module is installed, snap the RTB handle into place on the
module.
tu ule
s
Sta od
M
D tus ork
Sta etw
N
E:
O
N
le
t p
pu ou
In oc
erm
Th
IT 34
17
2I
44012
WARNING: When you connect or disconnect the RTB with field-side power
applied, an electrical arc can occur. This can cause an explosion in hazardous
location installations.
Be sure that power is removed or the area is nonhazardous before proceeding.
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 that are connected to the embedded I/O modules of the
controller or local expansion modules. Power must be connected to the FP+
and FP- terminals to provide power to input or output devices that are
connected to the embedded I/O modules of the controller or local expansion
modules.
The external power supply can be used to power both the VDC+/- and FP+/-
terminals on the series B L1 controller, see page 144.
For more information on how to provide power to input or output devices that
are connected to the embedded I/O modules of the controller and local
expansion modules, see page 144.
• Use a power source that most effectively meets your application needs.
That is, calculate The power requirements for your application 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.
• Not all Class 2/SELV-listed power supplies are certified for use in all
applications, for example, use in nonhazardous and hazardous
environments.
• Only for example purposes, this section describes how to use a 1606-
XLE120E, NEC Class 2 switched-mode power supply. The exact steps for
other external power supplies can vary from the steps that are described
here.
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 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.
5. Connect the wire that is 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.
6. Connect the wire that is 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.
The following graphic shows an external 24V DC power source that is connected
to a CompactLogix 5370 L1 controller.
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.
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.
Bottom of Controller
Port 1 - Front
Port 2 - Back
IMPORTANT This example shows how to connect the controller to the network through one
port. Depending on the network topology of your application, you can connect
both ports of the controller to the EtherNet/IP network.
For more information on EtherNet/IP network topologies, see page 127.
Topic Page
Before You Begin 36
Install the Secure Digital Card 38
Install the System 40
Connect to the Controller via a USB Cable 53
Connect the Controller to an EtherNet/IP Network 54
Before You Begin Consider the following before installing a CompactLogix™ 5370 L2 controller:
Embedded Power
Supply Terminals
• 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.
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 reinstall an SD card that has been removed from the
controller back into the controller or to install a new SD card into the controller.
We recommend that you leave the SD card in the controller, even when it is not
used. If the controller experiences a Major Non-recoverable Fault, extended fault
information is saved to the card.
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
You can install the SD card in one orientation only. The beveled corner is
at the bottom.
If you feel resistance when inserting the SD card, pull it out and change the
orientation.
We recommend that 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 297.
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 spacing 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
118.00 mm
(4.65 in.)
2.8 mm 115.00 mm
(0.12 in.) (4.53 in.)
This graphic shows the system dimensions for the 1769-L24ER-QB1B controller
with expansion modules installed.
118.00 mm 126.6 mm
(4.65 in.) (4.98 in.)
118.00 mm
(4.65 in.)
2.8 mm 140.00 mm
(0.12 in.) (5.51 in.)
126.6 mm
118.00 mm (4.98 in.)
(4.65 in.)
18.00 mm
(0.71 in.)
118.00 mm
(4.65 in.)
2.8 mm 140.00 mm
(0.12 in.) (5.51 in.)
35.00 mm
(1.38 in.) 25.00 mm
(0.98 in.)
105 mm 140.00 mm
(4.13 in.) (5.51 in.)
118.00 mm 126.6 mm
(4.65 in.) (4.98 in.)
18.00 mm
(0.71 in.)
Use two M4 or #8 pan head 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.
TIP If you are mounting more modules, mount only the last one of this group
and put the others aside. This reduces remounting time when you are
drilling and tapping the next group of modules.
7. Repeat steps 1…6 for any remaining modules.
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.
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 can be
installed onto the controller.
7. Push the end cap locking mechanism to the right to lock it onto
the controller.
If you are using local expansion modules, see Local Expansion Modules -
Optional on page 214 for more information on how to install them in a
CompactLogix 5370 L2 control system.
To remove the RTB, loosen the upper and lower retaining screws. The terminal
block backs away from the module as you remove the screws. When replacing the
terminal block, torque the retaining screws to 0.46 N•m (4.1 lb•in).
3 1
Item Description
1 Wiring the finger-safe cover
2 Lower retaining screws
3 Upper retaining screws
TIP The retaining screws are non-captive. You can use a ring lug [maximum 6.35
mm (0.25 in.) o.d. with a 3.53 mm (0.139 in.) minimum i.d. (M3.5)] with the
module.
3. Tighten the retaining screw making sure the pressure plate secures the wire.
Recommended torque when tightening retaining screws is 0.68 N•m
(6 lb•in).
TIP If you need to remove the finger-safe cover, insert a screwdriver into one of the
square wiring holes and gently pry the cover off. If you wire the terminal block
with the finger-safe cover removed, you cannot put it back on the terminal
block because of wires in the way.
Each terminal accepts one or two wires with the following restrictions.
Wire Type Wire Size Terminal Screw Torque Retaining Screw Torque
Solid Cu-90 °C (194 °F) #14…#22 AWG 0.68 N•m (6 lb•in) 0.46 N•m (4.1 lb•in)
Stranded Cu-90 °C (194 °F) #16…#22 AWG 0.68 N•m (6 lb•in) 0.46 N•m (4.1 lb•in)
• This section describes how to connect power only to the embedded power
supply of the CompactLogix 5370 L2 controller.
• Not all Class 2 or SELV-listed power supplies are certified for use in all
applications, for example, use in 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.
Use only the FG terminal when connecting a field device to the controller.
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 50 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 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 connect
to the +24VDC terminal on the controller.
5. Connect the wire from the 24VDC+ terminal on the external 24V DC
power source to the +24VDC terminal on the controller.
6. Strip 8 mm (0.31 in) insulation from the end of the wire that you 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.
IMPORTANT If your application requires a power control device, for example, a switch or
relay, between the external power supply and the embedded power supply of
the CompactLogix 5370 L2 controller to control when the controller is powered,
you must install the power control device at the +24V DC terminal on the
controller.
If you install the power control device at the COM terminal, the
CompactLogix 5370 L2 controller cannot power up or power down properly.
The following graphic shows an external 24V DC power source that is connected
to a CompactLogix 5370 L2 controller.
IMPORTANT When you remove power from the CompactLogix 5370 L2 controller to cycle
power, the OK status indicator of the controller remains lit briefly as the
controller passes through its shutdown sequence.
Do not reapply power from the external power supply to the embedded power
supply of the CompactLogix 5370 L2 controller until after the OK status
indicator of the controller 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.
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 can result.
Bottom of Controller
Port 1 - Front
Port 2 - Back
IMPORTANT This example shows how to connect the controller to the network through one
port. Depending on the network topology of your application, you can connect
both ports of the controller to the EtherNet/IP network.
For more information on EtherNet/IP network topologies, see page 127.
Topic Page
Before You Begin 58
Install the Secure Digital Card 60
Install the System 62
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 that the controller must be within four slots of the power supply.
You can install as many as three modules between the power supply and
the controller, as shown in the following graphic.
• 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. You can terminate a bank at the left or right end of the
bank dependent upon your system design.
A 1769-ECx end cap is required to terminate the end of the last bank in
the control system.
For graphics of CompactLogix 5370 L3 control systems that use one bank
or multiple banks, see Mount the System on page 65.
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 reinstall an SD card that has been removed from the
controller back into the controller or to install a new SD card into the controller.
We recommend that you leave the SD card in the controller, even when it is not
used. If the controller experiences a Major Non-recoverable Fault, extended fault
information is saved to the card.
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
You can install the SD card in only one orientation. The beveled corner is
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.
We recommend that 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 297.
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.
3. Use the upper and lower tongue-and-groove slots to secure the controller
and power supply together.
Tongue-and-groove Slots
4. Move the power supply back along the tongue-and-groove slots until the
bus connectors align with each other.
5. Use your fingers or a small screwdriver to push the bus lever of the power
supply back slightly to clear the positioning tab.
6. Move the bus lever of the power supply fully to the left until it clicks;
making sure that it locks.
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 L3 controller system either at the end of the
controller or at the end of any local expansion modules that can be
installed onto the controller.
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.
To remove the terminal block, loosen the upper and lower retaining screws. The
terminal block backs away from the module as you remove the screws. When
replacing the terminal block, torque the retaining screws to 0.46 N•m (4.1 lb•in).
.
3 1
Item Description
1 Wiring the finger-safe terminal block
2 Lower retaining screws
3 Upper retaining screws
When wiring the terminal block, keep the finger-safe cover in place.
TIP The terminal screws are non-captive. You can use a ring lug [maximum 6.35
mm (0.25 in.) o.d. with a 3.53 mm (0.139 in.) minimum i.d. (M3.5)] with the
module.
3. Tighten the terminal screw making sure the pressure plate secures the wire.
Recommended torque when tightening terminal screws is 0.68 N•m
(6 lb•in).
TIP If you need to remove the finger-safe cover, insert a screwdriver into one of the
square wiring holes and gently pry the cover off. If you wire the terminal block
with the finger-safe cover removed, you cannot put it back on the terminal
block because of wires in the way.
Each terminal accepts one or two wires with the following restrictions.
Wire Type Wire Size Terminal Screw Torque Retaining Screw Torque
Solid Cu-90 °C (194 °F) #14…#22 AWG 0.68 N•m (6 lb•in) 0.46 N•m (4.1 lb•in)
Stranded Cu-90 °C (194 °F) #16…#22 AWG 0.68 N•m (6 lb•in) 0.46 N•m (4.1 lb•in)
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
Bank 1
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 spacing 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
132 mm
(5.20 in.)
118 mm
(4.65 in.)
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.)
105 mm
(4.13 in.)
CompactLogix 5370 L3 controllers and the Compact I/O modules have power
supply distance ratings. Power supply distance ratings determine how many slots
in a bank that a device can be from the power supply.
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.
For more information, see the Industrial Automation Wiring and Grounding
Guidelines, publication 1770-4.1.
Use two M4 or #8 pan head screws to mount the controller. Mounting screws are
required on many modules. 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.
TIP If you are mounting more modules, mount only the last one of this group
and put the others aside. This reduces remounting time when you are
drilling and tapping the next group of modules.
7. Repeat steps 1…6 for any remaining modules.
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 DIN rail latches of
the controller.
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.
ATTENTION: The USB port is intended only for temporary local programming
purposes and not intended for permanent connection.
The USB cable is not to exceed 3.0 m (9.84 ft) and must not contain hubs.
Plug the USB cable into the CompactLogix 5370 L3 controller as shown.
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 or damage to the port can result.
Bottom of Controller
Port 1 - Front
Port 2 - Rear
IMPORTANT This example shows how to connect the controller to the network through one
port. Depending on the Ethernet network topology of your application, you can
connect both ports of the controller to the EtherNet/IP network.
For more information on EtherNet/IP network topologies, see page 127.
Topic Page
Set the IP Address of a Controller 77
Change the IP Address of a Controller 94
Load the Controller Firmware 98
Select the Operating Mode of the Controller 112
To complete the tasks that are described in this chapter, you must have the
software that is 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
• Set the IP address for a controller that does not have one assigned.
Set the IP Address of a You must set the IP address of a CompactLogix 5370 controller when the
controller powers up for the first time, that is, when commissioning the controller
Controller for the first time. You are not required to set an IP address each time that power is
cycled to the controller.
You can use these tools to set the IP address of a CompactLogix 5370 controller:
• Bootstrap Protocol (BOOTP) server
• Dynamic Host Configuration Protocol (DHCP) server
• RSLinx Classic software
• Studio 5000 Logix Designer® application
• SD card
IMPORTANT Each tool has connection requirements to set the IP address of the controller
via that tool. For example, your computer must be connected to the controller
via a USB cable to set the initial IP address of the controller with RSLinx Classic
software or the application.
Figure 2 - Set the IP address on a power cycle during initial installation or after operation has
begun
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 IP address of the controller:
IMPORTANT Before you start the BOOTP/DHCP utility, make sure that you have the hardware (MAC) address of the controller. 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
Complete these steps to set the IP address of the controller with the
BOOTP/DHCP server.
IMPORTANT To use the BOOTP server, your computer and the controller must be connected
to the same EtherNet/IP network.
The Request History panel appears with the hardware addresses of all
devices that issue BOOTP requests. This process can take some time to
complete.
5. Select the appropriate module.
8. Click OK.
9. To 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.
1. Make sure that a USB cable is connected to your computer and the
controller.
2. Start RSLinx Classic software.
8. Click OK.
4. On the Controller Properties dialog box, click the Internet Protocol tab.
5. Click Manually configure IP settings.
6. Click OK.
7. When prompted to confirm the IP address setting, click Yes.
You can use RSLinx software to set the IP address of the CompactLogix 5370
controller.
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 software, you must be
connected to your controller via the USB port.
Complete these steps to set the IP address of the controller with RSLinx
software.
IMPORTANT These steps show a 1769-L36ERM controller. The same steps also apply to all
CompactLogix 5370 controllers with slight variations in screens.
1. Make sure that a USB cable is connected to your computer and the
controller.
2. Start RSLinx software.
The RSWho dialog box appears and includes the USB driver.
4. Right-click the EtherNet/IP module and choose Module Configuration.
IMPORTANT If you click Dynamic, on a power cycle, the controller clears the
current IP configuration and starts to send BOOTP requests.
As with all configuration changes, if desired, make sure that you are using the SD
card in a way that does 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 297.
IMPORTANT These steps show a 1769-L18ERMBB1B controller. The same steps also apply to
all 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 Remote Program or Program mode.
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 To set the IP address from an SD card, software is not required during the
power-up process. However, you must have previously saved the project to the
SD card.
The IP address of the CompactLogix 5370 controller is automatically configured
at power-up as long as you have configured an IP address, stored the program
onto a controller, and set the SD card to the Load Image parameter set to On
Power Up.
The option to set the IP address of a CompactLogix 5370 controller via an SD
card at power-up is only one part of the process to load an entire project to the
controller from the SD card.
Use this option carefully. For example, the SD card can 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 that is 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 297.
Change the IP Address of a You can change the IP address of a CompactLogix 5370 controller after system
operation has begun. In this case, the controller has an IP address that is assigned
Controller to it, but you must change that IP address.
IMPORTANT You cannot use any of these tools to change a the IP address of a controller:
• Bootstrap Protocol (BOOTP) server
• Dynamic Host Configuration Protocol (DHCP) server
Consider these factors when you determine how to change the IP address of a
controller:
• Network isolation from, or integration into, the plant/enterprise network
• Network size - For large, isolated networks, it can be more convenient and
safer to use a BOOTP/DHCP server rather than
the Studio 5000 environment or RSLinx Classic software. A BOOTP/
DHCP server limits the possibility of duplicate IP address assignment.
However, you can only use the BOOTP/DHCP server to set the IP
address of the controller and not to change it. If you decide to change the
IP address of the controller and want to use a BOOTP/DHCP server to
limit the possibility of duplicate IP address assignment, you must first clear
the IP address.
After clearing the IP address, use the steps that are described at Use the
BOOTP Server to Set the IP Address of the Controller on page 79 or Use
the DHCP Server to Set the IP Address of the Controller on page 86 to
set the IP address of the controller.
• Company policies and procedures that deal with plant floor network
installation and maintenance
IMPORTANT The steps in Use RSLinx Software to Set the IP Address of the Controller on
page 87 describe how to assign an IP address for a CompactLogix 5370
controller that does not have an IP address.
The steps in this section describe how to change the IP address on a
CompactLogix 5370 controller that has an IP address that is assigned to it.
The graphics in this section show how to change the IP address for a
1769-L36ERM controller. The same steps also apply to all 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 starts to send BOOTP or DHCP
requests, depending on the controller configuration.
5. Click OK.
IMPORTANT The steps in Use the Studio 5000 Environment to Set the IP Address of the
Controller on page 89 describe how to assign an IP address for a
CompactLogix 5370 controller that does not have an IP address.
The steps in this section describe how to change the IP address on a
CompactLogix 5370 controller that has an IP address that is assigned to it.
You can change the IP address of a CompactLogix 5370 controller 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 also
apply to all other CompactLogix 5370 controllers with slight variations in
screens.
You can 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 removes the need for software to complete this task.
IMPORTANT To set the IP address from an SD card, software is not required 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 that is stored on the SD card includes another IP address for
the CompactLogix 5370 controller than the IP address currently in use on
the physical controller that houses the SD card.
• The project that is 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 297.
Load the Controller Firmware You must download the current firmware before you can use the
CompactLogix 5370 controller.
IMPORTANT The controller firmware revision that is loaded via the ControlFLASH software
or the AutoFlash option can be overwritten after future controller power cycles
if the conditions described in Use the Secure Digital Card to Load Firmware on
page 111 exist.
The firmware is available with the application or you can download it from the
support website. Go to http://www.rockwellautomation.com/support.
6. Click the correct product and select the desired firmware revision.
You can use the ControlFLASH software to load firmware through a USB or
EtherNet/IP network connection. We recommend the following when you load
firmware via the ControlFLASH software:
• 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 also apply to all
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
receive the following message:
• The target device is not in the proper mode to accept an update in
ControlFLASH.
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 click Yes.
Before the firmware upgrade begins, you see the following dialog box. Take
the required 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 software, click Cancel and click Yes.
After the controller firmware upgrade process is complete, the controller can
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 only the embedded I/O module, not the
local expansion modules.
If you must update the firmware revision on any 1734 POINT I/O™
modules that are 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 also apply to all
CompactLogix 5370 controllers with slight variations in screens.
1. Make sure that the 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 can also choose to click Update Firmware to complete this process. If
you do so, skip to step 6.
A dialog box appears to indicate that the project revision and controller
firmware revision are different.
5. Click Update Firmware.
6. Use the checkbox and pull-down menu to choose your controller and
firmware revision.
7. Click Update.
Before the firmware upgrade begins, you can be warned about your
controller missing its SD card. Take the required action, typically click
OK.
IMPORTANT An installed SD card automatically updates the firmware of the controller if the
SD card is configured with the Load Image parameter set to On Power Up. This
feature is and cannot be disabled.
• You must have saved the project to the SD card before the power cycle.
• The firmware revision in the project that is stored on the SD card differs
from the firmware revision on the CompactLogix 5370 controller.
For more information on using the SD card, see Chapter 12, Use a Secure Digital
Card on page 297.
Select the Operating Mode of CompactLogix 5370 controllers have slightly different front designs and mode
switch placements.
the Controller
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.
Use the mode switch on the controller to set the operating mode of the
CompactLogix 5370 controller.
Topic Page
CompactLogix 5370 Control System Components 116
Controller Functionality 117
Electronic Keying 119
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 that is documented in this publication
Power supply External power supply that is connected to the External power supply that is connected to the One of the following 1769 Compact I/O™
embedded 24V DC nominal input of the embedded 24V DC input of the controller, power supplies:
controller, nonisolated power supply. The isolated power supply • 1769-PA2
power supply 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 only for programming and • USB connection only for programming and firmware upgrades
firmware upgrades
Software • One of the following:
– RSLogix™ 5000 software, version 20.xx.xx, - For CompactLogix 5370 controllers that are using firmware revision 20.xxx
– Logix Designer application, version 21.00.00 or later, - For CompactLogix 5370 controllers that are 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
• Only 1769-L24ER-QBFC1B and
• 16 embedded 24V DC digital output points - 1769-L27ERM-QBFC1B controllers 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 clears the user program from the internal memory of the controller.
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)
1769-L18ER-BB1B NA
512 KB As many as eight
1769-L18ERM-BB1B 1734 POINT I/O
modules(2)
1769-L19ER-BB1B 1 MB
1769-L24ER-QB1B Support the
following 768 KB As many as four
1769-L24ER-QBFC1B topologies: See footnote(1) Compact I/O
Yes - Eliminating modules
1769-L27ERM-QBFC1B 32 1000 the need for a • Device-level 1 MB
battery ring (DLR)
1769-L30ER
• Linear As many as eight
1769-L30ER-NSE • Traditional star 1 MB Compact I/O
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 that
are 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 regarding using Compact I/O modules in a CompactLogix 5370 L2 control system, see page 125 and page 221.
(2) IMPORTANT: You can use up to the maximum number of 1734 POINT I/O modules with the CompactLogix 5370 L1 controllers that are 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 must 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.
IMPORTANT The Real Time Clock (RTC) does not retain its time and date when the power is
off.
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 can include other devices that also require a wait time before removing
them. See the documentation of those products for more information.
Electronic Keying Electronic Keying reduces the possibility that you use the wrong device in a
control system. It compares the device that is defined in your project to the
installed device. If keying fails, a fault occurs. These attributes are compared.
Attribute Description
Vendor The device manufacturer.
Device Type The general type of the product, for example, digital I/O module.
Product Code The specific type of the product. The Product Code maps to a catalog number.
Major Revision A number that represents the functional capabilities of a device.
Minor Revision A number that represents behavior changes in the device.
Carefully consider the implications of each keying option when selecting one.
IMPORTANT Changing Electronic Keying parameters online interrupts connections to the device and
any devices that are connected through the device. Connections from other controllers
can also be broken.
If an I/O connection to a device is interrupted, the result can be a loss of data.
More Information
For more detailed information on Electronic Keying, see Electronic Keying in
Logix5000™ Control Systems Application Technique, publication LOGIX-
AT001.
EtherNet/IP Network
IMPORTANT Figure 3, Figure 4, and Figure 5 show CompactLogix 5370 controllers that are
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 123.
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 Application on page 285.
Kinetix 5500
PowerFlex® 525
PanelView Plus 7
Kinetix 5500
1734-AENTR POINT I/O 1794-AENTR FLEX I/O
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.
Topic Page
EtherNet/IP Network Communication 123
DeviceNet Network Communication 135
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 that is required to support
information data exchange and control applications.
For more information on socket interface transactions, see Socket Interface with
CompactLogix 5370 Controllers on page 133.
Available Software
Use the software that is listed in the following table with a CompactLogix 5370
controller on an EtherNet/IP network.
Software Required Version Functions Required
RSLogix™ 5000 Version 20 - For CompactLogix 5370 • Configure the CompactLogix project.
controllers that are using firmware revision • Define EtherNet/IP communication.
20. • Change IP address for devices on network, Yes. Studio 5000® environment,
including the CompactLogix 5370 version 28 or later - For 1769-L19ER-
Studio 5000 Version 21 or later - For CompactLogix 5370 controller.
environment controllers that are using firmware revision 21 BB1B controllers
or later. (1)
RSLinx® Classic 2.59.00 or later • Assign or change IP addresses to devices
CompactLogix 5370 L2 controllers require on an EtherNet/IP network.
RSLinx Classic software, version 2.59.01 or • Configure communication devices.
later. • Provide diagnostics.
The1769-L19ER-BB1B controller requires • Establish communication between
RSLinx Classic software, version 3.74.00 devices.
BOOTP/DHCP Most current version is installed with Assign IP addresses to devices on an EtherNet/ No
utility RSLinx Classic software installation. IP network.
(1) If you are using the L19 you must have at a minimum, Studio 5000, version 28. There is no version of RSLogix 5000 (version 20) for support of the L19.
IMPORTANT While CompactLogix 5370 controllers offer the option of using Ethernet node
count to effectively 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/rockwellautomation/products-
technologies/integrated-architecture/tools/overview.page#/tab3.
The EtherNet/IP Capacity Tool helps you in the initial layout of your
EtherNet/IP network.
• Ethernet Design Considerations Reference Manual, publication ENET-RM002.
Any devices that you add directly to the local Ethernet I/O configuration are
counted toward the node limitation of the controller. 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 that are 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-EN2DNR, Ethernet-to-DeviceNet
linking device
• Third-party devices that are directly 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
• HMIs that are not added to the I/O configuration section, for example,
PanelView Plus terminals
• MSG instructions
• Devices the CompactLogix 5370 controllers use a socket interface to
communicate with.
For example, the following devices require communication via a socket
interface:
– Modbus TCP/IP device
– Barcode scanners
IMPORTANT The topology graphics that are shown in this section are examples of
applications that use only DLR network topologies.
We recommend that you exercise caution if you consider designing an
application that includes the connection of 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.
Kinetix 5500
PowerFlex 525
PanelView Plus 7
Kinetix 5500
1734-AENTR POINT I/O 1794-AENTR FLEX I/O
IMPORTANT Keep the following in mind when using sockets with CompactLogix 5370 controllers:
• A significant difference between CompactLogix 5370 controllers and other Logix5000 controllers
is the communication path. CompactLogix 5370 controllers do not require a separate EtherNet/IP
network communication module, for example, a 1756-EN2T module. In the case of the
CompactLogix 5370 controllers, the MSG is sent to the controller itself by using the path ‘1,0’.
• All CompactLogix 5370 controllers must use unconnected MSG instructions for socket servers.
When you configure a message for a CompactLogix 5370 controller, make sure the Connected
checkbox on the Message Configuration dialog box is cleared.
Some EtherNet/IP devices do not support QoS technology unless the firmware
of the device 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 The DeviceNet network uses the Common Industrial Protocol (CIP) to provide
the control, configuration, and data collection capabilities for industrial devices.
IMPORTANT This section applies to applications using only CompactLogix 5370 L2 and L3
controllers.
CompactLogix 5370 L1 controllers do not operate on DeviceNet networks.
Available Software
The software applications that are 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 - For CompactLogix 5370 controllers using firmware Configure the CompactLogix project
revision 20.
Studio 5000 environment 21 or later - For CompactLogix 5370 controllers using
firmware revision 21 or later.
Studio 5000 environment, version 28 or later - For 1769-
L19ER-BB1B controllers.
RSLinx Classic 2.59.00 or later(1), (2), (3) • Configure communication devices
• Provide diagnostics
• Establish communication between devices
RSNetWorx™ for DeviceNet One of the following: • Configure DeviceNet devices
• 11.00.00 or later if used with RSLogix 5000 software, • Define the scanlist for the DeviceNet network
version 20.xx.xx
• 21.00.00 or later if used with the Studio 5000
environment, 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 the Studio 5000 environment, version 21.00.00 or later.
(3) RSLinx version 3.74.00 is recommended for use with the 1769-L19ER-BB1B controller.
Power supply distance rating is the number of slots a 1769-SDN scanner can be
installed away from the power supply. The 1769-SDN scanner 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 and the
power supply.
Additionally, the controller has embedded I/O modules that disallow installation
of the 1769-SDN scanner directly to the right of the embedded power supply.
CompactLogix 5370 L2 control systems have one or two embedded I/O
modules, described as follows:
• 1769-L24ER-QB1B controller - One embedded I/O module
• 1769-L24ER-QBFC1B and 1769-L27ERM-QBFC1B controllers - Two
embedded I/O modules
While the embedded I/O modules are not considered local expansion modules,
you must still include each embedded I/O module in the module slot count when
determining where to install the 1769-SDN scanner as a local expansion module.
The farthest local expansion module slot where you can install the 1769-SDN
scanner in a CompactLogix 5370 L2 control system is module slot number two
or three as determined by the controller catalog number that is used in the
control system.
Table 6 describes the farthest local expansion module slot where you can install a
1769-SDN scanner and meet its power supply distance rating requirement.
Three modules between the power supply and the 1769-SDN scanner.
With this controller catalog number, you can only install up to two local expansion modules
between the controller and the 1769-SDN scanner.
Three modules between the power supply and the 1769-SDN scanner.
With this controller catalog number, you can only install one local expansion modules
between the controller and the 1769-SDN scanner.
IMPORTANT When counting I/O modules to determine the 1769-SDN scanner 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 appearance in the application of the module.
The physical appearance is shown in the previous graphic. The second module
is two rows of termination points below one 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 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 in the following graphic.
1769-SDN scanner 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 scanners that are installed to the left of the
power supply in the local bank, are in a module slot that meets the power supply
distance rating requirements of the module.
CompactLogix 5370 L3 control systems also support the use of extra banks for
the local expansion modules of the system. Each 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 with no more three
Compact I/O modules between the scanner and the power, regardless of whether
the modules are installed to the left or right of the power supply.
In a local or extra bank, the modules that are 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 5V DC and 0.4A at 24V DC. Because a
For more information on 1769 Compact I/O power supply maximum current
capacity and calculations you can use to design the modules that are used in local
or extra banks, see Calculate System Power Consumption on page 245.
Topic Page
Select I/O Modules 143
Validate I/O Layout 163
Use the Event Task 170
Configure I/O 174
Configure Distributed I/O Modules on an EtherNet/IP Network 176
Configure Distributed I/O Modules on an EtherNet/IP Network 176
Monitor I/O Modules 179
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
IMPORTANT You must connect a separate external power source to the FP+ and FP-
terminals on the removable connector on the controller to power the field-side
circuitry of the embedded I/O modules and the local expansion modules for
only series A L1 controllers. See Appendix C for further information.
Power connections to the FP+ and FP- terminals provides power to input and
output devices that are connected to the embedded I/O modules or local
expansion modules of the controller. For example, input or output devices, such
as a barcode scanner.
The embedded I/O of the controller and the field-side power of the local
expansion modules is 24V DC nominally with an input range of 10…28.8V DC.
• The external 24V DC power source that is connected to the FP+ and FP-
terminals must be separate from the power source that is dedicated to
power the controller via the VDC+ and VDC- terminals for only series A
controllers (see Appendix C).
• 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 the power requirements of your application 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.
IMPORTANT Do not use the following steps to connect power to the CompactLogix 5370
series A L16ER, L18ER, and L18 ERM controllers controller. See Appendix C for
steps to connect power to the CompactLogix 5370 series A L16ER, L18ER, and
L18 ERM controllers controller. The steps in Appendix C provide an optional way
to connect power to a series B L1 controller.
1. Verify that the separate external 24V DC power source that powers the
CompactLogix 5370 L1 controller is not powered.
2. Connect wires to the + and - 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. Connect the wire that is connected to the + terminal on the external 24V
DC power source to the FP+ terminal, that is, the fourth terminal from
the top, on the removable connector.
5. Connect the wire that is connected to the - terminal on the external 24V
DC power source to the FP- terminal, that is the fifth terminal from the
top, on the removable connector.
The following graphic shows separate external 24V DC power supply that is
connected to the VDC+/VDC- and FP+/FP- terminals on the removable
connector, respectively.
Consider the following when you connect input or output devices to the
embedded I/O modules of your CompactLogix 5370 L1 controller:
• You must connect an external 24V DC power source to the FP+ and FP-
terminals on the removable connector on the controller to power input
and output devices that are connected to the embedded I/O modules on
the controller:
• The available RPI range of the I/O points 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 applied.
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 that are needed in your
application.
Complete these steps to remove and replace and I/O module connector.
3. Pull the connector out from the I/O module to remove it.
4. Disconnect any wires from the connector.
5. Connect any wires to the replacement connector.
6. Push the replacement connector back into the I/O module.
7. Secure the connector to the I/O module with the small screwdriver.
This method is required if you must continue reading data from the input
devices when the embedded output terminals are disabled, for example,
when the use of a Master Control Relay (MCR) disrupts output power.
Figure 19 and Figure 20 show examples of how to power 2-wire and 3-wire input
devices in your application.
IMPORTANT When using Figure 19 and Figure 20, use the following guidelines:
• With this wiring configuration, you can monitor the input devices even if
field power is interrupted, for example, by the MCR. The FP- connection
must be maintained as a reference for inputs to function.
• With this wiring configuration, the controller does not help protect field-
side devices from overcurrent draw conditions.
• Design your application so that power consumption does not exceed the
power supply ratings.
• The following figure is a wiring example that complies with the National
Electrical Code (NEC) standard for isolation between system and field
power.
• The FP+ terminal on the removable connector is the voltage connection.
• The FP- terminal on the removable connector is the common connection.
• The MCR must be closed for the removable connector to provide power to
the embedded I/O module.
• Install a user-replaceable fuse with overcurrent protection of 4…6 A @
52.5…68.25 A2t in line between the incoming power and the FP+
terminal.
For series A L1 controllers only, you must use a separate, dedicated Class 2
power supply for the CompactLogix 5370 L1 controller and a separate power
supply for the embedded I/O module (see Appendix C).
Figure 19 - CompactLogix 5370 L16ER, L18ER, and L18ERM Controllers with Input Devices
Powered by External Power Supplies (Series A [Alternate Series B])
Power
Supply 1
MCR
Figure 20 - CompactLogix 5370 L1 Controllers with Input Devices Powered by External Power
Supplies (Series B)
MCR
Figure 21 and Figure 22 shows examples of how to power 2-wire and 3-wire input
devices in your application with connections to a V terminal.
IMPORTANT When using Figure 21 and Figure 22, use the following guidelines:
• With this wiring configuration, the input devices lose power if the
removable connector does not power the embedded I/O modules.
• With this wiring configuration, the controller does not help protect field-
side devices from overcurrent draw conditions.
• Design your application so that power consumption does not exceed the
power supply ratings.
• The following figure is a wiring example that complies with the National
Electrical Code (NEC) standard for isolation between system and field
power.
• The FP+ terminal on the removable connector is the Voltage connection.
• The FP- terminal on the removable connector is the Common connection.
• The MCR must be closed for the removable connector to provide power to
the embedded I/O module.
• Install a user-replaceable fuse with overcurrent protection of 4…6 A in
line between the incoming power and the FP+ terminal.
For series A L1 controllers only, you must use a separate, dedicated Class 2
power supply for the CompactLogix 5370 L1 controller and a separate power
supply for the embedded I/O module (see Appendix C).
Figure 21 - CompactLogix 5370 Series B L16ER, L18ER, L18ERM and Series A L19 Controllers with
Input Devices Powered by a V Terminal on Embedded I/O Module (Series A [Alternate Series B])
Power
Supply 1
MCR
MCR
Power
Supply
IMPORTANT Do not exceed the per point output current rating or total output module
current rating.
Figure 23 - CompactLogix 5370 L1 Controllers Embedded Digital Output Point Wiring Diagram
Load
Load
Load
Load
Load
Load
Load
Load
IMPORTANT Do not exceed the per point output current rating or total output module
current rating.
Figure 24 - CompactLogix 5370 L1 Controllers Embedded Digital Output Point Wiring Diagram
Load
Load
Load
Load
Load
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 that are listed in Table 7, 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 field power current of 3 A.
IMPORTANT Do not put more than three of the 1734-IT2I or 1734-IR2 modules on
the POINT I/O bus that draws power from the same power source. This
includes power sources such as from communication adapters or the
1734-EPAC or 1734-EP24DC expansion power supply modules. The
inrush current exceeds the current limit of the DC to DC converter in the
power source.
Based on the configuration of your application, you can use one of the
following devices to make more POINTBus backplane current or field
power current available:
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 to 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 changes only 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 removable connector on the controller to provide power
to input and output devices that are connected to the local expansion
modules.
For more information on how to connect a power source to the FP+ and
FP- terminals, see page 144.
• We recommend that you make sure all 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 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 transmitted in a CompactLogix 5370 L1
control system. For more information, see Estimate Requested
Packet Interval on page 166.
If you must 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 project of the controller must match
the number of local expansion modules that are installed in the system for
the controller to establish connections to the local expansion modules.
IMPORTANT Field power is required for the 1734-232ASC module. The module
cannot receive adequate power without the application of field power.
The following graphic shows a CompactLogix 5370 L1 control system that uses
all three I/O module options.
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.
• 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 replace
a 1734 POINT I/O module in a CompactLogix 5370 control system.
• After you cycle power, the controller only enables I/O connections if the
number of local expansion modules present on POINTBus matches the
value that is 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 Studio
5000® environment 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 configuration parameters for a system determine the impact on actual RPI
rates. These configuration factors can affect the effective scan frequency for any
individual module:
• Other 1734 POINT I/O module RPI rate settings
• Number of other 1734 POINT I/O modules in the system
• Types of other 1734 POINT I/O modules in the system
• Application user task priorities
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
that are 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 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 RPI values of 1734 POINT I/O modules
to the values listed previously. 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 less frequent data scans.
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 can experience minor faults that are
described in the following table.
In some circumstances, you can configure a system that requires more current
than the embedded power supply of the system 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 that 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.
Before you physically install the I/O modules, you must assemble, mount, and
ground the system as described in Chapter 1, Install the CompactLogix 5370 L1
Controller on page 13.
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 embedded input points of the
controller. 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 stops 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 succeeds.
You can configure multiple embedded input points to trigger an Event task.
However, we recommend that 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 one of these events occurs:
• An event occurs on one point on an input module.
• A trigger event does not occur in a 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 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 that is 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 an 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 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 8.
Table 8 - 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 affect data transmission between the controller and the I/O module. The parameters include the
following:
• Series - Hardware series of the module.
• Revision - Major and minor firmware revision levels that are used on the module.
• Electronic Keying - See LOGIX-AT001 for Electronic Keying information.
• Connection - Type of connection between the controller that writes the configuration and the I/O module, such as Output.
• Data format - Type of data that is 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
IMPORTANT You can only use direct connections with the local expansion modules in a
CompactLogix 5370 L1 control system.
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 controller.
The distributed I/O modules that are 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 chassis of the
adapter 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 125.
Monitor I/O Modules With CompactLogix 5370 L1 controllers, you can use the following options to
monitor I/O modules:
When a fault occurs on an I/O module, a yellow triangle on the module listing in
the Controller Organizer alerts you to the fault.
The following graphic shows the Quick View Pane, which indicates 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 that are physically installed in the system.
2. Make sure that 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 must 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.
Notes:
Topic Page
Select I/O Modules 183
Embedded Analog I/O Modules Data Arrays 204
Validate I/O Layout 218
Configure Local I/O Modules 224
Configure Distributed I/O Modules on an EtherNet/IP Network 227
Configure Distributed I/O Modules on an EtherNet/IP Network 227
Configure Distributed I/O Modules on a DeviceNet Network 231
Monitor I/O Modules 233
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 on one 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 time
intervals at which data is transmitted between the controller and each embedded
I/O point. The’ available RPI range of the embedded I/O points 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 applied.
• The RPI value for an embedded I/O module is intended to establish a time
interval at which data is transmitted. However, the configuration of your
CompactLogix 5370 L2 control system can affect the actual time interval of
data transmission.
For more information, see Estimate Requested Packet Interval on page 218.
IMPORTANT Figure 25 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.
Digital Input
Points
Digital Output
Points
Figure 26 - CompactLogix 5370 L2 Controllers Embedded Digital Input Point Wiring Diagram
+ DC (Sinking)
- DC (Sourcing)
24V DC
- DC (Sinking)
+ DC (Sourcing)
Figure 27 - CompactLogix 5370 L2 Controllers Embedded Digital Output Point Wiring Diagram
+ DC
24V DC
- DC
IMPORTANT The embedded analog I/O points are available on only the 1769-L24ER-QBFC1B
and 1769-L27ERM-QBFC1B controllers.
Table 10 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 10 - Input Types
Input Type Input Ranges Project Configuration
Voltage • Type -50…50 mV
• Type -100…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 28 shows the embedded analog I/O points and how each termination
point is used with different analog input types.
Thermocouple Input Type Connections RTD and Resistance Input Type Connections
2-wire Device
Wiring Diagram
Earth
3-wire Device
Wiring Diagram
Earth
4-wire Device
Wiring Diagram
Table 11 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 11 - 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 33 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.
Voltage
Load
Current
Load
IMPORTANT The embedded high-speed counters are available on only the 1769-L24ER-
QBFC1B and 1769-L27ERM-QBFC1B controllers.
The L2 embedded high-speed counters operate like the 1769-HSC module. See
1769-UM006 for further information.
Each counter uses differential inputs that are compatible with standard
differential-line driver output devices and single-ended devices. Figure 34 shows
the embedded high-speed counter input points.
Cable
External
Power Shield
Supply
Earth
Shield/Housing
Only connect if housing is electronically
isolated from the motor and ground.
Cable
Shield
External
Power
Supply
Earth
Shield/Housing
Only connect if housing is electronically
isolated from the motor and ground.
The embedded high-speed counter also supports four output points. Figure 37
shows a wiring diagram for the embedded high-speed counter output points.
IMPORTANT Figure 37 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.
+DC
5/24V DC
-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 open terminal for secure
placement, we recommend that you connect the wire to a ferrule and insert
it into the open terminal.
4. Repeat step 3 for all embedded I/O wires that are needed in your
application.
If any issues arise with a removable connector and you suspect a connection point
can 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 that illuminates on the tester,
varies by continuity tester. The following example graphic shows a continuity
tester with one 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.
3. Pull the connector away from the module and disconnect any wires.
4. Connect the wires to the replacement connector.
5. Push the connector back into the module and engage the clips to secure it.
The module update time is the time that is 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 that are described in the
following section.
Some combination of the following times determines the channel update time for
an enabled analog input channel:
• 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 that are 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 10 on page 187.
Regardless of which voltage range the channel uses, the channel update time
remains the same. For more information, see Table 12.
Table 12 shows the channel update times for each channel input type and filter
frequency selection.
Table 12 - 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 must account for more voltage at the junction of the thermocouple
field wires and the input point. More voltage can alter the input signal on that
point and, therefore, affect the update time of that channel.
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 by using the thermocouple
input type. If you enable CJC and select Update Cold Junction Compensation
every other scan, an extra update time exists on the channel. This extra update
time increases the overall channel update time.
The filter frequency selection for the channel determines the CJC update time.
Table 13 shows the CJC update times that are based on filter
frequency selections.
Table 13 - 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 another filter value is selected for each, the filter frequency selection
with the slowest update time determines the filter frequency selection
with the slowest update time determines the CJC 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 instance 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 for the respective input channel in the tags for the
project.
Open circuit detection can be enabled or disabled on any channel input type
except for an input channel that is 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 an Open Circuit
Response selection for the channel.
Table 14 describes the module response that is associated with each enable
selection.
Table 14 - Open Circuit Detection Response Definitions
Response Option Definition
Upscale Sets the input data value to full upper-scale value of channel data word. The selected input
type and data format determines the full-scale value.
Downscale Sets the input data value to full lower-scale value of channel data word. The selected input
type and data format determines the low scale value.
Last State Sets the input data value to the last input value before 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 extra 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.
Table 15 lists example module update times that are based on channel
configurations.
Table 15 - Example Module Update Times
Example Enabled Analog Input Channel Update Time Calculations Module
Channel Configuration Update
Time
• Channel 0: 57 ms 57 ms
– Input type = Current
– Filter Frequency Selection = 60 Hz
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 only the 1769-L24ER-QBFC1B
and 1769-L27ERM-QBFC1B controllers.
The 1769-L24ER-QB1B controller does not have an embedded analog
I/O module.
Input Array
The input data array for the embedded analog I/O module contains 11 words as
described in Table 16. This array is read-only and the default value for all bits is 0.
Table 16 - CompactLogix 5370 L2 Controller Embedded Analog I/O Module 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 16 - CompactLogix 5370 L2 Controller Embedded Analog I/O Module 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 that is 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 output image array of the module contains four words
as described in Table 17. This array is write only and the default value for all bits
is 0.
Table 17 - CompactLogix 5370 L2 Controller Embedded Analog I/O Module 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 configuration image array of the module contains 43
words as described in Table 18.
Table 18 - CompactLogix 5370 L2 Controller Embedded Analog I/O Module 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 18 - CompactLogix 5370 L2 Controller Embedded Analog I/O Module 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 the process alarms of a channel.
0 = Disable
1 = Enable
AL Use this bit to enable or disable alarm latching on the process alarm of a channel.
0 = No latch
1 = Latch
EI Use this bit to enable or disable interrupts on the process alarms of a channel.
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 before 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 combination of values in bits 14 and 15 determine the mode, 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 18 - CompactLogix 5370 L2 Controller Embedded Analog I/O Module 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 used by the controller. The combination of multiple selections in
(cont.) Dta Fm words and bits determines this value.
ChIx For more information on what selections determine the input data form that is used, see Table 20 on page 212.
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 21 on page 212.
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 19 on
Setting page 211.
Chx
Process Use to configure the Process Alarm High value for a channel. Configuration is done by 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 by 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 by 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 is 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 is also 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 internal calibration of the module occurs once every 5 minutes.
• If disabled, the internal calibration of the module occurs only once at power on/ reset.
Cycle Calibration enables 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 18 - CompactLogix 5370 L2 Controller Embedded Analog I/O Module 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 that is derived from lab
measurements of each terminal block pin's stable temperature. In this condition, all channel data is overridden with the CJC temperature of that
channel.
• 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 used by the controller. The combination of multiple selections in
Dta Fm words and bits determines this value.
ChIx For more information on what selections determine the output data form that is used, see Table 22 on page 213.
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 23 on page 214.
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 18 - CompactLogix 5370 L2 Controller Embedded Analog I/O Module 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 19 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 19 - 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 causes a
Module Configuration Error (contained in the Mod_Condition Array).
Table 20 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 21 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 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 29 and 37 to make this selection.
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 29 and 37 to make the
selections.
• 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 that is 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.
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:
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
system configuration parameters determine the actual rate at which the controller
scans the modules. That is, the controller can be configured to scan an I/O
module at one rate but actually scan the module at another 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.
The configuration parameters for a system determine the impact on actual RPI
rates. These configuration factors can affect the effective scan frequency for any
individual embedded or local expansion module:
• Rates at which RPI values are set for embedded I/O modules
• Number of embedded I/O modules that are used in the system
• Types of embedded I/O modules that are used in the system
• Rates at which RPI values are set for Compact I/O modules
• Number of Compact I/O modules in the system
• Types of Compact I/O modules in the system
• Application user task priorities
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 that are used as local expansion modules.
Therefore, the consideration for using modules can be any of the following system
configurations:
• Only embedded I/O modules
• Only Compact I/O modules
• Some combination of embedded I/O modules and Compact I/O modules
You can set RPI rates higher for individual Compact I/O modules than the rates
listed in Table 24. 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 24, most CompactLogix 5370
L2 control systems operate as expected. Some systems that follow the guidelines
can experience a Module RPI Overlap minor fault that is described in the
following table.
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 module 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 are designed to
protect against 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 as follows:
The embedded I/O modules are not considered local expansion modules.
However, you must still 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 25 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 25 - 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 in the following
graphic.
1769-HSC Module
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 25 - 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 in the
following graphic.
1769-HSC High-speed
Module
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 appearance of the module in the application.
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 one of these types of local I/O modules in
the Studio 5000 environment:
• Configure Embedded I/O Modules
• Configure Local Expansion Modules
2. Click the required tab, make the necessary changes, and click OK.
IMPORTANT You can also use the tags to configure the embedded I/O modules of the
CompactLogix 5370 L2 controller. 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 26.
Table 26 - 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 in the CompactLogix 5370 L2 control system, distributed input
modules are scanned at the rate the DeviceNet adapter that connects the input modules to the network supports. For example, if your
system includes a remote system of 1734 POINT I/O™ modules on a DeviceNet network, the 1769-SDN scanner 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 - Hardware series of the module.
• Revision - Major and minor firmware revision levels that are used on the module.
• Electronic Keying - See LOGIX-AT001 for Electronic Keying information.
• Connection - Type of connection between the controller writing the configuration and the I/O module, such as Output.
• Data format - Type of data that is 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 enabled, that is, if the connection to an I/O module fails in Run mode, a major fault occurs 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.
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 controller.
The distributed I/O modules that are 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 chassis of the adapter 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 125.
PanelView™ Plus
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.
1. If you have not done so, install a 1769-SDN Compact I/O DeviceNet
scanner into the local bank of your CompactLogix 5370 L2 control
system.
2. Right-click 1769 Bus and choose New Module.
6. Use RSNetWorx for DeviceNet software to define the scan list in the
1769-SDN scanner to communicate data between the devices and the
controller through the scanner.
• 1769-L27ERM-QBFC1B
• 1769-SDN
Monitor I/O Modules With CompactLogix 5370 L2 controllers, you can use the following options to
monitor I/O modules:
When a fault occurs on an I/O module, a yellow triangle on the module listing in
the Controller Organizer alerts you to the fault, as shown in the following
graphic.
The following graphic shows the Quick View Pane, which indicates 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
Notes:
Topic Page
Select I/O Modules 237
Validate I/O Layout 242
Configure I/O 253
Configure Distributed I/O Modules on an EtherNet/IP Network 255
Configure Distributed I/O Modules on a DeviceNet Network 258
Monitor I/O Modules 260
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 more 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, how you connect to the first extra bank—on the right or left
side of the bank, determines the expansion cable that is installed at the
end of the local bank. See Figure 38 on page 239 for examples of how to
connect a local bank to extra banks.
c. Complete the installation of the remaining banks in your system.
IMPORTANT Make sure that you install an end cap at the end of the last bank in
your system.
Horizontal Orientation
Bank 1
1769-CRRx Cable
Vertical Orientation
Bank 2
Wire each Compact I/O module that is 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.
Local Expansion Modules Distributed I/O Modules
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
Validate I/O Layout After you have selected your I/O modules, you must validate the system that 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
The configuration parameters for a system determine the impact on actual RPI
rates. These configuration factors can affect the effective scan frequency for any
individual module:
• Rates at which RPI rates are set for other Compact I/O modules
• Number of other Compact I/O modules in the system
• Types of other Compact I/O modules in the system
• Application user task priorities
You can set the RPI rates of individual Compact I/O modules higher than the
rates listed in Table 28. 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 28, most CompactLogix 5370
L3 control systems operate as expected. Some systems that follow the guidelines
can experience a Module RPI Overlap minor fault as described in the
following table.
The 1769 Compact I/O power supplies provide power to CompactLogix local
and more banks. The provided power is measured in current capacity.
• 1769 Compact I/O power supplies have two maximum current capacity
requirements that affect how you design and configure one bank.
Current Capacity for Side of Bank Current Capacity for Side of Bank
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 left and right sides of the power supply.
IMPORTANT One bank requires the CompactLogix 5370 L3 controllers to reside in the
leftmost slot. At minimum, you must calculate the power consumption of the
controller on the left side of the power supply.
If more modules are installed on the left side of the power supply, you must
calculate the power consumption for those modules as well.
If more 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 more banks, you can install up to eight modules if power supply
distance ratings for the modules validate the system design.
IMPORTANT In extra 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 following table.
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 multiple banks, you can install the additional
banks horizontally or vertically, as shown in this graphic.
Horizontal Orientation
Local Bank
Extra Bank
• Each I/O module also has a power supply distance rating and 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 can 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 245.
Local Bank
To validate the local bank design, confirm that 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 power consumption of the modules on each side of the power supply
does not exceed the capacity of the power supply for that side.
• The total power consumption by all modules in the bank does not exceed
the capacity of the power supply 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 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 Regarding power supply distance ratings, if you install a module that violates
its power supply distance rating specification, the system can appear to
operate normally for a time, but could experience operational issues over time,
such as I/O faults.
Additional Banks
If your application calls for twelve or more I/O modules, at minimum, you must
install the modules in extra banks. The conditions of each application determine
the number of extra banks.
Once the local bank design is validated, you must validate the design for any
additional banks. To validate extra bank designs, confirm that 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 power consumption of the modules on each side of the power supply
does not exceed the capacity of the power supply for that side.
• Modules are installed such that all power supply distance rating
requirements are met.
Local Bank
1769-CRRx Cables
Extra 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 extra banks for
the local expansion modules of the system. 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 extra 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.
This graphic shows 1769-HSC high-speed counter modules that are installed in
a 1769-L36ERM control system that meet the power supply distance rating of
the module.
Local Bank
Extra 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 31.
Table 31 - 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 that the DeviceNet adapter that connects
the input modules to the network supports. For example, the scan rate for distributed 1734 POINT I/O™ over DeviceNet can only occur 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 - Hardware series of the module.
• Revision - Major and minor firmware revision levels that are used on the module.
• Electronic Keying - See LOGIX-AT001 for Electronic Keying information.
• Connection - Type of connection between the controller writing the configuration and the I/O module, such as Output.
• Data format - Type of data that is 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 enabled, that is, if the connection to an I/O module fails in Run mode, a major fault occurs on
the controller.
I/O Connections
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 controller.
The remote I/O modules that are 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 125.
PanelView™ Plus
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.
1. If you have not done so, install a 1769-SDN Compact I/O DeviceNet
scanner into the local bank of your CompactLogix CompactLogix 5370
L3 control system.
2. Right-click 1769 Bus and choose New Module.
6. Use RSNetWorx for DeviceNet software to define the scan list in the
1769-SDN scanner to communicate data between the devices and the
controller through the scanner.
• 1769-L33ERM
• 1769-SDN Scanner
Monitor I/O Modules With CompactLogix 5370 L3 controllers, you can monitor I/O modules in the
following ways:
When a fault occurs on an I/O module, a yellow triangle on the module listing in
the Controller Organizer alerts you to the fault.
The following graphic shows the Quick View Pane, which indicates 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
Develop Applications
Topic Page
Elements of a Control Application 263
Tasks 264
Programs 268
Routines 270
Tags 271
Programming Languages 274
Add-On Instructions 275
Access the Module Object 276
Monitoring Controller Status 278
Monitoring I/O Connections 279
System Overhead Time Slice 282
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
• Parameters and Local Tags
Task 32
Task 1
Configuration
Status
Watchdog
Program 1000
Program 1
Program (Local
Main Routine Tags and
Parameters)
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 that are based on criteria. This multitasking allocates
the processing time of the controller among the different operations in your
application:
• The controller executes only one task at a time.
• One task can interrupt the execution of another task and take control.
• In any given task, multiple programs can be used. However, only one
program executes at a time.
• You can display tasks in the Controller or Logical Organizer views, as
necessary.
Control Application
Task 32
Task 1 Task 1
Contains the following: Configuration
• Configuration Data
Status
• Status Data
• Watchdog Data Watchdog
• Programs Program 1000
Program 1
Program (Local
Main Routine Tags and
Parameters)
Fault Routine
Other Routines
Controller (global)
I/O Data System-shared Data
Tags
Main Task
(continuous)
Main Task
(continuous)
Task 2
(periodic)
Task 2
(periodic) Task 3
(event)
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 1000 separate Programs per task, each with its own
executable routines and program-scoped tags. Once a task is triggered (activated),
all programs that are assigned to the task execute in the order in which they are
grouped. Multiple tasks cannot share Programs and Programs appear only once in
the Controller Organizer.
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 interrupts any lower priority task. A periodic or
event task interrupts the continuous task, which has the lowest priority.
You can configure periodic tasks to execute from the lowest priority of 15 up to
the highest priority of 1. Configure the task priority by using the Task Properties
dialog box.
Task 32
Task 1
Configuration
Status
Watchdog
Program 1000
Program 1
Program 1 Program (Local
Contains the following: Tags and
Main Routine
• Main Routine Parameters)
• Fault Routine
• Other Routines Fault Routine
• Program Tags
Other Routines
Program
Program
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.
Each program has a main routine. This is the first routine to execute when the
controller triggers the associated task and calls the associated program. Use logic,
such as the Jump to Subroutine ( JSR) instruction, to call other routines.
You can also specify an optional program fault routine. The controller executes
this routine if it encounters an instruction-execution fault in any of the routines
in the associated program.
Task 32
Task 1
Configuration
Status
Watchdog
Program 1000
Program 1
Program (Local
Main Routine Tags and
Parameters)
Fault Routine
Other Routines
Controller (global)
Tags I/O Data System-shared Data
Routine
Routine
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 in the following figure, 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. The tag lets you do the following:
• Organize your data to mirror your machinery.
• Document your application as you develop it.
This example shows data tags that are 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 parameters and local
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 more information, such as limits,
engineering units, or state identifiers, for various components within your
controller project.
You must know which tags have limits that are 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 that are 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.
• Alias 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 only by HMI applications.
If an array tag is using indirect addressing to access limits in logic, the following
conditions apply:
• If the array tag has limits that are 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, any element of the array that does not have Max
configured inherits the value of 100 when being used in logic. However, it
is not visible to you that the value inherited from MyArray is configured in
the tag properties.
• At least one array element must have a limit that is 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 that is configured if
MyArray has not configured Max.
• 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, use the value of 127.
If an array element is directly accessed, the element has to have the extended
property defined. If not, verification fails.
Programming Languages The CompactLogix controller supports these programming languages, 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 one 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.
Access the Module Object The MODULE object provides status information about a module. To select a
particular module object, set the Object Name operand of the GSV/SSV
instruction to the module name. The specified module must be present in the
I/O Configuration section of the controller organizer and must have a device
name.
You must create a Module Reference parameter when you define the Add-On
Instruction to access the MODULE object data. A Module Reference parameter
is an InOut parameter of the MODULE data type that points to the MODULE
Object of a hardware module. You can use module reference parameters in both
Add-On Instruction logic and program logic.
For more information on the Module Reference parameter, see the Logix5000
Controllers Add-On Instructions Programming Manual, publication
1756-PM010 and the Logix Designer application online help.
The Path attribute is available with Logix Designer application, version 24.00.00
and later. This attribute provides a communication path to the module.
For more information on the attributes available in the MODULE object, see the
Logix5000™ Controllers General Instructions Reference Manual, publication
1756-RM003.
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. The instructions are available from the Input/Output tab of the
Instruction tool bar.
When you add a GSV/SSV instruction to the program, the object classes, object
names, and attribute names for each instruction are displayed. For the GSV
instruction, you can get values for the available attributes. For the SSV
instruction, only those attributes you are allowed to set are displayed.
Some object types appear repeatedly, so you have to specify the object name. For
example, there can be several tasks in your application. Each task has its own Task
object that you access by the task name.
There are several objects and attributes that you can use the GSV and SSV
instructions to monitor and set the system. For more information about GSV
instructions, SSV instructions, objects, and attributes see the Logix5000
Controllers General Instructions Reference Manual, publication 1756-RM003.
Monitoring I/O Connections If communication with a device in the I/O configuration of the controller does
not occur in an application-specific period, 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 can be greater, depending on the RPI of
the application. 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.
Depending on your application, you can want an I/O connection error to cause
the Controller Fault Handler to execute. To do so, set the module property that
causes a major fault to result from an I/O connection error. The major fault
causes the execution of the Controller Fault Handler.
First, develop a routine in the Controller Fault Handler that can respond to I/O
connection faults. 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 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 effect.
The table shows the ratio between the continuous task and service
communication at various system overhead time slices.
As shown in Table 36, 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.
Topic Page
Motion Axes Support 286
Maximum Number of Position Loop-configured Drives 287
Time Synchronization 288
Configure Integrated Motion on the EtherNet/IP Network 289
Scalability in Applications Using Integrated Motion on EtherNet/IP Networks 293
IMPORTANT The following CompactLogix 5370 controllers support Integrated Motion over
an EtherNet/IP network:
• 1769-L18ERM-BB1B controller
• 1769-L27ERM-QBFC1B controller
• 1769-L30ERM controller
• 1769-L33ERM controller
• 1769-L36ERM controller
AXIS_VIRTUAL Axis
AXIS_CIP_DRIVE Axis
The AXIS_CIP_DRIVE axis is a motion axis that is 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 the Studio 5000® environment. 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 one 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 that are connected over an EtherNet/IP network.
IMPORTANT While all CompactLogix 5370 controllers are CIP Sync-capable, not all
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 37 on page 287 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 that you have previously created a project for your
1769-L36ERM controller. If you have not, do so before continuing.
Add a Drive
You can only use these drives in an application that uses Integrated Motion over
an EtherNet/IP network:
• Kinetix 350 drive
• Kinetix 5700 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 that is listed on page 11.
6. If you must change the configuration for any of the following parameters,
click Change in the Module Definition area:
• Revision
• Electronic Keying
• Connection
• Power Structure
• Verify Power Rating on Connection
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 that require simpler
configuration and complex configuration of Integrated Motion on EtherNet/IP
networks parameters:
• 1769-L30ERM
• 1769-L33ERM
• 1769-L36ERM
1769-L33ERM
Stratix 2000
PowerFlex 755
PanelView™
Kinetix 350
1769-L33ERM
Kinetix 350
Kinetix 6500
POINT I/O™
PowerFlex 755
1769-L18ERM-BB1B
The simpler control system often includes unmanaged switches, such a Stratix
2000™ switch, and Kinetix 350 drives, as shown in this example.
1769-L18ERM-BB1B
Stratix 2000
PowerFlex 755
PanelView Plus
Kinetix 350
1769-L27ERM-QBFC1B Controller
1769-L27ERM-QBFC1B
Stratix 2000
PowerFlex 755
PanelView Plus
Kinetix 350
This chapter describes the primary tasks that are 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 299
Store a Project 299
Load a Project 302
IMPORTANT The life expectancy of nonvolatile media is dependent on the number of write
cycles that are performed. Nonvolatile media use a wear leveling technique, or
technology for prolonging the service life, but avoid frequent writes.
Avoid frequent writes when logging data. We recommend that you log data to
a buffer in the memory of your controller 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 that you can
send to Rockwell Automation® that provides enhanced diagnostics of your
application and firmware revision if 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 can complete other tasks by 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 user memory
(RAM) of the CompactLogix 5370 controller. The controller configuration
the Secure Digital Card determines the option that is used.
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.
5. Click Load/Store.
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 can 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 can 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 can exist:
– After the controller fully resets itself, the OK indicator is solid green.
Notes:
Use Logix Designer The Logix Designer application indicates fault conditions in the following ways:
Application for Warning signal on the main screen next to the module - This occurs when the
Troubleshooting connection to the module is broken. The controller state also indicates Faulted
and the Controller fault is illuminated in red.
On the Module Info tab, in the Status section, the Major and Minor Faults are
listed along with the Internal State of the module.
Notification in the Tag Editor - General module faults are also reported in the
Tag Editor. Diagnostic faults are reported only in the tag editor.
To display recent fault information in the Major Faults tab of the Module
Properties screen, you must check the Major Fault on Controller option in the
Connection tab.
When you are monitoring the configuration properties of a module in the Logix
Designer application and receive a Communication fault message, the Major
Faults tab indicates the type of fault under Recent Faults.
Use the CompactLogix 5370 The following graphic shows the controller status indicators for all
CompactLogix 5370 controllers.
Controllers Status Indicators
Replacement Considerations
Firmware Compatibility
Dimensions There are no dimension differences between the Series A controller and the
Series B controller.
Series A Wiring
Examples
In this example:
• Replace a Series A controller with a Series B controller
• Update controller firmware from V21 to V23
Requirements:
Category Tasks
Power Supply Wiring The series B controller requires only one power supply,
but the Series B controller does support two power
supplies. You can retain the current power supply
design for the Series A controller and avoid rewiring.
Controller Firmware Install firmware, V24
Programming Software Install the Studio 5000® environment, V24
Personal Computer Windows 7
In this example:
• Replace a Series A controller with a Series B controller
• Leave controller at firmware version 20
Requirements:
Category Tasks
Power Supply Wiring The Series B controller requires only one power supply,
but the Series B controller does support two power
supplies. You can retain the current power supply design
for the Series A controller and avoid rewiring.
Controller Firmware Install Firmware, V20
Programming Software No change required
Personal Computer Windows XP
Topic Page
CompactLogix 5370 L1, Series A, Controller Power Connection 315
CompactLogix 5370 L1, Series A, Controller Field Power to I/O Devices Connection 321
The external power supply must be dedicated to the embedded supply of the
controller. The external power supply converts 115/230V AC power to 24V DC
or other application-required DC voltage that is within the operating range of
the controller.
• The external 24V DC power source that is connected to the VDC+ and
VDC- terminals on the removable connector must reside in the same
enclosure as the CompactLogix 5370 L1 controller.
• Use a power source that most effectively meets your application needs.
That is, calculate The power requirements for your application 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.
• Not all Class 2/SELV-listed power supplies are certified for use in all
applications, for example, use in nonhazardous and hazardous
environments.
• Only for example purposes, this section describes how to use a 1606-
XLE120E, NEC Class 2 switched-mode power supply. The exact steps for
other external power supplies can vary from the steps that are described
here.
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 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.
5. Connect the wire that is 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.
6. Connect the wire that is 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.
The following graphic shows an external 24V DC power source that is connected
to a CompactLogix 5370 L1 controller.
CompactLogix 5370 L1, Complete these steps to connect field power to the CompactLogix 5370 L1 series
A controller. Series B L1 CompactLogix 5370 controllers can also be connected
Series A, Controller Field to field power as instructed in this procedure.
Power to I/O Devices
Connection 1. Verify that the separate external 24V DC power source that powers the
CompactLogix 5370 L1 controller is not powered.
2. Verify that the external 24V DC power source that is connected to the
FP+ and FP- terminals is not powered.
3. Mount the external power supply that connects 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.
6. Connect the wire that is connected to the + terminal on the external 24V
DC power source to the FP+ terminal, that is, the fourth terminal from
the top, on the removable connector.
7. Connect the wire that is connected to the - terminal on the external 24V
DC power source to the FP- terminal, that is the fifth terminal from the
top, on the removable connector.
10. Turn on power to the separate external 24V DC power source connected
to the VDC+ and VDC- terminals of the removable connector.
11. Turn on power to the external 24V DC power source connected to the
FP+ and FP- terminals of the removable connector.
FP Power Supply
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 can be especially useful if you are
deciding to upgrade your hardware or software that is based on information
added with previous revisions of this manual.
This table lists the publication revision, publication date, and changes that are
made with the revision.
Table 46 - History of Changes
Publication Revision and Date Topic
1769-UM021E-EN-P, November 2014 Added Replacement Considerations Appendix
Added series B information
Added updated Electronic Keying information
Addition of Series A appendix
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 is
never triggered because the functionality has been disabled in the
controller.
Numerics C
1734 POINT I/O modules 143-181 CompactLogix 5370 L1 controllers
BUS OFF detection and recovery 181 connecting power 26-30, 315-324
configure 174-179 connections to I/O modules 175
monitor faults 179 DIN rail use 21
removal and insertion under power 165 direct connections 176
requested packet interval 166 embedded I/O module 17
select 143 wiring diagrams 152
using as local expansion modules with embedded power supply 16, 317
CompactLogix 5370 L1 controllers example EtherNet/IP network system
17 configuration 120
validate layout 163-169 grounding 21, 24
1769 Compact I/O modules 237-262 I/O modules 143-181
calculate system power consumption 245- installation 13-32
247 grounding 24
CompactLogix 5370 L3 controllers 58 minimum spacing 22
configure 224-227, 253-259 mounting 21-23
connections 227, 254 SD card 19-20
end cap detection 235, 262 system dimensions 23
local banks available with CompactLogix 5370 integrated motion over an EtherNet/IP
L3 controllers 58 network 285-296
monitor faults 233, 260 local expansion modules 17
requested packet interval 218, 226, 242, 254 BUS OFF detection and recovery 181
select 183, 237 removal and insertion under power 165
using as local expansion modules with minimum spacing 22
CompactLogix 5370 L2 controllers mounting 21-23
36 networks
validate layout 242-250 EtherNet/IP network connection 32
1769 Compact I/O power supplies USB connection 31
calculate system power consumption 245- parts 18
247 place I/O modules 169
1784-SD1 and 1784-SD2 cards 18, 37 rack-optimized connections 176
select I/O modules 143
installation selecting operating mode 112-113
CompactLogix 5370 L1 controllers 19- status indicators 305-310
20 system components 16, 116
CompactLogix 5370 L2 controllers 38- system dimensions 23
39 wiring diagrams 152
CompactLogix 5370 L3 controllers 60- CompactLogix 5370 L2 controllers
61
connecting power 50-53
connections to I/O modules 227
A DIN rail use 40, 46
direct connections 227
additional resources 11 embedded I/O module 36
Add-On Instructions embedded power supply 36, 50
in project 275 example DeviceNet network system
application configuration 122
elements 263 example EtherNet/IP network system
AutoFlash 98 configuration 121
grounding 40, 46
load firmware 108-111 installation 33-54
grounding 46
minimum spacing 41
B mounting 40-41, 45
BOOTP server 75 SD card 38-39
set IP address 79-83 system dimensions 41
integrated motion over an EtherNet/IP
network 285-296
local expansion modules 36
minimum spacing 41
mounting 40-41, 45
networks
EtherNet/IP network connection 54
P 20
CompactLogix 5370 L2 controllers 38-
panel mounting 39
CompactLogix 5370 L2 controllers 45 CompactLogix 5370 L3 controllers 60-
CompactLogix 5370 L3 controllers 70 61
periodic task 266 load a project 302-303
power supply load firmware 111
connections to CompactLogix 5370 L1 set IP address 93
controllers 26-30, 315-324 store a project 299-301
connections to CompactLogix 5370 L2 software
controllers 50-53 BOOTP 75
connections to CompactLogix 5370 L3 set IP address 79-83
controllers 63 DHCP 75
distance rating set IP address 86
CompactLogix 5370 L3 controllers 69 Logix Designer application
embedded power supply with CompactLogix AutoFlash 98
5370 L1 controllers 16, 317 required installation tasks 75-113
embedded power supply with CompactLogix RSLinx Classic 75
5370 L2 controllers 36, 50 change IP address 95
priority set IP address 87-88
task 267 RSLogix 5000 75
program RSNetWorx for DeviceNet 75
Studio 5000 environment 75
in project 268
star network topology 74
scheduled 269
system overhead time slice 282 status
unscheduled 269 monitor
programming languages 274 connections 279
project status indicators 305-310
elements 263 Studio 5000 environment 75
Studio 5000 Logix Designer application. See
Logix Designer application
R system assembly
rack-optimized connections calculate system power consumption
CompactLogix 5370 L1 controllers 176 CompactLogix 5370 L1 controllers 168,
CompactLogix 5370 L2 controllers 227 220
CompactLogix 5370 L3 controllers 254 CompactLogix 5370 L3 controllers 245-
removal and insertion under power 247
local 1769 Compact I/O modules CompactLogix 5370 L3 controllers
CompactLogix 5370 L3 controllers 62 select I/O modules 237
local expansion modules place I/O modules
CompactLogix 5370 L1 controllers 165 CompactLogix 5370 L1 controllers 169
requested packet interval select I/O modules
CompactLogix 5370 L1 controllers 143
CompactLogix 5370 L1 controllers 166, 175
CompactLogix 5370 L2 controllers 183
CompactLogix 5370 L2 controllers 218, 226
validate I/O modules layout
CompactLogix 5370 L3 controllers 242, 254
1734 POINT I/O modules 163-169
routine
1769 Compact I/O modules 218-223
in project 270 CompactLogix 5370 L1 controllers 163-
RSLinx Classic software 75 169
change IP address 95 CompactLogix 5370 L2 controllers 218-
set IP address 87-88 223
RSLogix 5000 software 75 CompactLogix 5370 L3 controllers 242-
RSNetWorx for DeviceNet software 75 250
system components
CompactLogix 5370 L1 controllers 16, 116
S CompactLogix 5370 L2 controllers 36, 116
CompactLogix 5370 L3 controllers 58, 116
sample projects 284
system dimensions
scheduled
CompactLogix 5370 L1 controllers 23
program 269 CompactLogix 5370 L2 controllers 41
SD card 98, 297-303 CompactLogix 5370 L3 controllers 68
change IP address 97 system overhead time slice 282
installation configure 283
CompactLogix 5370 L1 controllers 19-
T
tag
in project 271
task
continuous 266
event 170-173, 266
in project 264
periodic 266
priority 267
time slice 282
U
unscheduled
program 269
USB cable
CompactLogix 5370 L1 controllers 31
CompactLogix 5370 L2 controllers 53
CompactLogix 5370 L3 controllers 72
V
validate I/O modules layout
1734 POINT I/O modules 163-169
1769 Compact I/O modules 218-223, 242-
250
W
wiring diagrams
CompactLogix 5370 L1 controllers 152
In addition, we offer multiple support programs for installation, configuration, and troubleshooting. For more
information, contact your local distributor or Rockwell Automation representative, or visit
http://www.rockwellautomation.com/services/online-phone.
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/rockwellautomation/support/overview.page, or contact your local
Rockwell Automation representative.
Rockwell Automation tests all of its products to help 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