User Manual

Original Instructions

CompactLogix 5380 Controllers

Catalog Numbers 5069-L306ER, 5069-L306ERM, 5069-L310ER, 5069-L310ER-NSE, 5069-L310ERM, 5069-L320ER, 5069-
L320ERM, 5069-L330ER, 5069-L330ERM, 5069-L340ER, 5069-L340ERM, 5069-L350ERM, 5069-L380ERM, 5069-L3100ERM
Important User Information
Read this document and the documents listed in the additional resources section about installation, configuration, and
operation of this equipment before you install, configure, operate, or maintain this product. Users are required to
familiarize themselves with installation and wiring instructions in addition to requirements of all applicable codes, laws,
and standards.

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.

Labels may also be on or inside the equipment to provide specific precautions.

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).
 Table of Contents

Preface
Summary of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 1
CompactLogix 5380 System Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
and Controllers Controller Firmware and Logix Designer Application
Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Software Application Requirements. . . . . . . . . . . . . . . . . . . . . . . . . 12
Product Compatibility and Download Center . . . . . . . . . . . . . . . 12
CompactLogix 5380 System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Controller Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Design a CompactLogix 5380 System . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
System Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Power a CompactLogix 5380 System . . . . . . . . . . . . . . . . . . . . . . . . 16
Secure Digital (SD) Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Chapter 2
Use EtherNet/IP Modes EtherNet/IP Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Dual-IP Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Linear/DLR Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Configure the EtherNet/IP Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Configure Dual-IP Mode in the Logix Designer
Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Configure Dual-IP Mode in RSLinx Classic Software. . . . . . . . . 35
Configure Linear/DLR Mode in the Logix
Designer Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Configure Linear/DLR Mode in RSLinx Classic
Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Change the EtherNet/IP Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Change the EtherNet/IP Mode in the Logix
Designer Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Change the EtherNet/IP Mode in RSLinx Classic
Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Port Functionality in Dual-IP Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Port IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
DNS Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
DNS Request Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
SMTP Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Use Socket Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Send Message Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Software Display Differences for EtherNet/IP Modes . . . . . . . . . . . . 51
Controller IP Address and Firmware Updates . . . . . . . . . . . . . . . . . . . 53

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 3

Table of Contents

Chapter 3
Use the Communication Drivers Configure the EtherNet/IP Driver in RSLinx Classic
in RSLinx Classic Software Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Configure the Ethernet Devices Drivers in RSLinx
Classic Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Use the USB Communication Driver in RSLinx
Classic Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Chapter 4
Start to Use the Controller Out-Of-Box State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Connect to the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Connect an Ethernet Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Connect a USB Cable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Set the Controller IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Use the BOOTP-DHCP Tool to Set the Controller
IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Disable BOOTP/DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Use the DHCP Server to Set the Controller IP
Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Use RSLinx Classic Software to Set the Controller
IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Use the Logix Designer Application to Set the
Controller IP Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Use a Secure Digital Card to Set the Controller
IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Update Controller Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Determine Required Controller Firmware . . . . . . . . . . . . . . . . . . . 81
Obtain Controller Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Use ControlFLASH Software to Update Firmware. . . . . . . . . . . 82
Use AutoFlash to Update Firmware. . . . . . . . . . . . . . . . . . . . . . . . . 87
Create a Logix Designer Application Project. . . . . . . . . . . . . . . . . . . . . 89
Change Controller Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Go Online with the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Download a Project to the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Use the Who Active Dialog Box to Download . . . . . . . . . . . . . . . 94
Use the Controller Status Menu to Download . . . . . . . . . . . . . . . 95
Upload from the Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Use the Who Active Dialog Box to Upload . . . . . . . . . . . . . . . . . . 96
Use the Controller Status Menu to Upload . . . . . . . . . . . . . . . . . . 97
Choose the Controller Operation Mode . . . . . . . . . . . . . . . . . . . . . . . . 98
Use the Mode Switch to Change the Operating Mode . . . . . . . . 99
Use the Logix Designer to Change the Operating Mode . . . . . 100

4 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Table of Contents

Chapter 5
Tasks After Controller Use the Secure Digital Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Operation Begins Store to the Secure Digital Card . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Load from the Secure Digital Card . . . . . . . . . . . . . . . . . . . . . . . . . 104
Other Secure Digital Card Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Reset Button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Stage 1 Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Stage 2 Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Disable the Ethernet Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Chapter 6
EtherNet/IP Network Network Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
EtherNet/IP Network Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Software for EtherNet/IP Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Nodes on an EtherNet/IP Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Devices Included in the Node Count. . . . . . . . . . . . . . . . . . . . . . . 118
Devices Excluded from the Node Count. . . . . . . . . . . . . . . . . . . . 118
EtherNet/IP Network Communication Rates . . . . . . . . . . . . . . . . . . 120
Set the Network Communication Rate . . . . . . . . . . . . . . . . . . . . . 120
EtherNet/IP Network Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Device Level Ring Network Topology . . . . . . . . . . . . . . . . . . . . . . 122
Linear Network Topology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Star Network Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Integrated Architecture Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Socket Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Chapter 7
Use I/O Modules Local I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Add Local I/O Modules to a Project . . . . . . . . . . . . . . . . . . . . . . . 131
Electronic Keying. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Remote I/O Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Add Remote I/O Modules to a Project . . . . . . . . . . . . . . . . . . . . . 138
Add to the I/O Configuration While Online . . . . . . . . . . . . . . . . . . . 147
Modules and Devices that Can be Added While Online . . . . . 147
Determine When Data is Updated. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Input Data Update Flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Output Data Update Flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 5

Table of Contents

Chapter 8
Manage Controller Connection Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Communication Controller Communication Interaction with Control Data. . . . . . 152
Produce and Consume (Interlock) Data. . . . . . . . . . . . . . . . . . . . . . . . 153
Requested Packet Interval (RPI) of Multicast Tags . . . . . . . . . . 154
Send and Receive Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Determine Whether to Cache Message Connections . . . . . . . . 156

Chapter 9
Develop Control Applications Elements of a Control Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Event Task with 5069 Compact I/O Modules . . . . . . . . . . . . . . 161
Task Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Routines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Parameters and Local Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Programming Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Add-On Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Extended Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Access the Module Object from an Add-On Instruction . . . . . . . . . 170
Create the Add-On Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Monitor Controller Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Monitor I/O Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Determine If I/O Communication Has Timed Out . . . . . . . . . 173
Determine if I/O Communication to a Specific
I/O Module has Timed Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Automatic Handling of I/O Module Connection
Faults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Sample Controller Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Chapter 10
Develop Motion Applications Motion Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Motion Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Program Motion Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Obtain Axis Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

6 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Table of Contents

Chapter 11
Troubleshoot the Controller Controller Diagnostics with Logix Designer . . . . . . . . . . . . . . . . . . . . 183
Warning Symbol in the I/O Configuration Tree . . . . . . . . . . . . 184
Controller Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Categories on I/O Module Properties Dialog Box . . . . . . . . . . . 186
Notification in the Tag Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Fault Information in Controller Properties Dialog
Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Port Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Advanced Time Sync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Controller Diagnostics with RSLinx Software . . . . . . . . . . . . . . . . . . 197
General Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Port Diagnostics Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Connection Manager Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
USB Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Controller Web Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Home Web Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Tasks Web Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Diagnostics Web Pages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Ethernet Port Web Pages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Advanced Diagnostics Web Pages . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Browse Chassis Web Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Other Potential Issues to Troubleshoot . . . . . . . . . . . . . . . . . . . . . . . . 210
Continuous Task Sends Output Data at High
Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Immediate Output Instructions Issued at High
Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Integrated Motion On an EtherNet/IP Network
Traffic Priority Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 7

Table of Contents

Appendix A
Status Indicators 4-Character Status Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
General Status Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Fault Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Major Fault Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
I/O Fault Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Controller Status Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
RUN Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
FORCE Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
OK Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
SD Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
EtherNet/IP Status Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
NET A1 and NET A2 Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . 223
LINK A1 and LINK A2 Indicators . . . . . . . . . . . . . . . . . . . . . . . . 223
Power Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
MOD Power Indicator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
SA Power Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Thermal Monitoring and Thermal Fault Behavior . . . . . . . . . . . . . . 225

Appendix B
Security Options Disable an Ethernet Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Disable the 4-character Status Display. . . . . . . . . . . . . . . . . . . . . . . . . . 230
Disable the 4-character Display Entirely . . . . . . . . . . . . . . . . . . . . 231
Disable a Subset of 4-character Display Information . . . . . . . . . 233
Disable the Controller Web Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

Index
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

8 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Preface

This manual explains how to use the CompactLogix 5380 controllers.

Make sure that you are familiar with the following:

Use of controllers in a Logix5000 control system

Use of an EtherNet/IP network

Use of various software applications from Rockwell Automation

Summary of Changes This manual was changed to include information about the following
CompactLogix 5380 controllers:

5069-L350ERM

5069-L380ERM

5069-L3100ERM

Additional Resources These documents contain additional information concerning related products
from Rockwell Automation.
Table 1 - Additional Resources
Resource Description
CompactLogix 5380 Controller Provides specifications for CompactLogix 5380 controllers.
Specifications Technical Data,
publication 5069-TD002
CompactLogix 5380 Controllers Describes how to install a CompactLogix 5380 controller.
Installation Instructions, publication
5069-IN013
CompactLogix System Selection Provides information about how to design and select components for a
Guide, publication 1769-SG001 CompactLogix system.
5069 Compact I/O Modules Provides specifications, wiring diagrams, and functional block diagrams for
Specifications Technical Data, 5069 Compact I/O modules.
publication 5069-TD001
Replacement Guidelines: Logix5000 Provides guidelines on how to replace the following:
Controllers Reference Manual, ControlLogix 5560/5570 controller with a ControlLogix 5580 controller
publication 1756-RM100 CompactLogix 5370 L3 controllers with a CompactLogix 5380 controller
5000 Series Digital I/O Module User Provides information on how to install, configure, and operate 5000 Series
Manual, publication 5000-UM004 digital I/O modules.
5000 Series Analog I/O Module User Provides information on how to install, configure, and operate 5000 Series
Manual, publication 5000-UM005 analog I/O modules.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 9

Preface

Table 1 - Additional Resources

Resource Description
5000 Series High-speed Counter Provides information on how to install, configure, and operate 5000 Series
Module User Manual, publication high-speed counter modules.
5000-UM006
EtherNet/IP Communication Modules Describes how to use 5000 Series EtherNet/IP communication modules.
in Logix5000 Control Systems User
Manual, publication ENET-UM004
Ethernet Design Considerations Describes the following Ethernet concepts:
Reference Manual, publication Overview
ENET-RM002 Network layout and components
Network infrastructure devices
Network infrastructure features
Protocol
EtherNet/IP Socket Interface Describes the socket interface that you can use to program MSG
Application Technique, publication instructions to communicate between a Logix5000 controller and Ethernet
ENET-AT002 devices that do not support the EtherNet/IP application protocol.
EtherNet/IP Embedded Switch Describes how to install, configure, and maintain linear and Device Level
Technology Application Guide, Ring (DLR) networks by using Rockwell Automation EtherNet/IP devices
publication ENET-AP005 that are equipped with embedded switch technology.
Integrated Architecture and CIP Sync Provides information on CIP Sync and the IEEE 1588-2008 Precision Time
Configuration Application Technique, Protocol.
publication IA-AT003
Integrated Motion on the EtherNet/IP Reference descriptions of the AXIS_CIP_DRIVE attributes and the
Network Reference Manual, Logix Designer application Control Modes and Methods
publication MOTION-RM003
Electronic Keying in Logix5000 Describes how to use electronic keying in Logix5000 control systems.
Control Systems Application
Technique, publication LOGIX-AT001
Logix5000 Controllers Design Provides information to help design and plan Logix5000 control systems.
Considerations Reference Manual,
publication 1756-RM094
Logix5000 Controllers Instructions Describes the programming instructions available to use in Logix Designer
Reference Manual, publication application projects.
1756-RM009
Motion Coordinate System User Details how to create and configure a coordinated motion application
Manual, publication MOTION-UM002 system.
Industrial Automation Wiring and Provides general guidelines for installing a Rockwell Automation industrial
Grounding Guidelines, publication system.
1770-4.1
Product Certifications website, http:/ Provides declarations of conformity, certificates, and other certification
/www.rockwellautomation.com/ details.
global/certification/overview.page

You can view or download publications at

http://www.rockwellautomation.com/global/literature-library/overview.page.
To order paper copies of technical documentation, contact your local
Allen-Bradley distributor or Rockwell Automation sales representative.

10 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Chapter 1

CompactLogix 5380 System and Controllers

Topic Page
Before You Begin 11
CompactLogix 5380 System 13
Design a CompactLogix 5380 System 15

This chapter describes CompactLogix 5380 control systems.

Before You Begin Before you use your CompactLogix 5380 controller, verify that you have the
required firmware revision and software versions to configure, program, and
monitor the controller.

The following software is required to operate a CompactLogix 5380

control system:
Studio 5000 Logix Designer application
RSLinx Classic software
ControlFLASH software

IMPORTANT You are expected to have the knowledge necessary to use the software
applications mentioned above.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 11

Chapter 1 CompactLogix 5380 System and Controllers

Controller Firmware and Logix Designer Application Compatibility

In a CompactLogix 5380 control system, the controller firmware and the

Logix Designer application must be compatible. To be compatible, the
firmware and software must be of the same major revision level.

For example, the Logix Designer application with major revision 29 is only
compatible with a controller firmware with major revision 29.

For more information on the available firmware revisions and corresponding

software versions that are available with a CompactLogix 5380 controller, see
the Product Compatibility and Download Center.

Software Application Requirements

There are minimum software version requirements for the software

applications that you use in your CompactLogix 5380 control system. If your
CompactLogix 5380 control system does not meet the minimum requirements
it does not work.

Software requirements are not based on major revision levels. For example, to
use the Logix Designer application, version 29.00.00, you must RSLinx Classic
software version 3.81.00 or later.

For more information on the software application requirements to use a

CompactLogix 5380 controller, see the Product Compatibility and Download
Center.

Product Compatibility and Download Center

For more information on controller firmware revisions and software

application minimum requirements, go to the Rockwell Automation Product
Compatibility and Download Center (PCDC) available at:
http://compatibility.rockwellautomation.com/Pages/home.aspx

You can access firmware for your CompactLogix 5380 controller in the
Download section of the PCDC. You can see software compatibility for the
software applications used in a CompactLogix 5380 control system in the
Compare section of the PCDC.

12 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 CompactLogix 5380 System and Controllers Chapter 1

CompactLogix 5380 System The CompactLogix 5380 system is a DIN rail-mounted system that is part of
the Logix5000 family of controllers.

CompactLogix 5380 controller can operate in various applications that range

from standalone systems or in more complex systems with devices connected to
the controller via an EtherNet/IP network.

Controller Features

Table 2 describes features available on CompactLogix 5380 controllers.

Table 2 - CompactLogix 5380 Controller Features
Feature Description
Controller tasks 32 tasks
1000 programs/task
Event tasks; all event triggers
Communication ports 1 - USB port, 2.0 full-speed, Type B
2 - EtherNet/IP ports, 10 Mbps, 100 Mbps, 1 Gbps
EtherNet/IP network topologies supported Device Level Ring (DLR)
Star
Linear
EtherNet/IP nodes supported, max 5069-L306ER, 5069-L306ERM: 16
5069-L310ER, 5069-L310ER-NSE, 5069-L310ERM: 24
5069-L320ER, 5069-L320ERM: 40
5069-L330ER, 5069-L330ERM: 50
5069-L340ER, 5069-L340ERM: 55
5069-L350ERM: 60
5069-L380ERM: 70
5069-L3100ERM: 80
EtherNet/IP modes Linear/DLR mode
Dual-IP mode - Available with the Logix Designer application,
version 29.00.00 or later.
For more information on EtherNet/IP modes, see Chapter 2, Use
EtherNet/IP Modes on page 27.
Integrated motion axes supported 5069-L306ERM: 2
IMPORTANT: Not all CompactLogix 5380 5069-L310ERM: 4
controllers support Integrated Motion on an
EtherNet/IP network 5069-L320ERM: 8
5069-L330ERM: 16
5069-L340ERM: 20
5069-L350ERM: 24
5069-L380ERM: 28
5069-L3100ERM: 32

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 13

Chapter 1 CompactLogix 5380 System and Controllers

Table 2 - CompactLogix 5380 Controller Features

Feature Description
Local I/O modules, max 5069-L306ER, 5069-L306ERM, 5069-L310ER, 5069-L310ER-NSE,
5069-L310ERM: 8
5069-L320ER, 5069-L320ERM: 16
5069-L330ER(1), 5069-L330ERM(1), 5069-L340ER, 5069-
L340ERM, 5069-L350ERM, 5069-L380ERM, L3100ERM: 31
Programming languages Ladder Diagram (LD)
Structured Text (ST)
Function Block Diagram (FBD)
Sequential Function Chart (SFC)
(1) When you use this controller with the Logix Designer application, version 29.00.00, the application limits the number of local
I/O modules in the project to 16. For more information, see the Rockwell Automation Knowledgebase article #942580, 5380
CompactLogix controllers limited to 16 local 5069 modules in V29 of Studio 5000. The document is available at http://
www.rockwellautomation.com/knowledgebase.
With the Logix Designer application, version 30.00.00 or later, the controller supports as many as 31 local I/O modules.

IMPORTANT When you use a CompactLogix 5380 controller, remember the following:
You do not need to configure a System Overhead Time Slice value.
You do not need to reserve controller memory for future memory
usage increases.
For example, when you use CompactLogix 5370 controllers, we
recommend that you reserve 2030% of the controller memory to
accommodate future project increases. This is not necessary with the
CompactLogix 5380 controllers.

Figure 1 - CompactLogix 5380 System

CompactLogix 5380 Controller 5069 Compact I/O Local I/O Modules

14 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 CompactLogix 5380 System and Controllers Chapter 1

Design a CompactLogix 5380 When you design a CompactLogix 5380 system, some components are
required, for example, a DIN rail that is required to mount the system. Other
System components are optional.

System Components

Table 3 describes components that are commonly used in a

CompactLogix 5380 systems.
Table 3 - Components CompactLogix 5380 Systems
Component Purpose Required For More Information
DIN rail Mounting system Yes CompactLogix 5380 Controllers Installation
Instructions, publication 5069-IN013
End cap (5069-ECR) The end cap covers the exposed interconnections Yes
IMPORTANT: The end cap ships with the on the last module in the system.
controller. If you do not install the end cap before powering
the system, equipment damage or injury from
electric shock can result.
External power supply(1) Provides Module (MOD) Power to the system Yes
(1)
External power supply Provides Sensor/Actuator (SA) Power to the Yes - Only if the system
system requires SA power. Power a CompactLogix 5380 System on
If the system does not page 16
require SA power, the
external power supply
is not needed.
Logix Designer application Configure the project that is used to define Yes Before You Begin on page 11
controller activity during system operation Create a Logix Designer Application Project
on page 89
RSLinx Classic software Used as follows: Yes Before You Begin on page 11
Assign the controller an IP address Use the Communication Drivers in
Maintain communication over the EtherNet/IP RSLinx Classic Software on page 55
network
ControlFLASH software Update controller firmware Yes Before You Begin on page 11
Update Controller Firmware on page 80
Secure Digital (SD) card Store data, such as the controller project and No Secure Digital (SD) Card on page 25
IMPORTANT: The 1784-SD2 card ships with diagnostics
the controller.
Ethernet cables Used as follows: No Connect an Ethernet Cable on page 64
Access the controller from the workstation IMPORTANT: If you do
over an EtherNet/IP network to set IP address, not access the
update firmware, download, and upload controller over an
projects EtherNet/IP network,
Connect controller to an EtherNet/IP network you must access it with
and perform tasks that are required for normal a USB connection.
operations
USB cable Access the controller directly from the No Connect a USB Cable on page 65
workstation to set IP address, update firmware, IMPORTANT: If you do
download, and upload projects not access the
controller with a USB
connection, you must
access it over an
EtherNet/IP network.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 15

Chapter 1 CompactLogix 5380 System and Controllers

Table 3 - Components CompactLogix 5380 Systems

Component Purpose Required For More Information
5069 Compact I/O modules Used as follows: Yes - If your application Use I/O Modules on page 129
Local I/O modules that are installed in the uses local I/O modules.
CompactLogix 5380 system
Remote I/O modules accessible via the
EtherNet/IP network
Devices that are installed on an Dependent upon device type. Examples include: No Varies by product type and catalog number
EtherNet/IP network Remote I/O modules
Ethernet switches
Motion control devices, such as drives
HMI devices
(1) We strongly recommend that you use separate external power supplies for MOD power and SA power, respectively.

Power a CompactLogix 5380 System

The CompactLogix 5380 controller provides power to the system as follows:

System-side power that powers the CompactLogix 5380 system and lets
modules transfer data and execute logic. System-side power is also
known as Module (MOD) power.

System-side power is provided through the MOD Power connection.

Field-side power that powers some 5069 Compact I/O modules and
field-side devices that are connected to them. Field-side power is also
known as Sensor/Actuator (SA) power.

Field-side power is provided through the SA Power connection.

Connect external power supplies to removable terminal blocks (RTBs) to

provide MOD power and SA power.

Figure 2 - CompactLogix 5380 Controller Power Connectors

MOD Power Connection

SA Power Connection

16 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 CompactLogix 5380 System and Controllers Chapter 1

Power begins at the CompactLogix 5380 controller and passes across the 5069
Compact I/O module internal circuitry via power buses. The MOD power bus
and SA power bus are isolated from each other.

We strongly recommend that you use separate external power supplies

for MOD power and SA power, respectively. This practice can prevent
unintended consequences that can result if you use one supply.
IMPORTANT If you use separate external power supplies, the loss of power from one
external power supply does not affect the availability of power from the
other supply. For example, if separate external power supplies are used and
SA power is lost, MOD power remains available for the CompactLogix 5380
controller and 5069 Compact I/O modules.

For more information on how to connect MOD power and SA power, see the
CompactLogix 5380 Controllers Installation Instructions, publication
5069-IN013.

MOD Power

MOD power is a DC power source that is required to operate the

CompactLogix 5380 system. Remember the following:

Every module in the system draws current from the MOD power bus
and passes the remaining current to the next module.

MOD power lets 5069 Compact I/O modules transfer data and the
CompactLogix 5380 controller execute logic.

A CompactLogix 5380 system uses only one MOD power bus.

You must limit the MOD power source to 10 A, max, at 18...32V DC.

We recommend that you use an external power supply that is adequately

sized for the total MOD power bus current draw in the system.

For example, if the total MOD power current draw is 5 A, you can use a
MOD power supply that is limited to 5 A.

You must consider current inrush requirements when you calculate the
total MOD power bus current draw in the system.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 17

Chapter 1 CompactLogix 5380 System and Controllers

CompactLogix 5380 System MOD Power Bus

When the MOD power source is turned on, the following occurs.

1. The CompactLogix 5380 controller draws current from the MOD

power bus and passes the remaining current through to the next module.
2. The next module draws MOD power bus current and passes the
remaining current through to the next module.
3. The process continues until MOD power bus current needs are met for
all modules in the system.

For more information on the current that the 5069 Compact I/O modules
draw from the MOD power bus, see the 5069 Compact I/O Modules
Specifications Technical Data, publication 5069-TD001.

SA Power

SA power provides power to devices that are connected to some of the 5069
Compact I/O modules in the CompactLogix 5380 system.

Remember the following:

Some 5069 Compact I/O modules draw current from the SA power bus
and pass the remaining current to the next module.

Some 5069 Compact I/O modules only pass current along the SA
power bus to the next module.

A CompactLogix 5380 system can have more than one SA power bus.
You use a 5069-FPD field potential distributor to establish a new SA
power bus. The new SA power bus is isolated from the SA power bus to
its left in the system.

For more information on 5069-FPD field potential distributors,

see page 22.

18 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 CompactLogix 5380 System and Controllers Chapter 1

You must limit the SA power source to one of the following:

If you use DC voltage, you must limit the SA power source to 10 A,
max at 1832V DC.
If you use AC voltage, you must limit the SA power source to 10 A,
max at 18240V AC.

IMPORTANT If your system includes AC and DC modules that require SA power,

you must use a 5069-FPD field potential distributor to establish a
new SA power bus.
You install one set of the same module types, for example, DC
modules, to the first SA power bus and the other set, for example,
AC modules to the second SA power bus. That is, the SA power bus
to the right of the 5069-FPD field potential distributor.
The SA power source limitations described previously apply to each
isolated SA power bus separately.
For more information on 5069-FPD field potential distributors,
see page 22.

We recommend that you use an external power supply that is adequately

sized for the total SA power bus current draw in the system.

For example, if the total SA power current draw is 4 A, you can use an
SA power supply that is limited to 4 A.

You must consider current inrush requirements when you calculate the
total SA power bus current draw in the system.

Connections to an SA power bus use a shared common. All inputs that

draw current from an SA power bus to power field-side devices have a
return through circuitry to the SA - terminal on the SA power
connector.

IMPORTANT Each SA power bus has a shared common unique to that bus
because SA power buses are completely isolated from each other.
That is, the SA power bus that the controller establishes has a
shared common. If you use a 5069-FPD field potential distributor to
establish a new SA power bus in the system, that second bus has its
own shared common for module that draw current from it.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 19

Chapter 1 CompactLogix 5380 System and Controllers

5069 Compact I/O System SA Power Bus

When the SA power source is turned on, the following occurs.

1. The CompactLogix 5380 controller draws current from the SA power

bus and passes the remaining current through to the next module.

IMPORTANT The level of current that the controller draws from the SA power bus
is negligible. It draws 10 mA when DC power is used and 25 mA
when AC power is used.

2. The next module completes one of the following tasks.

If the module uses SA power, the module draws current from the SA
power bus and passes the remaining current through to the next
module.
If the module does not use SA power bus current, the module passes
the remaining current through to the next module.
3. The process continues until all SA power bus current needs are met for
the modules on the SA power bus.

Keep in mind, if your system includes AC and DC modules that require SA

power, you must use a 5069-FPD field potential distributor to establish a
separate SA power bus and separate the module types on the isolated SA power
buses. For more information, see page 19.

For more information on the current that the 5069 Compact I/O modules
draw from the SA power bus, see the 5069 Compact I/O Modules
Specifications Technical Data, publication 5069-TD001.

20 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 CompactLogix 5380 System and Controllers Chapter 1

Track SA Power Bus Current Draw

We recommend that you track the SA power bus current draw, max, per
module, and collectively for the CompactLogix 5380 system. You must make
sure that the 5069 Compact I/O modules installed on an SA power bus do not
consume more than 10 A. If so, you must establish another SA power bus.

Consider the following with this example:

The values in this example represent a worst-case calculation. That is, all
modules that draw SA power bus current, draw the maximum available
on the module.

Not all modules that are shown in Figure 3 use SA power bus current.
For example, the 5069-ARM and 5069-OW4I modules only pass SA
power bus current to the next module. Other modules that do not use
SA power bus current, but are not shown in the graphic, include the
5069-OB16, 5069-OB16F, and 5069-OX4I modules.

System SA power bus current, max, is calculated as each module draws

SA power bus current.

In Figure 3, after the 5069-IB16 module in slot 1 draws SA power bus

current, the system SA power bus current, max, is 138 mA. After the
5069-IB16 module in slot 2 draws SA power bus current, the system SA
power bus current draw is 266 mA. This process continues until the
system SA power bus current, max, is 1.222 A.

Figure 3 - CompactLogix 5380 System - Calculate SA Power Bus Current Draw

Continuous MOD Power Bus Limited to 10 A, Max

Continuous SA Power Bus Limited to 10 A, Max

SA Power Bus Current, Max, 10 mA 128 mA 128 mA 128 mA 128 mA 0 mA 0 mA 100 mA 100 mA 250 mA 250 mA
Per Module

System SA Power Bus Current, Max = 1.222 A

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 21

Chapter 1 CompactLogix 5380 System and Controllers

5069-FPD Field Potential Distributor Creates Additional SA Power Buses

The 5069-FPD field potential distributor lets you change the field-side power
distribution source for 5069 Compact I/O modules to the right of the field
potential distributor. The field potential distributor passes MOD power bus
signals through to the next module in the system.

You can use a 5069-FPD field potential distributor to add an SA power bus to a
CompactLogix 5380 system. The field potential distributor blocks the current
that passes across the SA power bus to the left of the field potential distributor.
At that point, the field potential distributor establishes a new SA power bus for
modules to the right.

The SA power bus that the field potential distributor establishes functions in
the same way as the SA power bus that a CompactLogix 5380 controller
establishes, as described on page 20.

Examples of system configurations that use multiple SA power buses include:

The modules in the system collectively draw more than 10 A of SA

power. That is, the maximum current that one SA power bus
can provide.

The modules in the system must be isolated according to module types,

such as digital I/O and analog I/O modules.

The modules in the system are isolated according to the type of

field-side device to which they are connected.

For example, you can separate modules that are connected to field-side
devices that use DC voltage from modules that are connected to field-
side devices that require AC voltage.

Figure 4 - 5069-FPD Field Potential Distributor

SA Power Connection

22 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 CompactLogix 5380 System and Controllers Chapter 1

Create a New SA Power Bus in a 5069 Compact I/O System

Figure 5 shows a CompactLogix 5380 system that uses a 5069-FPD field

potential distributor to create a second SA power bus. The separate SA power
bus is needed to isolate the digital I/O modules from the analog I/O modules.

Figure 5 - CompactLogix 5380 System - Create a New SA Power Bus

5069-FPD Field Potential Distributor

Breaks field-side power distribution to isolate 5069 Compact I/O digital and analog I/O modules.

Continuous MOD Power Bus Limited to 10 A, Max

SA Power Bus Limited to 10 A, Max SA Power Bus Limited to 10 A, Max

5069 Compact I/O Digital I/O Modules 5069 Compact I/O Analog I/O Modules

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 23

Chapter 1 CompactLogix 5380 System and Controllers

SA Power - Additional Notes

Remember the following:

We strongly recommend that you use separate power supplies for SA

power and MOD power connections.

The actual current in a 5069 Compact I/O system changes based on the
operating conditions at a given time.

For example, the SA power bus current draw on some modules is

different if all channels power field devices or half of the channels power
field devices.

Not all 5069 Compact I/O modules use SA power.

Some 5069 Compact I/O modules use field-side power but do not draw
it from a SA power bus. The modules receive field-side power from an
external power supply that is connected directly to the I/O module.

For example, the 5069-OB16 and 5069-OB16F modules use Local

Actuator (LA) terminals on the module RTB, that is, LA+ and LA
terminals for all module channels.

In this case, you can use the same external power supply that is
connected to the SA power RTB on the controller to the LA+ and LA
terminals.

IMPORTANT You must consider the current limit of an external power supply if
you use it to provide power to the SA power RTB on the controller
and the LA+ and LA terminals on a 5069-OB16 or 5069-OB16F
module.

24 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 CompactLogix 5380 System and Controllers Chapter 1

Secure Digital (SD) Card

The CompactLogix 5380 controllers ship with an SD card installed. The SD

card is also known as a non-volatile memory card. We recommend that you
leave the SD card installed.

A 1784-SD2 card ships with the controller. If you need additional SD cards, we
recommend that you use one that is available from Rockwell Automation. The
1784-SD1 (1 GB) and 1784-SD2 (2 GB) cards are available.

You can use third-party SD cards with the controller. You can use SD cards
with as much as 32 GB of memory. Keep in mind, Rockwell Automation does
not test the use of third-party SD cards with the controller. If you use an SD
card other than those cards that are available from Rockwell Automation,
unexpected results can occur. For example, you can experience data corruption
or data loss.

SD cards that are not provided by Rockwell Automation can have different
industrial, environmental, and certification ratings as those cards that are
available from Rockwell Automation. These cards can have difficulty with
survival in the same industrial environments as the industrially rated versions
available from Rockwell Automation.

Remember the following:

An SD card slot is on the front of the controller behind the door.

SD Card Slot

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 25

Chapter 1 CompactLogix 5380 System and Controllers

If the card is installed and a fault occurs, diagnostic data is automatically

written to the card. Diagnostic data helps the investigation and
correction of the fault cause.

The controller detects the presence of an SD card at power-up or if a

card is inserted during controller operation.

The SD card can store all configuration data that is stored in nonvolatile
memory, for example, the controller IP address.

The SD card can store the back-up program.

IMPORTANT We recommend that you back up your Logix Designer program to an

SD card on a regular basis.
If a major nonrecoverable fault occurs that removes the program
from the controller memory, the backup copy on the SD card can be
automatically restored to the controller and quickly resume normal
controller operation.
For more information on how to back up the program to the SD card,
see Store to the Secure Digital Card on page 101.

26 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Chapter 2

Use EtherNet/IP Modes

Topic Page
EtherNet/IP Modes 28
Configure the EtherNet/IP Modes 33
Change the EtherNet/IP Mode 41
Port Functionality in Dual-IP Mode 46
Controller IP Address and Firmware Updates 53

This chapter describes the EtherNet/IP modes that are available with the
CompactLogix 5380 controllers.

We recommend that you understand the EtherNet/IP modes before you

complete the tasks described in the rest of this publication.

IMPORTANT Dual-IP mode is first available with CompactLogix 5380 controller firmware
revision 29.011 or later.

We expect you to have a working knowledge of both modes before using a

CompactLogix 5380 controller. This chapter describes specific tasks in each
application that are related to the EtherNet/IP modes.

Other chapters in this publication describe how to perform more general tasks
in the Logix Designer application and RSLinx Classic software. If necessary,
read those chapters to understand better the tasks described in this chapter.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 27

Chapter 2 Use EtherNet/IP Modes

EtherNet/IP Modes With the Logix Designer application, version 29 or later, CompactLogix 5380
controllers support the following EtherNet/IP modes:
Dual-IP Mode
Linear/DLR Mode

Dual-IP Mode

Dual-IP mode lets you configure the controller embedded Ethernet ports to
connect to separate networks, that is, an enterprise-level Ethernet network and
a device-level network.

Each controller port requires its own network configurations in the controller.

Enterprise-level CompactLogix 5380 Controller

Network 5069 Compact I/O Modules

PanelView Plus 7 Terminal

F1 F9

F2 F10

F3 F11

F4 F12

F5 F13

F6 F14

F7 F15

F8 F16

Device-level Network

Stratix 2000 Switch

527

5069-AEN2TR Adapter PowerFlex 527 Drive

5069 Compact I/O Modules

28 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Use EtherNet/IP Modes Chapter 2

User Action Considerations

You must complete the following actions when you use Dual-IP mode:

You must assign an IP address and Subnet mask for each controller
Ethernet port. Subnet mask is also known as Network mask.

You must avoid overlapping IP address ranges when you configure the
controller Ethernet ports in Dual-IP mode.

For more information, see Overlapping IP Address Ranges.

You can use the methods that are described in Set the Controller IP
Address on page 66 to assign an IP address and Subnet/Network mask
to each Ethernet port.

Controller Functionality Considerations

Remember the following controller functions when you use Dual-IP mode:

The controller does not support the following functions:

TCP routing or switching between the two separate networks.
CIP bridging of Class 0 packets between the two separate networks.
CIP bridging of Class 1 packets between the two separate networks.

The controller supports the following functions:

CIP bridging for Class 3 CIP messages between the two separate
networks.
CIP bridging for Unconnected CIP messages between the two
separate networks.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 29

Chapter 2 Use EtherNet/IP Modes

Overlapping IP Address Ranges

IMPORTANT Overlapping IP address ranges only applies when the controller operates in
Dual-IP mode.
If you use the controller in Linear/DLR mode, you can skip this section and
proceed to Linear/DLR Mode on page 32.

The IP address and Subnet mask values that you assign to an Ethernet port
establish an IP address range for the port. The Subnet mask value is used to
establish the Network part of the IP address.

Overlapping IP address ranges occurs when any IP address from one range is
also present in the other IP address range. When a CompactLogix 5380
controller uses Dual-IP mode, the Network parts cannot overlap between the
Ethernet ports.

The following examples describe conditions in which IP address ranges do not

or do overlap.

EXAMPLE IP Address Ranges Do Not Overlap

The table describes port A1 and port A2 configurations that use IP address
ranges that do not overlap.
None of the IP addresses in either port IP address range exists in the IP
address range for the other port.

Port Number IP Address Subnet Mask/ IP Address Range

Network Mask (Low to High)
A1 192.168.1.5 255.255.255.0 192.168.1.1192.168.1.254
A2 192.168.2.1 255.255.255.0 192.168.2.1192.168.2.254

30 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Use EtherNet/IP Modes Chapter 2

EXAMPLE IP Address Ranges Do Overlap

The table describes port A1 and port A2 configurations that use IP address
ranges that do overlap.
All IP addresses in the port A2 IP address range are in the port A1 IP
address range.

Port Number IP Address Subnet Mask/ IP Address Range

Network Mask (Low to High)
A1 192.168.1.5 255.255.252.0 192.168.0.1192.168.3.254
A2 192.168.2.1 255.255.255.0 192.168.2.1192.168.2.254

The difference between the port configurations in the examples is the Subnet
Mask/Network Mask value for port A1.

In the first example, the value is 255.255.255.0. In the second example, the
value 255.255.252.0.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 31

Chapter 2 Use EtherNet/IP Modes

Linear/DLR Mode

When CompactLogix 5380 controllers operate in Linear/DLR mode, they can

only connect to one network. That is, there is only one network configuration.
The two physical ports allow the controller to connect to linear or DLR media
topologies if desired.

After firmware revision 29.011 or later is installed on a CompactLogix 5380

controller, the EtherNet/IP mode is automatically set to Dual-IP mode. You
must change the EtherNet/IP Mode to use Linear/DLR mode.

For more information on how to change the controller EtherNet/IP mode, see
Change the EtherNet/IP Mode on page 41.

The following graphic shows a CompactLogix 5380 controller that uses

Linear/DLR mode in a DLR network topology. Keep in mind that you can use
a CompactLogix 5380 controller that uses Linear/DLR mode in any
EtherNet/IP network topology.

CompactLogix 5380 Controller

5069 Compact I/O Modules

PanelView Plus 7 Terminal

F1 F9

F2 F10

F3 F11

F4 F12

F5 F13

F6 F14

F7 F15

F8 F16

Device-level Network

527

5069-AEN2TR Adapter PowerFlex 527 Drive

5069 Compact I/O Modules
h

32 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Use EtherNet/IP Modes Chapter 2

Configure the EtherNet/IP You can configure the EtherNet/IP modes with the following
software applications:
Modes
Logix Designer application, version 29.00.00 or later
RSLinx Classic software, version 3.81.00 or later

Configure Dual-IP Mode in the Logix Designer Application

In the Logix Designer application, the EtherNet/IP Mode is Dual-IP by

default and is displayed on the General tab in the Controller Properties dialog
box.

You set the IP address and Subnet Mask on the Internet Protocol tab.

TIP When you set the IP address and Subnet Mask, we recommend that you use
a USB connection from the workstation to the controller.

1. Confirm that the project is online.

2. Confirm that the controller is in one of the following modes:
Program mode
Remote Program mode
Remote Run mode

You cannot change the IP Address or Subnet Mask if the controller is in

Run mode.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 33

Chapter 2 Use EtherNet/IP Modes

3. Click the Internet Protocol tab.

4. From the Port pull-down menu, choose A1.
5. Click Manually configure IP settings.
6. Assign IP Address and Network Mask values.
7. Click Apply.

8. Repeat the previous steps, beginning at step 4

In step 4, make sure that you choose A2 from the Port pull-down menu.

34 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Use EtherNet/IP Modes Chapter 2

Configure Dual-IP Mode in RSLinx Classic Software

In RSLinx Classic software, the IP Mode for which the controller is configured
is displayed on the General tab in the Configuration dialog box.

For example, the following graphic displays that the controller is in

Dual-IP mode.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 35

Chapter 2 Use EtherNet/IP Modes

You set the IP Address and Network Mask on the Port Configuration tab.

TIP When you set the IP address and Subnet Mask, we recommend that you use
a USB connection from the workstation to the controller.

1. From the Port pull-down menu, choose A1.

2. Click Manually configure IP settings.
3. Assign IP Address and Network Mask values.
4. Click Apply.

5. Repeat the steps.

In step 1, make sure that you choose A2 from the Port pull-down menu.

36 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Use EtherNet/IP Modes Chapter 2

Configure Linear/DLR Mode in the Logix Designer Application

Remember, with firmware revision 29.011 or later, the EtherNet/IP Mode is

Dual-IP by default. You must change the mode to use Linear/DLR mode.

IMPORTANT For more information on how to change the controller EtherNet/IP mode,
see Change the EtherNet/IP Mode on page 41.

After you change the EtherNet/IP mode to Linear/DLR mode, the new mode
choice is displayed on the General tab in the Controller Properties dialog box.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 37

Chapter 2 Use EtherNet/IP Modes

You set the IP Address and Subnet Mask on the Internet Protocol tab.

1. Confirm that the project is online and the controller is in Program

mode, Remote Program mode, or Remote Run mode.

You cannot change the IP Address or Subnet Mask if the controller is in

Run mode.
2. Click the Internet Protocol tab.
3. Click Manually configure IP settings.
4. Assign IP Address and Network Mask values.
5. Click Apply.

38 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Use EtherNet/IP Modes Chapter 2

Configure Linear/DLR Mode in RSLinx Classic Software

Remember, with firmware revision 29.011 or later, the EtherNet/IP Mode is

Dual-IP by default. You must change the mode to use Linear/DLR mode.

IMPORTANT For more information on how to change the controller EtherNet/IP mode,
see Change the EtherNet/IP Mode on page 41.

The new mode choice is displayed on the General tab in the Controller
Properties dialog box.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 39

Chapter 2 Use EtherNet/IP Modes

You set the IP Address and Subnet Mask on the Internet Protocol tab.

1. Confirm that the project is online.

2. Click the Port Configuration tab.
3. Click Manually configure IP settings.
4. Assign IP Address and Network Mask values.

5. Click Apply.

40 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Use EtherNet/IP Modes Chapter 2

Change the EtherNet/IP You can change the EtherNet/IP mode in the Logix Designer application or
RSLinx Classic software.
Mode
IMPORTANT Exercise caution when you change the EtherNet/IP mode on your controller,
and consider the possible effects of the change.

The effects of changing the EtherNet/IP mode are different based on mode
change. Make sure that you are aware of them before changing the EtherNet/IP
mode.
Table 4 - Effect of Changing the EtherNet/IP Mode
EtherNet/IP Mode Change Effects
Dual-IP Mode to Linear/DLR Mode The port A2 IP address, network mask, default
gateway settings are applied to the A1/A2 port.
The MAC address of port A1 is applied to port A1/A2.
This scenario exists if the controller firmware is
upgraded to revision 29.011 or greater before an IP
address is set.
Attempts to change from Dual-IP mode to Linear/
DLR mode are only successful if the I/O configuration
section in at least one port does not contain
modules.
If the I/O configuration section for both ports include
modules, you cannot change the EtherNet/IP mode
from Dual-IP mode to Linear/DLR mode.
Linear/DLR Mode to Dual-IP Mode The port A1/A2 IP address, network mask, default
gateway settings are applied to port A2.
Other port A1/A2 settings, for example, DNS servers
and Domain Name, are lost.
The port A1/A2 MAC address is applied to port A1. A
separate MAC address is applied to Port A2.
Port A1 is DHCP-enabled.
The I/O Configuration section in the Logix Designer
application project is automatically assigned to
port A1.
You can change the I/O configuration in the Logix
Designer application project to assign it to port A2.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 41

Chapter 2 Use EtherNet/IP Modes

Change the EtherNet/IP Mode in the Logix Designer Application

IMPORTANT This example shows the EtherNet/IP mode change from Dual-IP mode to
Linear/DLR mode. The same tasks apply to change from Linear/DLR mode to
Dual-IP mode.

To change the EtherNet/IP mode in the Logix Designer application, complete

the following steps.

1. Confirm that the project is offline.

2. On the General tab of the Controller Properties dialog box, click
Change IP Mode.

3. From the New mode pull-down menu, choose the new mode and
click OK.

42 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Use EtherNet/IP Modes Chapter 2

4. Click OK on the Controller Properties dialog box.

5. Save the project.
6. Download the updated project to the controller.
7. When the following warning appears, read it carefully.

IMPORTANT Before you change the EtherNet/IP mode, make sure that you
understand the impact on your controller when you change
the mode.
For more information on the impact of changing the EtherNet/IP
mode, see Table 4 on page 41.

8. Click Yes to continue.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 43

Chapter 2 Use EtherNet/IP Modes

Change the EtherNet/IP Mode in RSLinx Classic Software

To change the EtherNet/IP mode in RSLinx Classic software, complete the

following steps.

1. Confirm that the controller is online and there is no project in the

controller.
2. Confirm that the controller is in one of the following modes:
Program mode
Remote Program mode
Remote Run mode

You cannot change the IP Address or Subnet Mask if the controller is in

Run mode.
3. Right-click the controller and choose Module Configuration.

44 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Use EtherNet/IP Modes Chapter 2

4. On the General tab of the Configuration dialog box, click Change

IP Mode.

5. From the New mode pull-down menu, choose the new mode and
click OK.

A warning appears.

IMPORTANT Before you change the EtherNet/IP mode, make sure that you
understand the impact on your controller when you change
the mode.
For more information on the impact of changing the EtherNet/IP
mode, see Table 4 on page 41.

6. Click Yes to continue.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 45

Chapter 2 Use EtherNet/IP Modes

Port Functionality in This section describes ways that the Ethernet ports on CompactLogix 5380
controllers, when used in Dual-IP mode, differ from Ethernet ports that are
Dual-IP Mode used in Linear/DLR mode.

The port names and purposes are the following:

Port A1 - Designated the enterprise port and used to interact with the
enterprise-level network.

Throughout this section, the term enterprise port refers to port A1.

Port A2 - Designated the device-level port and used to interact with the
device-level network

Throughout this section, the term device-level port refers to port A2.

Port IP Configuration

The controller Ethernet ports function differently in Dual-IP mode. As a

result, you configure more parameters on the enterprise port.

Parameters to Configure
Port Type IP Address Subnet Mask Gateway Address Host Name Domain Name Primary DNS Secondary DNS
Server Address Server Address
Enterprise port X X X X X X X
(A1)
Device-level X X X X
port (A2)

46 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Use EtherNet/IP Modes Chapter 2

Port Configuration in Logix Designer Application

Figure 6 - Differences Between Enterprise Port Configuration and Device-level Configuration
Enterprise port

Device-level port

Parameters are not configured for the device-level port.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 47

Chapter 2 Use EtherNet/IP Modes

IP Configuration in RSLinx Classic Software

Figure 7 - Differences Between Enterprise Port Configuration and Device-level Configuration
Enterprise port

Device-level port

Parameters are not configured for the device-level port.

48 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Use EtherNet/IP Modes Chapter 2

DNS Requests

Although you cannot configure the DNS servers or the domain name on a
device-level port, it can use DNS requests. The device-level port uses the DNS
servers and domain name from the enterprise port.

DNS Request Routing

DNS requests can be generated from port A1 or port A2.

DNS Request Generated From Port A1

If the DNS server address is in the local subnet of port A1, DNS
requests leave through A1 port.

If port A2 is enabled and the DNS server address is in local subnet of

port A2, DNS requests leave through A2 port.

If the DNS server address is outside of all local subnets, DNS requests
leave through A1 port towards port A1 default gateway.

DNS Request Generated From Port A2

If port A1 is enabled and the DNS server address is in local subnet of

port A1, DNS requests leave through A1 port.

If the DNS server address is in local subnet of port A2, DNS requests
leave through A2 port.

If port A1 is enabled and the DNS server address is outside of all local
subnets, DNS requests leave through A1 port towards port A1 default
gateway.

If port A1 is disabled and the DNS server address is outside of all local
subnets, DNS requests leave through A2 port towards port A2 default
gateway.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 49

Chapter 2 Use EtherNet/IP Modes

SMTP Server

The SMTP server is only available via the enterprise port. Therefore, emails
can only be sent on the enterprise port.

For more information on how to send emails via an Ethernet port, see the
EtherNet/IP Network Configuration User Manual, publication
ENET-UM001.

Use Socket Object

When the controller operates in Dual-IP mode and uses a Socket Object, you
can use an IP address with a Socket_Create service type. By default this IP
address is INADDR_ANY.

Remember the following:

If you use INADDR_ANY, IP communication that the Socket Object

instance initiates follows the same routing rules as DNS request routing
rules described in DNS Request Routing on page 49.

If you use the IP address of port A1 instead of INADDR_ANY, IP

packets can only go to the port A1 subnet or via its default gateway.

If you use the IP address of port A2 instead of INADDR_ANY, IP

packets can go only to port A2 subnet or via its default gateway.

If you use an IP address other than the port A1 or A2 IP addresses or

INADDR_ANY, the Create_Socket_Service request is rejected.

Send Message Instructions

You can send Message (MSG) instructions out the enterprise port or the
device-level port. The only difference between the MSG instruction
configurations is the path.

When you configure a MSG instruction on a CompactLogix 5380 controller

that operates in Dual-IP mode, use the following paths:
Enterprise port (Port A1) - 3
Device-level port (Port A2) - 4

If the controller operates in Linear/DLR mode, the path is 2.

For more information on how to use MSG instructions, see the

Logix5000 Controllers General Instructions Reference Manual,
publication 1756-RM003.

50 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Use EtherNet/IP Modes Chapter 2

Software Display Differences Table 5 shows differences in the Logix Designer application when the
controller uses Dual-IP mode or Linear/DLR mode.
for EtherNet/IP Modes

Table 5 - EtherNet/IP Mode Display Differences in the Logix Designer Application

EtherNet/IP Mode
Section in Dual-IP Mode Linear/DLR Mode
Application
I/O Configuration
Tree in Controller
Organizer

General Tab on
Controller
Properties Dialog
Box

Internet Protocol on
Controller
Properties Dialog
Box

The Controller Properties dialog box also provides a Network tab in the Logix
Designer application when the controller uses Linear/DLR mode. The
Network tab is not available when the controller uses Dual-IP mode.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 51

Chapter 2 Use EtherNet/IP Modes

Table 6 shows differences in RSLinx Classic software when the controller uses
Dual-IP mode or Linear/DLR mode.
Table 6 - EtherNet/IP Mode Display Differences in the RSLinx Classic Software
EtherNet/IP Mode
Section in Dual-IP Mode Linear/DLR Mode
Software
General Tab

Port Configuration
Tab

The Configuration dialog box also provides a Network tab in RSLinx Classic
software when the controller uses Linear/DLR mode. The Network tab is not
available when the controller uses Dual-IP mode.

52 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Use EtherNet/IP Modes Chapter 2

Controller IP Address and CompactLogix 5380 controllers require an IP address and updated firmware
revision to operate properly. You must be aware of the following before you set
Firmware Updates the IP address and update the controller firmware:

Controller state before you make changes

Firmware revision to which you are updating the controller

Order in which you set the IP address and update the firmware revision

Controller State Description Firmware Revision Task Completion Order Result of Completing Tasks in Order Indicated
Before Making of Update/Change
Changes
Out-of-box No IP address set Revision 29.011 or 1. Change the EtherNet/IP mode The controller EtherNet/IP mode is automatically set to Dual-IP
Unique MAC later from Dual-IP mode to Linear/ mode.
addresses are used DLR mode. The port A1/A2 IP address, network mask, default gateway
for port A1 and For more information, see settings are applied to port A2.
port A2, Change the EtherNet/IP Mode Other port A1/A2 settings, for example, DNS servers and
respectively on page 41. Domain Name, are lost.
2. Set IP address on port A1/A2.
Each port on the 3. Install controller firmware. The port A1/A2 MAC address is applied to port A1, and a
controller is separate MAC address is applied to Port A2.
DHCP-enabled
You must set the IP address configuration
Firmware revision
1.xxx 1. Install controller firmware. The controller EtherNet/IP mode remains set to Dual-IP mode
2. Set IP addresses on port A1 and after the firmware is installed.
port A2. The controller EtherNet/IP mode is set to Dual-IP mode when it
is in the out-of-box state.
A unique MAC address is assigned to each controller port.
You must set the IP address and related parameters for port A1
(enterprise port) and port A2 (device-level port).
No IP address is set Revision 28.xxx 1. Set IP address on port A1/A2. The controller EtherNet/IP mode is automatically set to Linear/
One MAC address is IMPORTANT: Only the 2. Install controller firmware. DLR mode.
used for port A1/A2 5069-L320ER and The IP address settings on port A1/A2 remain the same.
5069-L340ERM 1. Install controller firmware.
Port A1/A2 is controllers support 2. Set IP address on port A1/A2.
DHCP-enabled revision 28.xxx.
Firmware revision
1.xxx

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 53

Chapter 2 Use EtherNet/IP Modes

Controller State Description Firmware Revision Task Completion Order Result of Completing Tasks in Order Indicated
Before Making of Update/Change
Changes
Operating IP address set on Revision 29.011 or Update controller firmware EtherNet/IP mode changes to Dual-IP mode.
port A1/A2 later The port A1/A2 IP address, network mask, default gateway
Firmware revision settings are applied to port A2.
28.xxx is installed
Other port A1/A2 settings, for example, DNS servers and
Domain Name, are lost.
The port A1/A2 MAC address is applied to port A1. A separate
MAC address is applied to Port A2.
The I/O Configuration section in the Logix Designer application
project is automatically assigned to port A1.
You can change the I/O configuration in the Logix Designer
application project to assign it to port A2.
If necessary, you can change to DLR/Linear mode after the
firmware revision update. For more information, see Change
the EtherNet/IP Mode on page 41.
Controller operates Downgrade to revision Downgrade controller firmware EtherNet/IP mode remains in Linear/DLR mode
in Linear/DLR mode 28.xxx IP address settings remain the same
IP address set on IMPORTANT: You can
port A1/A2 perform this download
Firmware revision only on the 5069-
29.011 or later is L320ER and 5069-
installed L340ERM controllers.
Controller operates Downgrade controller firmware EtherNet/IP mode automatically changes from Dual-IP mode to
in Dual-IP mode Linear/DLR mode
IP addresses are set After the change is made, the port A2 Internet Protocol
on port A1 and configuration is applied to the A1/A2 port.
port A2
Firmware revision
29.011 or later is
installed

54 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Chapter 3

Use the Communication Drivers in

RSLinx Classic Software

Topic Page
Configure the EtherNet/IP Driver in RSLinx Classic Software 57
Configure the Ethernet Devices Drivers in RSLinx Classic Software 59
Use the USB Communication Driver in RSLinx Classic Software 61

To use RSLinx Classic software with your CompactLogix 5380 controller,

you must use a communication driver that corresponds to the cable
connections.

For example, before you can connect to the controller via an Ethernet cable,
you must create an EtherNet/IP driver in RSLinx Classic software.

A communication driver is required to complete the following tasks:

Upload and download Logix Designer application projects

Update controller firmware

Set or change the controller IP address

Collect controller data for electronic operator interfaces over an

Ethernet network

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 55

Chapter 3 Use the Communication Drivers in RSLinx Classic Software

Remember the following when you use the RSLinx Classic software
communication drivers:
EtherNet/IP driver:
Supports runtime communications
Requires that the workstation and the controller are configured
Supports communications over longer distances when compared to
the USB driver

Ethernet devices driver:

Lets you download a Logix Designer application project to a
controller that is on an Ethernet network when your controller is not
directly connected to that network
Requires that you configure the IP addresses to which the software
browses and, therefore, the devices with which the controller
communicates

USB driver:
Convenient method to connect to an unconfigured controller and
configure the Ethernet port
Convenient method to connect to a controller when the Ethernet
port configuration is unknown
Convenient method to update the controller firmware
Not intended for runtime connections; it is a temporary-use only
connection with a limited cabling distance

56 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Use the Communication Drivers in RSLinx Classic Software Chapter 3

Configure the EtherNet/IP Before you add an Ethernet driver, confirm that these conditions exist:
Driver in RSLinx Classic The workstation is properly connected to the EtherNet/IP network.
Software
The workstation IP address and other network parameters are
configured correctly.

To configure the EtherNet/IP driver, complete the following steps.

1. From the Communications pull-down menu, choose Configure Drivers.

The Configure Drivers dialog box appears.

2. From the Available Driver Types pull-dowlnn menu, choose
EtherNet/IP Driver.
3. Click Add New.

The Add New RSLinx Driver dialog box appears.

4. You can use the default name for the new drive or type a new name, and
click OK.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 57

Chapter 3 Use the Communication Drivers in RSLinx Classic Software

The Configure driver dialog box appears.

5. Click Browse Local Subnet.

TIP To view devices on another subnet or VLAN from the workstation running
RSLinx Classic software, click Browse Remote Subnet.

6. Select the desired driver, and click OK.

The new driver is available on the Configure Drivers dialog box.

58 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Use the Communication Drivers in RSLinx Classic Software Chapter 3

Configure the Ethernet The following conditions must exist to configure an Ethernet devices driver:
Devices Drivers in RSLinx The workstation is connected to a different Ethernet network than the
Classic Software target controller.

The IP address and other network parameters are correctly configured

on the workstation.

To configure the Ethernet devices driver, complete the following steps.

1. From the Communications pull-down menu, choose Configure Drivers.

The Configure Drivers dialog box appears.

2. From the Available Driver Types pull-down menu, choose
Ethernet devices.
3. Click Add New.

The Add New RSLinx Driver dialog box appears.

4. You can use the default name for the new drive or type a new name, and
click OK.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 59

Chapter 3 Use the Communication Drivers in RSLinx Classic Software

The Configure driver dialog box appears.

5. On the Configure driver dialog box, enter a host name for each station
to which RSLinx Classic software browses.

The host name is the IP address for the device.

6. Click Add New to add stations and give each a host name.
7. When you are finished adding stations, click OK.
8. On the Configure Drivers dialog box, click Close.

60 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Use the Communication Drivers in RSLinx Classic Software Chapter 3

Use the USB In RSLinx Classic software, version 3.80.00 or later, a USB driver
automatically appears in the software when you connect the USB cable from
Communication Driver in your workstation to the controller.
RSLinx Classic Software
The USB driver can take a moment to appear in RSLinx Classic software.

IMPORTANT EtherNet/IP drivers remain visible in RSLinx Classic software after they are
configured regardless of whether they are in use or not.
A USB driver appears in RSLinx Classic software only when a USB cable is
connected between the workstation and the controller.
Once the cable is disconnected, the driver disappears from RSLinx
Classic software.

If you use the RSLinx Classic software, version 3.80.00 or later, and a USB
driver does not appear automatically, you can complete the following steps.

1. Confirm that the USB cable is connected to the controller.

The Found New Hardware Wizard dialog box appears.

2. Click any of the Windows Update connection options and click Next.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 61

Chapter 3 Use the Communication Drivers in RSLinx Classic Software

3. Click Install the software automatically (Recommended) and

click Next.
The software is installed.

4. Click Finish to configure your USB driver.

5. From the Communications pull-down menu, choose RSWho.

The USB Port Driver appears.

62 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Chapter 4

Start to Use the Controller

Topic Page
Out-Of-Box State 63
Connect to the Controller 64
Set the Controller IP Address 66
Update Controller Firmware 80
Create a Logix Designer Application Project 89
Change Controller Configuration 91
Go Online with the Controller 92
Download a Project to the Controller 94
Upload from the Controller 96
Choose the Controller Operation Mode 98

This chapter describes how to begin using the CompactLogix 5380 controller
during its initial installation.

Out-Of-Box State The following conditions apply when the CompactLogix 5380 controller is in
the out-of-box state:

EtherNet/IP mode is Dual-IP mode

For more information on the EtherNet/IP mode options, see Chapter 2,

Use EtherNet/IP Modes on page 27.

Does not have any IP addresses assigned.

To assign IP addresses, complete the steps described in Set the

Controller IP Address on page 66.

Uses firmware revision 1.x. You must update the firmware revision
before you can use it in a Logix Designer application project.

To update controller the firmware revision, see Update Controller

Firmware on page 80.

Controller does not contain a controller project.

To create a project, see Create a Logix Designer Application Project on

page 89.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 63

Chapter 4 Start to Use the Controller

Connect to the Controller Before you can use the CompactLogix 5380 controller, you must connect the
desired cable to the controller. The following controllers connections
are available:

Connect an Ethernet Cable on page 64

Connect a USB Cable on page 65

Connect an Ethernet Cable

WARNING: If you connect or disconnect the communications cable with

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.

If you are connecting the controller directly to an EtherNet/IP network,

connect a CAT 5e or CAT 6 Ethernet cable with an RJ45 connector to a
controller Ethernet port.

For information on how to select the proper cable, see Guidance for Selecting
Cables for EtherNet/IP Networks, publication ENET-WP007-EN-P.

64 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Start to Use the Controller Chapter 4

Connect a USB Cable

Use the USB connection to update firmware and download programs.

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.

WARNING: Do not use the USB port in hazardous locations.

Figure 8 - USB Connection

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 65

Chapter 4 Start to Use the Controller

Set the Controller IP Address You must set the IP address on a CompactLogix 5380 controller for the
controller to operate on an EtherNet/IP network. The controllers ship without
an IP address.

When the controller is in the out-of-the-box condition, the following apply

with respect to IP addresses:

The controller embedded Ethernet ports are configured to obtain an IP

address via a DHCP server.

If there is no DHCP server or the DHCP server is not configured to set

the IP address, you must set the IP Address manually.

The controller is configured so that you must set the IP address each
time that power is cycled.

You can configure your controller so that you are not required to set an
IP address each time that power is cycled.

IMPORTANT This section provides a general description of how to set an IP address.

The EtherNet/IP mode in which a CompactLogix 5380 controller operates
affects the setting and use of IP addresses on the controller. For example, if
the controller operates in Dual-IP mode, you must set an IP address for each
controller Ethernet port. That is, you must complete the steps described in
this section twiceonce for each port.
For more information on how the EtherNet/IP modes affect the controller IP
address, see Chapter 2, Use EtherNet/IP Modes on page 27.

You can use these tools to set the IP address:

BOOTP-DHCP tool
DHCP server
RSLinx Classic software
Logix Designer application
SD card

Each tool has connection requirements to set the IP address 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.

66 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Start to Use the Controller Chapter 4

To operate on an EtherNet/IP network, you must define these parameters.

EtherNet/IP Network Parameter Description

IP address The IP address uniquely identifies the module. The IP address is in the form xxx.xxx.xxx.xxx where each xxx is a number from
000255.
There are some reserved values that you cannot use as the first octet in the address. These numbers are examples of values you
cannot use:
001.xxx.xxx.xxx
127.xxx.xxx.xxx
223 to 255.xxx.xxx.xxx
The specific reserved values that cannot be used vary according to the conditions of each application. The previous values are only
examples of reserved values.
Subnet mask The subnet mask divides IP addresses into a network address and a host address. It defines whether the controller exchanges
Ethernet packets directly with another device, or whether it routes packets through the Gateway. This field is set to 0.0.0.0 by
default.
Gateway A gateway connects individual physical networks into a system of networks. When a node communicates with a node on another
network, a gateway transfers the data between the two networks. This field is set to 0.0.0.0 by default.

If you use Domain Name System (DNS) addressing, or reference the controller
via host name in MSG instructions, define these parameters.
Table 7 - EtherNet/IP Network Parameters for DNS Addressing
EtherNet/IP Network Parameter Description
Host name A host name is part of a text address that identifies the host for a module. The full text address of a module is
host_name.domain_name.
Domain name A domain name is part of a text address that identifies the domain in which the module resides. The full text address of a module is
host_name.domain_name. The domain name has a 48-character limit.
If you specify a DNS server, you must type a domain name. Also, if you send email from the module, some mail relay servers require a
domain name during the initial handshake of the SMTP session.
Primary DNS server address An address that identifies any DNS servers that are used in the network. You must have a DNS server if you specified a domain name
or a host name in the module configuration. The DNS server converts the domain name or host name to an IP address that is used by
Secondary DNS server address the network.
For more information on DNS addressing, see page 74.

Check with your Ethernet network administrator to determine if you must

specify these parameters.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 67

Chapter 4 Start to Use the Controller

Use the BOOTP-DHCP Tool to Set the Controller IP Address

CompactLogix 5380 controllers are DHCP-enabled by default.

The BOOTP-DHCP tool is a standalone tool that you can use to set an IP
address. When used, the BOOTP-DHCP tool sets an IP address and other
Transport Control Protocol (TCP) parameters.

The BOOTP-DHCP tool is installed automatically when you install

RSLinx Classic software or the Logix Designer application on your computer.

Access the BOOTP-DHCP tool from one of these locations:

Programs > Rockwell Software > BOOTP-DHCP Tool

Tools directory on the Studio 5000 environment installation CD

IMPORTANT Before you start the BOOTP-DHCP tool, make sure that you have the
module hardware (MAC) address.
The MAC address scrolls across the controller status on the front of
the controller. The address uses a format similar to the following:
00-00-BC-14-55-35

To set the IP address with a BOOTP-DHCP tool, complete these steps.

1. Connect your workstation to the Ethernet network where the

controller resides.
2. Start the BOOTP-DHCP tool.

68 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Start to Use the Controller Chapter 4

The MAC address of the controller appears in the Request

History window.
3. Select the appropriate controller and click Add to Relation List.

The New Entry dialog box appears.

4. Type an IP address, Hostname, and Description for the module.

Hostname and Description are optional.

5. Click OK.

IMPORTANT If your controller is operating in Dual-IP mode, you must set an IP address for
each controller Ethernet port. In this case, set the IP address for the second
port, beginning at step 3.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 69

Chapter 4 Start to Use the Controller

Disable BOOTP/DHCP

After an IP address is assigned to the controller, we recommend that you

disable BOOTP/DHCP.

Click Disable BOOTP/DHCP.

The module now uses the assigned configuration and does not issue a BOOTP
or DHCP request.

IMPORTANT Remember the following:

If you do not click Disable BOOTP/DHCP, on future power cycles,
the current IP configuration is cleared and the controller sends
DHCP requests again.
If you click Disable BOOTP/DHCP and it does not disable
BOOTP/DHCP, you can use RSLinx Classic software to disable
BOOTP/DHCP.
For more information on how to use RSLinx Classic software to
disable BOOTP/DHCP, see page 71.

70 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Start to Use the Controller Chapter 4

To disable BOOTP/DHCP from RSLinx Classic software, complete the

following steps.

1. Start RSLinx Classic software.

After several seconds, an RSWho dialog box appears.

2. If no RSWho dialog box appears, from the Communications pull-down
menu, choose RSWho.

3. Navigate to the controller.

You can access the controller via the USB or an EtherNet/IP driver.
4. Right-click on the controller and choose Module Configuration.

5. Click the Port Configuration tab.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 71

Chapter 4 Start to Use the Controller

6. From the Network Configuration Type, click Static to disable

BOOTP/DHCP.

7. Click OK.

Use the DHCP Server to Set the Controller IP Address

Because the CompactLogix 5380 controllers are DHCP-enabled when they

are in the out-of-box condition, you can use a DHCP server to set the
IP address.

The DHCP server automatically assigns IP addresses to client stations logging

on to a TCP/IP network. DHCP is based on BOOTP and maintains some
backward compatibility.

ATTENTION: The controller must be assigned a fixed network address. The IP

address of this controller must not be dynamically provided.
Failure to observe this precaution can result in unintended machine motion or
loss of process control.

72 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Start to Use the Controller Chapter 4

Duplicate IP Address Detection

The controller verifies that its IP address does not match any other network
device IP address when you perform either of these tasks:

Connect the controller to a EtherNet/IP network.

Change the controller IP address.

If the controller IP address matches that of another device on the network, the
controller EtherNet/IP port transitions to Conflict mode. In Conflict mode,
these conditions exist:

Network (NET) status indicator is solid red.

The 4-character display indicates the conflict.

The display scrolls: <IP_address_of_this_module> Duplicate IP

<Mac_address_of_duplicate_node_detected>

For example: 192.168.1.1 Duplicate IP - 00:00:BC:02:34:B4

Duplicate IP Address Resolution

When two devices on a network have IP addresses that conflict, the resolution
depends on the conditions in which the duplication is detected. This table
describes how duplicate IP addresses are resolved.

Duplicate IP Address Detection Conditions Resolution Process

Both devices support duplicate IP address detection. 1. The device that began operation first uses the IP address and continues to operate without interruption.
Second device is added to the network after the first 2. The device that begins operation second detects the duplication and enters Conflict mode.
device is operating on the network. To assign a new IP address to the controller and leave Conflict mode, see Use the BOOTP-DHCP Tool to Set the
Controller IP Address on page 68.
Both devices support duplicate IP address detection. Both EtherNet/IP devices enter Conflict mode.
Both devices were powered up at approximately the To resolve this conflict, follow these steps:
same time. a. Assign a new IP address to the controller. For more information, see Use the BOOTP-DHCP Tool to Set the
Controller IP Address on page 68.
b. Cycle power to the other device.
One device supports duplicate IP address detection and a 1. Regardless of which device obtained the IP address first, the device that does not support IP address detection uses
second device does not. the IP address and continues to operate without interruption.
2. The device that supports duplicate IP address detection detects the duplication and enters Conflict mode.
To assign a new IP address to the controller and leave Conflict mode, see Use the BOOTP-DHCP Tool to Set the
Controller IP Address on page 68.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 73

Chapter 4 Start to Use the Controller

DNS Addressing

You can also use DNS addressing to specify a host name for a controller, a
domain name, and DNS servers. DNS addressing makes it possible to
configure similar network structures and IP address sequences under different
domains.

DNS addressing is necessary only if you refer to the controller by host name,
such as in path descriptions in MSG instructions.

To use DNS addressing, follow these steps.

1. Assign a host name to the controller.

A network administrator can assign a host name. Valid host names must
be IEC-1131-3 compliant.
2. Configure the controller parameters.
3. Configure the IP address, subnet mask, gateway address, a host name for
the controller, domain name, and primary/secondary DNS server
addresses.

In the DNS server, the host name must match the IP address of the
controller.
4. In the Logix Designer application, add the controller to the I/O
configuration tree in the Logix Designer application project for
another controller.

IMPORTANT If a child module resides in the same domain as its parent module,
type the host name. If the domain of the child module differs from
the domain of its parent module, type the host name and the
domain name (hostname.domainname)

IMPORTANT You can also use DNS addressing in a module profile in the I/O controller tree
or in a message path. If the domain name of the destination module differs
from the domain name of the source module, use a fully qualified DNS name
(hostname.domainname).

74 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Start to Use the Controller Chapter 4

Use RSLinx Classic Software to Set the Controller IP Address

Complete these steps to set the IP address of the controller with

RSLinx Classic software.

1. Confirm that your computer is connected to the controller via a

USB cable.
2. Start the RSLinx Classic software.

After several seconds, an RSWho dialog box appears.

3. If the RSWho dialog box does not appear, from the Communications
pull-down menu, choose RSWho.

4. Right-click the controller and choose Module Configuration.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 75

Chapter 4 Start to Use the Controller

5. Click the Port Configuration tab on the Module Configuration

dialog box.
6. In the Network Configuration Type section, click Manually configure
IP settings for the port.
7. Assign the port configuration parameters and click OK.

76 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Start to Use the Controller Chapter 4

Use the Logix Designer Application to Set the Controller IP Address

IMPORTANT You must install firmware on your controller before you can use the Logix
Designer application to set the controller IP address.
If you install controller firmware revision 29.011 or later, the controller is
configured to use Dual-IP mode by default.

Complete these steps to set the controller IP address with the Logix Designer
application.

1. Confirm that your computer is connected to the controller via a

USB cable.
2. Confirm the controller is offline.
3. Start the Logix Designer application.
4. Create a new project.
5. Use RSWho to browse to the controller.

6. Select the controller and click Go Online.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 77

Chapter 4 Start to Use the Controller

7. When the Connected To Go Online dialog box appears,

click Download.

8. When the Download dialog box appears, click Download.

78 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Start to Use the Controller Chapter 4

9. Right-click the project name in the Controller Organizer and

choose Properties.

10. On the Internet Protocol tab, choose the port from the Port pull-down
menu.
11. Click Manually configure IP settings, enter the necessary values, and
click Apply.

IMPORTANT If your controller uses firmware revision 29.011 or later, as shown in this
example, the EtherNet/IP mode is Dual-IP by default after the firmware
update.
In this case, you must set an IP address for each controller port. To do so,
choose the port that does not have an IP address and repeat step 11.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 79

Chapter 4 Start to Use the Controller

Use a Secure Digital Card to Set the Controller IP Address

You can use an SD card to set the controller IP address. The SD card can set the
IP address when it loads a project onto the controller.

For more information on how to use an SD card, see Use the Secure
Digital Card on page 101.

Update Controller Firmware You can use the following tools to update the controller firmware:

ControlFLASH software

AutoFlash feature of the Logix Designer application

To update the controller firmware, complete the following tasks:

Determine Required Controller Firmware
Obtain Controller Firmware
Use ControlFLASH Software to Update Firmware
Use AutoFlash to Update Firmware

IMPORTANT This section provides a general description of how to update

controller firmware.
With CompactLogix 5380 controllers, firmware changes can have different
effects on the controller based on system conditions when the change is
made, particularly with respect to the EtherNet/IP mode that is used.
For example, if you update the controller from firmware revision 1.xxx to
firmware revision 29.011 or later, the EtherNet/IP mode is automatically set
to Dual-IP mode. However, if you upgrade the controller from firmware
revision 28.xxx to firmware revision 29.011 or later, the IP mode remains
Linear/DLR.
For more information on how controller firmware revision changes can
affect your CompactLogix 5380 controller configuration with respect to
EtherNet/IP mode use, see Chapter 2, Use EtherNet/IP Modes on page 27.

80 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Start to Use the Controller Chapter 4

Determine Required Controller Firmware

The firmware major revision level must match the software major version level.
For example, if the controller firmware revision is 28.xxx, you must use the
Logix Designer application, version 28.

Obtain Controller Firmware

You can obtain controller firmware in the following ways:

Firmware is packaged as part of the Studio 5000 Logix Designer

application installation.

IMPORTANT The firmware that is packaged with the software installation is the
initial release of the controller firmware. Subsequent firmware
revisions can be released.
We recommend that you check the Product Compatibility and
Download Center (PCDC) to determine if later revisions of the
controller firmware are available. For more information, see the
next bullet.

Download firmware, associated files, and access product release notes

from the PCDC at:

http://www.rockwellautomation.com/rockwellautomation/support/
pcdc.page

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 81

Chapter 4 Start to Use the Controller

Use ControlFLASH Software to Update Firmware

IMPORTANT You must use ControlFLASH software, version 13.00.00 or later, with
CompactLogix 5380 controllers.
The software is available as follows:
Part of Studio 5000 Logix Designer application installation process
Standalone download from the Product Compatibility and
Download Center at: http://www.rockwellautomation.com/
rockwellautomation/support/pcdc.page

Access the ControlFLASH software via: Programs > FLASH Programming

Tool > ControlFLASH

ATTENTION: If the Secure Digital (SD) card is locked and set to load on
power-up, this update can be overwritten by firmware on the SD card.
For more information on how to use SD cards, see Use the Secure Digital Card on
page 101.

1. Verify the following:

The network connection is made.
The network driver has been configured in RSLinx Classic software.
The controller is in Remote Program or Program mode and all major
recoverable faults are cleared.
2. Start the software.

82 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Start to Use the Controller Chapter 4

3. On the ControlFLASH dialog, click Next.

4. Enter the catalog number of the controller, select it, and click Next.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 83

Chapter 4 Start to Use the Controller

5. Expand the network driver to find the controller.

6. Select the controller and click OK.

7. Select the firmware revision and click Next.

TIP If you experience a Script File Error after you select the firmware revision
number, as shown, there can be a problem with your firmware files.

We recommend that you use the latest version of the ControlFLASH

software. If you are not, first upgrade to the latest version.
If the issue persists, go to http://www.rockwellautomation.com/support/
and download the firmware revision you are trying to update. Replace the
firmware revision that you have previously installed with that posted on the
Technical Support website.
.

84 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Start to Use the Controller Chapter 4

8. On the Summary Screen, click Finish.

9. When a confirmation dialog box appears, click Yes.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 85

Chapter 4 Start to Use the Controller

Before the firmware update begins, the following dialog box appears.
Take the required action for your application. In this example, the
upgrade continues when OK is clicked.

WARNING: Let the firmware update complete before you cycle power or
otherwise interrupt the update.

IMPORTANT If the ControlFLASH update of the controller is interrupted, the

CompactLogix 5380 controllers revert to boot firmware, that is,
revision 1.xxx.

When the update is complete, the Update Status dialog box indicates
that the update is complete.
10. Click OK.

11. Close ControlFLASH software.

86 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Start to Use the Controller Chapter 4

Use AutoFlash to Update Firmware

To update the controller firmware with the AutoFlash feature, complete the
following steps.

ATTENTION: If the Secure Digital Card is locked and set to load on power-up,
this update can be overwritten by firmware on the SD card.

1. Verify the following:

The network connection is made.
The network driver has been configured in RSLinx Classic software.
The controller is in Remote Program or Program mode and all major
recoverable faults are cleared.
2. Use the Logix Designer application to create a controller project.

For more information, see Create a Logix Designer Application Project

on page 89.
3. On the Logix Designer Path bar, click Who Active.

4. On the Who Active dialog box, select the controller under the
communication driver you want to use, and click Update Firmware.
.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 87

Chapter 4 Start to Use the Controller

5. On the Choose Firmware Revision dialog, browse to the location of the

firmware files (C:\Program Files (x86)\ControlFlash).
6. Select the firmware revision, and click Update.
7. On the Confirmation dialog, click Yes.

8. On the ControlFlash Attention dialog, click OK.

The firmware update begins. Let the update complete without

interruption.
When the firmware update is complete, the progress dialog closes.

88 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Start to Use the Controller Chapter 4

Create a Logix Designer To create a Logix Designer application project, complete the following steps.
Application Project 1. Start the application.

The Logix Designer application is part of the

Studio 5000 environment.

2. Click New Project.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 89

Chapter 4 Start to Use the Controller

3. On the New Project dialog box, complete the following steps:

a. Select the controller.
b. Name the project.
c. Browse to the location where the project file is created.
d. Click Next.

4. Select the following:

Revision
Security Authority (optional)
Secure With (only available if Security Authority is used)
5. Click Finish.

90 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Start to Use the Controller Chapter 4

Change Controller After the project is created, you can change some configuration parameters on
the Controller Properties dialog box while the controller is offline.
Configuration
Examples of configurable parameter that you can change offline include the
following:
EtherNet/IP Mode on the General tab
Enable Time Synchronization on the Date/Time tab
Execution Control on the SFC Execution tab

To change the controller configuration while the project is offline, complete

these steps:

1. Right-click the project name in the Controller Organizer and

choose Properties.

2. To change controller configuration, click the tabs to change the desired

configurable parameters.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 91

Chapter 4 Start to Use the Controller

Go Online with the Controller To go online with the controller, you must first specify a communication path
in the Logix Designer application.

TIP In this section, an Ethernet port is the communication path. You can also use
the USB port.

1. Open or create a Logix Designer application project.

2. In Logix Designer, click Who Active.

3. Expand the communication path and select the controller.

4. If you want to store the path in the project file, click Set Project Path.

92 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Start to Use the Controller Chapter 4

If you store the project path in the project, you do not have to choose the
path each time you go online.

TIP You can also select a recent communications path and go online or apply it
to your project.

When the list of recent paths appears, choose the desired path and click
Go Online.

5. After choosing the communication path, click Go Online in the

Who Active dialog box.

IMPORTANT If you are going online with the controller for the first time, you
must download the project. In this case, click Download at the On
the Connected To Go Online and Download dialog boxes
successively.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 93

Chapter 4 Start to Use the Controller

Download a Project to When you download a project to the controller, it copies the project from the
Logix Designer application onto the controller. You can download a project in
the Controller two ways:
Use the Who Active Dialog Box to Download on page 94
Use the Controller Status Menu to Download on page 95

Use the Who Active Dialog Box to Download

You can use the features of the Who Active dialog box to download to the
controller after you have set the communication path. Complete these steps to
download to the controller.

1. In the Who Active dialog box, choose the communication path and
click Download.

94 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Start to Use the Controller Chapter 4

2. Click Download after reading the warnings in the Download

dialog box.

Use the Controller Status Menu to Download

After you establish a communication path in the Logix Designer application,

you can use the Controller Status menu to download to the controller.

From the Controller Status menu, choose Download.

TIP After the download completes, the project name appears on the scrolling
status display of the controller.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 95

Chapter 4 Start to Use the Controller

Upload from the Controller When you upload a project from the controller, it copies the project from the
controller to the Logix Designer application. To upload a project, use one of
these methods:
Use the Who Active Dialog Box to Upload, page 96
Use the Controller Status Menu to Upload, page 97

Use the Who Active Dialog Box to Upload

To use the Who Active dialog box to upload from the controller, complete the
following steps.

1. Click the Who Active button.

2. Choose the controller, and click Upload.

96 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Start to Use the Controller Chapter 4

3. On the Connected to Upload dialog box, click Upload.

Use the Controller Status Menu to Upload

After you establish a communication path in the Logix Designer application,

you can use the Controller Status menu to upload from the controller.

From the Controller Status menu, choose Upload.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 97

Chapter 4 Start to Use the Controller

4. On the Connected to Upload dialog box, click Upload.

Choose the Controller Use Table 8 as a reference when determining the controller operation mode.
Operation Mode Table 8 - Controller Operation Modes and Meanings
Mode Switch Setting(1) Run Remote Program
Mode set with the Logix Designer application Run Test Program
while online, and the Mode Switch set to
Remote
If you want to: Select one of these modes:
Turn outputs to the state commanded by the logic X X
of the project
Turn outputs to their configured state for Program X X X
mode
Execute (scan) tasks X X X
Change the mode of the controller via Logix X X X
Designer application
Download a project X X
While online, edit the project X X X X
Send messages X X X
Send and receive data in response to a message X X X X X
from another controller
Produce and consume tags X X X X X
(1) Moving the mode switch from Run to Remote leaves the controller in the Remote Run mode. Moving the switch from Program
to Remote leaves the controller in the Remote Program mode. You cannot choose Remote Test mode by the mode switch alone.
Remote Test mode is only available via the Logix Designer application.

98 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Start to Use the Controller Chapter 4

Use the Mode Switch to Change the Operating Mode

To change the operating mode, use the mode switch. The controller mode
switch provides a mechanical means to enhance controller and control system
security. You must physically move the mode switch on the controller to
change its operating mode from RUN, to REM, or to PROG.

When the mode switch on the controller is set to RUN mode, features like
online editing, program downloads, and firmware updates are prohibited. See
Table 8 for a complete list of prohibited features.

The mode switch can complement other authorization and authentication

methods that similarly control user-access to the controller, such as the
FactoryTalk Security service.

IMPORTANT During runtime, we recommend that you place the controller mode switch in
RUN mode. This practice can discourage unauthorized access to the
controller or potential tampering with the controller program,
configuration, or device firmware.
Place the mode switch in REM or PROG mode during controller
commissioning and maintenance and whenever temporary access is
necessary to change the program, configuration, or firmware of the product.

The mode switch on the front of the controller can be used to change the
controller to one of these modes:
Run (RUN)
Remote (REM)
Program (PROG)

Mode Switch

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 99

Chapter 4 Start to Use the Controller

Table 9 - Mode Switch Positions Set the Controller Operating Mode

Mode Switch Position Available Controller Modes
ATTENTION:

RUN Run modeThe controller is actively controlling the process/machine. Projects cannot Run mode is used only when all conditions are safe.
be edited in the Logix Designer application while the project is online and the controller is
in Run mode.
REM Remote Run modeThis mode is identical to Run mode except you can edit the project You are able to modify a project file online in Remote
online, and change the controller mode through the Logix Designer application. Run mode.
Be sure to control outputs with care to avoid injury to
personnel and damage to equipment.
Remote Program modeThis mode functions like Program mode, except you can Outputs are commanded to their Program mode state,
change the controller mode through the Logix Designer application. which can cause a dangerous situation.
Remote Test modeThis controller mode executes code, but I/O is not controlled. You
can edit the project online, and change the controller mode through the Logix Designer
application.
Output modules are commanded to their Program mode state (on, off, or hold).
PROG Program modeThis controller mode does not execute code or control I/O, but editing Do not use Program mode as an emergency stop (E-
operations are available. stop). Program mode is not a safety device.
Output modules are commanded to their Program mode state (On, Off, or Hold). Outputs are commanded to their Program mode state,
In this position, controller modes cannot be changed through the Logix Designer which can cause a dangerous situation.
application.

Use the Logix Designer to Change the Operating Mode

To change the operating mode with the Logix Designer application, the
controller is online and the mode switch is in the REM position. The following
modes are available:
Remote Program
Remote Run
Remote Test

Use the Controller Status menu to specify the operation mode.

TIP For this example, the controller mode switch is set to Remote mode. If the
controller mode switch is set to Run or Program modes, the menu options
change.

100 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Chapter 5

Tasks After Controller Operation Begins

Topic Page
Use the Secure Digital Card 101
Reset Button 108
Disable the Ethernet Ports 112

Use the Secure Digital Card You use an SD card with your CompactLogix 5380 controller to complete
the following:
Store the controller project to the SD card
Load a project from the SD card to the controller

Store to the Secure Digital Card

We recommend that you back up your Logix Designer project to an SD card
on a regular basis.

If a major nonrecoverable fault occurs that removes the program from the
controller memory, the backup copy on the SD card can be automatically
restored to the controller to quickly resume normal controller operation.

To store a project to the SD card, complete the following steps.

1. Make sure that the controller is online and in Program mode or Remote
Program mode.
2. Right-click the controller name and choose Properties.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 101

Chapter 5 Tasks After Controller Operation Begins

3. On the Nonvolatile Memory tab, click Load/Store.

TIP If Load/Store is dimmed (unavailable), verify the following:

You have specified the correct communication path.
The SD card is installed.
The SD card is unlocked. The locked status appears in the bottom-left
corner of the Nonvolatile memory/Load Store dialog box.
If the SD card is not installed, a message in the lower-left corner of the
Nonvolatile Memory tab indicates the missing card as shown here.

4. Change the Load Image properties as needed.

The following table describes the available Load Image options.

If you want the image (project) to load when Choose Menu Items
Power to the controller is applied or cycled On Power Up
The controller has lost the project and power has been cycled or applied On Uninitialized Memory
Initiated via the Logix Designer application User Initiated

5. Set the Load Mode properties according to your application

requirements.

This table describes the Load Mode options that you can choose for the
project.

If you want the controller to go to this mode after loading Choose Menu Items
Program Program (remote only)
Run Run (remote only)

102 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Tasks After Controller Operation Begins Chapter 5

6. Set the Automatic Firmware Update properties according to your

application requirements. The Automatic Firmware Update property is
also referred to as the Firmware Supervisor feature.

This table describes the Automatic Firmware Update options that you
can choose for the project.

Setting Description Menu Items

Disable Disables any automatic firmware updates. This item only appears in the menu
when you initially save the image.

Enable and Store Files to Image Enables automatic firmware updates for I/O devices in the configuration tree of
the controller. Saves I/O device firmware and controller firmware to the image.
I/O devices must be configured to use Exact Match Keying.(1)
Disable and Delete Files to Disables automatic firmware updates for I/O devices in the configuration tree of
Image the controller. Removes I/O device firmware from the image, but does not
remove controller firmware from image.This item only appears in the menu on
subsequent saves of the image.
(1) The devices that are used with this option must support the firmware revision to which the device is being updated.

7. Click Store.
8. Click Yes in the confirmation dialog box that appears.

If you enabled Automatic Firmware Update, a dialog box informs you

which modules are not included in the Automatic Firmware Update
operation.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 103

Chapter 5 Tasks After Controller Operation Begins

9. On the Automatic Firmware Update dialog box, click Yes.

The project is saved to the SD card as indicated by the controller status
indicators.

While the store is in progress, the following occurs:

OK indicator flashes green
SD indicator flashes green
Saving....Do Not Remove SD Card is shown on the status display
A dialog box in the Logix Designer application indicates that the
store is in progress
Controller Resets
SAVE is shown on the status display

When the store is complete, the controller resets.

IMPORTANT Let the store complete without interruption. If you interrupt the store, data
corruption or loss can occur.

Load from the Secure Digital Card

You can load from an SD card to a controller in one of the following ways:
Controller Power-up
User-initiated Action

IMPORTANT The actions that are described in this section apply whether the SD card is
unlocked or locked.

Controller Power-up

The following table describes what happens at controller power-up when an

SD card is already installed in the controller and has an image stored on it.

Load Image Setting Controller is in out-of-box condition Firmware > 1.x and internal nonvolatile Firmware > 1.x and internal nonvolatile
(v1.x firmware) memory is not valid(2) memory is valid(2)
User Initiated Loads Firmware Only(1) Does Nothing Does Nothing
On Power Up Loads both Firmware and Application Loads Firmware if there is a revision mismatch Loads Firmware if there is a revision
Loads Application mismatch
Loads Application
On Uninitialized Memory Loads both Firmware and Application(1) Loads Firmware if there is a revision mismatch Does Nothing
Loads Application
(1) Indicates change in behavior from CompactLogix 5370 and older controllers.
(2) Valid includes the No Project condition.

104 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Tasks After Controller Operation Begins Chapter 5

User-initiated Action

IMPORTANT You cannot use the method of loading a project that is described in this
section on a controller that uses firmware revision 1.xx. That is, the firmware
revision on an out-of-box controller.

You must complete the following before you can upload a project to the
controller from the SD card when the controller is already powered-up:
Establish the communication path.
Go online with the controller.
Make sure that the controller is in Program mode.

1. Right-click the controller name and choose Properties.

2. On the Nonvolatile Memory tab, verify that the project that is listed is
the correct one.

TIP If no project is stored on the SD card, a message on the Nonvolatile Memory

tab indicates that an image (or project) is not available.

For information on how to change the project that is available to load

from nonvolatile memory, see the Logix5000 Controllers Nonvolatile
Memory Programming Manual, publication 1756-PM017.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 105

Chapter 5 Tasks After Controller Operation Begins

3. Click Load/Store.

TIP If Load/Store is dimmed (unavailable), verify the following:

You have specified the correct communication path and are online with
the controller.
The SD card is installed.
Verify that the controller is not in Run Mode.

4. Click Load.

5. Click Yes in the confirmation dialog box that appears.

After you click Yes, the project is loaded to the controller as indicated by
the controller status indicators.

106 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Tasks After Controller Operation Begins Chapter 5

While the load is in progress, the following occurs:

OK indicator is solid red

SD indicator is flashing green

One of the following is shown on the status display, based on when the
load occurs:
LOAD
Loading . . . Do Not Remove SD Card

UPDT can be shown on the status display if the firmware is also

updating with the load.

A dialog box in the Logix Designer application indicates that the store is
in progress.

When the load is complete, the controller reboots.

IMPORTANT Let the load to complete without interruption. If you interrupt the load, data
corruption or loss can occur.

Other Secure Digital Card Tasks

You can use the SD cards to complete the following other tasks:
Change the image that is loaded from the card
Check for a load that was completed
Clear an image from the SD card
Store an empty image
Change load parameters
Read/write application data to the card

For more information to complete any of these tasks, see the Logix5000
Controllers Memory Card Programming Manual, publication 1756-PM017.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 107

Chapter 5 Tasks After Controller Operation Begins

Reset Button You can reset the controller with the reset button. The controller has two
stages of reset:
Stage 1 Reset
Stage 2 Reset

IMPORTANT Because port enable/disable status is associated with the application

program, the Ethernet port becomes enabled after a Stage 1 or Stage 2
reset.

WARNING: When you press the reset button while power is on, an Electric
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.

Reset Button

IMPORTANT The processes to perform both reset types requires that you press the reset
button and hold it in place during the controller power-up sequence.
If you press the reset button outside a power-up sequence, there is no effect
on the controller.

108 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Tasks After Controller Operation Begins Chapter 5

Stage 1 Reset

IMPORTANT A stage 1 reset occurs only if the controller contains a user application.

The stage 1 reset completes the following:

Clears the application program and memory.

Retains the Ethernet port network settings, including the EtherNet/IP

mode and all of the IP address settings.

Retains APR (motion position info) information.

Retains all PTP configuration (Time Synchronization) parameters.

Retains WallClockTime within the energy retention capability of the

module.

Creates a timestamped entry in the Controller Log that a Stage 1 Reset

event has occurred.

Resets the controller to begin the controller start-up process.

Prevents the controller from loading firmware from the SD card on the
initial start-up after the reset.

The prevention occurs regardless of the SD card settings and without

modifying the SD card contents, regardless of the write-protect setting.

If configured to do so, an SD card reloads on subsequent powerup

situations.

Enables any Ethernet port that were previously disabled.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 109

Chapter 5 Tasks After Controller Operation Begins

To perform a Stage 1 reset, complete the following steps. This process assumes
that an SD card is installed in the controller.

1. Power down the controller.

2. Open the front door on the controller.
3. Use a small tool with a diameter of a paper clip, to press and hold the
reset button.
4. While holding in the reset button, power up the controller.
5. Continue to hold the reset button while the 4-character display cycles
through CLR, 4, 3, 2, 1, Project Cleared.
6. After Project Cleared appears, release the reset button.

IMPORTANT If you release the reset button before Project Cleared scrolls across
the display, the controller continues with powerup and does not
reset.

After a Stage 1 reset is performed, load a Logix Designer application project to

the controller in the following ways:

Download the project from the Logix Designer application - For more
information, see Download a Project to the Controller on page 94

Cycle power on the controller to load a project from the SD card.

This option works only if the project stored on the SD card is

configured to load the project on powerup.

110 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Tasks After Controller Operation Begins Chapter 5

Stage 2 Reset

IMPORTANT A stage 2 reset occurs only if the controller does not contain a user
application, and the current controller firmware is not a 1.x revision.

The stage 2 reset completes the following:

Returns the module to revision 1.x firmware, that is, the out-of-box
firmware revision.

Clears all user settings, including network and time synchronization

settings.

If the controller uses CompactLogix 5380 controller firmware revision

29.011 or later, the EtherNet/IP mode is reset to Dual-IP mode, that is,
the default mode.

Resets the controller to begin the controller start-up process.

There are no entries in the controller log after a Stage 2 reset, but saved
logs on the SD card remain.

To perform a Stage 2 reset, complete the following steps. This process assumes
that an SD card is installed in the controller.

1. Power down the controller.

2. Open the front door on the controller.
3. Remove the SD card.
4. Use a small tool with a diameter of a paper clip, to press and hold the
reset button.
5. While holding in the reset button, power up the controller.
6. Continue to hold the reset button while the 4-character display cycles
through DFLT, 4, 3, 2, 1, Factory Default
7. After Factory Default appears, release the reset button.
8. On your workstation, delete the files on the SD card.
9. Power down the controller.
10. Reinstall the SD card.
11. Powerup the controller.
12. Verify that the controller is at firmware revision 1.x, and the controller is
set to DHCP-enabled.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 111

Chapter 5 Tasks After Controller Operation Begins

After a Stage 2 reset is performed, you must complete the following tasks to use
the controller again:

Configure the Ethernet ports, including setting the desired EtherNet/IP

mode, and then setting the controller IP address configuration.

For more information, see Set the Controller IP Address on page 66.

Update the firmware revision - For more information, see Update

Controller Firmware on page 80.

Download a Logix Designer application project to the controller in one

of the following ways:
Download the project from the Logix Designer application - For
more information, see Download a Project to the Controller on
page 94.
Cycle power on the controller to load a project from the SD card.

This option works only if the project stored on the SD card is

configured to load the project on powerup.

Disable the Ethernet Ports You can disable either of the embedded Ethernet ports on the controller.

1. Right-click the controller name and choose Properties.

112 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Tasks After Controller Operation Begins Chapter 5

2. On the Port Configuration tab, clear the Enable checkbox for the port
that you want to disable and click Apply.

3. If you are online when you make this change, click Yes on the Alert
dialog box.

The change takes effect immediately.

If you are offline, the change takes effect when you download the
program to the controller.
4. On the Port Configuration tab, click OK.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 113

Chapter 5 Tasks After Controller Operation Begins

Notes:

114 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Chapter 6

EtherNet/IP Network

Topic Page
Network Overview 115
EtherNet/IP Network Functionality 116
Software for EtherNet/IP Networks 117
Nodes on an EtherNet/IP Network 117
EtherNet/IP Network Communication Rates 120
EtherNet/IP Network Topologies 122
Socket Interface 128

CompactLogix 5380 controllers operate on EtherNet/IP networks.

Network Overview The EtherNet/IP network offers a full suite of control, configuration, and data
collection services by layering the Common Industrial Protocol (CIP) over the
standard Internet protocols, such as TCP/IP and UDP. This combination of
well-accepted standards provides the capability that is required to support
information data exchange and control applications.

The CompactLogix 5380 controllers use socket interface transactions and

conventional communication over the EtherNet/IP network to communicate
with Ethernet devices that do not support the EtherNet/IP application
protocol.

For more information on socket interface transactions, see Socket Interface on

page 128.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 115

Chapter 6 EtherNet/IP Network

EtherNet/IP Network The CompactLogix 5380 controllers support the following EtherNet/IP
network functionality:
Functionality
Dual built-in EtherNet/IP network ports

Support for the following EtherNet/IP modes:

Dual-IP mode - Available with the Logix Designer application,
version 29.00.00 or later
Linear/DLR mode

Support for the following EtherNet/IP network topologies:

Device Level Ring (DLR)
Linear
Star

Support for the following EtherNet/IP network communication rates:

10 Mbps
100 Mbps
1 Gbps

Support for only full-duplex operation

IMPORTANT If a device supports only half-duplex, you must connect it to a

switch to communicate with a CompactLogix 5380 controller.

Support for CIP Sync technology based on Time Synchronization using

the IEEE-1588 Precision Time Protocol

Duplicate IP address detection

Socket interface to communicate with Ethernet devices that do not

support the EtherNet/IP application protocol

Compatible with industry-standard Ethernet switches - Managed

switches are recommended, and CIP-protocol-aware switches can
provide more predictable performance.

116 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 EtherNet/IP Network Chapter 6

Support for messaging, produced/consumed tags, HMI, and distributed

I/O modules

Support for Integrated Motion Over an EtherNet/IP network - Not

available on all CompactLogix 5380 controllers

For more information on using Integrated Motion over an EtherNet/IP

network, see Chapter 10, Develop Motion Applications on page 177.

For more information about network design, see the Ethernet Design
Considerations Reference Manual, publication ENET-RM002.

Software for EtherNet/IP Table 10 lists software that is used with the EtherNet/IP networks and
modules.
Networks .

Table 10 - Software for Use with EtherNet/IP Networks

Software Use Required or Optional
Logix Designer application Configure CompactLogix projects. Required
Define EtherNet/IP communication.
RSLinx Classic or RSLinx Configure communication devices. Required
Enterprise Provide diagnostics.
Establish communication between devices.
BootP DHCP EtherNet/IP Assign IP addresses to the controller and devices on an Optional
Commissioning tool EtherNet/IP network.

Nodes on an EtherNet/IP When you configure your CompactLogix 5380 control system, you must
account for the number of EtherNet/IP nodes that you include in the I/O
Network configuration section of your project.

Table 11 shows the maximum number of EtherNet/IP nodes that

CompactLogix 5380 controllers support.
Table 11 - CompactLogix 5380 Controller EtherNet/IP Nodes
Cat. No. Maximum Number of EtherNet/IP Nodes Supported
5069-L306ER, 5069-L306ERM 16
5069-L310ER, 5069-L310ER-NSE, 24
5069-L310ERM
5069-L320ER, 5069-L320ERM 40
5069-L330ER, 5069-L330ERM 50
5069-L340ER, 5069-L340ERM 55
5069-L350ERM 60
5069-L380ERM 70
5069-L3100ERM 80

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 117

Chapter 6 EtherNet/IP Network

Devices Included in the Node Count

Any EtherNet/IP devices that you add to the I/O configuration section are
counted toward the controller node limit. The following are examples of
devices that must be counted:

Remote communication adapters

Switches that are included in the I/O configuration section

Devices with an embedded EtherNet/IP port, such as drives, I/O

modules, and linking devices

Remote controllers when a produce/consume connection is established

between the two controllers

HMI devices that are included in the I/O configuration section

Third-party devices that are directly connected to the EtherNet/IP

network

Devices Excluded from the Node Count

When you calculate the EtherNet/IP node limitation of a controller, do not

count devices that exist on the EtherNet/IP network but are not added to the
I/O configuration section.

The following devices are not added to the I/O configuration section and are
not counted among the number of nodes:

Computer

HMIs that are not added to the I/O configuration section

Devices that are the target of MSG Instructions but were not added to
the I/O configuration section

Standard Ethernet devices with which the controller communicates via a

socket interface

118 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 EtherNet/IP Network Chapter 6

Figure 9 shows nodes in the I/O tree.

Figure 9 - Example EtherNet/IP Nodes

Node

Node

Node

Node

The Capacity tab in the Controller Properties dialog box keeps track of the
number of Ethernet nodes used in a project. The following graphic is
representative of the project shown in Figure 9.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 119

Chapter 6 EtherNet/IP Network

EtherNet/IP Network The CompactLogix 5380 controllers support the following EtherNet/IP
network communication rates:
Communication Rates
10 Mbps
100 Mbps
1 Gbps

Set the Network Communication Rate

Network performance in a CompactLogix 5380 system is optimal if the 1 Gbps

network communication rate is used. However, many Ethernet devices do not
support the 1 Gbps network communication rate. Instead, they support a
maximum rate of 100 Mbps.

The difference in maximum network communication rates impacts your

CompactLogix 5380 system and, in some applications, restricts you from using
the 1 Gbps network communication rate on a CompactLogix 5380 controller.

When you design a CompactLogix 5380 system and consider using the 1 Gbps
rate on the controller, remember the following:

You can use the 1 Gbps network communication rate on the controller
ports when all network devices support the 1 Gbps, for example,
5069-AEN2TR adapters with 5069 Compact I/O modules.

When you use the 1 Gbps network communication rate, configure the
controller ports to use Auto-Negotiate.

CompactLogix 5380 Controller

5069 Compact I/O Modules

Stratix 5400 Switch

1 Gbps

1 Gbps 5069-AEN2TR Adapter

5069 Compact I/O Modules
Workstation

5069-AEN2TR Adapter
5069 Compact I/O Modules

120 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 EtherNet/IP Network Chapter 6

You can use the 1 Gbps network communication rate on the controller
ports when some network devices support a maximum network
communication rate of 100 Mbps. However, in this case, the controller
must be connected to those devices through a managed switch.

The port to which the controller is connected must be configured for

Auto-Negotiate and the 1 Gbps network communication rate.
CompactLogix 5380 Controller
5069 Compact I/O Modules 5069-AEN2TR Adapter
5069 Compact I/O Modules

Workstation

Stratix 5400 Switch

F1 F9 100 Mbps 1 Gbps
PanelView Plus 7 F2

F3

F4
F10

F11

F12

Terminal F5

F6

F7
F13

F14

F15

F8 F16

100 Mbps 1 Gbps

100 Mbps

527

5069-AEN2TR Adapter
5069 Compact I/O Modules
PowerFlex 527 Drive Kinetix 5500 Drive

We recommend that you do not use the 1 Gbps network communication rate
on the controller ports if it operates on a linear or DLR network topology and
at least one device on the network supports the maximum network
communication rate of 100 Mbps.

That is, do not use different network communication rates on device ports in
the same EtherNet/IP network without a managed switch.

All network communication on this

network uses the 100 Mbps rate. 1794-AENTR Adapter 5069-AEN2TR Adapter
1794 FLEX I/O Modules 5069 Compact I/O Modules

F1 F9

F2 F10

F3 F11

F4 F12

F5 F13

F6 F14

F7 F15

F8 F16

Workstation PanelView Plus 7

Terminal
002 1734-AENTR

POINT I O
Module
Status
Network
Activity
Network
Status
Point Bus
Link 1 Status
Activity/
Status System
Power
Field
Power
IP ADDRESS

Link 2
Activity/
Status

CompactLogix 5380 Controller Kinetix 5500 Drives 1734-AENTR Adapter

5069 Compact I/O Modules 1734 POINT I/O Modules

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 121

Chapter 6 EtherNet/IP Network

EtherNet/IP Network CompactLogix 5380 controllers support these EtherNet/IP network types:
Topologies Device Level Ring Network Topology
Linear Network Topology
Star Network Topology

Device Level Ring Network Topology

A DLR network topology is a single-fault tolerant ring network that is

intended for the interconnection of automation devices. A DLR network uses
Supervisor (Active and Backup) nodes and Ring nodes.

DLR network topologies automatically convert to linear network topologies

when a fault is detected. The conversion to the new network topology
maintains communication of data on the network. The fault condition is
typically easily detected and corrected.

The controller is typically in Linear/DLR mode to operate on a

DLR topology. If the controller operates in Dual-IP mode, it must connect to a
DLR network only via an ETAP.

IMPORTANT Remember, if you use a CompactLogix 5380 controller in a DLR network with
devices that have a maximum network communication rate of 100 Mbps, set
the controller ports to 100 Mbps.

Figure 10 - CompactLogix 5380 Controller in a DLR Network Topology (Linear/DLR Mode)

CompactLogix 5380 Controller 5069-AEN2TR Adapter
5069 Compact I/O Modules 5069 Compact I/O Modules

Workstation

PowerFlex 527
All network communication on this network uses the 100 Mbps rate.
Drive
527

5069-AEN2TR Adapter
5069 Compact I/O Modules

002 1734-AENTR

POINT I O
Module
Status
Network
Activity F1 F9
Network
Status

Link 1
Point Bus
Status
F2 F10
Activity/
Status System
Power
Field
F3 F11
Power
IP ADDRESS

F4 F12

F5 F13

F6 F14

F7 F15

Link 2
Activity/ F8 F16
Status

1734-AENTR Adapter PanelView Plus 7 Terminal

Kinetix 5500 Drives 1734 POINT I/O Modules

122 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 EtherNet/IP Network Chapter 6

Figure 11 - CompactLogix 5380 Controller in a DLR Network Topology (Dual-IP Mode)

IMPORTANT If a CompactLogix 5380 controller is using Dual-IP mode, the controller can
only connect to a DLR network topology through a 1783 EtherNet/IP tap.

CompactLogix 5380 Controller

5069 Compact I/O Modules

Port A1 connected to an
Enterprise-level network
Port A2 connected
to the DLR network 5069-AEN2TR Adapter
via a 1783-ETAP tap 5069 Compact I/O Modules

PowerFlex 527
All network communication on this network uses the 100 Mbps rate.
Drive
527

5069-AEN2TR Adapter
5069 Compact I/O Modules

002 1734-AENTR

POINT I O
Module
Status
Network
Activity F1 F9
Network
Status

Link 1
Point Bus
Status
F2 F10
Activity/
Status System
Power
Field
F3 F11
Power
IP ADDRESS

F4 F12

F5 F13

F6 F14

F7 F15

Link 2
Activity/ F8 F16
Status

1734-AENTR Adapter PanelView Plus 7 Terminal

Kinetix 5500 Drives 1734 POINT I/O Modules

For more information on how to design a DLR network, see the EtherNet/IP
Embedded Switch Technology Application Guide, publication ENET-AP005

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 123

Chapter 6 EtherNet/IP Network

Linear Network Topology

A linear network topology is a collection of devices that are daisy-chained

together across an EtherNet/IP network. Devices that can connect to a linear
network topology use embedded switch technology to remove any need for a
separate switch, as required in Star network topologies.

IMPORTANT Remember, if you use a CompactLogix 5380 controller in a linear network

with devices that have a maximum network communication rate of
100 Mbps, set the controller ports to 100 Mbps.

Figure 12 - CompactLogix 5380 Controller in a Linear Network Topology (Linear/DLR Mode)

CompactLogix 5380 Controller

Workstation 5069 Compact I/O Modules PowerFlex 527 Drive 1734-AENTR Adapter
1734 POINT I/O Modules
00 2 1734-AENTR

POINT I O
Module
Status
Network
Activity
Network
Status
Point Bus
Link 1 Status
Activity/
Status System
Power
Field
Power

IP ADDRESS
Link 2
Activity/
Status

527

F1 F9

F2 F10

F3 F11

F4 F12

F5 F13

F6 F14

F7 F15

F8 F16

PanelView Plus 7 Terminal

5069-AEN2TR Adapter 5069-AEN2TR Adapter Kinetix 5500 Drives

5069 Compact I/O Modules 5069 Compact I/O Modules

All network communication on this network uses the 100 Mbps rate.

124 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 EtherNet/IP Network Chapter 6

Figure 13 - CompactLogix 5380 Controller in a Linear Network Topology (Dual-IP Mode)

IMPORTANT If a CompactLogix 5380 controller is using Dual-IP mode, the controller can
only connect to a linear network topology in one of the following ways:
As an end device
Through a 1783 EtherNet/IP tap
Both ways are shown below.

CompactLogix 5380 Controller

5069 Compact I/O Modules PowerFlex 527 Drive 1734-AENTR Adapter
1734 POINT I/O Modules
CompactLogix 5380 controller
connected as end device 002 1734-AENTR

POINT I O
Module
Status
Network
Activity
Network
Status
Point Bus
Link 1 Status
Activity/
Status System
Power
Field
Power

IP ADDRESS
Link 2
Activity/
Status
527

Port A1 connected to an Port A2 connected to

Enterprise-level network the linear network
F1 F9

F2 F10

F3 F11

F4 F12

F5 F13

F6 F14

F7 F15

F8 F16

PanelView Plus 7 Terminal

5069-AEN2TR Adapter Kinetix 5500 Drives

5069 Compact I/O Modules

CompactLogix 5380 Controller

5069 Compact I/O Modules

CompactLogix 5380 controller

connected via a 1783-ETAP tap

PowerFlex 527 Drive 1734-AENTR Adapter

Port A1 connected to an 1734 POINT I/O Modules
Enterprise-level network Port A2 connected
to the linear 002

Link 1
1734-AENTR

POINT I O
Module
Status
Network
Activity
Network
Status
Point Bus
Status

network via a
Activity/
Status System
Power
Field
Power
IP ADDRESS

1783-ETAP tap Link 2

Activity/
Status

527

F1 F9

F2 F10

F3 F11

F4 F12

F5 F13

F6 F14

F7 F15

F8 F16

PanelView Plus 7
Terminal

5069-AEN2TR Adapter 5069-AEN2TR Adapter Kinetix 5500 Drives

5069 Compact I/O Modules 5069 Compact I/O Modules

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 125

Chapter 6 EtherNet/IP Network

Star Network Topology

A star network topology is a traditional EtherNet/IP network that includes

multiple devices that are connected to each other via an Ethernet switch.

You can use the star network topology with Linear/DLR and Dual-IP modes.

Figure 14 - CompactLogix 5380 Controllers in a Star Network Topology (Linear/DLR Mode)

CompactLogix 5380 Controller

5069 Compact I/O Modules 5069-AEN2TR Adapter
5069 Compact I/O Modules
Workstation connected
to the controller via the
USB port

1 Gbps
Stratix 5700 Switch
F1 F9
100 Mbps 1 Gbps
The communication rates on this network vary F2

F3

F4
F10

F11

F12

based on the maximum network communication F5

F6

F7
F13

F14

F15

rate supported by each device because the devices F8 F16

100 Mbps
are connected via a managed switch. 100 Mbps

PanelView Plus 7
Terminal 100 Mbps

002 1734-AENTR

POINT I O
Module
Status
Network
Activity
Network
Status
Point Bus
Link 1 Status
Activity/
Status System
Power
Field
Power
527
IP ADDRESS

Link 2
Activity/
Status
Kinetix 5500 Drive
PowerFlex 527 Drive 1734-AENTR Adapter
1734 POINT I/O Modules

126 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 EtherNet/IP Network Chapter 6

Figure 15 - CompactLogix 5380 Controllers in a Star Network Topology (Dual-IP Mode)

CompactLogix 5380 Controller
Enterprise Level Network 5069 Compact I/O Modules PanelView Plus 7
Terminal

F1 F9

F2 F10

F3 F11

F4 F12

F5 F13

F6 F14

F7 F15

F8 F16

Device-level Network
Stratix 2000 Switch

527

5069-AEN2TR Adapter PowerFlex 527 Drive

5069 Compact I/O Modules

Integrated Architecture Tools

For more information when you design your CompactLogix 5380 system, see
the Integrated Architecture Tools and Resources web page. For example, you
can access the Popular Configuration Drawings with different EtherNet/IP
network topologies.

The tool and resources are available at: http://www.rockwellautomation.com/

global/products-technologies/integrated-architecture/tools/overview.page

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 127

Chapter 6 EtherNet/IP Network

Socket Interface The controller can use socket interfaces to communicate with Ethernet devices
that do not support the EtherNet/IP application protocol. The socket
interface is implemented via the Socket Object. The controller communicates
with the Socket Object via MSG instructions.

You must use MSG instructions that configure and operate the socket interface
as Unconnected, and use the Message to Self path. To communicate with
another device, you must understand the application protocol of the other
device. The following are example screens of an MSG instruction used with a
socket interface.

The CompactLogix 5380 controllers support up to 32 socket instances.

IMPORTANT Keep the following in mind when you use sockets with
CompactLogix 5380 controllers:
A significant difference between CompactLogix 5380 controllers and
other Logix5000 controllers is the communication path.
CompactLogix 5380 controllers do not require a separate EtherNet/IP
network communication module, for example, a 1756-EN2TR
communication module. In the case of the CompactLogix 5380
controllers, the MSG instruction is sent to the controller itself by using
the path THIS.
All CompactLogix 5380 controllers must use unconnected MSG
instructions for socket servers. When you configure a message for a
CompactLogix 5380 controller, make sure that the Connected checkbox
on the Message Configuration dialog box is cleared.
When the controller operates in Dual-IP mode and uses a Socket Object,
you can use an IP address with a Socket_Create service type. For more
information, see page 50.

For more information on the socket interface, see EtherNet/IP Socket

Interface Application Technique, publication ENET-AT002.

128 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Chapter 7

Use I/O Modules

Topic Page
Local I/O Modules 129
Remote I/O Modules 136
Add to the I/O Configuration While Online 147
Determine When Data is Updated 148

CompactLogix 5380 systems support the following I/O module options:

Local I/O modules

Remote I/O modules

Local I/O Modules The CompactLogix 5380 system use 5069 Compact I/O modules as local
I/O modules. The modules are installed to the right of the controller.

The number of local 5069 Compact I/O modules that you can install in a
CompactLogix 5380 system varies based on the controller that is used, up to a
maximum of 31 modules.

Table 12 lists the number of local I/O modules that CompactLogix 5380
controllers support.
Table 12 - Local I/O Modules in CompactLogix 5380 System
Cat. No. Local I/O Modules Supported, Max.
5069-L306ER, 5069-L306ERM, 5069-L310ER, 5069-L310ERM, 8
5069-L310ER-NSE
5069-L320ER, 5069-L320ERM 16
(1), 5069-L330ERM(1), 5069-L340ER, 5069-L340ERM,
5069-L330ER 31
5069-L350ERM, 5069-L380ERM, 5069-L3100ERM
(1) When you use this controller with the Logix Designer application, version 29.00.00, the application limits the number of local
I/O modules in the project to 16. For more information, see the Rockwell Automation Knowledgebase article #942580, 5380
CompactLogix controllers limited to 16 local 5069 modules in V29 of Studio 5000. The document is available at http://
www.rockwellautomation.com/knowledgebase.
With the Logix Designer application, version 30.00.00 or later, the controller supports as many as 31 local I/O modules.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 129

Chapter 7 Use I/O Modules

The following are example factors that you must consider when you decide
how to use local I/O modules in a CompactLogix 5380 system:

Number of local I/O modules that the controller supports

Features available on different modules, for example, sequence of events

per point timestamping on only some 5069 Compact I/O digital input
modules

I/O module power usage, including MOD power and SA power

For more information on 5069 Compact I/O modules, see Additional

Resources on page 9.

Figure 16 - Local I/O Modules in a CompactLogix 5380 System

Local I/O Modules

130 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Use I/O Modules Chapter 7

Add Local I/O Modules to a Project

Before you can add local I/O modules to a Logix Designer application project,
you must open an existing project or create a project. For information on how
to create a project, see Create a Logix Designer Application Project on page 89.

There are two methods to add local I/O modules to the project:

Discover Modules

New Module

Discover Modules

To use Discover Modules to add a local I/O module, complete these steps.

1. Go online with your Logix Designer application.

2. Right-click 5069 Backplane and choose Discover Modules.

The Logix Designer application automatically detects available modules

that are installed in the system.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 131

Chapter 7 Use I/O Modules

3. At the Select Module Type window, click Create to add a discovered

module to your project.

4. At the New Module window, configure the module properties and

click OK.

5. At the warning dialog box, click Yes.

TIP If you inhibit the module connection, you must remember to uninhibit the
connection later.

132 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Use I/O Modules Chapter 7

6. Close the Select Module Type dialog box.

To add additional local I/O modules, complete one of the following:

If you cleared the Close on Create checkbox when you created the first
I/O module, repeat steps 36.

If you did not clear the Close on Create checkbos when you created the
first I/O module, repeat steps 26.

New Module

To use New Module to add a module, complete these steps.

1. Right-click 5069 Backplane and choose New Module.

2. Select the module and click Create.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 133

Chapter 7 Use I/O Modules

The New Module dialog box appears.

3. Configure the module and click OK.

TIP Remember, if the Series and Revision parameter values do not match those
of the module for which this configuration is intended, your project can
experience module faults.

To add additional local I/O modules, complete one of the following:

If you cleared the Close on Create checkbox when you created the first
I/O module, repeat steps 23.

If you did not clear the Close on Create checkbos when you created the
first I/O module, repeat steps 13.

For more information on how to use local I/O modules in a

CompactLogix 5380 system, see the resources listed in Additional Resources
on page 9.

134 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Use I/O Modules Chapter 7

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.

The following Electronic Keying options are available.

Keying Option Description

Compatible Lets the installed device accept the key of the device that is defined in the project when the
Module installed device can emulate the defined device. With Compatible Module, you can typically
replace a device with another device that has the following characteristics:
Same catalog number
Same or higher Major Revision
Minor Revision as follows:
If the Major Revision is the same, the Minor Revision must be the same or higher.
If the Major Revision is higher, the Minor Revision can be any number.
Disable Keying Indicates that the keying attributes are not considered when attempting to communicate with
a device. With Disable Keying, communication can occur with a device other than the type
specified in the project.
ATTENTION: Be cautious when using Disable Keying; if used incorrectly, this option can lead
to personal injury or death, property damage, or economic loss.
We strongly recommend that you do not use Disable Keying.
If you use Disable Keying, you must take full responsibility for understanding whether the
device being used can fulfill the functional requirements of the application.
Exact Match Indicates that all keying attributes must match to establish communication. If any attribute
does not match precisely, communication with the device does not occur.

Carefully consider the implications of each keying option when selecting one.

IMPORTANT When you change Electronic Keying parameters online, it 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.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 135

Chapter 7 Use I/O Modules

Remote I/O Modules Remote I/O modules do not reside in the CompactLogix 5380 system. The
controller connects to the I/O modules via an EtherNet/IP network.
CompactLogix 5380 controllers support the use of a wide range of remote I/O
modules. For maximum performance, we recommend that you use 5069
Compact I/O modules when you use remote I/O modules.

For example, CompactLogix 5380 controllers can connect to following:

Chassis-based I/O module families, such as 5069 Compact I/O, 1756

ControlLogix I/O, 1769 Compact I/O, or 1746 SLC I/O modules

In-cabinet I/O module families, such as 1734 POINT I/O or

1794 FLEX I/O modules

On-Machine I/O module families, such as 1732D ArmorBlock I/O

modules

IMPORTANT The following network examples are solely intended to show remote I/O
modules in various network topologies. The examples do not address
network communication rates between the CompactLogix 5380 controller
and the I/O modules.
We recommend, however, that you consider network communication rates
when you determine the best way to incorporate remote I/O modules in your
CompactLogix 5380 system.
For more information, see EtherNet/IP Network Communication Rates on
page 120

Figure 17 - Remote I/O in a CompactLogix 5380 System on a DLR Network Topology

CompactLogix 5380 Controller 5069-AEN2TR Adapter

5069 Compact I/O Modules 5069 Compact I/O Modules

Workstation

PowerFlex 527
Drive Remote I/O Modules
527

5069-AEN2TR Adapter
5069 Compact I/O Modules
002 1734-AENTR

POINT I O
Module
Status
Network
Activity F1 F9
Network
Status

Link 1
Point Bus
Status
F2 F10

Kinetix 5500
Activity/
Status System
Power
Field
F3 F11
Power
IP ADDRESS

F4 F12

F5 F13

Drives Link 2
Activity/
Status
F6

F7

F8
F14

F15

F16

1734-AENTR Adapter PanelView Plus 7 Terminal

1734 POINT I/O Modules

136 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Use I/O Modules Chapter 7

Figure 18 - Remote I/O in a CompactLogix 5380 System on a Linear Network Topology

CompactLogix 5380 Controller 5069-AEN2TR Adapter

1734-AENTR Adapter
Workstation 5069 Compact I/O Modules 5069 Compact I/O Modules
1734 POINT I/O Modules

00 2 1734-AENTR

POINT I O
Module
Status
Network
Activity
Network
Status
Point Bus
Link 1 Status
Activity/
Status System
Power
Field
Power

IP ADDRESS
Link 2
Activity/
Status

527

Remote I/O Modules

F1 F9

F2 F10

F3 F11

F4 F12

F5 F13

F6 F14

F7 F15

F8 F16

PanelView Plus 7
Terminal

5069-AEN2TR Adapter 5069-AEN2TR Adapter Kinetix 5500 Drives

5069 Compact I/O Modules 5069 Compact I/O Modules

Figure 19 - Remote I/O in a CompactLogix 5380 System on a Star Network Topology

CompactLogix 5380 Controller

5069 Compact I/O Modules 5069-AEN2TR Adapter
5069 Compact I/O Modules

Workstation

Stratix 5700 Switch

F1 F9

F2 F10

F3 F11

PanelView Plus 7 F4

F5

F6
F12

F13

F14

Terminal F7

F8
F15

F16
Remote I/O Modules

PowerFlex 527 Drive 002 1734-AENTR

POINT I O
Module
Status
Network
Activity
Network
Status
Point Bus
Link 1 Status
Activity/
Status System
Power
Field
Power
527
IP ADDRESS

Link 2
Activity/
Status
Kinetix 5500 Drive

1734-AENTR Adapter
1734 POINT I/O Modules

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 137

Chapter 7 Use I/O Modules

Add Remote I/O Modules to a Project

Before you can add remote I/O modules to a project, you must add the
EtherNet/IP communication module that facilitates communication between
the CompactLogix 5380 controller and the remote I/O modules.

There are two methods to add remote I/O modules to the project:

Discover Modules

New Module

Discover Modules

When you use Discover Modules to find Ethernet devices, the Logix Designer
application browses based on how Ethernet browsing is configured in RSLinx
Classic software.

If the EtherNet/IP driver is used in RSLinx Classic software, the Logix

Designer automatically detects remote I/O modules.

If the Ethernet devices driver is used in RSLinx Classic software, you

must configure the IP address for each Ethernet device that you want to
display in the Select Module Type dialog box shown on page 139.

If the Ethernet bus is browsed via a CIP router, you must configure the
IP address for each Ethernet device that you want to display in the Select
Module Type dialog box shown on page 139.

The tasks described in this section apply when you use the EtherNet/IP driver
in RSWho to browse the network.

To use Discover Modules to add a remote I/O module, complete these steps.

1. Go online with your Logix Designer application.

138 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Use I/O Modules Chapter 7

2. Right-click Ethernet and choose Discover Modules.

The Logix Designer application automatically detects available modules

that are installed in the system.
3. At the Select Module Type window, click Create to add a discovered
adapter to your project.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 139

Chapter 7 Use I/O Modules

4. At the New Module window, configure the module properties and

click OK.

5. At the warning dialog box, click Yes.

TIP If you inhibit the module connection, you must remember to uninhibit the
connection later.

6. Close the Select Module Type dialog box.

140 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Use I/O Modules Chapter 7

7. Right-click 5069 Backplane and choose Discover Modules.

The Logix Designer application automatically detects available modules

that are installed in the system.
8. At the Select Module Type window, click Create to add a discovered
module to your project.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 141

Chapter 7 Use I/O Modules

9. At the New Module window, configure the module properties and

click OK.

10. At the warning dialog box, click Yes.

TIP If you inhibit the module connection, you must remember to uninhibit the
connection later.

11. Close the Select Module Type dialog box.

After you add the remote I/O module, consider the following:
To add remote I/O modules in the same remote location, complete one
of the following:
If you cleared the Close on Create checkbox when you created the
first I/O module, repeat steps 811.
If you did not clear the Close on Create checkbos when you created
the first I/O module, repeat steps 711.

To add remote I/O modules in another new remote location, repeat

steps 211.

142 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Use I/O Modules Chapter 7

New Module

To use New Module to add a remote I/O module, complete these steps.

1. Right-click Ethernet and choose New Module.

2. Select
3. the EtherNet/IP adapter and click Create.
For some modules, the Select Major Revision dialog box can appear.
If the dialog box appears, choose the major revision of the module
and click OK.
TIP
Remember, if the Series and Revision parameter values do not
match those of the module for which this configuration is intended,
your project can experience module faults.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 143

Chapter 7 Use I/O Modules

4. At the New Module window, configure the module properties and

click OK.

5. At the warning dialog box, click Yes.

TIP If you inhibit the module connection, you must remember to uninhibit the
connection later.

6. Close the Select Module Type dialog box.

144 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Use I/O Modules Chapter 7

7. Right-click the newly added EtherNet/IP communication module or

the backplane and choose New Module.

8. Select the I/O module that you want to add and click Create.

TIP If you must add multiple I/O modules to the same remote location, we
recommend that you clear the Close on Create checkbox before you
click Create.
If the Close on Create checkbox is cleared, when you complete configuration
for an I/O module, the Select Module Type dialog box appears automatically
and you can skip step 7.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 145

Chapter 7 Use I/O Modules

9. Configure the I/O module.

10. At the New Module window, configure the module properties and
click OK.

11. At the warning dialog box, click Yes.

TIP If you inhibit the module connection, you must remember to uninhibit the
connection later.

12. Close the Select Module Type dialog box.

After you add the remote I/O module, consider the following:
To add remote I/O modules in the same remote location, complete one
of the following:
If you cleared the Close on Create checkbox when you created the
first I/O module, repeat steps 89.
If you did not clear the Close on Create checkbox when you created
the first I/O module, repeat steps 79.

To add remote I/O modules in another new remote location, repeat

steps 112.

146 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Use I/O Modules Chapter 7

Add to the I/O Configuration You can add local and remote I/O modules and other devices to the controller
configuration while the project is online.
While Online
IMPORTANT To add I/O modules when the controller is online, the controller mode switch
must be in the REM or PROG position.
The I/O modules must already be installed in the system. You cannot install
the I/O modules when the system is powered.

The modules and devices you can add while online depends on the software
version that you use. Later versions have more modules and devices that can be
added while online.

Add-on Profiles (AOP) for modules are made available between releases of
different Logix Designer application versions. There are cases in which, after
you download and install the AOP file for a module, you can add the module
to a project while online.

To see a list of the available AOP files, go to:

https://download.rockwellautomation.com/esd/
download.aspx?downloadid=addonprofiles

For more information about adding to the I/O Configuration while online, see
the Logix5000 Controllers Design Considerations Reference Manual,
publication 1756-RM094

Modules and Devices that Can be Added While Online

You can add these modules and devices to the CompactLogix 5380 controller
I/O configuration while online with Logix Designer, version 28 or later.

5069 Compact I/O modules - As local or remote I/O modules

5069 Compact I/O EtherNet/IP adapters

1756 ControlLogix EtherNet/IP modules

1756 ControlLogix I/O modules

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 147

Chapter 7 Use I/O Modules

Determine When Data CompactLogix 5380 controllers update data asynchronously with the
execution of logic. See the following flowcharts to determine when a controller,
is Updated input module, or bridge sends data:

Input Data Update Flowchart

Output Data Update Flowchart

Input Data Update Flowchart

Digital without events, analog without RTS, produced tag

Method of Input Data Production Produced tag with data state change events

Digital with Events Enabled

Analog with RTS Enabled

RTSRPI? No

Yes

The module sends data at the RTS. The module sends data at
the RTS and RPI.

Data is sent by the module at the RPI

and at the change of a specified point.

Data is sent by the producing controller

at the RPI and when an IOT executes.
The Event task in a consuming controller
is only triggered when an IOT instruction
is executed in the producer.

Data is sent by the module or the

producing controller at the RPI.

New data can appear in Input tags at any point in the program scan. If the
control logic reads input tag values in multiple locations, do not assume
that the data remains unchanged throughout the scan of the logic.

148 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Use I/O Modules Chapter 7

Output Data Update Flowchart

Automatic output
processing of each task.
Method of Output Data Production Output Module Profile Configuration

Cyclic data production IOT instruction executes.

at the RPI.
Module profile lets data be Module profile lets data be
sent at the RPI only sent at the RPI or at the
end of task scans

Data is sent by the Data is sent by the Data is sent by the controller
controller triggered controller triggered No data is sent by automatic triggered by the end of task.
by the RPI. by the user program. output processing

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 149

Chapter 7 Use I/O Modules

Notes:

150 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Chapter 8

Manage Controller Communication

Topic Page
Connection Overview 151
Controller Communication Interaction with Control Data 152
Produce and Consume (Interlock) Data 153
Send and Receive Messages 155

Connection Overview Logix5000 controllers provide connection resources when communications

are established between two devices.

Connections are used when the system contains the following conditions:

I/O modules, communication modules, and adapters are present in the

I/O configuration of the user project.

Produced or Consumed tags are configured in the user project.

Connected Messages are executed in the user application.

External devices, programming terminals, or HMI terminals

communicate with the controller.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 151

Chapter 8 Manage Controller Communication

Controller Communication The CompactLogix 5380 controller runs the communications task separately
from the application code. The controller runs communications
Interaction with asynchronously to the application. Therefore, it is important to make sure
Control Data communications that are delivered to the controller are complete before the
application executes on the newly delivered data. This applies to data that is
coming into the controller and data that is going out from the controller.

For example, if an HMI device writes a large block of recipe data to the
controller, the application code can start to execute on that data before the data
is written. This action results in half of the current recipe and half of the last
recipe in the application space.

Traditionally, programmers have used the following to control the effects of

asynchronous communications:
UID/UIE pairs
Periodic tasks
Moving data with CPS instructions.

These options rely on controlling when the main core can switch tasks. As a
result, the communication task cannot change data when the control task is
using it. Because the controller processes communications on an independent
CPU core, these methods are no longer effective in all cases.

Table 13 highlights the controller behavior.

Table 13 - CompactLogix 5380 Controller Behavior
Tag Access
Application Construct HMI MSG I/O Update Produce/Consume Other User Tasks Motion Planner
UID/UIE Allows Allows Allows Allows Blocks Allows
CPS Blocks Blocks Blocks Blocks Allows Allows
Periodic Tasks Allows Allows Allows Allows Allows Allows
Blocks - Prevents source data values from change by communications during application execution.
Allows - Communications can change source data values during application execution.

Because the controllers have 32-bit data integrity, this only applies to data
structures larger than 32 bits. If word-level integrity is your primary concern,
the 32-bit data integrity does not impact your data use.

Good programming practice dictates the use of two unique words at the
beginning and the end of data. The controller validates the words to assure the
entire structure has data integrity. We recommend that the handshake data is
changed and the application code validates it every transaction before the
controller application code or higher-level system reading controller data acts
on it.

152 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Manage Controller Communication Chapter 8

Table 14 shows two data elements that are added to a structure for data
integrity checking. That is, Start Data and End Data are added. We
recommend that the controller validates the Start Data value and the End Data
value match before the controller acts on My_Recipe1.

If the Start Data and End Data values do not match, it is likely communications
is in the process of filling the structure. The same applies to higher-level
systems that are receiving data from the controller.
Table 14 - Data Elements
Structure My_Recipe1 My_Recipe2 My_Recipe3
Start Data 101 102 103
Sugar 3 4 8
Flour 4 3 9
Chocolate 2 2 4
Oil 6 7 2
End Data 101 102 103

TIP We recommend that you perform this test on a buffered copy of the data
and not the actual data element being written to by the communications
core. If you use buffered data, you prevent the risk of the communication
core changing data after you have passed the data valid test.

Produce and Consume CompactLogix 5380 controllers let you produce (transmit) and consume
(receive) controller-scoped tags.
(Interlock) Data
Figure 20 - Example Produced and Consumed Tags

Controller_1 Controller_2
Produced Tag Consumed Tag

Controller_3
Consumed Tag

Controller_4
Consumed Tag

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 153

Chapter 8 Manage Controller Communication

Table 15 describes the system-shared tags.

Table 15 - Produced and Consumed Tag Descriptions

Tag Description
Produced tag A tag that a controller makes available for use by other controllers. Multiple controllers can
simultaneously consume (receive) the data.
A produced tag sends its data to one or more consumed tags (consumers) without using logic.
Consumed tag A tag that receives the data of a produced tag. The data type of the consumed tag must match
the data type (including any array dimensions) of the produced tag. The RPI of the consumed
tag determines the period at which the data updates.

For two controllers to share produced or consumed tags, the controllers must
be attached to the same network. You cannot bridge produced and consumed
tags over two networks.

Produced and consumed tags use connections of the controller and the
communication modules being used.

Requested Packet Interval (RPI) of Multicast Tags

The first consumer of a multicast produced tag on any given communications

port establishes the RPI value for that port. All subsequent consumers that use
the same port must request the same RPI value as the first consumer, otherwise
they fail to connect. Controllers with backplane and EtherNet/IP ports can
produce data at an independent RPI value on each port.

For more information about produced/consumed tags, see the Logix5000

Controllers Produced and Consumed Tags Programming Manual,
publication 1756-PM011.

154 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Manage Controller Communication Chapter 8

Send and Receive Messages Messages transfer data to other devices, such as other controllers or operator
interfaces. The MSG instruction is a ladder logic output instruction that
asynchronously reads or writes a block of data to or from another module over
the backplane or a network. The size of the instruction depends on the data
types and message command that you program.

Messages use connection resources to send or receive data. Messages can leave
the connection open (cached) or can close the connection when the message is
done transmitting.

Messages can be unconnected or connected. Unconnected messages depend on

the availability of unconnected buffers in all devices through which the
message passes. Connected messages begin with a request to allocate
connection buffers in all of those devices, before sending the actual message. If
you choose to cache a connected message, the controller keeps the connection
open after the message is complete. Cached message improves efficiency if you
intend to send the message repeatedly.

Connected messages use connection resources. If the connected message is

uncached, the resources are used temporarily each time the message is
triggered. As long as a cached connected message remains in the cache, the
resources remain allocated and are not available for other messages. Cached
messages can get pushed from the cache if the application exceeds the cache
capacity of the controller.

Each message uses one connection out of the controller, regardless of how
many devices are in the message path.
Table 16 - Message Types
Message Type Communication Connected Message Message Can Be
Method Cached
CIP data table read or write N/A Configurable Yes(2)
PLC-2, PLC-3, PLC-5, or SLC CIP No No
(all types)
CIP with Source ID No No
DH+ Yes Yes(2)
CIP generic N/A Optional (1) Yes(2)
Block-transfer read or write N/A Yes Yes(2)
(1) You can connect CIP generic messages. However, for most applications we recommend that you leave CIP generic messages
unconnected.
(2) We recommend that you cache connected messages that occur more frequently than once every 60 seconds, if possible.

For more information about how to use messages, see the Logix5000
Controllers Messages Programming Manual, publication 1756-PM012

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 155

Chapter 8 Manage Controller Communication

Determine Whether to Cache Message Connections

When you configure a message instruction, you can cache the connection. Use
Table 17 to decide to cache a connection.
.

Table 17 - Options for Caching Connections

If the message executes Then
Repeatedly Cache the connection.
When you cache the connection, the connection remains open and execution
time is optimized. If a connection is opened each time that the message
executes, execution time is increased.
Infrequently Do not cache the connection.
When you do not cache the connection, the connection closes upon completion
of the message. As a result, the connection is available for other uses.

TIP Cached connections transfer data faster than uncached connections. The
CompactLogix 5380 controller can cache as many as 256 connections.

156 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Chapter 9

Develop Control Applications

Topic Page
Elements of a Control Application 157
Tasks 159
Programs 163
Routines 165
Parameters and Local Tags 166
Programming Languages 167
Add-On Instructions 168
Extended Properties 169
Access the Module Object from an Add-On Instruction 170
Monitor Controller Status 171
Monitor I/O Connections 172

Elements of a A control application consists of several elements that require planning for
efficient application execution. Application elements include the following:
Control Application
Tasks
Programs
Routines
Parameters and Local Tags
Add-On Instructions

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 157

Chapter 9 Develop Control Applications

Figure 21 - Elements of a Control Application

Controller Fault Handler

Task 32

Task 1
Configuration

Status

Program 1000 Watchdog

Program 1 Program Tags

and Program
Main Routine Parameters

Fault Routine

Other Routines

Add-On Instruction
Controller (global) Tags I/O Data System-shared Data
Definition

158 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Develop Control Applications Chapter 9

Tasks A Logix5000 controller lets you use multiple tasks to schedule and prioritize
the execution of your programs based on criteria. This multitasking allocates
the processing time of the controller among the operations in your application:

The controller executes one task at a time.

One task can interrupt the execution of another and take control based
on its priority.

In any given task, you can use multiple programs. One program executes
at a time.

You can display tasks in the Controller or Logical Organizer views, as

necessary.

Figure 22 - Task Within a Control Application

Controller Fault Handler

Task 32

Task 1
Configuration
Status

Watchdog
Program 1000

Program 1
Program Tags
Main Routine and Program
Parameters
Fault Routine
Other
Routines

Controller (global) Add-On Instruction I/O Data System-shared

Tags Definition Data

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 159

Chapter 9 Develop Control Applications

Figure 23 - Tasks

Controller Organizer Logical Organizer

Main Task
(continuous)

Main Task
(continuous)

Task 2
(periodic)
Task 2
(periodic)

A task provides scheduling and priority information for a set of one or more
programs. Use the Task Properties dialog box to configure tasks as continuous,
periodic, or event.

Figure 24 - Configuring the Task Type

160 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Develop Control Applications Chapter 9

Table 18 explains the types of tasks you can configure.

Table 18 - Task Types and Execution Frequency
Task Type Task Execution Description
Continuous Constant The continuous task runs in the background. Any CPU time that is not allocated to other operations (such as motion and
other tasks) is used to execute the programs in the continuous task.
The continuous task runs constantly. When the continuous task completes a full scan, it restarts immediately.
A project does not require a continuous task. If used, you use only one continuous task.
Periodic At a set interval, such as every A periodic task performs a function at an interval.
100 ms Whenever the time for the periodic task expires, the task interrupts any lower priority tasks, executes once, and returns
control to where the previous task left off.
You can configure the time period from 0.12,000,000.00 ms. The default is 10 ms. It is also controller and
configuration dependent.
Event Immediately when an event occurs An event task performs a function when an event (trigger) occurs. The trigger for the event task can be the following:
Module input data change of state
A consumed tag trigger
An EVENT instruction
An axis trigger
A motion event trigger
You can configure an optional timeout interval for missed event triggers. The timeout interval causes the event tasks to
execute even in the absence of the trigger. Set the Check the Execute Task If No Event Occurs Within <timeout period>
checkbox for task.

The CompactLogix 5380 controller supports up to 32 tasks. Only one of the

tasks can be continuous.

A task can have up to 1000 programs, each with its own executable routines
and program-scoped tags. Once a task is triggered (activated), the programs
that are assigned to the task execute in the order in which they are grouped.
Programs can appear only once in the Controller Organizer and multiple tasks
cannot share them.

Event Task with 5069 Compact I/O Modules

Some 5069 Compact I/O modules can trigger an Event task. For example,
complete these steps to configure an Event task with a 5069-IB16F module
input state change triggering the event.

1. Configure the 5069-IB16F input module to trigger the Event task. The
following tasks are required.
a. Use the Data with Events connection type in the 5069-IB16F
module definition.
b. Enable the Event.
c. Select at least one point on the module to participate in the event.
d. Define what constitutes an event, for example, a state change from
Off to On.
e. Choose which edge of the event triggers the event. That is, the rising
edge, falling edge, or both can trigger an event.

You can also latch an event and enable independent point triggers.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 161

Chapter 9 Develop Control Applications

2. Create an Event task in your project.

3. Configure the Event task.
You must choose the event trigger. For example, you can choose
Module Input Data State Change as the trigger.
Link the task to the appropriate Event Input tag on the module.

For more information on how to use event tasks with 5069 Compact I/O
modules, see the 5000 Series Digital I/O Module User Manual, publication
5000-UM004

For more information on how to use event tasks in general, see the Logix5000
Controllers Tasks, Programs, and Routines Programming Manual, publication
1756-PM005.

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. The
continuous task has the lowest priority and a periodic or event task
interrupts it.

You can configure periodic and event tasks to execute from the lowest priority
of 15 up to the highest priority of 1. Use the Task Properties dialog box to
configure the task priority.

Figure 25 - Configure Task Priority

162 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Develop Control Applications Chapter 9

Programs The controller operating system is a preemptive multitasking system that is in

compliance with IEC 61131-3. This system provides the following:
Programs to group data and logic
Routines to encapsulate executable code that is written in one
programming language

Each program contains the following:

Local Tags
Parameters
A main executable routine
Other routines
An optional fault routine

Figure 26 - Program Within a Control Application

Controller Fault Handler

Task 32

Task 1
Configuration

Status

Watchdog
Program 1000

Program 1
Program Tags
Main Routine and Program
Parameters

Fault Routine

Other Routines

Add-On Instruction
Controller (global) Tags I/O Data System-shared Data
Definition

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 163

Chapter 9 Develop Control Applications

Figure 27 - Scheduled and Unscheduled Programs

Controller Organizer Logical Organizer

The scheduled programs within a task execute to completion from first to last.
Programs that are not attached to any task show up as unscheduled programs.

Unscheduled programs within a task are downloaded to the controller with the
entire project. The controller verifies unscheduled programs but does not
execute them.

You must schedule a program within a task before the controller can scan the
program. To schedule an unscheduled program, use the Program/
Phase Schedule tab of the Task Properties dialog box.

Figure 28 - Scheduling an Unscheduled Program

164 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Develop Control Applications Chapter 9

Routines A routine is a set of logic instructions in one programming language, such as

Ladder Diagram (ladder logic). Routines provide the executable code for the
project in a controller.

Each program has a main routine. The main is the first routine to execute when
the controller triggers the associated task and calls the associated program. Use
logic, such as the Jump to Subroutine ( JSR) instruction, to call other routines.

You can also specify an optional program fault routine. The controller executes
this routine if it encounters an instruction-execution fault within any of the
routines in the associated program.

Figure 29 - Routines in a Control Application

Controller Fault Handler

Task 32

Task 1
Configuration

Status

Watchdog
Program 1000

Program 1
Program Tags
and Program
Main Routine
Parameters

Fault Routine

Other Routines

Controller (global) Tags Add-On Instruction I/O Data System-shared Data

Definition

Figure 30 - Routines
Controller Designer Logical Designer

Routine
Routine

Routine Routine

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 165

Chapter 9 Develop Control Applications

Parameters and Local Tags With a Logix5000 controller, you use a tag (alphanumeric name) to address
data (variables). In Logix5000 controllers, there is no fixed, numeric format.
The tag name identifies the data and 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 within the scope of the Main
Program of the controller.

Figure 31 - Tags Example

Controller Organizer Main Program Parameters and Local Tags

Program Tags WindowMain Program Parameters and Local Tags

Analog I/O Device

Integer Value
Storage Bit
Counter
Timer
Digital I/O Device

There are several guidelines for how to create and configure 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.

166 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Develop Control Applications Chapter 9

Programming Languages The Logix Designer application supports these programming languages.

Language Is best used in programs with

Ladder Diagram (LD) Continuous or parallel execution of multiple operations (not sequenced)
Boolean or bit-based operations
Complex logical operations
Message and communication processing
Machine interlocking
Operations that service or maintenance personnel have to interpret to
troubleshoot the machine or process
Function Block Diagram (FBD) Continuous process and drive control
Loop control
Calculations in circuit flow
Sequential Function Chart (SFC) High-level management of multiple operations
Repetitive sequence of operations
Batch process
Motion control that uses structured text
State machine operations
Structured Text (ST) Complex mathematical operations
Specialized array or table loop processing
ASCII string handling or protocol processing

For information about programming in these languages, see the

Logix5000 Controllers Common Procedures Programming Manual,
publication 1756-PM001.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 167

Chapter 9 Develop Control Applications

Add-On Instructions With the Logix Designer application, you can design and configure sets of
commonly used instructions to increase project consistency. Similar to the
built-in instructions that are 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 creating logic for one instance.
Apply source protection to help protect intellectual property.
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.

Table 19 explains some of the capabilities and advantages of use Add-On

Instructions.
Table 19 - Add-On Instruction Capabilities
Capability Description
Save Time With Add-On Instructions, you can combine your most commonly used logic into sets of reusable instructions. You save time when
you create instructions for your projects and share them with others. Add-On Instructions increase project consistency because
commonly used algorithms all work in the same manner, regardless of who implements the project.
Use Standard Editors You use one of these editors to create Add-On Instructions:
Ladder Diagram
Function Block Diagram
Structured Text
Export Add-On Instructions You can export Add-On Instructions to other projects and copy and paste them from one project to another. Give each instruction a
unique, descriptive name to make it easier to manage and reuse your collection of Add-On Instructions.
Use Context Views Context views let you visualize the logic of an instruction to perform instant and simple online troubleshooting of your Add-On
Instructions.
Document the Instruction When you create an instruction, you enter information for the description fields. Each instruction definition includes revision, change
history, and description information. The description text also becomes the help topic for the instruction.
Apply Source Protection When you create Add-On Instructions, you can limit users of your instructions to read-only access. You can also bar access to the
internal logic or local parameters that the instructions use. This source protection lets you stop unwanted changes to your
instructions and helps protect your intellectual property.

Once defined in a project, Add-On Instructions behave similarly to the built-in

instructions in Logix5000 controllers. They appear on the instruction tool bar
for easy access along with internal instructions.

Figure 32 - Add-On Instructions

Controller Organizer

Instruction Toolbar

168 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Develop Control Applications Chapter 9

Extended Properties The Extended Properties feature lets you define more information, such as
limits, engineering units, or state identifiers for various components within the
controller project.

Component Extended Properties

Tag In the tag editor, add extended properties to a tag.
User-defined data type In the data type editor, add extended properties to data types.
Add-On Instructions In the properties that are associated with the Add-On Instruction definition,
add extended properties to Add-On Instructions.

Pass-through behavior is the ability to assign extended properties at a higher

level of a structure or Add-On Instruction and have that extended property
automatically available for all members. Pass-through behavior is available for
descriptions, state identifiers, and engineering units and you can configure it.

Configure pass-through behavior on the Project tab of the Controller

Properties dialog box. If you choose not to show pass-through properties, only
extended properties that are configured for a given component are displayed.

Pass-through behavior is not available for limits. When an instance of a tag is

created, if limits are associated with the data type, the instance is copied.

Use the .@Min and .@Max syntax to define tags that have limits. There is no
indication in the tag browser that limits extended properties are defined for a
tag. If 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. Visual
indicators include:
A rung error in Ladder Logic.
A verification error X in Function Block Diagrams.
The error underlined in Structured Text.

You can access limit extended properties that the .@Min and .@Max syntax
defines. However, you cannot write to extended properties values in logic.

For more information on Extended Properties, see the Logix5000 Controllers

I/O and Tag Data Programming Manual, publication 1756-PM004.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 169

Chapter 9 Develop Control Applications

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
from an Add-On Instruction 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.

Create the Add-On Instruction

You can access a MODULE object directly from an Add-On Instruction.

Previously, you could access the MODULE object data but not from within an
Add-On Instruction.

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 Logix
Designer application online help and the Logix5000 Controllers Add-On
Instructions Programming Manual, publication 1756-PM010.

The MODULE object uses the following attributes to provide status

information:
EntryStatus
FaultCode
FaultInfo
FWSupervisorStatus
ForceStatus
Instance
LEDStatus
Mode
Path

170 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Develop Control Applications Chapter 9

Monitor Controller Status The CompactLogix 5380 controller uses Get System Value (GSV) and Set
System Value (SSV) instructions to get and set (change) controller data. The
controller stores system data in objects. There is no status file, as in the PLC-5
processor.

The GSV instruction retrieves the specified information and places it in the
destination. The SSV instruction sets the specified attribute with data from the
source. Both instructions are available from the Input/Output tab of the
Instruction toolbar.

Figure 33 - GSV and SSV Instructions for Monitoring and Setting Attributes

When you add a GSV/SSV instruction to the program, the object classes,
object names, and attribute names for the instruction are shown. For the GSV
instruction, you can get values for the available attributes. For the SSV
instruction, only the attributes that you can set are shown.

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.

The GSV and SSV instructions monitor and set many objects and attributes.
See the online help for the GSV and SSV instructions.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 171

Chapter 9 Develop Control Applications

Monitor 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,
search the Rockwell Automation Knowledgebase for answer ID 38535. The
document is available at http://www.rockwellautomation.com/
knowledgebase.

When a timeout does occur, the controller produces these warnings;

I/O Fault status information scrolls across the 4-character status display
of the controller.

A ! shows over the I/O configuration folder and over the devices that
have timed out.

A module fault code is produced. You can access the fault code via the
following:
The Module Properties dialog box
A GSV instruction

For more information about I/O faults, see the Logix5000 Controllers Major,
Minor, and I/O Faults Programming Manual, publication 1756-PM014.

172 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Develop Control Applications Chapter 9

Determine If I/O Communication Has Timed Out

This example can be used with the CompactLogix 5380 controllers:

The GSV instruction gets the status of the I/O status indicator (via the
LEDStatus attribute of the Module object) and stores it in the
IO_LED tag.

IO_LED is a DINT tag that stores the status of the I/O status indicator
or status display on the front of the controller.

If IO_LED equals 2, at least one I/O connection has been lost and the
Fault_Alert is set.

Figure 34 - GSV Used to Identify I/O Timeout

Determine if I/O Communication to a Specific I/O Module has

Timed Out

If communication times out with a device (module) in the I/O configuration

of the controller, the controller produces a fault code and fault information for
the module. You can use GSV instructions to get fault code and information
via the FaultCode and FaultInfo attributes of the Module object.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 173

Chapter 9 Develop Control Applications

Automatic Handling of I/O Module Connection Faults

You can use 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.

It can be important to interrupt your normal program scan to handle an I/O

connection fault. In this case, set the 'Major Fault On Controller If
Connection Fails While In Run Mode' and put the logic in the Controller
Fault Handler.

Figure 35 - I/O Connection Fault Causes Major Fault

You can configure the application so that a response to a failed I/O module
connection can wait until the next program scan. In this case, put the logic in a
normal routine and use the GSV technique that is described on page 173 to
call the logic.

First, develop a routine in the Controller Fault Handler that can respond to
I/O connection faults. Then, in the Module Properties dialog box of the I/O
module or parent communication module, check Major Fault On Controller If
Connection Fails While in Run Mode.

It takes at least 100 milliseconds to detect an I/O connection loss, even if the
TIP
Controller Fault Handler is used.

For more information about programming the Controller Fault Handler, see
the Logix5000 Major, Minor, and I/O Faults Programming Manual,
publication 1756-PM014.

174 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Develop Control Applications Chapter 9

Sample Controller Projects

Logix Designer includes sample projects that you can copy and modify to fit
your application. To access the sample projects, click Sample Project in the
Studio 5000 environment interface as shown and navigate to
Samples > ENU > v29 > Rockwell Automation.

Figure 36 - Open Sample Projects

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 175

Chapter 9 Develop Control Applications

Notes:

176 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Chapter 10

Develop Motion Applications

Topic Page
Motion Overview 178
Motion Applications 179
Obtain Axis Information 182
Program Motion Control 180

Some CompactLogix 5380 controllers support Integrated Motion over an

EtherNet/IP network on digital and integrated motion interfaces. Consider
the following:
The controllers support the following number of integrated
motion axes:
5069-L306ERM: 2
5069-L310ERM: 4
5069-L320ERM: 8
5069-L330ERM: 16
5069-L340ERM: 20
5069-L350ERM: 24
5069-L380ERM: 28
5069-L3100ERM: 32

Digital drive interfaces include EtherNet/IP connected drives.

Integrated Motion over an EtherNet/IP network supports

the following:
Kinetix 350 drives
Kinetix 5500 drives
Kinetix 5700 drives
Kinetix 6500 drives
PowerFlex 527 drives
PowerFlex 755 drives

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 177

Chapter 10 Develop Motion Applications

All CompactLogix 5380 controllers support single-axis motor control

with PowerFlex variable frequency drives over an EtherNet/IP network.

This functionality is available on CompactLogix 5380 controllers that

do not support other aspects of Integrated Motion over an EtherNet/IP
network.

For more information, see the following:

Integrated Motion on the EtherNet/IP network Configuration and

Startup User Manual, publication MOTION-UM003.

Integrated Motion on the EtherNet/IP network Reference Manual,

Publication MOTION-RM003.

Motion Overview The CompactLogix 5380 controllers support the following Integrated Motion
axes types:
CIP - As many as 32 Position Loop axes are supported
Virtual
Consumed

You can use any combination of CIP, Virtual, and Consumed axes. You can add
all axes to one Motion Group, and you can assign any combination of axes to
different axis update schedules.

IMPORTANT The CompactLogix 5380 controllers do not support Analog or

SERCOS motion.

You can associate Integrated Motion axes to any appropriate drive.

178 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Develop Motion Applications Chapter 10

Motion Applications The following are general steps to configure a motion application. The
configuration process varies, based on your application and drive selection.

1. Create a controller project.

2. Add a drive to the I/O configuration of the project.
3. Create and configure logical Axes, and associate them with physical
drives or virtual axes.
4. Create and configure a Motion Group.
5. Assign Axes to the Motion Group.
6. Specify the motor data source.
7. Display the motor model information.
8. Assign Motor Feedback.
9. Configure the load feedback.
10. Configure the master feedback.
11. Commission an axis.
12. Home an axis.
13. Optionally create and configure Coordinate Systems.
14. Write user logic to control motion.
15. Optionally tune the physical drives for the attached loads.

For more information on how to configure a motion application, see the

Integrated Motion on the EtherNet/IP Network Configuration and Startup
User Manual, publication MOTION-UM003.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 179

Chapter 10 Develop Motion Applications

Program Motion Control The controller provides a set of motion control instructions for your axes:

The controller uses these instructions just like the rest of the Logix5000
instructions.

Each motion instruction works on one or more axes.

Each motion instruction needs a motion control tag. The tag uses a
MOTION_INSTRUCTION data type and stores the information
status of the instruction.

You can use motion control instructions in these

programming languages:
Ladder Diagram (LD)
Structured Text (ST)
Sequential Function Chart (SFC)

For more information, see the Logix5000 Controller Motion Instructions

Reference Manual, publication MOTION-RM002.

Figure 37 - Motion Control Instruction

Motion Control Tag

ATTENTION: Use each motion control tag in only one motion instruction.
Unintended operation can result if you reuse the same motion control tag in
other motion instructions, or if you write to any of the motion control tag
elements.

180 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Develop Motion Applications Chapter 10

Example

In this example, a simple ladder diagram that homes, jogs, and moves an axis.

If Initialize_Pushbutton = on and the axis = off (My_Axis_X.ServoActionStatus = off), the MSO instruction turns on the axis.

If Home_Pushbutton = on and the axis hasnt been homed (My_Axis_X.AxisHomedStatus = off), the MAH instruction homes the axis.

If Jog_Pushbutton = on and the axis = on (My_Axis_X.ServoActionStatus = on), the MAJ instruction jogs the axis forward at 8 units/second.

If Jog_Pushbutton = off, the MAS instruction stops the axis at 100 units/.second2. Make sure that Change Decel is Yes. Otherwise, the axis decelerates at
its maximum speed.

If Move_Command = on and the axis = on (My_Axis_X.ServoActionStatus = on), the MAM instruction moves the axis. The axis moves to the position of
10 units at 1 unit/second.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 181

Chapter 10 Develop Motion Applications

Obtain Axis Information You can obtain axis information via the following methods:

Double-click the axis to open the Axis Properties dialog box.

Use a Get System Value (GSV) or Set System Value (SSV) instruction to
read or change the configuration at runtime.

View the QuickView pane to see the state and faults of an axis.

Use an axis tag for status and faults.

Figure 38 - Obtain Axis Information

Axis Properties Dialog Box

SSV (or GSV) Instruction

Axis Tag

Quick View Pane

182 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Chapter 11

Troubleshoot the Controller

Topic Page
Controller Diagnostics with Logix Designer 183
Controller Diagnostics with RSLinx Software 197
Controller Web Pages 202
Other Potential Issues to Troubleshoot 210

This chapter describes how to troubleshoot the controller if issues occur during
normal operation. In addition to the ways described in this chapter, you can use
messages on the 4-character display to troubleshoot the controller.

For more information, see Appendix A, Status Indicators on page 211.

Controller Diagnostics with You can use the Controller Properties in Logix Designer to view fault
conditions in the following ways:
Logix Designer
Warning Symbol in the I/O Configuration Tree

Categories on I/O Module Properties Dialog Box

Notification in the Tag Editor

Fault Information in Controller Properties Dialog Box

Port Diagnostics

Advanced Time Sync

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 183

Chapter 11 Troubleshoot the Controller

Warning Symbol in the I/O Configuration Tree

A warning symbol appears in the I/O Configuration tree when a module

fault occurs.

Figure 39 - Warning Symbol on I/O Module

Controller Status Indicators

Your project configuration determines if an I/O module fault causes a

controller fault. You enable the option on the Connection category of the
Module Properties dialog box.

Figure 40 - Enable Major Fault on Controller

184 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Troubleshoot the Controller Chapter 11

The following conditions are possible:

When the I/O module is configured to cause a major fault on the
controller and an I/O module fault occurs, the following can result:
Controller state displays Faulted.
Controller status displays Controller Fault and is steady red.
I/O module status displays I/O Not Responding and blinks green.

IMPORTANT The descriptions in the Logix Designer application can change based
on the controller mode and status.

When the I/O module is not configured to cause a major fault on the
controller and an I/O module fault occurs, the following result:
Controller state displays the current state, for example, Rem Run.
Controller status displays Controller OK and is steady green.
I/O module status displays I/O Not Responding and blinks green.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 185

Chapter 11 Troubleshoot the Controller

Categories on I/O Module Properties Dialog Box

The Module Properties dialog box for I/O modules includes a series of
categories. You can use some of the categories to troubleshoot the controller.

IMPORTANT The number and type of categories varies by I/O module type.

The following are examples of ways to use categories on the Module Properties
dialog box when you troubleshoot a controller:

Module Status on General Category

Module Fault Descriptions on Connection Category

Module Fault Descriptions on Module Info Category

Diagnostics Option on Module Info Category

The categories described in this section display the module status. When a
fault exists, the text is Status: Faulted in the module status line as shown in
Figure 41.

Module Status on General Category

The General category displays the module status.

Figure 41 - Module Status in Fault Message Line

186 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Troubleshoot the Controller Chapter 11

Module Fault Descriptions on Connection Category

The Connection category displays the module fault description that includes
an error code that is associated with the specific fault type.

Figure 42 - Fault Description with Error Code

Module Fault Descriptions on Module Info Category

When you click the Module Info category, a dialog box displays the module
fault description and the corresponding fault code. Click OK to access the
Module Info category.

TIP The Module Info tab requires successful communications to help you
troubleshoot the fault effectively. Consider the following:
If communication to the I/O module is OK, but the module is faulted, we
recommend that you use the Module Info category to troubleshoot the
fault.
If communication to the I/O module is faulted, we recommend that you
use the Connection category to troubleshoot the fault.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 187

Chapter 11 Troubleshoot the Controller

On the Module Info category, the Status section displays the following about
the I/O module:
Major and Minor Faults
Internal State

Figure 43 - Major and Minor Fault Information

188 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Troubleshoot the Controller Chapter 11

Diagnostics Option on Module Info Category

You can access the diagnostics for a module from the Module Info category.
Click Diagnostics, to access the Module Diagnostics dialog box.

Figure 44 - Module Diagnostics

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 189

Chapter 11 Troubleshoot the Controller

Notification in the Tag Editor

General and diagnostic module faults are reported in the Tag Editor of your
Logix Designer application project.

The Value field indicates a fault with the number 1.

Fault Information in Controller Properties Dialog Box

You can use the following tabs on the Controller Properties dialog box to
troubleshooting the controller:
Major Faults
Minor Faults
Network

Major Faults

You can monitor information about recent major faults and also clear major
faults on the Major Faults tab.

Figure 45 - Major Faults Tab in Controller Properties Dialog Box

190 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Troubleshoot the Controller Chapter 11

Minor Faults

You can monitor information about recent minor faults and also clear minor
faults on the Minor Faults tab.

Figure 46 - Minor Faults Tab in Controller Properties Dialog Box

Network

Typically, the Network tab is used to monitor for faults that occur when the
controller is used in a DLR network.

IMPORTANT The Network tab is not available when the controller operates in
Dual-IP mode.

Figure 47 - Network Tab in Controller Properties Dialog Box

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 191

Chapter 11 Troubleshoot the Controller

Port Diagnostics

When your project is online, you can view the status of the embedded Ethernet
ports on the controller.

1. Access the Controller Properties.

2. On the Port Configuration tab, click the Port Diagnostics button for an
active port.

The Port Diagnostics page, displays information for the port. See
Table 20 on page 193 for parameter descriptions.

192 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Troubleshoot the Controller Chapter 11

Table 20 - Port Diagnostics Parameters - Logix Designer

Parameter Description
Interface Counters The Interface Counters values have no value when you are offline or online
and there is a communication error.
Octets Inbound Displays the number of octets that are received on the interface.
Octets Outbound Displays the number of octets that are transmitted to the interface.
Unicast Packets Inbound Displays the number of unicast packets that are received on the interface.
Unicast Packets Outbound Displays the number of unicast packets that are transmitted on the interface.
Non-unicast Packets Inbound Displays the number of non-unicast packets that are received on the
interface.
Non-unicast Packets Outbound Displays the number of non-unicast packets that are transmitted on the
interface.
Packets Discarded Inbound Displays the number of inbound packets that are received on the interface
but discarded.
Packets Discarded Outbound Displays the number of outbound packets that are transmitted on the
interface but discarded.
Packets With Errors Inbound Displays the number of inbound packets that contain errors (excludes
discarded inbound packets).
Packets With Errors Outbound Displays the number of outbound packets that contain errors (excludes
discarded outbound packets).
Unknown Protocol Packets Inbound Displays the number of inbound packets with unknown protocol.
Media Counters The Media Counters values have no value when you are offline or online and
there is a communication error.
Alignment Errors Displays the number of frames received that are not an integral number of
octets in length.
FCS Errors Displays the number of frames received that do not pass the FCS check.
Single Collisions Displays the number of successfully transmitted frames that experienced
exactly one collision.
Multiple Collisions Displays the number of successfully transmitted frames that experienced
multiple collisions.
SQE Test Errors Displays the number of times an SQE test error message was generated.
Deferred Transmissions Displays the number of frames for which the first transmission attempt is
delayed because the medium is busy.
Late Collisions Displays the number of times a collision is detected later than 512 bit-times
into the transmission of a packet.
Excessive Collisions Displays the number of frames for which transmission fails due to excessive
collisions.
MAC Transmit Errors Displays the number of frames for which transmission fails due to an internal
MAC sub layer transmit error.
MAC Receive Errors Displays the number of frames for which reception on an interface fails due
to an internal MAC sub layer receive error.
Carrier Sense Displays the number of times that the carrier sense condition was lost or
never asserted when attempting to transmit a frame.
Frame Too Long Displays the number of frames received that exceed the maximum permitted
frame size.
Reset Counters Click Reset Counter to cause the interface and media counter values on the
module to set to zero, and the values in the dialog to update.
Reset Counter appears dimmed when:
offline
online and a communication error has occurred

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 193

Chapter 11 Troubleshoot the Controller

Advanced Time Sync

The Advanced Time Sync dialog displays information that is related to CIP
Sync time synchronization.

IMPORTANT The information appears only if the project is online and Time
Synchronization is enabled on the Date/Time tab. Also, when the controller
operates in Dual-IP mode, the Advanced Time Sync tab shown below
provides data for each port.

1. On the Date/Time tab, click the Advanced button.

The Advanced Time Sync dialog box opens. See Table 21 on page 195
for parameter descriptions.

194 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Troubleshoot the Controller Chapter 11

Table 21 - Time Sync Parameters

Grandmaster Clock
Description Displays information about the Grandmaster clock. The vendor of the Grandmaster device
controls this information. The following information is specified:
User Name
User Location
Protocol Address
Physical Address
Clock Type
Manufacturer Name
Model
Serial Number
Hardware Revision
Firmware Revision
Software Version
Profile Identity
Physical Protocol
Network Protocol
Port Number
Use the vertical scroll bar to view the data.
Identity Displays the unique identifier for the Grandmaster clock. The format depends on the
network protocol. Ethernet network encodes the MAC address into the identifier.
Class Displays a measure of the quality of the Grandmaster clock. Values are defined from
0255 with zero as the best clock.
Accuracy Indicates the expected absolute accuracy of the Grandmaster clock relative to the PTP
epoch. The accuracy is specified as a graduated scale that starts at 25 nsec and ends at
greater than 10 seconds or unknown. The lower the accuracy value, the better the clock.
Variance Displays the measure of inherent stability properties of the Grandmaster clock. The value
is represented in offset scaled log units. The lower the variance, the better the clock.
Source Displays the time source of the Grandmaster clock. The available values are:
Atomic Clock
GPS
Radio
PTP
NTP
HAND set
Other
Oscillator
Priority 1 / Priority 2 Displays the relative priority of the Grandmaster clock to other clocks in the system. The
priority values range from 0255. The highest priority is zero. The default value for both
settings is 128.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 195

Chapter 11 Troubleshoot the Controller

Table 21 - Time Sync Parameters (Continued)

Local Clock
Synchronization Status Displays whether the local clock is synchronized or not synchronized with the
Grandmaster reference clock. A clock is synchronized if it has one port in the slave state
and is receiving updates from the time master.
Offset to Master Displays the amount of deviation between the local clock and the Grandmaster clock in
nanoseconds.
Backplane State Displays the current state of the backplane. The available values are as follows:
Initializing
Faulty
Disabled
Listening
PreMaster
Master
Passive
Uncalibrating
Slave
None
Ethernet State Displays the state of the Ethernet port. The available values are as follows:
Initializing
Faulty
Disabled
Listening
PreMaster
Master
Passive
Uncalibrating
Slave
None
IMPORTANT: When the controller operates in Dual-IP mode, this attribute provides data
for each controller port. The fields appear as follows:
A1, Ethernet State
A2, Ethernet State
Identity Displays the unique identifier for the local clock. The format depends on the network
protocol. Ethernet network encodes the MAC address into the identifier.
Class Displays a measure of quality of the local clock. Values are defined from 0255, with
zero as the best clock.
Accuracy Indicates the expected absolute accuracy of the local clock relative to the PTP epoch. The
accuracy is specified as a graduated scale that starts at 25 nsec and ends at greater than
10 seconds or unknown. The lower the accuracy value, the better the clock.
Variance Displays the measure of inherent stability properties of the local clock. The value is
represented in offset scaled log units. The lower the variance, the better the clock.
Source Displays the time source of the local clock. The available values are:
Atomic Clock
GPS
Terrestrial Radio
PTP
NTP
HAND set
Other
Oscillator

196 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Troubleshoot the Controller Chapter 11

Controller Diagnostics with You can also view diagnostic information in RSLinx Classic software.
RSLinx Software 1. Use the RSWho button to browse.
2. Navigate to the Ethernet network.
3. Right-click the controller and choose Module Statistics.

General Tab

The General tab shows device information, and any faults on the controller.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 197

Chapter 11 Troubleshoot the Controller

Port Diagnostics Tab

The Port Diagnostics tab shows information for the port. See Table 22 on
page 198 for parameter descriptions.

Table 22 - Port Diagnostics Parameters - RSLinx

Parameter Description
Interface Counters Provides information relevant to receipt of packets on the interface
In Octets Octets received on the interface.
Out Octets Octets sent out from the interface.
In Ucast Packets Unicast packets that are received on the interface.
Out Ucast Packets Unicast packet sent out from the interface.
In NUcast Packets Non-unicast packets that are received on the interface.
Out NUcast Packets Non-unicast packets sent out from the interface.
In Discards Inbound packets that were received on the interface but discarded.
Out Discards Outbound packets that were sent out from the interface but were discarded.
In Errors Inbound packets that contain errors (excludes In Discards).
Out Errors Outbound packets that contain errors.
In Unknown Protos Inbound packets with unknown protocol.

198 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Troubleshoot the Controller Chapter 11

Table 22 - Port Diagnostics Parameters - RSLinx (Continued)

Parameter Description
Media Counters Provides information specific to Ethernet media you are using
Alignment Errors Frames received that are not an integral number of octets in length.
FCS Errors Frames received that do not pass the FCS (Frame Check Sequence) check.
Single Collisions Successfully transmitted frames that experienced exactly one collision.
Multiple Collisions Successfully transmitted frames that experienced multiple collision.
SQE Test Errors Number of times an SQE test error message was generated.
Deferred Transmissions Frames for which the first transmission attempt is delayed because the medium is
busy.
Late Collisions Number of times a collision is detected later than 512 bit-times into the transmission
of a packet.
Excessive Collisions Frames for which transmission fails due to excessive collisions.
MAC Transmit Errors Frames for which transmission fails due to an internal MAC sub layer transmit error.
MAC Receive Errors Frames for which reception on an interface fails due to an internal MAC sub layer
receive error.
Carrier Sense Times that the carrier sense condition was lost or never asserted when attempting to
transmit a frame.
Frame Too Long Frames received that exceed the maximum permitted frame size.
Reset Counters Click Reset Counter to cause the interface and media counter values on the module to
set to zero, and the values in the dialog to update.
Reset Counter appears dimmed when either of the following conditions exist:
The project is offline.
The project is online and a communication error has occurred.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 199

Chapter 11 Troubleshoot the Controller

Connection Manager Tab

See Table 23 for a description of the Connection Manager properties.

Table 23 - Connection Manager Properties

Field Description
Requests Number of open/close connection requests that this module has received.
Format Rejects Number of open/close connection requests that this module has rejected because the
request was not formatted correctly or because some parameter value was not within a
supported range of values.
Resource Rejects Number of open connection requests that this module has rejected because the module
did not have enough resources (buffers, link bandwidth, or CPU utilization) to honor the
request.
Other Rejects Number of open/close connection requests a module rejects.
Timeouts Number of connections that the connection originator has not explicitly closed but were
closed by this module because they were not being used.

200 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Troubleshoot the Controller Chapter 11

USB Tab
The USB tab provides the following information about the controller
USB port.

Table 24 - General Information

Attribute Name Description
State State (Initializing, Fault, Initialized, Configured, Ready, and Reserved) of the USB interface.
Suspend The USB interface was suspended by the host.
Disabled The USB interface was disabled by the host.
Logical Address Logical address of the USB interface (slot number in the virtual backplane).
Bus Speed The highest USB bus speed the USB interface supports.
OTG Support USB On The Go (OTG) capability support.
Mode The operating mode (slave/host) of the USB interface, if the interface supports OTG.

Table 25 - Interface Counters provide diagnostic information in the USB-CIP layer

Counter Name Description
Rx Good Counter Total number of good USB-CIP transfers received.
Rx Bad Counter Total number of bad USB-CIP transfers received.
Rx Dropped Counter Total number of dropped USB-CIP transfers.
Tx Good Counter Total number of USB-CIP transfers sent.
Tx Retry Counter Total number of USB-CIP transfers retried.
Tx Dropped Counter Total number of USB-CIP transfers dropped.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 201

Chapter 11 Troubleshoot the Controller

Table 26 - Media Counters provide diagnostic information in the USB driver layer.
Counter Name Description
Rx Byte Counter Total number of bytes received.
Rx Dropped Counter Total number of received bytes dropped.
Tx Byte Counter Total number of bytes sent.
Tx Dropped Bytes Total number of transmit bytes dropped.
FIFO Overflow Total number of FIFO (First in First Out) overflows.

Controller Web Pages The controller provides diagnostic web pages that track controller
performance, network performance, and backplane performance.

To access the diagnostic web pages, follow these steps.

1. Open your web browser.

2. In the Address field, type the IP address of the controller and
press Enter.
3. Use the links in the left-side navigation bar to access the information
that you need.

IMPORTANT The controller web pages are slightly different based on the EtherNet/IP
mode that is used. The web pages look different and provide different
information.
For example, consider the following:
When the controller operates in Linear/DLR mode, the left-side
navigation bar displays a Ethernet Port A1/A2 folder with three tabs.
There is one Ethernet Port web page for both ports, and the controller
web pages provide one set of Ethernet data.
When the controller operates in Dual-IP mode, the left-side navigation
bar displays an Ethernet Port A1 folder and an Ethernet Port A2 folder.
Each folder has three tabs.
There is an Ethernet Port web page for each port, and the controller web
pages provide one set of Ethernet data for port A1 and another set of
Ethernet data for port A2.

202 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Troubleshoot the Controller Chapter 11

Home Web Page

The Home web page provides general project and controller information.

Linear/DLR Mode

Dual-IP Mode

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 203

Chapter 11 Troubleshoot the Controller

Tasks Web Page

On the Tasks web page, the pie chart shows the percentage of the control core's
CPU consumed by the tasks that are on that core. The gauges show the CPU
utilization of the control and communications cores.

This web page is not available with CompactLogix 5370 L3 controllers.

The table shows the tasks that are running on the Control core (all system tasks
are summarized as one task).

204 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Troubleshoot the Controller Chapter 11

Diagnostics Web Pages

The Diagnostics web pages use a series of tabs to provide information about
the following:
Module Diagnostics
Application Connections
Bridge Connections
Ring Statistics

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 205

Chapter 11 Troubleshoot the Controller

Ethernet Port Web Pages

The Ethernet Port web pages use a series of tabs to provide information about
the following:
Diagnostic Overview
Network Settings
Ethernet Statistics

Linear/DLR Mode

Dual-IP Mode

206 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Troubleshoot the Controller Chapter 11

Advanced Diagnostics Web Pages

The Advanced Diagnostics web pages provide information about

the following:
TCP/IP Network - Provide information about the following:
ICMP Statistics
IP Statistics
UDP Statistics
TCP Statistics
TCP Connection
UDP Table

Ethernet Port A1/A2- Provide information about the following:

Interface Statistics
ARP Table
IP Route Table

IMPORTANT This information is listed separately for, and is unique to, each port
when the controller operates in Dual-IP mode.

1588 PTP (Time Sync)

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 207

Chapter 11 Troubleshoot the Controller

Linear/DLR Mode

Dual-IP Mode

208 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Troubleshoot the Controller Chapter 11

Browse Chassis Web Page

The Browse Chassis provides information about the devices in the system. You
can click the link for each catalog number to access more information about
that device.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 209

Chapter 11 Troubleshoot the Controller

Other Potential Issues to Your CompactLogix 5380 controller can experience other issues that you can
experience, and need to troubleshoot, in your CompactLogix 5380 system.
Troubleshoot

Continuous Task Sends Output Data at High Rate

A free-running Continuous Task can keep sending outputs at a very high rate.
If the Continuous Task executes repetitively with a very short task execution
time, and local output or produced data is changing, the controller can produce
data faster than the receiving modules can react. We recommend that you
program appropriately to avoid this condition.

Immediate Output Instructions Issued at High Rate

CompactLogix 5380 controllers can issue Immediate Output (IOT)

instructions faster than I/O modules can react to them. We recommend that
you program IOT instructions so that they are sent at a rate appropriate for the
I/O module and the corresponding physical devices.

Integrated Motion On an EtherNet/IP Network Traffic

Priority Status

When you use a Stratix managed switch to change the network

communication rate from 1 Gbps to 100 Mbps, the system can fail to prioritize
the Integrated Motion On an EtherNet/IP network communication higher
than standard I/O communication.

For more information on when to use a Stratix managed switch to change the
network communication rate from 1 Gbps to 100 Mbps, see page 121.

For more information on managed switches in general, see the EtherNet/IP

Network section of the product directory accessible at this address:
http://ab.rockwellautomation.com/networks-and-communications/ethernet-
ip-network.

210 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Appendix A

Status Indicators

Topic Page
4-Character Status Display 212
Controller Status Indicators 221
EtherNet/IP Status Indicators 223
Power Status Indicators 224
Thermal Monitoring and Thermal Fault Behavior 225

The CompactLogix 5380 controllers have a four-character scrolling status

display, controller status indicators, EtherNet/IP network status indicators,
and power indicators.

Figure 48 - Status Display and Indicators

4-Character Scrolling Status Power Status Indicators,

Display, see page 212 see page 224

Controller Status Indicators, EtherNet/IP Status

see page 221 Indicators, see page 223

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 211

Appendix A Status Indicators

4-Character Status Display The CompactLogix 5380 controller 4-character status display scrolls messages
that provide information about the following:
Firmware revision
Energy storage status
Project status
Ethernet port status
Major faults of the controller
Local I/O faults information

General Status Messages

Table 27 describes the messages.

Table 27 - General Status Messages
Message Interpretation
No message is The controller is Off.
indicated Check the MOD POWER status indicator to see if power is applied to the system.
Check the OK indicator to determine if the controller is powered and to determine the
state of the controller.
TEST The controller is conducting power-up tests.
CHRG The embedded energy storage circuit is charging.
PASS Power-up tests have completed successfully.
Saving...Do Not The controller is about to save an image to the SD card.
Remove SD Card
SAVE A project is being saved to the SD card. For more information, see SD Indicator on
page 222.
Let the save operation complete before you take the following actions:
Remove the SD card.
Disconnect the power.
IMPORTANT: Do not remove the SD card while the controller is saving to the SD card. Let
the save complete without interruption. If you interrupt the save, data corruption or loss
can occur.
One of the following: A project is being loaded from the SD card. For more information, see SD Indicator on
LOAD page 222.
Let the load operation complete before doing the following:
Loading . . . Do Not Remove the SD card
Remove SD Card
Disconnect the power
IMPORTANT: Do not remove the SD card while the controller is loading from the SD card.
Let the load complete without interruption. If you interrupt the load, data corruption or
loss can occur.
UPDT A firmware update is being conducted from the SD card upon powerup. For more
information, see SD Indicator on page 222.
If you do not want the firmware to update upon powerup, change the Load Image
property of the controller.
Rev XX.xxx The firmware major and minor revision of the controller.
5069-L3xxx The controller catalog number and series.

212 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Status Indicators Appendix A

Table 27 - General Status Messages (Continued)

Message Interpretation
Link Down Message appears when an EtherNet/IP port does not have a network connection.
Message scrolls continuously during operation.
IMPORTANT: When the controller operates in Dual-IP mode, this information is provided
for each link, that is, Link A1 and Link A2. The link name appears before the information.
Link Disabled Message appears when you have disabled an EtherNet/IP port. Message scrolls
continuously during operation.
IMPORTANT: When the controller operates in Dual-IP mode, this information is provided
for each link, that is, Link A1 and Link A2. The link name appears before the information.
DHCP- Message appears when the controller is set for DHCP, but not configured on a network.
00:00:XX:XX:XX:XX The message shows the MAC address of the controller. Message scrolls continuously
during operation if no IP address is set.
IMPORTANT: When the controller operates in Dual-IP mode, this information is provided
for each port, that is Port A1 and Port A2. The port name appears before the information.
Ethernet Port Rate/ The current port rate and duplex state when an EtherNet/IP port has a connection.
Duplex State Message scrolls continuously during operation.
IMPORTANT: When the controller operates in Dual-IP mode, this information is provided
for each link, that is, Link A1 and Link A2. The link name appears before the information.
IP Address The IP address of the controller. Appears on powerup and scrolls continuously during
operation. If the IP address is not yet set, the MAC address appears.
IMPORTANT: When the controller operates in Dual-IP mode, this information is provided
for each port, that is Port A1 and Port A2. The port name appears before the information.
Duplicate IP - Message appears when the controller detects a device with the same IP Address on the
00:00:XX:XX:XX:XX network. The message shows the MAC address of the device with the duplicate IP Address.
Message scrolls continuously during operation.
IMPORTANT: When the controller operates in Dual-IP mode, this information is provided
for each port, that is Port A1 and Port A2. The port name appears before the information.
DHCP-Address Lost The controller communicated with the DHCP server to renew the IP address. The server
either did not reply or did not renew the IP address.
The controller continues to operate, but with no Ethernet connectivity out of this port.
IMPORTANT: When the controller operates in Dual-IP mode, this information is provided
for each port, that is Port A1 and Port A2. The port name appears before the information.
IP Address/Mask/ The DHCP server responded with an unusable combination.
Gateway/DNS Invalid IMPORTANT: When the controller operates in Dual-IP mode, this information is provided
for each port, that is Port A1 and Port A2. The port name appears before the information.
IP Address Invalid The IP Address used in the port configuration is not valid.
IMPORTANT: When the controller operates in Dual-IP mode, this information is provided
for each port, that is Port A1 and Port A2. The port name appears before the information.
Mask Invalid The Subnet/Network Mask used in the port configuration is not valid.
IMPORTANT: When the controller operates in Dual-IP mode, this information is provided
for each port, that is Port A1 and Port A2. The port name appears before the information.
Gateway Invalid The Gateway Address used in the port IP configuration is not valid.
IMPORTANT: When the controller operates in Dual-IP mode, this information is provided
for each port, that is Port A1 and Port A2. The port name appears before the information.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 213

Appendix A Status Indicators

Table 27 - General Status Messages (Continued)

Message Interpretation
DNS Invalid The DNS used in the port IP configuration is not valid.
No Project No project is loaded on the controller.
To load a project, complete one of the following tasks:
Use the Logix Designer application to download the project to the controller
Use an SD card to load a project to the controller
Project Name The name of the project that is loaded on the controller.
BUSY The I/O modules that are associated with the controller are not yet fully powered.
Let powerup and I/O module self-testing complete.
Corrupt Certificate The security certificate that is associated with the firmware is corrupted.
Received Go to http://www.rockwellautomation.com/support/ and download the firmware revision to
which you are trying to update. Replace the firmware revision that you have previously
installed with that posted on the Technical Support website.
Corrupt Image The firmware file is corrupted.
Received Go to http://www.rockwellautomation.com/support/ and download the firmware revision to
which you are trying to update. Replace the firmware revision that you have previously
installed with that posted on the Technical Support website.
Backup Energy HW A failure with the embedded storage circuit has occurred, and the controller is incapable
Failure - Save Project of saving the program in the event of a powerdown. If you see this message, save your
program to the SD card before you remove power and replace the controller.
Backup Energy Low - The embedded storage circuit does not have sufficient energy to enable the controller to
Save Project save the program in the event of a powerdown. If you see this message, save your
program to the SD card before you remove power and replace the controller.
Flash in Progress A firmware update that is initiated via ControlFLASH or AutoFlash utilities is in progress.
Let the firmware update complete without interruption.
Firmware Installation The controller is using boot firmware, that is, revision 1.xxx, and requires a
Required firmware update.
SD Card Locked An SD card that is locked is installed.

214 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Status Indicators Appendix A

Fault Messages

If the controller displays a fault, these messages can be indicated on the status
display.
Table 28 - Fault Messages
Message Interpretation
Major Fault TXX:CXX message A major fault of Type XX and Code XX has been detected.
For example, if the status display indicates Major Fault T04:C42 Invalid
JMP Target, a JMP instruction is programmed to jump to an invalid LBL
instruction.
For details about major recoverable faults, see the Logix5000 Major,
Minor, and I/O Fault Codes Programming Manual, publication
1756-PM014.
I/O Fault Local:X #XXXX message An I/O fault has occurred on a module in the local chassis. The slot
number and fault code are indicated along with a brief description.
For example, I/O Fault Local:3 #0107 Connection Not Found indicates
that a connection to the local I/O module in slot three is not open.
Take corrective action specific to the type of fault indicated.
For details about each I/O fault code, see the Logix5000 Major, Minor,
and I/O Fault Codes Programming Manual, publication 1756-PM014.
I/O Fault ModuleName #XXXX message An I/O fault has occurred on a module in a remote chassis. The name of
the faulted module is indicated with the fault code and brief description
of the fault.
For example, I/O Fault My_Module #0107 Connection Not Found
indicates that a connection to the module named My_Module is not
open.
Take corrective action specific to the type of fault indicated.
For details about each I/O fault code, see the Logix5000 Major, Minor,
and I/O Fault Codes Programming Manual, publication 1756-PM014.
I/O Fault ModuleParent:X #XXXX message An I/O fault has occurred on a module in a remote chassis. The parent
name of the module is indicated because no module name is configured
in the I/O Configuration tree of Logix Designer application. In addition,
the fault code is indicated with a brief description of the fault.
Take corrective action specific to the type of fault indicated.
For details about each I/O fault code, see the Logix5000 Major, Minor,
and I/O Fault Codes Programming Manual, publication 1756-PM014.
X I/O Faults I/O faults are present and X = the number of I/O faults present.
If there are multiple I/O faults, the controller indicates that the first fault
reported. As each I/O fault is resolved, the number of indicated faults
decreases and the I/O Fault message indicates the next reported fault.
Take corrective action specific to the type of fault indicated.
For details about each I/O fault code, see the Logix5000 Major, Minor,
and I/O Fault Codes Programming Manual, publication 1756-PM014.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 215

Appendix A Status Indicators

Major Fault Messages

The Major Fault TXX:CXX message on the controller status display indicates
major faults. Table 29 lists fault types, codes, and the associated messages as
they are shown on the status display.

For detailed descriptions and suggested recovery methods for major faults, see
the Logix5000 Major, Minor, and I/O Fault Codes Programming Manual,
publication 1756-PM014.
Table 29 - Major Fault Status Messages
Type Code Message
1 1 Run Mode Powerup
1 60 Nonrecoverable
1 61 Nonrecoverable Diagnostics Saved on SD Card
3 16 I/O Connection Failure
3 20 Chassis Failure
3 21
3 23 Connection Failure
4 16 Unknown Instruction
4 20 Invalid Array Subscript
4 21 Control Structure LEN or POS < 0
4 31 Invalid JSR Parameter
4 34 Timer Failure
4 42 Invalid JMP Target
4 82 SFC Jump Back Failure
4 83 Value Out of Range
4 84 Stack Overflow
4 89 Invalid Target Step
4 90 Invalid Instruction
4 91 Invalid Context
4 92 Invalid Action
4 990 User-defined
4 991
4 992
4 993
4 994
4 995
4 996
4 997
4 998
4 999

216 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Status Indicators Appendix A

Table 29 - Major Fault Status Messages (Continued)

Type Code Message
6 1 Task Watchdog Expired
7 40 Save Failure
7 41 Bad Restore Type
7 42 Bad Restore Revision
7 43 Bad Restore Checksum
7 44 Failed to Restore Processor Memory
8 1 Mode switch Change Ignored
10 14 Energy Storage Fault
10 15
11 1 Positive Overtravel Limit Exceeded
11 2 Negative Overtravel Limit Exceeded
11 3 Position Error Tolerance Exceeded
11 4 Encoder Channel Connection Fault
11 5 Encoder Noise Event Detected
11 7 Synchronous Connection Fault
11 8 Servo Module Fault
11 9 Asynchronous Connection Fault
11 32 Motion Task Overlap Fault
11 33 CST Reference Loss Detected
12 32 Disqualified Secondary Controller Cycle Power
12 33 Unpartnered Controller Identified in New Primary Chassis
12 34 Mode switch Positions of Primary and Secondary Controllers
Mismatched
17 34 Temperature Fault or Preservation Fault
18 1 CIP Motion Initialization Fault
18 2 CIP Motion Initialization Fault Mfg
18 3 CIP Motion Axis Fault
18 4 CIP Motion Axis Fault Mfg
18 5 CIP Motion Fault
18 6 CIP Module Fault
18 7 Motion Group Fault
18 8 CIP Motion Configuration Fault
18 9 CIP Motion APR Fault
18 10 CIP Motion APR Fault Mfg
18 128 CIP Motion Guard Fault

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 217

Appendix A Status Indicators

I/O Fault Codes

The controller indicates I/O faults on the status display in one of these
formats:
I/O Fault Local:X #XXXX message
I/O Fault ModuleName #XXXX message
I/O Fault ModuleParent:X #XXXX message

The first part of the format is used to indicate the location of the module with
a fault. How the location is indicated depends on your I/O configuration and
the properties of the module that are specified in Logix Designer application.

The latter part of the format, #XXXX message, can be used to diagnose the
type of I/O fault and potential corrective actions. For details about each I/O
fault code, see the Logix5000 Major, Minor, and I/O Fault Codes
Programming Manual, publication 1756-PM014.
Table 30 - I/O Fault Messages
Code Message
#0001 Connection Failure
#0002 Insufficient Resource
#0003 Invalid Value
#0004 IOI Syntax
#0005 Destination Unknown
#0006 Partial Data Transferred
#0007 Connection Lost
#0008 Service Unsupported
#0009 Invalid Attribute Value
#000A Attribute List Error
#000B State Already Exists
#000C Object Mode Conflict
#000D Object Already Exists
#000E Attribute Not Settable
#000F Permission Denied
#0010 Device State Conflict
#0011 Reply Too Large
#0012 Fragment Primitive
#0013 Insufficient Command Data
#0014 Attribute Not Supported
#0015 Data Too Large
#0100 Connection In Use
#0103 Transport Not Supported
#0106 Ownership Conflict
#0107 Connection Not Found
#0108 Invalid Connection Type

218 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Status Indicators Appendix A

Table 30 - I/O Fault Messages (Continued)

Code Message
#0109 Invalid Connection Size
#0110 Module Not Configured
#0111 RPI Out of Range
#0113 Out of Connections
#0114 Wrong Module
#0115 Wrong Device Type
#0116 Wrong Revision
#0117 Invalid Connection Point
#0118 Invalid Configuration Format
#0119 Module Not Owned
#011A Out of Connection Resources
#0203 Connection Timeout
#0204 Unconnected Message Timeout
#0205 Invalid Parameter
#0206 Message Too Large
#0301 No Buffer Memory
#0302 Bandwidth Not Available
#0303 No Bridge Available
#0305 Signature Mismatch
#0306 CCM Not Available
#0311 Invalid Port
#0312 Invalid Link Address
#0315 Invalid Segment Type
#0317 Connection Not Scheduled
#0318 Invalid Link Address
#0319 No Secondary Resources Available
#031E No Available Resources
#031F No Available Resources
#0800 Network Link Offline
#0801 Incompatible Multicast RPI
#0814 Data Type Mismatch
#FD01 Bad Backplane EEPROM
#FD02 No Error Code
#FD03 Missing Required Connection
#FD04 No CST Master
#FD05 Axis or GRP Not Assigned
#FD0A Axis Attribute Reject
#FD1F Safety I/O
#FD20 No Safety Task
#FE01 Invalid Connection Type

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 219

Appendix A Status Indicators

Table 30 - I/O Fault Messages (Continued)

Code Message
#FE02 Invalid Update Rate
#FE03 Invalid Input Connection
#FE04 Invalid Input Data Pointer
#FE05 Invalid Input Data Size
#FE06 Invalid Input Force Pointer
#FE07 Invalid Output Connection
#FE08 Invalid Output Data Pointer
#FE09 Invalid Output Data Size
#FE0A Invalid Output Force Pointer
#FE0B Invalid Symbol String
#FE0C Invalid Scheduled Personal Computer Instance
#FE0D Invalid Symbol Instance
#FE0E Module Firmware Updating
#FE0F Invalid Firmware File Revision
#FE10 Firmware File Not Found
#FE11 Firmware File Invalid
#FE12 Automatic Firmware Update Failed
#FE13 Update Failed - Active Connection
#FE14 Searching Firmware File
#FE22 Invalid Connection Type
#FE23 Invalid Unicast Allowed
#FF00 No Connection Instance
#FF01 Path Too Long
#FF04 Invalid State
#FF08 Invalid Path
#FF0B Invalid Config
#FF0E No Connection Allowed

220 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Status Indicators Appendix A

Controller Status Indicators The controller status indicators display the state of the controller.

RUN Indicator

The RUN indicator shows the current mode of the controller.

To change the controller mode, you can use the mode switch on the front of the
controller or the Controller Status menu in the Logix Designer application.

Table 31 - RUN Indicator

State Description
Off The controller is in Program or Test mode.
Steady green The controller is in Run mode.

FORCE Indicator

The Force indicator shows if I/O forces are enabled on the controller.

Table 32 - FORCE Indicator

State Description
Off No tags contain I/O force values.
Solid yellow I/O forces are enabled. If any I/O force values exist, they are active.
IMPORTANT: Use caution if you change any force values. In this state, the changes take effect
immediately.
Flashing yellow I/O forces exist in the application, but are not active because I/O forces are not enabled.
IMPORTANT: Use caution if you enable I/O forces. All existing I/O force values take effect
immediately.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 221

Appendix A Status Indicators

OK Indicator

The OK indicator shows the state of the controller.

Table 33 - OK Indicator
State Description
Off No power is applied.
Flashing red One of the following exists:
The controller requires a firmware update. Typically, the controller is in its out-of-box
state when a firmware update is required.
If a firmware update is required, the 4-character display indicates Firmware Installation
Required. For more information on how to update firmware, see Upload from the
Controller on page 96.
A firmware update is in progress.
If a firmware update is in progress, the 4-character display indicates Flash in Progress. For
more information on how to update firmware, see Upload from the Controller on
page 96.
The controller has a major fault. The fault can be recoverable or nonrecoverable. If the
fault is nonrecoverable, the program has been cleared from the controller memory.
If a fault has occurred, the 4-character display shows information about the fault, for
example, the Type and Code.
For details about major faults, see the following:
The fault descriptions in the 4-Character Status Display beginning on page 212.
Logix5000 Major, Minor, and I/O Fault Codes Programming Manual, publication
1756-PM014.
Solid red One of the following:
The controller is completing power-up diagnostics.
The controller is depleting its residual stored energy upon powerdown.
The controller is powered, but is inoperable.
The controller is loading a project to nonvolatile memory.
The controller is experiencing a Hardware Preservation Fault due to a high internal
module temperature.
In this condition, only the status indicator receives power. Once the controller cools down
to an acceptable temperature, full power is applied.
Solid green The controller is operating normally.

SD Indicator

The SD indicator shows if the SD card is in use.

Table 34 - SD Indicator
State Description
Off No activity is occurring with the SD card.
Flashing green The controller is reading from or writing to the SD card.
IMPORTANT: Do not remove the SD card while the controller is reading or writing. Let the
Solid green read/write complete without interruption. If you interrupt the read/write, data corruption or
loss can occur.
Flashing red One of the following exists:
The SD card does not have a valid file system.
The SD card drew excessive current and power has been removed from the card.
Solid red The controller does not recognize the SD card.

222 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Status Indicators Appendix A

EtherNet/IP Status Indicators The EtherNet/IP indicators show the state of the controller Ethernet ports and
network communication activity.

NET A1 and NET A2 Indicators

The NET A1 and NET A2 indicators show the state of the EtherNet/IP port.
Table 35 - NET A1 and NET A2 Indicators
State Description
Off One of the following:
The controller is not configured, or does not have an IP address.
The port is administratively disabled.
The EtherNet/IP mode is Linear/DLR mode. In this case, the NET A2 indicator is off. The NET
A1 indicator remains on.
Flashing green The controller has an IP address, but no active connections are established.
Steady green The controller has an IP address and at least one established active connection.
Steady red Duplicate IP Address or invalid configuration.

LINK A1 and LINK A2 Indicators

The LINK A1 and LINK A2 indicators show the state of the EtherNet/IP
links.
Table 36 - LINK A1 and LINK A2 Indicators
State Description
Off The link is down. One or more of these conditions exists:
Ethernet cables are not properly connected at both ends. That is, the cables are not properly
connected the controller Ethernet port and to the connected device.
No link exists on the port. For example, the connected device is not powered.
The port is administratively disabled.
LINK A2 only:
The controller is the active ring supervisor in a DLR network, and the ring is not broken.
This is normal operation.
The controller is the active ring supervisor in a DLR network and has detected a rapid
ring fault.
Flashing green All of these conditions exist:
The port is enabled.
A link exists. That is, the cable is properly connected to an enabled controller Ethernet port
on to another device.
There is activity on the port.
Steady green All of these conditions exist:
The port is enabled.
A link exists. That is, the cable is properly connected to an enabled controller Ethernet port
on to another device.
There is no activity on the port.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 223

Appendix A Status Indicators

Power Status Indicators The power status indicators show the status of module power and sensor/
actuator power, known as MOD Power and SA Power, respectively.

MOD Power Indicator

Table 37 describes the MOD Power indicator on a CompactLogix 5380
controller.
Table 37 - MOD Power Indicator
State Description
Off Module Power is not present
Steady green Module Power is present(1)
(1) Although unlikely, it is possible that there is enough Module Power present for the indicator to turn steady green but the power
is not valid. Valid power is 1832V DC to operate a CompactLogix 5380 system. If the system does not power up and operate
successfully, Module Power can be invalid.
If Module Power is invalid, we recommend that you make sure that the external power supply is working correctly, properly sized
for your application and that all wiring is correct.

SA Power Indicator

Table 38 describes the SA Power indicator on a CompactLogix 5380

controller.
Table 38 - SA Power Indicator
State Description
Off One of the following:
Sensor Actuator Power is not present
Status of Sensor Actuator power is unknown
Steady green Sensor Actuator Power is present(1)
(1) Although unlikely, it is possible that there is enough Sensor/Actuator Power present for the indicator to turn steady green but
the power is not valid. Valid power is 1832V DC in applications that require DC voltage and 18240V AC in applications that
require AC voltage.
If Sensor/Actuator Power is invalid, we recommend that you make sure that the external power supply is working correctly,
properly sized for your application and that all wiring is correct.

224 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Status Indicators Appendix A

Thermal Monitoring and The CompactLogix 5380 controllers monitor internal module temperatures.
As shown in Figure 49, the controller takes actions as the
Thermal Fault Behavior temperature increases.

Figure 49 - The CompactLogix 5380 Controller Thermal Fault Behavior

All power to the controller is disabled except Threshold for controller to declare a `Hardware Preservation
to run the red OK status indicator and Power to t he Fault, resetting the module and disabling power.
monitor the temperature. controller is In the disabled power condition, only the OK status indicator is
disabl ed illuminated, and it is red. The module does not apply power
until it has cooled below the Hardware Preservation Hysteresis
Power does not
become enabled
limit. The module then enters fault mode, records the fault in
when in this range the major fault log, and displays `CPU Temperature Fault on
Hardware Preservation the front panel.
Hysteresis Limit

Threshold for controller to declare a `CPU Temperature Fault

major recoverable fault.
If a fault handler does not clear the fault, the module enters
fault mode, records the fault in the major fault log, and displays
`T17:C34 CPU Temperature Fault on the front display.

Threshold for controller to declare a `T17:C35 Controller internal

temperature is approaching operating limit minor fault and set
the Diagnostics minor fault bit.
The fault is recorded in the minor fault log, but is not displayed
on the front panel. If the temperature returns to an acceptable
range, the Diagnostics minor fault bit clears, but the minor fault
record remains.

IMPORTANT If you follow the recommended limits for ambient (inlet) temperature and apply the required clearances around the system, the
controller is unlikely to reach the initial warning (minor fault) temperature.
For more information on CompactLogix 5380 controller specifications, see CompactLogix 5380 Controller Specifications
Technical Data, publication 5069-TD002.

IMPORTANT The presence of any temperature warning indicates that measures need to be taken to reduce the ambient temperature of
the module.
Instructions for how to use relay ladder logic to check for a minor fault can be found in the Logix5000 Controllers Major, Minor,
and I/O Faults Programming Manual, publication 1756-PM014.
You can use a GSV instruction to read the MinorFaultBits attribute of the FaultLog class name. If the Diagnostics minor fault bit
(Bit 17) is set, a temperature minor fault can be present. Check the Minor Faults tab of the Controller Properties dialog box in
Logix Designer to see if the minor fault is a temperature warning.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 225

Appendix A Status Indicators

Notes:

226 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Appendix B

Security Options

Topic Page
Disable an Ethernet Port 227
Disable the 4-character Status Display 230
Disable the Controller Web Pages 235

This section describes how to disable functionality on your

CompactLogix 5380 controller. For example, you can disable a controller
Ethernet port.

Disable an Ethernet Port You can disable the controller Ethernet ports with Logix Designer application,
version 28.00.00 or later.

IMPORTANT Remember the following:

When you use the Logix Designer application, version 29.00.00 or later,
you can disable either of the Ethernet ports whether the controller uses
Dual-IP mode or Linear/DLR mode.
Once an Ethernet port is disabled, you lose any connection that is
established through that port.
When a controller is used in a linear topology, only disable an Ethernet
port if the controller is an end device on the network.
You cannot disable Ethernet ports if the controller is in Run mode or if
the FactoryTalk Security settings deny this editing option.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 227

Appendix B Security Options

Ethernet ports return to the default setting after the following occur on
the controller:

Stage 1 reset

Stage 2 reset

New project is downloaded - In this case, the settings in the new project
take effect.

Program is cleared from the controller - The following are examples of

what clears the program from a controller:
Major non-recoverable fault occurs.
Firmware update occurs.

You must reconfigure the settings to disable an Ethernet port after the port
returns to its default settings.

1. Add a MSG instruction to your program.

IMPORTANT You cannot add a MSG instruction to your program if the controller
is in Run mode or if the FactoryTalk Security settings deny this
editing option.

2. Configure the Configuration tab on the Message Configuration dialog

box as follows:

IMPORTANT The values listed below are stored to NVS memory in such a way
that the MSG instruction is not required to be executed each time
the controller powers up.

Message Type - CIP Generic

Service Type - Set Attribute Single
Instance - 1 to disable Port A1, 2 to disable Port A2
Class - f6
Attribute - 9
Source Element - Controller tag of SINT data type
In this example, the controller tag is named Port_Configuration.

228 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Security Options Appendix B

Source Length - 1

3. Configure the Communication tab to use a Path of THIS.

4. Before you enable the MSG instruction, make sure that the Source
Element tag value is 2.

IMPORTANT You can re-enable an Ethernet port after it is disabled.

To re-enable the port, complete the steps that are described in this
section. Before you enable the MSG instructions, however, make
sure that the Source Element tag value is 1.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 229

Appendix B Security Options

Disable the 4-character With the Logix Designer application, version 29.00.00 or later, you can disable
the 4-character status display in the following ways:
Status Display
Disable the 4-character Display Entirely

Disable a Subset of 4-character Display Information

Ethernet ports return to the default setting after the following occur on
the controller:

Stage 1 reset

Stage 2 reset

New project is downloaded - In this case, the settings in the new project
take effect.

Program is cleared from the controller - The following are examples of

what clears the program:
Major non-recoverable fault occurs.
Firmware update occurs.

You must reconfigure the settings to disable an Ethernet port after the port
returns to its default settings.

230 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Security Options Appendix B

Disable the 4-character Display Entirely

When you disable the 4-character display entirely, the following information is
no longer shown:

Project name

Link status

Port status

IP address

IMPORTANT When you use a CompactLogix 5380 controller in Dual-IP mode,

there is a unique link status, port status, and IP address for each of
the controller Ethernet ports.
When you complete the tasks in this section, none of the
information that is listed appears for either Ethernet port.

1. Add a MSG instruction to your program.

IMPORTANT You cannot add a MSG instruction to your program if the controller
is in Run mode or if the FactoryTalk Security settings deny this
editing option.

2. Configure the Configuration tab on the Message Configuration dialog

box as follows:
Message Type - CIP Generic
Service Type - Set Attribute Single
Instance - 1
Class - 3a5
Attribute - 1

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 231

Appendix B Security Options

Source Element - Controller tag of SINT data type

In this example, the controller tag is named LCD_SINT.

Source Length - 1

3. Configure the Communication tab to use a Path of THIS.

4. Before you enable the MSG instruction, make sure that the Source
Element tag value is 1.

IMPORTANT You can re-enable the 4-character display after it is disabled.

To re-enable the 4-character display, complete the steps that are
described in this section. Before you enable the MSG instructions,
however, make sure that the Source Element tag value is 0.

232 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Security Options Appendix B

Disable a Subset of 4-character Display Information

You can disable a subset of the information that scrolls across the
CompactLogix 5380 controller. You can disable the following subsets:

Project name and link status

Port status and IP address

IMPORTANT When you use a CompactLogix 5380 controller in Dual-IP mode,

there is a unique link status, port status, and IP address for each of
the controller Ethernet ports.
When you complete the tasks in this section, none of the
information that is listed appears for either Ethernet port.

1. Add a MSG instruction to your program.

IMPORTANT You cannot add a MSG instruction to your program if the controller
is in Run mode or if the FactoryTalk Security settings deny this
editing option.

2. Configure the Configuration tab on the Message Configuration dialog

box as follows:
Message Type - CIP Generic
Service Type - Set Attribute Single
Instance - 1
Class - 3a5
Attribute - 2
Source Element - Controller tag of DINT data type - In this example,
the controller tag is named Line_MASK.
Source Length - 4

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 233

Appendix B Security Options

3. Configure the Communication tab to use a Path of THIS.

4. Before you enable the MSG instruction, set the bits in the Source
Element tag to the following values, based on what information that you
want to disable:
Project name and link status - Bit 0 of the Source Element = 1
Port status and IP address - Bit 1 of the Source Element = 1

IMPORTANT You can re-enable the subsets of information on the 4-character

display after they are disabled.
To re-enable the subsets, complete the steps that are described in
this section. Before you enable the MSG instructions, however,
make sure the appropriate bit in the Source Element tag value is 0.

234 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Security Options Appendix B

Disable the Controller You can disable the CompactLogix 5380 controller web pages with
Studio 5000 Logix Designer environment, version 28.00.00 or later.
Web Pages
Controller web pages return to the default setting after the following occur on
the controller:

Stage 1 reset

Stage 2 reset

New project is downloaded - In this case, the settings in the new project
take effect.

Program is cleared from the controller - The following are examples of

what clears the program from a controller:
Major non-recoverable fault occurs.
Firmware update occurs.

You must reconfigure the settings to disable the controller web page after it
returns to its default settings.

1. Add a MSG instruction to your program.

IMPORTANT You cannot add a MSG instruction to your program if the controller
is in Run mode or if the FactoryTalk Security settings deny this
editing option.

2. Configure the Configuration tab on the Message Configuration dialog

box as follows:
Message Type - CIP Generic
Service Type - Custom
Service Code - 4c
Instance - 1
Class - f5
Attribute - 0

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 235

Appendix B Security Options

Source Element - Controller tag of SINT[5] data type.

In this example, the controller tag is named WP_Disable and must
match the following graphic.

IMPORTANT The Source Element tag in your Logix Designer application project
must match the values shown in the graphic.
If you use values that are different than the ones shown, the
controller web pages are not disabled.

Source Length - 5

236 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Security Options Appendix B

3. Configure the Communication tab to use a Path of THIS.

4. Before you enable the MSG instruction, consider the following:

To disable the controller web page, the last element in the SINT array
for the Source Element must be 0.

To enable the controller web page, the last element in the SINT array
for the Source Element must be 1.

Rockwell Automation Publication 5069-UM001C-EN-P - December 2016 237

Appendix B Security Options

Notes:

238 Rockwell Automation Publication 5069-UM001C-EN-P - December 2016

 Index

Numerics communication path

set 92
1732 ArmorBlock Guard I/O modules 136 CompactLogix 5380
1732D ArmorBlock I/O modules 136 design system 15
1734 POINT I/O modules 136 configure
1746 SLC I/O modules 136 DHCP server 72
1756 ControlLogix I/O modules 136 motion 178
1769 Compact I/O modules 136 consume data 153
1784-SD1 and 1784-SD2 cards continuous task 161
load from 104 - 107 control data 152
other tasks 107 ControlFLASH software 82
store to 101 - 104 controller
1794 FLEX I/O modules 136 available modes 100
4-character display behavior 152
disable 231 - 232 design system with 15
disable a subset of display information 233 - download project 94
234 go online 92
4-character status display 212 - 220 set communication path 92
fault messages 215 upload project 96
general status messages 212 controller firmware
I/O fault codes 218 - 220 obtain 81
5069 Compact I/O modules 129, 136 update with AutoFlash 87
update with ControlFLASH 82
controller operation mode
A change with Logix Designer application 100
add I/O modules while online 147 change with mode switch 99
controller reset
Add-On Instructions 168
stage 1 109
Advanced Diagnostics web page stage 2 111
use to troubleshoot 207 controller status
allow communication 152 4-character status display 212 - 220
application fault messages 215
elements 157 general status messages 212
AutoFlash I/O fault codes 218 - 220
update 87 controller status indicators 221
axis FORCE indicator 221
consumed 178 OK indicator 222
obtain information 182 RUN indicator 221
virtual 178 SD indicator 222
troubleshoot with in Logix Designer
application 184
B controller tasks 159
block communication 152 controller web pages
BOOTP/DHCP server 117 disable 235 - 237
troubleshoot with Advanced Diagnostics
setting IP network address 68 - 70 web page 207
Browse Chassis web page troubleshoot with Browse Chassis web page
use to troubleshoot 209 209
troubleshoot with Diagnostics web page 205
troubleshoot with Ethernet Port A1/A2 web
C page 206
communication troubleshoot with Home web page 203
allow 152 troubleshoot with Tasks web page 204
block 152 use to troubleshoot 202 - 209
with EtherNet/IP devices via socket interface
128

Rockwell Automation Publication 1769-UM021H-EN-P - November 2016 239

Index

D configure Linear/DLR mode via Logix

Designer application 37
data update configure Linear/DLR mode via RSLinx
I/O data 148 Classic software 39
design Dual-IP mode 28
system 15 overlapping IP address ranges 30
diagnostics Dual-IP mode port functionality
with Logix Designer 183 - 196 considerations 46 - 50
with RSLinx Classic software 197 - 202 Linear/DLR mode 32
Diagnostics web page EtherNet/IP network
use to troubleshoot 205 communication driver in RSLinx Classic
disable software 57 - 58, 59 - 60
communication via socket interface 128
4-character display 231 - 232
controller web pages 235 - 237 DLR network topology 122
linear network topology 124
Ethernet port 227 - 229 network communication rates 120
subset of 4-character display information nodes 117
233 - 234 optimize network performance 120
disable the Ethernet ports 112 parameters for DNS addressing 67
DLR network topology 122, 136 star network topology 126
DNS addressing 67, 74 topologies 122 - 126
EtherNet/IP network parameters 67 EtherNet/IP status indicators 223
domain name 67 LINK A1 and LINK A2 indicators 223
download NET A1 and NET A2 indicators 223
project 94 event tasks 161
drivers
RSLinx Classic software 57 - 58, 59 - 60
Dual-IP mode 28 F
overlapping IP address ranges 30 fault codes 218 - 220
port functionality considerations 46 - 50 use GSV instruction to get 173
duplicate IP address fault handler
detection 73 execute at I/O module fault 174
resolution 73 fault messages
on 4-character status display 215
faults
E cpu temperature 225
electronic keying hardware preservation 225
about 135 recoverable 225
elements FBD
control application 157 using 167
error firmware
script file 84 obtain 81
Ethernet Port A1/A2 web page required 81
use to troubleshoot 206 security certificate, error 84
Ethernet ports update controller firmware 80 - 88
update with AutoFlash 87
disable 112, 227 - 229 update with ControlFLASH 82
Dual-IP mode 28 FORCE status indicator 221
Linear/DLR mode 32
EtherNet/IP mode
change 41 - 45 G
change via Logix Designer application 42
change via RSLinx Classic software 44 gateway 67
configure 33 - 40 GSV instruction
configure Dual-IP mode via Logix Designer monitor a connection 173
application 33 use to get fault codes 173
configure Dual-IP mode via RSLinx Classic
software 35

240 Rockwell Automation Publication 1769-UM021H-EN-P - November 2016

 Index

H Logix Designer application 117

add I/O modules while online 147
handshake 152 add local I/O modules to a project 131 - 134
Home web page add remote I/O modules to a project 138 -
use to troubleshoot 203 146
host name 67 Add-On Instructions 168
change controller operation mode 100
change EtherNet/IP mode 42
I configure Dual-IP mode 33
configure Linear/DLR mode 37
I/O
continuous tasks 161
determine data update 148 develop applications 157 - 175
I/O fault codes develop motion applications 177 - 182
on 4-character status display 218 - 220 diagnotics 183 - 196
I/O modules download project 94
about local I/O modules 129 event tasks 161
about remote I/O modules 136 go online 92
add local I/O modules to Logix Designer motion instructions 180
application project 131 - 134 obtain motion axis information 182
add remote I/O modules to Logix Designer parameters 166
application project 138 - 146 periodic tasks 161
add while online 147 programming languages 167
connection error 174 programs 163
local routine 165
example 130 routines 165
on a DLR network topology 136 set communication path 92
on a linear network topology 137 tags 166
on a star network topology 137 tasks in project 159
remote troubleshoot with Advanced Time Sync
example 136 dialog box 194
instructions troubleshoot with Connection category 187
motion 180 troubleshoot with controller status
IP addresses indicators 184
troubleshoot with Ethernet Port Diagnostics
definition 67 dialog box 192
DHCP server 72 troubleshoot with General category 186
Dual-IP mode 28 troubleshoot with I/O module properties
overlapping IP address ranges 30 dialog box 186 - 189
duplicate address detection 73 troubleshoot with Module Info category 187
duplicate address resolution 73 upload project 96
Linear/DLR mode 32

L M
memory card 101 - 107
Ladder Logic
load project from card 104 - 107
using 167 other tasks 107
linear network topology 124, 137 store project to card 101 - 104
Linear/DLR mode 32 message
LINK A1 and LINK A2 status indicators 223 about 155
load MOD power indicator 224
from memory card 104 - 107 mode switch 98
local I/O modules change controller operation mode 99
about 129 position 100
add to a Logix Designer application project monitor I/O connections 172
131 - 134 motion
example 130 about 178
instructions 180
obtain axis information 182
program 180

Rockwell Automation Publication 1769-UM021H-EN-P - November 2016 241

Index

N project
download 94
NET A1 and NET A2 status indicators 223 elements 157
network address go online 92
DNS addressing 74 programs 163
network communication rates routines 165
on an EtherNet/IP network 120 tasks 159
network parameters upload 96
DNS addressing 67 projects
domain name 67 Add-On Instructions 168
gateway 67 parameters 166
host name 67 programming languages 167
IP addresses 67 tags 166
subnet mask 67
nodes on an EtherNet/IP network 117
R
receive messages 155
O remote I/O modules
obtain 1732 ArmorBlock Guard I/O 136
axis information 182 1732D ArmorBlock I/O 136
obtain firmware 81 1734 POINT I/O 136
OK status indicator 222 1746 SLC I/O 136
1756 ControlLogix I/O 136
online 1769 Compact I/O 136
go 92 1794 FLEX I/O 136
optimize EtherNet/IP network performance 5069 Compact I/O 136
120 about 136
overlapping IP address ranges 30 add to a Logix Designer application project
138 - 146
example 136
P reset button 108
stage 1 reset 109
parameters stage 2 reset 111
in project 166 routines 165
path in project 165
set 92 RSLinx Classic software 117
periodic tasks 161 change EtherNet/IP mode 44
Power status indicators 224 configure Dual-IP mode 35
MOD power indicator 224 configure Linear/DLR mode 39
SA power indicator 224 diagnotics 197 - 202
produce data 153 Ethernet devices driver 59 - 60
produce/consume data 153 EtherNet/IP driver 57 - 58
programming languages 167 troubleshoot with Connection Manager tab
200
FBD 167 troubleshoot with General tab 197
Ladder Logic 167 troubleshoot with Port Diagnostics tab 198
SFC 167 troubleshoot with USB tab 201
Structured Text 167 USB driver 61
programs RSWho
in project 163 set communication path 92
scheduled 164 RUN status indicator 221
unscheduled 164

242 Rockwell Automation Publication 1769-UM021H-EN-P - November 2016

 Index

S routines in project 165

set communication path 92
SA power indicator 224 tasks 159
scheduled programs 164 troubleshoot with Advanced Time
script file Sync dialog box 194
error 84 troubleshoot with Connection catego-
SD card 25, 101 - 107 ry 187
troubleshoot with controller status in-
load from 104 - 107 dicators 184
other tasks 107
store to 101 - 104 troubleshoot with Ethernet Port Diag-
nostics dialog box 192
SD status indicator 222 troubleshoot with General category
security 186
disable a subset of 4-character display troubleshoot with I/O module proper-
information 233 - 234 ties dialog box 186 - 189
disable an Ethernet port 227 - 229 troubleshoot with Module Info cate-
disable the 4-character display 231 - 232 gory 187
disable the controller web pages 235 - 237 upload project 96
security certificate RSLinx Classic 117
error 84 change EtherNet/IP mode 44
send messages 155 configure Dual-IP mode 35
set IP network address configure Linear/DLR mode 39
diagnostics 197 - 202
BOOTP/DHCP server 68 - 70 Ethernet devices driver 59 - 60
SFC EtherNet/IP driver 57 - 58
using 167 troubleshoot with Connection Manag-
socket interface 128 er tab 200
software troubleshoot with General tab 197
add I/O modules while online 147 troubleshoot with Port Diagnostics tab
add local I/O modules to a Logix Designer 198
project 131 - 134 troubleshoot with USB tab 201
add remote I/O modules to a Logix Designer USB driver 61
project 138 - 146 stage 1 reset 109
change EtherNet/IP mode 41 - 45 stage 2 reset 111
configure EtherNet/IP mode 33 - 40 star network topology 126, 137
go online 92 status indicators
Logix Designer application 117
Add-On Instructions 168 controller status 221
change controller operation mode 100 EtherNet/IP status indicators 223
change EtherNet/IP mode 42 FORCE indicator 221
configure Dual-IP mode 33 LINK A1 and LINK A2 indicators 223
configure Linear/DLR mode 37 MOD power indicator 224
continuous tasks 161 NET A1 and NET A2 indicators 223
develop applications 157 - 175 OK indicator 222
develop motion applications 177 - Power status indicators 224
182 RUN indicator 221
diagnostics 183 - 196 SA power indicator 224
download project 94 SD indicator 222
event tasks 161 status messages
motion instructions 180 on 4-character status display 212
motion overview 178 store
obtain motion axis information 182 to memory card 101 - 104
periodic tasks 161 Structured Text
programming languages 167 using 167
programs in project 163 subnet mask 67
project parameters 166
project tags 166

Rockwell Automation Publication 1769-UM021H-EN-P - November 2016 243

Index

T U
tags unscheduled programs 164
consume 153 update
in project 166 determine frequency 148
produce 153 update controller firmware 80 - 88
tasks update firmware
continuous 161 AutoFlash 87
event 161 upload
in Logix Designer application project 159
periodic 161 project 96
priority 162 USB
Tasks web page communication driver in RSLinx Classic
use to troubleshoot 204 software 61
temperature use GSV instruction to get fault codes 173
limit 225
temperature warning 225
thermal monitoring 225
topologies
available on an EtherNet/IP network 122 -
126
DLR 122
linear 124
star 126
troubleshoot
controller status indicators 184
with Advanced Diagnostics web page 207
with Advanced Time Sync dialog box in Logix
Designer application 194
with Browse Chassis web page 209
with Connection category in Logix Designer
application 187
with Connection Manager tab in RSLinx
Classic software 200
with controller web pages 202 - 209
with Diagnostics web page 205
with Ethernet Port A1/A2 web page 206
with Ethernet Port Diagnostics dialog box in
Logix Designer application 192
with General category in Logix Designer
application 186
with General tab in RSLinx Classic software
197
with Home web page 203
with I/O module properties dialog box in
Logix Designer application 186 -
189
with Module Info category in Logix Designer
application 187
with Port Diagnostics tab in RSLinx Classic
software 198
with Tasks web page 204
with USB tab in RSLinx Classic software 201

244 Rockwell Automation Publication 1769-UM021H-EN-P - November 2016

.

Rockwell Automation Support

Use the following resources to access support information.

Knowledgebase Articles, How-to Videos, FAQs, Chat, User

Technical Support Center https://rockwellautomation.custhelp.com/
Forums, and Product Notification Updates.
Local Technical Support Phone Numbers Locate the phone number for your country. http://www.rockwellautomation.com/global/support/get-support-now.page
Find the Direct Dial Code for your product. Use the code to
Direct Dial Codes http://www.rockwellautomation.com/global/support/direct-dial.page
route your call directly to a technical support engineer.
Installation Instructions, Manuals, Brochures, and
Literature Library http://www.rockwellautomation.com/global/literature-library/overview.page
Technical Data.
Product Compatibility and Download Get help determining how products interact, check http://www.rockwellautomation.com/global/support/pcdc.page
Center (PCDC) features and capabilities, and find associated firmware.

Documentation Feedback
Your comments will help us serve your documentation needs better. If you have any suggestions on how to improve this document, complete the
How Are We Doing? form at http://literature.rockwellautomation.com/idc/groups/literature/documents/du/ra-du002_-en-e.pdf.

Rockwell Automation maintains current product environmental information on its website at http://www.rockwellautomation.com/rockwellautomation/about-us/sustainability-ethics/product-environmental-compliance.page.

Allen-Bradley, ArmorBlock, Compact I/O, CompactLogix, ControlFLASH, ControlLogix, FactoryTalk, FLEX I/O, Guard I/O, Integrated Architecture, Kinetix, Logix5000, On-Machine, PanelView, POINT I/O, PowerFlex, Rockwell Automation,
Rockwell Software, RSLinx, RSNetWorx, SLC, Stratix, Stratix 2000, Stratix 5400, Stratix 5410, Stratix 5700, 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.

Rockwell Otomasyon Ticaret A.., Kar Plaza Merkezi E Blok Kat:6 34752 erenky, stanbul, Tel: +90 (216) 5698400

Publication 5069-UM001C-EN-P - December 2016

Supersedes Publication 5069-UM001B-EN-P - June 2016 Copyright 2016 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.