This manual links to Logix 5000 Controller and I/O Fault Codes and Syslog

Messages, 1756-RD001; download the spreadsheet now for offline access.

ControlLogix 5580 and

GuardLogix 5580 Controllers
Bulletin 1756

User Manual Original Instructions

ControlLogix 5580 and GuardLogix 5580 Controllers User Manual

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.

These 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).

The following icon may appear in the text of this document.

Identifies information that is useful and can help to make a process easier to do or easier to understand.

2 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Table of Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
About This Publication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Summary of Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 1
ControlLogix and Minimum Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
GuardLogix Systems ControlLogix Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
ControlLogix No Stored Energy (NSE) Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . 12
ControlLogix-XT and GuardLogix-XT Controllers. . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Process Controllers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Conformal Coated Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Controller Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
ControlLogix System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Standalone Controller and I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Multiple Controllers in One Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Multiple Devices Connected via Multiple Networks . . . . . . . . . . . . . . . . . . . . . . . . . 15
GuardLogix System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
GuardLogix with Safety I/O and Integrated Safety Drives. . . . . . . . . . . . . . . . . . . . 17
Design the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
CIP Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Secure Controller Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
ControlLogix 5580 Controller Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
GuardLogix 5580 Controller Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Features Supported by GuardLogix 5580 Controllers via the Safety Task. . . . . . 22

Chapter 2
Safety Concept of Functional Safety Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
GuardLogix Controllers Safety Network Number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Safety Signature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Distinguish between Standard and Safety Components . . . . . . . . . . . . . . . . . . . . . . . 24
Controller Data Flow Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Safety Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Chapter 3
Connect to a Controller Set the IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Other Methods to Set the IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Duplicate IP Address Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Duplicate IP Address Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
DNS Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Update Controller Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Firmware Update Guidelines for Safety Controllers . . . . . . . . . . . . . . . . . . . . . . . 30
Determine Required Controller Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Obtain Controller Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 3

Table of Contents

Use ControlFLASH Plus or ControlFLASH Software to Update Firmware . . . . . . . . 31

Use AutoFlash to Update Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Chapter 4
Communication Networks EtherNet/IP Network Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
EtherNet/IP Port Speeds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
EtherNet/IP Communication Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Double Data Rate Backplane Communication for ControlLogix Controllers . . . . 38
ControlNet Network Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
GuardLogix Controllers in a ControlNet Network. . . . . . . . . . . . . . . . . . . . . . . . . . 40
ControlNet Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
DeviceNet Network Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
DeviceNet Bridge and Linking Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Connections Over DeviceNet Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Data Highway Plus (DH+) Network Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Communicate Over a DH+ Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Universal Remote I/O (RIO) Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Communicate Over a Universal RIO Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
FOUNDATION Fieldbus Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
HART Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Chapter 5
Start to Use the Controller Create a Logix Designer Application Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Configuration for a GuardLogix Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Set the Safety Level for a GuardLogix Controller . . . . . . . . . . . . . . . . . . . . . . . . . 48
Passwords for Safety-locking and Unlocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Protect the Safety Signature in Run Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Assign the Safety Network Number (SNN). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Copy and Paste a Safety Controller Safety Network Number. . . . . . . . . . . . . . . . 54
Go Online with the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Use RSWho . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Use a Recent Communication Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Considerations for Going Online with a GuardLogix Controller . . . . . . . . . . . . . . . . . . 58
Match Project to Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Firmware Revision Matching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Safety Status/Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Safety Signature and Safety-locked and -unlocked Status . . . . . . . . . . . . . . . . . 59
Checks for Going Online with a GuardLogix Controller . . . . . . . . . . . . . . . . . . . . . 60
Download to the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Use Who Active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Use the Controller Status Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Considerations for Download to a GuardLogix Controller . . . . . . . . . . . . . . . . . . . . . . 62
Upload from the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Use Who Active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Use the Controller Status Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Considerations for Upload from a GuardLogix Controller . . . . . . . . . . . . . . . . . . . . . . 66
Controller Operation Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Run Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Remote Run Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
4 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025
 Table of Contents

Remote Program Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Remote Test Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Program Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Use the Keyswitch to Change the Operation Mode . . . . . . . . . . . . . . . . . . . . . . . . 69
Use the Logix Designer Application to Change the Operation Mode . . . . . . . . . . 70
Reset Button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Stage 1 Reset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Stage 2 Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Safety Partner Reset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Chapter 6
Use the Secure Digital Card Considerations for Storing and Loading a Safety Project . . . . . . . . . . . . . . . . . . . . . . 76
Store to the SD Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Load from the SD Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Controller Powerup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
User-initiated Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Other Secure Digital Card Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Chapter 7
Manage Controller Connection Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Communication Nodes on an EtherNet/IP Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Devices Included in the Node Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Devices Excluded from the Node Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
CIP Security Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Controller Communication Interaction with Control Data . . . . . . . . . . . . . . . . . . . . . . 86
Produce and Consume (Interlock) Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Requested Packet Interval (RPI) of Multicast Tags . . . . . . . . . . . . . . . . . . . . . . . . 87
Send and Receive Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Determine Whether to Cache Message Connections . . . . . . . . . . . . . . . . . . . . . . 88
Socket Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
TLS Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
HTTP(S) REST API Client Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Simple Network Management Protocol (SNMP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Use a CIP Generic MSG to Enable SNMP on the Controller. . . . . . . . . . . . . . . . . . . 90
Use a CIP Generic MSG to Disable SNMP on the Controller . . . . . . . . . . . . . . . . . . 92

Chapter 8
Standard I/O Modules Selecting ControlLogix I/O Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Electronic Keying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Local I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Add Local I/O to the I/O Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Remote I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Add Remote I/O to the Ethernet Port on the Controller . . . . . . . . . . . . . . . . . . . . 101
Add Remote I/0 to a Local Communication Module . . . . . . . . . . . . . . . . . . . . . . . 103
Add to the I/O Configuration While Online. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Modules that Can be Added While Online. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Determine When Data is Updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Input Data Update Flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Output Data Update Flowchart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 5
Table of Contents

Chapter 9
Safety I/O Devices Add Safety I/O Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Configure Safety I/O Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Use Network Address Translation with CIP Safety Devices . . . . . . . . . . . . . . . . . . . . . 113
Set the SNN of a Safety I/O Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Change a Safety I/O Device SNN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Copy and Paste a Safety I/O Device SNN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Safety I/O Device Signature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Configuration via the Logix Designer Application. . . . . . . . . . . . . . . . . . . . . . . . . 118
Different Configuration Owner (Data-only Connection) . . . . . . . . . . . . . . . . . . . . 119
Reset Safety I/O Device to Out-of-box Condition . . . . . . . . . . . . . . . . . . . . . . . . . 119
I/O Device Address Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Monitor Safety I/O Device Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Replace a Safety I/O Device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Configuration Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Safety I/O Replacement Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Chapter 10
Develop Standard Applications Elements of a Control Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Task Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Scheduled and Unscheduled Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Parameters and Local Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Program Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Programming Languages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Add-On Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Extended Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Access the Module Object from an Add-On Instruction . . . . . . . . . . . . . . . . . . . . . . . . 138
Monitor Controller Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Monitor I/O Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Determine If I/O Communication Has Timed Out . . . . . . . . . . . . . . . . . . . . . . . . . 140
Determine if I/O Communication to a Specific I/O Module has Timed Out. . . . . . 140
Automatic Handling of I/O Module Connection Faults. . . . . . . . . . . . . . . . . . . . . . 141
Sample Controller Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Chapter 11
Develop Safety Applications Safety Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Program Safety Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Chapter 12
Develop Secure Applications Controller Security Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Security Checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Configure User-definable Major Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Create a Fault Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Configure the Program to Use the Fault Routine . . . . . . . . . . . . . . . . . . . . . . . . . 150
Jump to the Fault Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

6 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Table of Contents

License-based Source and Execution Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Enable License-based Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Configure Change Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Configure Component Tracking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Configure Controller Logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Disable the Controller Ethernet Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Disable the Ethernet Port on the Port Configuration Tab . . . . . . . . . . . . . . . . . . . 156
Disable the Ethernet Port with an MSG Instruction . . . . . . . . . . . . . . . . . . . . . . . . 157
Disable the Controller CIP Security Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Use the Disable CIP Security Checkbox in FactoryTalk Linx. . . . . . . . . . . . . . . . . 158
Use a CIP Generic MSG Instruction in the Logix Designer Application . . . . . . . . . 159
Disable the Controller USB Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Disable the Controller SD Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Disable the Status Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Disable All Categories of Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Disable Individual Categories of Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Disable Controller Webpages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Studio 5000 Logix Designer Application Version 33 or Later . . . . . . . . . . . . . . . . 168
Studio 5000 Logix Designer Application Version 32 or Earlier . . . . . . . . . . . . . . . 168
Controller Web Page Default Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Use a CIP Generic MSG to Disable the Controller Webpages. . . . . . . . . . . . . . . . . 169
Use a CIP Generic MSG to Enable the Controller Webpages . . . . . . . . . . . . . . . . . 171
Configure Trusted Slots on the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Privacy Aspects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Data Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Data Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Chapter 13
Develop Motion Applications Motion Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Program Motion Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Obtain Axis Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Chapter 14
Troubleshoot the Controller Automatic Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Considerations for Communication Loss Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . 180
Controller Diagnostics with the Logix Designer Application . . . . . . . . . . . . . . . . . . . . 181
I/O Module Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Notification in the Tag Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Enable Major Fault on Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Port Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Advanced Time Sync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Controller Diagnostics with Linx-based Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Controller Webpages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Home Webpage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Faults Webpage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Tasks Webpage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Browse Chassis Webpage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 7

Table of Contents

Appendix A
Status Indicators Status Display and Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
General Status Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
GuardLogix Status Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Safety Partner Status Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Fault Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Major Fault Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
I/O Fault Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Controller Status Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
RUN Status Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
FORCE Status Indicator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
SD Status Indicator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Controller OK Status Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Safety Partner OK Status Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
EtherNet/IP Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Thermal Monitoring and Thermal Fault Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Appendix B
Change Controller Type Change from a Standard to a Safety Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Change from a Safety to a Standard Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Change Safety Controller Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

Appendix C
History of Changes Change Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

8 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Preface

About This Publication This manual provides information to help you design a system, operate a ControlLogix® or
GuardLogix®-based controller system, and develop applications.

You must be trained and experienced in the creation, operation, and maintenance of safety
systems.

For information on Safety Integrity Level (SIL) and Performance Level (PL) requirements and
safety application requirements, see the GuardLogix 5580 and Compact GuardLogix 5380
Safety Reference Manual, publication 1756-RM012.

Summary of Changes This publication contains the following new or updated information. This list includes
substantive updates only and is not intended to reflect all changes.
Topic Page
Updated Additional Resources table 9
Revised Controller Redundancy section 13
Revised Secure Controller Systems section 19
Added IEC-62443-4-2 SL 1 security certification content for safety controllers 145…174
Added statement about impact of license-based source protection on download times 151
Added Privacy Aspects section 174
Added information about unique code for troubleshooting major faults Type 1, Codes 60, 61, 62 201

Additional Resources These documents contain additional information concerning related products from Rockwell
Automation. You can view or download publications at rok.auto/literature.
Resource Description
ControlLogix 5580 Controllers Installation Instructions, Provides installation instructions for ControlLogix 5580 controllers.
publication 1756-IN043
GuardLogix 5580 Controllers Installation Instructions, Provides installation instructions for GuardLogix 5580 controllers.
publication 1756-IN048
ControlLogix Power Supply Installation Instructions, Describes how to install standard power supplies.
publication 1756-IN619
Hardware Installation
ControlLogix Redundant Power Supply Describes how to install redundant power supplies.
Installation Instructions, publication 1756-IN620
ControlLogix Chassis Installation Instructions, Describes how to install a ControlLogix chassis.
publication 1756-IN621
Replacement door labels for the 1756 I/O modules, Contains door labels for the 1756 I/O modules that are available to print.
publication IASIMP-SP021
1756 ControlLogix Controllers Technical Data, Provides specifications for ControlLogix controllers.
publication 1756-TD001
1756 ControlLogix I/O Specifications Technical Data, Provides specifications for ControlLogix I/O modules.
publication 1756-TD002
1756 ControlLogix Communications Modules Provides specifications for ControlLogix communications modules.
Specifications Technical Data, publication 1756-TD003
Technical Data
1756 ControlLogix Integrated Motion Modules Provides specifications for ControlLogix integrated motion modules.
Specifications Technical Data, publication 1756-TD004
1756 ControlLogix Power Supplies Specifications Provides specifications for ControlLogix power supplies.
Technical Data, publication 1756-TD005
1756 ControlLogix Chassis Specifications Provides specifications for a ControlLogix chassis.
Technical Data, publication 1756-TD006
Describes how to configure and use EtherNet/IP devices with a
EtherNet/IP Network Devices User Manual, Logix 5000® controller and communicate with various devices on the
publication ENET-UM006 Ethernet network.
Networks ControlNet® Network Configuration User Manual,
(ControlNet®, DeviceNet®, EtherNet/IP™) publication CNET-UM001 Provides information about ControlNet networks.
DeviceNet Media Design Installation Guide, Provides information about DeviceNet networks.
publication DNET-UM072

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 9

Preface

Resource Description
Logix SIS Safety Reference Manual, Describes Logix SIS systems, which are type-approved and certified for
publication 1756-RM015 use in safety applications.
Safety application requirements Contains detailed requirements to achieve and maintain
GuardLogix 5580 and Compact GuardLogix 5380 Safety SIL 2/PLd and SIL 3/PLe with the GuardLogix 5580 controller system via
Reference Manual, publication 1756-RM012 the Studio 5000 Logix Designer® application.
Integrated Motion on the EtherNet/IP Network
Configuration and Startup User Manual, Details how to design your ControlLogix system for Integrated Motion on
publication MOTION-UM003 the EtherNet/IP network applications.
Integrated Motion on the EtherNet/IP Network Detailed information on axis control modes and attributes for
Motion Reference Manual, publication MOTION-RM003 Integrated Motion on EtherNet/IP networks.
Motion Coordinate System User Manual, Details how to create and configure a coordinated motion
publication MOTION-UM002 application system.
SERCOS and Analog Motion Configuration and Startup Details how to configure a SERCOS motion application system.
User Manual, publication MOTION-UM001
Logix 5000 Controllers Design Considerations
Reference Manual, publication 1756-RM094 Provides information to help design and plan Logix 5000® systems.
High Availability System Reference Manual, Provides information to help design and plan high availability systems.
publication HIGHAV-RM002
Provides information about how to set up, configure, program, monitor,
Redundancy System User Manual, 1756-UM015 and troubleshoot high availability systems that use Logix SIS,
ControlLogix 5580, or ControlLogix 5570 redundancy.
Design Considerations Provides guidance on how to conduct security assessments, implement
System Security Design Guidelines Reference Manual, Rockwell Automation products in a secure system, harden the control
SECURE-RM001 system, manage user access, and dispose of equipment.
This document provides design choices and best practices for
FOUNDATION Fieldbus Design Considerations implementing a FOUNDATION Fieldbus network with the
Reference Manual, PROCES-RM005 1788-EN2FFR or 1788-CN2FFR linking devices.
Using Logix 5000 Controllers as Masters or Slaves on For more information about using Modbus sample programs.
Modbus Application Solution, publication CIG-AP129
Provides access to the Logix 5000 controllers set of programming
Logix 5000 Controllers Common Procedures manuals. The manuals cover such topics as how to manage project
Programming Manual, publication 1756-PM001 files, organize tags, program logic, test routines, faults, and more.
Programming Tasks and Procedures Logix 5000 Controllers General Instructions Provides information on the programming instructions available to use
Reference Manual, publication 1756-RM003 in Logix Designer application projects.
GuardLogix Safety Application Instruction Set Provides information about the GuardLogix safety application
Reference Manual, publication 1756-RM095 instruction set.
Provides declarations of conformity, certificates, and other
Product Certifications Product Certifications website, rok.auto/certifications. certification details.

10 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 1
ControlLogix and GuardLogix Systems
This chapter describes features of the ControlLogix® 5580 and GuardLogix® 5580 controllers.
Controller Type Cat. No.
ControlLogix controllers 1756-L81E, 1756-L82E, 1756-L83E, 1756-L84E, 1756-L85E
ControlLogix controllers with conformal coating 1756-L81EK, 1756-L82EK, 1756-L83EK, 1756-L84EK, 1756-L85EK
1756-L81E-NSE, 1756-L82E-NSE, 1756-L83E-NSE, 1756-L84E-NSE, 1756-L85E-NSE
ControlLogix No Stored Energy (NSE) controllers 1756-L81E-NSEXT, 1756-L82E-NSEXT, 1756-L83E-NSEXT, 1756-L84E-NSEXT, 1756-L85E-NSEXT
ControlLogix-XT™ controllers 1756-L81EXT, 1756-L82EXT, 1756-L83EXT, 1756-L84EXT, 1756-L85EXT
1756-L81EP, 1756-L83EP, 1756-L85EP,
ControlLogix Process controllers 1756-L81EPXT, 1756-L83EPXT, 1756-L85EPXT
GuardLogix controllers 1756-L81ES, 1756-L82ES, 1756-L83ES, 1756-L84ES, 1756-L85ES(1), 1756-L8SP
GuardLogix controllers with conformal coating 1756-L81ESK, 1756-L82ESK, 1756-L83ESK, 1756-L84ESK, 1756-L8SPK
1756-L81EXTS, 1756-L82EXTS, 1756-L83EXTS, 1756-L84EXTS, 1756-L8XTSP
GuardLogix-XT™ controllers 1756-L81ESXT, 1756-L82ESXT, 1756-L83ESXT, 1756-L84ESXT, 1756-L8SPXT
(1) Supported by Studio 5000 Logix Designer® version 36 or later.

Minimum Requirements The controllers have these minimum requirements:

• ControlLogix, ControlLogix-XT, or ControlLogix-ZXT chassis, series C or later
(series B chassis function within a derated temperature range)
• ControlLogix or ControlLogix-XT power supply
• Studio 5000 Logix Designer® application, Linx-based communication software, and
ControlFLASH Plus™ or ControlFLASH™ software
For compatible versions, see the Product Compatibility and Download Center (PCDC).

IMPORTANT If safety connections or safety logic are required for your application,
then you must use any GuardLogix 5580 controller.
GuardLogix project editing requires Studio 5000 Logix Designer
Professional, Full Edition, or a licensed GuardLogix Safety Editor.

IMPORTANT When a ControlLogix or GuardLogix product that is rated for harsh

environments (corrosive atmosphere, extended temperature, etc.) is
used in a system with other ControlLogix products that have lower
specification values, the system is derated to the lowest common value.
EXAMPLE: If the maximum operating temperature specification found
in the Technical Data for your ControlLogix-XT module is 70 °C (158 °F)
and you pair it with a ControlLogix chassis that is temperature rated to
60 °C (140 °F), your system is derated to 60 °C (140 °F).
To ensure that your system is equipped for harsh environments,
compare the corrosive atmosphere, temperature, and other
specifications found in the Technical Data publication for each product.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 11

Chapter 1 ControlLogix and GuardLogix Systems

ControlLogix Controllers The controllers are available with different functionality based on your application.

ControlLogix No Stored Energy (NSE) Controllers

The NSE controller is intended for use in applications that require the installed controller to
deplete its residual stored energy to specific levels before transporting it into or out of your
application.

The residual stored energy of the NSE controller depletes to 400 µJ or less in 40 seconds.
If your application requires the NSE controller to deplete its residual stored energy to 400 µJ or
less before you transport it into or out of the application, complete these steps before you
remove the controller.
1. Turn off power to the chassis.
After you turn off power, the OK status indicator on the controller transitions from
green to steady red to OFF.
2. Wait at least 40 seconds for the residual stored energy to decrease to 400 µJ or less
before you remove the controller.
There is no visual indication of when the 40 seconds has expired. You must track that
time period.

IMPORTANT When power is off, the real-time clock (RTC) does not retain its time and
date.

Some applications require that the installed controller to deplete its residual stored energy to
specific levels before transporting it into or out of your application. This requirement can
include other devices that also require a wait time before removing them. See the
documentation of those products for more information.

ControlLogix-XT and GuardLogix-XT Controllers

The ControlLogix-XT and GuardLogix-XT controllers function in the same way as the traditional
ControlLogix and GuardLogix controllers. They have the same features as the ControlLogix
standard controllers and GuardLogix controllers, but are rated for extreme environmental
conditions when used properly with other system components that share the same extreme-
environment ratings.
The ControlLogix-XT and GuardLogix-XT controllers are conformal coated to add a degree of
protection when exposed to harsh, corrosive environments. While the standard ControlLogix
system can withstand temperatures from 0…60 °C (33…140 °F), most of the components of the
ControlLogix-XT system can withstand temperatures from -25…+70 °C (-13…+158 °F).

Process Controllers
The process controller is an extension of the Logix 5000® controller family that focuses on
plant-wide process control. The process controller comes configured with a default process-
tasking model and dedicated PlantPAx® process instructions optimized for process
applications that improve design and deployment efforts.

The ControlLogix process controller hardware is also conformal coated to add a degree of
protection when exposed to harsh, corrosive environments, and can be used in temperature
extremes from -25…+70 °C (-13…+158 °F) when deployed as part of a Logix-XT system.

12 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 1 ControlLogix and GuardLogix Systems

Conformal Coated Products

ATTENTION: ControlLogix 5580 controllers that end with a 'K' or 'XT' are
shipped with port protection plugs installed to provide a degree of protection
from corrosive atmospheres. Once the factory packaging seal is broken, port
plugs must remain installed in unused ports at all times during storage and
operation for the product to meet its corrosive atmosphere rating. If
temporary access is required, the plugs can be removed and then reinserted
after temporary access is complete.

Controller Redundancy
You can use ControlLogix 5580 and GuardLogix 5580 controllers in a redundant configuration
for high availability.

For more information and requirements, see these publications:

• High Availability System Reference Manual, publication HIGHAV-RM002
• Redundancy Systems User Manual, publication 1756-UM015

ControlLogix System The ControlLogix system is chassis-based, which provides options for configuring various
communications and I/O capabilities. ControlLogix controllers support multiple programming
Applies to these controllers: languages that enable sequential, process, motion, and drive control.
ControlLogix 5580
Standalone Controller and I/O
A simple controller configuration is a standalone controller with I/O in one chassis.
Figure 1 - Standalone Controller and I/O

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 13

Chapter 1 ControlLogix and GuardLogix Systems

Multiple Controllers in One Chassis

You can use multiple controllers in one ControlLogix chassis. This example shows the following
controllers in the same chassis:
• ControlLogix 5580 controller (slot 0) connected directly to the EtherNet/IP™ network
• ControlLogix 5570 controller (slot 1) connected to the network through a 1756-EN2TR
module (slot 7)
• GuardLogix 5580 controller in a SIL 2/PLd configuration (slot 5) connected directly to the
EtherNet/IP Network.
Figure 2 - Multiple Controllers in One Chassis

PowerFlex 755 Drive

5069-AENTR Adapter
Compact 5000 I/O 1756-L85E 1756-L72 1756-L84ES 1756-EN2TR

PanelView Plus 7

Stratix Switch

1734-AENTR Adapter
1734 POINT I/O

1734-AENTR Adapter
1734 POINT Guard I/O Safety Device

5069-AENTR Adapter PowerFlex 527 Drive

Compact 5000 I/O CIP Safety Enabled

IMPORTANT You cannot bridge through the front Ethernet port of another controller
to add remote I/O.

14 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 1 ControlLogix and GuardLogix Systems

Multiple Devices Connected via Multiple Networks

For some applications, various devices can be connected to the ControlLogix chassis via
multiple communication networks. For example, a system can have these devices and network
connections:
• Distributed I/O connects to an EtherNet/IP network
• A PowerFlex® drive connects to a DeviceNet® network
• Distributed I/O connects to a ControlNet® network
• Flowmeters use HART connectivity
Figure 3 - Multiple Devices Connected via Multiple Networks

DeviceNet HART

ControlNet EtherNet/IP

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 15

Chapter 1 ControlLogix and GuardLogix Systems

GuardLogix System The GuardLogix system can communicate with safety I/O devices via CIP Safety™ over an
EtherNet/IP network. For example, the network can include Guard I/O™ modules, integrated
Applies to these controllers: safety drives, and integrated safety components.
GuardLogix 5580
With a GuardLogix controller, you can interface to local standard I/O in the backplane via
standard tasks while you interface with remote safety I/O through the EtherNet/IP port.

For standard tasks, GuardLogix controllers support these programming languages:

• Ladder Diagram (LD)
• Structured Text (ST)
• Function Block Diagram (FBD)
• Sequential Function Chart (SFC)

For the safety task, GuardLogix controllers support Ladder Diagram only.

The GuardLogix system supports up to and including SIL 3 and PLe safety applications:
• Without a safety partner installed, you can achieve SIL 2/PLd (Category 3) with the use
of the safety task and safety I/O.
• With the safety task and a safety partner installed, you can achieve SIL 3/PLe
(Category 4) capability.

For SIL 3 safety applications, the GuardLogix system is composed of a primary GuardLogix
controller and a safety partner that function together in a 1oo2 architecture.
• The primary controller is the processor that performs standard and safety functions
and communicates with the safety partner for safety-related functions in the
GuardLogix control system.
• The safety partner is a co-processor that provides an isolated second channel for
safety-related functions in the system. The safety partner does not have a keyswitch or
communication port. The primary controller controls the configuration and operation of
the safety partner.
• The safety partner must be installed in the slot immediately to the right of the primary
controller. The firmware major and minor revisions of the primary controller and safety
partner must match exactly to establish the control partnership that is required for
safety applications
For information on Safety Integrity Level (SIL) and Performance Level (PL) requirements and
safety application requirements, see the GuardLogix 5580 and Compact GuardLogix 5380
Safety Reference Manual, publication 1756-RM012.

16 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 1 ControlLogix and GuardLogix Systems

GuardLogix with Safety I/O and Integrated Safety Drives

In this example, one GuardLogix controller makes the motion and safety connections.

IMPORTANT If one controller controls an application with motion and safety

connections, it must be a safety controller, such as the GuardLogix 5580
controller.
Figure 4 - Motion and Safety Configuration (One Controller)
Stratix Switch

Logix Designer Application GuardLogix 5580 Controller

GuardLogix 1756-L8SP Safety Partner

5069-IB8S 5069-OBV8S

5069-AENTR
Compact 5000 I/O

Kinetix 5700 Servo Drive System

MOD MOD MOD MOD

NET NET NET NET

Safety Device
2 2 2 2
2198-CAPMOD-2240
1 1 1 1
Capacitor Module
Digital Inputs to Sensors and Control String
1
I/O I/O-A I/O-B I/O-A I/O-B
1 6 1 6 1 6 1 6 1 6
4
I/O

5 10 5 10 5 10 5 10 5 10

UFB UFB-A UFB-B UFB-A UFB-B

D+ D+ D+ D+
D- D- D- D-

MF-A MF-B MF-A MF-B

-
MBRK
+

Kinetix VP
Servo Motor

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 17

Chapter 1 ControlLogix and GuardLogix Systems

In this example, a standard controller makes the motion-only connection and a separate
GuardLogix 5580 controller makes the safety-only connection.

IMPORTANT If two controllers are used in an application with motion-only and safety-
only connections, the safety-only connection must be a GuardLogix
controller while the motion-only connection can be made by either a
standard or a safety controller.
Figure 5 - Motion and Safety Configuration (Multiple Controllers)
ControlLogix 5580 Controller Stratix Switch Logix Designer Application

1734-AENTR
POINT Guard I/O EtherNet/IP Adapter

GuardLogix 5580 Controller Safety Device

GuardLogix 1756-L8SP Safety Partner

Kinetix 5700 Servo Drive System

MOD MOD MOD MOD

NET NET NET NET

2 2 2 2

1 1 1 1 2198-CAPMOD-2240
Digital Inputs to Sensors and Control String 1

4
I/O
1
I/O
6 1
I/O-A
6 1
I/O-B
6 1
I/O-A
6 1
I/O-B
6

Capacitor Module
5 10 5 10 5 10 5 10 5 10

UFB UFB-A UFB-B UFB-A UFB-B

D+ D+ D+ D+
D- D- D- D-

MF-A MF-B MF-A MF-B

-
MBRK
+

Kinetix VP
Servo Motor

Item Description
A Motion program—Module definition configured with Motion Only connection
B Safety program—Module definition configured with Safety Only connection

18 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 1 ControlLogix and GuardLogix Systems

Design the System When you design a system, there are several system components to consider for your
application:
Applies to these controllers:
• I/O devices
ControlLogix 5580
GuardLogix 5580
• Motion control axes and drives
• Communication modules
• Controllers
• Chassis
• Power supplies
• Studio 5000 Logix Designer application

Safety systems also have these components to consider:

• Safety controller
• Safety partner for SIL 3/PLe applications
• Safety I/O
• Safety devices

For more information to design and select components for your system, see the following:
• 1756 ControlLogix Controllers Technical Data, publication 1756-TD001
• 1756 ControlLogix I/O Specifications Technical Data, publication 1756-TD002
• GuardLogix 5580 and Compact GuardLogix 5380 Safety Reference Manual, publication
1756-RM012

CIP Security CIP Security™ is a standard, open-source communication mechanism that helps to provide a
secure data transport across an EtherNet/IP network. CIP Security lets CIP™-connected
Applies to these controllers: devices authenticate each other before transmitting and receiving data.
ControlLogix 5580
GuardLogix 5580 CIP Security uses the following security properties to help devices protect themselves from
malicious communication:
• Device Identity and Authentication
• Data Integrity and Authentication
• Data Confidentiality

Rockwell Automation uses the following products to implement CIP Security:

• FactoryTalk® Policy Manager software (includes FactoryTalk System Services, version
6.20 or later)
• FactoryTalk Linx software, version 6.11 or later (lets workstation software communicate
securely using CIP Security)
• Studio 5000 Logix Designer application, version 31 or later
This application is required to interface with CIP Security-enabled Logix controllers. The
minimum application version varies by controller product family.

For more information on CIP Security, for example, a list of CIP Security-capable products and
publications that describe how to use the products, including limitations and considerations,
see the following:
• The website is available at https://www.rockwellautomation.com/en-us/capabilities/
industrial-security/security-products/cip-security.html
• CIP Security with Rockwell Automation Products Application Technique, publication
SECURE-AT001

Secure Controller Systems ControlLogix 5580 controllers, firmware revision 32 and later, and GuardLogix 5580 controllers,
firmware revision 37 and later, support IEC-62443-4-2 SL 1 requirements. For security features
and system requirements, see Develop Secure Applications.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 19

Chapter 1 ControlLogix and GuardLogix Systems

ControlLogix 5580 This table lists the system, communication, and programming features available with
ControlLogix 5580 controllers.
Controller Features
Table 1 - ControlLogix 5580 Controller Features
1756-L81E, 1756-L83E, 1756-L85E, 1756-L85EK,
1756-L81EK, 1756-L82E, 1756-L83EK, 1756-L84E, 1756-L85E-NSE,
1756-L81E-NSE, 1756-L82EK, 1756-L83E-NSE, 1756-L84EK, 1756-L85E-NSEXT,
Feature 1756-L81E-NSEXT, 1756-L82E-NSE, 1756-L83E-NSEXT, 1756-L84E-NSE, 1756-L85EXT,
1756-L81EXT, 1756-L82E-NSEXT, 1756-L83EXT, 1756-L84E-NSEXT, 1756-L85EP,
1756-L81EP, 1756-L82EXT, 1756-L83EP, 1756-L84EXT 1756-L85EPXT
1756-L81EPXT 1756-L83EPXT
User Memory 3 MB 5 MB 10 MB 20 MB 40 MB
(3) (3) (2) (3)
60 nodes 80 nodes 100 nodes 150 nodes
EtherNet/IP nodes supported, max(1) 300 nodes(5)
100 nodes(4) 175 nodes(4) 250 nodes(4) 250 nodes(4)
1 - USB port, 2.0 full-speed, Type B
Communication ports 1 - EtherNet/IP port: 10 Mbps, 100 Mbps, 1 Gbps link speeds
• EtherNet/IP
• ControlNet
• DeviceNet
Communication options • Data Highway Plus™
• Remote I/O
• SynchLink™
• Third-party process and device networks
CIP Security See CIP Security.
• 32 tasks
Controller tasks • 1000 programs/task
• Event tasks: all event triggers
• Integrated Motion on the EtherNet/IP network
• Sercos interface(6)
Integrated motion • Analog options(6):
– Encoder input
– Linear displacement transducer (LDT) input
– Serial Synchronous Input (SSI)
• Ladder Diagram (LD)
• Structured Text (ST)
Programming languages
• Function Block Diagram (FBD)
• Sequential Function Chart (SFC)
(1) A node is an EtherNet/IP device that you add directly to the I/O configuration and counts toward the controller node limits.
(2) Logix Designer application versions 28 and 29.
(3) Logix Designer application version 29.
(4) Logix Designer application version 30 or later.
(5) Logix Designer application version 28 or later.
(6) Logix Designer application version 31 or later.

20 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 1 ControlLogix and GuardLogix Systems

GuardLogix 5580 This table lists the system, communication, and programming features available with
GuardLogix 5580 controllers.
Controller Features
Table 2 - GuardLogix 5580 Controller Features
1756-L81ES, 1756-L82ES, 1756-L83ES, 1756-L84ES,
1756-L81ESK, 1756-L82ESK, 1756-L83ESK, 1756-L84ESK,
Feature 1756-L81EXTS 1756-L82EXTS, 1756-L83EXTS, 1756-L84EXTS, 1756-L85ES(1)
1756-L81ESXT 1756-L82ESXT 1756-L83ESXT 1756-L84ESXT
User Memory 3 MB 5 MB 10 MB 20 MB 40 MB
Safety Memory 1.5 MB 2.5 MB 5 MB 6 MB 3 MB
EtherNet/IP nodes supported, max 100 175 250 250 300
1 - USB port, 2.0 full-speed, Type B
Communication ports 1 - EtherNet/IP port: 10 Mbps, 100 Mbps, 1 Gbps link speeds
• EtherNet/IP (1756-EWEB cannot be used for safety connections)
• Support for Network Address Translation (NAT)
• ControlNet
• DeviceNet
Communication options
• Data Highway Plus™
• Remote I/O
• SynchLink™
• Third-party process and device networks
CIP Security See CIP Security.
• 31 standard tasks, 1 safety task
Controller tasks • 1000 programs/task
• Event tasks: all event triggers
Integrated motion is supported in standard task only.
• Integrated Motion on the EtherNet/IP network
• Sercos interface
Integrated motion • Analog options:
– Encoder input
– Linear displacement transducer (LDT) input
– Serial Synchronous Input (SSI)
• For the safety task, GuardLogix controllers support Ladder Diagram only.
• For standard tasks, GuardLogix controllers support:
Programming languages – Ladder Diagram (LD)
– Structured Text (ST)
– Function Block Diagram (FBD)
– Sequential Function Chart (SFC)
• Integrated safety on the EtherNet/IP network (Kinetix® drives, PowerFlex drives, safety components)
Integrated safety • Distribute and control safety I/O (over EtherNet/IP and DeviceNet networks only)
• Produce and consume safety tag data.
• Data access control
• Firmware Supervisor
Controller Features • Secure Digital (SD) card
• Safety Connections
• Standard Connections
(1) Supported by Logix Designer application version 36 or later.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 21

Chapter 1 ControlLogix and GuardLogix Systems

Features Supported by GuardLogix 5580 Controllers via the

Safety Task
In the Logix Designer application, version 31 or later, the Safety task supports a subset of
features that are supported in the standard task as listed in this table.
Table 3 - Safety Task Features
Studio 5000 Logix Designer Application, Version 31 or Later
Feature
Safety Task Standard Task
Add-On instructions X X
Instruction-based alarms and events — X
Tag-based alarms — X
Controller logging X X
Event tasks(1) — X
Function block diagrams (FBD) — X
Integrated motion X(2) X
Analog motion — X
Sercos motion — X
Drive safety instructions X —
Ladder Diagram (LD) X X
Language switching X X
License-based source protection — X
Online import of program components — X
Online export of program components X X
Sequential function chart (SFC) routines — X
Structured Text (ST) — X
(1) While the safety task cannot be an Event task, standard Event tasks can be triggered with the use of the Event instruction in
the safety task.
(2) Limited to the use of drive safety instructions with Kinetix 5700 ERS4 drives.

IMPORTANT Safety Consideration

GuardLogix 5580 controllers can produce standard tags as unicast or multicast, but they can only produce safety tags
as unicast. The controllers can consume safety tags as either unicast or multicast.
When you configure a produced safety tag, you are only allowed to configure unicast connection options. The
Logix Designer application does not allow you to configure multicast connection options.
When you configure a consumed tag, you must consider the capabilities of the producer:
• If the producer in the I/O tree of this controller is a GuardLogix 5580 or Compact GuardLogix 5380 controller, and you
are consuming a safety tag, you must configure the consumed tag to use unicast.
• If the producer in the I/O tree of this controller is a GuardLogix 5570, GuardLogix 5560, or Compact GuardLogix 5370
controller, the safety-consumed tag can be configured as either unicast or multicast.
• GuardLogix 5580 controllers do not produce safety tags to GuardLogix 5570 controllers with firmware revision 30 or
earlier in the same chassis. GuardLogix 5580 controllers can only produce safety tags as unicast. GuardLogix 5570
controllers with firmware revision 30 or earlier cannot configure consumed tags as unicast. This restriction does not
apply over the EtherNet/IP network because consumed tags can be configured for unicast.

22 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 2
Safety Concept of GuardLogix Controllers
Functional Safety Capability The GuardLogix® 5580 controller system is certified for use in safety applications up to and
including SIL 2/PLd and SIL 3/PLe where the de-energized state is the safe state:
Applies to these controllers:
• For SIL 3/PLe safety applications, the GuardLogix system is composed of a primary
GuardLogix 5580 controller and a safety partner that function together in a 1oo2 architecture.
• For SIL 2/PLd and SIL 3/PLe safety system requirements, including functional validation
test intervals, system reaction time, and PFD/PFH calculations, see the GuardLogix 5580
and Compact GuardLogix 5380 Safety Reference Manual, publication 1756-RM012.

You must read, understand, and fulfill these requirements before you operate a GuardLogix
SIL 2/PLd or SIL 3/PLe safety system.

Safety Network Number A safety network number (SNN) uniquely identifies CIP Safety™ subnets within a routable
safety network. The combination of the SNN + Node Address uniquely identifies each CIP
Safety port on each device in the routable safety network. GuardLogix 5580 controllers require
two SNNs:
• An SNN for the backplane
• An SNN for the Ethernet port

For an explanation of SNNs, see the GuardLogix 5580 and Compact GuardLogix 5380 Safety
Reference Manual, publication 1756-RM012. To assign SNNs, see Assign the Safety Network
Number (SNN).
Figure 6 - Safety Network Numbers

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 23

Chapter 2 Safety Concept of GuardLogix Controllers

Safety Signature The GuardLogix system uses a safety signature to verify the integrity of a safety application:
• The safety signature applies to the entire safety portion of the controller project. The
ability to create, record, and verify that the safety signature is a mandatory part of the
safety-application development process. The safety signature must be present to
operate as a SIL 2/PLd or SIL 3/PLe safety controller. Nothing in the standard
application is included in the safety signature.
• The safety signature is a hierarchy of multiple safety signature elements. For example,
the safety task, programs, and routines are examples of safety signature elements.
Safety signature elements can help you during impact analysis by identifying the
individual changes within a controller project. If your validation plan does not require
revalidation of unchanged elements, your certification effort can be reduced.
All safety signature elements are created at the time that you generate the safety
signature for the project. To view all safety signature elements for a project, you can
run the Safety Signature report.

The safety signature and each of its elements have the following:
• Safety signature ID--A unique 64-character alphanumeric identification number.
• Time stamp—The date and time that the safety signature was generated. For a safety
signature element, the time stamp changes whenever its signature ID changes.
Figure 7 - Safety Signature

For details about the safety signature, safety signature elements, and how to generate the
safety signature and the Safety Signature report, see the GuardLogix 5580 and Compact
GuardLogix 5380 Safety Reference Manual, publication 1756-RM012.

Distinguish between Slots of a GuardLogix system chassis that are not used by the safety function can be populated
with other ControlLogix® modules that are certified to the Low Voltage and EMC Directives. See
Standard and Safety the Rockwell Automation Product Certifications page (rok.auto/certifications) to find the CE
Components certificate for the ControlLogix Product Family, and determine the modules that are certified.

You must create and document a clear, logical, and visible distinction between the safety and
standard portions of the controller project. As part of this distinction, the Studio 5000 Logix
Designer® application features safety identification icons to identify the safety task, safety
programs, safety routines, and safety components.

In addition, the Logix Designer application uses a safety class attribute that is visible
whenever safety task, safety programs, safety routine, safety tag, or safety Add-On Instruction
properties are displayed.

24 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 2 Safety Concept of GuardLogix Controllers

Controller Data Flow The following illustration explains the standard and safety data flow capabilities of the
GuardLogix controller.
Capabilities
Figure 8 - Data-flow Capabilities

GuardLogix Controller

Standard Safety
Safety Task
Standard Tasks
Safety Programs
Standard Programs
Safety Routines
Standard Routines

Program Safety Data

Program Data

Controller Standard Tags Controller Safety Tags

Item Description
1 Standard tags and logic behave the same way that they do in a standard ControlLogix controller.
2 Standard tag data, program- or controller-scoped, can be exchanged with external HMI devices, personal
computers, and other controllers.
GuardLogix controllers are integrated controllers with the ability to move standard tag data into safety
tags for use within the safety task. This is the only way to get standard tag data into the safety task.
Safety logic in the safety task cannot read or write the standard tag that is the source in the tag-mapping
data transfer. Safety logic can only reference the safety tag destination of the mapping. But, it can read
3 and write that safety tag.

ATTENTION: Mapped tag data must not be used to control a

SIL 2/PLd or SIL 3/PLe output directly.
4 Controller-scoped safety tags can be read directly by standard logic.
5 Safety tags can be read or written by safety logic.
Safety tags can be exchanged between safety controllers over EtherNet/IP™ or ControlNet® networks,
6 including GuardLogix and Compact GuardLogix controllers.
Safety tag data, program- or controller-scoped, can be read by external devices, such as HMI devices,
personal computers, or other standard controllers. External devices cannot write to safety tags whether
7 the controller is protected or not.
Once this data is read, it is considered standard data, not SIL 3/PLe data.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 25

Chapter 2 Safety Concept of GuardLogix Controllers

Safety Terminology This table defines safety terms that are used in this manual.
Table 4 - Safety Terms and Definitions
Abbreviation Full Term Definition
Identifies the programmable electronic controller
1oo1 One Out of One architecture. 1oo1 is a single-channel system.
Identifies the programmable electronic controller
1oo2 One Out of Two architecture. 1oo2 is a dual-channel system.
Common Industrial Protocol –
CIP Safety SIL 3/PLe-rated version of CIP™.
Safety Certified
DC Diagnostic Coverage The ratio of the detected failure rate to the total failure rate.
Probability of a dangerous failure The average probability of a system to fail to perform its
PFD on demand design function on demand.
Average frequency of a The probability of a system to have a dangerous failure occur
PFH dangerous failure per hour per hour.
PL Performance Level ISO 13849-1 safety rating.
A relative level of risk-reduction provided by a safety function,
SIL Safety Integrity Level or to specify a target level of risk reduction.
SIL CL SIL Claim Limit The maximum safety integrity level (SIL) that can be achieved.
SNN Safety Network Number A unique number that identifies a section of a safety network.
Unique Node ID (also called The unique node reference is a combination of a safety
UNID unique node reference) network number (SNN) and the node address of the node.

26 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 3
Connect to a Controller
Before you can connect to the controller through the Ethernet or USB port, you must configure
Applies to these controllers:
the EtherNet/IP™ or USB driver in Linx-based software on your workstation.
ControlLogix® 5580 • The controller has an Ethernet port that supports 10 Mbps, 100 Mbps, or 1 Gbps.
GuardLogix® 5580 • The controller has a USB port that uses a Type B receptacle. The port is USB 2.0
compatible and runs at 12 Mbps.
• Install and configure a communication module in the chassis with the controller as
described in the installation instructions for the communication module.

For more information on how to install communication drivers, see the EtherNet/IP Network
Device User Manual, publication ENET-UM006.

Set the IP Address When the controller is in the out-of-the-box state, the following apply regarding IP addresses:
• The controllers ship without an IP address.
• The controller is DHCP-enabled. That is, the controller is 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.

Requirements
To set the IP address, have the following:
• EtherNet/IP or USB drivers that are installed on the programming workstation
• MAC ID from the device, which is on the label on the side of the device
• Recommended IP address for the device

Other Methods to Set the IP Address

The controller supports the following methods to change the IP address:
• BOOTP/DHCP utility
• RSLinx® Classic software
• Studio 5000 Logix Designer® application

For more information on how to use these methods, see EtherNet/IP Network Device User
Manual, publication ENET-UM006.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 27

Chapter 3 Connect to a Controller

Duplicate IP Address The controller verifies that its IP address does not match any other network device IP address
when you perform either of these tasks:
Detection
• Connect the module 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 steady 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.
For details about how to assign IP addresses, see the EtherNet/IP Network Devices User
Manual, publication ENET-UM006.
Duplicate IP Address Detection Resolution Process
Conditions
1. The device that began operation first uses the IP address and continues
• Both devices support duplicate IP to operate without interruption.
address detection. 2. The device that begins operation second detects the duplication and
• A second device is added to the enters Conflict mode.
network after the first device is To assign a new IP address to the controller and leave Conflict mode, set
operating on the network. the network IP address with the BOOTP DHCP EtherNet/IP Commissioning
Tool.
Both EtherNet/IP devices enter Conflict mode.
• Both devices support duplicate IP To resolve this conflict, follow these steps:
address detection
1. Assign a new IP address to the controller. Set the network IP address with
• Both devices were powered up at the BOOTP DHCP EtherNet/IP Commissioning Tool.
approximately the same time.
2. Cycle power to the other device.
1. Regardless of which device obtained the IP address first, the device that
does not support IP address detection uses the IP address and continues
to operate without interruption.
One device supports duplicate IP
address detection and a second 2. The device that supports duplicate IP address detection detects the
device does not duplication and enters Conflict mode.
To assign a new IP address to the controller and leave Conflict mode, set
the network IP address with the BOOTP DHCP EtherNet/IP Commissioning
Tool.

28 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 3 Connect to a 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.

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
configuration tree or in a message path. If the domain name of the
destination module differs from the domain name of the source module,
then use a fully qualified DNS name (hostname.domainname). For
example, to send a message from EN2T1.location1.companyA to
EN2T1.location2.companyA, the host names match, but the domains
differ. Without the entry of a fully qualified DNS name, the module adds
the default domain name to the specified host name.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 29

Chapter 3 Connect to a Controller

Update Controller Firmware To update your controller firmware, complete these tasks:
Applies to these controllers:
• Determine Required Controller Firmware
ControlLogix 5580 • Obtain Controller Firmware
GuardLogix 5580 • Use ControlFLASH Plus or ControlFLASH Software to Update Firmware
or
Use AutoFlash to Update Firmware

Firmware Update Guidelines for Safety Controllers

IMPORTANT Safety Consideration
You cannot update a controller that is safety-locked.

The IEC 61508 functional safety standard requires impact analysis before you upgrade or
modify components in a certified, functional safety system. This section provides high-level
guidance on how you can perform the impact analysis for safety controller hardware/firmware
upgrades. Reference the standard to make sure you fulfill all requirements as they relate to
your application.

When you upgrade controller firmware to a newer version, consider the following:
• All major and minor firmware releases for GuardLogix controller systems are certified
for use in safety applications. As part of the certification process, Rockwell Automation
tests the safety-related firmware functions, such as the CIP Safety™ communication
subsystems, embedded safety instruction execution, and safety-related diagnostic
functions. The firmware release notes identify changes to safety-related functions.
• Perform an impact analysis of the planned firmware update:
- Review of the firmware release notes for changes in safety-related functionality.
- Review of hardware and firmware compatibility in the Product Compatibility and
Download site to identify potential compatibility conflicts.
- Any modification or enhancement of your validated software must be planned and
analyzed for any impact to the functional safety system as described in the 'Edit Your
Safety Application' section in the safety reference manual for your controller.
• You must remove and regenerate the safety signature as part of the firmware update
process. Use the online and offline edit process that is described in the safety
reference manual for your controller.
For more controller-specific information, see the GuardLogix 5580 and Compact
GuardLogix 5380 Safety Reference Manual, publication 1756-RM012.
IMPORTANT GuardLogix 5580 controllers have a different compiler than earlier
controllers. You must revalidate that applications on earlier controllers
compile correctly on GuardLogix 5580 controllers.

For product change management guidelines and product version management definitions, see
System Security Design Guidelines Reference Manual, publication SECURE-RM001.
Example:
1. From the Product Compatibility and Download Center:
a. Review all firmware release notes, starting with the original firmware revision
through the new firmware revision, to identify any changes that impact the safety-
related implementation of the application.
b. Review hardware and firmware compatibility to identify any restrictions between the
original system components and the new system components.
2. Perform a hazard and risk assessment for any changes that are identified during the
impact analysis and determine what additional testing is necessary.
3. Perform the online and offline edit process that is described in the safety reference
manual for your controller. You can restrict the 'Test the Application' block to the
testing identified by the hazard and risk assessment.
30 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025
 Chapter 3 Connect to a Controller

Determine Required Controller Firmware

IMPORTANT The controller must be in Remote Program or Program mode and all
major recoverable faults must be cleared to accept updates.

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

IMPORTANT Safety Consideration

For a GuardLogix system that includes a Safety Partner (SIL 3/PLe only),
the firmware on the primary controller and safety partner must match.
When you update the firmware on the primary controller, the safety
partner updates automatically.

Obtain Controller Firmware

You can obtain controller firmware in these ways:
• Install the Studio 5000 Logix Designer® application and use the packaged firmware.

IMPORTANT The firmware that is packaged with the software installation is the initial
release of the controller firmware. Subsequent firmware revisions to
address anomalies can be released during the life of a product.
We recommend that you check the Product Compatibility and Download
Center (PCDC) to determine if later revisions of the controller firmware
are available.
• From the PCDC, download revisions of controller firmware, and download controller
firmware, associated files, and product release notes.
ControlFLASH Plus™ software version 2.00.00 or later provides integration with PCDC for
an enhanced experience while you browse for firmware revisions, downloads, release
notes, and access to important notices.
Visit the PCDC at rok.auto/pcdc.

Use ControlFLASH Plus or ControlFLASH Software to Update Firmware

For information on how to download, install, and use ControlFLASH Plus or ControlFLASH™
software, see:
• ControlFLASH Plus Quick Start Guide, publication CFP-QS001
• ControlFLASH User Manual, publication 1756-UM105

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 31

Chapter 3 Connect to a Controller

Use AutoFlash to Update Firmware

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

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

1. Verify that the network connection is made and your network driver is configured in
Linx-based communication software.
2. Use the Logix Designer application to create a controller project.
3. On the Path bar, click Who Active.

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

5. On the Choose Firmware Revision dialog box, browse to the location of the firmware
files (C:\Program Files (x86)\ControlFLASH).

32 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 3 Connect to a Controller

6. Select the firmware revision, and click Update.

7. On the Confirmation dialog box, click Yes.

8. On the ControlFLASH Attention dialog box, click OK.
The firmware update begins.
Allow the firmware update to complete without interruption. When the firmware update
is complete, the progress dialog box closes.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 33

Chapter 3 Connect to a Controller

Notes:

34 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 4
Communication Networks
Several communication networks are available.

This table describes typical application features that are used with ControlLogix® and
GuardLogix® systems, and lists the networks available to support such application features.
Table 5 - Applications and Supported Networks
Application Features Networks for Standard Communications Networks for CIP Safety™ Communication
Integrated Motion, analog, or SERCOS motion interfaces EtherNet/IP™ EtherNet/IP
Time synchronization EtherNet/IP EtherNet/IP
• EtherNet/IP
• DeviceNet®
• ControlNet®
Control of distributed I/O Time synchronization does not use the safety protocol.
• Foundation Fieldbus
• HART
• Universal remote I/O
• EtherNet/IP • EtherNet/IP
Produce/consume data between controllers
• ControlNet • ControlNet
• EtherNet/IP
Messaging to and from other devices, including access to • ControlNet
the controller via the Studio 5000 Logix Designer® • DeviceNet (only to devices) Messaging does not use the safety protocol.
application • Data Highway Plus™ (DH+™)
• DH-485

EtherNet/IP Network The EtherNet/IP network offers control, configuration, and data collection services by layering
the Common Industrial Protocol (CIP™) over the standard Internet protocols, such as TCP/IP
Communication and UDP. This combination of standards provides full support for information data exchange
Applies to these controllers: and control applications.
ControlLogix 5580
GuardLogix 5580
IMPORTANT You cannot bridge through the Ethernet front port of another controller
to add remote I/O.

EtherNet/IP Port Speeds

The controller supports 10 Mbps/100 Mbps/1 Gbps EtherNet/IP port speeds.

Network performance in the controller system is optimal if the 1 Gbps speed is used. However,
legacy Ethernet devices do not support the 1 Gbps speed. Instead, they support a maximum
rate of 100 Mbps.

The difference in maximum link speeds impacts your controller system and, in some
applications, restricts you from using the 1 Gbps link speeds on a controller.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 35

Chapter 4 Communication Networks

When you design a controller system and consider using the 1 Gbps rate on the controller,
remember the following:
• You can use the 1 Gbps speed on the controller port when all network devices support
1 Gbps, for example, 5069-AEN2TR adapters with Compact 5000® I/O modules.
When switches are used in a star topology, configure the controller ports to use Auto
Negotiate.
Figure 9 - 1 Gbps EtherNet/IP Network Example
ControlLogix 5580 or
GuardLogix 5580 Controller
1756 I/O

5069-AENTR Adapter
Compact 5000 I/O
1 Gbps

5069-AENTR Adapter
1 Gbps Compact 5000 I/O
1 Gbps

1 Gbps
Stratix Switch
with Gigabit Copper Ports 5069-AENTR Adapter
Compact 5000 I/O

• You can use the 1 Gbps speed on the controller port when some network devices
support a maximum link speed of 100 Mbps. However, the controller must be connected
to those devices through a managed switch.
Figure 10 - 1 Gbps with 100 Mbps EtherNet/IP Network Example

PowerFlex 755 Drive

5069-AENTR Adapter
Compact 5000 I/O 1756-L85E 1756-L72 1756-L84ES 1756-EN2TR

1 Gbps 1 Gbps

100 Mbps
1 Gbps
PanelView Plus 7

100 Mbps
100 Mbps

1 Gbps Stratix Switch

100 Mbps
1734-AENTR Adapter
1734 POINT I/O

1734-AENTR Adapter
1734 POINT Guard I/O Safety Device

5069-AENTR Adapter PowerFlex 527 Drive

Compact 5000 I/O CIP Safety Enabled

36 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 4 Communication Networks

• Do not mix 1 Gbps and 100 Mbps port speeds within one DLR network or linear network.

IMPORTANT Do not use different speeds on device ports in the same EtherNet/IP
network without a managed switch.
If you use two or more of these components with a legacy Ethernet
device in a ring or linear topology, set all devices to a fixed speed of
100 Mbps and full-duplex:
• ControlLogix 5580 or GuardLogix 5580 controllers
• CompactLogix™ 5380 Controllers
• 5069 communication adapters
• 5094 communication adapters
This can help prevent bursts of traffic and DLR traffic reversal due to a
ring break from causing issues.
Figure 11 - 100 Mbps EtherNet/IP Network Example with An Unmanaged Switch

1756-L85E
1756 I/O
Remote I/O

1756-EN2T

CompactLogix 5570

100 Mbps 100 Mbps

1794-AENT
100 Mbps 100 Mbps
Switch
PowerFlex 700S 100 Mbps 100 Mbps

1794-AENT

100 Mbps

DLR Network Connected via Ethernet Tap

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 37

Chapter 4 Communication Networks

EtherNet/IP Communication Modules

ControlLogix 5580 and GuardLogix 5580 controllers feature one or more front Ethernet ports
that can be used for these purposes:
• Directly connect the controller to an EtherNet/IP network without requiring a bridge.
• Communicate with distributed I/O modules and other EtherNet/IP devices.
• Bridge messages over an EtherNet/IP network.
• Support 10 Mbps, 100 Mbps, 1 Gbps port speeds.

You can use the following communication modules for network communication.
Table 6 - EtherNet/IP Communication Modules
Communication Module Description
• Directly connects the controller to an EtherNet/IP network without
requiring a bridge.
• Communicates with distributed I/O modules and other EtherNet/IP
1756-EN2T, 1756-EN2TK, 1756-EN2TXT devices.
• Bridges messages over an EtherNet/IP network.
• 1756-EN2TXT operates in extreme environments with -25…+70 °C
(-13…+158 °F) temperatures.
• Performs the same functions as the 1756-EN2T modules.
• Supports communication for a single-fault tolerant Device Level Ring
1756-EN2TR, 1756-EN2TRK, (DLR) network.
1756-EN2TRXT • Supports a linear topology.
• 1756-EN2TRXT operates in extreme environments with -25…+70 °C
(-13…+158 °F) temperatures.
• Performs the same functions as the 1756-EN2T modules.
1756-EN2F, 1756-EN2FK
• Connects fiber media by an LC fiber connector on the module.
• Performs the same functions as the 1756-EN2T modules.
1756-EN2TP, 1756-EN2TPK
• Supports Parallel Redundancy Protocol (PRP).
• Performs the same functions as the 1756-EN2TR modules.
1756-EN3TR, 1756-EN3TRK • Extended Integrated Motion on EtherNet/IP network.
• Supports as many as 128 motion axes.
• Performs the same functions as the 1756-EN3TR modules.
1756-EN4TR, 1756-EN4TRK, • Supports as many as 256 motion axes.
1756-EN4TRXT • Supports a 1 Gbps communication rate.
• Helps to secure access to a control system from within the plant network.
• Directly connects the controller to an EtherNet/IP network without
requiring a bridge.
1756-ENBT, 1756-ENBTK • Communicates with distributed I/O modules and other EtherNet/IP
devices.
• Bridges messages over an EtherNet/IP network.
• Performs the same functions as a 1756-ENBT module with twice the
1756-EN2TSC capacity for more demanding applications.
• Helps to secure access to a control system from within the plant network.
• Performs the same functions as the 1756-ENBT modules.
• Provides remote access via an Internet browser to tags in a local
1756-EWEB, 1756-EWEBK ControlLogix controller.
This module does not provide support for I/O or produced/consumed tags.
This module does not support CIP Safety™.

Double Data Rate Backplane Communication

for ControlLogix Controllers
The controllers provide double data rate (DDR) capabilities across the ControlLogix backplane.

38 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 4 Communication Networks

ControlNet Network The ControlNet network is a real-time control network that provides high-speed transport of
time-critical I/O and interlocking data and messaging data. This includes the upload and
Communication download of program and configuration data on one physical-media link.
Applies to these controllers:
The ControlNet network is highly deterministic and repeatable and is unaffected when devices
ControlLogix 5580
are connected or disconnected from the network. This quality results in synchronized and
GuardLogix 5580 coordinated real-time performance.

The ControlNet network often functions as the following:

• A substitute/replacement for the remote I/O (RIO) network because the ControlNet
network adeptly handles large numbers of I/O points
• A backbone for multiple distributed DeviceNet networks
• A peer interlocking network

In the following example, these actions occur on the ControlNet network:

• The controllers produce and consume tags.
• The controllers initiate MSG instructions that do the following:
- Send and receive data.
- Configure devices.
• The workstation is used to do the following:
- Configure the ControlNet devices and the ControlNet network.
- Download and upload projects from the controllers.
Figure 12 - ControlNet Network

CompactLogix PowerFlex 700S

Distributed I/O

ControlNet Network

1794-ACN15
1794 I/O

PanelView
1734-ACNR
1734 I/O

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 39

Chapter 4 Communication Networks

GuardLogix Controllers in a ControlNet Network

ControlNet communication modules provide the following:
• Support for messaging, produced/consumed safety and standard tags, and distributed
standard I/O
• Support the use of coax and fiber repeaters for isolation and increased distance

This example illustrates the following:

• GuardLogix controllers can produce and consume standard or safety tags between each
other.
• GuardLogix controllers can initiate MSG instructions that send/receive standard data or
configure devices. GuardLogix controllers do not support MSG instructions for safety
data.
• The 1756-CN2 module can be used as a bridge, letting the GuardLogix controller produce
and consume standard and safety data to and from I/O devices.
Figure 13 - GuardLogix Controllers in a ControlNet Network
Compact GuardLogix Controller
with 1768-CNB Module
GuardLogix 5580 Controller
with 1756-CN2 Module Distributed I/O

PowerFlex 700S AC Drive

with DriveLogix Software

1756-DNB Module
1756-CN2 Module to DeviceNet Network
with 1756 I/O Modules with Safety I/O

ControlNet Network

GuardLogix 5580 Controller

with 1756-DNB Module

1794-ACN15 Adapter
with 1794 I/O
PanelView Terminal

to DeviceNet Network 1734-ACNR Adapter

PLC-5/40C Controller
with Safety I/O with 1734 I/O

The 1734-ACN adapter does not support POINT Guard I/O™ Safety modules.

40 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 4 Communication Networks

ControlNet Modules
This table lists the available ControlNet modules and their primary features.
Table 7 - ControlNet Modules
Module System Description
1756-CN2 ControlLogix • Performs the same functions as a 1756-CNB module.
1756-CN2K GuardLogix • Provides twice the capacity for more demanding applications.
• Performs the same functions as a 1756-CN2 module.
1756-CN2R ControlLogix • Supports redundant ControlNet media.
1756-CN2RK GuardLogix • 1756-CN2RXT operates in extreme environments with -25…+70 °C (-13…+158 °F)
1756-CN2RXT
temperatures.
• Controls I/O modules.
• Communicates with other ControlNet devices (messages).
1756-CNB ControlLogix • Shares data with other Logix 5000® series controllers (produce/consume).
1756-CNBK
• Bridges ControlNet links to route messages to devices on other networks.
• Standard connections only.
• Performs the same functions as a 1756-CNB module.
1756-CNBR ControlLogix • Supports redundant ControlNet media.
1756-CNBRK
• Standard connections only.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 41

Chapter 4 Communication Networks

DeviceNet Network The DeviceNet network uses the Common Industrial Protocol (CIP™) to provide the control,
configuration, and data collection capabilities for industrial devices. You can connect devices
Communication directly to plant-floor controllers without having to hard-wire each device into an I/O module.
Applies to these controllers:
In the following example, a ControlLogix controller is connected to the DeviceNet network and
ControlLogix 5580
devices via the 1788-EN2DNR linking device.
GuardLogix 5580
For more information about DeviceNet modules and devices, see DeviceNet Modules in
Logix 5000 Control Systems User Manual, publication DNET-UM004.
Figure 14 - DeviceNet Network
ControlLogix Controller

EtherNet/IP Network

FLEX I/O Modules 1788-EN2DNR

CompactLogix Controller

Sensor
Push Button Cluster
Motor
Starter

Barcode Scanner
I/O Devices
Indicator Lights
PowerFlex Drive

DeviceNet Bridge and Linking Devices

This table lists the available DeviceNet bridge and linking devices that can be used with the
DeviceNet network.

Table 8 - DeviceNet Communication Modules and Capabilities

Module System Description
ControlLogix • Controls I/O modules.
1756-DNB, 1756-DNBK GuardLogix • Communicates with other DeviceNet devices (via messages).
1788-EN2DNR ControlLogix Links an EtherNet/IP network to a DeviceNet network.
1788-CN2DN ControlLogix Links a ControlNet network to a DeviceNet network.

Connections Over DeviceNet Networks

A ControlLogix controller requires two connections for each 1756-DNB module:
• One connection for module status and configuration
• One rack-optimized connection for device data

42 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 4 Communication Networks

Data Highway Plus (DH+) For DH+™ network communication, you have two module options for use in the ControlLogix
chassis. This table lists the DH+ modules and capabilities.
Network Communication
Table 9 - DH+ Modules and Capabilities
Applies to these controllers:
RIO Module Description
ControlLogix 5580
• Function as a remote I/O (RIO) scanner.
• Support 32 logical rack connections or 16 block transfer connections per channel.
1756-DHRIO, • Establish connections between controllers and I/O adapters.
1756-DHRIOK
• Distribute control so that each controller has its own I/O.
• Use for standard communications only.
• Performs the same functions as a1756-DHRIO module.
1756-DHRIOXT • Operates in extreme environments with -25…+70 °C (-13…+158 °F) temperatures.
• Use for standard communications only.

For DH+ network communication, use a 1756-DHRIO or 1756-DHRIOXT module in the

ControlLogix chassis to exchange information between these controllers:
• PLC and SLC™ controllers
• ControlLogix controllers and PLC or SLC™ controllers
• ControlLogix controllers

You can connect a maximum of 32 stations to one DH+ link:

• Channel A supports 57.6 Kbps, 115.2 Kbps, and 230.4 Kbps.
• Channel B supports 57.6 Kbps and 115.2 Kbps.
Figure 15 - DH+ Network
Data Collection
Recipe Management

EtherNet/IP Network

ControLogix ControLogix
Chassis Chassis

DH+ Network DH+ Network

PLC-5 SLC 500 RSView PLC-5 SLC 500 RSView

Communicate Over a DH+ Network

For the controller to communicate to a workstation or other device over a DH+ network, use
Linx-based communication software to do the following:
• Specify a unique link ID for each ControlLogix backplane and additional network in the
communication path.
• Configure the routing table for the 1756-DHRIO or 1756-DHRIOXT module.

The 1756-DHRIO or 1756-DHRIOXT module can route a message through up to four

communication networks and three chassis. This limit applies only to the routing of a message
and not to the total number of networks or chassis in a system.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 43

Chapter 4 Communication Networks

Universal Remote I/O (RIO) For communication in a Universal RIO network, you have three module options for use in the
ControlLogix chassis. This table lists the RIO modules and capabilities.
Communication
Table 10 - RIO Modules and Capabilities
Applies to these controllers:
ControlLogix 5580 Module Description
• Functions as an RIO scanner and adapter.
1756-RIO • Supports connections to 32 racks in any combination of rack size or block transfers.
1756-RIOK • Updates data to the ControlLogix controller by using scheduled connections.
• Supports only standard communication.
• Functions as an RIO scanner.
• Supports 32 logical rack connections or 16 block transfer connections per channel.
1756-DHRIO • Establishes connections between controllers and I/O adapters.
1756-DHRIOK
• Distributes control so that each controller has its own I/O.
• Supports only standard communication.
• Performs the same functions as a 1756-DHRIO module.
1756-DHRIOXT • Operates in extreme environments with -25…+70 °C (-13…+158 °F) temperatures.
• Supports only standard communication.

When a channel on the 1756-DHRIO or 1756-DHRIOXT module is configured for Universal RIO
communication, the module acts as a scanner for the network. The controller communicates
to the module to send and receive the I/O data on the Universal RIO network.

The 1756-RIO module can act as a scanner or adapter on a Universal RIO network. The 1756-RIO
module transfers digital, block transfer, analog, and specialty data without message
instructions.
Figure 16 - Universal RIO Network
1756-L85E
1756-RIO

SAFETY ON

0000
NET

LINK
1771-ASB
RUNFORCESD OK

1746-ASB

PLC-5

1794-ASB

44 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 4 Communication Networks

Communicate Over a Universal RIO Network

For the controller to control I/O over a Universal RIO network, follow these steps.
1. Configure the remote I/O adapter.
2. Lay out the remote I/O network cable.
3. Connect the remote I/O network cable.
4. Configure the scanner channel.

As you design your Universal RIO network, remember the following:

• All devices that are connected to a Universal RIO network must communicate with the
same communication rate. Available rates include the following:
- 57.6 Kbps
- 115.2 Kbps
- 230.4 Kbps
• You must assign unique partial and full racks to each channel used in Remote I/O
Scanner mode. Both channels of a 1756-DHRIO or 1756-DHRIOXT module cannot scan the
same partial or full rack address. Both module channels can communicate to 00…37
octal or 40…77 octal, but each channel can communicate only with one address at a
time in whichever of these two ranges it falls.

FOUNDATION Fieldbus FOUNDATION Fieldbus is an open interoperable fieldbus that is designed for process control
instrumentation. The devices in the following table can be connected to a ControlLogix
Communication controller via another network.
Applies to these controllers: Table 11 - FOUNDATION Fieldbus Devices and Capabilities
ControlLogix 5580
Device Description
• Bridge an EtherNet/IP network to FOUNDATION Fieldbus.
• Connect via a low-speed serial (H1) and high-speed Ethernet network (HSE).
1788-EN2FFR
• Access devices directly via an OPC server.
• Use for standard communications only.
• Connect via low-speed serial (H1) connections.
• Bridge a ControlNet network to a FOUNDATION Fieldbus.
1788-CN2FFR
• Support redundant ControlNet media.
• Use for standard communications only.

The fieldbus executes control in the device. The linking device does the following:
• Bridges from an EtherNet/IP network to an H1 connection
• Accepts HSE or EtherNet/IP messages and converts them to the H1 protocol
Figure 17 - FOUNDATION Fieldbus Network
1756-L85E

RSFieldbus Software

1788-EN2FFR 24V DC
Linking Device Power Supply

Power
Conditioner

Field Device
Field Device

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 45

Chapter 4 Communication Networks

HART Communication HART (Highway Addressable Remote Transducer) is an open protocol that is designed for
process control instrumentation.
Applies to these controllers:
ControlLogix 5580 Device Description
• Acts as HART master to allow communication with HART field devices.
1756 analog HART I/O modules: • Interfaces directly with field devices (through built-in HART modems),
1756-IF8H, 1756-IF8HK which mitigates the need for external hardware and more wiring.
1756-IF8IH • Provides access to more field device data, including voltage and current
1756-IF16H, 1756-IF16HK measurements.
1756-IF16IH • Directly connects asset management software to HART devices.
1756-OF8H, 1756-OF8HK • Supports differential wiring for environments where improved noise
1756-OF8IH immunity is needed (input modules).
• Supports only standard communication.
• Acquires data or control applications with slow update requirements, such
as a tank farm.
ProSoft interface • Does not require external hardware to access the HART signal.
MVI56-HART
• Does not provide a direct connection to asset management software.
• Supports only standard communication.

The HART protocol combines digital signals with analog signals to ready the digital signal for
the Process Variable (PV). The HART protocol also provides diagnostic data from the
transmitter.
Figure 18 - HART Protocol

1756-L85E
1756-IF8H or 1756-OF8H

HART Field Devices

46 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 5
Start to Use the Controller
Create a Logix Designer Create a controller project by using the Studio 5000 Logix Designer® application.
Application Project 1. Create a project and select the controller.
2. Define the properties of the controller:
Applies to these controllers:
ControlLogix® 5580
- Choose the major revision of firmware for the controller.
GuardLogix® 5580 - Choose the chassis size.
- Choose the slot for the controller.
- Choose a security authority option.
- Enter a description of the project.
3. Click Finish.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 47

Chapter 5 Start to Use the Controller

Configuration for a GuardLogix® controllers require additional configuration after you create the project. These
topics describe how to configure your controller.
GuardLogix Controller
Applies to these controllers: For a GuardLogix controller, the Logix Designer application creates a safety task and a safety
program. A main Ladder Diagram safety routine that is called MainRoutine is also created
GuardLogix 5580
within the safety program.

A red bar under the icon distinguishes safety programs and routines from standard project
components in the Controller Organizer.
Figure 19 - Safety Components

Set the Safety Level for a GuardLogix Controller

The safety level declares to the Logix Designer application the intent of the safety application.
The safety level indicates whether the project is at safety level SIL 2/PLd or SIL 3/PLe.
• The safety level that is required for an application is based on a required risk
assessment that you must perform.
• The safety level that is achieved is determined by conformance to Safety Integrity Level
(SIL) and Performance Level (PL) requirements and safety application requirements.

See the GuardLogix 5580 and Compact GuardLogix 5380 Safety Reference Manual, publication
1756-RM012.
You must specify the safety level:
• The default setting is SIL 2/PLd.
• You can only modify the setting offline, when the safety application is in the Unlocked
state and no safety signature exists.
• For SIL 3/PLe, you must have a 1756-L8SP safety partner that is installed to the right of
the primary controller.
• If you select SIL 3/PLe, a safety partner appears in the Controller Organizer I/O tree. If
you change the value back to SIL 2/PLd, the safety partner disappears from the I/O tree.

48 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 5 Start to Use the Controller

Perform these steps to set the safety level:

1. On the Online toolbar, click the Controller Properties icon.
2. On the Controller Properties dialog box, click the Safety tab.
3. On the Safety tab, select the Safety Level.
4. Click Apply and then OK.
Figure 20 - Safety Level

Passwords for Safety-locking and Unlocking

Safety-locking the controller helps to protect safety control components from modification.
Only safety components, such as the safety task, safety programs, safety routines, safety tags,
and safety signature are affected. Standard components are unaffected. You can safety-lock
or -unlock the controller project when online or offline.

The safety-lock and -unlock feature uses two separate passwords. Passwords are optional.

IMPORTANT Rockwell Automation does not provide any form of password or security
override services. When products and passwords are configured,
Rockwell Automation encourages customers to follow good security
practices and to plan accordingly for password management.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 49

Chapter 5 Start to Use the Controller

Protect the Safety Signature in Run Mode

You can help prevent the safety signature from being deleted while the controller is in Remote
Run mode, regardless of whether the safety application is locked or unlocked.

IMPORTANT You must complete these steps before you create a safety signature or
safety-lock the controller. Once a safety signature exists, or the
application is safety-locked, the Protect Signature in Run Mode checkbox
is not editable.

Follow these steps to protect the safety signature:

1. Open the Controller Properties dialog box.
2. Click the Safety tab.
3. Check Protect Signature in Run Mode and then click OK.
Figure 21 - Protect Signature

50 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 5 Start to Use the Controller

Assign the Safety Network Number (SNN)

When you create controller projects, the Studio 5000 Logix Designer application generates an
SNN value automatically whenever it recognizes a new subnet that contains CIP Safety™
devices:
• Each CIP Safety™-capable port on the controller is assigned an SNN. The GuardLogix
5580 controllers have two safety network numbers: one for the EtherNet/IP™ port, and
one for the backplane.
• If a bridge or adapter device is in the I/O tree and a child CIP Safety device is added, the
subnet that is created by the bridge or adapter is assigned an SNN.

For typical users, the automatic assignment of a time-based SNN is sufficient. However,
manual assignment of the SNN is required if the following is true:
• One or more controller ports are on a CIP Safety subnet that already has an established
SNN.
• A safety project is copied to another hardware installation within the same routable CIP
Safety system.

Rockwell Automation recommends changing each SNN to the SNN already established for that
subnet, if one exists. That way, devices created later in the project are automatically assigned
the correct SNN.

For information regarding whether the controller or Ethernet ports are being added to existing
subnets, see the GuardLogix 5580 and Compact GuardLogix 5380 Safety Reference Manual,
publication 1756-RM012.

Each safety network must have a unique safety network number. You must be sure that a
unique SNN is assigned to each CIP Safety network that contains safety devices.
Multiple safety network numbers can be assigned to a CIP Safety subnet or a
ControlBus™ chassis that contains multiple safety devices. However, for
simplicity, we recommend that each CIP Safety subnet has only one unique SNN.

The SNN can be software-assigned (time-based) or user-assigned (manual).

Automatic Assignment of Time-based SNN

When a new controller or device is created, a time-based SNN is automatically assigned.

• Devices that are created directly under the controller port default to having the same
SNN as that port on the controller.
• For devices not directly under a controller port, subsequent new safety device additions
to the same CIP Safety network are assigned the same SNN defined within the lowest
address on that CIP Safety network.

The time-based format sets the SNN value as the date and time when the number was
generated, according to the computer running the configuration software.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 51

Chapter 5 Start to Use the Controller

Figure 22 - Time-based Format

Manual Assignment of SNN

Manual assignment is useful if you lay out your network and put the SNNs on your network
diagram. It may be easier to read SNNs from a diagram than it is to copy and paste them from
multiple projects.

Manual assignment of the SNN is required if the following is true:

• One or more controller ports are on a CIP Safety subnet that already has an established
SNN.
• A safety project is copied to another hardware installation within the same routable
CIP Safety system.

IMPORTANT If you assign an SNN automatically or manually, make sure that system expansion does not result in a duplication of
SNN and unique node reference combinations.
A warning appears if your project contains duplicate SNN and unique node reference combinations. You can still verify
the project, but Rockwell Automation recommends that you resolve the duplicate combinations.
However, there can be safety devices on the routable safety network that have the same SNN and node address and
are not in the project. In this case, these safety devices are unknown to the Logix Designer application, and you will not
see a warning.
If two different devices have the same node references, the safety system cannot detect a packet received by one
device that was intended for the other device.
If there are duplicate unique node references, as the system user, you are responsible for proving that an unsafe
condition cannot result.

52 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 5 Start to Use the Controller

Follow these steps to change the controller SNNs to a manual assignment:

1. On the Online toolbar, click the Controller Properties icon.
2. On the Controller Properties dialog box, click the Safety tab.
3. On the Safety tab, click to the right of the safety network number for the port that
you want to change.

4. On the Safety Network Number dialog box, select Manual.

5. Enter the SNN as a value from 1…9999 (decimal) and then click OK.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 53

Chapter 5 Start to Use the Controller

Copy and Paste a Safety Controller Safety Network Number

If you must apply a Safety Network Number (SNN) to other safety controllers, you can copy and
paste the SNN.
Copy a Safety Controller SNN
1. On the Online toolbar, click the Controller Properties icon .
2. On the Controller Properties dialog box, click the Safety tab.
3. On the Safety tab, click to the right of the safety network number.

4. On the Safety Network Number dialog box, click Copy and then OK.

5. On the Controller Properties dialog box, click OK.

54 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 5 Start to Use the Controller

Paste a Safety Controller SNN

1. On the Online toolbar, click the Controller Properties icon .
2. On the Controller Properties dialog box, click the Safety tab.
3. On the Safety tab, click to the right of the safety network number.

4. On the Safety Network Number dialog box, click Paste and then OK.

5. On the Controller Properties dialog box, click OK.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 55

Chapter 5 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.
Applies to these controllers:
ControlLogix 5580 Use RSWho
GuardLogix 5580
1. Open or create a Logix Designer application project.
2. In the application, click RSWho.

3. Expand the communication path and select the controller.

4. To store the path in the project file, click Set Project Path.
If you store the project path in the project, then you do not have to choose the path
each time you go online.
5. After choosing the communication path, click Go Online in the Who Active dialog box.
Go Online uses the highlighted node in the Who Active tree, regardless of the setting for
Path in Project.

56 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 5 Start to Use the Controller

Use a Recent Communication Path

You can also select a recent communications path and go online or apply it to your project.
1. In the application, click the arrow that is on the Path bar.

2. On the Select Recent Communications Path dialog box, choose the path.

3. To store the path in your project, click Set Project Path.

4. Click Go Online.

Once you establish a communication path, you can choose Go Online from the Controller Status
menu.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 57

Chapter 5 Start to Use the Controller

Considerations for Going The Logix Designer application determines whether you can go online with a target controller
based on whether the offline project is new or whether changes occurred in the offline project.
Online with a GuardLogix If the project is new, you must first download the project to the controller. If changes occurred
Controller to the project, you are prompted to upload or download. If no changes occurred, you can go
online to monitor the execution of the project.
Applies to these controllers:
GuardLogix 5580 A number of factors affect these processes, including Project to Controller Match feature, the
safety status and faults, the existence of a safety signature, the safety-lock/-unlock status of
the project and the controller, and the configured safety level disagreeing with the presence or
absence of a partner in the chassis.

Match Project to Controller

The Match Project to Controller feature affects the download, upload, and go online processes
of standard and safety projects. This feature is on the Advanced tab of the Controller
Properties dialog box.
Figure 23 - Match Project to Controller

If the Match Project to Controller feature is enabled in the offline project, the Logix Designer
application compares the serial number of the controller in the offline project to that of the
connected controller. If they do not match, you must cancel the download/upload, connect to
the correct controller, or confirm that you are connected to the correct controller that updates
the serial number in the project to match the target controller.

58 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 5 Start to Use the Controller

Firmware Revision Matching

Firmware revision matching affects the download process. If the revision of the controller
does not match the revision of the project, you are prompted to update the firmware of the
controller. The Logix Designer application lets you update the firmware as part of the
download sequence.

IMPORTANT To update the firmware of the controller, first install a firmware

update kit. An upgrade kit ships on a supplemental DVD along with
the Studio 5000® environment.

You can also upgrade the firmware by choosing ControlFLASH Plus™ or

ControlFLASH™ from the Tools menu in the Logix Designer application.
Safety Status/Faults
Uploading program logic and going online is allowed regardless of safety status. Safety status
and faults only affect the download process.

You can view the safety status via the Safety tab on the Controller Properties dialog box.

Safety Signature and Safety-locked and -unlocked Status

The existence of a safety signature and the safety-locked or -unlocked status of the controller
affect both the upload and download processes.
The safety signature and the safety-lock status are uploaded with the project. For example, if
the project in the controller was safety-unlocked, the offline project remains safety-unlocked
following the upload, even if it was locked before the upload.

Following an upload, the safety signature in the offline project matches the controller’s safety
signature.

The safety-lock status always uploads with the project, even when there is no safety
signature.

The existence of a safety signature, and the controller’s safety-lock status determines
whether a download can proceed.
Table 12 - Effect of Safety-lock and Safety Signature on Download Functionality
Controller Status Safety Signature Status Download Functionality
• All standard project components download.
Safety signature in the offline project matches
the safety signature in the controller. • Safety-lock status matches the status in the offline project. The safety signature does
not change.
Safety-unlocked
• If the controller had a safety signature, it is automatically deleted, and the entire project
Safety signatures do not match. is downloaded.
• Safety-lock status matches the status in the offline project.
• If the offline project and the controller are safety-locked, all standard project
components are downloaded.
Safety signatures match.
• If the offline project is not safety-locked, but the controller is, the download is blocked
and you must first unlock the controller to allow the download to proceed.
Safety-locked
• You must first safety-unlock the controller to allow the download to proceed.
• If the controller had a safety signature, it is automatically deleted, and the entire project
Safety signatures do not match. is downloaded.
• Safety-lock status matches the status in the offline project.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 59

Chapter 5 Start to Use the Controller

Checks for Going Online with a GuardLogix Controller

For a safety project, the Logix Designer application checks for the following:
• If Match Project to Controller is selected, do the offline project and controller serial
numbers match?
• Does the offline project contain changes that are not in the controller project?
• Do the revisions of the offline project and controller firmware match?
• Are either the offline project or the controller safety-locked?
• Do the offline project and the controller have compatible safety signatures?
Table 13 - Connect to the Controller with a Safety Project
Software Message Action
Connect to the correct controller, select another project file, or choose the Update
Unable to connect to controller. Mismatch between the offline project and the project serial number checkbox and choose Go Online… to connect to the controller
controller serial number. Selected controller may be the wrong controller. and update the offline project serial number to match the controller.
Choose one of the following options:
• Choose Update Firmware. Choose the required revision and click Update. Click Yes
to confirm your selection.
Unable to connect to controller. The revision of the offline project and the IMPORTANT: The online project is deleted.
controller’s firmware are not compatible.
• To preserve the online project, cancel the online process and install a version of
the Studio 5000® environment that is compatible with the firmware revision of
your controller.
Choose one of the following options:
• Upload to update the offline project.
You need to upload or download to go online by using the open project.
• Download to update the controller project.
• Choose File to select another offline project.
• To preserve the safety signature when the firmware minor revision is
incompatible, update the firmware revision in the controller to exactly match the
Unable to connect in a manner that preserves safety signature. The firmware minor offline project. Then go online to the controller.
revision on the controller is not compatible with safety signature in offline project. • To proceed with the download despite the safety signature incompatibility, click
Download. The safety signature is deleted.
IMPORTANT: The safety system requires revalidation.
Unable to connect to controller. Incompatible safety signature cannot be deleted Cancel the online process. You must safety-unlock the offline project before
while project is safety-locked. attempting to go online.

When the controller and the Logix Designer application are online, the safety-locked status
and safety signature of the controller match the controller’s project. The safety-lock status
and safety signature of the offline project are overwritten by the controller. If you do not want
the changes to the offline project to be permanent, do not save the project file following the go
online process.

60 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 5 Start to Use the Controller

Download to the Controller When you download a project to the controller, it copies the project from the Logix Designer
application onto the controller.
Applies to these controllers:
ControlLogix 5580 Use Who Active
GuardLogix 5580
You can use the features of the Who Active dialog box to download to your controller after you
have set the communication path. Complete these steps to download to the controller.
1. After you set the communication path, click Download on the Who Active dialog box.

2. After reading the warnings in the Download dialog box, click Download.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 61

Chapter 5 Start to Use the Controller

Use the Controller Status Menu

After you select 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. After the download completes, the project
name appears on the scrolling status display.
Figure 24 - Download via the Controller Status Menu

Considerations for For a safety project, the Logix Designer application compares the following information in the
offline project and the controller:
Download to a GuardLogix
• Controller serial number (if Match Project to Controller is selected)
Controller • Firmware major and minor revisions
Applies to these controllers: • Safety status
GuardLogix 5580 • Safety signature (if one exists)
• Safety-lock status
• Safety partner (if one exists)
The Logix Designer application does not allow the download of a project configured for
SIL 2 if a safety partner is to the right of the primary controller.

After the checks all pass, a download confirmation dialog appears. Click Download.

62 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 5 Start to Use the Controller

The Logix Designer application displays status messages in the download dialog, progress
screen, and the Errors window.
Software Message Action
Unable to download to the controller. Mismatch between the offline project Connect to the correct controller or verify that this is the correct controller. If it is the correct
and the controller serial number. Selected controller may be the wrong controller, check the Update project serial number checkbox to allow the download to
controller. proceed. The project serial number is modified to match the controller serial number.
Unable to download to the controller. The major revision of the offline Choose Update Firmware. Choose the required revision and click Update. Click Yes to
project and the controller’s firmware are not compatible. confirm your selection.
Unable to download a SIL 2 application, Safety Partner is Present. Remove the safety partner.
Unable to download to controller. The safety partner is missing or Cancel the download process. Install a compatible safety partner before attempting to
unavailable. download.
Unable to download to controller. The firmware revision of the safety Update the firmware revision of the safety partner. Choose Update Firmware. Choose the
partner is not compatible with the primary controller. required revision and click Update. Click Yes to confirm your selection.
Unable to download to controller. Safety partnership has not been Cancel this download process and attempt a new download.
established.
Cancel the download. To download the project, you must safety-unlock the offline project,
Unable to download to controller. Incompatible safety signature cannot be delete the safety signature, and download the project.
deleted while the project is safety-locked. IMPORTANT: The safety system requires revalidation.
• If the firmware minor revision is incompatible, to preserve the safety signature, update the
firmware revision in the controller to exactly match the offline project. Then download the
Cannot download in a manner that preserves the safety signature. offline project.
Controller’s firmware minor revision is not compatible with safety signature
in offline project. • To proceed with the download despite the safety signature incompatibility, click
Download. The safety signature is deleted.
IMPORTANT: The safety system requires revalidation.
Unable to download to controller. Controller is locked. Controller and offline Choose Unlock. The Safety Unlock for Download dialog box appears. If the Delete Signature
project safety signatures do not match. checkbox is selected and you choose Unlock, click Yes to confirm the deletion.
Downloading safety signature... The safety signature is present in the offline project and is downloading.

Following a successful download, the safety-locked status and safety signature of the
controller match the project that was downloaded. Safety data is initialized to the values that
existed when the safety signature was created.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 63

Chapter 5 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.
Applies to these controllers:
ControlLogix 5580 Use Who Active
GuardLogix 5580
You can use the features of the Who Active dialog box to upload from your controller after you
have set the communication path. Complete these steps to upload from the controller.
1. After choosing the communication path, click Upload on the Who Active dialog box.

2. On the Connected to Upload dialog box, verify the project to upload and click Upload.

64 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 5 Start to Use the Controller

Use the Controller Status Menu

After you have chosen a communication path in the Logix Designer application, you can use
the Controller Status menu to upload from the controller.
1. From the Controller Status menu, choose Upload.
Figure 25 - Upload via the Controller Status Menu

2. On the Connected to Upload dialog box, verify the project to upload and click Upload.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 65

Chapter 5 Start to Use the Controller

Considerations for Upload For a safety project, the Logix Designer application compares the following information in the
project and the controller:
from a GuardLogix
• Controller serial number (if project to controller match is selected)
Controller • Open project to the controller project
Applies to these controllers: • Firmware major and minor revisions
GuardLogix 5580 • Safety signature (if one exists)

IMPORTANT An upload is allowed regardless of the Safety status and the safety-
locked state of the offline project and controller. The locked status
follows the state of the uploaded project.

Upload Behavior Response

• Connect to the correct controller or verify that this is the
correct controller.
If the project to controller match is enabled, the • Select a new project to upload into or select another
Logix Designer application checks whether the project by choosing Select File.
serial number of the open project and the serial • If it is the correct controller, select the Update project
number of the controller match. serial number checkbox to allow the download to proceed.
The project serial number is modified to match the
controller serial number.
• If the projects do not match, you must select a matching
The Logix Designer application checks whether file or cancel the upload process.
the open project matches the controller project. • If the projects match, the software checks for changes in
the offline (open) project.
• If there are no changes in the offline project, you can go
online without uploading. Click Go Online.
The Logix Designer application checks for changes
in the offline project. • If there are changes in the open project that are not
present in the controller, you can choose to upload the
project, cancel the upload, or select another file.
This message appears during the upload only if a safety
Uploading safety signature... signature matching the one in the controller does not exist in
the offline project.

If you choose Upload, the standard and safety applications are uploaded. If a safety
signature exists, it is also uploaded. The safety-lock status of the project reflects the
original status of the online (controller) project.
Before the upload, if an offline safety signature exists, or the offline project is
safety-locked but the controller is safety-unlocked or has no safety signature, the
offline safety signature and safety-locked state are replaced by the online values
(safety-unlocked with no safety signature). If you do not want to make these
changes permanent, do not save the offline project following the upload.

66 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 5 Start to Use the Controller

Controller Operation Modes The controller has the following operation modes:
Applies to these controllers:
• Run
ControlLogix 5580 • Remote Run
GuardLogix 5580 • Remote Program
• Remote Test
• Program

Run Mode
In Run mode, the controller is actively controlling the process or machine. Projects cannot be
edited in the Logix Designer application when in Run mode.

ATTENTION: Only use Run mode when all conditions are safe.

The controller can perform these functions in Run mode:

• Turn outputs to the state commanded by the logic of the project
• Execute (scan) tasks
• Send messages
• Send and receive data in response to a message from another controller
• Produce and consume tags

The controller cannot perform these functions in Run mode:

• Turn outputs to their configured state for Program mode
• Change the mode of the controller via the Logix Designer application
• Download a project
• Schedule a ControlNet® network
• While online, edit the project

Remote Run Mode

Remote Run mode is identical to Run mode except you can edit the project online, and change
the controller mode through the Logix Designer application.

ATTENTION: You are able to modify a project file online in Remote Run mode.
Be sure to control outputs with care to avoid injury to personnel and damage
to equipment.

The controller can perform these functions in Remote Run mode:

• Turn outputs to the state commanded by the logic of the project
• Execute (scan) tasks
• Change the mode of the controller via the Logix Designer application
• While online, edit the project
• Send messages
• Send and receive data in response to a message from another controller
• Produce and consume tags

The controller cannot perform these functions in Remote Run mode:

• Turn outputs to their configured state for Program mode
• Download a project
• Schedule a ControlNet® network

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 67

Chapter 5 Start to Use the Controller

Remote Program Mode

Remote Program mode functions like Program mode, except you can change the controller
mode through the Logix Designer application.

ATTENTION: Outputs are commanded to their Program mode state, which can
cause a dangerous situation.

The controller can perform these functions in Remote Program mode:

• Turn outputs to their configured state for Program mode
• Change the mode of the controller via the Logix Designer application
• Download a project
• Schedule a ControlNet network
• While online, edit the project
• Send and receive data in response to a message from another controller
• Produce and consume tags

The controller cannot perform these functions in Remote Program mode:

• Turn outputs to the state commanded by the logic of the project
• Execute (scan) tasks

Remote Test Mode

Remote Test 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.

ATTENTION: Outputs are commanded to their Program mode state, which can
cause a dangerous situation.

The controller can perform these functions in Remote Test mode:

• Turn outputs to their configured state for Program mode
• Execute (scan) tasks
• Change the mode of the controller via the Logix Designer application
• While online, edit the project
• Send messages
• Send and receive data in response to a message from another controller
• Produce and consume tags

The controller cannot perform these functions in Remote Test mode:

• Turn outputs to the state commanded by the logic of the project.
• Download a project
• Schedule a ControlNet network
• Send messages

68 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 5 Start to Use the Controller

Program Mode
Program mode does not execute code or control I/O, but editing is available. Controller modes
cannot be changed through the Logix Designer application.

ATTENTION: Do not use Program mode as an emergency stop (E-stop).

Program mode is not a safety device.
Outputs are commanded to their Program mode state, which can cause a
dangerous situation.
The controller can perform these functions in Program mode:
• Turn outputs to their configured state for Program mode
• Download a project
• Schedule a ControlNet network
• While online, edit the project
• Send and receive data in response to a message from another controller
• Produce and consume tags

The controller cannot perform these functions in Program mode:

• Turn outputs to the state commanded by the logic of the project
• Execute (scan) tasks
• Change the mode of the controller via the Logix Designer application
• Send messages

Use the Keyswitch to Change the Operation Mode

You can use the keyswitch on the front of the controller to change the operation mode.
Figure 26 - Controller Keyswitch

To change the operation mode, you must physically change the position of the keyswitch to
correspond with the desired operation mode, as described in the following table.
Table 14 - Controller Keyswitch Positions and Operation Modes
Keyswitch Position Operation Mode
RUN Run mode
• Remote Run mode
REM • Remote Program mode
• Remote Test mode
PROG Program mode

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 69

Chapter 5 Start to Use the Controller

When the keyswitch is in the REM position, there are three possible modes:
• To activate Remote Run mode, move the keyswitch from RUN to REM.
• To activate Remote Program mode, move the keyswitch from PROG to REM.
• To activate Remote Test mode, use the Logix Designer application along with the REM
keyswitch position.

The keyswitch provides a mechanical means to enhance controller and control system
security. The physical keyswitch 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 keyswitch
in RUN mode and remove the key from the switch. By removing the key,
you discourage unauthorized access to the controller or potential
tampering with the program of the controller, configuration, or firmware.
Place the keyswitch in REM or PROG mode during controller
commissioning and maintenance and whenever access is needed to
change the program, configuration, or firmware.

Use the Logix Designer Application to Change the Operation Mode

When you are online with the controller, and the keyswitch position is set to REM, then you can
use the Logix Designer application to change the operation mode.

The Controller Status menu lets you specify these operation modes:
• Remote Program
• Remote Run
• Remote Test
Figure 27 - Operation Modes in Logix Designer

70 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 5 Start to Use the Controller

Reset Button You can reset the controllers or the safety partner with the reset button. The reset button is
only read during a power-up or restart. If you press the reset button at another time, it has no
Applies to these controllers: effect.
ControlLogix 5580
GuardLogix 5580 For a safety controller, the Safety Locked status or safety signature does not prevent you from
performing a controller reset. Because the application is cleared from the controller during a
reset, the safety level of the controller is cleared also. When you download a safety project to
the controller, the safety level is set to the level specified in the project.

A controller has two stages of reset:

• A Stage 1 reset clears the application program and memory, but retains the IP address
and all network settings. A stage 1 reset occurs only if the controller contains a user
application.
• A Stage 2 reset returns the controller to factory settings, including firmware, and clears
all network settings. 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 version.

The Safety Partner reset returns the safety partner to out-of-box settings, including firmware.

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

program, the controller 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.

Figure 28 - Controller Reset Button

Reset Button

Figure 29 - Safety Partner Reset Button

OK

Reset Button

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 71

Chapter 5 Start to Use the Controller

Stage 1 Reset
The stage 1 reset does the following:
• Clears the application program.
• Retains the network settings for the embedded Ethernet port.
• Retains APR (motion position) information.
• Retains non-volatile configuration parameters for PTP (Precision Time Protocol)/CIP
Sync time synchronization.
• Resets WallClockTime to default parameters.
• Resets the controller to begin the controller startup process.
• Helps to prevent the controller from loading firmware or software from the SD card on
first start up after the reset, regardless of the setting on the SD card and without
modifying the SD card contents (the write-protect setting is irrelevant). An SD card will
reload on subsequent powerup situations.
• Enables the Ethernet port, if it was previously disabled.

To perform a Stage 1 reset, complete these steps. This process assumes that an SD card is
installed in the controller.
1. Power down the controller.
2. Remove the key from the keyswitch.
3. Open the front door on the controller.
4. Use a small tool with a diameter of a paper clip, to press and hold the reset button. The
button is recessed behind the panel.
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 CLR, 4, 3,
2, 1, Project Cleared.
7. 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
these ways:
• Download the project from the Logix Designer application.
• 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.

72 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 5 Start to Use the Controller

Stage 2 Reset
The stage 2 reset does the following:
• Returns the module to revision 1.x firmware (the out-of-box firmware revision).
• Clears all user settings to the out-of-box values including network and time
synchronization settings.
• Resets the controller to begin the controller start-up process.
• There will be no entries in the controller log after a Stage 2 reset, but saved logs on the
SD card remain.

Follow these steps to perform a Stage 2 reset.

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

After a Stage 2 reset is performed, you must complete these tasks to use the controller again:
• Configure the Ethernet ports, set the desired EtherNet/IP mode, and set the controller IP
address configuration.
• Update the firmware revision.
• Download a Logix Designer application project to the controller in one of these ways:
- Download the project from the Logix Designer application.
- 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.

Safety Partner Reset

Follow these steps to perform a safety partner reset.
1. Power down the safety partner.
2. Use a small tool with a diameter of a paper clip to press and hold the reset button. This
button is recessed 5 mm (0.19 in.) behind the panel.
3. While holding in the reset button, power up the safety partner.
4. Continue to hold the reset button while the 4-character display cycles through DFLT, 4,
3, 2, 1, Factory Default.
5. After Factory Default appears, release the reset button.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 73

Chapter 5 Start to Use the Controller

Notes:

74 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 6
Use the Secure Digital Card
The controllers ship with a 2 GB Secure Digital (SD) card, catalog number 1784-SD2, installed.
Applies to these controllers:
We recommend that you leave the SD card installed, so if a fault occurs, diagnostic data is
automatically written to the card. Rockwell Automation can then use the data to help
ControlLogix® 5580 investigate the cause of the fault.
GuardLogix® 5580
We recommend that you use the SD cards available from Rockwell Automation:
• Catalog numbers 1784-SD1, 1784-SD2, 1784-SDHC8, and 1785-SDHC32
• CodeMeter CmCard SD, 4 GB, catalog number 9509-CMSDCD4 (when license-based
source protection and execution protection features are enabled)
While other SD cards can be used with the controller, Rockwell Automation has not tested the
use of those cards with the controller and you could experience data corruption or 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.

The memory card that is compatible with your ControlLogix® controller is used to load or store
the contents of user memory for the controller.

When you use the Store feature, the project that is stored on the SD card matches the project
in the controller memory at that time. Changes that you make after you store the project are
not reflected in the project on the SD card.

If you change the project in the controller memory but do not store those changes, the next
time that you load the project from the SD card to the controller, you overwrite the changes.

IMPORTANT Do not remove the SD card while the controller is reading from, or writing
to, the card. If you remove the card during either activity, the data on the
card or controller can become corrupt.
Additionally, the controller firmware at the time when the card is
removed can become corrupted. Leave the card in the controller until
the OK status indicator turns steady green.

If an SD card is installed, you can see the contents of the card on the Nonvolatile Memory tab
of the Controller Properties dialog box. If a safety application is stored on the card, the safety-
lock status and the safety signature are shown.

The project must be online to see the contents of the SD card.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 75

Chapter 6 Use the Secure Digital Card

Considerations for Storing Only GuardLogix® 5580 controllers support safety projects. ControlLogix 5580 controllers do
not support safety projects.
and Loading a Safety Project
Applies to these controllers: You cannot store a safety project if the safety task status is Safety Task Inoperable. When you
store a safety project, the controller firmware is also stored to the SD card.
GuardLogix 5580
If no application project exists in the controller, you can save only the firmware of the safety
controller if a valid partnership exists. A firmware-only load does not clear a Safety Task
Inoperable condition.

If a safety signature exists when you store a project, the following occurs:
• Both safety and standard tags are stored with their current values.
• The current safety signature is saved.

When you store a safety application project on an SD card, Rockwell Automation recommends
you select Program (Remote Only) as the Load mode, that is, the mode that the controller
enters after a project is loaded from the SD card.

IMPORTANT To help prevent the firmware that is stored on the SD card from
overwriting newly-updated firmware:
• The update process first checks the load option on the SD card, and
changes the load option to User Initiated if necessary.
• The firmware update proceeds.
• The controller resets.
• The load option remains set to User Initiated.
If the SD card is locked, the load option does not change, and the
firmware that is stored on the SD card can overwrite the newly-updated
firmware.

76 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 6 Use the Secure Digital Card

Store to the SD Card We recommend that you back up your Logix Designer project to an SD card regularly. If a major
nonrecoverable fault occurs that removes the program from the controller memory, the
Applies to these controllers: backup copy on the SD card can be automatically restored to the controller to resume normal
ControlLogix 5580 controller operation.
GuardLogix 5580
To store a project to the SD card, complete these steps.
1. Make sure that the controller is online in Program mode or Remote Program mode.
2. In the Controller Organizer, double-click the controller to open the Controller Properties
dialog box.
3. On the Nonvolatile Memory tab, click Load/Store.

If Load/Store is dimmed, verify the following:

- The controller is in Program mode or Remote Program mode
- You 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.

4. In the Load Image field, select a setting according to your application requirements
described in the following table.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 77

Chapter 6 Use the Secure Digital Card

Table 15 - Choose a Load Image Setting

Application Load Image Description Safety Consideration
Requirement Setting
• During a power cycle, you lose any online changes,
tag values, and network schedule that you have not
stored in the nonvolatile memory.
Load image when • The controller loads the stored project and For a safety application, On Power Up loads whether the controller is
you turn on or On Power Up firmware at every powerup regardless of the safety-locked or there is a safety signature.
cycle power firmware or application project on the controller.
• You can always use the Studio 5000 Logix
Designer® application to load the project.
• If the project has been cleared from memory, this
option loads the project back into the controller on
Load image when powerup.
there is no project • The controller updates the firmware on the
in the controller On Uninitialized controller, if necessary. The application project The controller also updates the firmware on the safety partner, if
and you turn on or Memory that is stored in nonvolatile memory is also loaded necessary.
cycle chassis and the controller enters the selected mode, either
power Program or Run.
• You can always use the Logix Designer application
to load the project.
• You can initiate a load, regardless of the Safety Task status.
• You can load a project to a safety-locked controller only when the
safety signature of the project that is stored in nonvolatile memory
matches the project on the controller.
• If the signatures do not match or the controller is safety-locked without
Load image only If the controller type and the major and minor a safety signature, you are prompted to first unlock the controller.
through the Logix User Initiated revisions of the project in nonvolatile memory match IMPORTANT: When you unlock the controller and initiate a load from
Designer the controller type and major and minor revisions of nonvolatile memory, the safety-lock status, passwords, and safety
application the controller, you can initiate a load. signature are set to the values contained in nonvolatile memory once
the load is complete.
• If the firmware on the primary controller matches the revision in
nonvolatile memory, the safety partner firmware is updated, if
necessary, the application that is stored in nonvolatile memory is
loaded so that the Safety Task status becomes Safety Task Operable
and the controller enters the Program mode.

IMPORTANT To help prevent the firmware that is stored on the SD card from
overwriting newly updated firmware:
• The update process first checks the load option on the SD card, and
changes the load option to User Initiated if necessary.
• The firmware update proceeds.
• The controller resets.
• The load option remains set to User Initiated.
If the SD card is locked, the load option does not change, and the
firmware that is stored on the SD card can overwrite the newly updated
firmware.
5. In the Load Mode field, choose the mode that you want the controller to go to after
loading:
- Program (Remote Only)
- Run (Remote Only)

IMPORTANT Safety Consideration

Rockwell Automation recommends that you use Program (Remote Only),
when you set the Load Mode for a safety application project.

78 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 6 Use the Secure Digital Card

6. According to your application requirements, set the Automatic Firmware Update

properties for I/O devices in the configuration tree of the controller. The Automatic
Firmware Update property is also referred to as the Firmware Supervisor feature.

IMPORTANT Safety Consideration

Some Safety I/O devices do not support the Firmware Supervisor feature.
For example, Safety I/O devices on DeviceNet® networks and POINT
Guard I/O™ modules do not support the Firmware Supervisor feature.
This table describes the Automatic Firmware Update options for I/O devices.
Setting Description
• Disables any automatic firmware updates.
Disable
• This item only appears in the menu when you initially save the 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.
Enable and Store Files to Image
• Only I/O devices that are configured for Exact Match Keying participate in
the Automatic Firmware Update process. The devices that are used with
this option must support the revision of firmware being updated to.
• Disables automatic firmware updates for I/O devices in the configuration
tree of the controller.
Disable and Delete Files from • Removes I/O device firmware from the image, but does not remove
Image controller firmware from the image.
• This item only appears in the menu on subsequent saves of the image.
7. Click Store.
8. Click Yes in the confirmation dialog box that appears.

If you enabled Automatic Firmware Update, then a dialog box appears to inform you
which modules are not included in the Automatic Firmware Update operation.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 79

Chapter 6 Use the Secure Digital Card

IMPORTANT Do not remove the SD card while the controller is reading from or writing
to the card. If you remove the card during either activity, the data on the
card or controller can become corrupt. Also, the controller firmware at
the time when the card is removed can become corrupt. Leave the card
in the controller until the OK status indicator turns steady green.
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 is flashing green
- SD indicator is flashing 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 Allow the store to complete without interruption. If you interrupt the
store, data corruption or loss can occur.

Load from the SD Card After you set the communication path, are online with the controller, and changed the
controller to Program mode, you can load a project to the controller from the SD card.
Applies to these controllers:
ControlLogix 5580 IMPORTANT With the SD card and new, out-of-box controllers:
GuardLogix 5580 • If you insert an SD card with an image into a new, out-of-box controller
(firmware 1.x), then at powerup, the controller automatically updates the
firmware up to the version of firmware that is stored on the SD card. The
update happens regardless of the Load Image setting in the image on the
SD card (User Initiated, On Power Up, or On Uninitialized Memory).
• If the image was created with either On Power Up or On Uninitialized
Memory settings, then the controller both updates the firmware and loads
in the controller application.
You can load from an SD card to a controller in one of the following ways:
• Controller powerup
• User-initiated action

You can always use the Logix Designer application to load the project.

Controller Powerup
This table shows what happens at powerup when you insert an SD card that contains an image
into a controller.
Controller is in Firmware > 1.x and internal Firmware > 1.x and internal
Image Setting out-of-box condition
(v1.x firmware) nonvolatile memory is not valid(1) nonvolatile memory is valid(1)
User Initiated Loads Firmware Only(2) Does Nothing Does Nothing
• Loads Firmware if there is a • Loads Firmware if there is a
Loads both Firmware revision mismatch revision mismatch
On Power Up and Application
• Loads Application • Loads Application
• Loads Firmware if there is a
On Uninitialized Loads both Firmware revision mismatch
Memory (2) Does Nothing
and Application • Loads Application
(1) “Valid” includes the No Project condition.
(2) Indicates a change in behavior from ControlLogix 5570 and older controllers.

80 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 6 Use the Secure Digital Card

User-initiated Action

IMPORTANT For an out-of-box controller that uses firmware revision 1.xx, you must
manually update the controller to the required firmware revision before
you can load a project on the controller.

Before you can upload a project to the controller from the SD card when the controller is
already powered-up, you must do the following:
• Make sure that the controller has a working firmware revision.
• Establish the communication path.
• Go online with the controller.
• Make sure that the controller is in Program mode.

To load a project to the controller from the memory card, complete these steps.
1. Open the Controller Properties, and click the Nonvolatile Memory tab.
2. On the Nonvolatile Memory tab, verify that the project listed is the project that you want
to load.
If no project is stored on the SD card, a message in the lower-left corner of the
Nonvolatile Memory tab indicates that an image (project) is not available.
3. Click Load/Store.
If Load/Store is dimmed (unavailable), verify the following:
- You specified the correct communication path and are online with the controller.
- The SD card is installed.
- The controller is not in Run Mode.
4. Click Load.

After you click Load, the project loads to the controller as indicated by the controller
status indicators. A dialog box in the Logix Designer application also indicates that the
store is in progress.
Table 16 - Controller Status Indicators
OK
Controller SD Indicator 4-Character Display Message
Indicator
ControlLogix 5580 controller when Flashing Green Steady red “LOAD”, then followed by “UPDT”
restoring firmware or project
GuardLogix 5580 SIL 2 controller Flashing Green Steady red “LOAD”, then followed by “UPDT”
when restoring firmware or project
GuardLogix 5580 SIL 3 controller
during primary controller firmware Flashing Green Steady “Updating Firmware…Do Not Remove SD Card”
green
update
GuardLogix 5580 SIL 3 controller
during Safety Partner firmware Flashing Green Steady “Updating Firmware…Do Not Remove SD Card”
green
update
GuardLogix 5580 SIL 3 controller Flashing Green Steady “Loading…Do Not Remove SD Card”
during when loading project green

IMPORTANT Let the load complete without interruption. If you interrupt the
load, data corruption or loss can occur.
5. When the load is complete, the controller reboots.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 81

Chapter 6 Use the Secure Digital Card

Other Secure Digital Card You can perform these tasks with the SD card:
Tasks • Change the image that is loaded from the card
• Check for a load that was completed
Applies to these controllers:
ControlLogix 5580
• Clear an image from the SD card
GuardLogix 5580 • Store an empty image
• Change load parameters
• Read/write application data to the card
• (GuardLogix 5580 controllers only). View safety-lock status and safety signatures on the
Nonvolatile Memory tab

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

82 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 7
Manage Controller Communication
Connection Overview The controller provides connection resources whenever communication is established
between two devices.
Applies to these controllers:
ControlLogix® 5580 Connections are used when the system contains the following conditions or activities:
GuardLogix® 5580 • 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 HMIs communicate with the controller.

Nodes on an EtherNet/IP When configuring your control system, you must account for the number of EtherNet/IP™
nodes you include in the I/O configuration tree in your project. The following table shows the
Network maximum number of EtherNet/IP nodes that are supported for each controller.
Applies to these controllers: Table 17 - Maximum EtherNet/IP Nodes Supported for ControlLogix
ControlLogix 5580
Version 28 Version 29 Version 30 Version 31 or Version 36 or
GuardLogix 5580 Cat. No. later later
1756-L81E, 1756-L81EK, 1756-L81E-NSE, — 60 100 100 100
1756-L81EXT, 1756-L81EP
1756-L82E, 1756-L82EK, 1756-L82E-NSE, — 80 175 175 175
1756-L82EXT
1756-L83E, 1756-L83EK, 1756-L83E-NSE, 100 100 250 250 250
1756-L83EXT, 1756-L83EP
1756-L84E, 1756-L84EK, 1756-L84E-NSE, — 150 250 250 250
1756-L84EXT
1756-L85E, 1756-L85EK, 1756-L85E-NSE, 300 300 300 300 300
1756-L85EXT, 1756-L85EP
1756-L81ES, 1756-L81ESK, 1756-L81EXTS — — — 100 100
1756-L82ES, 1756-L82ESK, 1756-L82EXTS — — — 175 175
1756-L83ES, 1756-L83ESK, 1756-L83EXTS — — — 250 250
1756-L84ES, 1756-L84ESK, 1756-L84EXTS — — — 250 250
1756-L85ES — — — — 300

Table 18 - Maximum Ethernet/IP Nodes Supported for GuardLogix

Version 28 Version 29 Version 30 Version 31 or Version 36 or

Cat. No. later later
1756-L81ES, 1756-L81ESK, 1756-L81EXTS — — — 100 100
1756-L82ES, 1756-L82ESK, 1756-L82EXTS — — — 175 175
1756-L83ES, 1756-L83ESK, 1756-L83EXTS — — — 250 250
1756-L84ES, 1756-L84ESK, 1756-L84EXTS — — — 250 250
1756-L85ES — — — — 300

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 83

Chapter 7 Manage Controller Communication

With firmware revision 29 or later, the Capacity tab on the Controllers Properties dialog box
keeps a running count as you add nodes to the I/O configuration tree.

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 limits. The following are examples of devices that must be counted:
• Remote communication adapters
• Remote controllers
• Devices with an embedded EtherNet/IP port
• EtherNet/IP devices that connect to a communication module in the local chassis, even
though the communication module in the local chassis does not count as a node.
• 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 considering the EtherNet/IP node limitation of a ControlLogix 5580 controller, you do not
count Ethernet devices that exist on the EtherNet/IP network but are not added to the I/O
configuration section of the project.

The following devices are not added to the I/O configuration section in your project and are
not counted among the total number of nodes:
• Computer
• Communication modules in the local chassis
• HMIs that are not added to the I/O configuration section
• Devices that are the target of MSG Instructions
• Standard Ethernet devices with which the controller communicates via a socket
interface

84 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 7 Manage Controller Communication

The following example shows four nodes in the I/O tree.

Figure 30 - EtherNet/IP Nodes Example

Item Description
A Not a node. Module is in a local chassis.
B Node

CIP Security Considerations

If you use I/O data security (CIP Security™) for safety I/O, the maximum number of nodes
supported is reduced as follows:
Number of non-secure nodes + 2 * (number of secure nodes, integrity only) +
4 * (number of secure nodes, integrity, and confidentiality) <= 150
or
Maximum nodes supported by the controller, whichever is less.

If you do not use secure connections, the maximum number of nodes are dictated by the
controller catalog number.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 85

Chapter 7 Manage Controller Communication

Controller Communication The controller runs the communication task separately from the application code. The
controller runs communication asynchronously to the application. Therefore, it is important to
Interaction with Control Data make sure that communication that is delivered to the controller is complete before the
Applies to these controllers: 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.
ControlLogix 5580
GuardLogix 5580 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.

You can use the following methods to control the effects of asynchronous communication.
Blocking access helps to prevent source data values from changing by communication during
application execution. Allowing access means that communication can change source data
values during application execution.
• UID/UIE pairs
- Allows tag access for HMI, MSG instructions, I/O updates, produce/consume, and
motion planner
- Blocks tag access to other user tasks
• Moving data with CPS instructions—Blocks tag access for HMI, MSG instructions, I/O
updates, produce/consume, other user tasks, and motion planner.
• Periodic tasks—Allows tag access for HMI, MSG instructions, I/O updates, produce/
consume, other user tasks, and motion planner.

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 communication on an independent CPU core, these methods are no
longer effective in all cases.

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.

The following table shows that two data elements added to a structure for data integrity
checking: Start Data and End Data. 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 that communication is in the
process of filling the structure. The same applies to higher-level systems that are receiving
data from the controller.
Table 19 - 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

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 communication core. If you use
buffered data, you help prevent the risk of the communication core changing data
after you have passed the data valid test.

86 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 7 Manage Controller Communication

Produce and Consume The controllers let you produce (transmit) and consume (receive) controller-scoped tags.
ControlLogix 5580 controllers and GuardLogix 5580 controllers produce the same standard tag
(Interlock) Data through both the Ethernet port and the backplane, and consumer counts apply to the total
Applies to these controllers: consumers from both ports.
ControlLogix 5580 Figure 31 - Illustration of Produced and Consumed Tags
GuardLogix 5580

This table describes the system-shared tags.

Table 20 - Produced and Consumed Tag Definitions
Tag Definition
A tag that a controller makes available for use by other controllers. Multiple controllers can simultaneously consume (receive) the data. A
Produced tag produced tag sends its data to one or more consumed tags (consumers) without using logic.
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
Consumed tag 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 the connections of the controller and communication
modules.
For a ControlNet® network, produced and consumed tags use scheduled connections.
Table 21 - ControlNet Connections
Connection Definition
A scheduled connection is unique to ControlNet communication. A scheduled connection lets you send and receive data repeatedly at a
predetermined interval, which is the requested packet interval (RPI). For example, a connection to an I/O module is a scheduled
connection because you repeatedly receive data from the module at a specified interval.
Scheduled Other scheduled connections include connections to the following:
(unique to a ControlNet • Communication devices
network)
• Produced/consumed tags
On a ControlNet network, you must use RSNetWorx™ for ControlNet software to enable all scheduled connections and establish a network
update time (NUT). A scheduled connection reserves network bandwidth specifically to handle the connection.
An unscheduled connection is a message transfer between devices that the requested packet interval (RPI) or the program, such as an
Unscheduled MSG instruction, triggers. Unscheduled messaging lets you send and receive data as you need.
Unscheduled connections use the remainder of network bandwidth after scheduled connections are allocated.

Requested Packet Interval (RPI) of Multicast Tags

The first consumer of a multicast produced tag on any communication port establishes the RPI
value for that port. All subsequent consumers using 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.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 87

Chapter 7 Manage Controller Communication

Send and Receive Messages Messages transfer standard or safety data to other devices, such as other controllers or
operator interfaces. The MSG instruction is a ladder logic output instruction that
Applies to these controllers: asynchronously reads or writes a block of data to or from another module over the backplane
ControlLogix 5580 or a network. The size of the instruction depends on the data types and message command
GuardLogix 5580 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 either unconnected or connected. Unconnected messages are dependent

upon 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. Choosing to cache a connected message
instructs the controller to keep the connection open after the message has been completed -
this improves efficiency if the message is intended to be sent 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. 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. You can connect CIP™ generic messages. However, for most applications
we recommend that you leave CIP generic messages unconnected. Connected messages that
occur more frequently than once every 60 seconds should be cached if possible.
Table 22 - Message Types
Communication
Message Type Connected Message Message Can Be Cached
Method
CIP data table read or write N/A Configurable Yes
CIP No No
PLC-2®, PLC-3®, PLC-5®, or SLC™ CIP with Source ID No No
(all types)
DH+™ Yes Yes
CIP generic N/A Optional Yes
Block-transfer read or write N/A Yes Yes

Determine Whether to Cache Message Connections

When you configure an MSG instruction, you can choose whether to cache the connection.
Cached connections transfer data faster than uncached connections. The controllers
can cache 256 messages and trigger 256 messages simultaneously.
The following table describes the options for caching connections.
.

Table 23 - Options for Caching Connections

Frequency of Message Execution Action
Cache the connection.
Repeatedly This keeps the connection open and optimizes execution time. Opening a
connection each time the message executes increases execution time.
Do not cache the connection.
Infrequently This closes the connection upon completion of the message, which frees up
that connection for other uses.

88 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 7 Manage Controller Communication

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
Applies to these controllers: socket object. The controller communicates with the socket object via MSG instructions. MSG
ControlLogix 5580 instructions that configure and operate the socket interface must be configured as
GuardLogix 5580 Unconnected and use the Message to Self path. To communicate with another device, you
must understand the application protocol of the other device.

The controllers support up to 32 socket instances on a per-module basis: 32 sockets for the
embedded Ethernet port, plus 32 more for each Ethernet bridge in the local chassis.

These products support a secure socket object:

• Controllers, firmware revision 35.011 or later
• 1756-EN4TR modules, firmware revision 5.001 or later

For more information on the socket interface, see EtherNet/IP Socket Interface Application
Technique, publication ENET-AT002.

TLS Support
The secure socket option adds support for Transport Layer Security (TLS) to the socket object.

HTTP(S) REST API Client Support

You can develop your application to send HTTP REST API requests and implement HTTPS via
the socket interface with TLS. For more information, see the documentation for these objects
in the Common Application Library available from the Product Compatibility and Download
Center at rok.auto/pcdc:
• raC_Impl_HTTPClient
• raC_Impl_HTTPCmdGET
• raC_Impl_HTTPCmdPOST
• raC_Impl_HTTPCmdPUT

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 89

Chapter 7 Manage Controller Communication

Simple Network SNMP enables the controller to be remotely managed through other network management
software. SNMP defines the method of communication among the devices and also denotes a
Management Protocol manager for the monitoring and supervision of the devices. SNMP is disabled on the controller
(SNMP) by default. You can enable and disable SNMP on the controller with a CIP Generic MSG
(firmware revision 32 or later).

For more information about SNMP, see the Ethernet Reference Manual,
publication ENET-RM002.

Use a CIP Generic MSG to Enable SNMP on the Controller

1. Add an MSG instruction to your program.

IMPORTANT You cannot add an MSG instruction to your program if the

controller keyswitch 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 described
in the table below.

90 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 7 Manage Controller Communication

Table 24 - Enable SNMP

Field Description
Message Type CIP Generic
Service Type Custom
Service Code 4c
Instance 1
Class f5
Attribute 0
Controller tag of USINT[5] data type.
In this example, the controller tag is named onArray and must match the following
graphic.

Source Element

IMPORTANT: The Source Element tag in your Logix Designer application project
must match the values that are shown in the graphic. If you use values that are
different than the ones shown, SNMP will not be enabled.
Source Length 5
3. Configure the Communication tab to use a Path of THIS.

IMPORTANT Messages to THIS must be unconnected messages.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 91

Chapter 7 Manage Controller Communication

Use a CIP Generic MSG to Disable SNMP on the Controller

1. Add an MSG instruction to your program.

IMPORTANT You cannot add an MSG instruction to your program if the

controller keyswitch 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 described
in the table below.

Table 25 - Disable SNMP

Field Description
Message Type CIP Generic
Service Type Custom
Service Code 4c
Instance 1
Class f5
Attribute 0
Controller tag of USINT[5] data type.
In this example, the controller tag is named offArray and must match the following
graphic:

Source Element

IMPORTANT: The Source Element tag in your Logix Designer application project
must match the values that are shown in the graphic. If you use values that are
different than the ones shown, SNMP is not disabled.
Source Length 5

92 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 7 Manage Controller Communication

3. Configure the Communication tab to use a Path of THIS.

IMPORTANT Messages to THIS must be unconnected messages.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 93

Chapter 7 Manage Controller Communication

Notes:

94 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 8
Standard I/O Modules
Selecting ControlLogix Rockwell Automation offers many I/O modules for use in ControlLogix® controller systems. For
a list of all I/O product lines that are compatible with the ControlLogix controllers, see the 1756
I/O Modules ControlLogix Controllers Technical Data, publication 1756-TD001.
Applies to these controllers:
When you select I/O modules, remember the following:
ControlLogix 5580
GuardLogix 5580 • A wide variety of digital, analog, and specialty I/O modules are available from Rockwell
Automation. A number of these I/O modules support the following features:
- Field-side diagnostics
- Electronic fusing
- Individually isolated inputs/outputs
- Timestamping of inputs
- Scheduling of outputs
- Event detection of specific input patterns
• Removable terminal blocks (RTBs) or 1492 wiring systems are required for I/O modules.
• 1492 PanelConnect™ modules and cables can be used to connect input modules to
sensors.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 95

Chapter 8 Standard I/O Modules

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
Lets the installed device accept the key of the device that is defined in the project
when the installed device can emulate the defined device. With Compatible Module,
you can typically replace a device with another device that has the following
characteristics:
Compatible Module • 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.
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
Disable Keying 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.
Indicates that all keying attributes must match to establish communication. If any
Exact Match 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.

For more detailed information on Electronic Keying, see Electronic Keying in Logix 5000
Control Systems Application Technique, publication LOGIX-AT001.

96 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 8 Standard I/O Modules

Local I/O Modules The ControlLogix chassis that you choose affects how many local I/O modules you can use.
Several ControlLogix chassis sizes are available to suit your configuration requirements. You
Applies to these controllers: can fill the slots of your chassis with any combination of controllers, communication modules,
ControlLogix 5580 and I/O modules.
GuardLogix 5580
Table 26 - ControlLogix and ControlLogix-XT™ Chassis and Slots
Chassis Slots
1756-A4 4
1756-A7
7
1756-A7XT
1756-A10
10
1756-A10XT
1756-A13 13
1756-A17 17

If you have empty slots in your chassis, you can use the 1756-N2 or 1756-N2XT slot-filler
module.

Add Local I/O to the I/O Configuration

Add I/O modules to the backplane of the controller. There are two methods to add I/O modules
to the local chassis:
• Discover modules
• Add modules
Discover Modules

To use Discover Modules to add a local I/O module, complete these steps.
1. Go online with your controller.
2. In the I/O configuration, right-click the 1756 backplane and select Discover Modules.

The Logix Designer application automatically detects available modules that are
installed in the system.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 97

Chapter 8 Standard I/O Modules

3. On the Select Module Type dialog box, click Create next to the discovered module to add
to your project.

4. Configure the properties for the new module and click OK.

98 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 8 Standard I/O Modules

5. At the warning dialog box, click Yes and then close the Select Module Type dialog box.

IMPORTANT If you inhibit the module connection, you must remember to

uninhibit the connection later.

Add Modules
1. In the I/O configuration, right-click the backplane and select New Module.

2. On the Select Module Type dialog box, select the I/O module and click Create.

Use the filters to reduce the list of modules to choose from.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 99

Chapter 8 Standard I/O Modules

3. On the New Module dialog box, configure the module and click OK.

If the series or revision values in the module properties do not match those of the
module for which this configuration is intended, your project can experience
module faults.

100 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 8 Standard I/O Modules

Remote I/O Modules Remote I/O refers to I/O that is not in the local chassis and connects to the controller via a
communication network. There are several families of I/O that are remote from the controller:
Applies to these controllers:
• Compact 5000™ I/O modules in a remote bank using a 5069-AEN2TR or similar adapter
ControlLogix 5580
GuardLogix 5580
• 1756 I/O in a remote chassis via a Network Bridge Module
• Distributed I/O families such as POINT I/O™or Block I/O™
• On-Machine™ I/O families such as ArmorPOINT® or ArmorBlock® I/O

The ControlLogix controller supports the use of remote I/O via these networks:
• EtherNet/IP™
• ControlNet®
• DeviceNet®
• Universal remote I/O

For more information about the network configurations that can be used to connect remote
I/O, see Communication Networks on page 35.
Figure 32 - ControlLogix 5580 Controller and Remote I/O on a 1 Gbps EtherNet/IP Network

1756-L85E
1756 I/O
5069-AEN2TR
Compact 5000 I/O Modules

5069-AEN2TR
Compact 5000 I/O Modules

Workstation Stratix® Switch with 5069-AEN2TR

Gigabit Copper Ports Compact 5000 I/O Modules

Add Remote I/O to the Ethernet Port on the Controller

If you are adding remote I/O, you can add the I/O modules to the Ethernet port of the controller.
To add remote I/O to the I/O configuration of the controller project, complete these steps.

IMPORTANT You cannot bridge through the front Ethernet port of another controller
to add remote I/O.
1. In the I/O configuration, right-click Ethernet and select New Module.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 101

Chapter 8 Standard I/O Modules

2. On the Select Module Type dialog box, select the remote communication module or
EtherNet/IP device and click Create.

Use the filters to reduce the list of modules to choose from.

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.

3. Specify the communication module properties according to your network configuration

and click OK.
For more information about the communication module and network properties, see
Additional Resources on page 9.
4. Right-click the backplane of the newly added communication module and select New
Module.

102 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 8 Standard I/O Modules

5. On the Select Module Type dialog box, select the I/O module and click Create.

6. Specify the Module Properties according to your module and application and click OK.

Add Remote I/0 to a Local Communication Module

If you are using local communication modules that are connected to the controller, then add
the I/O modules to the backplane of the communication module. To add remote I/O to the I/O
Configuration in the Logix Designer application, complete these steps.
1. Right-click the backplane of the local chassis and select New Module.

2. On the Select Module Type dialog box, select a communication module and click Create.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 103

Chapter 8 Standard I/O Modules

3. Specify the communication module properties according to your network configuration

and click OK.

4. Right-click the communication network under the communication module and select
New Module.

5. Select the communication adapter for the I/O platform that you are using and click
Create.

104 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 8 Standard I/O Modules

6. Specify the module and connection properties according to your network configuration
and click OK.

7. Right-click the backplane of the newly added communication adapter and select New
Module.

8. On the Select Module Type dialog box, select the I/O module to add and click Create.

Use the filters to reduce the list of modules to choose from.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 105

Chapter 8 Standard I/O Modules

9. Specify the module properties according to your module and application and click OK.

106 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 8 Standard I/O Modules

Add to the I/O Configuration You can add I/O and other devices to the controller configuration while you are online, and the
keyswitch is in either the REM or PROG positions.
While Online .

Applies to these controllers: IMPORTANT To add I/O modules when the controller is online, the controller
ControlLogix 5580 keyswitch must be in the REM or PROG position.
GuardLogix 5580 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 version of the software you
are using. 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

You can add modules and devices to the local or remote chassis via an EtherNet/IP network, or
via the unscheduled portion of a ControlNet network.

For information on the number of nodes you can have for an EtherNet/IP network, see Nodes
on an EtherNet/IP Network on page 83.

For more information about adding to the I/O Configuration while online, see the Logix 5000
Controllers Design Considerations Reference Manual, publication 1756-RM094.

Modules that Can be Added While Online

You can add these modules to the I/O configuration while online with Logix Designer, version
28.00.00 or later.
• 1756 controllers
• 1756 ControlNet modules
• 1756 DeviceNet bridges
• 1756 EtherNet/IP modules
• Compact 5000 EtherNet/IP adapters and I/O modules
• FLEX 5000™ EtherNet/IP adapters and I/O modules
• 1756 I/O and specialty modules
• 1756-DHRIO
• 1756-DHRIOXT

IMPORTANT These ControlLogix modules cannot be added while online:

• Motion modules (1756-MO2AE, 1756-HYD02, 1756-MO2AS, 1756-MO3SE,
1756-MO8SE, 1756-MO8SEG, 1756-M16SE)
• 1756-RIO
• 1756-SYNCH
• Safety I/O

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 107

Chapter 8 Standard I/O Modules

Determine When Data is ControlLogix controllers update data asynchronously with the execution of logic. See these
flowcharts to determine when a controller, input module, or bridge sends data:
Updated
• Input Data Update Flowchart on this page
Applies to these controllers: • Output Data Update Flowchart on page 109
ControlLogix 5580
GuardLogix 5580 Input Data Update Flowchart

IMPORTANT Safety Consideration

GuardLogix® standard inputs are updated just like ControlLogix standard
inputs, but GuardLogix safety input tags (inputs, consumed, and mapped)
are updated and frozen at the beginning of safety task execution.

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

RTS  RPI? No

Yes

Data is sent by the module

Data is sent by the module at the RTS.
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
will only be 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 the data will be unchanged throughout the scan of the logic.

108 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 8 Standard I/O Modules

Output Data Update Flowchart

Automatic output
processing of each task.
Method of Output Data Production Type of local module

Cyclic data production at IOT instruction executes.

the RPI.
Safety Consideration
Local ControlNet bridge Local analog module Local discrete
The safety output RPI is
(CN2 series B and newer) Local Ethernet bridge module
the safety task period.
Local DeviceNet scanner

Data is sent by the Data is sent by the Data is sent by the controller No data sent by automatic Data is sent by the controller
controller triggered controller triggered to the ControlNet module output processing (data sent triggered by the end of task.
by the RPI. by the user program. (sent out on ControlNet at the at RPI).
next scheduled interval).

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 109

Chapter 8 Standard I/O Modules

Notes:

110 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 9
Safety I/O Devices
Add Safety I/O Devices When you add a safety I/O device to the system, define a configuration for the device:
Applies to these controllers:
• IP address for EtherNet/IP™ networks.
GuardLogix® 5580 • Safety network number (SNN). To set the SNN, see page page 115.
• Configuration signature. For information on when the configuration signature is set
automatically and when you must set it, see page 118.
• Reaction time limit. For information on setting the reaction time limit, see the
GuardLogix 5580 and Compact GuardLogix 5380 Safety Reference Manual, publication
1756-RM012.
• Safety input, output, and test parameters complete the device configuration.

IMPORTANT You cannot add safety I/O devices while online with the controller.

Configure Safety I/O Devices Add the safety I/O device to the communication device in the I/O configuration of the
controller project.
Some safety I/O devices support both standard and safety data. The device
definition settings define what data is available.
1. Right-click the Ethernet network and select New Module.

2. On the Select Module Type dialog box, select the safety I/O device and click Create.

Use the filters to reduce the list of devices to choose from.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 111

Chapter 9 Safety I/O Devices

3. Enter a name and IP address for the new device.

If your network uses Network Address Translation (NAT), see Use Network Address
Translation with CIP Safety Devices on page 113.

4. To modify the module definition settings, click Change.

IMPORTANT For safety I/O devices, do not use Disable Keying.

See Electronic Keying on page 96.

5. To modify the safety network number, click the button.

See Set the SNN of a Safety I/O Device on page 115.
6. Set the connection reaction time limit by using the Safety tab.
For information about system reaction time, see the GuardLogix 5580 and Compact
GuardLogix 5380 Safety Reference Manual, publication 1756-RM012.
7. To complete configuration of the safety I/O device, refer to the user documentation and
the Logix Designer online help.

112 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 9 Safety I/O Devices

Use Network Address Network Address Translation (NAT) translates one IP address to another IP address via a NAT-
configured router or switch. The router or switch translates the source and destination
Translation with CIP Safety addresses within data packets as traffic passes between subnets.
Devices
This service is useful if you must reuse IP addresses throughout a network. For example, NAT
Applies to these controllers: makes it possible for devices to be segmented into multiple identical private subnets while
GuardLogix 5580 maintaining unique identities on the public subnet, such as for multiple identical machines or
lines.

This section only applies to safety users where the controller and the devices it talks to are on
separate sides of the NAT-configured router or switch.

With CIP Safety™, the IP address of the device is part of the unique node reference that is part
of the protocol. The device compares the IP address portion of the unique node reference in
CIP Safety packets to its own IP address, and rejects any packets where they do not match.
The IP address in the unique node reference must be the NAT'ed IP address. The controller
uses the translated address, but the CIP Safety protocol requires the actual address of the
device.

If you use NAT to communicate with a CIP Safety device, follow these steps to set the IP
address.
1. In the IP Address field, enter the IP address for the controller.
This is usually the IP address on the public network when using NAT.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 113

Chapter 9 Safety I/O Devices

2. Click Advanced to open the Advanced Ethernet Settings dialog box.

3. Select the checkbox to indicate that this device and the controller communicate
through NAT devices.
4. Enter the actual device address.
If you configured the IP address using the rotary switches, this is the address you
set on the device. Alternately, the actual device address is the same address that
is shown on the Internet Protocol tab.
5. Click OK.

114 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 9 Safety I/O Devices

Set the SNN of a A time-based SNN is automatically assigned when you add the first safety I/O device on the
network. This does not apply to the controller backplane or Ethernet port since the controller
Safety I/O Device counts as a device on the network.

When subsequent safety devices are added to the same network, they are assigned the same
SNN as defined in the lowest address on that CIP Safety network or the controller itself if ports
are attached to the controller. For most applications, the automatic, time-based SNN is
sufficient.

If your application requires you to assign the SNN of safety I/O devices manually, you only have
to assign the SNN of the first safety I/O device you add in a remote network or backplane. The
Logix Designer application then assigns the SNN of the first device to any additional devices
that you add to that same remote network or backplane.

For an explanation on SNN, see the GuardLogix 5580 and Compact GuardLogix 5380 Safety
Reference Manual, publication 1756-RM012.

Change a Safety I/O Device SNN

Follow these steps to change the safety I/O device SNN to a manual assignment.
1. In the I/O configuration, right-click the remote EtherNet/IP™ communication device and
select New Module.
2. Select the safety I/O device and select Create.
3. On the New Module dialog box, select next to the safety network number.

4. On the Safety Network Number dialog box, select Manual.

5. Enter the SNN as a value from 1…9999 (decimal) and select OK.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 115

Chapter 9 Safety I/O Devices

6. On the New Module dialog box, click OK.

Copy and Paste a Safety I/O Device SNN

If you must apply an SNN to other safety I/O devices, you can copy and paste the SNN.
Copy an SNN
1. On the General view of the Module Properties dialog, select to the right of the SNN.

116 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 9 Safety I/O Devices

2. On the Safety Network Number dialog box, click Copy.

Paste an SNN

1. On the General view of the Module Properties dialog, select to the right of the SNN.

2. On the Safety Network Number dialog box, click Paste.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 117

Chapter 9 Safety I/O Devices

Safety I/O Device Signature Each safety device has a configuration signature that uniquely identifies the device
configuration. The configuration signature is composed of an ID number, date, and time, and is
used to verify a device’s configuration.

Configuration via the Logix Designer Application

When the I/O device is configured via the Logix Designer application, the configuration
signature is generated automatically. You can view and copy the configuration signature on
the Safety view of the Module Properties dialog box.
Figure 33 - View and Copy the Configuration Signature

118 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 9 Safety I/O Devices

Different Configuration Owner (Data-only Connection)

When the I/O device configuration is owned by another controller, you must copy the device
configuration signature from its owner’s project and paste it into the Safety view of the device
properties.
If the device is only configured for inputs, you can copy and paste the
configuration signature. If the device has safety outputs, they are owned by the
controller that owns the configuration, and the configuration signature ID text box
is unavailable.
Figure 34 - View and Copy the Configuration Signature from a Different Owner

Reset Safety I/O Device to Out-of-box Condition

If a Guard I/O™ device was used previously, clear the existing configuration before installing it
on a safety network by resetting the device to its out-of-box condition.

When the controller project is online, the Safety tab of the device properties displays the
current configuration ownership. When the opened project owns the configuration, Local is
displayed. When a second device owns the configuration, Remote is displayed, along with the
SNN and node address or slot number of the configuration owner. A communication error
appears if the device read fails.

If the connection is local, you must inhibit the device connection before resetting ownership.
Follow these steps to inhibit the device.
1. Right-click the device and choose Properties.
2. Click the Connection tab.
3. Check Inhibit Connection.
4. Click Apply and then OK.

Follow these steps to reset the device to its out-of-box configuration when online.
1. Right-click the device and choose Properties.
2. Click the Safety tab.
.
3. Click Reset Ownership.
You cannot reset ownership when there are pending edits to the device properties,
when a safety signature exists, or when safety-locked.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 119

Chapter 9 Safety I/O Devices

I/O Device Address Format When you add a device to the I/O configuration, the Logix Designer application creates
controller-scoped tags for the device.

I/O information is presented as a set of tags. Each tag uses a structure of data, depending on
the type and features of the I/O device. The name of a tag is based on the name of the device.

A safety I/O device address follows this example: devicename:Type.Member

Table 27 - Safety I/O Device Address Format
Where Is
device name The name of the safety I/O device
Input: I
Type Type of data Output: O
Specific data from the I/O device
devicename:I.RunMode(1)
Input-only device devicename:I.ConnectionFaulted(1)
devicename:I.Input Members
devicename:I.RunMode(1)
Member Output-only device devicename:I.ConnectionFaulted(1)
devicename:O.Output Members
devicename:I.RunMode(1)
Combination I/O devicename:I.ConnectionFaulted(1)
devicename:I.Input Members
devicename:O.Output Members
(1) This member is required.

For more information on addressing standard I/O devices, see the Logix 5000 Controllers I/O
and Tag Data Programming Manual, publication 1756-PM004.

Monitor Safety I/O You can monitor safety I/O device status via Explicit Messaging or via the status indicators on
the device. For more information, see the product documentation for the device.
Device Status

120 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 9 Safety I/O Devices

Replace a Safety I/O Device You can replace safety I/O devices while they are connected to GuardLogix® controllers.

Configuration Ownership
When the controller project is online, the Safety tab of the device Properties dialog box
displays the current configuration ownership:
• When the opened project owns the configuration, Local is displayed.
• When a second device owns the configuration, Remote is displayed, along with the SNN
and the node address or slot number of the configuration owner.
• If the device read fails, a communication error appears.

If the connection is Local, you must inhibit the device connection before resetting ownership.
Follow these steps to inhibit the device.
1. Right-click the device and choose Properties.
2. Click the Connection tab.
3. Check Inhibit Connection.
4. Click Apply and then OK.

Safety I/O Replacement Options

Two options for safety I/O device replacement are available on the Safety tab of the Controller
Properties dialog box in the Logix Designer application:
• Only Allow Automatic Configuration When No Safety Signature Exists
Select this option if you rely on a portion of the CIP Safety system to maintain
SIL 2 or SIL 3 behavior during device replacement and functional testing.
See Only Allow Automatic Configuration When No Safety Signature Exists.
• Always Allow Automatic Configuration
Select this option if you do not rely on the entire routable CIP Safety system to maintain
SIL 2 or SIL 3 behavior during device replacement and functional testing.
See Always Allow Automatic Configuration.
For more considerations about choosing an automatic configuration setting, including
example use cases, see the GuardLogix 5580 and Compact GuardLogix 5380 Safety Reference
Manual, publication 1756-RM012.
Figure 35 - Figure 19 - Safety I/O Replacement Options

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 121

Chapter 9 Safety I/O Devices

Only Allow Automatic Configuration When No Safety Signature Exists

When a safety I/O device is replaced, the configuration is downloaded from the safety
controller if the DeviceID of the new device matches the original. The DeviceID is a
combination of the node/IP address and the Safety Network Number (SNN) and is updated
whenever the SNN is set.
If you select the Only Allow Automatic Configuration When No Safety Signature Exists option,
follow the guidance in Table 28 to replace a safety I/O device based on your scenario. After you
complete the steps, the DeviceID matches the original and enables the safety controller to
download the proper device configuration and re-establish the safety connection.
Table 28 - Replace a Device

Safety Signature Exists Replacement Device Action Required

Condition
No No SNN (out-of-box) None. The device is ready for use.
Same SNN as original
Yes or No None. The device is ready for use.
safety task configuration
See Scenario 1 - Replacement Device is Out-of-box and
Yes No SNN (out-of-box) Safety Signature Exists.

Yes See Scenario 2 - Replacement Device SNN is Different from

Different SNN from original Original and Safety Signature Exists.
safety task configuration See Scenario 3 - Replacement Device SNN is Different from
No Original and No Safety Signature Exists.

Scenario 1 - Replacement Device is Out-of-box and Safety Signature Exists

1. Remove the old I/O device and install the new device.
2. Right-click the replacement safety I/O device and choose Properties.
3. Click to the right of the safety network number to open the Safety Network
Number dialog box.

122 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 9 Safety I/O Devices

4. Click Set.

5. Verify that the Network Status (NS) status indicator is alternating red/green on the
correct device before clicking Yes on the confirmation dialog box to set the SNN and
accept the replacement device.
6. Follow your company-prescribed procedures to functionally test the replaced I/O device
and system and to authorize the system for use.

Scenario 2 - Replacement Device SNN is Different from Original and Safety Signature Exists
1. Remove the old I/O device and install the new device.
2. Right-click your safety I/O device and select Properties.
3. In the navigation pane, click Safety.
4. Click Reset Ownership.

5. Click OK.
6. Right-click the device and select Properties.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 123

Chapter 9 Safety I/O Devices

7. Click to the right of the safety network number to open the Safety Network
Number dialog box.

8. Click Set.

9. Verify that the Network Status (NS) status indicator is alternating red/green on the
correct device before clicking Yes on the confirmation dialog box to set the SNN and
accept the replacement device.
10. Follow your company-prescribed procedures to functionally test the replaced I/O device
and system and to authorize the system for use.

124 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 9 Safety I/O Devices

Scenario 3 - Replacement Device SNN is Different from Original and No Safety Signature Exists
1. Remove the old I/O device and install the new device.
2. Right-click your safety I/O device and select Properties.
3. In the navigation pane, select Safety.
4. Click Reset Ownership.

5. Click OK.
6. Follow your company-prescribed procedures to functionally test the replaced I/O device
and system and to authorize the system for use.
Always Allow Automatic Configuration

ATTENTION: Select the Always Allow Automatic Configuration option only if

the entire CIP Safety Control System is not being relied on to maintain SIL 2 or
SIL 3 behavior during the replacement and functional testing of a device. Do
not place devices that are in the out-of-box condition on a CIP Safety network
when the Always Allow Automatic Configuration option is selected, except
while following this replacement procedure.
When the Always Allow Automatic Configuration option is selected in the controller project, the
controller automatically checks for and connects to a replacement device that meets all the
following requirements:
• The controller has configuration data for a compatible device at that network address.
• The device is in out-of-box condition or has an SNN that matches the configuration.

If the Always Allow Automatic Configuration option is selected, follow these steps to replace a
safety I/O device.
1. Remove the old I/O device and install the new device.
a. If the device is in out-of-box condition, go to step 5.
No action is needed for the GuardLogix controller to take ownership of the device.
b. If an SNN mismatch error occurs, go to the next step to reset the device to an out-of-
box condition.
2. Right-click the safety I/O device and select Properties.
Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 125
Chapter 9 Safety I/O Devices

3. In the navigation pane, select Safety.

4. Click Reset Ownership and click OK.

5. Follow your company-prescribed procedures to functionally test the replaced I/O device
and system and to authorize the system for use.

126 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 10
Develop Standard Applications
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
Applies to these controllers: • Programs
ControlLogix® 5580
• Routines
GuardLogix® 5580
• Parameters and Local Tags
• Add-On Instructions
Figure 36 - Elements of 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

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 127

Chapter 10 Develop Standard Applications

Tasks The 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 only one task at a time.
• One task can interrupt the execution of another and take control based on its priority.
• In any given task, multiple programs can be used. However, only one program executes
at a time.
• You can display tasks in the Controller or Logical Organizer views, as necessary.
Figure 37 - Task Within a Control Application

Controller Fault Handler

Task 32

Task 1
Configuration

Status

Period
Program 1000
Watchdog
Program 1 Program Tags
Main Routine and Program
Parameters
Fault Routine

Other
Routines

Controller (global) Add-On Instruction System-shared

I/O Data
Tags Definition Data

Figure 38 - Tasks
Controller Organizer Logical Organizer

Main Task
(continuous)

Main Task
(continuous)

Task 2 Task 2
(periodic) (periodic)

128 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 10 Develop Standard Applications

A task provides scheduling and priority information for a set of one or more programs.
Configure tasks as continuous, periodic, or event by using the Task Properties dialog box.
Figure 39 - Configure the Task Type

This table explains the types of tasks that you can configure.
Table 29 - Task Types and Execution Frequency
Task Type Task Execution Description
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.
Continuous Constant • The continuous task runs constantly. When the continuous task
completes a full scan, it restarts immediately.
• A project does not require a continuous task. If used, there can be only
one continuous task.
A periodic task performs a function at an interval.
• Whenever the time for the periodic task expires, the task interrupts
At a set interval, such as any lower priority tasks, executes once, and returns control to where
Periodic each 100 ms the previous task left off.
• You can configure the time period from 0.1…2,000,000.00 ms. The
default is 10 ms. It is also controller and configuration dependent.
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
Immediately when an • An EVENT instruction
Event • An axis trigger
event occurs
• A motion event trigger
You can configure an optional timeout interval for missed event triggers,
which 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 ControlLogix 5580 and GuardLogix 5580 controllers support 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.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 129

Chapter 10 Develop Standard Applications

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. Configure the task priority by using the Task Properties dialog box.
Figure 40 - Configure the Task Priority

130 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 10 Develop Standard Applications

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 41 - 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

Figure 42 - Programs

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 131

Chapter 10 Develop Standard Applications

Scheduled and Unscheduled Programs

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 43 - Scheduling an Unscheduled Program

132 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 10 Develop Standard Applications

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 44 - 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

Figure 45 - Routines

Routine

Routine Routine

Routine

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 133

Chapter 10 Develop Standard Applications

Parameters and Local Tags With a Logix 5000® controller, you use a tag (alphanumeric name) to address data (variables).
In Logix 5000 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.
Controller Organizer —Main Program Parameters and Local Tags Logical Organizer —Main Program Parameters and Local Tags

Program Parameters and Local Tags Window

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 Logix 5000 Controllers and
I/O Tag Data Programming Manual, publication 1756-PM004.

Program Parameters
Program parameters define a data interface for programs to facilitate data sharing. Data
sharing between programs can be achieved either through pre-defined connections between
parameters or directly through a special notation.

Unlike local tags, all program parameters are publicly accessible outside of the program.
Additionally, HMI external access can be specified on an individual basis for each parameter.

There are several guidelines for creating and configuring parameters and local tags for
optimal task and program execution:
• Logix 5000 Controllers and I/O Tag Data Programming Manual, publication 1756-PM004
• Logix 5000 Controllers Program Parameters Programming Manual,
publication 1756-PM021
• Logix 5000 Controllers Design Considerations Reference Manual,
publication 1756-RM094

134 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 10 Develop Standard Applications

Programming Languages The Studio 5000 Logix Designer® application supports these programming languages.
Language Is best used in programs with
Continuous or parallel execution of multiple operations (not sequenced)
Boolean or bit-based operations
Complex logical operations
Message and communication processing
Ladder Diagram (LD) Machine interlocking
Operations that service or maintenance personnel have to interpret to
troubleshoot the machine or process
IMPORTANT: Ladder Diagram is the only programming language that can
be used with the Safety Task on GuardLogix 5580 controllers.
Continuous process and drive control
Function Block Diagram (FBD) Loop control
Calculations in circuit flow
High-level management of multiple operations
Repetitive sequence of operations
Sequential Function Chart (SFC) Batch process
Motion control that uses structured text
State machine operations
Complex mathematical operations
Structured Text (ST) Specialized array or table loop processing
ASCII string handling or protocol processing

For more information, see the Logix 5000 Controllers Common Procedures Programming
Manual, publication 1756-PM001.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 135

Chapter 10 Develop Standard 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 the 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 30 explains some
of the capabilities and advantages of using Add-On Instructions.
Table 30 - Add-On Instruction Capabilities
Capability Description
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
Save Time 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.
You create Add-On Instructions by using one of three editors:
• Ladder Diagram
Use Standard Editors
• Function Block Diagram
• Structured Text
You can export/import Add-On Instructions to other projects and copy and paste
Export/Import Add-On them from one project to another. Give each instruction a unique, descriptive name
Instructions to make it easier to manage and reuse your collection of Add-On Instructions.
Context views let you visualize the logic of an instruction for instant, simplified
Use Context Views
online troubleshooting of your Add-On Instructions.
When you create an instruction, you enter information for the description fields.
Each instruction definition includes revision, change history, and description
Document the Instruction information. The description text also becomes the help topic for the instruction.
You can also generate a signature for the Add-On Instruction, and include the Add-
On Instruction in a tracking group.
When you create Add-On Instructions, you can limit users of your instructions to
read-only access, or you can bar access to the internal logic or local parameters that
are used by the instructions. This source protection lets you stop unwanted changes
Apply Source Protection to your instructions and helps protect your intellectual property.
You can pre-compile and encrypt your Add-On Instruction for better Intellectual
property protection. This feature has less of a performance impact than the Logix
Designer application source protection.

Once defined in a project, Add-On Instructions behave similarly to the built-in instructions in
the controllers. With Studio 5000 Logix Designer application version 31 and greater, Add-On
Instructions appear under the Assets folder in the organizer. They also appear on the
instruction toolbar for easy access along with internal instructions.
Figure 46 - Add-On Instructions (Logix Designer Application Version 31 Example)

Instruction Toolbar

136 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 10 Develop Standard Applications

Extended Properties The Extended Properties feature lets you define more information, such as limits, engineering
units, or state identifiers for various components within your controller project.
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.
In the properties that are associated with the Add-On Instruction definition,
Add-On Instructions 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 have been
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, as there is no indication in the
tag browser that limit 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 the following:
• 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 .@Min and .@Max syntax defines. However, you
cannot write to extended properties values in logic.

For more information on Extended Properties, see the Logix 5000 Controllers I/O and Tag Data
Programming Manual, publication 1756-PM004.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 137

Chapter 10 Develop Standard 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 instruction to the module name. The
from an Add-On Instruction specified module must be present in the I/O Configuration section of the controller organizer
and must have a device name.
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 Logix 5000 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

138 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 10 Develop Standard Applications

Monitor Controller Status The ControlLogix controller uses Get System Value (GSV) and Set System Value (SSV)
instructions to get and set (change) controller data. The controller stores system data in
objects.

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 47 - 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 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 1756-UM543R-EN-P - March 2025 139

Chapter 10 Develop Standard 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, see Knowledgebase
Technote EtherNet/IP Reduced Heartbeats as of RSLogix5000 version 16.
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, which you can access via the following:
- The Module Properties dialog box
- A GSV instruction

For more information about I/O faults, see the Logix 5000 Controllers Major, Minor, and I/O
Faults Programming Manual, publication 1756-PM014.

Determine If I/O Communication Has Timed Out

This example can be used with the ControlLogix 5580 or GuardLogix 5580 controllers, and help
determine if controller communication has timed out:
• 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, then at least one I/O connection has been lost and the Fault_Alert is
set.
Figure 48 - GSV Used to Identify I/O Timeout

IMPORTANT Safety Consideration

Safety controllers have individual connection status on each safety I/O
module as part of the input tag.

Determine if I/O Communication to a Specific I/O Module has Timed Out

If communication times out with a device (module) in the I/O configuration of the controller,
the controller produces a fault code and fault information for the module. You can use GSV
instructions to get fault code and information via the FaultCode and FaultInfo attributes of the
Module object.
For more information about monitoring safety I/O faults, see the GuardLogix 5580 and
Compact GuardLogix 5380 Safety Reference Manual, publication 1756-RM012.

140 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 10 Develop Standard Applications

Automatic Handling of I/O Module Connection Faults

Depending on your application, you may want an I/O connection error to cause the Controller
Fault Handler to execute. To do so, set the module property that causes a major fault to result
from an I/O connection error. The major fault causes the execution of the Controller Fault
Handler.

ATTENTION: You cannot program Safety I/O module connections or safety

produce/consume connections to automatically cause a major fault on the
controller. See Develop Safety Applications on page 143.

If it is important to interrupt your normal program scan to handle an I/O connection fault, set
the ‘Major Fault On Controller If Connection Fails While In Run Mode’ and put the logic in the
Controller Fault Handler.
Figure 49 - I/O Connection Fault Causes Major Fault

If responding to a failed I/O module connection can wait until the next program scan, put the
logic in a normal routine and use the GSV technique that is described on page 140 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
Controller Fault Handler is used.

For more information about programming the Controller Fault Handler, see the Logix 5000
Major, Minor, and I/O Faults Programming Manual, publication 1756-PM014.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 141

Chapter 10 Develop Standard Applications

Sample Controller Projects The Logix Designer application includes sample projects that you can copy and modify to fit
your application. To access the sample projects, choose Sample Project on the Studio 5000®
dialog box.
Figure 50 - Sample Projects

142 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 11
Develop Safety Applications
You can use both standard (non-safety-related) and safety-related components in the
GuardLogix® control system. Within a GuardLogix project, you can perform standard
automation control from standard tasks. GuardLogix 5580 controllers and Compact GuardLogix
5380 controllers provide the same functionality as other controllers. What differentiates the
controllers from standard controllers is that the controllers also provide a SIL 2 or SIL 3
capable safety task.

However, a logical and visible distinction is required between the standard and safety-related
portions of the application. The Studio 5000 Logix Designer® application provides this
differentiation via the safety task, safety programs, safety routines, safety tags, and safety I/O
devices.

Safety Overview This chapter explains the components of a safety project and the features that help protect
safety application integrity, such as the safety signature and safety-locking.
Applies to these controllers:
GuardLogix 5580 The GuardLogix 5580 and Compact GuardLogix 5380 Safety Reference Manual, publication
1756-RM012 addresses the following topics:
• Guidelines and requirements for developing and commissioning
SIL 2/PLd and SIL 3/PLe safety applications, including Add-on Profiles
• Creating a detailed project specification
• Writing, documenting, and testing the application
• Generating the safety signature to identify and protect the project
• Confirming the project by printing or displaying the uploaded project and manually
comparing the configurations, safety data, and safety program logic
• Verifying the project through test cases, simulations, functional verification tests, and
an independent safety review, if necessary
• Locking the safety application
• Calculating system reaction time

ATTENTION: Performing an online modification (to logic, data, or

configuration) can affect the Safety Functions of the system if the
modification is performed while the application is running. A modification
should only be attempted if necessary. Also, if the modification is not
performed correctly, it can stop the application. Therefore, when the safety
signature is deleted to make an online edit to the safety task, before
performing an online modification, alternative safety measures must be
implemented and be present during the update.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 143

Chapter 11 Develop Safety Applications

Program Safety Applications Figure 51 shows the steps that are required for commissioning a GuardLogix system. For an
explanation of those steps, see the GuardLogix 5580 and Compact GuardLogix 5380 Safety
Reference Manual, publication 1756-RM012.
Figure 51 - Commission the System

Specification of the Safety Function

Create the Project Create the Project

Online Offline

Attach to Controller and Download

Test the Application Program

Generate the Safety Signature Make Required

Modifications

Validate the Project

Validation No Delete Safety Signature

Successful?

Yes

Confirm the Project

Record Safety Signature

Fill out the Safety Checklists

Safety Assessment

Project No
Valid?

Yes

Lock the Controller

144 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 12
Develop Secure Applications
These controllers support IEC-62443-4-2 SL 1 security certification.
Applies to these controllers:
Controller Firmware Revision
ControlLogix® 5580
ControlLogix 5580 standard controllers 32 or later
GuardLogix® 5580
ControlLogix 5580 NSE, XT, K, and Process controllers 33 or later
GuardLogix 5580 controllers 37 or later

IMPORTANT If enabled, the following features cause the controller to be excluded

from IEC-62443-4-2 SL 1 security certification:
• OPC UA
• Redundancy
• Secure socket objects
• Remote deployment of save/restore images

To help meet these requirements, you must use this publication and the Security Configuration
User Manual, publication SECURE-UM001. The Security Configuration User Manual describes
how to configure and use Rockwell Automation products to improve the security of your
industrial automation system.
The controller accepts all values appropriate for a tag data type, and it is the responsibility of
the user program to specify valid ranges and perform validity to check for those ranges. The
controller verifies incoming messages for syntax, length, and format.

You can apply these same measures to other ControlLogix and GuardLogix controllers, but
without security certification.
Resource Description
Provides guidance on how to conduct vulnerability assessments,
Security Design Guide Reference Manual, implement Rockwell Automation products in a secure system,
publication SECURE-RM001 harden the control system, manage user access, and dispose of
equipment.
Logix 5000 Controllers Security Describes how to configure security for the Studio 5000 Logix
Programming Manual, Designer® application, and explains how to configure source
publication 1756-PM016 protection for your logic and projects.
CIP Security Application Technique, Describes how to plan an implement a Rockwell Automation system
publication SECURE-AT001 that supports the CIP Security™ protocol.
Defines manufacturing-focused reference architectures to help
Converged Plantwide Ethernet (CPwE) accelerate the successful deployment of standard networking
Design and Implementation Guide, technologies and convergence of manufacturing and enterprise/
publication ENET-TD001 business networks.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 145

Chapter 12 Develop Secure Applications

Controller Security Features The following figure shows an example of a secure control system that implements other
security-focused products. For certification requirements related to other security-focused
products, see the security checklists.
Figure 52 - Secure Architecture Example
FactoryTalk® FactoryTalk FactoryTalk
Domain Controller Directory Server AssetCentre Server View SE Server Syslog Collector

Stratix® 5400 Switch

MOD MOD MOD MOD MOD

NET NET NET NET NET

2 2 2 2 2

EtherNet/IP
1 1 1 1 1
DC INPUT
1 I/O I/O-A I/O-B I/O-A I/O-B I/O-A I/O-B
1 6 1 6 1 6 1 6 1 6 1 6 1 6

4
I/O

5 10 5 10 5 10 5 10 5 10 5 10 5 10
UFB UFB-A UFB-B UFB-A UFB-B UFB-A UFB-B
LNK1 LNK2 NET OK

D+ D+ D+ D+ D+ D+
D- D- D- D- D- D-

MF- A MF- B MF- A MF-B MF- A MF-B

-
MBRK
+

Kinetix® 5700 ControlLogix 5580 Controller Studio 5000 Logix Designer FactoryTalk
Drive 1756-EN4T EtherNet/IP™ ControlFLASH Plus™ or View SE Client
Communication Module ControlFLASH™ software

Security Checklists
Follow the security checklists in this chapter to secure the system and controller. It is your
responsibility to monitor the system periodically to make sure that the security settings
function as you configured them.

Table 31 - Requirements for Identification and Authorization

Required to Meet
Security Component Details
IEC-62443-4-2 SL 1
Configure FactoryTalk Security to define policies, user groups, and other permission sets.
• The Logix Designer application enforces the policy based on the access policies that are
provided to it by FactoryTalk Security for the software authenticated user. Once
authenticated, the Logix Designer application acts as your interface to the controller. This
FactoryTalk Security software applies to all protected CIP™ communications to the controller, whether from Ethernet,
Studio 5000 Logix Designer application Yes backplane, or USB.
• The FactoryTalk Services Platform offers feature access control to manage user access to
product features such as controller download, project import, project create, and firmware
update.
For more information, see Configure System Security Features User Manual, SECURE-UM001.
May be required based
(Safety controllers only). Access control Configure FactoryTalk Security to restrict access to generate and delete the safety signature.
on system design,
to generate and delete the safety To configure FactoryTalk Security permissions, see the Configure System Security Features User
threat model, and risk
signature Manual, SECURE-UM001.
assessment.
May be required based
(Safety controllers only). Access control on system Configure FactoryTalk Security to restrict access to safety-lock and safety-unlock actions.
design,
to safety-lock and safety-unlock To configure FactoryTalk Security permissions, see the Configure System Security Features User
threat model, and risk
actions Manual, SECURE-UM001.
assessment.

146 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 12 Develop Secure Applications

Table 32 - Requirements for Use Control

Required to Meet
Security Component Details
IEC-62443-4-2 SL 1
Configure the controller project in the Logix Designer application to use these user access
methods:
• License-based source protection limits access to projects to only users with the required
license. Users without the required license cannot open the project or import components
that are protected by the license.
May be required based • License-based execution protection allows execution of the component only on a specific
Studio 5000 Logix Designer® application on system design, controller family, or only on controllers in a specific controller family that contain the
threat model, and risk execution license.
assessment. • Password-based protection uses a source key (password) to help protect source logic. All
source keys are stored in the sk.dat file.
• The Logix Designer application has two tag attributes that control access to tag data. The
External Access attribute controls how external applications can access tags. The Constant
attribute value determines if controller logic can change a tag.
For more information, see Logix 5000 Controllers Security Programming Manual, 1756-PM016.
Configure FactoryTalk Security to define policies, user groups, and other permission sets.
• The Logix Designer application enforces the policy based on the access policies that are
provided to it by FactoryTalk Security for the software authenticated user. Once
authenticated, the Logix Designer application acts as your interface to the controller,
including all protected CIP communication to the controller, whether from Ethernet,
backplane, or USB.
• The FactoryTalk Services Platform offers feature access control to manage user access to
FactoryTalk Security software product features, such as controller download, project import, project create, and firmware
Yes
Studio 5000 Logix Designer application update.
• In FactoryTalk Security, define which users can change controller modes and download
projects to the controller.
• Security authority binding restricts the controller to a specific FactoryTalk Security instance.
This binding reduces the attack surface for security server spoofing because the client
software and the security software determine the identity of the security authority
responsible for controlling access.
For more information, see the Configure System Security Features User Manual, SECURE-UM001.
Place the keyswitch in the RUN position to help prevent unauthorized remote configuration
changes to the controller, and restrict some communication services.
May be required based Remove the keyswitch from a running controller to help prevent modifications to the
on system design,
Controller keyswitch position configuration or program.
threat model, and risk IMPORTANT: Do not apply a new security policy while the controller is in RUN mode. RUN mode
assessment. does not help prevent updates to the security policy, and a policy change has the potential to
disrupt a running control system.
May be required based The Ethernet port is enabled by default. Disable the Ethernet port if required by the system
on system design,
Disable the controller Ethernet port design, threat model, or risk assessment.
threat model, and risk For more information, see page 156.
assessment.
May be required based
Disable Simple Network Management SNMP is disabled by default. If SNMP has been enabled, disable SNMP if required by the system
on system design,
Protocol (SNMP) on the controller design, threat model, or risk assessment.
threat model, and risk
(firmware revision 32 or later) For more information, see page 90.
assessment.
May be required based CIP Security ports on the controller are enabled by default. Disable the CIP Security ports if
Disable the controller CIP Security ports on system design, required by the system design, threat model, or risk assessment.
threat model, and risk For more information, see page 158.
assessment.
May be required based The USB port on the controller is enabled by default. Disable the USB port if required by the
on system design,
Disable the controller USB ports system design, threat model, or risk assessment.
threat model, and risk For more information, see page 161.
assessment.
May be required based The SD card is enabled by default. Disable the SD card if required by the system design, threat
on system design,
Disable the controller SD card model, or risk assessment.
threat model, and risk For more information, see page 162.
assessment.
May be required based Controller webpages for diagnostics are read-only. With Studio 5000 Logix Designer application
on system design, version 33 or later, controller webpages are disabled by default. Disable the controller webpages
Disable controller webpages threat model, and risk if required by the system design, threat model, or risk assessment.
assessment. For more information, see page 168.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 147

Chapter 12 Develop Secure Applications

Table 33 - Requirements for System Integrity

Required to Meet IEC- Details
Security Component 62443-4-2 SL 1
FactoryTalk AssetCentre software The FactoryTalk AssetCentre server centrally tracks and manages configuration changes and
restricts who can make changes based on FactoryTalk Security settings. This server
functionality assists with diagnostics and troubleshooting and reduces maintenance time for
Yes
FactoryTalk Security software production assets.
Configure the Device Monitor - Change Detect operation for the controller.
For more information, see Configure System Security Features User Manual, SECURE-UM001.
Use ControlFLASH Plus™ or ControlFLASH™ software to update controller firmware.
ControlFLASH Plus™ or ControlFLASH™ Yes Digitally signed firmware files have a .DMK (Device Management Kit) extension. ControlFLASH
software software authenticates the origin of a DMK file and validates the file before downloading in the
device.
You can generate a signature on an Add-On Instruction. This signature seals (encrypts) the Add-
Studio 5000 Logix Designer application Yes On Instruction to help prevent modification.
To meet IEC-62443-4-2 SL 1 security requirements, you must use a certified version of the
controller firmware. We recommend that you use the latest minor revision of your firmware.
The controller is designed such that:
Controller firmware update Yes • You cannot update firmware when the keyswitch is in the RUN position.
• You cannot go online with a controller that is in a firmware update process.
For more information, see page 30.
May be required to The Trusted slots feature restricts communication paths through which certain operations are
Trusted® slots on the controller maintain network performed on Logix 5000 controllers. A Trusted slot is not configured by default.
segmentation. For more information, see page 150.
May be required based If your application requires a major fault in addition to those already monitored by the controller,
User-definable major controller faults on system design,
threat model, and risk define a predetermined state with a major fault so that outputs are off.
For more information, see page 156.
assessment.
Safety controllers use a safety signature to verify the integrity of a safety application. The
Yes for SIL 2 or SIL 3 safety signature must be applied on a SIL 2/PLd or SIL 3/PLe safety controller to perform
(Safety controllers only). automated background integrity checks on the safety application. We recommend that you
Safety signature configuration. record and store the safety signature in a separate location to verify its integrity during audits
or when tampering is suspected.

Table 34 - Requirements for Data Confidentiality

Required to Meet
Security Component Details
IEC-62443-4-2 SL 1
Configure FactoryTalk Security to define policies, user groups, and other permission sets.
• The FactoryTalk Services Platform offers feature access control to manage user access to
product features such as controller download, project import, project create, and firmware
update.
• In FactoryTalk Security, define which users can change controller modes and download
FactoryTalk Security software Yes projects to the controller.
• Security authority binding restricts the controller to a specific FactoryTalk Security instance.
This binding reduces the attack surface for security server spoofing because the client
software and the security software determine the identity of the security authority
responsible for controlling access.
For more information, see Configure System Security Features User Manual, SECURE-UM001.
Use the FactoryTalk Policy Manager software to define a secure data transport over an
FactoryTalk Policy Manager software Yes EtherNet/IP™ network to the controller.
For more information, see Configure System Security Features User Manual, SECURE-UM001.
Configure licenses to manage access to controller source logic and execution of that logic.
These licenses are not enabled by default.
• License-based source protection limits access to projects to only users with the required
license. Users without the required license cannot open the project or import components
May be required based that are protected by the license.
License-based source and execution on system design,
protection threat model, and risk • License-based execution protection allows execution of the component only on a specific
assessment. controller family, or only on controllers in a specific controller family that contain the
execution license.
• License-based source protection cannot restrict access to safety logic and safety Add-On
Instructions.
For more information, see page 151.
May be required based Configure the following attributes in the Logix Designer application to control access to tag data:
on system design,
Access to tag data threat model, and risk • External Access attribute—Controls how external applications can access tags.
assessment. • Constant attribute—Determines if controller logic can change a tag.

148 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 12 Develop Secure Applications

Table 35 - Requirements for Restricted Data Flow

Required to Meet
Security Component Details
IEC-62443-4-2 SL 1
Use FactoryTalk Policy Manager software to define zones and conduits.
CIP Security Yes For more information, see CIP Security with Rockwell Automation Products Application
Technique, SECURE-AT001.

Table 36 - Requirements for Timely Response to Events

Required to Meet
Security Component Details
IEC-62443-4-2 SL 1
Configure and use the following:
• Audit log accessibility
• Continuous monitoring
FactoryTalk AssetCentre software Yes For more information, see the following:
• Configure System Security Features User Manual, SECURE-UM001.
• System Security Design Guidelines Reference Manual, SECURE-RM001
The controller supports syslog event logging. Choose a syslog collector that supports the
following:
• RFC-5424 syslog protocol
• Ability to receive messages from the controller
Yes, if not using
FactoryTalk IMPORTANT: The controller sends events to a syslog collector through its front Ethernet port.
Syslog collector AssetCentre for The Ethernet port must be connected to the same network as the syslog collector.
logging
To set the IP address of the syslog collector, use FactoryTalk Policy Manager software. For more
information, see CIP Security with Rockwell Automation Products Application Technique,
publication SECURE-AT001.
To view a list of syslog messages and their descriptions, see 1756-RD001.
Enable the change detection feature to monitor program components to determine whether they
Controller change detection Yes change. The change detection feature is not enabled by default.
For more information, see page 153.
May be required based Enable component tracking to monitor configurable program components to determine whether
on system design,
Controller component tracking threat model, and risk they change. Component tracking is not enabled by default.
For more information, see page 155.
assessment
The controller log stores security-related events that can be accessed via FactoryTalk
AssetCentre software.
To help prevent the potential loss of controller logs before FactoryTalk AssetCentre can access
them, follow these guidelines:
Disabled controller log auto-write Yes • Do not use a Message to Self (MSG with a Path of THIS) to auto-write controller logs to the
SD card.
• Do not manually force a write of controller logs to the SD card.
By default, the controller log auto-write is disabled.
For more information, see page 155.

Table 37 - Requirements for Resource Availability

Required to Meet
Security Component Details
IEC-62443-4-2 SL 1
Configure and use the following:
• Asset inventory
FactoryTalk AssetCentre software Yes • Control system backup
• Disaster recovery
For more information, see Configure System Security Features User Manual, SECURE-UM001.
Provide your own UPS with a separate battery unit and redundant power supplies.
UPS Yes Size the UPS so that is correctly supports the system and provides enough power to shut down
servers and workstations properly.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 149

Chapter 12 Develop Secure Applications

Configure User-definable To suspend (shut down) the controller based on conditions in the application, create a user-
defined major fault. With a user-defined major fault:
Major Faults
• The fault type = 4.
• Define a value for the fault code. Choose a value between 990…999. These codes are
reserved for user-defined faults.
• The controller handles the fault the same as other major faults:
• The controller changes to the Program mode and stops running the logic. Outputs are
set to their configured state or value for faulted mode.

To create a user-defined major fault, do the following:

1. Create a fault routine for the program.
2. Configure the program to use the fault routine.
3. Jump to the fault routine.

Create a Fault Routine

To create a fault routine, do the following:
1. In the Controller Organizer, right-click the program and click Add > New Routine.
2. On the New Routine dialog box, in the Name field, type a name for the fault routine.
3. In the Type field, use the default setting, Ladder Diagram.
4. In the In Program or Phase field, select the program or phase where the routine will
reside.
5. In the Assignment field, select Fault.
6. (optional) Select the Open Routine checkbox, to open the ladder logic program
immediately.
7. Click OK.

Configure the Program to Use the Fault Routine

To configure the program to use the fault routine, do the following:
1. In the Controller Organizer, right-click the program and click Properties.
2. On the Properties dialog box, click the Configuration tab.
3. In the Fault field, select the fault routine.
4. Click OK.

Jump to the Fault Routine

In the main routine of the program, enter the following rung, where:
• Fault_Routine_1 is the name of the fault routine for the program.
• 999 is the value for the fault code.

When Tag_1.0 = 1, execution jumps to name_of_fault_routine, a major fault occurs and the
controller enters the faulted mode. Outputs go to the faulted state. The Controller Properties
dialog box, Major Faults tab, displays the code 999.

150 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 12 Develop Secure Applications

License-based Source and Source protection helps prevent logic components from being modified based on a license.
Execution Protection Execution protection adds additional protection to controller logic. Execution protection
makes sure that the right controller has access to execute the protected program. Use this
with source protection to make sure that the right programmer has access to modify the logic.

Each device (controller or computer) requires an activation to access protection features.

Each logic component or program requires a license to be accessed or executed.

FactoryTalk Activations
for Protection

SD Card
9509-CMSDCD4 CMStick
9509-CMSTICKC
9509-CMSTICK8
Activation Activation
+ +
Execution License Source License

To execute protected logic, each controller

requires an SD card with the following: To execute protected logic with the Logix Designer
• FactoryTalk activation for protection application, each computer requires a CmStick
• Execution license with the following:
• FactoryTalk activation for protection
• Source license

Licensing Web Portal

• Source License
• Execution License

To enable license-based protection, you need the following:

• A CmStick that contains a license with Use permission must be present locally on any
USB port on the computer. Use permission cannot be obtained from a network license
server. All other license privileges can be contained on the local CmStick, or provided by
a license server on the network.
• A license that contains the Protect permission, either on a local CmStick or provided by
a license server on the network. When components are locked, unauthorized users
cannot view or edit the component, but authorized users can run the project without a
CmStick.

IMPORTANT Enabling license-based protection can have a significant impact on

download times.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 151

Chapter 12 Develop Secure Applications

Enable License-based Protection

1. Select Tools > Security > Configure Source Protection to open the Source Protection
Configuration dialog box.

2. Insert the CmStick that contains the license that you want to use to help protect the
component into the USB port on the computer. Licenses must contain the Protect
permission to be used to protect components. If a license does not contain the Protect
permission, it does not appear in the list of licenses.
3. In the Source Protection Configuration dialog box, select the component to be protected
and click Protect.
4. In the Protect dialog box, select the license to apply.

152 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 12 Develop Secure Applications

5. Select the Execution Protection type:

- Protect with controller key only. This option is selected by default. With this option
selected, the component, when locked, runs only on a controller in the same family
as the one specified for the project. For example, if you lock a License-based
Protected component for a project on a ControlLogix 5580 controller, the component
can only be executed on another ControlLogix 5580 controller.
- Protect with controller key and specific license. When you select this option, the
component runs only on a controller in the same family as the one specified for the
project and that contains a CmCard with the execution license that you select. If you
select Protect with controller key and specific license, select the execution license
from the list of available licenses.
After components are protected, they can also be locked. When you lock a
component, it helps prevent users from viewing or editing the component, but allows
authorized users to run it.
6. To return to the Source Protection Configuration dialog box, click OK.
To save changes to a component that is protected with License-Based
Source Protection, a CmStick that contains the required license must be
plugged into the computer that runs the Logix Designer application.
Make sure that you save your edits to the project or lock the protected
components before removing the CmStick that contains the required
license. If the license is not present, you could lose your edits to the project.

Configure Change Detection On the Security tab of the controller properties, the Change Detection feature tracks changes
to a controller and generates an audit value when a monitored change occurs.

For more information about change detection, see the Logix 5000 Controller Information and
Status Programming Manual, publication 1756-PM015.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 153

Chapter 12 Develop Secure Applications

Changes to Detect

Click Configure to open the Configure Changes to Detect dialog box. We recommend tracking
the changes that are shown in the following image for a standard ControlLogix 5580 controller.
By default, all event types can cause the audit value to change, resulting in a default value of
0xFFFFFFFFFFFFFFFF.

Audit Value

A unique value that is generated when a project is downloaded to the controller or loaded from
a storage device. This value is updated when a change to an event occurs. Some events
always cause an Audit Value change, while others are selectable in the Configure Changes to
Detect dialog box. When the controller is offline, the Audit Value box is blank.

154 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 12 Develop Secure Applications

Configure Component On the Security tab of the Controller Properties dialog box, component tracking enables you to
determine whether tracked routines, Add-On Instructions, I/O modules, and constant tags have
Tracking been changed. The Logix Designer application creates a tracked state value to indicate the
current state of all components.
For more information about component tracking, see the Logix 5000 Controller Information
and Status Programming Manual, publication 1756-PM015.

Configure Controller Logging The controller log stores various security-related events that can be written to an SD card or
accessed via FactoryTalk Asset Center or a third-party syslog collector. Some of these events
are Logix Designer application request errors, control system events, backup/restore events,
and configuration changes.

For more information on how to access the controller log, see the Logix 5000 Controller
Information and Status Programming Manual, publication 1756-PM015.

For more robust logging and to help prevent rollover, use FactoryTalk AssetCentre or a syslog
collector.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 155

Chapter 12 Develop Secure Applications

Disable the Controller You can disable the controller Ethernet port with the Studio 5000 Logix Designer application,
version 28 or later.
Ethernet Port
IMPORTANT Remember the following:
• Once a port is disabled, you lose any connection that is established
through the controller Ethernet port.
• You cannot disable Ethernet ports if the controller keyswitch is in Run
mode or if the FactoryTalk Security settings deny this editing option.

Ethernet ports return to the default setting after one of these actions occurs 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 - These examples clear the program from a
controller:
- Major nonrecoverable fault occurs.
- Firmware update occurs.

You must reconfigure the settings to disable an Ethernet port after the port returns to its
default settings.

There are two ways to disable the Ethernet port:

• Disable the Ethernet Port on the Port Configuration Tab on page 156
• Disable the Ethernet Port with an MSG Instruction on page 157

Disable the Ethernet Port on the Port Configuration Tab

You can disable the embedded Ethernet port on the controller. This method retains the setting
in the project, so every time you download the project to the controller, the Ethernet port is
disabled.
1. On the Online toolbar, click the Controller Properties button.

2. On the Controller Properties dialog box, click the Port Configuration tab.
3. On the Port Configuration tab, clear the Enable checkbox.

4. On the Port Configuration tab, click Apply.

- If you are online when you make this change, then an Alert dialog box appears. On
the dialog box, click Yes. The change takes effect immediately.
- If you are offline, then the change takes effect when you download the program to
the controller.
5. On the Port Configuration tab, click OK.

156 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 12 Develop Secure Applications

Disable the Ethernet Port with an MSG Instruction

You use a CIP™ Generic MSG with a Path of THIS to execute this option. You cannot use this
MSG instruction to disable the Ethernet port on another controller.
1. Add an MSG instruction to your program.
This message only has to execute once, it does not need to execute with every program
scan.

IMPORTANT You cannot add an MSG instruction to your program if the

controller keyswitch 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 described
in Table 38.

IMPORTANT These values are stored to non-volatile controller memory in such a

way that the MSG instruction is not required to execute each time the
controller powers up.

Table 38 - Disable the Ethernet Port

Field Description
Message Type CIP Generic
Service Type Set Attribute Single
Instance 1
Class f6
Attribute 9
Controller tag of SINT data type.
Source Element In this example, the controller tag is named Port_Configuration.
Source Length 1

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 157

Chapter 12 Develop Secure Applications

3. Configure the Communication tab to use a Path of THIS.

IMPORTANT Messages to THIS must be unconnected messages.

4. Before you enable the MSG instruction, verify 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.

Disable the Controller There are two ways to disable the CIP Security ports on the controller:
CIP Security Ports • Use the Disable CIP Security checkbox in FactoryTalk Linx software, version 6.30.00 or
later
• Use a CIP Generic MSG in Studio 5000 Logix Designer application, version 32 or later

Use the Disable CIP Security Checkbox in FactoryTalk Linx

1. If the Device Configuration menu in FactoryTalk Linx is not enabled, go to the Advanced
Settings dialog box and check the Enable Device Configuration checkbox.

158 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 12 Develop Secure Applications

2. From the Device Configuration menu, click the CIP Security tab, and then check the
Disable CIP Security (Port 2221) checkbox.

Use a CIP Generic MSG Instruction in the Logix Designer Application

IMPORTANT This procedure disables CIP Security ports. To re-enable the ports, use
the controller reset button to perform a Stage 2 reset, which returns
the controller to a factory default state.
See Stage 2 Reset on page 73.

You cannot use this MSG instruction to disable the CIP Security ports on another controller.
The message only has to execute once rather than with every program scan.
1. Create a controller tag with the SINT[9] data type.
In this example, the controller tag is named CIPSEC_DISABLE and must match the
following image.

Before you enable the MSG instruction, consider the following:

- The element CIPSEC_DISABLE[4] is responsible for disabling UDP port 2221 and
EtherNet/IP™ over DTLS, transport class 0/1.
- The element CIPSEC_DISABLE[8] is responsible for disabling TCP port 2221 and
EtherNet/IP over TLS, UCMM, and transport class 3.
- To disable the controller CIP Security ports, the elements CIPSEC_DISABLE[4] and
CIPSEC_DISABLE[8] in the SINT array for the Source Element CIPSEC_DISABLE must
be 0.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 159

Chapter 12 Develop Secure Applications

2. Add an MSG instruction to your program.

IMPORTANT You cannot add an MSG instruction to your program if the

controller keyswitch is in RUN mode or if the FactoryTalk
Security settings deny this editing option.
3. Configure the Configuration tab on the Message Configuration dialog box as described
in Table 39.

Table 39 - Disable the CIP Security Ports

Field Description
Message Type CIP Generic
Service Type Custom
Service Code 4c
Instance 1
Class f5
Attribute 0
Controller tag of SINT[9] data type.
Source Element This is the controller tag that you created in step 1.
Source Length 9

160 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 12 Develop Secure Applications

4. Configure the Communication tab to use a Path of THIS.

IMPORTANT Messages to THIS must be unconnected messages.

5. Cycle power on the controller for the configuration to take effect.

Disable the Controller With the Studio 5000 Logix Designer application, version 32 or later, you can use a CIP Generic
MSG with a Path of THIS to execute this option.
USB Port
1. Add an MSG instruction to your program.
This message only has to execute once, it does not need to execute with every program
scan.

IMPORTANT You cannot add an MSG instruction to your program if the

controller keyswitch 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 described
in Table 40.

IMPORTANT These values are stored to non-volatile controller memory in such a

way that the MSG instruction is not required to execute up each time
the controller powers up.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 161

Chapter 12 Develop Secure Applications

Table 40 - Disable the USB Port

Field Description
Message Type CIP Generic
Service Type Set Attribute Single
Instance 1
Class 33a
Attribute 4
Controller tag of SINT data type.
Source Element In this example, the Source Element is named Port_Configuration.
Source Length 1

3. Configure the Communication tab to use a Path of THIS.

IMPORTANT Messages to THIS must be unconnected messages.

Disable the Controller With the Studio 5000 Logix Designer application, version 32.00.00 or later, you can use a CIP
Generic MSG with a Path of THIS to execute this option.
SD Card
IMPORTANT Remember the following:
• An SD card can only be disabled with a Message to Self.
• Once an SD slot is disabled, you lose all ability to communicate to an SD
card inserted into the slot. This includes any diagnostic information.
1. Add an MSG instruction to your program.
This message only has to execute once, it does not need to execute with every program
scan.

IMPORTANT You cannot add an MSG instruction to your program if the

controller keyswitch is in Run mode, or if the FactoryTalk Security
settings deny this editing option.

162 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 12 Develop Secure Applications

2. Configure the Configuration tab on the Message Configuration dialog box as described
in Table 41.

IMPORTANT These values are stored to non-volatile controller memory in such a

way that the MSG instruction is not required to execute each time the
controller powers up.

Table 41 - Disable the SD Card

Field Description
Message Type CIP Generic
Service Type Set Attribute Single
Instance 1
Class 3a4
Attribute 4
Controller tag of SINT Array.
Source Element In this example, the Source Element is named src_array.
Source Length 1
3. Configure the Communication tab to use a Path of THIS.

IMPORTANT Messages to THIS must be unconnected messages.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 163

Chapter 12 Develop Secure Applications

Disable the Status Display With the Studio 5000 Logix Designer application, version 29 or later, you can disable certain
categories of messages on the four-character status display:
• Disable All Categories of Messages on page 164
• Disable Individual Categories of Messages on page 166

You use a CIP Generic MSG to execute each option.

IMPORTANT You cannot disable these system messages, and they will always
display:
• Power-up messages, such as TEST, PASS, CHRG
• Catalog number message
• Firmware revision message
• Major / Critical failure messages

The 4-character status display returns to the default setting after one of these actions occurs
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 - these examples can clear the program from a
controller:
- Major nonrecoverable fault occurs.
- Firmware update occurs.

You must reconfigure the settings to disable the 4-character status display after it returns to
its default settings.

Disable All Categories of Messages

When you disable all categories of messages, this information no longer shows:
• Project name
• Link status
• Port status
• IP address

Complete these steps.

1. Add an MSG instruction to your program.
2. Configure the Configuration tab on the Message Configuration dialog box as described
in Table 42.

164 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 12 Develop Secure Applications

Table 42 - Disable All Categories of Messages

Field Description
Message Type CIP Generic
Service Type Set Attribute Single
Instance 1
Class 3a5
Attribute 1
Controller tag of SINT data type.
Source Element In this example, the controller tag is named LCD_SINT.
Source Length 1
3. Configure the Communication tab to use a Path of THIS.

IMPORTANT Messages to THIS must be unconnected messages.

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.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 165

Chapter 12 Develop Secure Applications

Disable Individual Categories of Messages

You can disable a subset of the information that scrolls across the controller 4-character
display. You can disable these subsets:
• Project name and link status
• Port status and IP address

Complete these steps.

1. Add an MSG instruction to your program.
This message only has to execute once, it does not need to execute with every program
scan.

IMPORTANT You cannot add an MSG instruction to your program if the

controller keyswitch 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 described
in Table 43.

Table 43 - Disable Individual Categories of Messages

Field Description
Message Type CIP Generic
Service Type Set Attribute Single
Instance 1
Class 3a5
Attribute 2
Controller tag of DINT data type.
Source Element In this example, the controller tag is named Line_MASK.
Source Length 4

166 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 12 Develop Secure Applications

3. Configure the Communication tab to use a Path of THIS.

IMPORTANT Messages to THIS must be unconnected messages.

4. Before you enable the MSG instruction, make sure that the Source Element uses one of
the following tag values that are 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, be sure that
the appropriate bit in the Source Element tag value is 0.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 167

Chapter 12 Develop Secure Applications

Disable Controller Webpages You can disable the controller webpages with the Studio 5000 Logix Designer application,
version 28 or later.

Studio 5000 Logix Designer Application Version 33 or Later

With the Studio 5000 Logix Designer application version 33 or later, controller webpages are
disabled by default.

While using a CIP Generic MSG to disable controller webpages is supported in version 33 or
later, Rockwell Automation recommends these methods to disable the controller webpages:
• If the controller web pages are enabled, disable them by clearing the Enable Controller
Web Pages check box on the Security tab for the controller properties.

IMPORTANT In version 36 or later, the status of the Enable Controller Web

Pages checkbox is saved to and restored from the SD card when
using the save/restore feature.
Previous versions maintain the status of the Enable Controller
Web Pages checkbox that was applied to the controller prior to a
restore from the SD card.
• For CIP Security applications, you can also use FactoryTalk Policy Manager to disable
the webpages (this overrides the Controller Properties checkbox).

Studio 5000 Logix Designer Application Version 32 or Earlier

For Studio 5000 Logix Designer application, version 32 or earlier, you use a CIP Generic MSG to
execute this option.

See the following:

• Use a CIP Generic MSG to Disable the Controller Webpages on page 169
• Use a CIP Generic MSG to Enable the Controller Webpages on page 171

168 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 12 Develop Secure Applications

Controller Web Page Default Settings

These are the default settings for controller webpages:
• Webpages are enabled for controller firmware revision 32 or earlier
• Webpages are disabled for controller firmware revision 33 or later

Controller webpages return to the default setting in these situations:

• A stage 1 reset for all versions of the Studio 5000 Logix Designer application
• A stage 2 reset for all versions of the Studio 5000 Logix Designer application

IMPORTANT When you update the controller firmware to revision 33 or later

without a reset, the controller retains the previous controller
web page configuration (webpages enabled) and does not
automatically change to the default setting for version 33
(disable the webpages).
• You must reconfigure the settings to disable the controller webpages after it returns to
its default settings.

The setting of the controller webpages changes after the following occurs on the controller:
• New project is downloaded - in this case, the settings in the new project take effect.
• When the controller receives a configuration message, it takes the setting from the
configuration message.

Use a CIP Generic MSG to Disable the Controller Webpages

IMPORTANT If you use FactoryTalk Policy Manager to disable the webpages in

a CIP Security application, the CIP generic message-to-self
overrides the FactoryTalk Policy Manager setting.
1. Add an MSG instruction to your program.

IMPORTANT You cannot add an MSG instruction to your program if the

controller keyswitch 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 described
in the Table 44.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 169

Chapter 12 Develop Secure Applications

Table 44 - Disable the Webpages

Field Description
Message Type CIP Generic
Service Type Custom
Service Code 4c
Instance 1
Class f5
Attribute 0
Controller tag of SINT[5] data type.
In this example, the controller tag is named WP_Disable and must match the
following graphic:

Source Element

IMPORTANT: The Source Element tag in your Logix Designer application project
must match the values that are shown in the graphic. If you use values that are
different than the ones shown, the controller webpages are not disabled.
Source Length 5

3. Configure the Communication tab to use a Path of THIS.

IMPORTANT Messages to THIS must be unconnected messages.

170 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 12 Develop Secure Applications

Use a CIP Generic MSG to Enable the Controller Webpages

1. Add an MSG instruction to your program.

IMPORTANT You cannot add an MSG instruction to your program if the

controller keyswitch is in RUN mode, or if the FactoryTalk
Security settings deny this editing option.
2. On the Configuration tab of the Message Configuration dialog box, configure the
message as described in Table 45.

Table 45 - Enable Webpages

Field Description
Message Type CIP Generic
Service Type Custom
Service Code 4c
Instance 1
Class f5
Attribute 0
Controller tag of SINT[5] data type.
In this example, the controller tag is named WP_Enable and must match the
following graphic:

Source Element

IMPORTANT: The Source Element tag in your Logix Designer application project
must match the values that are shown in the graphic. If you use values that are
different than the ones shown, the controller webpages are not enabled.
Source Length 5

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 171

Chapter 12 Develop Secure Applications

3. On the Communication tab, configure a Path to THIS.

IMPORTANT Messages to THIS must be unconnected messages.

Configure Trusted Slots on Trusted slots are optional for 62443-4-2 certification, but can be required for security in
certain implementations.
the Controller
IMPORTANT Trusted slots and CIP Security™ are not compatible on the same device.
If both features are used on the same device, programming through the
controller front Ethernet port is disabled and you are locked out of
programming the controller until you perform a physical reset.

Trusted slots help maintain network segmentation when the controller front Ethernet port is
disabled, such as in redundant control systems. Trusted slots restrict communication paths
through which certain operations are performed on the controller.

The following rules apply to Trusted slots:

• The firmware revisions of the physical modules in the Trusted slots must be compatible
with the firmware revisions and electronic keying options that are configured in the I/O
tree of the project. For compatibility, see Electronic Keying on page 96.
• All communication is Trusted from the module as long as there is not a fault or keying
mismatch.
• If no module is configured in the I/O tree for the respective Trusted slot, then all
communication is Trusted regardless of which module is physically present.

172 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 12 Develop Secure Applications

You configure Trusted slots with these parameters on the Security tab of the Controller
Properties dialog box:
• Restrict Communications Except Through Selected Slots
Select this checkbox to restrict communication through any slot in the chassis that is
not Trusted. Clear the checkbox to allow the controller to communicate without
communication restrictions.

IMPORTANT When this checkbox is selected, communication is restricted

through the front Ethernet port and firmware updates are
restricted to Trusted slots when using AutoFlash, ControlFLASH
Plus, or ControlFLASH™ software. Support is restricted for tools
that require access to restricted data through Class 3
connections.
• Select Slots
Only the slots that are selected under Select Slots are Trusted communication paths for
the controller. The Select Slots grid configures the trusted slots for the controller. When
you select the Restrict Communications Except Through Selected Slots checkbox, you
must click at least one slot that is not occupied by the controller.
If the chassis size for the project is known, the number of slots equal to the chassis size
appear on the dialog box. Otherwise, 17 slots (0…16) appear on the dialog box.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 173

Chapter 12 Develop Secure Applications

Privacy Aspects If configured to do so, the controller can collect the following personal data for the purpose of
logging user activity:
• User name (full name and domain name)
• Workstation name
• FactoryTalk® ID

No more personal data is collected than needed and no personal data is logged by default.

IMPORTANT The general purpose programming capabilities of the controller allow

you to program the controller to collect personal data through
connection to other devices and systems for any purpose. You are
responsible for protecting personal data collected as a result of your
applications.

Data Protection
The following provides methods to protect personal data stored by the controller through
restricted access:
• CIP Security™—To implement CIP Security, see the CIP Security with Rockwell
Automation Products Application Technique, SECURE-AT001.
• FactoryTalk Security—To configure FactoryTalk Security permissions, see the Configure
System Security Features User Manual, SECURE-UM001.

Data Removal
Personal data can be stored by the controller in these locations:
• Internal memory of the controller. The circular buffer of the controller only keeps a
limited amount of data within the controller.
• External memory card, only if logging is configured to write to a text file on the card

IMPORTANT Data that has been retrieved by external software is the responsibility
of the respective software.

You can remove personal data by using these methods:

• Perform a factory reset on the controller to delete data from internal memory.
• Access the text file on the memory card and delete personal data.

IMPORTANT The controller does not have secure reset functionality to make deleted
data nonrecoverable. To address critical security concerns about data
recovery, Rockwell Automation recommends physically destroying a
device when decommissioned.

174 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 13
Develop Motion Applications
The controllers support these motion interfaces:
Applies to these controllers: • Integrated Motion on an EtherNet/IP™ network.
ControlLogix® 5580 • Digital drive interfaces include EtherNet/IP connected drives and Sercos interface
GuardLogix® 5580 connected drives.
• Analog drives support ±10V analog output and can interface with various feedback
devices, such as quadrature encoder, SSI, and LVDT feedback.

For more information, see these publications:

• 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.
• SERCOS and Analog Motion Configuration and Startup User Manual,
publication MOTION-UM001

Motion Overview The controllers support up to 256 axes of integrated motion. The 256 axes can be 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.
Rockwell Automation recommends using the built-in EtherNet/IP port for
high-performance motion applications.
You can associate Integrated Motion axes to any appropriate drive, regardless of whether the
communications path to the drive is via the embedded Ethernet port, or over the 1756
backplane via an Ethernet bridge, such as a 1756-EN2T.

The configuration process varies, depending on your application and drive selection. The
following are general steps to configure a motion application.
1. Create a controller project.
2. Select the type of drive.
Drive Type Requirements
• EtherNet/IP communication module
CIP Motion™
• Digital drive with an EtherNet/IP connection
Select a Sercos interface module:
• 1756-M03SE
Sercos interface
• 1756-M08SE
• 1756-M16SE
Select an analog interface module:
• 1756-HYD02
Analog interface
• 1756-M02AE
• 1756-M02AS
3. Create axis tags as needed.
4. Configure the drive.
5. Create axes as needed.

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 Logix 5000® instructions.
• Each motion instruction works on one or more axes.
• You can program by using motion control instructions in these programming languages:
Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 175
Chapter 13 Develop Motion Applications

- Ladder Diagram (LD)

- Structured Text (ST)
- Sequential Function Chart (SFC)
• Each motion instruction needs a motion control tag. The tag uses a
MOTION_INSTRUCTION data type and stores the information status of the instruction.

For more information, see the Logix 5000 Controller Motion Instructions Reference Manual,
publication MOTION-RM002.

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.

In this example, a simple ladder diagram that homes, jogs, and moves an axis.

If Initialize_Pushbutton = on and the axis = off (My_Axis_X.ServoActionStatus = off) then the MSO instruction turns on the axis.

If Home_Pushbutton = on and the axis hasn’t been homed (My_Axis_X.AxisHomedStatus = off) then the MAH instruction homes the axis.

If Jog_Pushbutton = on and the axis = on (My_Axis_X.ServoActionStatus = on) then the MAJ instruction jogs the axis forward at 8 units/
second.

If Jog_Pushbutton = off then the MAS instruction stops the axis at 100 units/.second². Make sure that Change Decel is Yes. Otherwise, the
axis decelerates at its maximum speed.

176 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 13 Develop Motion Applications

If Move_Command = on and the axis = on (My_Axis_X.ServoActionStatus = on) then the MAM instruction moves the axis. The axis moves to
the position of 10 units at 1 unit/second.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 177

Chapter 13 Develop Motion Applications

Obtain Axis Information You can obtain axis information by using these methods:
• Double-click the axis to open the Axis Properties dialog box.
• Use a Get System Value (GSV) or Set System Value (SSV) instruction to read or change
the configuration at runtime.
• View the QuickView pane to see the state and faults of an axis.
• Use an axis tag for status and faults.
Figure 53 - Obtain Axis Information

Axis Properties Dialog Box

SSV (or GSV) Instruction

Axis Tag

Quick View Pane

178 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 14
Troubleshoot the Controller
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
four-character display to troubleshoot the controller. For more information, see Status
Indicators.

Automatic Diagnostics Automatic Diagnostics is a system-level feature in Logix 5000® controllers that provides
device diagnostics to HMIs and other clients, with zero programming. The diagnostics include
Applies to these controllers: device description conditions and state events.
ControlLogix® 5580
GuardLogix® 5580 Automatic Diagnostics is enabled by default in controllers with firmware revision 33 or later.
You can disable and enable the whole feature while online or offline from the Advanced tab on
the Controller Properties dialog box. You can also disable Automatic Diagnostics for a specific
device in the device's configuration.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 179

Chapter 14 Troubleshoot the Controller

Considerations for The response time and diagnostic information for a loss of communication depends on the
device and configuration settings.
Communication Loss
Diagnostics Type of Connection Device Behavior
Direct connection to a Logix 5000 The device reports communication loss. The device communication
Applies to these controllers: controller loss can be replaced by the diagnostics of a communication adapter.
ControlLogix 5580 Communication adapters that do not have a connection to the
controller do not report communication loss diagnostics.
GuardLogix 5580 No connection to a Logix 5000 controller We recommend that you configure your communications adapters for
a status connection to make sure that they report any communication
loss diagnostic in a timely manner.
The device reports communication loss.
Data connection The device communication loss can be replaced by the diagnostics of
a communication adapter
The device does not report communication loss diagnostics. The
communication adapter reports communication loss diagnostics.
Rack-optimized connection A device with a rack-optimized connection has a reduced set of
diagnostics as compared to a direct connection.

When enabled, the Automatic Diagnostics feature enables:

• Communication loss diagnostics for all devices in the controller I/O configuration
• Device-level automatic diagnostics evaluations for all uninhibited and enabled devices.

You can disable Automatic Diagnostics for a specific device in the device configuration. The
communication loss diagnostic remains active even if the device disables Automatic
Diagnostics. To disable communication loss diagnostic, inhibit the device or disable Automatic
Diagnostics at the controller.

180 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 14 Troubleshoot the Controller

Controller Diagnostics with A warning symbol appears in the controller organizer next to the I/O module under these
conditions:
the Logix Designer
• If there are faults or other conditions in the I/O module
Application • If the connection to the I/O module fails while in run mode
Applies to these controllers:
ControlLogix 5580 If you have set a standard I/O module to fault the controller when the connection fails, then the
controller state indicates Faulted and the controller status displays Controller Fault and is lit
GuardLogix 5580
steady red. I/O Not Responding blinks green.

If you have set a standard I/O module to not fault the controller when the connection fails, or
there is a safety connection fault, then the controller status displays Controller OK and is lit
steady green. I/O Not Responding blinks green.

Controller Status

I/O Module Status

I/O Module Set to Fault Controller I/O Module Set to Not Fault Controller

IMPORTANT Safety Consideration

You cannot configure safety connections to automatically fault the
controller.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 181

Chapter 14 Troubleshoot the Controller

I/O Module Properties The Module Properties dialog box for an I/O device shows fault information:
Applies to these controllers:
• The General view shows a Faulted status.
ControlLogix 5580 • The Connection view shows the module fault.
GuardLogix 5580 • The Module Info view lists the major and minor faults along with the internal state of the
module.
The Module Info view requires successful communication. If communication to the I/O
module is OK, but the module itself is faulted, then the Module Info tab helps to
troubleshoot the fault. If there is a communication fault, then the Connection Tab is
more useful.
If communication is faulted and you try to view the Module Info view, a dialog box
appears that shows the module reported general error status and the fault code.
Figure 54 - I/O Fault Status on General View

182 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 14 Troubleshoot the Controller

Figure 55 - I/O Fault on Connection View

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 183

Chapter 14 Troubleshoot the Controller

Notification in the General module faults are also reported in the Tag Monitor. Diagnostic faults are reported only
in the Tag Monitor. When the Value field is set to 1, a fault is present.
Tag Monitor
Figure 56 - I/O Module Fault
Applies to these controllers:
ControlLogix 5580
GuardLogix 5580

Figure 57 - Safety I/O Connection Fault

184 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 14 Troubleshoot the Controller

Enable Major Fault on To display recent I/O fault information on the Major Faults tab of the controller properties, you
must first select Major Fault on Controller if Connection Fails While in Run Mode on the
Controller Connection view of the I/O Properties dialog box.
Applies to these controllers:
ControlLogix 5580 WARNING: If you select this option, a connection fault on the I/O module can
cause a major fault on the controller. A major fault on the controller causes the
outputs to go to their configured fault state.
Figure 58 - Major Fault on Controller Checkbox

When you are monitoring the configuration properties of a module in the Logix Designer
application and receive a communication fault message, the Major Faults tab for the controller
properties indicates the type of fault under Recent Faults.
Figure 59 - Major Faults in Controller Properties

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 185

Chapter 14 Troubleshoot the Controller

Port Diagnostics When your project is online, you can view the status of the embedded Ethernet port on the
controller.
Applies to these controllers:
ControlLogix 5580 On the Controller Properties dialog box, click the Port Configuration tab and then click the
GuardLogix 5580 Ellipse button in the Port Diagnostics column.
Figure 60 - Ethernet Port Diagnostics

The Port Diagnostics dialog box displays diagnostic details. For descriptions, see Table 46 on
page 187 for parameter descriptions.
Figure 61 - Port Diagnostic Details

186 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 14 Troubleshoot the Controller

Table 46 - Port Diagnostics Parameters - Logix Designer Application

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.
Click Reset Counter to cause the interface and media counter values on the module to set to zero and the values on the dialog box to
Reset Counters update to the current counter values.
The Reset Counter appears dimmed when offline or when online and a communication error occurs.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 187

Chapter 14 Troubleshoot the Controller

Advanced Time Sync The Advanced Time Sync dialog displays information that is related to CIP Sync™ time
synchronization. The information appears only if the project is online and Time
Applies to these controllers: Synchronization is enabled on the Date/Time tab.
ControlLogix 5580
GuardLogix 5580 IMPORTANT Precision Time Protocol (PTP) Software
• Access to software that manages PTP on a control system network mus
be limited to users who are trained on the administration of industrial
control system time including PTP. This includes the PTP update tool that
is supplied by Rockwell Automation, or other publicly available PTP
management software. Incorrect updates while a control system is
running can disrupt the operation of the control system, including major
faults and some devices taken offline.
• When disabling PTP on a controller, to give the controller time to process
the disable, use a two-second delay before setting the WallClockTime
(WCT) in the controller. Otherwise, there is a risk of the Grandmaster
clock overwriting the WCT.
1. On the Date/Time tab, click the Advanced button.

188 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 14 Troubleshoot the Controller

The Advanced Time Sync dialog box opens. See Table 47 on page 190 for parameter
descriptions.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 189

Chapter 14 Troubleshoot the Controller

Table 47 - Advanced Time Sync Parameters

Grandmaster Clock
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
Description
• Serial Number
• Hardware Revision
• Firmware Revision
• Software Revision
• Profile Identity
• Physical Protocol
• Network Protocol
• Port Number
Use the vertical scroll bar to view the data.
Displays the unique identifier for the Grandmaster clock. The format depends on the network protocol. Ethernet network encodes the
Identity MAC address into the identifier.
Class Displays a measure of the quality of the Grandmaster clock. Values are defined from 0…255 with zero as the best clock.
Indicates the expected absolute accuracy of the Grandmaster clock relative to the PTP epoch. The accuracy is specified as a graduated
Accuracy scale that starts at 25 nsec and ends at greater than 10 seconds or unknown. The lower the accuracy value, the better the clock.
Displays the measure of inherent stability properties of the Grandmaster clock. The value is represented in offset scaled log units. The
Variance
lower the variance, the better the clock.
Displays the time source of the Grandmaster clock. The available values are:
• Atomic Clock
• GPS
• Radio
Source • PTP
• NTP
• HAND set
• Other
• Oscillator
Displays the relative priority of the Grandmaster clock to other clocks in the system. The priority values range from 0…255. The highest
Priority 1 / Priority 2 priority is zero. The default value for both settings is 128.
Local Clock
Displays whether the local clock is synchronized or not synchronized with the Grandmaster reference clock. A clock is synchronized if it
Synchronization Status has one port in the slave state and is receiving updates from the master.
Offset to Master Displays the amount of deviation between the local clock and the Grandmaster clock in nanoseconds.
Displays the current state of the backplane. The available values are: Initializing, Faulty, Disabled, Listening, PreMaster, Master, Passive,
Backplane State Uncalibration, Slave, or None.
Displays the state of the Ethernet port. The available values are: Initializing, Faulty, Disabled, Listening, PreMaster, Master, Passive,
Ethernet State Uncalibration, Slave, or None.
Displays the unique identifier for the local clock. The format depends on the network protocol. Ethernet network encodes the MAC
Identity address into the identifier.
Class Displays a measure of the quality of the local clock. Values are defined from 0…255, with zero as the best clock.
Indicates the expected absolute accuracy of the local clock relative to the PTP epoch. The accuracy is specified as a graduated scale
Accuracy that starts at 25 nsec and ends at greater than 10 seconds or unknown. The lower the accuracy value, the better the clock.
Displays the measure of inherent stability properties of the local clock. The value is represented in offset scaled log units. The lower the
Variance variance, the better the clock.
Displays the time source of the local clock. The available values are:
• Atomic Clock
• GPS
• Terrestrial Radio
Source • PTP
• NTP
• HAND set
• Other
• Oscillator

190 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 14 Troubleshoot the Controller

Controller Diagnostics with You can also view diagnostic information in Linx-based software.
Linx-based Software 1. From the Communications menu, select RSWho.

Applies to these controllers:

ControlLogix 5580
GuardLogix 5580

2. Navigate to the Ethernet network.

3. Right-click the controller and choose Module Statistics.

The Module Statistics dialog box shows this information:

• The General tab shows device information, and any faults on the controller.
• The Port Diagnostics tab shows information for the EtherNet/IP™ port.
• The Connection Manager Tab shows information on connection requests.
• The Backplane tab shows ControlLogix® backplane status and diagnostic information.
• The USB tab shows information about the USB port.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 191

Chapter 14 Troubleshoot the Controller

Controller Webpages The controller provides diagnostic webpages that track controller performance, network
performance, and backplane performance. Controller webpages are read-only.
Applies to these controllers:
ControlLogix 5580 IMPORTANT With the Studio 5000 Logix Designer® application version 33 or later,
GuardLogix 5580 controller webpages are disabled by default.
• To enable the controller webpages, select the checkbox on the Security
tab of the controller properties.

• For CIP Security™ applications, you can also use FactoryTalk® Policy
Manager to enable the webpages. FactoryTalk Policy Manager overrides
the Controller Properties checkbox.

To access the diagnostic webpages, follow these steps.

1. Open your web browser.
2. In the Address field, type the IP address of the controller and press Enter.

To access the diagnostic webpages, open the Diagnostics folder in the leftmost navigation bar,
and click the link for each diagnostic webpage you monitor.
• The home page provides device information and controller status.
• The Faults webpage shows major and minor faults on the controller.
• The Diagnostics webpages provide communications and messaging data for the
controller.
• The Advanced diagnostics webpages provide data about the TCP/IP Network and
Precision Time Protocol.

192 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 14 Troubleshoot the Controller

Home Webpage
With Studio 5000 Logix Designer application version 32 or later, the Home webpage also
shows:
• Current 4-character display messages
• Controller status indicators state
• EtherNet/IP™ status indicators state
• Safety signature, safety-locked status, and the safety status of safety controllers

To set the refresh rate of the webpages, input the number of seconds into the Refresh field at
the bottom of the webpage.
Figure 62 - ControlLogix 5580 Home Webpage

Figure 63 - GuardLogix 5580 Home Webpage

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 193

Chapter 14 Troubleshoot the Controller

Faults Webpage
With Studio 5000 Logix Designer application version 32 or later, the Faults webpage shows
major and minor faults on the controller.
ControlLogix 5580 Faults Webpage

GuardLogix 5580 Faults Webpage

194 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Chapter 14 Troubleshoot the Controller

Tasks Webpage
On the Tasks webpage, 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. The table shows the tasks that are running on the control
core (all system tasks are summarized as one task).
This example shows the Tasks webpage from a GuardLogix 5580 controller:

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 195

Chapter 14 Troubleshoot the Controller

Browse Chassis Webpage

Browse Chassis lets you view module information, backplane statistics, and connection
statistics for modules in the local chassis.

196 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Appendix A

Status Indicators

The controller has six status indicators and one four-character scrolling status display. The
1756-L8SP safety partner has the four-character scrolling status display and the OK status
indicator.

Status Display and

Status Indicators
ControlLogix GuardLogix Safety Partner

1 3 1 3 1

2 2 4

Item Description
Four-character scrolling status display
1 You can disable some of these messages. See Disable the Status Display.
2 Controller status indicators. See page 203
3 EtherNet/IP™ status indicators. See page 204
4 Safety partner OK status indicator. See page 204

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 197

Appendix A Status Indicators

General Status Messages The scrolling messages that are described in Table 48 are typically indicated upon powerup,
powerdown, and while the controller is running to show the status of the controller.
Applies to these controllers:
ControlLogix® 5580 Table 48 - Controller General Status Messages
GuardLogix® 5580 Message Interpretation
The controller is Off.
No message is indicated Check the OK indicator to determine if the controller is powered and determine the
state of the controller.
Identity Mismatch—Contact
Tech Support
Missing Vendor Certificate— Beginning with firmware revision 34.011, if a firmware update identifies the controller
Contact Tech Support as not authentic, the hardware is permanently disabled.
Bad Vendor Certificate—
Contact Tech Support
TEST The controller is conducting power-up tests.
CHRG The embedded energy storage circuit is charging.
PASS Power-up tests have been successfully completed.
Saving…Do Not Remove SD The controller is about to save an image to the SD card.
Card
A project is being saved to the SD card. For more status information, you can also
view the SD indicator. See page 203.
Allow the save to complete before:
• Removing the SD card.
SAVE
• Disconnecting the power.
IMPORTANT: Do not remove the SD card while the controller is saving to the SD card.
Allow the save to complete without interruption. If you interrupt the save, data
corruption or loss can occur.
A project is being loaded from the SD card. For more status information, you can also
view the SD indicator. See page 203.
Allow the load to complete before doing the following:
• Removing the SD card
LOAD
• Disconnecting the power
IMPORTANT: Do not remove the SD card while the controller is loading from the SD
card. Allow the load to complete without interruption. If you interrupt the load, data
corruption or loss can occur.
A firmware update is being conducted from the SD card upon powerup. For more
status information, you can also view the SD indicator. See page 203.
UPDT
If you do not want the firmware to update upon powerup, change the Load Image
property of the controller.
Rev XX.xxx The major and minor revision of the firmware of the controller.
1756-L8XX The controller catalog number and series.
The message appears when the EtherNet/IP port does not have a connection. The
Link Down message scrolls continuously during operation.
The message appears when you have disabled the EtherNet/IP port. The message
Link Disabled scrolls continuously during operation.
The message appears when the controller is set for DHCP, but not configured on a
DHCP- 00:00:XX:XX:XX:XX network. The message shows the MAC address of the controller. The message scrolls
continuously during operation if no IP address is set.
Ethernet Port Rate/Duplex The current port rate and duplex state when the EtherNet/IP port has a connection.
State The message scrolls continuously during operation.
The IP address of the controller. Appears on powerup, then scrolls continuously
IP address during operation. If the IP address is not yet set, then the MAC address appears.
The message appears when the controller detects a device on the network that has
Duplicate IP - the same IP address as the controller Ethernet port. The message shows the MAC
00:00:XX:XX:XX:XX address of the device with the duplicate IP address. The message scrolls
continuously during operation.
No project is loaded on the controller.
To load a project, do one of the following:
No Project • Use the Studio 5000 Logix Designer® application to download a 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.
The I/O modules that are associated with the controller are not yet fully powered.
BUSY Allow time for powerup and I/O module self-testing.

198 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Appendix A Status Indicators

Table 48 - Controller General Status Messages (Continued)

Message Interpretation
The security certificate that is associated with the firmware is corrupted.
Corrupt Certificate Go to https://www.rockwellautomation.com/support/ and download the firmware
Received revision you are trying to update to. Replace the firmware revision that you have
previously installed with that posted on the Technical Support website.
The firmware file is corrupted.
Go to https://www.rockwellautomation.com/support/ and download the firmware
Corrupt Image Received revision you are trying to update to. Replace the firmware revision that you have
previously installed with that posted on the Technical Support website.
A failure with the embedded storage circuit has occurred, and the controller is
Backup Energy HW Failure - incapable of saving the program if a powerdown occurs. If you see this message,
Save Project then save your program to the SD card before you remove power, and then replace
the controller.
The embedded storage circuit does not have sufficient energy to enable the
Backup Energy Low - controller to save the program if a powerdown occurs. If you see this message, then
Save Project save your program to the SD card before you remove power, and then replace the
controller.
A firmware update that is initiated via ControlFLASH Plus™, ControlFLASH™ or
Flash in Progress AutoFlash software is in progress. Allow the firmware update to complete without
interruption.
Firmware Installation The controller is using boot firmware (revision 1.xxx) and requires a firmware update.
Required
SD Card Locked An SD card that is locked is installed.
The controller SD card has been unprotected and is available for remote read/write
SD Card Unprotected operations.
Download in Progress An active download is occurring
An active download is being canceled. This may be due to a user-initiated cancel, a
Aborting Download download failure, or connection loss. After completion, the No Project status
message displays.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 199

Appendix A Status Indicators

GuardLogix Status Messages In addition to the general status messages in Table 48, a GuardLogix 5580 controller display
can show these scrolling messages.
Applies to these controllers:
ControlLogix 5580 Table 49 - Safety Controller Status Messages
GuardLogix 5580 Message Interpretation
No Safety Signature Safety Task is in Run mode without a safety signature. Generate a safety signature.
The controller is in Run mode with a safety signature, but is not safety-locked. Safety-
Safety Unlocked lock the controller.
The safety partner is missing or unavailable. Make sure that the safety partner is seated
Safety Partner Missing properly in the slot that is immediately to the right of the safety controller. The
controller displays this message only in a SIL 3/PLe configuration.
The safety partner and primary controller hardware are incompatible. You must use the
Hardware Incompatible 1756-L8SP safety partner with GuardLogix 5580 Controllers. The controller displays this
message only in a SIL 3/PLe configuration.
The safety partner and primary controller firmware revision levels are incompatible.
Firmware Incompatible Update the modules to the correct firmware revision. The controller displays this
message only in a SIL 3/PLe configuration.
The safety logic is invalid. For example, a mismatch occurred between the primary
Safety Task Inoperable controller and the safety partner, a watchdog timeout occurred, or memory is corrupt.

Safety Partner Status The safety partner display can show these scrolling messages.
Messages Table 50 - Safety Partner Status Messages
Applies to these controllers: Message Interpretation
GuardLogix 5580 Standard display text. If there is a major nonrecoverable fault, then the fault code
L8SP scrolls across the display.
A firmware update that is initiated via ControlFLASH Plus, ControlFLASH or
Flash in Progress AutoFlash software is in progress. Allow the firmware update to complete without
interruption.

200 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Appendix A Status Indicators

Fault Messages If the controller displays a fault, these scrolling messages can appear on the status display.
For more information about how to monitor and handle major and minor controller faults, see
Applies to these controllers: the Logix 5000 Controllers Major, Minor, and I/O Faults Programming Manual, publication
ControlLogix 5580 1756-PM014.
GuardLogix 5580
Table 51 - Fault Messages
Message Interpretation
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
Major Fault TXX:CXX message instruction.
Major faults of Type 1, Codes 60, 61, 62 include a unique 9-character
code that you can provide to Rockwell Automation support for
troubleshooting.
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.
I/O Fault Local:X #XXXX message 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.
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 a brief
description of the fault.
I/O Fault ModuleName #XXXX message 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.
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 the Logix Designer application. In
I/O Fault ModuleParent:X #XXXX message addition, the fault code is indicated with a brief description of the fault.
For example, I/O Fault My_CNet:3 #0107 Connection Not Found indicates
that a connection to a module in slot 3 of the chassis with the
communication module named My_CNet is not open.
Take corrective action specific to the type of fault indicated.
I/O faults are present and X = the number of I/O faults present.
If there are multiple I/O faults, the controller indicates the first fault
X I/O Faults 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.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 201

Appendix A Status Indicators

Major Fault Messages The Major Fault TXX:CXX message on the controller scrolling display indicates major faults.
Applies to these controllers:
ControlLogix 5580 This manual links to Logix 5000 Controller and I/O Fault Codes and
GuardLogix 5580 Syslog Messages, 1756-RD001; the file automatically downloads when
you click the link.

For suggested recovery methods for major faults, see the Logix 5000 Major, Minor, and I/O
Fault Codes Programming Manual, publication 1756-PM014.

I/O Fault Codes The controller indicates I/O faults on the status display in one of these formats:
Applies to these controllers:
• I/O Fault Local:X #XXXX message
ControlLogix 5580 • I/O Fault ModuleName #XXXX message
GuardLogix 5580 • 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 the 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.

This manual links to Logix 5000 Controller and I/O Fault Codes and Syslog
Messages, 1756-RD001; the file automatically downloads when you click
the link.

For suggested recovery methods for I/O faults, see the Logix 5000 Major, Minor, and I/O Fault
Codes Programming Manual, publication 1756-PM014.

202 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Appendix A Status Indicators

Controller Status Indicators The status indicators are below the status display on the controller. They indicate the state of
the controller as described in these tables.
Applies to these controllers:
ControlLogix 5580
IMPORTANT Safety Consideration
GuardLogix 5580 Status indicators are not reliable indicators for safety functions. Use
them only for general diagnostics during commissioning or
troubleshooting. Do not attempt to use status indicators to determine
operational status.

RUN Status Indicator

The RUN status indicator shows the current mode of the controller.

To change the controller mode, you can use the keyswitch on the front of the controller or the
Controller Status menu in the Logix Designer application.
Table 52 - RUN Status Indicator
State Description
Off The controller is in Program or Test mode.
Steady green The controller is in Run mode.

FORCE Status Indicator

The Force status indicator shows if I/O forces are enabled on the controller.
Table 53 - FORCE Status Indicator
State Description
Off No tags contain I/O force values, and I/O force values are not enabled.
I/O forces enabled. If any I/O force values exist, they are active.
Steady yellow IMPORTANT: Use caution if you change any force values. In this state, the changes take
effect immediately.
I/O forces exist in the application, but are not active because I/O forces are not enabled.
Flashing yellow IMPORTANT: Use caution if you enable I/O forces. All existing I/O force values take effect
immediately.

SD Status Indicator
The SD status indicator shows if the SD card is in use.
Table 54 - SD Status 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. Allow the
Steady green read/write to complete without interruption. If you interrupt the read/write, data corruption
or loss can occur.
Flashing red The SD card does not have a valid file system.
Steady red The controller does not recognize the SD card.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 203

Appendix A Status Indicators

Controller OK Status Indicator

The OK status indicator shows the state of the controller.
Table 55 - Controller OK Status Indicator
State Description
Off No power is applied to the controller.
One of the following is true:
• It is a new controller, out of the box, and it requires a firmware update. If a firmware update
is required, the status display indicates Firmware Installation Required. To update firmware,
see Update Controller Firmware on page 30.
Flashing red
• It is a previously used or in-use controller and a major fault has occurred. All user tasks,
standard and safety, are stopped.
• For details about major recoverable and nonrecoverable faults, see the Logix 5000 Major,
Minor, and I/O Fault Codes Programming Manual, publication 1756-PM014.
One of the following is true:
• The controller is completing power-up diagnostics.
• The charge of the capacitor in the ESM is being discharged upon powerdown.
Steady red • 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, then full power is applied.
Steady green The controller is operating normally.

Safety Partner OK Status The safety partner has an OK status indicator.

Indicator Table 56 - Safety Partner OK Status Indicator
Applies to these controllers: Sate Description
GuardLogix 5580 Off No power is applied.
Green The safety partner is operating with no faults.
One of the following is true:
• The safety partner is completing power-up diagnostics.
• The charge of the capacitor in the ESM is being discharged upon powerdown.
Red • The safety partner is powered, but is inoperable.
• The safety partner is loading a project to nonvolatile memory.
• The safety partner is experiencing a Hardware Preservation Fault due to a high internal module
temperature. In this condition, only the status indicator receives power. Once the safety
partner cools down to an acceptable temperature, then full power is applied.
Flashing Red The controller is configured for SIL 2 operation but a safety partner is installed.

EtherNet/IP Status The EtherNet/IP status indicators show the state of the EtherNet/IP port and communication
activity.
Indicators
Table 57 - EtherNet/IP Status Indicators
Applies to these controllers:
ControlLogix 5580 Indicator State Description
GuardLogix 5580 • The controller is not configured, or does not have an IP address.
Off
• The port is administratively disabled.
NET 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.
No activity. One of these conditions exists:
• No link exists on the port.
Off • Verify that the RJ45 cables are properly seated in the adapter and connected
LINK devices.
• The port is administratively disabled.
Flashing green Activity exists on the port.

204 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Appendix A Status Indicators

Thermal Monitoring and The controllers can monitor internal module temperatures and act as the temperature
increases.
Thermal Fault Behavior
IMPORTANT If you follow the recommended limits for ambient (inlet) temperature
and apply the required clearances around the chassis, the controller
should not reach the initial warning (minor fault) temperature.
See the 1756 ControlLogix and GuardLogix Controllers Technical Data,
publication 1756-TD001.

All power to the controller is

disabled except to run the
red OK status indicator and Threshold for the controller to declare a `Hardware Preservation
monitor the temperature. Fault’, resetting the module and disabling power.
Power to the
controller is In the disabled power condition, only the OK status indicator is
disabled illuminated, and it is red. The module does not apply power until
it has cooled below the Hardware Preservation Hysteresis limit.
Power does not The module then enters fault mode, records the fault in the
become enabled major fault log, and displays `CPU Temperature Fault’ on the front
Hardware Preservation
when in this range panel.
Hysteresis Limit

Threshold for the controller to declare a `CPU Temperature

Applies to these controllers:
Fault’ major recoverable fault.
ControlLogix 5580 If a fault handler does not clear the fault, then the module
GuardLogix 5580 enters fault mode, records the fault in the major fault log, and
displays `T17:C34 CPU Temperature Fault’ on the front panel.

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 The presence of any temperature warning indicates that you must act to reduce the ambient temperature of the
module.
Instructions for using relay ladder logic to check for a minor fault can be found in the Logix 5000 Controllers Major,
Minor, and I/O Faults Programming Manual, publication 1756-PM014.
A GSV instruction can read the MinorFaultBits attribute of the FaultLog class name. If the Diagnostics minor fault bit
(Bit 17) is set, then a temperature minor fault can be present. Check the Minor Faults tab of the Controller Properties
dialog box in the Logix Designer application to see if the minor fault is a temperature warning.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 205

Appendix A Status Indicators

Notes:

206 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Appendix B
Change Controller Type
Because safety controllers have special requirements and do not support certain standard
features, you must understand the behavior of the system when changing the controller type
from standard to safety or from safety to standard in your controller project.

Changing controller type affects the following:

• Supported features
• Physical configuration of the project (safety partner and safety I/O)
• Controller properties
• Project components such as tasks, programs, routines, and tags
• Safety Add-On Instructions

Change from a Standard to a Upon confirmation of a change from a standard controller to a safety controller project, safety
components are created to meet the minimum requirements for a safety controller:
Safety Controller
• The safety task is created only if the maximum number of downloadable tasks has not
Applies to these controllers: been reached. The safety task is initialized with its default values.
ControlLogix® 5580
GuardLogix® 5580
If your project already contains 32 tasks, and you request a change from a
standard to a safety controller, the project does not convert and stays with
the standard controller.
• Safety components are created (safety task, safety program, and so forth).
• The safety project defaults to safety level SIL 2/PLd.
• A time-based safety network number (SNN) is generated for the local chassis.
• A time-based safety network number (SNN) is also generated for the embedded
EtherNet/IP™ port.
• Standard controller features that are not supported by the safety controller are
removed from the Controller Properties dialog box.

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 207

Appendix B Change Controller Type

Change from a Safety to a Upon confirmation of a change from a safety controller project to a standard controller, some
components are changed and others are deleted, as described below:
Standard Controller
• The safety partner is deleted from the I/O chassis if it existed.
Applies to these controllers: • Safety I/O devices and their tags are deleted.
ControlLogix 5580
• The safety task, programs, and routines are changed to a standard task, programs, and
GuardLogix 5580 routines.
• All safety tags, except safety consume tags, are changed to standard tags. Safety
consume tags are deleted.
• Safety tag mappings are deleted.
• The safety network numbers (SNN) are deleted.
• Safety-lock and safety-unlock passwords are deleted.
• If the standard controller supports features that were not available to the safety
controller, those new features are visible in the Controller Properties dialog box.
Peer safety controllers are not deleted, even if they have no connections
remaining.

• Instructions can still reference modules that have been deleted and can produce
verification errors.
• Consumed tags are deleted when the producing module is deleted.
• As a result of the above changes to the system, safety-specific instructions and safety
I/O tags do not verify.

If the safety controller project contains safety Add-On Instructions, you must remove them
from the project or change their class to standard before changing the controller type.

Change Safety When you change one safety controller type to another, the class of tags, routines, and
programs remain unaltered. Any I/O devices that are no longer compatible with the target
Controller Types controller are deleted.
The representation of the safety partner is updated to appear appropriately for the target
controller.

208 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Appendix C
History of Changes
This appendix contains the new or updated information for each revision of this
publication. These lists include substantive updates only and are not intended to reflect all
changes. Translated versions are not always available for each revision.

Change Log
1756-UM543Q-EN-P, July 2024
Change
Updated information about system compatibility and extreme environment ratings
Added catalog numbers 1756-L81ESXT, 1756-L82ESXT, 1756-L83ESXT, 1756-L84ESXT, 1756-L8SPXT,
1756-L81E-NSEXT, 1756-L82E-NSEXT, 1756-L83E-NSEXT, 1756-L84E-NSEXT, 1756-L85E-NSEXT, 1756-L81EPXT,
1756-L83EPXT, and 1756-L85EPXT
Updated information about conformal coated products
Added recommended SD cards

1756-UM058P-EN-P, November 2023

Change
Added catalog number 1756-L85ES
Revised the Safety Signature section in Chapter 2
Updated controller Safety tab screenshots
Updated Safety I/O Replacement Options section
Added statement about the status of the Enable Controller Web Pages checkbox

1756-UM058O-EN-P, February 2023

Change
Updated the controller minimum requirements.

1756-UM058N-EN-P, November 2022

Change
Moved information about connection reaction time limit to publication 1756-RM012
Added GuardLogix-XT™ catalog numbers
Revised ControlLogix-XT™ and GuardLogix-XT Controllers section
Revised information about the safety signature
Added 1756-EN4TR, 1756-EN4TRK, 1756-EN4TRXT catalog numbers
Added information about secure socket objects
Added introduction and Program Safety Applications section to Chapter 11 and moved other safety topics from
Chapter 11 to publication 1756-RM012
Added information about component tracking

1756-UM058M-EN-P, May 2022

Change
Added publication to the Additional Resources table
Separated ControlLogix® and GuardLogix® K catalog numbers
Updated CIP Security™ content
Added CIP Security to ControlLogix and GuardLogix controller feature tables
Added CIP Security considerations for the number of EtherNet/IP™ nodes

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 209

Appendix C History of Changes

1756-UM058M-EN-P, May 2022 (Continued)

Change
Added K controllers to the description of ControlLogix 5580 controllers that support
IEC-62443-4-2 SL 1 security requirements
Added syslog collector to controller system image
Restructured security checklists
Moved Verification of Security Implementation content to beginning of security checklist
Changed “Studio 5000 Logix Designer® application” checklist item in Table 37 from “yes” to “may
be required” for IEC-62443-4-2 SL 1 security requirements
Added FactoryTalk® Security software to Table 38 and revised details
Revised details of “Firmware update” checklist item in Table 38
Added “Syslog collector” checklist item to Table 41
Changed “Controller log” checklist item in Table 41 o “Disabled controller log auto-write” and
revised details
Added information about matching firmware revisions and Trusted slots
Changed NVS to non-volatile controller memory
Added syslog log collector to Controller Log section
Added method to disable CIP Security™ ports in FactoryTalk® Linx software
Updated general status messages for the controller

1756-UM058L-EN-P, August 2021

Change
Updated link to Logix Controller and I/O Fault Codes
Updated Conformal Coated Products statement
Updated Controller Log section
Added Controller Status messages

1756-UM058K-EN-P, August 2020

Change
Added ControlLogix NSE, ControlLogix-XT, and ControlLogix Process controllers
Updated safety signature definition
Updated behavior of controller status indicators while loading a project from the SD card
Added Simple Network Management Protocol (SNMP).
Added Automatic Diagnostics
Added Considerations for Communication Loss Diagnostics

1756-UM058J-EN-P, October 2019

Change
Added links to access Controller and I/O fault code information from the Knowledgebase Support Center

1756-UM058I-EN-P, March 2019

Change
Moved information on Controller and I/O fault codes to the attached spreadsheets
Added Develop Secure Applications chapter
Updated Controller webpage information

1756-UM058H-EN-P, August 2018

Change
Updated the ControlLogix and ControlLogix-XT™ Chassis and Slots tabl

210 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Appendix C History of Changes

1756-UM058G-EN-P, July 2018

Change
Changed some remaining instances of “safety task signature” to “safety signature” Throughout
Updated the Assign the Safety Network Number (SNN)section
Updated the Copy and Paste a Safety Controller Safety Network Numbersection
Updated the Set the SNN of a Safety I/O Device section

1756-UM058F-EN-P, February 2018

Change
Added GuardLogix® 5580 and Safety information

1756-UM058E-EN-P, December 2016

Change
Updated tables with new maximum number of EtherNet/IP™ nodes supported in Version 30 or later
Added the 1756-IF16IH module to the list of supported HART devices

1756-UM058D-EN-P, August 2016

Change
Added the catalog numbers 1756-L81E, 1756-L82E, 1756-L84E
Added ControlFLASH™ to the Required Software section
Added the section ‘EtherNet/IP Network Communication Rates
Added information on the Ethernet node counter to the section 'Nodes on an EtherNet/IP Network
Added the appendix ‘Security Options’

1756-UM058C-EN-P, November 2015

Change
Updated the diagram for multiple controllers in one chassis

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 211

Appendix C History of Changes

Notes:

212 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Index

Numerics A
10/100/1000 27 add
1756-CN2 local I/O 97
uses 41 remote I/O 101, 103
1756-CN2R Add-On Instructions 22, 208
uses 41 in project 136
1756-CN2RXT API 89
uses 41 application
1756-CNB elements 127
uses 41 networks and 35
1756-CNBR audit value 154
uses 41 AutoFlash
1756-DHRIO 43 update 32
communication via 43 automatic diagnostics 179
uses axes
remote I/O 44 consumed 175
1756-DHRIOXT virtual 175
uses 43, 44 axis
1756-DNB obtain information 178
uses 42
1756-EN2F
uses 38 B
1756-EN2T behavior
uses 38 thermal fault 205
1756-EN2TR
uses 38
1756-EN2TRXT C
uses 38 cache
1756-EN2TSC message options 88
uses 38 changing controllers 208
1756-EN2TXT chassis
uses 38 ControlLogix
1756-EN3TR list 97
uses 38 CIP Safety 26, 126
1756-ENBT CIP Safety I/O
uses 38 adding 111
1756-EWEB node address 111
uses 38 CIP Security ports
1756-IF8H disable 158
uses 46 communication
1756-N2 97 Data Highway Plus 43
1756-N2XT 97 HART 46
1756-RIO network options 20, 21
uses 44 path
1784-SD1 set 56
load from 80 universal remote I/O 44
1784-SD2 configuration owner 119
load from 80 resetting 119, 121
1788-CN2DN configuration signature
uses 42 components 118
1788-CN2FFR copy 118
configure
uses 45
1788-EN2DNR motion 175
configure change detection 153
uses 42
1788-EN2FFR audit value 154
connection
uses 45
DeviceNet
network 42
EtherNet/IP 83
scheduled

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 213

Index

ControlNet 87 D
unscheduled
ControlNet 87 Data Highway Plus 43
consume data-only connection 119
data 87 design
continuous task 129 system 19
control data 86 develop
controler security 146 applications 127
ControlFLASH Plus software 31, 59 motion applications 175
DeviceNet
ControlFLASH software 31, 59
connection use 42
controller network 42
change type 207 DH+ 43
communication path
set 56 diagnostic coverage 26
ControlLogix 5580 diagnostics
communication options 20, 21 with Logix Designer 181
design system with 19 port configuration category 186
firmware 30 time sync category 188
obtain 31 with RSLinx software 191
go online 56 disable the 4-character status display 164
match 58 disable the CIP Security ports 158
monitor disable the controller web pages 168
connections 140
disable the Ethernet port 73, 156
operation mode
change with keyswitch 69 on port configuration tab 156
change with Logix Designer 70 with a MSG instruction 157
program 131 disable the SD card 162
routine 133 disable the USB port 161
serial number 58 DNS addressing 29
serial number mismatch 60, 63 double data rate (DDR) 38
status indicators 203
tags 134 download
tasks 128 effect of controller match 58
upload a project 64 effect of firmware revision match 59
controller log 155 effect of safety status 59
duplicate IP address
controller redundancy 13
detection 28
controller web pages 192 resolution 28
disable 168
ControlLogix
chassis E
list 97
design system 19 electronic keying
I/O about 96
remote 101 elements
selection 95 control application 127
remote I/O safety signature 24
local 97 enable license-based protection 152
slot filler 97 Ethernet 27
ControlLogix 5580 process controller 12 Ethernet port
ControlLogix No Stored Energy (NSE) diagnostics
Controllers 12 Logix Designer 186
ControlLogix system disable 73, 156
minimum requirements 11 EtherNet/IP
ControlLogix-XT connections 83
chassis link speeds 35
list 97 network 35
ControlNet nodes 83
EtherNet/IP network
example 40
module 40 integrated motion 20, 21
network 39 network communication rates 35
scheduled connection number of nodes supported 21
scheduled connection 87 optimize network performance 35
unscheduled connection event task 129
unscheduled connection 87
create a fault routine 150

214 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Index

F IP addresses
duplicate address detection 28
fault
duplicate address resolution 28
cpu temperature 205
hardware preservation 205
recoverable 205 J
fault code
jump to the fault routine 150
use GSV to get 140
fault messages 201
I/O 202 K
features 20
controller keyswitch
communication 20 change controller operation mode 69
programming 20
filler slot
slot filler 97 L
firmware license-based source and execution protection
controller 30 151
obtain 31 enable license-based protection 152
required 31 link speeds
update with AutoFlash, use 32
firmware revision EtherNet/IP 35
load
match 59
from memory card 80
mismatch 60, 63
load a project
firmware upgrade kit 59
on corrupt memory 78
FORCE indicator 203
on power up 78
user initiated 78
local
G I/O
general status messages 198 add 97
GSV remote I/O 97
fault code 140 Logix Designer
monitor change controller operation mode 70
connection 140 Logix Designer application
Add-On Instructions 136
program 131
H routine 133
handshake 86 tags 134
tasks 128
HART. See Highway Addressable Remote
Transducer.
Highway Addressable Remote Transducer 46 M
match project to controller 58
I memory card 77
load from 80
I/O other tasks 82
ControlLogix message
remote 101 cache 88
selection 95 determine if 88
determine data update 108 fault 201
fault codes 202 status display 198
remote 101 messages
I/O configuration
safety status 200
add minimum requirements 11
local I/O 97
remote I/O 101, 103 Monitor Safety I/O Device Status 120
while online 107 motion
indicator 203 about 175
FORCE 203 application 175
OK 204 instructions 175
SD 203 program 175
instruction MVI56-HART
motion 175 uses 46
integrated motion
on the EtherNet/IP network 20, 21
integrated STO mode 17, 18

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 215

Index

N program
in project 131
network
scheduled 132
application and 35 unscheduled 132
controller options 20, 21 programming languages 135
ControlNet 39
Data Highway Plus 43 project
DeviceNet 42 Add-On Instructions 136
DH+. See Data Highway Plus. elements 127
EtherNet/IP 35 go online 56
HART 46 program 131
universal remote I/O 44 routine 133
network address tags 134
tasks 128
DNS addressing 29
upload 64
network address translation (NAT)
protect signature in run mode 50
set the IP address 113
network communication rates
on an EtherNet/IP network 35 R
network status
redundant controllers 13
indicator 123, 124
no stored energy 12 remote
node address 111 I/O 101
remote I/O 43
nodes on an EtherNet/IP network 83
nonvolatile memory add 101, 103
ControlLogix
tab 75 local 97
NSE controllers 12 universal 44
reset
module 119
O ownership 119
obtain reset button 71
axis information 178 safety partner reset 73
firmware 31 stage 1 reset 72
OK indicator 204 stage 2 reset 73
online reset module 119, 121
add RIO. See universal remote I/O
to I/O configuration 107 routine
go 56 in project 133
optimize EtherNet/IP network performance 35 RSLinx software
out-of-box 122 controller diagnostics 191
reset module 119 RSWho
set
path 56
P
password
set 49
S
path safe torque-off
set configurations
communication 56 integrated 17, 18
Performance Level 26 safety network number
periodic task 129 automatic assignment 51
port diagnostics 186 copy 54
definition 26
primary controller
description 23, 51
description 16 managing 51
priority manual assignment 52
task 130 paste 54
probability of failure on demand (PFD) set 115
definition 26 safety signature
probability of failure per hour (PFH) about 24
definition 26 effect on download 59
process controllers 12 effect on upload 59
produce storing a project 76
safety signature elements 24
data 87
produce/consume
data 87

216 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 Index

safety status task

effect on download 59 continuous 129
view 59 event 129
safety tab in project 128
configuration signature 118 periodic 129
module replacement 121 priority 130
view safety status 59 temperature
safety-lock limit 205
effect on download 59 warning 205
effect on upload 59 terminology 26
scheduled TLS 89
program 132 Trusted slots 150
SD card 22
disable 162
SD indicator 203 U
secure applications 145 universal remote I/O 44
configure change detection 153 communicate via 45
audit value 154 unscheduled
controller log 155 program 132
controller security 146 update
disable the 4-character status display 164
disable the CIP Security ports 158 determine frequency 108
disable the controller web pages 168 update firmware
disable the Ethernet port 156 AutoFlash, use 32
on port configuration tab 156 upload
with a MSG instruction 157 effect of controller match 58
disable the SD card 162 effect of safety signature 59
disable theUSB port 161 effect of safety-lock 59
license-based source and execution project 64
protection 151 USB port
enable license-based protection 152 disable 161
user-definable major faults 150 use a fault routine 150
Secure Digital (SD) card 22, 77 user-definable major faults 150
disable 162 create a fault routine 150
load from 80 jump to the fault routine 150
other tasks 82 use a fault routine 150
secure socket object 89
selection
I/O 95 V
serial number 58 view
simple network management protocol 90 safety status 59
slots, Trusted 150
snmp 90
socket interface 89 W
specifications 9, 19, 205 web pages 192
status webpages
fault messages 201 disable 168
indicators 203
messages 200
display 198
monitor
connections 140
store a project 76
system 20

T
tag
consume 87
in project 134
produce 87
tags
naming 120

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 217

Index

218 Rockwell Automation Publication 1756-UM543R-EN-P - March 2025

 ControlLogix 5580 and GuardLogix 5580 Controllers User Manual

Notes:

Rockwell Automation Publication 1756-UM543R-EN-P - March 2025 219

Rockwell Automation Support
Use these resources to access support information.
Find help with how-to videos, FAQs, chat, user forums, Knowledgebase, and product
Technical Support Center rok.auto/support
notification updates.
Local Technical Support Phone Numbers Locate the telephone number for your country. rok.auto/phonesupport
Quickly access and download technical specifications, installation instructions, and user
Technical Documentation Center rok.auto/techdocs
manuals.
Literature Library Find installation instructions, manuals, brochures, and technical data publications. rok.auto/literature
Product Compatibility and Download Center Download firmware, associated files (such as AOP, EDS, and DTM), and access product rok.auto/pcdc
(PCDC) release notes.

Documentation Feedback
Your comments help us serve your documentation needs better. If you have any suggestions on how to improve our content, complete the
form at rok.auto/docfeedback.

Waste Electrical and Electronic Equipment (WEEE)

At the end of life, this equipment should be collected separately from any unsorted municipal waste.

Rockwell Automation maintains current product environmental compliance information on its website at rok.auto/pec.

Allen-Bradley, ArmorBlock, ArmorPOINT, Block I/O, Compact 5000, CompactLogix, ControlBus, ControlFLASH, ControlFLASH Plus, ControlLogix, ControlLogix-XT, Data Highway Plus, DH+,
DriveLogix, expanding human possibility, FactoryTalk, FLEX I/O, FLEX 5000, Guard I/O, GuardLogix, Kinetix, Logix 5000, On-Machine, PanelConnect, PanelView, PLC-2, PLC-3, PLC-5, POINT I/O,
POINT Guard I/O, PowerFlex, QuickView, Rockwell Automation, RSFieldbus, RSLinx, RSNetWorx, RSView, SLC, Stratix, Studio 5000, Studio 5000 Logix Designer, and SynchLink are trademarks of
Rockwell Automation.
CIP, CIP Motion, CIP Safety, CIP Security, CIP Sync, ControlNet, DeviceNet, and EtherNet/IP are trademarks of ODVA, 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, İçerenköy, İstanbul, Tel: +90 (216) 5698400 EEE Yönetmeliğine Uygundur

Publication 1756-UM543R-EN-P - March 2025

Supersedes Publication 1756-UM543Q-EN-P - July 2024 Copyright © 2025 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.