FLEX 5000 Standard and

Safety I/O Modules

Catalog Numbers 5094-IA16, 5094-IA16XT, 5094-IM8, 5094-
IM8XT, 5094-IB16, 5094-IB16XT, 5094-IB16S, 5094-IB16SXT,
5094-IB32, 5094-IB32XT, 5094-OA16, 5094-OA16XT, 5094-OB8,
5094-OB8XT, 5094-OB16, 5094-OB16XT, 5094-OB16S, 5094-
OB16SXT, 5094-OB32, 5094-OB32XT, 5094-OW4IS, 5094-
OW4ISXT, 5094-OW8I, 5094-OW8IXT

User Manual Original Instructions

FLEX 5000 Standard and Safety I/O Modules 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.
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).

2 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Table of Contents
About This Publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Manual Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Feature Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Download Firmware, AOP, EDS, and Other Files . . . . . . . . . . . . . . . . . . . 10
Summary of Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 1
Digital I/O Module Operation in a Controller and Software Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Logix 5000 Control System Controller Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Firmware and Software Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . 15
Secure Access to the System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Types of Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Module Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Multiple Owners of FLEX 5000 Input Modules . . . . . . . . . . . . . . . . . 18
Configuration Changes in an Input Module with Multiple Owners. . . 18
Construct a 5094 FLEX 5000 I/O System. . . . . . . . . . . . . . . . . . . . . . . . . . . 19
FLEX 5000 I/O System Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Configuration via Logix Designer Application . . . . . . . . . . . . . . . . . . . . . 20
Connections for Standard
I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Requested Packet Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Connection Types Available with FLEX 5000 Standard I/O
Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Data Types Available with FLEX 5000 Standard I/O Modules. . . . . 22
Connections for Safety I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
‘Configured By’ Options for Safety I/O Modules . . . . . . . . . . . . . . . . 23
Data Types Available with FLEX 5000 Safety I/O Modules . . . . . . . 24
Requested Packet Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Connection Over an EtherNet/IP Network . . . . . . . . . . . . . . . . . . . . . . . . 25
Input Module Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Trigger Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Output Module Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Listen Only Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Protected Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Considerations Specific to Safety Modules . . . . . . . . . . . . . . . . . . . . . . . . 28
Use with Safety Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Determine Conformity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Obtain Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Safety Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Safety Application Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Safe State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Configuration Signature and Ownership . . . . . . . . . . . . . . . . . . . . . . 32
Reset FLEX 5000 I/O Safety Modules to Out-of-Box State. . . . . . . . 33

Rockwell Automation Publication 5094-UM001E-EN-P - May 2022 3

Table of Contents

Chapter 2
Common Digital I/O Module Input Module Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Features Output Module Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Producer/Consumer Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Module Data Quality Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Software Configurable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Fault and Status Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Module Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Module Inhibiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Electronic Keying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Chapter 3
Input Module Features Data Transfer at RPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Software Configurable Input Filters and Delays. . . . . . . . . . . . . . . . . . . . 41
Field Power Loss Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Short Circuit Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Test Output Recovery After Overload or Short Circuit to
Ground Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Fault and Status Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Chapter 4
Output Module Features Features Specific to All
FLEX 5000 Output Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Output State Change Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Configurable Point-level Output State in Program Mode or
Communications Fault Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Output Behavior Immediately After a Connection Fault . . . . . . . . . 47
Output State Once Connection Is Re-established . . . . . . . . . . . . . . . 47
Forcing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Enable Forces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Disable or Remove a Force. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Check Force Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
GSV Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Data Echo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Field Power Loss Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Fault and Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Features Specific to Only Standard and Safety Solid-state Output
Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
No Load Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
No Load Detection Fault for Safety Module. . . . . . . . . . . . . . . . . . . . . 51
Short-Circuit Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Thermal Shutoff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Features Specific to Only Standard Output Modules. . . . . . . . . . . . . . . . 54
Time-scheduled Output Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Use a MAOC Instruction with a 5094-OB16 or 5094-OB16XT
Standard Output Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Feature Specific to Only Relay Output Modules . . . . . . . . . . . . . . . . . . . . 57
Isolated Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

4 Rockwell Automation Publication 5094-UM001E-EN-P - May 2022

 Table of Contents

Chapter 5
Safety I/O Module Features Safety Input Module Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Safety Application Suitability Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Input Modules in CIP Safety Systems. . . . . . . . . . . . . . . . . . . . . . . . . . 59
Use Test Output with a Safety Input . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Single-channel Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Safety Input Fault Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Safety Input Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Safety Output Module Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Safety Application Suitability Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Output Module in CIP Safety Systems . . . . . . . . . . . . . . . . . . . . . . . . . 65
Safety and Safety Pulse Test Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Single-channel Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Dual-channel Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Surge Capability of Safety Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Safety Output Fault Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Safety Relay Output Module Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Safety Application Suitability Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Safety Relay Output Module in CIP Safety Systems . . . . . . . . . . . . . 70
Safety Relay Output Fault Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Fault and Status Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Chapter 6
Configure the Standard Module Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Create a New Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Discover Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
New Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Edit the Module Configuration Common Categories . . . . . . . . . . . . . . . 77
General Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Connection Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Module Info Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Edit 5094-IA16/5094-IM8 Module Configuration Categories . . . . . . . . . 80
Points Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Edit 5094-IB16/5094-IB32 Module Configuration Categories . . . . . . . . 80
Counters Category. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Points Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Events Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Time Sync Category. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Edit 5094-OA16 Module Configuration Categories. . . . . . . . . . . . . . . . . . 85
Points Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Edit 5094-OB8/5094-OB16/5094-OB32 Module Configuration
Categories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Points Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Edit 5094-OW8I Module Configuration Categories . . . . . . . . . . . . . . . . . 86
Points Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
View the Module Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Rockwell Automation Publication 5094-UM001E-EN-P - May 2022 5

Table of Contents

Chapter 7
Configure and Replace Safety Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Modules Create a New Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
New I/O Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Edit the Module Configuration Common Categories . . . . . . . . . . . . . . . 91
General Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Connection Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Safety Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Module Info Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Edit the 5094-IB16S or
5094-IB16SXT Module Configuration Categories . . . . . . . . . . . . . . . . . . . 96
Input Points Category. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Test Output Points Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Edit the 5094-OB16S or 5094-OB16SXT Module Configuration
Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Edit the 5094-OW4IS or 5094-OW4ISXT Module Configuration
Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
View the Module Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Replace a Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Set the SNN Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Reset to Out-of-Box Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Replace a Module in a Logix 5000 System . . . . . . . . . . . . . . . . . . . . . 101

Appendix A
Troubleshoot Your Module SA Power Indicator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Module Status Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
FLEX 5000 Input Modules Status Indicators. . . . . . . . . . . . . . . . . . . . . . 105
FLEX 5000 Output Modules Status Indicators . . . . . . . . . . . . . . . . . . . . 107
FLEX 5000 Safety Input Modules Status Indicators . . . . . . . . . . . . . . . 110
FLEX 5000 Safety Output Modules Status Indicators . . . . . . . . . . . . . . . 111
FLEX 5000 Safety Relay Output Modules Status Indicators . . . . . . . . . 111
Use the Logix Designer Application for Troubleshooting . . . . . . . . . . . 112
Warning Signal in the I/O Configuration Tree. . . . . . . . . . . . . . . . . 112
Status and Fault Information in Module Properties Categories . 112
Logix Designer Application Tag Editor. . . . . . . . . . . . . . . . . . . . . . . . 116

Appendix B
Module Tag Definitions Tag Name Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Access the Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
5094-IA16 Module Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Configuration Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Input Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
5094-IM8 Module Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Configuration Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Input Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
5094-IB16 Module Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Configuration Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Input Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

6 Rockwell Automation Publication 5094-UM001E-EN-P - May 2022

 Table of Contents

Output Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Event Input Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Event Output Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
5094-IB32 Module Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Configuration Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Input Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Output Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Event Input Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Event Output Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
5094-OA16 Module Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Configuration Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Input Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Output Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
5094-OB8 Module Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Configuration Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Input Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Output Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
5094-OB16 Module Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Configuration Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Input Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Output Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
5094-OB32 Module Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Configuration Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Input Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Output Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
5094-OW8I Module Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Configuration Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Input Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Output Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
5094-IB16S Module Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Input Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Test Output Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Output Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
5094-OB16S Module Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Input Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Output Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
5094-OW4IS Module Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Input Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Output Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Appendix C
Module Diagnostic Assembly Create User-defined Diagnostic Assembly Types . . . . . . . . . . . . . . . . . . 147
5094-IA16, 5094-IA16XT Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
5094-IM8, 5094-IM8XT Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
5094-IB16, 5094-IB16XT Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
5094-IB32, 5094-IB32XT Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
5094-OA16, 5094-OA16XT Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
5094-OB8, 5094-OB8XT Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
5094-OB16, 5094-OB16XT Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Rockwell Automation Publication 5094-UM001E-EN-P - May 2022 7

Table of Contents

5094-OB32, 5094-OB32XT Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

5094-OW8I, 5094-OW8IXT Module. . . . . . . . . . . . . . . . . . . . . . . . . . . 169
5094-IB16S, 5094-IB16SXT Module . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
5094-OB16S, 5094-OB16SXT Module . . . . . . . . . . . . . . . . . . . . . . . . . . 175
5094-OW4IS, 5094-OW4ISXT Module . . . . . . . . . . . . . . . . . . . . . . . . 178
Create Message Type User Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Definitions for Diagnostic Assembly Types . . . . . . . . . . . . . . . . . . . . . . . 182

Appendix D
Application/Wiring Examples for 5094-IB16S and 5094-IB16SXT Module Wiring Diagrams. . . . . . . . . . . 185
Safety 5094-OB16S and 5094-OB16SXT Module Wiring Diagrams . . . . . . . . . 189
5094-OW4IS and 5094-OW4ISXT Relay Module Wiring Diagrams . . 191
I/O Modules
Appendix E
Safety Data for I/O Modules FLEX 5000 I/O Safety Input Module Safety Data . . . . . . . . . . . . . . . . . . 193
FLEX 5000 I/O Safety Output Module Safety Data. . . . . . . . . . . . . . . . . 194
FLEX 5000 I/O Safety Relay Output Module Safety Data . . . . . . . . . . . 194

Appendix F
History of Changes

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

8 Rockwell Automation Publication 5094-UM001E-EN-P - May 2022

 Preface

About This Publication This manual describes how to use FLEX 5000® standard and safety I/O
modules in Logix 5000® control systems.

Make sure that you are familiar with the following:

• Use of a controller in a Logix 5000 control system
• Use of an EtherNet/IP™ network, if the digital I/O modules are installed
in a remote location from the controller that is accessible via the
EtherNet/IP network
• Use of safety systems
• Studio 5000 Logix Designer® environment

Rockwell Automation recognizes that some of the terms that are currently
used in our industry and in this publication are not in alignment with the
movement toward inclusive language in technology. We are proactively
collaborating with industry peers to find alternatives to such terms and
making changes to our products and content. Please excuse the use of such
terms in our content while we implement these changes.

Manual Conventions Within this manual, we simplified product names and added product icons for
your ease of use.

We use standard module to indicate a module that does not have functional
safety capability. We use safety module to indicate a module with functional
safety capability (catalog numbers ending in “S” or “SXT”). Further, we use
FLEX 5000 I/O module to indicate when a concept or task applies to both the
standard and safety digital I/O modules.

Feature Support Throughout this manual, the table at left indicates the I/O modules that
support the feature that is described in that chapter or section.
Applies to these modules:
• If both standard and safety modules support a feature, both module
5094 Standard I/O Modules types are in the table. Any difference in operation between the modules
5094 Safety I/O Modules
for that feature is communicated in the text in the chapter or section.
• If only one type of module, standard or safety, supports a feature, only
that module type appears in the table.

Terminology Table 1 defines terms that are used in this manual.

Table 1 - Terminology
Abbreviation Full Term Definition
1oo2 One out of Two Identifies the programmable electronic controller architecture.
An industrial communication protocol that is used by Logix 5000-based automation
CIP™ Common Industrial Protocol systems on EtherNet/IP, ControlNet®, and DeviceNet® communication networks.
CIP Sync provides the increased control coordination needed for control applications
Common Industrial Protocol Synchronization
CIP Sync™ where absolute time synchronization is vital to achieve real-time synchronization
between distributed intelligent devices and systems.
CIP Safety™ Common Industrial Protocol – Safety Certified SIL-rated version of CIP.
Logical communication channel for communication between nodes. Connections are
— Connection maintained and controlled between masters and slaves.
CL Claim Limit The maximum safety integrity level (SIL) that can be achieved.
DC Diagnostic Coverage The ratio of the detected failure rate to the total failure rate.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 9

Preface

Table 1 - Terminology (Continued)

Abbreviation Full Term Definition
A template that is used in RSNetWorx™ software to display the configuration
parameters, I/O data profile, and connection-type support for a given I/O module.
EDS Electronic Data Sheet RSNetWorx software uses these simple text files to identify products and commission
them on a network.
EN European Norm. The official European Standard.
Used for backup for memory retention at powerdown on Compact GuardLogix® 5380
ESS Energy Storage System controllers. The ESS is inside the controller and cannot be removed.
A ladder logic instruction that retrieves specified controller status information and
GSV Get System Value places it in a destination tag.
The length of time that a device or other product is expected to remain reliable in
MTTF Mean Time To Failure operation.
— Multicast The transmission of information from one sender to multiple receivers.
The translation of an Internet Protocol (IP) address to another IP address on another
NAT Network Address Translation network.
A nonprofit association of vendors that are established for the promotion of CIP
ODVA Open DeviceNet Vendor Association networks.
Computer that is used to interface with and control a Logix-based system via the
PC Personal computer Studio 5000® environment.
PFD Probability of Failure on Demand The average probability of a system to fail to perform its design function on demand.
PFH Average frequency of a dangerous failure per hour The probability of a system to have a dangerous failure occur per hour.
PL Performance Level ISO 13849-1 safety rating.
Periodic test that detects failures in a safety-related system so that, if necessary, the
— Proof test system can be restored to an as-new condition or as close as practical to this condition.
— Safety (devices) Devices or portions of devices that have functional safety capability.
A relative level of risk-reduction provided by a safety function, or to specify a target
SIL Safety Integrity Level level of risk reduction.
SNN Safety Network Number A unique number that identifies a section of a safety network.
SRT Safety Reaction Time A consideration of delays or latencies within the safety system.
SSV Set System Value A ladder logic instruction that sets controller system data.
— Standard (devices) Devices or portions of devices that do not have functional safety capability.
— Unicast The transmission of information from one sender to one receiver.

Download Firmware, AOP, Download firmware, associated files (such as AOP, EDS, and DTM), and access
EDS, and Other Files product release notes from the Product Compatibility and Download Center at
rok.auto/pcdc.

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 trademarks 9
Added inclusive language acknowledgment 9
Updated Feature Support description 9
Added section on short circuit protection for safety modules 42
Updated description of No Load Detection for safety modules 50
Added No Load Detection Fault for Safety Modules section 51, 53
Added safety fault reset tips 63, 69
Added Safety Output NoLoad as option for Safety Output Fault Reset 69
Updated the 5094-OB16S or 5094-OB16SXT input point image 96
Updated SA Power Indicator state and recommended action 104
Updated Figure 30 Point Diagnostics 115
Added Ptxx.NoLoad module tag for 5094-OB8 and 5094-OB16S 135, 144
Added Module Diagnostic Assembly appendix for standard and safety modules 147
Added History of Changes appendix 195

10 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Preface

Additional Resources These documents contain additional information concerning related products
from Rockwell Automation.
Additional Resources
Resource Description
FLEX 5000 Modules Specifications Technical Data, publication 5094-TD001 Provides specifications for FLEX 5000 EtherNet/IP adapters and FLEX 5000 modules.
FLEX 5000 EtherNet/IP Adapters with RJ45 Ports Installation Instructions, Describes how to install and wire the 5094-AENTR, 5094-AENTRXT, 5094-AEN2TR, and
publication 5094-IN001 5094-AEN2TRXT EtherNet/IP adapters.
FLEX 5000 EtherNet/IP Adapters with SFP Support Installation Instructions, Describes how to install and wire the 5094-AENSFPRXT and 5094-AEN2SFPRXT EtherNet/IP
publication 5094-IN002 adapters.
FLEX 5000 Digital 16-point Sinking Input Modules Installation Instructions, Describes how to install and wire the 5094-IB16 and 5094-IB16XT digital input modules.
publication 5094-IN003
FLEX 5000 Digital 16-point Sourcing Output Modules Installation Instructions, Describes how to install and wire the 5094-OB16 and 5094-OB16XT digital output modules.
publication 5094-IN004
FLEX 5000 Digital 8-point Isolated Relay Output Modules Installation Instructions, Describes how to install and wire the 5094-OW8I and 5094-OW8IXT digital output modules.
publication 5094-IN005
FLEX 5000 Analog 8-channel Current/Voltage Input Modules Installation Describes how to install and wire the 5094-IF8 and 5094-IF8XT analog input modules.
Instructions, publication 5094-IN006
FLEX 5000 Analog 8-channel Current/Voltage Output Modules Installation Describes how to install and wire the 5094-OF8 and 5094-OF8XT analog output modules.
Instructions, publication 5094-IN007
FLEX 5000 Analog 8-channel Current/Voltage/RTD/Thermocouple Input Modules Describes how to install and wire the 5094-IY8 and 5094-IY8XT analog input modules.
Installation Instructions, publication 5094-IN008
FLEX 5000 High-speed Counter I/O Modules Installation Instructions, publication Describes how to install and wire the 5094-HSC and 5094-HSCXT high-speed counter
5094-IN009 I/O modules.
FLEX 5000 Terminal Base Assembly Modules Installation Instructions, publication Describes how to install and wire the terminal base assemblies for the FLEX 5000 system.
5094-IN010
FLEX 5000 Interconnect Cables Installation Instructions, publication 5094-IN011 Describes how to install the FLEX 5000 interconnect cable in your FLEX 5000 system.
FLEX 5000 Digital 16-point Sinking Safety Input Modules Installation Instructions, Describes how to install and wire the 5094-IB16S and 5094-IB16SXT digital safety input modules.
publication 5094-IN012
FLEX 5000 Digital 16-point Sourcing Safety Output Modules Installation Describes how to install and wire the 5094-OB16S and 5094-OB16SXT digital safety output
Instructions, publication 5094-IN013 modules.
FLEX 5000 Relay 4-point Safety Output Modules Installation Instructions, Describes how to install and wire the 5094-OW4IS and 5094-OW4ISXT digital relay safety output
publication 5094-IN015 modules.
FLEX 5000 Digital 32-point Sinking Input Modules Installation Instructions, Describes how to install and wire the 5094-IB32 and 5094-IB32XT digital input modules.
publication 5094-IN022
FLEX 5000 Digital 8-point High Current Output Modules Installation Instructions, Describes how to install and wire the 5094-OB8 and 5094-OB8XT digital high current output
publication 5094-IN023 modules.
FLEX 5000 Digital 32-point Sourcing Output Modules Installation Instructions,
publication 5094-IN024 Describes how to install and wire the 5094-OB32 and 5094-OB32XT digital output modules.
FLEX 5000 Digital 16-point 120V AC Input Modules Installation Instructions, Describes how to install and wire the 5094-IA16 and 5094-IA16XT digital AC input modules.
publication 5094-IN025
FLEX 5000 Digital 8-point 240V AC Input Modules Installation Instructions, Describes how to install and wire the 5094-IM8 and 5094-IM8XT digital AC input modules.
publication 5094-IN026
FLEX 5000 Digital 16-point 120/240V AC Output Modules Installation Instructions, Describes how to install and wire the 5094-OA16 and 5094-OA16XT digital AC output modules.
publication 5094-IN027
FLEX 5000 Analog I/O Modules User Manual, publication 5094-UM002 Describes how to configure, operate, and troubleshoot FLEX 5000 analog I/O modules.
FLEX 5000 High-speed Counter I/O Modules User Manual, publication 5094- Describes how to configure, operate, and troubleshoot FLEX 5000 high-speed counter modules.
UM003
CompactLogix 5380 Controllers User Manual, publication 5069-UM001 Describes how to configure, operate, and troubleshoot CompactLogix™ 5380 controllers.
Describes how to configure and use EtherNet/IP devices to communicate on the EtherNet/IP
EtherNet/IP Network Devices User Manual, ENET-UM006 network.
Ethernet Reference Manual, ENET-RM002 Describes basic Ethernet concepts, infrastructure components, and infrastructure features.
Provides guidance on how to conduct security assessments, implement Rockwell Automation
System Security Design Guidelines Reference Manual, SECURE-RM001 products in a secure system, harden the control system, manage user access, and dispose of
equipment.
Assists original equipment manufacturers (OEMs) with construction of panels, to help ensure that
UL Standards Listing for Industrial Control Products, publication CMPNTS-SR002 they conform to the requirements of Underwriters Laboratories.
American Standards, Configurations, and Ratings: Intro to Motor Circuit Design, Provides an overview of American motor circuit design based on methods that are outlined in
publication IA-AT001 the NEC.
Industrial Components Preventive Maintenance, Enclosures, and Contact Ratings
Specifications, publication IC-TD002 Provides a quick reference tool for Allen-Bradley industrial automation controls and assemblies.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 11

Preface

Additional Resources (Continued)

Safety Guidelines for the Application, Installation, and Maintenance of Solid-state Designed to harmonize with NEMA Standards Publication No. ICS 1.1-1987 and provides general
guidelines for the application, installation, and maintenance of solid-state control in the form of
Control, publication SGI-1.1 individual devices or packaged assemblies incorporating solid-state components.
Industrial Automation Wiring and Grounding Guidelines, publication 1770-4.1 Provides general guidelines for installing a Rockwell Automation industrial system.
Product Certifications website, rok.auto/certifications Provides declarations of conformity, certificates, and other certification details.

You can view or download publications at rok.auto/literature.

12 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 1

Digital I/O Module Operation in a Logix 5000

Control System

Topic Page
Controller and Software Compatibility 14
Before You Begin 20
Secure Access to the System 15
Types of Modules 16
Module Overview 16
Ownership 17
Construct a 5094 FLEX 5000 I/O System 19
Configuration via Logix Designer Application 20
Connections for Standard I/O Modules 20
Connections for Safety I/O Modules 22
Connection Over an EtherNet/IP Network 25
Input Module Operation 25
Output Module Operation 26
Listen Only Mode 27
Protected Operations 28
Considerations Specific to Safety Modules 28
Use with Safety Controllers 30

IMPORTANT You cannot use FLEX 5000 I/O modules with all Logix 5000 controllers.
For example, you can use FLEX 5000 I/O modules with CompactLogix 5380
and ControlLogix® 5580 controllers but not with CompactLogix 5370 and
ControlLogix 5570 controllers.
You can use FLEX 5000 I/O modules with Logix 5000 controllers as
remote I/O modules only.
Throughout this publication, the term Logix 5000 controller refers to the
controllers with which you can use FLEX 5000 I/O modules in a given
capacity. The term does not refer to all Logix 5000 controllers.
For the most current information on the Logix 5000 controllers with which
you can use FLEX 5000 I/O modules, see the product description
at rok.auto/flex5000IO.
Logix 5000 controllers use FLEX 5000 standard and safety I/O modules to
control devices in a control system. The controllers access the modules over an
EtherNet/IP network. FLEX 5000 I/O modules use terminal base (TB)
assemblies to connect field-side wiring.

FLEX 5000 I/O modules use the Producer/Consumer network communication

model. This communication is an intelligent data exchange between modules
and other system devices in which each module produces data without first
being polled.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 13

Chapter 1 Digital I/O Module Operation in a Logix 5000 Control System

You use FLEX 5000 I/O modules as remote I/O modules that are accessible via
an EtherNet/IP network. The modules are installed to the right of a FLEX 5000
EtherNet/IP adapter.
Logix 5000 controllers can exchange data with the modules over the network.
Figure 1 shows a standard controller with standard I/O modules. Standard
controllers do not support safety I/O modules.
Figure 1 - FLEX 5000 Standard I/O Modules in a Logix 5000 Control System

X100
FLEX 5000 I/O FLEX 5000 I/O FLEX 5000 I/O
TM TM TM
POWER STATUS POWER STATUS POWER STATUS
FLEX 5000 I/O
TM

EtherNet/IP™ Adapter

X10 STATUS

NET

LINK 1 5094-IB16 DIGITAL 16 INPUT 24 VDC 1 1 TB3 5094-OB16 DIGITAL 16 OUTPUT 24 VDC 1 2 TB3 5094-OW8I RELAY 8 OUTPUT ISOLATED 2 2 TB3W
X1
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 0 1 2 3 4 5 6 7
IP ADDRESS LINK 2
5094-AENTR
POWER
PRP
DLR

5069-L340ERM EtherNet/IP Network 5094-AENTR 5094 Standard I/O

Figure 2 shows a safety controller with standard and safety I/O modules.
Safety controllers support both standard and safety I/O modules.
Figure 2 - FLEX 5000 Safety I/O Modules in a Logix 5000 Control System

SIL2 CPU

5069-L3100ERMS2
X100
FLEX 5000 I/O FLEX 5000 I/O
TM TM
POWER STATUS POWER STATUS
FLEX 5000 I/O
TM
POWER STATUS
FLEX 5000 I/O
TM

EtherNet/IP™ Adapter

X10 STATUS

NET

LINK 1 5094-IB16S SAFETY DIGITAL 16 INPUT 24 VDC 5 5 TB3I 5094-OB16S SAFETY DIGITAL 16 OUTPUT 24 VDC 5 1 TB3I 5094-OW8I RELAY 8 OUTPUT ISOLATED 2 2 TB3W
MOD Power

X1
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 0 1 2 3 4 5 6 7
IP ADDRESS LINK 2
5094-AENTR
POWER
PRP
DLR
SA Power

Compact GuardLogix

5069-L5380 EtherNet/IP Network 5094-AENTR 5094 Safety I/O 5094 Standard I/O

Controller and Software Controller and programming software compatibility requirements apply when
Compatibility you use FLEX 5000 standard and safety I/O modules. A module type and how it
is used affect which requirements apply.

You must also consider Logix Designer application version requirements when
you design your system. For example, you can use FLEX 5000 safety I/O
modules with only version 32 or greater of the Logix Designer application.

14 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 1 Digital I/O Module Operation in a Logix 5000 Control System

Controller Compatibility
Compatibility between Logix 5000 controllers and FLEX 5000 I/O modules
varies based on module type, that is, whether the module is standard or safety.

While you must pair safety I/O with a safety controller, you can also pair
standard I/O with a safety controller. For example, ControlLogix 5580
controllers are compatible with FLEX 5000 standard I/O modules.
GuardLogix 5580 controllers are compatible with FLEX 5000 standard and
safety I/O modules.

Firmware and Software Compatibility

Table 2 describes the module compatibility requirements when you use
FLEX 5000 I/O standard and safety modules with Logix 5000 controllers.

IMPORTANT You must use adapter firmware revision 3.011 or later with standard I/O
firmware revision 2.011 and safety I/O modules.

Table 2 - FLEX 5000 I/O Standard and Safety Modules Controller and Software Compatibility Requirements
Controllers Logix Designer
Modules System Cat. Nos. Application Version
5069-L320ER, 5069-L340ERM 31.00.00 or later
Standard Modules 5069-L306ER, 5069-L306ERM, 5069-L310ER, 5069-L310ERM, 5069-L310ER-NSE,
CompactLogix 5380 31.00.00 or later
5094-IA16, 5094-IA16XT, 5069-L310ERS2, 5069-L320ERM, 5069-L330ER, 5069-L330ERM, 5069-L340ER
5094-IM8, 5094-IM8XT, 5069-L350ERM, 5069-L380ERM, 5069-L3100ERM 31.00.00 or later
5094-IB16, 5094-IB16XT, 5069-L306ERMS2, 5069-L306ERS2, 5069-L310ERS2, 5069-L310ERMS2,
5094-IB32, 5094-IB32XT, 5069-L320ERS2, 5069-L320ERMS2, 5069-L330ERS2, 5069-L330ERMS2,
5094-OA16, 5094-OA16XT Compact GuardLogix 5380 5069-L340ERS2, 5069-L340ERMS2, 5069-L350ERS2, 5069-L350ERMS2, 31.00.00 or later
5094-OB8, 5094-OB8XT, 5069-L380ERS2, 5069-L380ERMS2, 5069-L3100ERS2, 5069-L3100ERMS2
5094-OB16, 5094-OB16XT,
5094-OB32- 5094-OB32XT, 1756-L83E, 1756-L85E 31.00.00 or later
5094-OW8I, 5094-OW8IXT, ControlLogix 5580
1756-L81E, 1756-L82E, 1756-L84E 31.00.00 or later
GuardLogix 5580 1756-L81ES, 1756-L82ES, 1756-L83ES, 1756-L84ES 31.00.00 or later
5069-L306ERMS2, 5069-L306ERS2, 5069-L310ERS2, 5069-L310ERMS2,
Safety Modules 5069-L320ERS2, 5069-L320ERMS2, 5069-L330ERS2, 5069-L330ERMS2,
5094-IB16S, 5094-IB16SXT, Compact GuardLogix 5380 32.00.00 or later
5069-L340ERS2, 5069-L340ERMS2, 5069-L350ERS2, 5069-L350ERMS2,
5094-OB16S, 5094-OB16SXT, 5069-L380ERS2, 5069-L380ERMS2, 5069-L3100ERS2, 5069-L3100ERMS2
5094-OW4IS, 5094-OW4ISXT
GuardLogix 5580 1756-L81ES, 1756-L82ES, 1756-L83ES, 1756-L84ES 32.00.00 or later

Secure Access to the To secure access to the [device] by authorized users only, consider these
System options:
• Password helps protect the source and execution of the control program
• Remove the key from the controller
• Deploy EtherNet/IP devices in accordance with recommended
architectures and concepts. See the Converged Plantwide Ethernet
(CPwE) Design and Implementation Guide, publication ENET-TD001.
• Implement physical barriers, such as locked cabinets

To secure access to the system, consider these options:

• Follow industry best practices to harden your personal computers and
servers, including anti-virus/anti-malware and application whitelisting
solutions.
The recommendations are published at the Rockwell Automation
technical support center in Knowledgebase article Rockwell Automation
Customer Hardening Guidelines, Document ID: PN767. The technical support
center is available at: rok.auto/knowledgebase.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 15

Chapter 1 Digital I/O Module Operation in a Logix 5000 Control System

Develop and deploy backup and disaster recovery policies and

procedures. Test backups on a regular schedule.
• Minimize network exposure for all control system devices and systems,
and confirm that they are not accessible from the Internet.
• Locate control system networks and devices behind firewalls and isolate
them from the business network.
• Subscribe to the Rockwell Automation Security Advisory Index, #54102
available at: rok.auto/knowledgebase, so that you have access to
information about security matters that affect Rockwell Automation
products.

Types of Modules Table 3 describes the types of FLEX 5000 I/O modules.
Table 3 - FLEX 5000 Standard and Safety Digital I/O Modules

Cat. No.(1) Description

5094-IA16, 5094-IA16XT 120V AC 16-point input module
5094-IM8, 5094-IM8XT 240V AC 8-point input module
5094-IB16, 5094-IB16XT 18…32V DC 16-point, sinking input module
5094-IB16S, 5094-IB16SXT 18…32V DC 16-point sinking safety input module
5094-IB32, 5094-IB32XT 18…32V DC 32-point, sinking input module
5094-OA16, 5094-OA16XT 120/240V AC 16-point output module
5094-OB8, 5094-OB8XT 18…32V DC 8-point, high current sourcing output module
5094-OB16, 5094-OB16XT 18…32V DC 16-point, sourcing output module
5094-OB16S, 5094-OB16SXT 18…32V DC 16-point sourcing safety output module
5094-OB32, 5094-OB32XT 18…32V DC 32-point, sourcing output module
5094-OW4IS, 5094-OW4ISXT 5…240V/125V DC 4-point safety relay output module
5094-OW8I, 5094-OW8IXT 5…240V AC /125V DC 8-point, isolated normally open relay output module
(1) XT modules can operate in extreme environments while non-XT modules cannot.

Module Overview Figure 3 shows the parts of an example FLEX 5000 standard I/O module.
Figure 3 - Example FLEX 5000 Standard I/O Module

FRONT VIEW 2 BACK VIEW 3

FLEX 5000 I/O

TM
POWER STATUS

5094-IB16 DIGITAL 16 INPUT 24 VDC 1 1 TB3

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

1 3 4 5

16 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 1 Digital I/O Module Operation in a Logix 5000 Control System

Table 4 - FLEX 5000 Standard I/O Module Parts

Item Description
Status indicators - Displays the status of communication, module health, and input/output devices.
1 Indicators help with troubleshooting anomalies
Release lever - Disengages the latching hooks to allow removal of the module from the terminal base
2 assembly
Module keying - Indicates the keying position the terminal base assembly must be configured to
3 before installing the module
4 Terminal base - Indicates the type of terminal base assembly to use with the module
5 Latching hooks - Securely installs FLEX 5000 modules on the terminal base assembly

Figure 4 shows the parts of an example FLEX 5000 safety I/O module.
Figure 4 - Example FLEX 5000 Safety I/O Module

FRONT VIEW BACK VIEW

2

FLEX 5000 I/O

TM
POWER STATUS

5094-IB16S SAFETY DIGITAL 16 INPUT 24 VDC 5 5 TB3I

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

5
1
3 4

Table 5 - FLEX 5000 Safety I/O Module Parts

Item Description
Status indicators - Displays the status of communication, module health, and input/output devices.
1 Indicators help with troubleshooting anomalies
Release lever - Disengages the latching hooks to allow removal of the module from the terminal base
2 assembly
Module keying - Indicates the keying position the terminal base assembly must be configured to
3 before installing the module
4 Terminal base - Indicates the type of terminal base assembly to use with the module
5 Latching hooks - Securely installs FLEX 5000 modules on the terminal base assembly

Ownership A controller, also known as the owner-controller, must own every I/O module
in a Logix 5000 control system. When the FLEX 5000 I/O modules are used in a
Applies to these modules: Logix 5000 control system, the owner-controller performs the following:
5094 Standard I/O Modules • Stores configuration data for every module that it owns.
5094 Safety I/O Modules • Can reside in a location that differs from the FLEX 5000 I/O modules.
• Sends the I/O module configuration data to define module behavior and
begin operation in the control system.

Each FLEX 5000 I/O module must continuously maintain communication

with its owner-controller during normal operation.

Typically, each I/O module in a FLEX 5000 I/O system has only one
owner-controller. Modules with output tags are limited to one owner-
controller.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 17

Chapter 1 Digital I/O Module Operation in a Logix 5000 Control System

Multiple Owners of FLEX 5000 Input Modules

While typically only one owner-controller is connected to a FLEX 5000
digital input module, multiple Logix 5000 controllers can own FLEX 5000
digital input modules as owner-controllers. In this case, the following
conditions must exist:
• The controllers maintain the same configuration.
• The configuration in each controller uses a Data connection to the
input module.
• The first controller to make a connection to the input module is the only
controller that can change the configuration. Therefore, it ‘owns’ the
module configuration.

IMPORTANT If the controller that owns the module configuration changes the
configuration, the other controllers are not notified of any changes. See
Configuration Changes in an Input Module with Multiple Owners on page 18
for more information.
• The controllers that do maintain but do not ‘own’ the module
configuration are similar to Listen-only controllers. The difference
between the controllers is that the controllers that maintain but do not
own the module configuration can use a Multicast or Unicast connection
over the EtherNet/IP network.
For more information on Listen-only controllers, see Listen Only Mode
on page 27.

Configuration Changes in an You must be careful when changing the configuration data of an input module
Input Module with Multiple in a multiple owner scenario. If the configuration data is changed in owner A
and sent to the module, that configuration data is accepted as the new
Owners configuration for the module. Owner B continues to listen unaware that any
changes have been made in the behavior of the input module, as illustrated.
Figure 5 - Module Configuration Changes with Multiple Owners

X100
FLEX 5000 I/O
TM
POWER STATUS
FLEX 5000 I/O
TM

EtherNet/IP™ Adapter

X10 STATUS

NET

LINK 1 5094-IB16 DIGITAL 16 INPUT 24 VDC 1 1 TB3

X1
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
IP ADDRESS LINK 2
5094-AENTR
POWER
PRP
DLR

Controller A sends new configuration to the module. Controller B is unaware of any configuration changes.

IMPORTANT A message in Logix Designer alerts you to the possibility of a multiple

owner-controller situation and lets you inhibit the connection before
changing the module configuration. When changing the configuration for a
module with multiple owners, we recommend that you inhibit the
connection.

To prevent other owner-controllers from receiving potentially erroneous data,

use these steps when changing the configuration of a module in a multiple
owner scenario while online.

18 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 1 Digital I/O Module Operation in a Logix 5000 Control System

1. For each owner-controller, inhibit the connection to the module either in

the software on the Connection tab or the message dialog box warning
you of the multiple owner condition.
2. Make the appropriate configuration data changes in the software. For
more information about using Logix Designer to change the
configuration, see Chapter 6.
3. Repeat step 1 and step 2 for all owner-controllers, making the exact same
changes in each.
4. Clear the Inhibit checkbox in each owner-controller configuration.

Construct a 5094 FLEX 5000 FLEX 5000 I/O is a small, modular I/O system for distributed applications that
I/O System performs all of the functions of rack-based I/O. The FLEX system contains the
components pictured below.
Adapter I/O Module Terminal Base End Caps

X100
FLEX 5000 I/O
TM

EtherNet/IP™ Adapter

X10 STATUS

NET

LINK 1
X1

IP ADDRESS LINK 2
5094-AENTR
POWER
PRP
DLR

• Adapter - transfers read and write configuration data to and from the
I/O module
• Terminal base - contains a terminal strip to terminate wiring for two- or
three-wire devices
• I/O modules - contains the bus interface and circuitry needed to perform
specific functions related to your application
• End cap - basically a dust cap for the last module in a rack

FLEX 5000 I/O System Power

ATTENTION: Power to this equipment and all connected I/O must be supplied
from a source that is isolated from Mains power via an approved isolating
transformer constructed with basic insulation

FLEX 5000 I/O SA Field-Side Power

• FLEX 5000 I/O modules use terminal base (TB) assemblies to connect
field-side wiring.
• SA field-side power source is connected to the terminal base (TB)
assemblies via SA Power terminals.
• If you are using DC voltage for SA power, you must limit the SA field-side
power source to 10 A, max, at 18…32V DC.
• If you are using AC voltage for SA power, you must limit the SA field-side
power source to 10 A, max, at 120…240V AC.
• Confirm that the external module power supply is adequately sized for
the total SA field-side power current draw in the module.
For example, if the total module power current draw, including current
inrush requirements, is 5 A, you can use a module power supply that is
limited to 5 A.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 19

Chapter 1 Digital I/O Module Operation in a Logix 5000 Control System

• You must use SELV-listed power supplies for module power if there are
functional safety modules that are connected to the FLEX 5000 I/O
system.
• Not all power supplies are certified for use in all applications, for
example, nonhazardous and hazardous environments.

IMPORTANT We recommend that you use separate external power supplies for the
adapter and the adjacent terminal base. This practice can prevent
unintended consequences that can result if you use one supply.

For more information, see the publications that are listed in Additional
Resources on page 11.

Before You Begin Before you use your digital I/O module, you must complete the following:
a. Install a FLEX 5000 EtherNet/IP adapter.
b. Install the FLEX 5000 I/O modules to the right of the adapter.
c. Install an EtherNet/IP network.
d. Install the Logix 5000 controller that accesses the FLEX 5000 I/O
modules via an EtherNet/IP network.

Make sure that you have enough FLEX 5000 terminal base (TB) assemblies to
satisfy your application needs. For more information, see the FLEX 5000
Terminal Base Assembly Modules Installation Instructions,
publication 5094-IN010.

IMPORTANT Terminal bases are not included with your module and are not available for
purchase. A terminal base consists of a mounting base (MB) and removable
terminal block (RTB). You must purchase MBs and RTBs separately and
assemble them together.

For adapter information, see the FLEX 5000 EtherNet/IP Adapters with RJ45
Ports Installation Instructions, publication 5094-IN001, and the FLEX 5000
EtherNet/IP Adapters with SFP Support Installation Instructions, publication
5094-IN002.

Configuration via Logix You must create a Logix Designer application project for the Logix 5000
Designer Application controller that owns the FLEX 5000 standard and safety I/O modules. The
project includes module configuration data for the FLEX 5000 I/O modules.

The Logix Designer application transfers the project to the owner-controller

during the program download. Data is then transferred to the FLEX 5000 I/O
modules over the EtherNet/IP network.

The FLEX 5000 I/O modules can operate immediately after receiving the
configuration data.

Connections for Standard During module configuration, you must define the module. Among the
I/O Modules Module Definition parameters, you must choose a connection type for the
module. A connection is a real-time data transfer link between the owner-
Applies to these modules:
controller and the module that occupies the slot that the configuration
references.
5094 Standard I/O Modules
When you download module configuration to a controller, the controller
attempts to establish a connection to each module in the configuration.

20 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 1 Digital I/O Module Operation in a Logix 5000 Control System

Because part of module configuration includes a slot in the FLEX 5000 I/O
system, the owner-controller checks for the presence of a module there. If a
module is detected, the owner-controller sends the configuration. One of the
following occurs:
• If the configuration is appropriate to the module detected, a connection
is made and operation begins.
• If the configuration is not appropriate to the module detected, the data is
rejected and the Logix Designer application indicates that an error
occurred.
The configuration can be inappropriate for many reasons. For example, a
mismatch in electronic keying that helps prevents normal operation.

The owner-controller monitors its connection with a module. Any break in the
connection, for example, the loss of power to the FLEX 5000 I/O system, causes
a fault. The Logix Designer application monitors the fault status tags to
indicate when a fault occurs on a module.

Requested Packet Interval

The Requested Packet Interval (RPI) is a configurable parameter that defines a

rate at which the owner-controller and the module exchange data. You set the
Applies to these modules: RPI value during initial module configuration and can adjust it as necessary
5094 Standard I/O Modules after module operation has begun. The valid RPI values for FLEX 5000
standard I/O modules are 0.2…750 ms.
5094 Safety I/O Modules

IMPORTANT You can change the RPI while the project is online. If you change the RPI
while the project is online, however, the connection to the module is closed
and reopened in one of the following ways:
• You inhibit the connection to the module, change the RPI value, and
uninhibit the connection.
• You change the RPI value. In this case, the connection is closed and
reopened immediately after you apply the change to the module
configuration.

For more information on guidelines for specifying RPI rates, see the
Logix 5000 Controllers Design Considerations Reference Manual,
publication 1756-RM094.

Connection Types Available with FLEX 5000 Standard I/O Modules

When configuring a FLEX 5000 standard I/O module, you must define the
module. Connection is a required parameter in the Module Definition. The
Applies to these modules: choice determines what data is exchanged between the owner-controller and
5094 Standard I/O Modules the module.

Table 6 describes the connection types that you can use with FLEX 5000 I/O
modules.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 21

Chapter 1 Digital I/O Module Operation in a Logix 5000 Control System

Table 6 - Connections - FLEX 5000 I/O Modules

Description
Connection Type
FLEX 5000 Input Modules FLEX 5000 Output Modules
The module returns the following to the The module returns the following to the
owner-controller: owner-controller:
Data • General fault data • General fault data
• Input data • Output data
The module returns the following to the
owner-controller:
Data with Events(1) • Event fault data N/A
• Event input data
• Event output data
When a Listen Only Data connection is used, another controller owns the module.
A controller that makes a Listen Only Data connection to the module does not write
configuration for the module. It merely listens to the data exchanged with the owner-
controller.
Listen Only Data Use Listen Only Data when the connection type is set to Data. Use Listen Only Data with
Listen Only Data Events when the connection type is set to Data with Events.
with Events(1) IMPORTANT: If a controller uses a Listen Only Data connection, the connection must use the
Multicast option.
For more information on Listen Only connections, see Listen Only Mode on page 27. In this
case, all other connections to the module, for example, the connection to the owner-
controller must also use the Multicast option.
(1) Data with Events and Listen Only Data with Events are available only on the 5094-IB16 digital input module.

Data Types Available with FLEX 5000 Standard I/O Modules

The Module Definition includes a Data parameter that matches the module
type. Digital input modules use Input Data, and digital output modules use
Applies to these modules: Output Data.
5094 Standard I/O Modules
The module type and Connection choice determine the available Input Data or
Output Data choices. For example, you can configure a 5094-IB16 digital input
module to use the Connection choice Data with Events. The resulting Input
Data choices are Data with Events include Data, Packed Data, or Timestamped
Data.

For more information on the Connection and Data parameter choices

available with FLEX 5000 I/O modules, see the Logix Designer application.

Connections for Safety I/O

Modules IMPORTANT This section shows some Logix Designer application screens that are used
when you configure FLEX 5000 I/O safety modules. For a complete
Applies to these modules: description of how to configure the modules, see Chapter 7, Configure and
5094 Safety I/O Modules Replace Safety Modules on page 89.
During module configuration, you must define the module. Among the
Module Definition parameters with FLEX 5000 safety I/O modules, you must
choose how module is configured.

The choice depends on whether the project is downloaded to the controller that
owns the module configuration, that is, the owner-controller, or to a controller
that is listening to input modules in a project.

A real-time data transfer link is established between the controller and the
module that occupies the slot that the configuration references.

When you download module configuration to a controller, the controller

attempts to establish a connection to each module in the configuration.

22 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 1 Digital I/O Module Operation in a Logix 5000 Control System

Because part of module configuration includes a slot number in the remote

FLEX 5000 I/O system, the owner-controller checks for the presence of a
module there. If a module is detected, the owner-controller sends the
configuration. One of the following occurs:
• If the configuration is appropriate to the module detected, a connection
is made and operation begins.
• If the configuration is not appropriate to the module detected, the data is
rejected and the Logix Designer application indicates that an error
occurred.
The configuration can be inappropriate for many reasons. For example,
a mismatch in electronic keying that helps prevents normal operation.

The owner-controller monitors its connection with a module. Any break in the
connection, for example, the loss of power to a remote FLEX 5000 I/O system,
causes a fault. The Logix Designer application monitors the fault status tags to
indicate when a fault occurs on a module.

‘Configured By’ Options for Safety I/O Modules

The ‘Configured By’ choice determines what data is exchanged between the
owner-controller and the module. This is an example Module Definition dialog
box, and available Connection choices, for FLEX 5000 I/O safety modules.

Table 7 describes the connection types that you can use with FLEX 5000 I/O
safety modules.
Table 7 - Configured By Choices - FLEX 5000 Safety I/O Modules
Description
Configured by Choice
FLEX 5000 Safety Input Module FLEX 5000 Safety Output Module
The module exchanges the following with the owner-
The module returns the following to the owner-controller: controller:
This controller • General fault data • General fault data
• Safety input data • Safety input data
• Safety output data
When the External Means option is chosen, another controller owns the module.
External means A controller that chosen this option does not write configuration for the module. It merely listens to the data exchanged
with the owner-controller. That is, it receives Safety input data.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 23

Chapter 1 Digital I/O Module Operation in a Logix 5000 Control System

Data Types Available with FLEX 5000 Safety I/O Modules

The Module Definition includes a Data parameter that matches the module
type. Safety input modules use Input Data, and safety output modules use
Output Data.

The module type and Connection choice determine the available Input Data or
Output Data choices. We recommend that you use Safety Data as the Input
Data choice unless you need to use Safety Packed Data(1) for backward
application compatibility.

For more information on the Connection and Data parameter choices

available with FLEX 5000 I/O modules, see the Logix Designer application.

Requested Packet Interval

The requested packet interval (RPI) is a configurable parameter that defines a
rate at which the owner-controller and the module exchange data. You set the
RPI value during initial module configuration and can adjust it as necessary
after module operation has begun.

The valid RPI values for FLEX 5000 I/O safety modules are 2…500 ms.

IMPORTANT You can change the RPI while the project is online. If you change the RPI
while the project is online, however, the connection to the module is closed
and reopened in one of the following ways:
• You inhibit the connection to the module, change the RPI value, and
uninhibit the connection.
• You change the RPI value. In this case, the connection is closed and
reopened immediately after you apply the change to the module
configuration.

Connection Reaction Time Limit With FLEX 5000 I/O Safety Modules

Setting the RPI on FLEX 5000 I/O safety modules is not as straightforward as
setting it on FLEX 5000 I/O digital modules. With FLEX 5000 I/O safety

(1) Safety Packed Data is not available for the 5094-OW4IS and 5094-OW4ISXT modules.

24 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 1 Digital I/O Module Operation in a Logix 5000 Control System

modules, the Connection Reaction Time Limit configuration affects the RPI
that is used for a module.

The Connection Reaction Time Limit defines the predicted period of safety
packets on the associated connection. If the Max Network Delay exceeds the
Connection Reaction Time Limit, a connection fault occurs.

By default, the Connection Reaction Time Limit is four times the RPI.

Use the default values for Timeout Multiplier (2) and Network Delay Multiplier
(200). The Network Delay Multiplier value is in terms of percentage. Thus, 200
means 200%.

IMPORTANT To determine what is appropriate, analyze each safety channel. The default
Timeout Multiplier of 2 and Network Delay Multiplier of 200 creates a worst-
case input connection reaction time limit of 4 times the RPI, and an output
connection reaction time limit of 3 times the RPI.
Changes to these parameters must be approved only after a thorough
review by a safety administrator.

For more information on specifying RPI rates, see the following:

• FLEX 5000 I/O safety I/O modules - page 24
• Logix 5000 Controllers Design Considerations Reference Manual,
publication 1756-RM094

Connection Over an During module configuration, you must configure the Connection over
EtherNet/IP Network EtherNet/IP parameter. The configuration choice dictates how input data is
broadcast over the network.
The FLEX 5000 I/O modules use one of the following methods to broadcast
data:
• Multicast - Data is sent to all network devices
• Unicast - Data is sent to a specific controller depending on the module
configuration
Unicast is the default setting. We recommend that you use Unicast
because it reduces network bandwidth usage.

Input Module Operation Logix 5000 controllers do not poll the FLEX 5000 input modules for input data.
Instead, the input modules send data at the RPI.

FLEX 5000 input modules reside in a FLEX 5000 I/O system that is accessible
to a Logix 5000 controller over an EtherNet/IP network. A FLEX 5000
EtherNet/IP adapter is the first component in a FLEX 5000 I/O system and
connects the system to the EtherNet/IP network.

FLEX 5000 input modules communicate input data to the FLEX 5000
EtherNet/IP adapter at the defined RPI. The input data consists of point and
status data.

At the RPI, the following events occur.

1. The digital input module scans its points for input data.
2. The module sends the data to the FLEX 5000 EtherNet/IP adapter.
3. The FLEX 5000 EtherNet/IP adapter in the FLEX 5000 I/O system sends
the data over the EtherNet/IP network.
4. One of the following:

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 25

Chapter 1 Digital I/O Module Operation in a Logix 5000 Control System

• If the controller is directly connected to the EtherNet/IP network, it

receives the input data immediately.
• If the controller is connected to the EtherNet/IP network through
another communication module, the module sends the data to its
backplane and the controller receives it.

Trigger Events
IMPORTANT FLEX 5000 I/O safety input modules cannot trigger events.

A FLEX 5000 standard input module can trigger as many as four events. The
module can also trigger an Event task to execute in the owner-controller. The
event task lets you execute a section of logic immediately when an event
occurs.
For more information on event tasks, see the Logix 5000 Controllers Tasks,
Programs, and Routines Programming Manual, publication 1756-PM005.

Output Module Operation The controller sends data to an output module at the RPI or after an
Immediate Output (IOT) instruction is executed.

IMPORTANT Immediate Output instruction is not supported in safety applications.

The RPI defines when the controller sends data to the FLEX 5000 standard
output module and when the output module echoes data. The controller sends
data to an output module only at the RPI.
At the RPI, not only does the controller send data to the output module, but
also the output module sends data to the controller. For example, the output
module sends an indication of the point data quality.

IMPORTANT The RPI for a FLEX 5000 I/O safety output module is the Safety Task period.
Safety output data is sent at the completion of the Safety Task scan.

FLEX 5000 output modules reside in a FLEX 5000 I/O system that is accessible
to a Logix 5000 controller over an EtherNet/IP network. A FLEX 5000
EtherNet/IP adapter is the first component in a FLEX 5000 I/O system and
connects the system to the EtherNet/IP network.
FLEX 5000 output modules receive output data from a controller. The output
module also sends data to the controller.

Controller to Output Module Data Transmission

The controller broadcasts data to its local backplane at one of the following:
• RPI
• An IOT instruction is executed (standard I/O modules only)

IMPORTANT An IOT instruction sends data to all of the output modules in the
system immediately, and resets the RPI timer.

Based on the RPI rate and the length of the controller program scan, the output
module can receive and echo data multiple times during one program scan.

When the RPI is less than the program scan length, the output points can
change values multiple times during a program scan. The owner-controller
does not depend on the program scan to complete to send data.

26 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 1 Digital I/O Module Operation in a Logix 5000 Control System

These events occur when the controller sends data to a FLEX 5000 output
module.
1. Data is sent in one of the following ways:
• If the controller is directly connected to the EtherNet/IP network, it
broadcasts data to the network.
In this case, skip to step 3.

• If the controller is connected to the EtherNet/IP network via a

communication module, the controller transmits the data to the
backplane.
In this case, proceed to step 2.

2. The EtherNet/IP communication module transmits the data to the

EtherNet/IP network.
3. The FLEX 5000 EtherNet/IP adapter in the FLEX 5000 I/O system
receives the data from the network and transmits it to the backplane.
4. The digital output module receives the data from the backplane and
behaves as dictated by its configuration.

Output Module to Controller Data Transmission

When a FLEX 5000 output module receives new data and the requested data
value is present on the RTB, the output module sends, or ‘echoes’, a data value
back to the controller and to the rest of the control system. The data value
corresponds to the signal present at its terminals. This feature is called Data
Echo.

In addition to the Data Echo, the output module sends other data to the
controller at the RPI. For example, the module alerts the controller if a short
circuit condition exists on the module.

The following events occur when a FLEX 5000 output module sends data to the
controller at the RPI.
1. The module sends the data to the backplane.
2. The FLEX 5000 EtherNet/IP adapter in the FLEX 5000 I/O system sends
the data over the EtherNet/IP network.
3. One of the following occurs:
• If the controller is directly connected to the EtherNet/IP network, it
receives the input data from the network without need for a
communication module.
• If the controller is connected to the EtherNet/IP network through
another communication module, the module transmits the data to its
backplane and the controller receives it.

Listen Only Mode Any controller in the system can listen to the data from an I/O module. An
owner-controller, as described in Ownership on page 17, exchanges data with
digital I/O modules.

Other controllers can use a Listen Only connection with the digital I/O module.
In this case, the ‘listening’ controller can only listen to input data or ‘echoed’
output data. The listening controller does not own the module configuration
or exchange other data with the module.

During the I/O configuration process, you can specify a Listen Only
connection. For more information on Connection options, see Module
Definition on page 78.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 27

Chapter 1 Digital I/O Module Operation in a Logix 5000 Control System

IMPORTANT Remember the following:

• The Listen Only Mode applies only to standard I/O modules.
• If a controller uses a Listen Only connection, the connection must use the
Multicast option. In this case, all other connections to the module, for
example, the connection of the owner-controller, must also use the
Multicast option.
• If a controller attempts to use a Listen Only connection to a module but the
owner-controller connection uses the Unicast option, the attempt at a
Listen Only connection fails.
The ‘Listen Only’ controller receives data from the module as long as a
connection between an owner-controller and module is maintained.
• If the connection between an owner-controller and the module is broken,
the module stops sending data and connections to all ‘listening controllers’
are also broken.

Protected Operations To maintain the secure operation of your FLEX 5000 digital I/O module,
operations that can disrupt module operation are restricted based on the
module operating mode. Table 8 describes the restrictions.

Table 8 - Protected Operations on FLEX 5000 Digital I/O Modules

Activity
Current Module Operation Firmware Connection or
Module Reset Connection Configuration Electronic
Update Data Format RPI Change
Request Request Change Keying Change
Request Change
Connection not running Accepted
Connection running Rejected Accepted(1) Accepted(2) Not allowed(3) Accepted(4)
Firmware update is in process Rejected
(1) Only requests for Listen Only connections are accepted.
(2) Configuration change is accepted in the following scenarios:
- Changes are made in the Module Properties dialog box and you click Apply.
- Changes are made in the Configuration tags and you send a Reconfigure Module MSG to the module.
(3) The difference between Rejected and Not allowed is that rejected activities can be attempted in the Logix Designer application but do not take effect. The activities that are not allowed, that is,
attempts to change the Connection or Data Format used, do not occur in the Logix Designer application.
For example, if you attempt to reset a module that is connected to the owner-controller, the Logix Designer application executes the request and alerts you that it was rejected. If you attempt to
change the data format on a module that is connected to an owner-controller, the Logix Designer application does not execute the attempted change. The application only alerts you that the change
is not allowed. In the case, if the change is attempted online, the Module Definition dialog box field that changes the data format is disabled.
(4) The change occurs after the connection is closed and reopened. You can close and reopen the connection in the following ways:
- Change the project while it is offline and download the updated project before going online again.
- Change the project while it is online and click Apply or OK in the Module Properties dialog box. In this case, a dialog box alerts you of the ramifications before the change is made.

Considerations Specific to FLEX 5000 safety I/O modules have additional items to be aware of. Type
Safety Modules approval, certification, and suitability for use in safety applications vary by
catalog number.
Applies to these modules:
These modules can be used with GuardLogix 5580 and Compact GuardLogix
5094 Safety I/O Modules 5380 safety controllers in applications up to SIL 3, PLe, Cat. 4 in single-channel
and dual-channel configurations. The Studio 5000 Logix Designer application,
version 32 or later, is the configuration and programming tool for these
modules.

IMPORTANT TÜV Rheinland has approved GuardLogix 5580 and Compact GuardLogix
5380 controller systems for use in safety-related applications where the
de-energized state is always considered to be the safe state. You must
confirm that the configuration of each channel of the safety I/O module is
set for “Off” under the Output State During Program Mode and
Communications Fault Mode selection to consider those output points as
part of the safety function of any equipment. The safety I/O modules to
which this note applies include 1756-OBV8S, 5094-OB16S, and 5094-OW4IS.
28 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022
 Chapter 1 Digital I/O Module Operation in a Logix 5000 Control System

IMPORTANT Functional safety certification and performance of FLEX 5000 I/O safety
modules requires that the modules operate in conditions at or below the
ambient operating temperature specification.
The Probability of Failure on Demand (PFD) and average frequency of a
dangerous failure per hour (PFH) calculations for these modules are based
on the module operating conditions adhering to the ambient operating
temperature specification.
For more information on the maximum ambient operating temperature
specification for FLEX 5000 I/O safety modules, see the FLEX 5000 Modules
Specifications Technical Data, publication 5094-TD001.

These restrictions apply to the modules:

• Type-approved and certified for use in safety applications up to and
including SIL 3 per IEC 61508
• Suitable for use in safety applications up to and including SIL CL 3 per
IEC 62061
• Suitable for use in safety applications up to and including Performance
Level e (PLe), category 4 per ISO 13849-1

IMPORTANT Requirements are based on the ISO standards that are current at
the time of certification.
For more information on safety application suitability levels with the
FLEX 5000 safety I/O modules, see the following:
• 5094-IB16S - Safety Input Module Features on page 59
• 5094-OB16S - Safety Output Module Features on page 65
• 5094-OW4IS - Safety Relay Output Module Features on page 69

Single-channel or Dual-channel Mode

You can use FLEX 5000 safety I/O modules in single-channel mode or dual-
channel configuration. The configuration affects the safety application
suitability level for a module.

In single-channel mode, the signal status on one channel is evaluated. Based

on that status, safety input data and safety input status can be off or on.

In dual-channel mode, the consistency between the signal status on two

channels is evaluated. Based on the status on both channels, safety input data
and safety input status can be off or on.
You use safety instructions in the safety controller ladder logic with two single
channels, that is, one even and one odd.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 29

Chapter 1 Digital I/O Module Operation in a Logix 5000 Control System

Use with Safety Controllers You can use only the Compact GuardLogix 5380 or GuardLogix 5580 controllers
with the FLEX 5000 safety I/O modules. Restrictions apply with respect to how
Applies to these modules: the controllers can use the I/O modules. The restrictions are described in
5094 Safety I/O Modules Controller and Software Compatibility on page 14.
For more information on which controllers you can use with FLEX 5000 I/O
safety modules, see Table 2 on page 15.

You must use the Logix Designer application, version 32 or later, to configure
the FLEX 5000 I/O safety modules.

Determine Conformity

ATTENTION: Use only appropriate components or devices that comply with the
relevant safety standards and meet the required safety integrity level or
performance level and safety category.
• Conformity to the requirements of the relevant safety standards must be
determined for the entire system by conducting a risk assessment.
• Use devices properly according to the installation environment, performance
rating, and functions of the machine.
• Use devices within their specified ratings.
• We recommend that you consult a certification body regarding assessment of
conformity to the required safety integrity level or performance level.
You are responsible for confirming compliance with the applicable standards for
the entire system. You must read, understand, and fulfill the functional safety
requirements of the standard applicable to your safety application.

Obtain Firmware
Firmware information for safety I/O devices is available at the Rockwell
Automation Product Compatibility and Download Center (PCDC) at rok.auto/
pcdc.

Do not download firmware from non-Rockwell Automation sites.

Safety Function During Firmware Update

The FLEX 5000 I/O safety modules are not safety capable when a firmware
update is in process. You must use other methods to maintain the safety
function during the update process.

Safety Precautions

ATTENTION: Personnel responsible for the application of safety-related

programmable electronic systems (PES) shall be aware of the safety
requirements in the application of the system and shall be trained in the use of
the system.

Observe these precautions for the proper use FLEX 5000 I/O safety modules.

30 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 1 Digital I/O Module Operation in a Logix 5000 Control System

ATTENTION: As serious injury can occur due to loss of required safety function,
follow these safety precautions.
• Never use test outputs as safety outputs. Test outputs are not safety outputs.
• Do not use standard I/O data or explicit message data as safety data.
• Do not use light-emitting diode (LED) status indicators on the I/O modules for
safety operations.
• Do not connect loads beyond the rated value to the safety outputs.
• Apply properly specified voltages to the module. Applying inappropriate voltages
can cause the module to fail to perform its specified function, which could lead to
loss of safety functions or damage to the module.
• Wire the FLEX 5000 I/O safety modules as shown in the FLEX 5000
Technical Data, publication 5094-TD001.
• Set unique network node addresses before connecting devices to the network.
• Perform testing to confirm that device wiring, configuration, and operation is
correct before starting system operation.
ATTENTION: Do not disassemble, repair, or modify the module. This can result in
loss of safety functions.

For more information about safety precautions, see Secure Access to the
System on page 15.

Installing and Replacing Modules

ATTENTION:
• Clear previous configuration data before connecting devices to the network or
connecting input or output power to the device.
• Configure the replacement device properly and confirm that it operates correctly.
• After installation of the module, a safety administrator must confirm the
installation and conduct trial operation and maintenance.

Safety Application Requirements

Safety application requirements include evaluating the following:
• Probability of failure rates (PFD and PFH)
• System reaction time settings
• Functional verification tests that fulfill appropriate safety-level criteria

Creating, recording, and verifying the safety signature is also a required part
of the safety application development process. The safety controller creates the
safety signatures. The safety signature consists of an identification number,
date, and time that uniquely identifies the safety portion of a project. This
number includes all safety logic, data, and safety I/O configuration.

For safety system requirements, including information on the safety network

number (SNN), verifying the safety signature, functional verification test
intervals, system reaction time, and PFD/PFH calculations, see the
GuardLogix 5580 and Compact GuardLogix 5380 Controller Systems Safety
Reference Manual, publication 1756-RM012.

You must read, understand, and fulfill the requirements that are described in
this publication before you operate a safety system that uses FLEX 5000 I/O
safety modules.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 31

Chapter 1 Digital I/O Module Operation in a Logix 5000 Control System

Safe State

ATTENTION:
• The safe state of the outputs is defined as the off state.
• The safe state of the module and its data is defined as the off state.
• Use the FLEX 5000 I/O safety modules only in applications where the off state is
the safe state.

The following are the safe states of the safety modules:

• Safety outputs: OFF
• Safety input data to network: OFF
Figure 6 - Safety Status

Networks Input to Networks OFF

Safety Status

Output OFF Input

The modules are designed for use in applications where the safe state is the off state.

IMPORTANT If you inhibit a safety module from transitioning to a safe state when a fault
occurs because an I/O connection is lost, you accept responsibility for any
consequences that result from your decision to inhibit.
We recommend that you use other means to maintain the safe state if you
inhibit the safety module from transitioning to a safe state.

Configuration Signature and Ownership

Every FLEX 5000 I/O safety module in a system has a configuration signature
and configuration ownership.

Configuration Signature

Each safety device has a unique configuration signature that defines the
module configuration. The configuration signature includes the following:
• ID number
• Date
• Time

The configuration signature is used to verify a module’s configuration.

IMPORTANT The signature can only be considered “verified” (and configuration locked)
after user testing.

32 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 1 Digital I/O Module Operation in a Logix 5000 Control System

Configuration Ownership

The connection between the owner-controller and the FLEX 5000 I/O safety
module is based on the following:
• FLEX 5000 I/O safety module node number
• FLEX 5000 I/O safety module safety network number
• Controller node or slot number

IMPORTANT If the owner-controller is a Compact GuardLogix 5380 controller, the

controller has a node number.
If the owner-controller is a GuardLogix 5580 controller, the
controller has a slot number.
• Controller safety network number
• Path from the controller to the FLEX 5000 I/O safety module
• Configuration signature

If any differences are detected, the connection between the owner-controller

and the FLEX 5000 I/O safety module is lost, the yellow yield icon appears in
the controller project tree.

Different Configuration Owner

When a controller owns the I/O module configuration, other controllers can
listen to the input module. In this case, the module configuration signature in
the Logix Designer project for any listening controller must match the one in
the owner-controller project.
If the safety module is configured for inputs only, you can copy and paste the
configuration signature from one project to the other.
If the safety module has safety outputs, for example, the 5094-OB16S module, the
configuration signature parameter is disabled.

Reset FLEX 5000 I/O Safety Modules to Out-of-Box State

If a FLEX 5000 I/O safety module was used previously, you must clear the
configuration ownership before you can install it on a safety network. That is,
you must return the module configuration to its out-of-box state.

When a FLEX 5000 I/O safety module is in the out-of-box state, its
configuration is not owned by a controller.

The Safety category on the Module Properties dialog box displays the module
Configuration Ownership. The Logix Designer application project must be
online to check.

If the module configuration is owned, the Safety category displays whether the
controller for the opened project owns the module configuration or another
controller owns it.

For information on how to reset the module in the Logix Designer application,
see Reset to Out-of-Box Configuration on page 100.
You cannot reset the module to its out-of-box configuration if either of the
following conditions is true:
• Pending edits to the module properties exist
• Safety signature exists in the controller project

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 33

Chapter 1 Digital I/O Module Operation in a Logix 5000 Control System

Notes:

34 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 2

Common Digital I/O Module Features

Topic Page
Input Module Compatibility 35
Output Module Capability 36
Producer/Consumer Communication 36
Module Data Quality Reporting 36
Software Configurable 37
Fault and Status Reporting 37
Module Firmware 37
Module Inhibiting 38
Electronic Keying 38

This chapter describes module features that are available on all FLEX 5000
digital I/O modules.

Input Module Compatibility FLEX 5000 digital input modules interface to sensing devices and detect
whether they are On or Off.
Applies to these modules:
5094 Standard I/O Modules FLEX 5000 digital input modules convert DC On/Off signals from user devices
to appropriate logic level for use within the processor. Typical input devices
5094 Safety I/O Modules include the following:
• Proximity switches
• Limit switches
• Selector switches
• Float switches
• Push button switches

When you design systems with FLEX 5000 digital input modules, consider
these factors:
• Voltage necessary for your application
• Current leakage
• Whether you need a solid-state device
• Whether your application uses sinking or sourcing wiring

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 35

Chapter 2 Common Digital I/O Module Features

Output Module Capability FLEX 5000 digital output modules can be used to drive various output devices.
Typical output devices compatible with FLEX 5000 digital output modules
Applies to these modules: include these items:
5094 Standard I/O Modules • Motor starters
5094 Safety I/O Modules • Solenoids
• Indicators

Follow these guidelines when designing a system:

• Make sure that the FLEX 5000 digital output modules can supply the
necessary surge and continuous current for proper operation.
• Make sure that the surge and continuous current are not exceeded.
Damage to the module could result.
When you size output loads, refer to the documentation supplied with the
output device for the surge and continuous current necessary to operate the
device.

Producer/Consumer FLEX 5000 digital I/O modules use the Producer/Consumer communication
Communication model to produce data without a controller polling them first. The modules
produce the data and controllers consume it. That is, the owner-controller and
Applies to these modules:
controllers with a Listen Only connection to the module can consume it.
5094 Standard I/O Modules When an input module produces data, the controllers can consume the data
5094 Safety I/O Modules simultaneously. Simultaneous data consumption mitigates the need for one
controller to send the data to other controllers.

Module Data Quality The FLEX 5000 digital I/O modules indicate the quality of point data that is
Reporting returned to the owner-controller. Data quality represents accuracy. Levels of
data quality are reported via module input tags.
Applies to these modules:
The following inputs indicate the level of data quality.
5094 Standard I/O Modules
5094 Safety I/O Modules IMPORTANT Once the condition that causes the Fault or Uncertain tag to change to 1 is
removed, the tag automatically resets to 0. The Logix Designer application
controls the tags. You cannot change the status of the tags.
Keep in mind that in some system configurations, the tag is not reset
immediately after the condition is removed. The tag typically resets after a
small delay.
• I.Ptxx.Fault - This tag indicates that the reported point data is inaccurate
and cannot be trusted for use in your application. Do not use the
reported channel data for control.
If the tag is set to 1, you cannot trust the data reported. You must
troubleshoot the module to correct the cause of the inaccuracy.
Example causes of inaccurate data include the following:
- Field Power Loss condition (output modules)
- No Load condition (output modules)
- Short Circuit condition (output modules)

We recommend that you troubleshoot the module for the typical causes first.
• I.Ptxx.Uncertain - This tag indicates that the reported point data can be
inaccurate but the degree of inaccuracy is unknown. We recommend
that you do not use the reported channel data for control.

36 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 2 Common Digital I/O Module Features

If the tag is set to 1, you know that the data can be inaccurate. You must
troubleshoot the module to discover what degree of inaccuracy exists.
Example causes of uncertain data include the following:
- Module is operating outside its designed operating range
- Data is under manual or override control
We strongly recommend that you monitor the tags in your program to make sure
that the application is operating as expected with accurate channel input data.

Software Configurable You use the Logix Designer application to configure the module, monitor
system operation, and troubleshoot issues. You can also use the Logix Designer
Applies to these modules: application to retrieve the following information from any module in the
5094 Standard I/O Modules system:
5094 Safety I/O Modules
• Serial number
• Firmware revision information
• Product code
• Vendor
• Error and fault information
• Diagnostic information

By minimizing the need for tasks, such as setting hardware switches and
jumpers, the software makes module configuration easier and more reliable.

Fault and Status Reporting The FLEX 5000 digital I/O modules report fault and status data along with
point data. Fault and status data is reported in the following ways:
Applies to these modules:
• Logix Designer application
5094 Standard I/O Modules • Module status indicators
5094 Safety I/O Modules
IMPORTANT Do not use the module status indicators or I/O status indicators on
FLEX 5000 I/O safety modules for safety operations.
For more information on fault reporting, see the individual module feature
chapters and Appendix A, Troubleshoot Your Module on page 103.

Module Firmware The FLEX 5000 digital I/O modules are manufactured with module firmware
installed. If updated module firmware revisions are available in the future, you
Applies to these modules: can update the firmware.
5094 Standard I/O Modules
Updated firmware revisions are made available for various reasons, for
5094 Safety I/O Modules example, to correct an anomaly that existed in previous module firmware
revisions.

Firmware information for I/O devices is available at the Rockwell Automation

Product Compatibility and Download Center (PCDC). The PCDC is available
at: rok.auto/pcdc.
At the PCDC, you can use the module catalog number to check for firmware
updates. If the catalog number is not available, then no updates exist.
Verify that the firmware revision of the FLEX 5000 I/O modules that you use is
correct before commissioning the system.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 37

Chapter 2 Common Digital I/O Module Features

IMPORTANT Only download firmware and access product release notes from the
Rockwell Automation PCDC.
Do not download firmware from non-Rockwell Automation sites.

Module Inhibiting Module inhibiting lets you indefinitely suspend a connection, including Listen
Only connections, between an owner-controller and a digital I/O module
Applies to these modules: without removing the module from the configuration. This process lets you
5094 Standard I/O Modules temporarily disable a module, such as to perform maintenance.
5094 Safety I/O Modules
IMPORTANT You cannot inhibit a connection when the controller is safety-locked or a
safety signature exists for the controller.

You can use module inhibiting in the following ways:

• You write a configuration for an I/O module but inhibit the module to
help prevent it from communicating with the owner-controller. The
owner does not establish a connection and the configuration is not sent
to the module until the connection is uninhibited.
• In your application, a controller already owns a module, has downloaded
the configuration to the module, and is exchanging data over the
connection between the devices.
In this case, you can inhibit the module and the connection to the module
does not exist.

IMPORTANT Whenever you inhibit an output module that is ProgMode enabled, it

enters Program mode, and all outputs change to the state
configured for Program mode.
For example, if an output module is configured so that the state of
the outputs transition to zero during Program mode, whenever that
module is inhibited, outputs transition to zero.

You can use module inhibiting in these instances:

• You want to update a digital I/O module, for example, update the module
firmware revision. Use the following procedure.
a. Inhibit the module.
b. Perform the update.
c. Uninhibit the module.
• You use a program that includes a module that you do not physically
possess yet. You do not want the controller to look for a module that does
not yet exist. In this case, you can inhibit the module in your program
until it physically resides in the proper slot.

To see where to inhibit a FLEX 5000 digital I/O module, see page 100.

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
Applies to these modules: installed device. If keying fails, a fault occurs. These attributes are compared.
5094 Standard I/O Modules
Attribute Description
5094 Safety I/O Modules 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.

38 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 2 Common Digital I/O Module Features

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:
• Same catalog number
• Same or higher Major Revision
Compatible Module • 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.
• Non-XT and XT version as follows:
– You can use an XT version of the module in place of a non-XT module.
– You cannot use a non-XT version of the module in place of an XT module.
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.
IMPORTANT: This option is not available for Safety applications.
Disable Keying ATTENTION: Be extremely cautious when using Disable Keying; if used incorrectly, this option can
lead to personal injury or death, property damage, or economic loss.
We strongly recommend that you do not use Disable Keying.
If you use Disable Keying, you must take full responsibility for understanding whether the device
being used can fulfill the functional requirements of the application.
Indicates that all keying attributes must match to establish communication. If any attribute does
Exact Match not match precisely, communication with the device does not occur.

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

IMPORTANT Changing Electronic Keying parameters online interrupts connections to the

device and any devices that are connected through the device.
Connections from other controllers can also be broken.
If an I/O connection to a device is interrupted, the result can be a loss of
data.
For more detailed information on Electronic Keying, see Electronic Keying in
Logix5000 Control Systems Application Technique, publication LOGIX-AT001.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 39

Chapter 2 Common Digital I/O Module Features

Notes:

40 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 3

Input Module Features

Topic Page
Data Transfer at RPI 41
Software Configurable Input Filters and Delays 41
Field Power Loss Detection 42
Short Circuit Protection 42
Fault and Status Reporting 43

This chapter describes features common to these FLEX 5000 standard and
safety input modules:
• 16-point standard 120V AC input module, catalog number 5094-IA16
• 16-point standard 120V AC input module for extreme environments,
catalog number 5094-IA16XT
• 8-point standard 240V AC input module, catalog number 5094-IM8
• 8-point standard 240V AC input module for extreme environments,
catalog number 5094-IM8XT
• 16-point sinking standard input module, catalog number 5094-IB16
• 16-point sinking standard input module for extreme environments,
catalog number 5094-IB16XT
• 16-point sinking safety input module, catalog number 5094-IB16S
• 16-point sinking safety input module for extreme environments,
catalog number 5094-IB16SXT
• 32-point sinking standard input module, catalog number 5094-IB32
• 32-point sinking standard input module for extreme environments,
catalog number 5094-IB32XT

Data Transfer at RPI FLEX 5000 digital input modules always send data at the RPI, a user-defined
rate at which the module updates the information sent to its owner-controller.
Applies to these modules:
5094 Standard I/O Modules To see where to set the RPI for standard modules, see page 21, and for safety
modules, see page 95.
5094 Safety I/O Modules

Software Configurable Input You can adjust On to Off and Off to On filter times through the Logix Designer
Filters and Delays application for all FLEX 5000 digital input modules. These filters improve
noise immunity within a signal.
Applies to these modules:
A larger filter value affects the length of delay times for signals from these
5094 Standard I/O Modules modules. The filter values are adjustable in the Points category of the Module
5094 Safety I/O Modules Properties window.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 41

Chapter 3 Input Module Features

Ptxx Input Ptxx Event

timestamp timestamp

Input signal

Filter result

Filter delay time

Table 9 - FLEX 5000 Digital Input Module - Input Filter and Delay
Catalog Input Filter Time (Off -> On) Input Filter Time (On -> Off)
5094-IB16, 5094-IB16XT • 0 µs (default) • 0 µs (default)
• 100 µs • 100 µs
• 200 µs • 200 µs
• 500 µs • 500 µs
• 1 ms • 1 ms
5094-IB32, 5094-IB32XT • 2 ms • 2 ms
• 5 ms • 5 ms
• 10 ms • 10 ms
• 20 ms • 20 ms
• 50 ms • 50 ms
• 0 ms (default) • 0 ms (default)
• 1 ms • 1 ms
• 2 ms • 2 ms
5094-IB16S, 5094-IB16SXT • 5 ms • 5 ms
• 10 ms • 10 ms
• 20 ms • 20 ms
• 50 ms • 50 ms
• 10 ms (default)
5094-IA16, 5094-IA16XT • 1 ms (default)
• 20 ms
• 1 ms (default) • 5 ms
5094-IM8, 5094-IM8XT • 2 ms • 10 ms (default)
• 5 ms • 20 ms

To see where to set the input filter values for standard modules, see page 80. To
see where to set the input delay values for safety modules, see page 96.

Field Power Loss Detection The Field Power Loss Detection feature monitors for the loss of power at an
input module point. When field power to the module is lost, a point-level fault
Applies to these modules: is sent to the controller to identify the exact point faulted.
5094 Standard I/O Modules
Field Power Loss Detection has a corresponding tag that can be examined in
5094 Safety I/O Modules the user program if a fault occurs. For information on modules, see Appendix
B, Module Tag Definitions on page 117

To see where to enable or disable field power loss detection, see page 80.

Short Circuit Protection Short Circuit Protection helps prevent damage to a Test Output on a 5094-
IB16S or 5094-IB16SXT module that can result when more current is present at
Applies to these modules: the output than it can handle.
5094 Safety I/O Modules
There are ShortCircuit and Overload tags in Diagnostic assembly.

IMPORTANT The 5094-IB16S and 5094-IB16SXT are the only FLEX 5000 I/O input
modules that support Short Circuit Protection.

42 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 3 Input Module Features

When a short circuit condition is detected, the Test Output turns off,
I.Testxx.ShortCircuit tag and I.Testxx.Fault tag are set to 1.

To correct the issue, see Test Output Recovery After Overload or Short Circuit
to Ground Condition on page 43.

When a short circuit condition is removed, the Test Output restarts in its
commanded state, I.Testxx.ShortCircuit tag and I.Testxx.Fault tag are reset
to 0.
For more information on the maximum current that you can apply to a Test
Output, see Input Modules in CIP Safety Systems on page 59 or the FLEX 5000
Modules Specifications Technical Data, publication 5094-TD001.

Test Output Recovery After Overload or Short Circuit to

Ground Condition
Table 10 describes the Test Output recovery after overload or short circuit to
ground conditions occur.
Table 10 - Test Output Recover – FLEX 5000 I/O Safety Input Modules
Cause of Fault Correction Recover Time
Overload condition Remove the load from the Test Output point. After the Overload or Short Circuit
fault occurs, the Test Output
channel holds fault indications for
Short Circuit to ground condition Correct the cause of the short circuit condition. 10 seconds until it checks if the
fieldfault is removed.

Other types of Test Output faults are non-recoverable. You must cycle power to the
module.

IMPORTANT The TO channel may report Short Circuit fault when the load is hot plugged
during run mode.

Fault and Status Reporting The digital input modules multicast fault and status data with point data to the
owner and listening controllers. The data is returned via modules that you can
Applies to these modules: monitor in your Logix Designer application.
5094 Standard I/O Modules
With some exceptions, the FLEX 5000 digital input modules provide the fault
5094 Safety I/O Modules and data status in a point-centric format. The tag names in the following table
that include Ptxx represent point-centric data. The xx represents the point
number.

For more information on fault reporting, see Appendix A, Troubleshoot Your

Module on page 103.
Table 11 - FLEX 5000 Digital Input Module - Fault and Data Status
Data Type Tag Name(1) Triggering Event That Sets the Tag
ConnectionFaulted(2) The owner-controller loses its connection to the module.
Fault The point data quality is bad.
PtxxFault This tag is used if you select Packed Data in the module definition.
Ptxx.Fault The point data quality is bad.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 43

Chapter 3 Input Module Features

Table 11 - FLEX 5000 Digital Input Module - Fault and Data Status (Continued)
Data Type Tag Name(1) Triggering Event That Sets the Tag
RunMode The module is in Run Mode.
DiagnosticActive Indicates if any diagnostics are active.
A counter that increments when a diagnostic condition occurs or goes
DiagnosticSequenceCount away. The counter is a rolling counter that skips 0 on rollovers.
Status The point input status is one or zero.
PtxxData This tag is used if you select Packed Data in the module definition.
Ptxx.Data The point input status is one or zero.
Ptxx.Uncertain The point data can be imperfect.
The module is operating outside its designed operating range if data
Uncertain is under manual or override control.
(1) Not all tag names apply to all FLEX 5000 digital input modules.
(2) This tag provides module-wide data and affects all points simultaneously.

44 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 4

Output Module Features

Topic Page
Features Specific to All FLEX 5000 Output Modules 45
Features Specific to Only Standard and Safety Solid-state Output Modules 50
Features Specific to Only Standard Output Modules 54
Feature Specific to Only Relay Output Modules 57

This chapter describes features common to these FLEX 5000 standard and
safety output modules:
• 16-point standard AC output module, catalog number 5094-OA16
• 16-point standard AC output module for extreme environments,
catalog number 5094-OA16XT
• 8-point standard DC high current output module, catalog number
5094-OB8
• 8-point standard DC high current output module for extreme
environments, catalog number 5094-OB8XT
• 16-point standard DC output module, catalog number 5094-OB16
• 16-point standard DC output module for extreme environments,
catalog number 5094-OB16XT
• 16-point safety DC output module, catalog number 5094-OB16S
• 16-point safety DC output module for extreme environments,
catalog number 5094-OB16SXT
• 32-point standard DC output module, catalog number 5094-OB32
• 32-point standard DC output module for extreme environments,
catalog number 5094-OB32XT
• 4-point safety relay output module, catalog number 5094-OW4IS
• 4-point safety relay output module for extreme environments,
catalog number 5094-OW4ISXT
• 8-point standard relay output module, catalog number 5094-OW8I
• 8-point standard relay output module for extreme environments,
catalog number 5094-OW8IXT

Features Specific to All The following topics are specific to all FLEX 5000 output modules.
FLEX 5000 Output Modules
Output State Change Time
Applies to these modules:
5094 Standard I/O Modules Table 12 lists the time that it takes for FLEX 5000 output module outputs to
5094 Safety I/O Modules change state after a command.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 45

Chapter 4 Output Module Features

Table 12 - Time for a Module Output to Change States

Module Time(1)
5094-OA16, 5094-OA16XT 1/2 AC cycle (Typical)
5094-OB8, 5094-OB8XT 100 µs
5094-OB16, 5094-OB16XT 100 µs
5094-OB16S, 5094-OB16SXT 4.5 ms
5094-OB32, 5094-OB32XT 100 µs
5094-OW8I, 5094-OW8IXT 10 ms
20 ms (Off to On)
5094-OW4IS, 5094-OW4ISXT
10 ms (On to Off)(2)
(1) The times that are listed in Table 12 are from the time the module receives the message.
(2) Under no fault condition.

Configurable Point-level Output State in Program Mode or

Communications Fault Mode
You can configure individual output points to specific states when the module
is in Program mode or Communications Fault mode. The following output
states are available:
• Off
• On (This option is not available for Safety applications.)
• Hold last state

To see where to configure the output states in Program mode or

Communications Fault mode, see the following:
• 5094-OA16 and 5094-OA16XT modules - page 85
• 5094-OB8 and 5094-OB8XT modules - page 86
• 5094-OB16 and 5094-OB16XT modules - page 86
• 5094-OB16S and 5094-OB16SXT modules - page 97
• 5094-OB32 and 5094-OB32XT modules - page 86
• 5094-OW4IS and 5094-OW4ISXT modules - page 98
• 5094-OW8I and 5094-OW8IXT modules - page 86

Applies to these modules:

ATTENTION: Selection of “Hold” for Output State During Program mode and
5094 Safety I/O Modules Communications Fault mode prevents the output point from going to the safe
state, making the output point not suitable for a SIL or PL rated safety function.
Set Output State During Program mode and Communications Fault mode to “Off”
to allow points to go to safe state.

Connection Fault Handling

You can configure FLEX 5000 output module behavior when a connection fault
occurs, that is, the connection between the owner-controller and the output
module breaks.

You must define the following:

• In standard and safety modules
- Immediate output behavior when the connection breaks
• In standard modules only
- Length of time that the output behaves as defined

46 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 4 Output Module Features

- Output behavior if the connection remains broken when the length of

time that is defined previously expires

Output Behavior Immediately After a Connection Fault

Applies to these modules: ATTENTION: Selection of “Hold” for Output State During Program mode and
5094 Safety I/O Modules Communications Fault mode prevents the output point from going to the safe
state, making the output point not suitable for a SIL or PL rated safety function.
Set Output State During Program mode and Communications Fault mode to “Off”
to allow points to go to safe state.
When the connection between an owner-controller and output module breaks,
the output can behave in the following ways, depending on how the
Communications Fault mode parameter is configured:
• Turn off - Default
• Transition to a specific, user-defined value
(This option is not available for Safety applications.)
• Hold its last state

The output remains at that state value until the following occurs:
• The connection to the owner-controller is re-established.
• The output returns to normal operation, as defined in the module
configuration.

Output State Once Connection Is Re-established

Once the connection between the owner-controller and output module is re-
established, the output resumes normal operation.

To see where to configure the Connection Fault Handling parameters,

see the following:
• 5094-OA16 and 5094-OA16XT modules - page 85
• 5094-OB8 and 5094-OB8XT modules - page 86
• 5094-OB16 and 5094-OB16XT modules - page 86
• 5094-OB16S and 5094-OB16SXT modules - page 97
• 5094-OB32 and 5094-OB32XT modules - page 86
• 5094-OW4IS and 5094-OW4ISXT modules - page 98
• 5094-OW8I and 5094-OW8IXT modules - page 86

Forcing
Use a force to override data that your logic either uses or produces.
• Test and debug your logic.
• Temporarily maintain normal system operations when an input device
has failed.

Use forces only as a temporary measure. They are not intended to be a

permanent part of your application.

Make sure that you understand the following before using forces.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 47

Chapter 4 Output Module Features

ATTENTION: Forcing can cause unexpected machine motion that could injure
personnel. Before you use a force, determine how the force affects your machine
or process and keep personnel away from the machine area.
• Enabling I/O or SFC forces causes your machine or process to go to another state
or phase.
• Removing forces can still leave forces in the enabled state.
• If forces are enabled and you install a force, the new force immediately takes
effect.

Enable Forces
For a force to take effect, you enable forces. You can only enable and disable
forces at the controller level.
• You can enable I/O forces and SFC forces separately or simultaneously.
• You cannot enable or disable forces for a specific module, tag collection,
or tag element.

Disable or Remove a Force

To stop the effect of a force and let your project execute as programmed,
disable or remove the force.
• You can disable or remove I/O and SFC forces simultaneously or
separately.
• When you remove a force on an alias tag, you also remove the force on
the base tag.

ATTENTION: Changes to forces can cause unexpected machine motion

that could injure personnel. Before you disable or remove forces,
determine how the change affects your machine or process and keep
personnel away from the machine area.

Check Force Status

Before you use a force, determine the status of forces for the controller.

The Online toolbar shows the status of forces. It shows the status of I/O forces
and SFC forces separately.
To determine the status of Use any of the following
• Online toolbar
I/O forces
• GSV instruction
SFC forces Online toolbar

Forces tab

48 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 4 Output Module Features

Forces Tab Status Means

• If the project contains any forces of this type, they are overriding your logic.
Enabled
• If you add a force of this type, the new force immediately takes effect
Forces of this type are inactive. If the project contains any forces of this type, they are
Disabled not overriding your logic.
Installed At least one force of this type exists in the project.
None Installed No forces of this type exist in the project.

GSV Instruction
This example shows how to use a GSV instruction to get the status of forces.
For the purposes of this example, Force_Status is a DINT tag.

Table 13 - GSV Instruction

To determine the following Examine this bit For this value
Forces are installed 0 1
No forces are installed 0 0
Forces are enabled 1 1
Forces are disabled 1 0

Data Echo
Data Echo automatically multicasts point data values that match the digital
value that was sent to the screw terminals of the module then.

A FLEX 5000 digital output module returns a value sent to it by the owner-
controller. The echoed value is either On or Off.

Fault and status data are also sent. This data is sent at the RPI.

Field Power Loss Detection

The Field Power Loss Detection feature monitors for the loss of power at an
output module point. When field power to the module is lost, a point-level fault
is sent to the controller to identify the exact point faulted.
Field Power Loss Detection has a corresponding tag that can be examined in
the user program if a fault occurs. For information on modules, see Appendix
B, Module Tag Definitions on page 117.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 49

Chapter 4 Output Module Features

Fault and Status Reporting

The digital output modules multicast fault and status data with point data to
the owner and listening controllers. The data is returned via modules that you
can monitor in your Logix Designer application.

IMPORTANT For 5094-OB16 and 5094-OB16XT output modules only, an output must
remain in the On state for a minimum of 250 ms for an overload or short
circuit to be detected. However, if a short-circuit condition exists long term,
it is detected as long as the output is switching at a rate no faster than
1 ms.

For more information on fault reporting, see Appendix A, Troubleshoot Your

Module on page 103.
Table 14 - FLEX 5000 Digital Output Module - Fault and Data Status
Data Type Tag Name(1) Triggering Event That Sets the Tag
Connection Faulted(2) The owner-controller loses its connection to the module.
The point data quality is bad. This tag is used if you select Packed
PtxxFault Data in the module definition.
Fault
Ptxx.Fault The point data quality is bad.
Ptxx.NoLoad A no load condition exists on the point.
Ptxx.ShortCircuit A short-circuit condition exists on the point.
RunMode The module is in Run Mode.
DiagnosticActive Indicates if any diagnostics are active.
A counter that increments when a diagnostic condition occurs or goes
DiagnosticSequenceCount away. The counter is a rolling counter that skips 0 on rollovers.
Status The point data is one or zero. This tag is used if you select Packed
PtxxData Data in the module definition.
Ptxx.Data The point data is one or zero.
Ptxx.Uncertain The point data can be imperfect.
The module is operating outside its designed operating range if data
Uncertain is under manual or override control.
(1) Not all tag names apply to all FLEX 5000 tag.digital I/O modules.
(2) This tag provides module-wide data and affects all points simultaneously.

Features Specific to Only The following features are specific to only the standard and safety solid-state
Standard and Safety Solid- output modules, catalog numbers 5094-OB8, 5094-OB8XT, 5094-OB16,
5094-OB16XT, 5094-OB16S, 5094-OB16SXT, 5094-OB32, and 5094-OB32XT.
state Output Modules
No Load Detection
No Load Detection detects when a wire is disconnected from the output or a
missing load for each output point.

For standard modules, No Load Detection occurs only when the output point is
in the Off state. For safety modules, No Load Detection occurs when the output
points are in either state, Off or On.
For standard modules, the No Load Detection feature is disabled by default.
You must enable the feature in your Logix Designer application project. For
safety modules, the No Load Detection feature is always enabled in firmware
revision 1.011 and is not configurable. The feature is configurable from
firmware revision 2.011 onwards.
• For safety modules with firmware revision 2.011 and above, in order to
support configurable No Load Diagnostic, see Enable 5094-OB16S or
5094-OB16SXT No Load Diagnostic on page 52.

50 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 4 Output Module Features

IMPORTANT These FLEX 5000 output modules are the only ones to support No Load
Detection:
• 5094-OB8, 5094-OB8XT
• 5094-OB16, 5094-OB16XT
• 5094-OB16S, 5094-OB16SXT
• 5094-OB32, 5094-OB32XT

The standard output modules support the following minimum load currents:
• No load detection current, max = 0.5 mA
• On-state current per point, max = 1 mA

The I.Ptxx.NoLoad tag indicates the presence of a no load condition when it is

set to 1.

You can monitor a module tag in your program that corresponds to the No
Load Detection to check for a fault. For more information on the tag, see
Appendix B, Module Tag Definitions on page 117.

For safety output modules (5094-OB16S and 5094-OB16SXT), the guaranteed

load detection is 10 mA for both states, Off and On.

Recommended Loading Resistor - To limit the effects of leakage current

through solid-state outputs, you can connect a loading resistor in parallel with
your load. For 24V DC operation in standard modules, use a 5.6K ohms, 0.5 W
resistor for transistor operation. For 24V DC operation in safety modules, use a
2.4K ohms, 0.5 W resistor for transistor operation.

In the On state, the module must be connected to a load that draws a

minimum current equal to these values.

IMPORTANT An output must remain in the off state a minimum of 250 ms for an open
load to be detected.

No Load Detection Fault for Safety Module

With firmware revision 2.011 onwards, In Controller Tag, I.Ptxx.NoLoad tag is
used to indicate No Load faults. When there is a No Load Fault, this tag is set to
1 and the Fault Exist tag is set to Yes in the Point Diagnostic Dialog. This is a
recoverable fault and the channel enters safe state (page 32). In order to reset
the fault, see Safety Output Fault Reset on page 69.

If No Load Fault has occurred, do not disable No Load Diagnostic and apply
new configuration. The No Load fault must be cleared, or the module enters a
critical fault state.

IMPORTANT If Point Operation Type is 'Dual', No load Diagnostic configuration must

match for associated points.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 51

Chapter 4 Output Module Features

Figure 7 - Example of Unmatched No Load Diagnostic Selection in Dual Point Operation

Unmatched No Load Diagnostic Warning Dialog

ATTENTION: When using a 5094-OB16S or 5094-OB16SXT module with

firmware 2.011 or later, the No Load Detection is disabled by default, regardless of
the Revision and Electronic Keying selection in the Add-on Profile. To enable
diagnostics, see Enable 5094-OB16S or 5094-OB16SXT No Load Diagnostic on
page 52.
For more information on No Load Detection behavior based on different Add-on
Profile revisions, firmware revisions, and channel configurations, see
Knowledgebase article 5094-OB16S and 5094-OB16SXT No Load
Diagnostic parameter is disabled by default, #1134767 available at:
rok.auto/knowledgebase.

Enable 5094-OB16S or 5094-OB16SXT No Load Diagnostic

In firmware revision 2.011 or later, a No Load is reported as a channel fault. To

enable No Load Diagnostic,
1. Download and install the Add-on Profile revision 3.01 or later.
2. From the General page, select Major Revision 2 under Module Definition.

3. Select the check boxes to enable No Load Diagnostic for the operations
that you wish to enable.

52 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 4 Output Module Features

Short-Circuit Protection
Short-Circuit Protection helps prevent damage to the output that can result
when more current is present at the output than it can handle.

For safety output modules (5094-OB16S and 5094-OB16SXT),

I.Ptxx.ShortCircuit tag is used for short to high or channel to channel shorts,
which do not incur over current.

There are ShortCircuitGround and Overload tags in Diagnostic assembly.

IMPORTANT These FLEX 5000 output modules are the only ones to support the Short-
Circuit Detection feature:
• 5094-OB8, 5094-OB8XT
• 5094-OB16, 5094-OB16XT
• 5094-OB16S, 5094-OB16SXT
• 5094-OB32, 5094-OB32XT

In standard modules, when a short-circuit condition is detected, the following

occurs:
• The output turns off.
• The I/O status indicator for the output flashes red.
• The I.Ptxx.ShortCircuit tag is set to 1.
For more information on how to use the modules, see Appendix B,
Module Tag Definitions on page 117.

In standard modules, when the short-circuit condition is removed, the

following occurs:
• The output restarts in its commanded state.
• The I/O status indicator for the output turns off.
• The I.Ptxx.ShortCircuit tag is reset to 0.

For safety modules, see the Safety Output Fault Reset procedure on page 69.
For more information on the maximum current that you can apply
to an output, see the FLEX 5000 Modules Specifications Technical Data,
publication 5094-TD001.

Thermal Shutoff
Thermal Shutoff helps prevent damage to the output that can result when an
output gets hotter than it can handle.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 53

Chapter 4 Output Module Features

IMPORTANT These FLEX 5000 digital output modules are the only ones to support the
Thermal Shutoff feature:
• 5094-OB8, 5094-OB8XT
• 5094-OB16, 5094-OB16XT
• 5094-OB16S, 5094-OB16SXT
• 5094-OB32, 5094-OB32XT

This feature is directly related to Short-Circuit Protection feature. The

increased temperature at the output results from an excessive load at the
output. That is, a load with high current is applied to the output. The high
current heats the output beyond an acceptable temperature and the output
turns off.

In the safety output modules (5094-OB16S, 509-OB16SXT), if overload or short

circuit to ground occurs, the point will turn off. This trigger by current
threshold is exceeded, regardless of temperature.

For standard modules, when conditions exist that cause Thermal Shutoff to
turn off the output, the following occurs:
• The output turns off.
• The I/O status indicator for the output becomes solid red.
• The I.Ptxx.ShortCircuit tag is set to 1.
For more information on how to use the modules, see Appendix B,
Module Tag Definitions on page 117.

For standard modules, when the conditions that caused a Thermal Shutoff no
longer exist, the following occurs:
• The output restarts in its commanded state.
• The I/O status indicator for the output turns off.
• The I.Ptxx.ShortCircuit tag is reset to 0.

For safety modules, refer to the Safety Output Fault Reset procedure on
page 69.

Features Specific to Only The following features are specific to only the 5094-OB16 and 5094-OB16XT
Standard Output Modules modules.

Applies to these modules: Time-scheduled Output Control

5094 Standard I/O Modules
You can schedule times for module outputs to turn On or Off. The time
schedules use units in nanoseconds.

IMPORTANT These FLEX 5000 standard output modules are the only ones to support
the Time-scheduled Output Control feature:
• 5094-OB16
• 5094-OB16XT

The timing of scheduled outputs for the 5094-OB16 and 5094-OB16XT modules
are as follows:
- ±100 μs accuracy
- 1 ns resolution
The module must be time synced or schedules are note applied.

54 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 4 Output Module Features

Time-scheduled output control is used with the Motion Arm Output Cam
(MAOC) instruction. The MAOC instruction enables position-based output
control in these ways:
Uses the position of any motion axis in a Logix 5000 control system as the
position reference

Updates the outputs based on the motion axis position at the motion group
coarse update rate, typically 1…32 ms.

The instruction can update standard digital output modules at the coarse
update rate. However, some high-speed applications require a higher degree of
accuracy.

The scheduled output modules improve the accuracy of the MAOC instruction
by supporting the ability to schedule output On and Off times. All scheduling
configuration for the On and Off times of an output is completed through the
MAOC instruction. The instruction then updates values in the output s of the
module that define the scheduled output behavior.
Table 15 - FLEX 5000 Output Module Schedule Parameters
Feature 5094-OB16, 5094-OB16XT
Number of schedules 32
Output points available for scheduling 16 (points 0…15)
Remote operation N/A
100 µs
Minimum schedule interval(1) For schedules output the MAOC instruction, you can use 50
µs.
(1) The MAOC limits the minimum schedule interval (minimum pulse width) to 1/16 of the coarse update period.

Use a MAOC Instruction with a 5094-OB16 or 5094-OB16XT Standard

Output Module
To use a MAOC instruction with schedule outputs on a 5094-OB16 or
5094-OB16XT output module, complete the following steps.

IMPORTANT Before you complete the steps, make sure that Time Synchronization is
enabled in the controller and, if applicable, the Ethernet module, to use
scheduled outputs.
1. If necessary, add a 5094-OB16 or 5094-OB16XT output module to your
Logix Designer application project.
For more information on how to add a 5094-OB16 or 5094-OB16XT output
module to a Logix Designer application and configure the module, see
Chapter 6, Configure the Standard Module on page 73.
2. From the Module Properties dialog box, click Change to access the
Module Definition parameters.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 55

Chapter 4 Output Module Features

3. On the Module Definition dialog box, choose Scheduled Data for the
Output Data and click OK.

4. Click OK to close the Module Properties dialog box.

5. Add an MAOC instruction to your logic.
6. In the MAOC instruction, use the module output tag in the Output
operand, for example Adapter:1:O for the output module and
shown below.
The tag value displays as ??. This value is correct.

For more information on how to use an MAOC instruction in general, see

the following:
• Logix 5000 Controllers Motion Instructions Reference Manual,
publication MOTION-RM002.
• Position-based Output Control with the MAOC Instruction Application
Technique, publication 1756-AT017.

56 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 4 Output Module Features

Feature Specific to Only The following feature is specific to only the relay output modules.
Relay Output Modules
Isolated Output
Applies to these modules:
5094 Standard I/O Modules These digital output modules provide point-to-point wiring isolation:
5094 Safety I/O Modules • 5094-OW4IS
• 5094-OW4ISXT
• 5094-OW8I
• 5094-OW8IXT

IMPORTANT Although some FLEX 5000 digital I/O modules do not provide wiring
isolation, all FLEX 5000 modules maintain internal electrical isolation
between the system-side and field-side power buses.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 57

Chapter 4 Output Module Features

Notes:

58 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 5

Safety I/O Module Features

Topic Page
Safety Input Module Features 59
Applies to these modules:
Safety Output Module Features 65
5094 Safety I/O Modules Safety Relay Output Module Features 69
Fault and Status Reporting 71

This chapter describes features that are specific to FLEX 5000 I/O safety
modules.

Safety Input This section describes features that are available on the FLEX 5000 I/O safety
Module Features input modules, that is, the 5094-IB16S and 5094-IB16SXT modules.

The 5094-IB16S and 5094-IB16SXT modules are 16-point safety sinking input
modules that use 16 safety inputs and 8 test outputs.

Safety Application Suitability Levels

Table 16 describes the safety application suitability levels for a 5094-IB16S and
5094-IB16SXT module.
Table 16 - Safety Application Suitability for 5094-IB16S and 5094-IB16SXT Modules
Suitability Level Conditions Notes
Applications that are rated up to, and including, Consider the following:
The modules uses single-channel mode
SIL CL3, PLc, Cat.2, as defined in IEC 61508, • The channel mode type, that is, single or dual, affects
Point mode is Safety Pulse Test or Safety
IEC 61551, IEC 62061, and ISO 13849-1 Performance Level and Category. You can use the modules
in SIL CL3 applications regardless of channel mode type.
The modules use single-channel mode: • To achieve SIL CL3 single-channel, the sensor that is used
Point mode is Safety Pulse Test or Safety must be SIL CL3 single-channel as well.
Use sheathed cable or cable trunk to separate channel wiring • The requirement that Point mode be Safety Pulse Test
to mitigate short-circuit faults. assumes that only the safety I/O module provides
Applications that are rated up to, and including, diagnostics to a specific Suitability Level.
The modules use dual-channel mode: The larger safety system within which the safety I/O module
SIL CL3, PLe, Cat.4, as defined in IEC 61508, Point mode is Safety resides can provide the diagnostics necessary to achieve the
IEC 61551, IEC 62061, and ISO 13849-1 Use sheathed cable or cable trunk to separate channel wiring stated Suitability Level without the requirement that Point mode
to mitigate short-circuit faults. be Safety Pulse Test.
To achieve the specific Safety Integrity Level, see Appendix D,
The modules use dual-channel mode: Application/Wiring Examples for Safety I/O Modules on
Point mode is Safety Pulse Test only page 185.

Input Modules in CIP Safety Systems

The following apply to the safety inputs:
• You can connect safety devices, such as Emergency Stop Push Button,
gate switches, and safety light curtains.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 59

Chapter 5 Safety I/O Module Features

• An external wiring short-circuit check is possible when inputs are wired

in combination with test outputs. The module must be wired in
combination with test outputs when this function is used.
• Independently adjustable on and off delays are available per channel.
• If you configure test outputs, you must choose a test source.
• Diagnostics. See Point Diagnostics.
• Safety input points are configured as the following:
- Not Used
- Safety
- Safety Pulse Test

The following apply to the test outputs:

• Test outputs can be configured as the following:
- Not Used
- Power Supply
- Pulse Test
• Separate test outputs are provided for short-circuit detection of a safety
input (or inputs).
• Can supply 24V DC power to devices, such as safety sensors.
• Test output rating (TO) 200 mA @ 18…32V DC

Use Test Output with a Safety Input

A test output can be used in combination with a safety input for short circuit
and cross-channel fault detection.

Configure the test output as a pulse test source and associate it to a specific
safety input. The associated safety input must use a Point Mode = Safety Pulse
Test.
These mappings are the only allowed and default digital-input-to-test-output
association mappings for Safety Pulse Test configuration. Only a test output
that is configured as Pulse Test can be used as test source.
Safety Input Maps to Test Output
0,8 0
1,9 1
2,10 2
3,11 3
4,12 4
5,13 5
6,14 6
7,15 7

60 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 5 Safety I/O Module Features

Figure 8 - FLEX 5000 I/O Safety Input Module - Input Connected to Test Output
Inputs
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

Sensor Sensor
2-wire 3-wire
+ Common – +
SA– 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 SA–

Test Outputs
TO_0 TO_1 TO_2 TO_3 TO_4 TO_5 TO_6 TO_7 TO_0 TO_1 TO_2 TO_3 TO_4 TO_5 TO_6 TO_7
SA + 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 SA+

This diagram shows:

• A 2-wire sensor is connected to safety input 0, with test output 0
configured as Test Pulse/Power Supply.
• A 3-wire sensor is connected to safety input 15, with test output 7
configured as Power Supply.
Figure 9 - 5094-IB16S and 5094-IB16SXT Test Pulse in a Cycle

On

OUT
X
Off
Y

On the 5094-IB16S and 5094-IB16SXT modules, the pulse width (X) is less than
600 μs; the pulse period (Y) is less than 100 ms.

When the external input contact is closed, a test pulse is output from the test
output terminal to diagnose the field wiring and input circuitry. By using this
function, short circuits between inputs and 24V power and between input
signal lines can be detected. However, a short circuit between two input
channels cannot be detected if these two channels correspond to the same Test
Output. For example, Test Output 0 associates to Safety Input 0 and 8. If these
two channels short circuit, it cannot be detected.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 61

Chapter 5 Safety I/O Module Features

Figure 10 - Short Circuit Between Input Signal Lines

Single-channel Mode
If an error is detected on the input channel, Safety Input Data and Safety Input
Status turn off.
For information about how using Single-channel mode with a 5094-IB16S or
5094-IB16SXT module affects the safety application suitability level, see
Table 16 on page 59.

62 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 5 Safety I/O Module Features

Figure 11 - Normal Operation and Fault Detection (Not to Scale)

Normal Operation 24V
Test O utput 0
0V

ON
External Device
OFF

Input Terminal 0 ON

OF F

Safety ON
I/O Safety Input 0
Network Data OFF
Data Sent
to the
ON
Controller Safety Input 0
Status OFF

24V
Fau lt Detec tion Test Output 0
0V

ON
External Device
OFF

Input Terminal 0 ON

OF F
Fault D etected
Safety ON
Safety Input 0
I/O
Data OFF
Network
Data Sent
to the ON
Controller Safety Input 0
Status OFF

Safety Input Fault Reset

The I/O channel supports a module-level user-configurable ‘Latch Fault until
reset via output tag’ mode and recovers from these faults:
• Field Power Off Detection
• Safety Input Short Circuit
Other types of Safety Input faults are non-recoverable. You must cycle power to
the module.

‘Latch Fault until reset via output tag’ mode is Enabled.

When Latch Fault… mode is Enabled, the I/O channel holds safety input fault
indications until it checks that the fault is removed. If the fault is removed, the
channel clears the fault status only upon detecting that the ResetFault in its
consume assembly channel sees a rising edge.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 63

Chapter 5 Safety I/O Module Features

‘Latch Fault until reset via output tag’ mode is Disabled.

When Latch Fault… mode is Disabled (default), the I/O channel holds safety
input fault indications for 1 second until it checks if the fault is removed. If the
fault is removed, the channel clears the fault status only upon detecting the
safety input is low on the screw. If not, the channel continues to check if the
fault is removed.

Safety Input Delay

This setting helps prevent rapid changes of input data due to contact bounce.

Off to On Delay

An input signal is treated as Logic 0 during the Off to On delay time after the
rising edge of the input contact.

The input turns on only if the input contact remains on after the Off to On
delay time has elapsed. This setting help prevent rapid changes of the input
data due to contact bounce.

You can delay the Off to On transition by the following times:

• 0 ms
• 1 ms
• 2 ms
• 5 ms
• 10 ms
• 20 ms
• 50 ms
Figure 12 - Off to On Delay

Input signal ON
OFF

Safety input ON
Network data OFF
On-delay

On to Off Delay

An input signal is treated as Logic 1 during the On to Off delay time after the
falling edge of the input contact.

The input turns off only if the input contact remains off after the On to Off
delay time has elapsed. This setting helps to prevent rapid changes of the input
data due to contact bounce.

You can delay the On to Off transition by the following times:

• 0 ms
• 1 ms
• 2 ms
• 5 ms
• 10 ms
• 20 ms
• 50 ms
64 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022
 Chapter 5 Safety I/O Module Features

Figure 13 - On to Off Delay

Input signal ON
OFF

Safety input ON
Network data OFF
Off-delay

Safety Output This section describes features that are available only on the FLEX 5000 I/O
Module Features safety output modules.

The 5094-OB16S and 5094-OB16SXT modules are safety sourcing output

module that use 16 digital safety outputs. You use the sourcing outputs in
Sourcing Output mode.

Safety Application Suitability Levels

Table 17 describes the safety application suitability levels for a 5094-OB16S or
5094-OB16SXT module.
Table 17 - Safety Application Suitability for 5094-OB16S and 5094-OB16SXT Module
Suitability Level Conditions Notes
Applications that are rated up to, and including, Use single-channel mode. Consider the following:
SIL 3 as defined in IEC 61508, IEC 61511, and • The channel mode type, that is, single or dual, affects
IEC 62061, and PLc, cat. 2 as defined in ISO 13849-1 – Point mode is Safety Pulse Test or Safety. Category. You can use the modules in SIL 3, PLe
1. The module uses single-channel mode. applications regardless of channel mode type.
– Point mode is Safety Pulse Test or Safety. • The requirement that Point mode be Safety Pulse Test
– Use IEC60947 certified Safety Contactor. assumes that only the safety I/O module provide
– Use sheathed cable or cable trunk to separate channel wiring diagnostics to a specific Suitability Level.
Applications that are rated up to, and including, to mitigate short-circuit faults. The larger safety system within which the safety I/O
SIL CL3, PLe, Cat.4, as defined in IEC 61508, 2. The module uses dual-channel mode. module resides can provide the diagnostics necessary to
IEC 61551, IEC 62061, and ISO 13849-1 – Point mode is Safety. achieve the stated Suitability Level without the
– Use sheathed cable or cable trunk to separate channel wiring requirement that Point mode be Safety Pulse Test.
to mitigate short-circuit faults. To achieve the specific Safety Integrity Level, see
3. The module uses dual-channel mode. Appendix D, Application/Wiring Examples for Safety I/O
– Point mode is Safety Pulse Test. Modules on page 185.

• Solid-state outputs
• Safety outputs can be pulse-tested to detect field wiring short circuits to
24V DC
• Supports field-power loss detection and configurable channel-level
output state in Program mode and Communications Fault mode

Output Module in CIP Safety Systems

The following apply to the safety outputs:
• You can connect safety devices, such as safety relays, safety contactors.
• An external wiring short-circuit check between channels or supply is
possible when the safety output is configured as Safety Pulse Test mode.
When the safety output is configured as Safety mode, external wiring
short-circuit check to supply is possible; check between channels is not
supported. The detection of external wiring fault is ≤ 300 msec.
• Diagnostics. See Status and Fault Information in Module Properties
Categories.
• Safety output points are configured as the following:

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 65

Chapter 5 Safety I/O Module Features

- Not Used
- Safety
- Safety Pulse Test
• Safety output point shall connect to a load that draws a minimum
current of 10 mA while in the “ON” state.

Safety and Safety Pulse Test Mode

The Safety Output can be configured to two types of point modes:
• Safety Mode
• Safety Pulse Test Mode

When the safety output is configured to Safety Mode, the safety output
channel continuously test the ability of the safety output switching elements
ability to turn off while maintaining the safety output at its nominal voltage
with less than 1 Volt change. This small voltage variation during the pulse test
is insignificant for most of the connected device.

If an error is detected, the safety output data and individual safety output
status turn off.

On the 5094-OB16S and 5094-OB16SXT modules, the pulse width (X) is less
than 500 μs, and the pulse period (Y) is less than 200 ms.

When the safety output is configured to Safety Pulse Test Mode, the safety
output channel continuously test the ability of the safety output to remove
power from the output terminals of the module. The safety output turn off
momentarily during the pulse test duration.

If an error is detected, the safety output data and individual safety output
status turn off.

On the 5094-OB16S and 5094-OB16SXT modules, the pulse width (X) is less
than 500 μs, and the pulse period (Y) is less than 200 ms.
To help prevent the test pulse from causing the connected device to malfunction, pay
careful attention to the input response time of the output device.
See 5094-OB16S and 5094-OB16SXT Module Wiring Diagrams on page 189 for
more details about applying Safety Mode and Safety Pulse Test Mode in your
application.

66 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 5 Safety I/O Module Features

Single-channel Mode
When the output channel is in the On state and without any faults, the safety
outputs turned on. The status is normal. If a fault is detected on the output
channel, the safety output data and individual safety output status turn off.

For information about how using single-channel mode with a 5094-OB16S or

5094-OB16SXT module affects the safety application suitability level, see
Table 17 on page 65.
Figure 14 - 5094-OB16S/5094-OB16SXT Single-channel Mode (Not to Scale)

ON
Output 0
OFF

Normal operation

ON
Safety network data sent Safety output 0
to the controller status OFF

ON
Output 0
OFF

Fault detection

Error detected
ON
Safety Network Data Safety output 0
Sent to the Controller status OFF

Dual-channel Mode
When dual-channel mode is used, output channels function as connection
pairs. Connection pairs are as follows:
• Channels 0 and 1
• Channels 2 and 3
• Channels 4 and 5
• Channels 6 and 7
• Channels 8 and 9
• Channels 10 and 11
• Channels 12 and 13
• Channels 14 and 15

When both output channels in a connection pair are in the On state and
without any faults, the safety outputs are turned on.
For information about how using dual-channel mode with a 5094-OB16S or
5094-OB16SXT module affects the safety application suitability level, see
Table 17 on page 65.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 67

Chapter 5 Safety I/O Module Features

Figure 15 - 5094-OB16S Dual-channel Mode (Not to Scale)

ON
Output 0
OFF

Normal operation
ON
Output 1
OFF

Safety network data sent ON

Safety Outputs 0
to the controller and 1 Status OFF

ON
Output 0
Fault Detection OFF

ON
Output 1
OFF

Error detected
Safety network data sent Safety outputs 0 ON
to the controller and 1 status
OFF

Surge Capability of Safety Output

The safety output supports temporary surge of current when transitioning
from OFF to ON.
Figure 16 - Surge Capability of 5094-OB16S and 5094-OB16SXT
Current per channel
(Ampere)

Surge current

Rated current

t1 t2 t3 Time (sec)

t1 = Surge time, maximum 150 msec

t2 = ON time
t3 - t2 = OFF time, 2 seconds

Surge Current per channel = 1.8 Amperes

IMPORTANT: The module current rating cannot exceed 10 Amperes at any time.

68 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 5 Safety I/O Module Features

Safety Output Fault Reset

The I/O channel supports a module-level user-configurable ‘Latch Fault until
reset via output tag’ mode and recovers from only these field faults:
• Field Power Off Detection
• Safety Output ShortCircuitGround
• Safety Output Overload
• Safety Output NoLoad
Other types of Safety Output faults are non-recoverable. You must cycle power to
the module.

‘Latch Fault until reset via output tag’ mode is Enabled.

When Latch Fault… mode is Enabled, the I/O channel holds safety output fault
indications until it checks that the field fault is removed. If the field fault is
removed, the channel clears the fault status only upon detecting that the
ResetFault in its consume assembly channel sees a rising edge.

‘Latch Fault until reset via output tag’ mode is Disabled.

When Latch Fault… mode is Disabled (default), the I/O channel holds safety
output fault indications for 1 second until it checks if the field fault is removed.
If the field fault is removed, the channel clears the fault status only upon
detecting the consume data bit is low. The fault status will also be cleared by a
module reset or power cycle, or when ‘Output State During Program Mode and
Communications Fault Mode’ is configured to Off and any of these conditions:
• Controller in Program mode
• Controller or Safety task fault
• Communications fault
• Module inhibit

After the channel clears the fault, the I/O indicator (red) turns off. The output
data can now be controlled.

IMPORTANT If the module outputs experience persistent high faults, consider cycling
power to the module to clear the error.

Safety Relay Output Module This section describes features that are available only on the FLEX 5000 relay
Features 4-point safety output modules.

The 5094-OW4IS and 5094-OW4ISXT relay modules are safety output modules
that use 4-point safety outputs.

Safety Application Suitability Levels

Table 18 describes the safety application suitability levels for a 5094-OW4IS or
5094-OW4ISXT module.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 69

Chapter 5 Safety I/O Module Features

Table 18 - Safety Application Suitability for 5094-OW4IS and 5094-OW4ISXT Module

Suitability Level Conditions Notes
Applications that are rated up to, and including, Consider the following:
The modules uses single-channel mode
SIL CL2, PLd, Cat.3, as defined in IEC 61508, IEC • To achieve SIL CL3 single-channel, the actuator that is used
– Signal state change at least once a year
61551, IEC 62061, and ISO 13849-1 must be SIL CL3 single-channel as well.
• Use sheathed cable or cable trunk to separate channel wiring
1. The modules use single-channel mode: to mitigate short-circuit fault.
Applications that are rated up to, and including, – Signal state change at least once a month • Fuse with proper rating should be connected to prevent relay
SIL CL3, PLe, Cat.4, as defined in IEC 61508, IEC 2. The modules use dual-channel mode: contacts from overload and short circuit.
61551, IEC 62061, and ISO 13849-1 – Ladder logical alternative toggle each channel at least • To achieve the specific Safety Integrity Level, see Appendix D,
once a month Application/Wiring Examples for Safety I/O Modules on
page 185.

Safety Relay Output Module in CIP Safety Systems

The following apply to the safety relay outputs:
• You can connect safety devices, such as safety relays, safety contactors.
• Diagnostics. See Status and Fault Information in Module Properties
Categories.
• Safety relay output points are configured as the following:
- Not Used
- Safety

The safety relay module is rated up to 2A/channel when all 4 channels are used
in 5…30V DC mode or 125/240V AC, 50/60 Hz mode. This module can also be
used in 5…30V DC applications requiring up to 4A/channel with the restriction
of using only channels 0 and 1; channels 2 and 3 are unused.

Snubber circuit is required when the relay output is used to drive inductive
load. See the module wiring diagram requirements on page 191.

Safety Relay Output Fault Reset

The I/O channel supports a module-level user-configurable ‘Latch Fault until
reset via output tag’ mode and recovers from only this fault:
• Field Power Off Detection

‘Latch Fault until reset via output tag’ mode is Enabled.

When Latch Fault... mode is Enabled, the I/O channel holds safety output fault
indications until it checks that the fault is removed. If the fault is removed, the
channel clears the fault status only upon detecting that the ResetFault in its
consume assembly channel sees a rising edge.

‘Latch Fault until reset via output tag’ mode is Disabled.

When Latch Fault... mode is Disabled (default), the I/O channel holds safety
output fault indications for 1 second until it checks if the fault is removed. If
the fault is removed, the channel clears the fault status only upon detecting the
consume data bit is low. If not, the channel continues to check if the fault is
removed.

After the channel clears the fault, the I/O indicator (red) turns off. The output
data can now be controlled.

IMPORTANT If the module outputs experience persistent high faults, consider cycling
power to the module to clear the error.

70 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 5 Safety I/O Module Features

Fault and Status Reporting The FLEX 5000 I/O safety modules produce fault and status data with channel
data to the owner and listening controllers. The data is returned via module
tags that you can monitor in your Logix Designer application.

For more information on how to use module tags to monitor fault and status
reporting, see the following:
• 5094-IB16S and 5094-IB16SXT modules - Table 62 on page 142
• 5094-OB16S and 5094-OB16SXT modules - Table 64 on page 143
• 5094-OW4IS and 5094-OW4ISXT modules - Table 67 on page 145
• Appendix A, Troubleshoot Your Module on page 103.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 71

Chapter 5 Safety I/O Module Features

Notes:

72 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 6

Configure the Standard Module

Topic Page
Before You Begin 73
Applies to these modules: Create a New Module 73
5094 Standard I/O Modules Edit the Module Configuration Common Categories 77
Edit 5094-IA16/5094-IM8 Module Configuration Categories 80
Edit 5094-IB16/5094-IB32 Module Configuration Categories 80
Edit 5094-OA16 Module Configuration Categories 85
Edit 5094-OB8/5094-OB16/5094-OB32 Module Configuration Categories 86
Edit 5094-OW8I Module Configuration Categories 86
View the Module Tags 87

This chapter describes how to configure your FLEX 5000 digital I/O modules
in a Logix Designer application project. You can use the default module
configuration or edit the module configuration.

IMPORTANT Consider the following:

• You must use the Studio 5000 Logix Designer application, version 31 or
later, to configure the FLEX 5000 I/O modules. Version 31 or later is slightly
different from previous programming software versions. For example,
in some cases, instead of tabs across the top of the Module Properties
dialog box, the application uses categories on the left side of the dialog box.
• This chapter does not explain the user-configurable module features that
you can edit on different screens in your Logix Designer application project.
For detailed information about module features, see the following:
- Chapter 2, Common Digital I/O Module Features on page 35
- Chapter 3, Input Module Features on page 41
- Chapter 4, Output Module Features on page 45

Before You Begin You must complete the following tasks before you can configure the module:
1. Create a Logix Designer application project.
2. Add a FLEX 5000 EtherNet/IP adapter to the project.
For more information on how to add a FLEX 5000 EtherNet/IP adapter
to a Logix Designer application project, see the FLEX 5000 EtherNet/IP
Adapter User Manual, publication 5094-UM005.

Create a New Module After you create a Logix Designer application project and add a FLEX 5000
EtherNet/IP adapter to the project, you can use the following methods to add
modules to the project.
• Discover Modules
• New Module

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 73

Chapter 6 Configure the Standard Module

Discover Modules
To use the Discover Modules method with FLEX 5000 I/O modules, complete
these steps.
1. Go online with your Logix Designer application.
The project must include a FLEX 5000 EtherNet/IP adapter.
2. Right-click the FLEX 5000 EtherNet/IP adapter and choose Discover
Modules.
The Logix Designer application automatically detects available modules
that are connected to the backplane.

3. At the Select Module Type window, click Create to add the discovered
module to your project.

74 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 6 Configure the Standard Module

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

click OK.

5. At the warning dialog box, make sure that Inhibit module connection is
selected and click Yes.

6. Close the Select Module Type dialog box.

To add additional I/O modules with this method, complete one of the
following:
• If you cleared the Close on Create check box when you created the first
I/O module, repeat steps 3…6.
• If you did not clear the Close on Create checkbox when you created the
first I/O module, repeat steps 2…6.

New Module
To use the New Module method with FLEX 5000 I/O modules, complete these
steps.
This example shows how to add an I/O module when the Logix Designer application
project is offline.
You can add new modules when the project is online, if desired. In this case, the steps
are similar to the steps described in Discover Modules on page 74. One exception is
that, in step 1, you choose New Module instead of Discover Modules.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 75

Chapter 6 Configure the Standard Module

1. Right-click the FLEX 5000 EtherNet/IP adapter and choose New Module.

2. Select the module and click Create.

The New Module dialog box appears with a list of categories on the left
side. The number and type of categories varies by module type.

76 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 6 Configure the Standard Module

3. You can click OK to use the default configuration as shown or edit the
module configuration. The rest of this chapter describes how to edit
module configuration categories.

To add additional remote I/O modules with this method, complete one of
the following:
• If you cleared the Close on Create checkbox when you created the first I/
O module, repeat steps 2…3.
• If you did not clear the Close on Create checkbox when you created the
first I/O module, repeat steps 1…3.

Edit the Module You click the category names in the New Module dialog box to view and change
Configuration Common the configuration parameters.

Categories IMPORTANT This chapter shows how to edit configuration when you add the module to
the Logix Designer application project.
If you access the module configuration after it is added to the project, the
dialog box is named Module Properties. The same categories are displayed
as the categories displayed on the New Module dialog box.

Some new module configuration categories apply to all FLEX 5000 digital I/O
modules. Some categories are specific to the module type.

For example purposes, the figures in this section are from a 5094-IB16 module.

The following categories apply to all FLEX 5000 digital I/O modules and are
described in this section.
• General Category
• Connection Category
• Module Info Category

General Category
The General category appears first when you create a module. The parameters
in this category are the same for all FLEX 5000 digital I/O modules.

You use this category to complete the following tasks:

• Name the module.
• Assign a slot number. (required)
• Describe the module.
• Access the Module Definition.
Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 77
Chapter 6 Configure the Standard Module

Module Definition

Module Definition parameters are available on the General tab of the Module
Properties dialog box in the Logix Designer application project.

Table 19 describes the parameters on the Module Definition dialog box.

IMPORTANT The graphic is an example of a Module Definition dialog box. The same set
of fields and options are not available on all FLEX 5000 I/O modules.

Table 19 - Module Definition Parameters

Parameter Definition Available Choices(1)
Series Module hardware series Module-specific
Revision Module firmware revision, including major and minor revision levels Module-specific
Software method by which you reduce the possibility of using the wrong device in a control system.
For more information, see the following: Exact Match
Electronic Keying Compatible Module
• View the Module Tags on page 87 Disable Keying
• Electronic Keying in Logix5000 Control Systems Application Technique, publication LOGIX-AT001
Determines the following for the module type you configure: Data
• Available configuration parameters Data with Events
Connection
• Data type transferred between the module and the controller Listen Only Data(2)
• Which tags are generated when configuration is complete Listen Only Data with Events(2)
Data
All available configurations, input data. This connection type creates all controller tags specific to the
Input Data - Input modules only Timestamped Data
module type being used. Packed Data
None
4
Counters - DC Input modules only Determines the number of counters that are used for the module type. 8
12
16
Data
Output Data - Output modules only All available configurations, output data. This connection type creates all controller tags specific to the Scheduled Data
module type being used. Packed Data
(1) The choices that are available vary by module type and catalog number.
(2) Controller and module establish communication without the controller sending any configuration or output data to the module. A full input data connection is established but depends on the
connection between the owner-controller and the module.

Connection Category
The Connection category lets you complete the following tasks:
• Set the RPI rate. For more information on the RPI, see Data Types
Available with FLEX 5000 Standard I/O Modules on page 22.
• Set the connection type to use on the EtherNet/IP network.

78 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 6 Configure the Standard Module

For more information on unicast and multicast connections, see the

FLEX 5000 EtherNet/IP Adapter User Manual, publication 5094-UM005.
• Inhibit the module. For more information on how to inhibit the module,
see Module Inhibiting on page 38.
• Configure whether a connection failure while the controller is in Run
module causes a major or minor fault.
The Module Fault area of the Connection category is useful during module
troubleshooting. For more information on the Module Fault area, see page 112.

Module Info Category

The Module Info category displays module and status information about the
module when the project is online. You can use this category to complete the
following:
• Determine the identity of the module.
• Access module diagnostics.
• Refresh the data on the screen.
• Reset the module.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 79

Chapter 6 Configure the Standard Module

Edit 5094-IA16/5094-IM8 In addition to the General, Connection, and Module Info categories, the Points
Module Configuration category is available when you configure a 5094-IA16, 5094-IA16XT, 5094-IM8,
or 5094-IM8XT module.
Categories
IMPORTANT If you use the Listen Only Data connection type, the Points Category does
not appear.

Points Category
The Points category shows the available input filter time values for the
module points.

Edit 5094-IB16/5094-IB32 In addition to the General, Connection, and Module Info categories, the
Module Configuration following categories are available when you configure a 5094-IB16,
5094-IB16XT, 5094-IB32 or 5094-IB32XT module:
Categories • Counters Category
• Points Category
• Events Category
• Time Sync Category

IMPORTANT If you use the Listen Only Data or Listen Only Data with Events connection
type, the Points Category, Counters Category, and Events Category do not
appear.

Counters Category
The Counters category is available only if you choose a value for Counters in
the Module Definition dialog box.

The Counters category shows the configuration options available for each
counter. Based on your Input Filter Time selections, the Input Filter Time

80 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 6 Configure the Standard Module

Off→On and On→Off times change. You can also configure the counter Preset
value and enable Rollover at Preset.

IMPORTANT The total number of Counters subtracts from the available number of
Points. For example, if you configure a 5094-IB16 module to use four
counters, the first four terminals are not available to use as points.
The number of points available on the module in this case is 12. That is,
points 4…15.

Points Category
The Points category shows the available input filter time values for the
module points.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 81

Chapter 6 Configure the Standard Module

If you choose Timestamped Data for Input Data in the Module Definition
dialog box, the Points category expands.

PTxx Category

The PTxx category shows the configuration options available when you use
Timestamping on a point.

IMPORTANT You must choose the Input Data option Timestamp Data on the Module
Definition dialog box to see this category in the Module Properties dialog
box.

Click each Ptxx to configure it as necessary for your application.

Events Category
The Events category is available only if you choose Data with Events for
Connection in the Module Definition dialog box. Click the + sign next to the
Events category to expand it.

IMPORTANT You cannot configure events on the Module Properties dialog box. The
parameters that are displayed are read-only.
You must use the Event Output tags to configure an event. For more
information, see Configure an Event in the Event Output Tags on page 83.

IMPORTANT For 5094-IB32 and 5094-IB32XT input modules, Events are supported only
on points 0…15. Events are not supported on points 16…31.

82 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 6 Configure the Standard Module

The Events subcategories show the configuration parameters for events.

Configure an Event in the Event Output Tags

To configure an event, you must change the Event Output tags for the affected
module via the Tag Monitor in the Logix Designer application. When you
change the tags, the change is reflected on the Module Properties dialog box.

The following graphics show how tag values are reflected on the Module
Properties. The following conditions are shown:
• Event is enabled
• Point 4 is configured to trigger the event
• Event is latched
• Trigger Event is on input transition to match pattern

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 83

Chapter 6 Configure the Standard Module

These changes in the Event Output

tags configure the event.
After the tags are changed, the
related parameters on the Module
Properties are updated
automatically.

For more information on module tags, see the following:

• View the Module Tags on page 87
• Appendix B, Module Tag Definitions on page 117

84 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 6 Configure the Standard Module

Time Sync Category

The Time Sync category displays and status information about the module
when the project is online. The Time Sync category displays the following
information:
• CIP Sync Time Synchronization
• UTC System Time
• Grandmaster Clock information
• Local Clock information

Edit 5094-OA16 Module In addition to the General, Connection, and Module Info categories, the Points
Configuration Categories category is available when you configure a 5094-OA16 or 5094-OA16XT module.

IMPORTANT If you use the Listen Only Data connection type, the Points Category does
not appear.

Points Category
The Points category shows the configuration options available for each point.
You can configure the following parameters from the Points category:
• Output State During Program Mode
• Output State During Fault Mode
• Fault Mode Output State Duration
• Fault Mode Output State Final State
• Output State When Communications Fail in Program Mode

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 85

Chapter 6 Configure the Standard Module

Edit 5094-OB8/5094-OB16/ In addition to the General, Connection, and Module Info categories, the Points
5094-OB32 Module category is available when you configure a 5094-OB8, 5094-OB8XT, 5094-OB16,
5094-OB16XT, 5094-OB32, or 5094-OB32XT module.
Configuration Categories
IMPORTANT If you use the Listen Only Data connection type, the Points Category does
not appear.

Points Category
The Points category shows the configuration options available for each point.
You can configure the following parameters from the Points category:
• Output State During Program Mode
• Output State During Fault Mode
• Fault Mode Output State Duration
• Fault Mode Output State Final State
• Output State When Communications Fail in Program Mode
• Enable No Load Diagnostics

Edit 5094-OW8I Module In addition to the General, Connection, and Module Info categories, the Points
Configuration Categories category is available when you configure a 5094-OW8I module.

IMPORTANT If you use the Listen Only Data connection type, the Points Category does
not appear.

86 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 6 Configure the Standard Module

Points Category
The Points category shows the configuration options available for each point.
You can configure the following parameters from the Points category:
• Output State During Program Mode
• Output State During Fault Mode
• Fault Mode Output State Duration
• Fault Mode Output State Final State
• Output State When Communications Fail in Program Mode

View the Module Tags When you create a module, the Logix Designer application creates a set of tags
that you can view in the Tag Editor. Each configured feature on your module
has a distinct tag that is available for use in the controller program logic.
Complete the following steps to access the module tags.
1. In the Controller Organizer, right-click Controller Tags and choose
Monitor Tags.

The Controller Tags dialog box appears with data.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 87

Chapter 6 Configure the Standard Module

2. To view the tags, click the symbols as shown.

For more information on module tags, see Appendix B, Module Tag

Definitions on page 117.

88 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 7

Configure and Replace Safety Modules

Topic Page
Before You Begin 89
Applies to these modules: Create a New Module 90
5094 Safety I/O Modules Edit the Module Configuration Common Categories 91
Edit the 5094-IB16S or 5094-IB16SXT Module Configuration Categories 96
Edit the 5094-OB16S or 5094-OB16SXT Module Configuration Category 97
Edit the 5094-OW4IS or 5094-OW4ISXT Module Configuration Category 98
View the Module Tags 98
Replace a Module 99

This chapter describes how to configure your FLEX 5000 safety I/O modules in
a Logix Designer application project.

IMPORTANT You must use the Logix Designer application, version 32 or greater with the
modules.

This chapter does not explain the user-configurable parameters, or

corresponding module features, in your Logix Designer application project.

For detailed information about module features, see the following:

• Chapter 2, Common Digital I/O Module Features on page 35
• Chapter 3, Input Module Features on page 41
• Chapter 4, Output Module Features on page 45
• Chapter 5, Safety I/O Module Features on page 59

IMPORTANT By default, all safety input and output channels on FLEX 5000 safety I/O
modules are disabled.
You must configure each point that is used in a safety application.

Before You Begin You must complete the following tasks before you can configure the module:
1. Create a Logix Designer application project.
2. If you use the FLEX 5000 safety I/O modules as remote I/O modules, add
a FLEX 5000 I/O EtherNet/IP adapter to the project.
For more information on how to add a FLEX 5000 I/O EtherNet/IP
adapter to a Logix Designer application project, see the FLEX 5000
EtherNet/IP Adapter User Manual, publication 5094-UM005.

Once the project is created and, if necessary, the adapter is added, you can
create a new module in the Logix Designer application project.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 89

Chapter 7 Configure and Replace Safety Modules

Create a New Module Unlike FLEX 5000 standard I/O modules, you cannot add FLEX 5000 safety
I/O modules to a Logix Designer project while the project is online. The project
must be offline to add FLEX 5000 safety I/O modules to it.

You can create a new FLEX 5000 safety I/O module. I/O modules are installed
in a system that includes a FLEX 5000 I/O EtherNet/IP adapter that connects
to an EtherNet/IP network.

New I/O Module

To create a new FLEX 5000 safety I/O module, complete these steps.
1. Add a FLEX 5000 I/O EtherNet/IP adapter to the project.
This example uses a 5094-AENTR or 5094-AEN2TR adapter.
2. Right-click the FLEX 5000 I/O EtherNet/IP adapter and choose
New Module.

3. Select the module and click Create.

The New Module dialog box appears with a list of categories on the left
side. The number and type of categories varies by module type.

90 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 7 Configure and Replace Safety Modules

4. You can click OK to use the default configuration as shown or edit the
module configuration. The rest of this chapter describes how to edit
module configuration categories.

To add additional I/O modules with this method, complete one of

the following:
• If you cleared the Close on Create checkbox when you created the first I/
O module, repeat steps 3…4.
• If you did not clear the Close on Create checkbox when you created the
first I/O module, repeat steps 2…4.

Edit the Module You click the category names in the New Module dialog box to view and change
Configuration Common the configuration parameters. Before you edit the module configuration,
consider the following:
Categories • This chapter shows how to edit configuration when you add the module
to the Logix Designer application project.
If you access the module configuration after it is added to the project, the
dialog box is named Module Properties. The same categories are
displayed as the categories displayed on the New Module dialog box.
• Some new module configuration categories apply to all FLEX 5000
digital safety I/O modules. Some categories are specific to the
module type.

IMPORTANT By default, all safety input and output channels on FLEX 5000 safety I/O
modules are disabled.
You must configure each point that is used in a Safety application.

The following categories apply to all FLEX 5000 digital safety I/O modules and
are described in these sections:
• General Category
• Connection Category
• Safety Category
• Module Info Category

General Category
The General category appears first when you create a module. The parameters
in this category are the same for all FLEX 5000 digital I/O modules.

You use this category to complete the following tasks:

• Name the module.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 91

Chapter 7 Configure and Replace Safety Modules

• Assign a node number.

• Describe the module.
• Access the Module Definition.

Safety Network Number

The Logix Designer application automatically assigns a Safety Network

Number (SNN) to FLEX 5000 safety I/O modules as they are added to the
project.

The SNN is a time-based number that uniquely identifies subnets across all
networks in the safety system. All FLEX 5000 safety I/O modules in a same
system use the same SNN and are automatically assigned the same SNN by
default.

The Logix Designer application assigns an SNN to the first safety module that
is added to a remote system. The application assigns the same SNN to
additional safety modules that are added to this remote I/O system.

For more information on Safety Network Numbers, see the GuardLogix 5580
and Compact GuardLogix 5380 Controller Systems Safety Reference Manual,
publication 1756-RM012.

92 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 7 Configure and Replace Safety Modules

Module Definition

Module Definition parameters are available on the General tab of the Module
Properties dialog box in the Logix Designer application project.
5094-IB16S and 5094-IB16SXT Modules 5094-OB16S and 5094-OB16SXT Modules

Table 20 describes the parameters that are available on the Module Definition
dialog box.
Table 20 - Module Definition Parameters
Parameter Definition Available Choices
Series Module hardware series Module-specific
Revision Module firmware revision, including major and minor revision levels Module-specific
Software method by which you reduce the possibility of using the wrong device in a control system.
For more information, see the following: • Exact Match
Electronic Keying • Electronic Keying on page 38 • Compatible Module
• Electronic Keying in Logix5000 Control Systems Application Technique, publication LOGIX-AT001
Determines the following for the module type you configure: • This Controller
Configured By • Which controller tags are generated when configuration is complete • External Means(1)
Determines what type of input data is exchanged between the module and the controller. • Safety data
Input Data Creates all controller tags specific to the module type being used. • Safety packed data
• None - If Configured By is
External Means.
Output Data - 5094-OB16S and Determines what type of output data is exchanged between the module and the controller.
5094-OB16SXT modules only The available choices are dictated by the Configured By parameter choice. • Safety data and Safety
packed data - If Configured
By is This Controller.
(1) Controller and module establish communication without the controller sending any configuration or output data to the module. A full input data connection is established but depends on the
connection between the owner-controller and the module.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 93

Chapter 7 Configure and Replace Safety Modules

Connection Category
The Connection category lets you inhibit the module.

Before you inhibit the module, make sure that you are aware of the impact it
has on your application. For more information on inhibiting the module, see
page 38.

IMPORTANT Unlike FLEX 5000 standard I/O modules, you cannot set the RPI for FLEX
5000 safety I/O modules on the Connections category. For FLEX 5000
safety I/O modules, you set the RPI on the Safety category.

Connection Over the EtherNet/IP Network

Remote FLEX 5000 safety I/O modules support the Connection over
EtherNet/IP parameter.
• With safety input data, you can choose Unicast or Multicast.
• With safety output data, you must choose Unicast.

For more information on unicast and multicast connections, see the

FLEX 5000 EtherNet/IP Adapter User Manual, publication 5094-UM005.

94 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 7 Configure and Replace Safety Modules

Safety Category
The Safety category lets you set the RPI rate.

To change the Connection Reaction Time Limit configuration, click Advanced.

IMPORTANT Remember, the Safety Task period determines the 5094-OB16S module RPI.

Need to add artwork.

For more information on the RPI and the Connection Reaction Time Limit
parameters, see Requested Packet Interval on page 21.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 95

Chapter 7 Configure and Replace Safety Modules

Module Info Category

The Module Info category displays module and status information about the
module when the project is online. You can use this category to complete the
following:
• Determine the identity of the module.
• Access module diagnostics.
• Refresh the data on the screen.
• Reset the module.

Edit the 5094-IB16S or These categories are available when you configure a 5094-IB16S or
5094-IB16SXT Module 5094-IB16SXT module:
• Input Points Category
Configuration Categories • Test Output Points Category

Input Points Category

The Input Points category is only available if you choose This Controller for the
Configured By parameter on the Module Definition dialog box.
You must configure each point to use it in a Safety application. The inputs are
disabled by default.

For more information on input delay times, see page 64.

96 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 7 Configure and Replace Safety Modules

Test Output Points Category

The Test Output Points category is only available if you choose This Controller
for the Configured By parameter on the Module Definition dialog box.

You must configure each point to use it in a safety application. The outputs are
disabled by default.

Need to add artwork.

Edit the 5094-OB16S or The 5094-OB16S or 5094-OB16SXT module uses the Output Configuration
5094-OB16SXT Module category.

Configuration Category The Points Configuration category is only available if you choose This
Controller for the Configured By parameter on the Module Definition
dialog box.
You must configure each point to use it in a safety application. The outputs are
disabled by default.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 97

Chapter 7 Configure and Replace Safety Modules

Edit the 5094-OW4IS or The 5094-OW4IS or 5094-OW4ISXT relay module uses the Output
5094-OW4ISXT Module Configuration category.

Configuration Category The Points Configuration category is only available if you choose This
Controller for the Configured By parameter on the Module Definition
dialog box.

You must configure each point to use it in a safety application. The outputs are
disabled by default.

View the Module Tags When you create a module, the Logix Designer application creates a set of tags
that you can view in the Tag Editor. Each configured feature on your module
has a distinct tag that is available for use in the controller program logic.

Complete the following steps to access the tags for a module.

1. In the Controller Organizer, right-click Controller Tags and choose
Monitor Tags.

The Controller Tags dialog box appears with data.

2. To view the tags, click the triangle symbols.

For more information on module tags, see Appendix B, Module Tag

Definitions on page 117

98 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 7 Configure and Replace Safety Modules

Replace a Module Replacing a safety module that sits on a CIP Safety network is more
complicated than replacing standard devices because of the safety network
number (SNN).

Safety devices require this more complex identifier to make sure that module
numbers that are duplicated on separate subnets across all of the networks in
the application do not compromise communication between the correct safety
devices.

The SNN is a unique identifier that is automatically assigned to each subnet in

a safety application. The same SNN is assigned to also devices on the subnet.

For example, when a FLEX 5000 I/O EtherNet/IP adapter is used in a safety
application, the Logix Designer project assigns it an SNN. All FLEX 5000 I/O
modules that are installed with that adapter, are automatically assigned the
same SNN.

However, each FLEX 5000 safety I/O modules require a unique identifier
within the same subnet. A DeviceID is used to uniquely identify each safety
module. The SNN and module slot number make up the DeviceID of the safety
module.

Set the SNN Manually

The SNN is used to provide integrity on the initial download to a FLEX 5000
I/O safety module.
If a safety signature exists, the FLEX 5000 I/O safety module must have
DeviceID that matches the module in the safety controller project, before it can
receive its configuration.

To maintain integrity, the module SNN must be set manually.

1. On the General category of the Module Properties dialog box, click the
ellipsis next to the Safety Network Number.

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

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 99

Chapter 7 Configure and Replace Safety Modules

3. Type the SNN in the Number field and click OK.

4. On the Module Properties dialog box, click OK.

Reset to Out-of-Box Configuration

When the Logix Designer application is online, the Safety tab of the Module
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 node address or slot number of the configuration owner.
Communication error is displayed if the module read fails.

If the connection is Local, you must inhibit the module connection before you
reset ownership.

To inhibit the module, follow these steps.

1. Right-click the module and choose Properties.
2. On the Connection tab, click Inhibit module.
3. Click Apply and then OK.

Follow these steps to reset the module to its out-of-box configuration

when online.
1. Right-click the module and choose Properties.
2. On the Safety tab, click Reset Ownership.

100 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Chapter 7 Configure and Replace Safety Modules

3. When a dialog box appears asking if you want to continue with the reset,
read it and click Yes.

Replace a Module in a Logix 5000 System

Consider the following conditions before you replace a FLEX 5000 safety I/O
module in a Logix 5000 system:
• If you rely on a portion of the CIP Safety system to maintain SIL 3
behavior during module replacement and functional testing, you must
use the Configure Only When No Safety Signature Exists feature.
• If you rely on the entire routable CIP Safety control system to maintain
SIL 3/PL (d or e) during the replacement and functional testing of a
module, you can use the Configure Always feature.

Replacement with ‘Configure Only When No Safety Signature Exists’ Enabled

When a module is replaced, the configuration is downloaded from the safety

controller if the DeviceID of the new module matches the original. The
DeviceID is updated whenever the SNN is set.

If the project is configured with Configure Only When No Safety Signature

Exists enabled, follow the appropriate instructions in to replace a FLEX 5000
safety I/O module.

After you complete the steps in a scenario correctly, the DeviceID matches the
original. This match enables the safety controller to download the proper
module configuration, and re-establish the safety connection.
Table 21 - Replace a FLEX 5000 Safety I/O Module
Controller Safety Replacement Module Condition Action Required
Signature Exists
No No SNN (Out-of-box) None. The module is ready for use.
Same SNN as original safety task
Yes or No None. The module is ready for use.
configuration
Yes No SNN (Out-of-box) Complete the steps in Set the SNN Manually on page 99.
1. Reset to Out-of-Box Configuration on page 100.
Yes
2. Set the SNN Manually on page 99.
Different SNN from original safety 1. Reset to Out-of-Box Configuration on page 100.
task configuration 2. Follow your company-prescribed procedures to
No
functionally test the replaced I/O device and system
and to authorize the system for use.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 101

Chapter 7 Configure and Replace Safety Modules

Replacement with ‘Configured Always’ Enabled

ATTENTION: Enable the ‘Configure Always’ feature only if the entire CIP Safety
Control System is not being relied on to maintain SIL 3 behavior during the
replacement and functional testing of a module.
Do not place modules that are in the out-of-box condition on a CIP Safety network
when the Configure Always feature is enabled, except while following this
replacement procedure.

When the ‘Configure Always’ feature is enabled, the controller automatically

checks for and connects to a replacement module that meets all the following
requirements:
• The controller has configuration data for a compatible module at that
network address.
• The module is in out-of-box condition or has an SNN that matches the
configuration.

If the project is configured for ‘Configure Always’, follow the appropriate steps
to replace a FLEX 5000 safety I/O module.
1. Remove the old I/O module and install the new module.
If Then
go to step 6.
the module is in out-of-box condition No action is needed for the controller to take ownership of the
module.
an SNN mismatch error occurs go to the next step to reset the module to out-of-box condition.
2. Right-click your I/O module and choose Properties.
3. Click the Safety tab.
4. Click Reset Ownership.
5. Click OK.
6. Follow your company-prescribed procedures to functionally test the
replaced I/O module and system and to authorize the system for use.

102 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix A

Troubleshoot Your Module

Topic Page
SA Power Indicator 103
Module Status Indicator 104
FLEX 5000 Input Modules Status Indicators 105
FLEX 5000 Output Modules Status Indicators 107
FLEX 5000 Safety Input Modules Status Indicators 110
FLEX 5000 Safety Output Modules Status Indicators 111
FLEX 5000 Safety Relay Output Modules Status Indicators 111
Use the Logix Designer Application for Troubleshooting 112

FLEX 5000 I/O modules use the following status indicators:

• SA Power Indicator – This indicator operates the same for all FLEX 5000
I/O modules.
• Module Status Indicator – This indicator operates the same for all
FLEX 5000 I/O modules.
• I/O Status Indicator – This indicator operates differently based on the
module type.

SA Power Indicator Table 22 describes the SA Power indicator on FLEX 5000 I/O modules.
Table 22 - SA Power Indicator - FLEX 5000 Standard I/O Modules
Indicator State Description Recommended Action
Complete the following actions:
Off The module is not powered. 1. Confirm that the system is powered.
2. Confirm that the module is installed properly.
Steady green There is SA power to the module. None
Complete the following actions:
1. Confirm that the SA Power wiring on the terminal base is installed
properly.
2. Check the following:
Steady red There is no SA power to the module. – Confirm that there is sufficient voltage supplied to the module.
– If an external power supply is used, confirm that the power supply is
turned on.
– If power is daisychained from the previous terminal base, confirm that
the wiring on the previous terminal base is installed properly.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 103

Appendix A Troubleshoot Your Module

Table 23 - SA Power Indicator - FLEX 5000 Safety I/O Modules

Indicator State Description Recommended Action
Complete the following actions:
Off The module is not powered. 1. Confirm that the system is powered.
2. Confirm that the module is installed properly.
Steady green There is SA power to the module. None
Complete the following actions:
1. Confirm that the SA Power wiring on the terminal base is installed
properly.
2. Check the following:
• There is no SA power to the module. – Confirm that there is sufficient voltage supplied to the module.
Steady red
• SA voltage is not within a valid range. – If an external power supply is used, confirm that the power supply is
turned on.
– If power is daisychained from the previous terminal base, confirm that
the wiring on the previous terminal base is installed properly.
– Confirm that the SA voltage is within the correct range (18…32V).

Module Status Indicator Table 24 describes the Module Status indicator on FLEX 5000 I/O modules.
Table 24 - Module Status Indicator - FLEX 5000 Digital I/O Modules
Indicator State Description Recommended Action
Complete the following actions:
Off The module is not powered. 1. Confirm that the system is powered.
2. Confirm that the module is installed properly.
Steady green The module has a connection to the owner-controller and is operating normally. None
One of the following conditions exist: Complete the following actions:
– The module has powered up successfully. • Troubleshoot your Logix Designer application to determine what is
– The module is OK, but it does not have a connection. preventing a connection from the module to the controller and
No connection can result from missing, incomplete, or incorrect
Flashing green correct the issue.
module configuration.
For safety modules only - A connection can be established with the controller, • Confirm that the system conditions require the controller to be in
but initial time coordination exchange is not complete. Remote Run mode or Run mode, transition the controller to one of
Connection to an output module is in the idle state. those modes.
Complete the following actions:
1. Cycle power to the module.
Steady red The module experienced a nonrecoverable fault.
2. If the status indicator remains in the steady red state, replace the
module.
Complete one of the following:
• Let the firmware update progress complete.
• Reattempt a firmware update after one fails.
• Use the Logix Designer application to determine the cause of the
module fault.
The Connection and Module Info categories of the modules
configuration indicate the fault type.
One of the following conditions exist: To clear a recoverable fault, complete one of the following:
• A module firmware update is in progress. – Cycle module power.
Flashing red • A module firmware update attempt failed. – Click Reset Module in the Logix Designer project via the Module
• The device has experienced a recoverable fault. Info category of the Module Properties dialog box.
• A connection to the module has timed out. If the fault does not clear after cycling power and clicking Reset
Module, contact Rockwell Automation Technical Support.
• Use the Logix Designer application to determine if a connection has
timed out. The Connection category in the Module Properties for the
module indicates the module state, including if a connection has
timed out.
If a connection has timed out, determine the cause and correct it.
For example, a cable failure can cause a connection timeout.
Red/green (railroad) For safety modules only - This pattern indicates that a UNID for the safety device None
needs to be configured.

104 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Status Indicators
FLEX 5000 Input Modules

Bottom row
Top row
0

Input Point 16 (I16) Input Point 0 (I00) Input Point 0 (I00)

0
16
1

1
Input Point 17 (I17) Input Point 1 (I01) Input Point 1 (I01)

17
5094-IB32
5094-IB16
2

2
Input Point 18 (I18) Input Point 2 (I02) Input Point 2 (I02)

18
3

Input Point 19 (I19) Input Point 3 (I03) Input Point 3 (I03)

3
19
4

Input Point 20 (I20) Input Point 4 (I04) Input Point 4 (I04)

4
20
5

5
Input Point 21 (I21) Input Point 5 (I05) Input Point 5 (I05)

21
6

6
Input Point 22 (I22) Input Point 6 (I06) Input Point 6 (I06)

22
7

TM
TM

7
Input Point 23 (I23) Input Point 7 (I07) Input Point 7 (I07)

23
8

FLEX 5000 I/O

FLEX 5000 I/O

8
Input Point 24 (I24) Input Point 8 (I08) Input Point 8 (I08)

24
9

9
25
Input Point 25 (I25) Input Point 9 (I09) Input Point 9 (I09)
10

DIGITAL 32 INPUT 24 VDC

DIGITAL 16 INPUT 24 VDC
5094-IB16, 5094-IB16XT

10
26
Input Point 26 (I26) Input Point 10 (I10) Input Point 10 (I10)
5094-IB32, 5094-IB32XT

POWER
11
POWER

27
11
Input Point 27 (I27) Input Point 11 (I11) Input Point 11 (I11)

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

12

28
12
Input Point 28 (I28) Input Point 12 (I12) Input Point 12 (I12)

1
1
13

Input Point 29 (I29) Input Point 13 (I13) Input Point 13 (I13)

29
13
Figure 17 - FLEX 5000 DC Input Module Status Indicators

STATUS
STATUS

14

Input Point 30 (I30) Input Point 14 (I14) Input Point 14 (I14)

30
14
1 TB3

15
31
Input Point 31 (I31) Input Point 15 (I15) Input Point 15 (I15)
15

4 TB32V
Appendix A

I/O status indicators

I/O status indicators

Module status indicator

Module status indicator
Figure 17 shows the status indicators on FLEX 5000 DC input modules.

SA power status indicator

SA power status indicator

105
Troubleshoot Your Module
Appendix A Troubleshoot Your Module

Table 25 describes the I/O Status indicators on FLEX 5000 input modules.
Table 25 - I/O Status Indicators - FLEX 5000 Input Modules
Indicator State Description Recommended Action
One of the following:
One of the following: • Confirm that the input point is configured
properly.
Off • The input point is Off.
• Confirm that there is backplane power
• There is no backplane power. supplied through the FLEX 5000 EtherNet/
IP adapter.
Steady yellow The input point is operating normally. None
Locate and correct the cause of field power
Flashing red A Field Power Loss condition exists. loss condition.

Figure 18 shows the status indicators on FLEX 5000 AC input modules.

Figure 18 - FLEX 5000 AC Input Module Status Indicators

5094-IA16, 5094-IA16XT

POWER STATUS
FLEX 5000 I/O
TM

Module status indicator

SA power status indicator

5094-IA16 DIGITAL 16 INPUT AC 4 4 TB3AC

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 I/O status indicators
Input Point 6 (I06)

Input Point 11 (I11)

Input Point 9 (I09)

Input Point 14 (I14)

Input Point 1 (I01)

Input Point 8 (I08)

Input Point 2 (I02)
Input Point 3 (I03)

Input Point 7 (I07)

Input Point 13 (I13)

Input Point 0 (I00)

Input Point 4 (I04)

Input Point 5 (I05)

Input Point 12 (I12)

Input Point 10 (I10)

Input Point 15 (I15)

5094-IM8, 5094-IM8XT

POWER STATUS
FLEX 5000 I/O
TM

Module status indicator

SA power status indicator

5094-IM8 DIGITAL 8 INPUT AC 4 2 TB3AC

0 1 2 3 4 5 6 7 I/O status indicators
Input Point 0 (I00)

Input Point 5 (I05)

Input Point 7 (I07)

Input Point 3 (I03)
Input Point 1 (I01)

Input Point 2 (I02)

Input Point 6 (I06)

Input Point 4 (I04)

106 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix A Troubleshoot Your Module

Table 26 describes the I/O Status indicators on FLEX 5000 input modules.
Table 26 - I/O Status Indicators - FLEX 5000 Input Modules
Indicator State Description Recommended Action
One of the following:
One of the following: • Confirm that the input point is configured
properly.
Off • The input point is Off.
• Confirm that there is backplane power
• There is no backplane power. supplied through the FLEX 5000 EtherNet/
IP adapter.
Steady yellow The input point is operating normally. None
Locate and correct the cause of field power
Flashing red A Field Power Loss condition exists. loss condition.

FLEX 5000 Output Modules Figure 19 show the status indicators on FLEX 5000 DC output modules.
Status Indicators Figure 19 - FLEX 5000 DC Output Modules Status Indicators
5094-OB8, 5094-OB8XT

POWER STATUS
FLEX 5000 I/O
TM

Module status indicator

SA power status indicator

5094-OB8 DIGITAL 8 OUTPUT HIGH CURRENT 1 3 TB3

0 1 2 3 4 5
Output Point 5 (O15) 6 7 I/O status indicators
Output Point 0 (O00)

Output Point 1 (O01)

Output Point 3 (O03)

Output Point 6 (O16)

Output Point 2 (O02)

Output Point 4 (O04)

Output Point 7 (O17)

5094-OB16, 5094-OB16XT

FLEX 5000 I/O

TM
POWER STATUS

Module status indicator

SA power status indicator

5094-OB16 DIGITAL 16 OUTPUT 24 VDC 1 2 TB3

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 I/O status indicators
Output Point 11 (O11)
Output Point 5 (O05)

Output Point 15 (O15)

Output Point 0 (O00)

Output Point 12 (O12)

Output Point 2 (O02)
Output Point 3 (O03)
Output Point 1 (O01)

Output Point 6 (O06)

Output Point 8 (O08)

Output Point 9 (O09)
Output Point 10 (O10)
Output Point 4 (O04)

Output Point 7 (O07)

Output Point 13 (O13)

Output Point 14 (O14)

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 107

Appendix A Troubleshoot Your Module

5094-OB32, 5094-OB32XT

POWER STATUS
FLEX 5000 I/O
TM

Module status indicator

SA power status indicator

5094-OB32 DIGITAL 32 OUTPUT 24 VDC 2 5 TB32C

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 I/O status indicators
16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

Output Point 0 (O00)

Output Point 1 (O01)

Output Point 5 (O05)

Output Point 7 (O07)

Output Point 11 (O11)

Output Point 3 (O03)

Output Point 8 (O08)

Output Point 9 (O09)
Output Point 10 (O10)

Output Point 12 (O12)

Output Point 13 (O13)

Output Point 15 (O15)

Output Point 2 (O02)

Output Point 4 (O04)

Output Point 6 (O06)

Output Point 14 (O14)

Top row

Output Point 26 (O26)

Output Point 16 (O16)

Output Point 19 (O19)

Output Point 28 (O28)

Output Point 17 (O17)
Output Point 18 (O18)

Output Point 20 (O20)

Output Point 21 (O21)

Output Point 30 (O30)

Output Point 31 (O31)
Output Point 23 (O23)

Output Point 27 (O27)

Output Point 24 (O24)
Output Point 25 (O25)

Output Point 29 (O29)

Output Point 22 (O22)
Bottom row

Table 27 describes the I/O Status indicators on FLEX 5000 output modules.
Table 27 - I/O Status Indicators - FLEX 5000 Output Modules
Indicator State Description Recommended Action
One of the following:
One of the following: • Confirm that the output point is configured
Off • The output point is Off. properly.
• There is no backplane power. • Confirm that there is backplane power supplied
through the FLEX 5000 EtherNet/IP adapter.
Steady yellow The output point is operating normally. None
• One of the following:
One of the following:
• Locate and correct the cause of No Load or
• A No Load or Short Circuit condition is
Flashing red Short Circuit condition.
detected.
• Locate and correct the cause of Field Power
• A Field Power Loss condition exists. Loss condition.

108 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix A Troubleshoot Your Module

Figure 20 show the status indicators on FLEX 5000 AC output modules.

Figure 20 - FLEX 5000 AC Output Modules Status Indicators
5094-OA16, 5094-OA16XT

POWER STATUS
FLEX 5000 I/O
TM

Module status indicator

SA power status indicator

5094-OA16 DIGITAL 16 OUTPUT AC 4 3 TB3AC

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 I/O status indicators

Output Point 13 (O13)

Output Point 5 (O05)

Output Point 10 (O10)

Output Point 14 (O14)

Output Point 15 (O15)
Output Point 4 (O04)

Output Point 11 (O11)

Output Point 12 (O12)
Output Point 1 (O01)

Output Point 7 (O07)

Output Point 8 (O08)
Output Point 6 (O06)
Output Point 0 (O00)

Output Point 2 (O02)

Output Point 3 (O03)

Output Point 9 (O09)

Table 28 describes the I/O Status indicators on FLEX 5000 output modules.
Table 28 - I/O Status Indicators - FLEX 5000 Output Modules
Indicator State Description Recommended Action
One of the following:
One of the following: • Confirm that the output point is configured
Off • The output point is Off. properly.
• There is no backplane power. • Confirm that there is backplane power supplied
through the FLEX 5000 EtherNet/IP adapter.
Steady yellow The output point is operating normally. None
One of the following:
One of the following: • Locate and correct the cause of No Load or
Flashing red • A No Load or Short Circuit condition is detected. Short Circuit condition.
• A Field Power Loss condition exists. • Locate and correct the cause of Field Power
Loss condition.

Figure 21 show the status indicators on FLEX 5000 relay output modules.
Figure 21 - FLEX 5000 Relay Output Module Status Indicators
5094-OW8I, 5094-OW8IXT

FLEX 5000 I/O

TM
POWER STATUS

Module status indicator

SA power status indicator

5094-OW8I RELAY 8 OUTPUT ISOLATED 2 2 TB3W

0 1 2 3 4 5 6 7 I/O status indicators
Output Point 3 (O03)

Output Point 6 (O06)

Output Point 1 (O01)

Output Point 2 (O02)

Output Point 4 (O04)

Output Point 0 (O00)

Output Point 5 (O05)

Output Point 7 (O07)

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 109

Appendix A Troubleshoot Your Module

Table 29 describes the I/O Status indicators on FLEX 5000 relay output
modules.
Table 29 - I/O Status Indicators - FLEX 5000 Relay Output Modules
Indicator State Description Recommended Action
One of the following:
One of the following: • Confirm that the output point is configured
properly.
Off • The output point is Off.
• Confirm that there is backplane power
• There is no backplane power. supplied through the FLEX 5000 EtherNet/
IP adapter.
Steady yellow The output point is operating normally. None
Locate and correct the cause of field power
Flashing red A Field Power Loss condition exists. loss condition.

FLEX 5000 Safety Input Figure 22 shows the status indicators on FLEX 5000 safety input modules.
Modules Status Indicators Figure 22 - FLEX 5000 Safety Input Modules

FLEX 5000 I/O

TM
POWER STATUS

Module status indicator

SA power status indicator

5094-IB16S SAFETY DIGITAL 16 INPUT 24 VDC 5 5 TB3I

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 I/O status indicators
Input Point 11 (I11)
Input Point 6 (I06)
Input Point 1 (I01)

Input Point 14 (I14)

Input Point 8 (I08)
Input Point 2 (I02)
Input Point 3 (I03)

Input Point 9 (I09)

Input Point 12 (I12)

Input Point 0 (I00)

Input Point 4 (I04)

Input Point 5 (I05)

Input Point 7 (I07)

Input Point 10 (I10)

Input Point 13 (I13)

Input Point 15 (I15)

Table 30 - I/O Status Indicators - FLEX 5000 Safety Input Modules

Indicator State Description Recommended Action
One of the following:
One of the following:
• Confirm that the input point is configured properly.
Off • The input point is Off.
• Confirm that there is backplane power supplied
• There is no backplane power.
through the FLEX 5000 EtherNet/IP adapter.
Steady yellow The input point is operating normally. None
Flashing red Recoverable faults. Locate and correct faults.
• Locate and correct the cause of field power loss
• A Field Power Loss condition exists.
Steady red condition.
• Internal channel fault. • Locate and correct the internal fault.

110 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix A Troubleshoot Your Module

FLEX 5000 Safety Output Figure 23 shows the status indicators on FLEX 5000 safety output modules.
Modules Status Indicators Figure 23 - FLEX 5000 Safety Output Modules

FLEX 5000 I/O

TM
POWER STATUS

Module status indicator

SA power status indicator

5094-OB16S SAFETY DIGITAL 16 OUTPUT 24 VDC 5 1 TB3I

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 I/O status indicators

Output Point 3 (O03)

Output Point 7 (O07)

Output Point 10 (O10)

Output Point 12 (O12)

Output Point 15 (O15)

Output Point 0 (O00)

Output Point 2 (O02)

Output Point 1 (O01)

Output Point 4 (O04)

Output Point 5 (O05)

Output Point 8 (O08)

Output Point 11 (O11)

Output Point 13 (O13)

Output Point 14 (O14)
Output Point 9 (O09)
Output Point 6 (O06)
Table 31 - I/O Status Indicators - FLEX 5000 Safety Output Modules
Indicator State Description Recommended Action
One of the following:
One of the following:
• Confirm that the output point is configured properly.
Off • The output point is Off.
• Confirm that there is backplane power supplied through
• There is no backplane power. the FLEX 5000 EtherNet/IP adapter.
Steady yellow The output point is operating normally. None
A No Load or Short Circuit condition is Locate and correct the cause of No Load or Short Circuit
Flashing red detected. condition.
One of the following:
One of the following:
• A Field Power Loss condition exists. • condition.
Locate and correct the cause of field power loss
Steady red
• Internal channel fault. • Locate and correct the internal fault.

FLEX 5000 Safety Relay Figure 24 shows the status indicators on FLEX 5000 safety relay output
Output Modules modules.

Status Indicators Figure 24 - FLEX 5000 Safety Relay Output Modules

FLEX 5000 I/O

TM
POWER STATUS

Module status indicator

SA power status indicator

5094-OW4IS SAFETY RELAY 4 OUTPUT ISOLATED 2 3 TB3W

0 1 2 3 I/O status indicators
Output Point 0 (O00)

Output Point 1 (O01)

Output Point 3 (O03)

Output Point 2 (O02)

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 111

Appendix A Troubleshoot Your Module

Table 32 - I/O Status Indicators - FLEX 5000 Safety Relay Output Modules
Indicator State Description Recommended Action
One of the following:
One of the following:
• Confirm that the output point is configured properly.
Off • The output point is Off.
• Confirm that there is backplane power supplied through
• There is no backplane power. the FLEX 5000 EtherNet/IP adapter.
The output point is operating
Steady yellow None
normally.
One of the following:
One of the following:
• Locate and correct the cause of Field Power Loss
Steady red • A Field Power Loss condition exists. condition.
• Internal channel fault. • Locate and correct internal fault.

Use the Logix Designer In addition to the status indicator display on the module, the Logix Designer
Application for application indicates the presence of fault conditions.

Troubleshooting Fault conditions are reported in the following ways:

• Warning Signal in the I/O Configuration Tree
Applies to these modules:
• Status and Fault Information in Module Properties Categories
5094 Standard I/O Modules
• Logix Designer Application Tag Editor
5094 Safety I/O Modules

Warning Signal in the I/O Configuration Tree

As shown in Figure 25, a warning icon appears in the I/O Configuration tree
when a fault occurs.
Figure 25 - Warning Icon in Controller Organizer

Status and Fault Information in Module Properties Categories

The Module Properties section in the Logix Designer application includes a
series of categories. The numbers and types of categories varies by module
type.

Each category includes options to configure the module or monitor the status
of the module. The following are ways to monitor the state of a module for
faults:
• Module Status on General Category
• Module Fault Descriptions on Connection Category

112 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix A Troubleshoot Your Module

• Module Fault Descriptions on Module Info Category

• Module Diagnostics Dialog Box
• Point Diagnostics

Module Status on General Category

As shown in Figure 26, the status of a module is indicated on the General

category of the Modules Properties.
Figure 26 - Fault Message in Status Line

Module Fault Descriptions on Connection Category

As shown in Figure 27, a module fault description that includes an error code
that is associated with the specific fault type is listed on the Connection
category.
Figure 27 - Fault Description with Error Code

Module Fault Descriptions on Module Info Category

As shown in Figure 28, major and minor fault information is listed on the
Module Info category.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 113

Appendix A Troubleshoot Your Module

Figure 28 - Major and Minor Fault Information

Module Diagnostics Dialog Box

Module Diagnostics are accessible from the Module Info category on the
Module Properties dialog box, as shown in Figure 29.

You can use diagnostics in a Logix Designer project to monitor module

operating conditions and to troubleshoot issues that affect a module. You can
use diagnostics only when the project is online.

Module diagnostics provide information on a module-wide basis. For example,

the Module Diagnostics dialog box indicates the mode within which a module
is operating, that is, Run, Remote Run, Remote Program, or Program.
Figure 29 - Module Diagnostics

114 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix A Troubleshoot Your Module

Point Diagnostics

You can use diagnostics in a Logix Designer project to monitor module and/or
point operating conditions and to troubleshoot issues that affect a module
and/or point. You can use diagnostics only when the project is online.

Point diagnostics provide information on an individual point basis. For

example, you can check individual points on a 5094-IB16S or 5094-IB16SXT
safety input module for the presence of a Short Circuit condition.

Remember the following:

• Not all FLEX 5000 I/O digital modules provide point diagnostics.
• The point diagnostics that are available vary by module type and
functionality.
• There are some differences between modules, but most commonly, the
Module Properties dialog box category from which you can access point
diagnostics is Points.

Figure 30 shows how to access output point diagnostics on the 5094-OB16S

module and the diagnostics dialog box.
Figure 30 - Point Diagnostics

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 115

Appendix A Troubleshoot Your Module

Logix Designer Application Tag Editor

Figure 31 show how fault conditions are indicated in the controller tags for the
module.
Figure 31 - Fault Indication in Controller Tags

116 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix B

Module Tag Definitions

Topic Page
Tag Name Conventions 118
Access the Tags 118
5094-IA16 Module Tags 119
5094-IM8 Module Tags 120
5094-IB16 Module Tags 122
5094-IB32 Module Tags 128
5094-OA16 Module Tags 134
5094-OB8 Module Tags 135
5094-OB16 Module Tags 137
5094-OB32 Module Tags 138
5094-OW8I Module Tags 140
5094-IB16S Module Tags 142
5094-OB16S Module Tags 144
5094-OW4IS Module Tags 145

Module tags are created when you add a module to the Logix Designer
application project. XT and non-XT modules use the same module tag
definitions. For instance, the 5094-OB16SXT module uses the same module tag
definitions as the 5094-OB16S module.

The set of module tags associated with a module depends on the module type
and Module Definition choices made during module configuration. For
example, if you use a Listen Only Connection, the Logix Designer application
creates only Input tags for that module.

The following types of tags are available with FLEX 5000 I/O modules:
• Configuration
• Event Input – 5094-IB16, 5094-IB16XT, 5094-IB32, and 5094-IB32XT
modules only
• Event Output – 5094-IB16, 5094-IB16XT, 5094-IB32, and 5094-IB32XT
modules only
• Input
• Output
The tables contained in this section list all of the tags available with a module.
Not all tags in the list are used when that module type is added to a project. Tag
use varies by module configuration.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 117

Appendix B Module Tag Definitions

Tag Name Conventions The module tag names use defined naming conventions. The conventions are
as follows:
Applies to these modules:
5094 Standard I/O Modules Example tag name = Adapter1:I.Pt00.Data
5094 Safety I/O Modules
• Adapter = name of the FLEX 5000 EtherNet/IP adapter in the FLEX 5000
I/O system
• 1 = slot number
• I = tag type
The possible FLEX 5000 I/O tag types are C (configuration), EI (event
input), EO (event output), I (input), and O (output)
• Pt00 = module point number
• Data = tag function
In this case, Data represents the input data that is returned to the owner-
controller.

Access the Tags You view tags from the Tag Editor.
1. Open your Logix Designer application project.
Applies to these modules:
2. Right-click Controller Tags and choose Monitor Tags.
5094 Standard I/O Modules
5094 Safety I/O Modules

3. Open the tags as necessary to view specific tags.

118 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix B Module Tag Definitions

5094-IA16 Module Tags This section describes the tags that are associated with the 5094-IA16 module.
Applies to these modules:
5094 Standard I/O Modules
Configuration Tags
Table 33 describes the 5094-IA16 module configuration tags.
Table 33 - 5094-IA16 Module Configuration Tags
Name Data Type Definition Valid Values
The amount of time that a signal must be in the on state
before the input data indicates the on state.
The amount of time is indicated using an enumeration. Not all
Ptxx.InputOffOnFilter SINT • 13 = 1 ms
products support all enumeration values.
Ptxx depends on the number of counters that have been
configured.
The amount of time that a signal must be in the off state
before the input data indicates the off state.
The amount of time is indicated using an enumeration. Not all • 16 = 10 ms
Ptxx.InputOnOffFilter SINT products support all enumeration values. • 17 = 20 ms
Ptxx depends on the number of counters that have been
configured.
Determines whether the point faults when no field power is
present. • 0 = Field Power/SA Power Diagnostics is not sent to
• If the input is powered from the SA, select this checkbox to the controller.
Pt0x.FieldPowerDiagEn BOOL monitor the status of the SA power. • 1 = Field Power/SA Power Diagnostics is sent to the
• If the input is powered from another power supply, do not controller. Use this if the sensor uses the SA power
select this checkbox, so that the input continues to work in the terminal base.
even when there is no SA power

Input Tags
Table 34 describes the 5094-IA16 module input tags.
Table 34 - 5094-IA16 Module Input Tags
Name Data Type Definition Valid Values
• 0 = Idle
RunMode BOOL The point’s operating state
• 1 = Run Mode
Indicates if a connection is running. • 0 = Connection running
ConnectionFaulted BOOL The module sets this tag to 0 when connected. If the module
is not connected, it changes the tag to 1. • 1 = Connection not running
• 0 = No diagnostics active
Indicates if any diagnostics are active or if the prognostics
DiagnosticActive BOOL threshold is reached. • 1 = One or more diagnostics are active or the
prognostics threshold is reached
Increments for each time a distinct diagnostic condition is
detected, and when a distinct diagnostic condition transitions -128…+127
DiagnosticSequenceCount SINT from detected to not detected. The value of 0 is skipped except during module
Set to zero by product reset or power cycle. Wraps from 255 powerup.
(-1) to 1, skipping zero.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 119

Appendix B Module Tag Definitions

Table 34 - 5094-IA16 Module Input Tags (Continued)

Name Data Type Definition Valid Values
• 0 = Off
Ptxx.Data BOOL Indicates the current digital input value.
• 1 = On
• 0 = Good
• 1 = Bad, causing fault
The typical causes of uncertain data are the
following:
Indicates that point data is inaccurate and cannot be trusted – Field Power Loss condition
for use in the application. – No Load condition
Ptxx.Fault BOOL For more information, see Module Data Quality Reporting on – Short Circuit condition
page 36. If the tag is set to 1, you must troubleshoot the
module to correct the cause of the inaccuracy.
IMPORTANT: Once the condition that causes the
tag to change to 1 is removed, the tag automatically
resets to 0.
• 0 = Good data
Indicates that the point data can be inaccurate but the • 1 = Uncertain data
degree of inaccuracy is not known. If the tag is set to 1, you must troubleshoot the
Ptxx.Uncertain BOOL module to correct the cause of the inaccuracy.
For more information, see Module Data Quality Reporting on
page 36. IMPORTANT: Once the condition that causes the
tag to change to 1 is removed, the tag automatically
resets to 0.

5094-IM8 Module Tags This section describes the tags that are associated with the 5094-IM8 module.
Applies to these modules:
5094 Standard I/O Modules
Configuration Tags
Table 35 describes the 5094-IM8 module configuration tags.
Table 35 - 5094-IM8 Module Configuration Tags
Name Data Type Definition Valid Values
The amount of time that a signal must be in the on state
before the input data indicates the on state. • 13 = 1 ms
The amount of time is indicated using an enumeration. Not all
Ptxx.InputOffOnFilter SINT • 14 = 2 ms
products support all enumeration values.
Ptxx depends on the number of counters that have been • 15 = 5 ms
configured.
The amount of time that a signal must be in the off state
before the input data indicates the off state. • 15 = 5 ms
The amount of time is indicated using an enumeration. Not all
Ptxx.InputOnOffFilter SINT • 16 = 10 ms
products support all enumeration values.
Ptxx depends on the number of counters that have been • 17 = 20 ms
configured.
Determines whether the point faults when no field power is
present. • 0 = Field Power/SA Power Diagnostics is not sent to
• If the input is powered from the SA, select this checkbox to the controller.
Pt0x.FieldPowerDiagEn BOOL monitor the status of the SA power. • 1 = Field Power/SA Power Diagnostics is sent to the
• If the input is powered from another power supply, do not controller. Use this if the sensor uses the SA power
select this checkbox, so that the input continues to work in the terminal base.
even when there is no SA power

120 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix B Module Tag Definitions

Input Tags
Table 36 describes the 5094-IM8 module input tags.
Table 36 - 5094-IM8 Module Input Tags
Name Data Type Definition Valid Values
• 0 = Idle
RunMode BOOL The point’s operating state
• 1 = Run Mode
Indicates if a connection is running. • 0 = Connection running
ConnectionFaulted BOOL The module sets this tag to 0 when connected. If the module
is not connected, it changes the tag to 1. • 1 = Connection not running
• 0 = No diagnostics active
Indicates if any diagnostics are active or if the prognostics
DiagnosticActive BOOL • 1 = One or more diagnostics are active or the
threshold is reached.
prognostics threshold is reached
Increments for each time a distinct diagnostic condition is
detected, and when a distinct diagnostic condition transitions -128…+127
DiagnosticSequenceCount SINT from detected to not detected. The value of 0 is skipped except during module
Set to zero by product reset or power cycle. Wraps from 255 powerup.
(-1) to 1, skipping zero.
• 0 = Off
Ptxx.Data BOOL Indicates the current digital input value.
• 1 = On
• 0 = Good
• 1 = Bad, causing fault
The typical causes of uncertain data are the
following:
Indicates that point data is inaccurate and cannot be trusted – Field Power Loss condition
for use in the application. – No Load condition
Ptxx.Fault BOOL For more information, see Module Data Quality Reporting on – Short Circuit condition
page 36. If the tag is set to 1, you must troubleshoot the
module to correct the cause of the inaccuracy.
IMPORTANT: Once the condition that causes the
tag to change to 1 is removed, the tag automatically
resets to 0.
• 0 = Good data
Indicates that the point data can be inaccurate but the • 1 = Uncertain data
degree of inaccuracy is not known. If the tag is set to 1, you must troubleshoot the
Ptxx.Uncertain BOOL module to correct the cause of the inaccuracy.
For more information, see Module Data Quality Reporting on
page 36. IMPORTANT: Once the condition that causes the
tag to change to 1 is removed, the tag automatically
resets to 0.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 121

Appendix B Module Tag Definitions

5094-IB16 Module Tags This section describes the tags that are associated with the 5094-IB16 module.
Applies to these modules:
5094 Standard I/O Modules
Configuration Tags
Table 37 describes the 5094-IB16 module configuration tags.
Table 37 - 5094-IB16 Module Configuration Tags
Name Data Type Definition Valid Values
• 9 = 0 µs
• 10 = 100 µs
• 11 = 200 µs
The amount of time that a signal must be in the on state • 12 = 500 µs
before the input data indicates the on state. • 13 = 1 ms
Counterxx.InputOffOnFilter SINT The amount of time is indicated using an enumeration. Not all • 14 = 2 ms
products support all enumeration values. • 15 = 5 ms
• 16 = 10 ms
• 17 = 20 ms
• 18 = 50 ms
• 9 = 0 µs
• 10 = 100 µs
• 11 = 200 µs
The amount of time that a signal must be in the off state • 12 = 500 µs
before the input data indicates the off state. • 13 = 1 ms
Counterxx.InputOnOffFilter SINT The amount of time is indicated using an enumeration. Not all • 14 = 2 ms
products support all enumeration values. • 15 = 5 ms
• 16 = 10 ms
• 17 = 20 ms
• 18 = 50 ms
Determines whether the point faults when no field power is
present. • 0 = Field Power/SA Power Diagnostics is not sent to
• If the input is powered from the SA, select this checkbox to the controller.
FieldPowerDiagEN BOOL monitor the status of the SA power. • 1 = Field Power/SA Power Diagnostics is sent to the
• If the input is powered from another power supply, do not controller. Use this if the sensor uses the SA power
select this checkbox, so that the input continues to work in the terminal base.
even when there is no SA power
Determines whether the simple counter will rollover to 0 • 0 = Maximum value
Counterxx.RolloverAtPreset BOOL when it reaches O:Preset (1) or at 2147483647 (0). • 1 = Preset value
• 9 = 0 µs
• 10 = 100 µs
The amount of time that a signal must be in the on state • 11 = 200 µs
before the input data indicates the on state. • 12 = 500 µs
The amount of time is indicated using an enumeration. Not all • 13 = 1 ms
Ptxx.InputOffOnFilter SINT products support all enumeration values. • 14 = 2 ms
Ptxx depends on the number of counters that have been • 15 = 5 ms
configured. • 16 = 10 ms
• 17 = 20 ms
• 18 = 50 ms
• 9 = 0 µs
• 10 = 100 µs
The amount of time that a signal must be in the off state • 11 = 200 µs
before the input data indicates the off state. • 12 = 500 µs
The amount of time is indicated using an enumeration. Not all • 13 = 1 ms
Ptxx.InputOnOffFilter SINT products support all enumeration values. • 14 = 2 ms
Ptxx depends on the number of counters that have been • 15 = 5 ms
configured. • 16 = 10 ms
• 17 = 20 ms
• 18 = 50 ms
Ptxx.ChatterTime INT A value from 1…10000 ms in whole ms increments. 1…10000
• 0 = Disabled
Ptxx.ChatterCount SINT The number of input changes that are considered Chatter.
• 2…127 = Enabled

122 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix B Module Tag Definitions

Table 37 - 5094-IB16 Module Configuration Tags (Continued)

Name Data Type Definition Valid Values
• 0 = Capture disabled for OFF to ON input transitions
Enables capturing Off to On time stamps. If cleared, the point
Ptxx.CaptureOffOnEn BOOL • 1 = Capture enabled (default) for OFF to ON input
does not record Off to On time stamps.
transitions
• 0 = Capture disabled for ON to OFF input transitions
Enables capturing On to Off time stamps. If cleared, the point
Ptxx.CaptureOnOffEn BOOL • 1 = Capture enabled (default) for ON to OFF input
does not record On to Off time stamps.
transitions
When this bit is set, timestamps are latched; this means that
a Timestamp is not overwritten until acknowledged. All
subsequent transitions on that point are ignored until
acknowledged/reset. If the bit is not set, the new LO • 0 = Timestamps are overridden with each
Timestamp overwrites the first LO Timestamp immediately, successive COS transition.
Ptxx.TimestampLatchEn BOOL even if the controller has yet to extract that data.
Timestamp can also be acknowledged by writing • 1 = Timestamps are latched until acknowledged.
I:TimestampxxNumber to O:TimestampxxNumberAck. This
clears the I:Timestampxx and I:TimestampOverflowxx (where
xx = OnOff or OffOn).

Input Tags
Table 38 describes the 5094-IB16 module input tags.
Table 38 - 5094-IB16 Module Input Tags
Name Data Type Definition Valid Values
• 0 = Idle
RunMode BOOL The point’s operating state
• 1 = Run
Indicates if a connection is running. • 0 = Good
ConnectionFaulted BOOL The module sets this tag to 0 when connected. If the module
is not connected, it changes the tag to 1. • 1 = Bad
• 0 = No diagnostics active
Indicates if any diagnostics are active or if the prognostics
DiagnosticActive BOOL • 1 = One or more diagnostics are active or the
threshold is reached.
prognostics threshold is reached
• 0 = CIP Sync is not available
CIPSyncValid BOOL Indicates whether the module is synced with a 1588 master.
• 1 = CIP Sync is available
• 0 = A valid time master has not timed out
Indicates that the module was once synced with a 1588 • 1 = A valid time master was detected on the
CIPSyncTimeout BOOL backplane, but the time master has timed out. The
master, but is not now due to a timeout.
module is using its local clock and can be drifting
away from the last known master time.
Increments for each time a distinct diagnostic condition is
detected, and when a distinct diagnostic condition transitions -128…+127
DiagnosticSequenceCount SINT from detected to not detected. The value of 0 is skipped except during module
Set to zero by product reset or power cycle. Wraps from 255 powerup.
(-1) to 1 skipping zero.
• 0 = Off
Counterxx.Data BOOL Indicates the current digital input value.
• 1 = On
• 0 = Good
Indicates that counter data is inaccurate and cannot be • 1 = Bad, causing fault
trusted for use in the application. If the tag is set to 1, you must troubleshoot the
Counterxx.Fault BOOL module to correct the cause of the inaccuracy.
For more information, see Module Data Quality Reporting on
page 36. IMPORTANT: Once the condition that causes the
tag to change to 1 is removed, the tag automatically
resets to 0.
• 0 = Good data
• 1 = Uncertain data
Indicates that the counter data can be inaccurate but the
degree of inaccuracy is not known. If the tag is set to 1, you must troubleshoot the
Counterxx.Uncertain BOOL module to correct the cause of the inaccuracy.
For more information, see Module Data Quality Reporting on
page 36. IMPORTANT: Once the condition that causes the
tag to change to 1 is removed, the tag automatically
resets to 0.
When set, indicates the corresponding counter Done bit • 0 = Corresponding Done bit did not trigger the event
Counterxx.Done BOOL (rising or falling depending on configuration) triggered the
event. • 1 = Corresponding Done bit triggered the event

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 123

Appendix B Module Tag Definitions

Table 38 - 5094-IB16 Module Input Tags (Continued)

Name Data Type Definition Valid Values
The counter counted up to Preset -1 and continued counting • 0 = Counter has not counted up to Preset - 1
from or 0.
Counterxx.Rollover BOOL • 1 = Counter counted up to Preset - 1 and continued
The O:RolloverAck bit transitioning from 0 to 1 or the O:Reset
transitioning from 0 to 1 clears this bit. counting from 0.
Counterxx.Count DINT The number of input transitions counted by a counter. All values.
• 0 = CIP Sync is not available
EventStatus[x].CIPSyncValid BOOL Indicates whether the module is synced with a 1588 master.
• 1 = CIP Sync is available
• 0 = A valid time master has not timed out
Indicates that the module was once synced with a 1588 • 1 = A valid time master was detected on the
EventStatus[x].CIPSyncTimeout BOOL backplane, but the time master has timed out. The
master, but is not now due to a timeout.
module is using its local clock and can be drifting
away from the last known master time.
Indicates when an event has been discarded because events • 0 = An event status has not been dropped
EventStatus[x].EventDropped BOOL are occurring faster than they are being acknowledged. • 1 = An event status has been dropped
When EO.Event[<n>].ResetEvent transitions from 0 to 1,
I.EventStatus[<n>].EventReset transitions to 1 to indicate that • 0 = Do not reset
EventStatus[x].EventReset BOOL the reset was received and completed. It stays 1 until • 1 = Reset
EO.Event[<n>].ResetEvent transition to zero.
The number of events currently queued in the modules. A
EventStatus[x].EventsPending SINT value greater than zero indicates that the controller is not All positive values.
currently keeping up with the rate of events.
Running count of events, which increments by one each new
time event. The originator sets the Event Number Ack to the
EventStatus[x].EventNumber DINT Event Number to acknowledge receipt of the event. When All values.
the EventNumber reaches it maximum value and rolls over it
is to roll over to 1, not 0.
• 0 = Off
Ptxx.Data BOOL Indicates the current digital input value.
• 1 = On
• 0 = Good
Indicates that point data is inaccurate and cannot be trusted • 1 = Bad, causing fault
for use in the application. If the tag is set to 1, you must troubleshoot the
Ptxx.Fault BOOL module to correct the cause of the inaccuracy.
For more information, see Module Data Quality Reporting on
page 36. IMPORTANT: Once the condition that causes the
tag to change to 1 is removed, the tag automatically
resets to 0.
• 0 = Good data
Indicates that the point data can be inaccurate but the • 1 = Uncertain data
degree of inaccuracy is not known. If the tag is set to 1, you must troubleshoot the
Ptxx.Uncertain BOOL module to correct the cause of the inaccuracy.
For more information, see Module Data Quality Reporting on
page 36. IMPORTANT: Once the condition that causes the
tag to change to 1 is removed, the tag automatically
resets to 0.
Indicates if the input is chattering per the ChatterTime and • 0 = Normal
Ptxx.Chatter BOOL ChatterCount settings. • 1 = Input is chattering
Indicates an Off to On time stamp was lost in a discrete
product. If TimestampLatchEn is set then a new time stamp 0 or 1
Ptxx.TimestampOverflowOffOn BOOL was not recorded because one is already latched. If
TimestampLatchEn is clear a timestamp was overwritten.
Indicates an On to Off time stamp was lost in a discrete
product. If TimestampLatchEn is set then a new time stamp 0 or 1
Ptxx.TimestampOverflowOnOff BOOL was not recorded because one is already latched. If
TimestampLatchEn is clear a timestamp was overwritten.
• 0 = CIP Sync is not available
Ptxx.CIPSyncValid BOOL Indicates whether the module is synced with a 1588 master.
• 1 = CIP Sync is available
• 0 = A valid time master has not timed out.
Indicates that the module was once synced with a 1588 • 1 = A valid time master was detected on the
Ptxx.CIPSyncTimeout BOOL backplane, but the time master has timed out. The
master, but is not now due to a timeout.
module is using its local clock and can be drifting
away from the last known time master.
An Off to On timestamp identifier for the currently produced All values.
Ptxx.TimestampOffOnNumber INT timestamp.

124 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix B Module Tag Definitions

Table 38 - 5094-IB16 Module Input Tags (Continued)

Name Data Type Definition Valid Values
An On to Off timestamp identifier for the currently produced All values.
Ptxx.TimestampOnOffNumber INT timestamp.
64 bit Timestamp corresponding to when a change of state All values.
Ptxx.TimestampOffOn LINT Off to On was recorded at the input.
64 bit Timestamp corresponding to when a change of state All values.
Ptxx.TimestampOnOff LINT On to Off was recorded at the input.

Output Tags
Table 39 describes the 5094-IB16 module output tags. The 5094-IB16 module
output tags are only available if you have enabled counters in the Module
Definition dialog box.
Table 39 - 5094-IB16 Module Output Tags
Name Data Type Definition Valid Values
When this bit transitions from 0 to 1 I:Count and I:Rollover are • 0 = I:Count and I:Rollover values are not set to 0
Counterxx.Reset BOOL set to zero. • 1 = I:Count and I:Rolloever values are set to 0
Clears the Rollover bit in the input tag when it transitions from • 0 = I:Rollover bit is not cleared
Counterxx.RolloverAck BOOL 0 to 1. • 1 = I:Rollover bit is cleared
• If RolloverAtPreset is set, the counter counts to the Preset
value and then rolls over to zero.
• If RolloverAtPreset is not set, the counter sets the Done bit
and continues counting up to Max DINT.
Counterxx.Preset DINT • If C:RolloverAtPreset = 1, then if I:Count ≥ O:Preset, 0…2,147,483,647
I:Count=0, else I:Done bit always = 0. Set I:Rollover bit when
I:Count transitions from O:Preset – 1 to 0.
• If C:RolloverAtPreset = 0, then if I:Count ≥ O:Preset, I:Done =
1, else I:Done = 0. Set I:Rollover bit when I:Count transitions
from 2,147,483,647 to 0.
Erases all recorded timestamps for the input point when it • 0 = Timestamps are not erased
Ptxx.ResetTimestamps BOOL transitions from 0 to 1. • 1 = Timestamps are erased
An Off to On timestamp identifier that is written by the
controller to indicate that the identified timestamp has been
seen and acted on. When Latching is enabled and the
Ptxx.TimestampOffOnNumberAck INT All values.
Timestamp Number that is received from the controller
matches the most recent timestamp that is produced, the
module is then allowed to produce a new timestamp.
An On to Off timestamp identifier that is written by the
controller to indicate that the identified timestamp has been
seen and acted on. When Latching is enabled and the
Ptxx.TimestampOnOffNumberAck INT All values.
Timestamp Number that is received from the controller
matches the most recent timestamp that is produced, the
module is then allowed to produce a new timestamp.

Event Input Tags

Table 40 describes the 5094-IB16 module event input tags. The event input tags
are displayed only if Data with Events is selected in the Module Definition
window.
Table 40 - 5094-IB16 Module Event Input Tags
Name Data Type Definition Valid Values
• 0 = Idle
RunMode BOOL The point’s operating state
• 1 = Run Mode
Indicates if a connection is running. • 0 = Connection running
ConnectionFaulted BOOL The module sets this tag to 0 when connected. If the module
is not connected, it changes the tag to 1. • 1 = Connection not running
• 0 = No diagnostics active
Indicates if any diagnostics are active or if the prognostics
Diagnostic Active BOOL • 1 = One or more diagnostics are active or the
threshold is reached.
prognostics threshold is reached

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 125

Appendix B Module Tag Definitions

Table 40 - 5094-IB16 Module Event Input Tags (Continued)

Name Data Type Definition Valid Values
Increments for each time a distinct diagnostic condition is
detected, and when a distinct diagnostic condition transitions -128…+127
DiagnosticSequence Count SINT from detected to not detected. The value of 0 is skipped except during module
Set to zero by product reset or power cycle. Wraps from 255 powerup.
(-1) to 1 skipping zero.
Eventx BOOL Indicates the number of the event. 0…3
• 0 = Good
Indicates that point data is inaccurate and cannot be trusted • 1 = Bad, causing fault
for use in the application. If the tag is set to 1, you must troubleshoot the
Eventx.PtxxFault BOOL module to correct the cause of the inaccuracy.
For more information, see Module Data Quality Reporting on
page 36. IMPORTANT: Once the condition that causes the
tag to change to 1 is removed, the tag automatically
resets to 0.
• 0 = Good data
Indicates that the point data can be inaccurate but the • 1 = Uncertain data
degree of inaccuracy is not known. If the tag is set to 1, you must troubleshoot the
Eventx.Uncertain BOOL module to correct the cause of the inaccuracy.
For more information, see Module Data Quality Reporting on
page 36. IMPORTANT: Once the condition that causes the
tag to change to 1 is removed, the tag automatically
resets to 0.
Indicates when an event has been discarded because events • 0 = An event status has not been dropped.
Eventx.EventDropped BOOL are occurring faster than they are being acknowledged. • 1 = An event status has been dropped.
Indicates whether an event triggered when an input transition 0 or 1
Eventx.EventRising BOOL results in an event pattern being matched.
Indicates whether an event triggered when an input transition 0 or 1
Eventx.EventFalling BOOL resulted in an event pattern no longer being matched.
• 0 = CIP Sync is not available
Eventx.CIPSyncValid BOOL Indicates whether the module is synced with a 1588 master.
• 1 = CIP Sync is available
• 0 = A valid time master has not timed out.
Indicates that the module was once synced with a 1588 • 1 = A valid time master was detected on the
Eventx.CIPSyncTimeout BOOL backplane, but the time master has timed out. The
master, but is not now due to a timeout.
module is using its local clock and can be drifting
away from the last known time master.
The number of events currently queued in the modules. A
Eventx.EventsPending SINT value greater than 0 indicates that the controller is not All positive values.
currently keeping up with the rate of events.
Running count of events, which increments by one each new
time event. The originator sets the Event Number Ack to the
Eventx.EventNumber DINT Event Number to acknowledge receipt of the event. When the All values.
EventNumber reaches it maximum value and rolls over it is to
roll over to 1, not 0.
Eventx.EventTimestamp LINT The time the event occurred. All positive values.
• 0 = Corresponding counter Done bit did not trigger
When set, indicates the corresponding counter Done bit the event
Eventx.CounterxxDone BOOL (rising or falling depending on configuration) triggered the
event. • 1 = Corresponding counter Done bit triggered the
event
• 0 = Corresponding data value did not trigger the
When set, indicates the corresponding data value (rising or event
Eventx.PtxxData BOOL falling depending on configuration) triggered the event.
• 1 = Corresponding data value triggered the event
• 0 = Corresponding counter did not have a fault
When set, indicates that the corresponding counter had a indicated when the event occurred
Eventx.CounterxxFault BOOL fault indicated when the event occurred. • 1 = Corresponding counter did have a fault
indicated when the event occurred
Detects whether the signal is good data. The fault is set to 1 • 0 = Good
Eventx.Fault BOOL by the originator when the connection is lost. • 1 = Bad

126 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix B Module Tag Definitions

Event Output Tags

Table 41 describes the 5094-IB16 module event output tags. The event output
tags are displayed only if Data with Events is selected in the Module Definition
window.
Table 41 - 5094-IB16 Module Event Output Tags
Name Data Type Definition Valid Values
• 0 = Event trigger definition is not active and events
When set, the corresponding event trigger definition is active are not triggered when conditions match the definition
Eventxx.En BOOL and events are triggered when conditions match the
definition. • 1 = Event trigger definition is active and events are
triggered when conditions match the definition
When set an event is to trigger each time a condition change When Enable Independent Point Triggers = Checked
Eventxx.EventRisingEn BOOL results in conditions that match the event trigger definition. (EventRisingEn, EventFallingEn)
• Disable (0,0)
• On transition (1, 0)
• On inverted transition (0, 1)
• On any transition (1, 1)
When set an event is to trigger each time a condition change When Enable Independent Point Triggers = Unchecked
Eventxx.EventFallingEn BOOL results in conditions that no longer match the event trigger (EventRisingEn, EventFallingEn)
definition. • Disable (0, 0)
• On input transition to match pattern (1, 0)
• On input transition to not match pattern (0, 1)
• On input transition to match or not match pattern (1, 1)
When set, events are latched until acknowledged. A new
event is lost if the previous event has not been • 0 = Not latched (default)
Eventxx.LatchEn BOOL acknowledged. When not set, new events overwrite old • 1 = Latched
events.
When transitions from 0 to 1, resets all events and clears the • 0 = Events are not cleared.
Eventxx.ResetEvent BOOL event queue on the point. • 1 = Events are cleared when a rising edge occurs.
• 0 = When all selected conditions achieve the
For events, determines whether each condition that is configured values, an event is triggered.
Eventxx.IndependentConditionTriggerEn BOOL indicated in the trigger definition can initiate an event
independently. • 1 = When any selected condition achieves the
configured value, an event is triggered.
The controller writes back the EI:Event[<n>].EventNumber
into this EO:Event[<n>].EventNumberAck to indicate receipt All values.
Eventxx.EventNumberAck DINT of the event. All events with I:EventNumbers that occurred
before EventNumberAck is acknowledged.
• 0 = Corresponding counter does not participate in the
When set, indicates that the corresponding counter is to event trigger definition
Eventxx.CounterxxSelect BOOL participate in the event trigger definition. • 1 = Corresponding counter participates in the event
trigger definition
When set, indicates that the corresponding data value is to 0 or 1
Eventxx.PtxxDataSelect BOOL participate in the event trigger definition.
If the counter function is selected in the event trigger
Eventxx.CounterxxValue BOOL definition, this member indicates that value that is to trigger 0 or 1
the event.
• 0 = Input inactive
Eventxx.PtxxDataValue BOOL Indicates the input value of the event point data.
• 1 = Input active

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 127

Appendix B Module Tag Definitions

5094-IB32 Module Tags This section describes the tags that are associated with the 5094-IB32 module.
Applies to these modules:
5094 Standard I/O Modules
Configuration Tags
Table 42 describes the 5094-IB32 module configuration tags.
Table 42 - 5094-IB32 Module Configuration Tags
Name Data Type Definition Valid Values
• 9 = 0 µs
• 10 = 100 µs
• 11 = 200 µs
The amount of time that a signal must be in the on state • 12 = 500 µs
before the input data indicates the on state. • 13 = 1 ms
Counterxx.InputOffOnFilter SINT The amount of time is indicated using an enumeration. Not all • 14 = 2 ms
products support all enumeration values. • 15 = 5 ms
• 16 = 10 ms
• 17 = 20 ms
• 18 = 50 ms
• 9 = 0 µs
• 10 = 100 µs
• 11 = 200 µs
The amount of time that a signal must be in the off state • 12 = 500 µs
before the input data indicates the off state. • 13 = 1 ms
Counterxx.InputOnOffFilter SINT The amount of time is indicated using an enumeration. Not all • 14 = 2 ms
products support all enumeration values. • 15 = 5 ms
• 16 = 10 ms
• 17 = 20 ms
• 18 = 50 ms
Determines whether the simple counter will rollover to 0 • 0 = Maximum value
Counterxx.RolloverAtPreset BOOL when it reaches O:Preset (1) or at 2147483647 (0). • 1 = Preset value
• 9 = 0 µs
• 10 = 100 µs
The amount of time that a signal must be in the on state • 11 = 200 µs
before the input data indicates the on state. • 12 = 500 µs
The amount of time is indicated using an enumeration. Not all • 13 = 1 ms
Ptxx.InputOffOnFilter SINT products support all enumeration values. • 14 = 2 ms
Ptxx depends on the number of counters that have been • 15 = 5 ms
configured. • 16 = 10 ms
• 17 = 20 ms
• 18 = 50 ms
• 9 = 0 µs
• 10 = 100 µs
The amount of time that a signal must be in the off state • 11 = 200 µs
before the input data indicates the off state. • 12 = 500 µs
The amount of time is indicated using an enumeration. Not all • 13 = 1 ms
Ptxx.InputOnOffFilter SINT products support all enumeration values. • 14 = 2 ms
Ptxx depends on the number of counters that have been • 15 = 5 ms
configured. • 16 = 10 ms
• 17 = 20 ms
• 18 = 50 ms
Ptxx.ChatterTime INT A value from 1…10000 ms in whole ms increments. 1…10000
• 0 = Disabled
Ptxx.ChatterCount SINT The number of input changes that are considered Chatter.
• 2…127 = Enabled

128 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix B Module Tag Definitions

Table 42 - 5094-IB32 Module Configuration Tags (Continued)

Name Data Type Definition Valid Values
• 0 = Capture disabled for OFF to ON input transitions
Enables capturing Off to On time stamps. If cleared, the point
Ptxx.CaptureOffOnEn BOOL • 1 = Capture enabled (default) for OFF to ON input
does not record Off to On time stamps.
transitions
• 0 = Capture disabled for ON to OFF input transitions
Enables capturing On to Off time stamps. If cleared, the point
Ptxx.CaptureOnOffEn BOOL • 1 = Capture enabled (default) for ON to OFF input
does not record On to Off time stamps.
transitions
When this bit is set, timestamps are latched; this means that
a Timestamp is not overwritten until acknowledged. All
subsequent transitions on that point are ignored until
acknowledged/reset. If the bit is not set, the new LO • 0 = Timestamps are overridden with each
Timestamp overwrites the first LO Timestamp immediately, successive COS transition.
Ptxx.TimestampLatchEn BOOL even if the controller has yet to extract that data.
Timestamp can also be acknowledged by writing • 1 = Timestamps are latched until acknowledged.
I:TimestampxxNumber to O:TimestampxxNumberAck. This
clears the I:Timestampxx and I:TimestampOverflowxx (where
xx = OnOff or OffOn).

Input Tags
Table 43 describes the 5094-IB32 module input tags.
Table 43 - 5094-IB32 Module Input Tags
Name Data Type Definition Valid Values
• 0 = Idle
RunMode BOOL The point’s operating state
• 1 = Run
Indicates if a connection is running. • 0 = Good
ConnectionFaulted BOOL The module sets this tag to 0 when connected. If the module
is not connected, it changes the tag to 1. • 1 = Bad
• 0 = No diagnostics active
Indicates if any diagnostics are active or if the prognostics
DiagnosticActive BOOL • 1 = One or more diagnostics are active or the
threshold is reached.
prognostics threshold is reached
Indicates that the module is operating outside its designed • 0 = Good data
Uncertain BOOL operating range if data is under manual or override control. • 1 = Uncertain data
• 0 = CIP Sync is not available
CIPSyncValid BOOL Indicates whether the module is synced with a 1588 master.
• 1 = CIP Sync is available
• 0 = A valid time master has not timed out
Indicates that the module was once synced with a 1588 • 1 = A valid time master was detected on the
CIPSyncTimeout BOOL backplane, but the time master has timed out. The
master, but is not now due to a timeout.
module is using its local clock and can be drifting
away from the last known master time.
Increments for each time a distinct diagnostic condition is
detected, and when a distinct diagnostic condition transitions -128…+127
DiagnosticSequenceCount SINT from detected to not detected. The value of 0 is skipped except during module
Set to zero by product reset or power cycle. Wraps from 255 powerup.
(-1) to 1 skipping zero.
• 0 = Off
Counterxx.Data BOOL Indicates the current digital input value.
• 1 = On
• 0 = Good
Indicates that counter data is inaccurate and cannot be • 1 = Bad, causing fault
trusted for use in the application. • If the tag is set to 1, you must troubleshoot the
Counterxx.Fault BOOL module to correct the cause of the inaccuracy.
For more information, see Module Data Quality Reporting on
page 36. IMPORTANT: Once the condition that causes the
tag to change to 1 is removed, the tag automatically
resets to 0.
• 0 = Good data
Indicates that the counter data can be inaccurate but the • 1 = Uncertain data
degree of inaccuracy is not known. If the tag is set to 1, you must troubleshoot the
Counterxx.Uncertain BOOL module to correct the cause of the inaccuracy.
For more information, see Module Data Quality Reporting on
page 36. IMPORTANT: Once the condition that causes the
tag to change to 1 is removed, the tag automatically
resets to 0.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 129

Appendix B Module Tag Definitions

Table 43 - 5094-IB32 Module Input Tags (Continued)

Name Data Type Definition Valid Values
When set, indicates the corresponding counter Done bit • 0 = Corresponding Done bit did not trigger the event
Counterxx.Done BOOL (rising or falling depending on configuration) triggered the
event. • 1 = Corresponding Done bit triggered the event
The counter counted up to Preset -1 and continued counting • 0 = Counter has not counted up to Preset - 1
from or 0.
Counterxx.Rollover BOOL • 1 = Counter counted up to Preset - 1 and continued
The O:RolloverAck bit transitioning from 0 to 1 or the O:Reset
transitioning from 0 to 1 clears this bit. counting from 0.
Counterxx.Count DINT The number of input transitions counted by a counter. All values.
Indicates when an event has been discarded because events • 0 = An event status has not been dropped
EventStatus[x].EventDropped BOOL are occurring faster than they are being acknowledged. • 1 = An event status has been dropped
• 0 = CIP Sync is not available
EventStatus[x].CIPSyncValid BOOL Indicates whether the module is synced with a 1588 master.
• 1 = CIP Sync is available
• 0 = A valid time master has not timed out
Indicates that the module was once synced with a 1588 • 1 = A valid time master was detected on the
EventStatus[x].CIPSyncTimeout BOOL backplane, but the time master has timed out. The
master, but is not now due to a timeout.
module is using its local clock and can be drifting
away from the last known master time.
When EO.Event[<n>].ResetEvent transitions from 0 to 1,
I.EventStatus[<n>].EventReset transitions to 1 to indicate that • 0 = Do not reset
EventStatus[x].EventReset BOOL the reset was received and completed. It stays 1 until • 1 = Reset
EO.Event[<n>].ResetEvent transition to zero.
The number of events currently queued in the modules. A
EventStatus[x].EventsPending SINT value greater than zero indicates that the controller is not All positive values.
currently keeping up with the rate of events.
Running count of events, which increments by one each new
time event. The originator sets the Event Number Ack to the
EventStatus[x].EventNumber DINT Event Number to acknowledge receipt of the event. When All values.
the EventNumber reaches it maximum value and rolls over it
is to roll over to 1, not 0.
• 0 = Off
Ptxx.Data BOOL Indicates the current digital input value.
• 1 = On
• 0 = Good
Indicates that point data is inaccurate and cannot be trusted • 1 = Bad, causing fault
for use in the application. • If the tag is set to 1, you must troubleshoot the
Ptxx.Fault BOOL module to correct the cause of the inaccuracy.
For more information, see Module Data Quality Reporting on
page 36. IMPORTANT: Once the condition that causes the
tag to change to 1 is removed, the tag automatically
resets to 0.
• 0 = Good data
• 1 = Uncertain data
Indicates that the point data can be inaccurate but the
degree of inaccuracy is not known. If the tag is set to 1, you must troubleshoot the
Ptxx.Uncertain BOOL module to correct the cause of the inaccuracy.
For more information, see Module Data Quality Reporting on
page 36. IMPORTANT: Once the condition that causes the tag
to change to 1 is removed, the tag automatically
resets to 0.
Indicates if the input is chattering per the ChatterTime and • 0 = Normal
Ptxx.Chatter BOOL ChatterCount settings. • 1 = Input is chattering
Indicates an Off to On time stamp was lost in a discrete
product. If TimestampLatchEn is set then a new time stamp 0 or 1
Ptxx.TimestampOverflowOffOn BOOL was not recorded because one is already latched. If
TimestampLatchEn is clear a timestamp was overwritten.
Indicates an On to Off time stamp was lost in a discrete
product. If TimestampLatchEn is set then a new time stamp 0 or 1
Ptxx.TimestampOverflowOnOff BOOL was not recorded because one is already latched. If
TimestampLatchEn is clear a timestamp was overwritten.
• 0 = CIP Sync is not available
Ptxx.CIPSyncValid BOOL Indicates whether the module is synced with a 1588 master.
• 1 = CIP Sync is available
• 0 = A valid time master has not timed out.
Indicates that the module was once synced with a 1588 • 1 = A valid time master was detected on the
Ptxx.CIPSyncTimeout BOOL backplane, but the time master has timed out. The
master, but is not now due to a timeout.
module is using its local clock and can be drifting
away from the last known time master.
An Off to On timestamp identifier for the currently produced All values.
Ptxx.TimestampOffOnNumber INT timestamp.

130 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix B Module Tag Definitions

Table 43 - 5094-IB32 Module Input Tags (Continued)

Name Data Type Definition Valid Values
An On to Off timestamp identifier for the currently produced All values.
Ptxx.TimestampOnOffNumber INT timestamp.
64 bit Timestamp corresponding to when a change of state All values.
Ptxx.TimestampOffOn LINT Off to On was recorded at the input.
64 bit Timestamp corresponding to when a change of state All values.
Ptxx.TimestampOnOff LINT On to Off was recorded at the input.
• 0 = Off
PtxxData BOOL Indicates the current digital input value.
• 1 = On
• 0 = Good
Indicates that point data is inaccurate and cannot be trusted • 1 = Bad, causing fault
for use in the application. • If the tag is set to 1, you must troubleshoot the
PtxxFault BOOL module to correct the cause of the inaccuracy.
For more information, see Module Data Quality Reporting on
page 36. IMPORTANT: Once the condition that causes the
tag to change to 1 is removed, the tag automatically
resets to 0.

Output Tags
Table 44 describes the 5094-IB32 module output tags. The 5094-IB32 module
output tags are only available if you have enabled counters in the Module
Definition dialog box.
Table 44 - 5094-IB32 Module Output Tags
Name Data Type Definition Valid Values
When this bit transitions from 0 to 1 I:Count and I:Rollover are • 0 = I:Count and I:Rollover values are not set to 0
Counterxx.Reset BOOL set to zero. • 1 = I:Count and I:Rolloever values are set to 0
Clears the Rollover bit in the input tag when it transitions from • 0 = I:Rollover bit is not cleared
Counterxx.RolloverAck BOOL 0 to 1. • 1 = I:Rollover bit is cleared
• If RolloverAtPreset is set, the counter counts to the Preset
value and then rolls over to zero.
• If RolloverAtPreset is not set, the counter sets the Done bit
and continues counting up to Max DINT.
Counterxx.Preset DINT • If C:RolloverAtPreset = 1, then if I:Count ≥ O:Preset, 0…2,147,483,647
I:Count=0, else I:Done bit always = 0. Set I:Rollover bit
when I:Count transitions from O:Preset – 1 to 0.
• If C:RolloverAtPreset = 0, then if I:Count ≥ O:Preset, I:Done
= 1, else I:Done = 0. Set I:Rollover bit when I:Count
transitions from 2,147,483,647 to 0.
Erases all recorded timestamps for the input point when it • 0 = Timestamps are not erased
Ptxx.ResetTimestamps BOOL transitions from 0 to 1. • 1 = Timestamps are erased
An Off to On timestamp identifier that is written by the
controller to indicate that the identified timestamp has been
seen and acted on. When Latching is enabled and the
Ptxx.TimestampOffOnNumberAck INT All values.
Timestamp Number that is received from the controller
matches the most recent timestamp that is produced, the
module is then allowed to produce a new timestamp.
An On to Off timestamp identifier that is written by the
controller to indicate that the identified timestamp has been
seen and acted on. When Latching is enabled and the
Ptxx.TimestampOnOffNumberAck INT All values.
Timestamp Number that is received from the controller
matches the most recent timestamp that is produced, the
module is then allowed to produce a new timestamp.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 131

Appendix B Module Tag Definitions

Event Input Tags

Table 45 describes the 5094-IB32 module event input tags. The event input tags
are displayed only if Data with Events is selected in the Module Definition
window.
Table 45 - 5094-IB32 Module Event Input Tags
Name Data Type Definition Valid Values
• 0 = Idle
RunMode BOOL The point’s operating state
• 1 = Run Mode
Indicates if a connection is running. • 0 = Connection running
ConnectionFaulted BOOL The module sets this tag to 0 when connected. If the module
is not connected, it changes the tag to 1. • 1 = Connection not running
• 0 = No diagnostics active
Indicates if any diagnostics are active or if the prognostics
DiagnosticActive BOOL • 1 = One or more diagnostics are active or the
threshold is reached.
prognostics threshold is reached
Increments for each time a distinct diagnostic condition is
detected, and when a distinct diagnostic condition transitions -128…+127
DiagnosticSequenceCount SINT from detected to not detected. The value of 0 is skipped except during module
Set to zero by product reset or power cycle. Wraps from 255 powerup.
(-1) to 1 skipping zero.
• 0 = Good
Indicates that point data is inaccurate and cannot be trusted • 1 = Bad, causing fault
for use in the application. If the tag is set to 1, you must troubleshoot the
Eventxx.Fault BOOL module to correct the cause of the inaccuracy.
For more information, see Module Data Quality Reporting on
page 36. IMPORTANT: Once the condition that causes the
tag to change to 1 is removed, the tag automatically
resets to 0.
0 = Good data
1 = Uncertain data
Indicates that the point data can be inaccurate but the If the tag is set to 1, you must troubleshoot the
degree of inaccuracy is not known.
Eventxx.Uncertain BOOL module to correct the cause of the inaccuracy.
For more information, see Module Data Quality Reporting on IMPORTANT: Once the condition that causes the
page 36. tag to change to 1 is removed, the tag automatically
resets to 0.
Indicates when an event has been discarded because events • 0 = An event status has not been dropped.
Eventxx.EventDropped BOOL are occurring faster than they are being acknowledged. • 1 = An event status has been dropped.
Indicates whether an event triggered when an input transition 0 or 1
Eventxx.EventRising BOOL results in an event pattern being matched.
Indicates whether an event triggered when an input transition 0 or 1
Eventxx.EventFalling BOOL resulted in an event pattern no longer being matched.
• 0 = CIP Sync is not available
Eventxx.CIPSyncValid BOOL Indicates whether the module is synced with a 1588 master.
• 1 = CIP Sync is available
• 0 = A valid time master has not timed out.
Indicates that the module was once synced with a 1588 • 1 = A valid time master was detected on the
Eventxx.CIPSyncTimeout BOOL backplane, but the time master has timed out. The
master, but is not now due to a timeout.
module is using its local clock and can be drifting
away from the last known time master.
The number of events currently queued in the modules. A
Eventxx.EventsPending SINT value greater than 0 indicates that the controller is not All positive values.
currently keeping up with the rate of events.
Running count of events, which increments by one each new
time event. The originator sets the Event Number Ack to the
Eventxx.EventNumber DINT Event Number to acknowledge receipt of the event. When the All values.
EventNumber reaches it maximum value and rolls over it is to
roll over to 1, not 0.
Eventxx.EventTimestamp LINT The time the event occurred. All positive values.
• 0 = Corresponding counter Done bit did not trigger
When set, indicates the corresponding counter Done bit the event
Eventxx.CounterxxDone BOOL (rising or falling depending on configuration) triggered the
event. • 1 = Corresponding counter Done bit triggered the
event

132 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix B Module Tag Definitions

Table 45 - 5094-IB32 Module Event Input Tags (Continued)

Name Data Type Definition Valid Values
• 0 = Corresponding data value did not trigger the
When set, indicates the corresponding data value (rising or event
Eventxx.PtxxData BOOL falling depending on configuration) triggered the event.
• 1 = Corresponding data value triggered the event
• 0 = Corresponding counter did not have a fault
When set, indicates that the corresponding counter had a indicated when the event occurred
Eventxx.CounterxxFault BOOL fault indicated when the event occurred. • 1 = Corresponding counter did have a fault
indicated when the event occurred
Detects whether the signal is good data. The fault is set to 1 • 0 = Good
Eventxx.PtxxFault BOOL by the originator when the connection is lost. • 1 = Bad

Event Output Tags

Table 46 describes the 5094-IB32 module event output tags. The event output
tags are displayed only if Data with Events is selected in the Module Definition
window.
Table 46 - 5094-IB32 Module Event Output Tags
Name Data Type Definition Valid Values
• 0 = Event trigger definition is not active and events are
When set, the corresponding event trigger definition is active not triggered when conditions match the definition
Eventxx.En BOOL and events are triggered when conditions match the
definition. • 1 = Event trigger definition is active and events are
triggered when conditions match the definition
When set an event is to trigger each time a condition change When Enable Independent Point Triggers = Checked
Eventxx.EventRisingEn BOOL results in conditions that match the event trigger definition. (EventRisingEn, EventFallingEn)
• Disable (0,0)
• On transition (1, 0)
• On inverted transition (0, 1)
• On any transition (1, 1)
When set an event is to trigger each time a condition change When Enable Independent Point Triggers = Unchecked
Eventxx.EventFallingEn BOOL results in conditions that no longer match the event trigger (EventRisingEn, EventFallingEn)
definition. • Disable (0, 0)
• On input transition to match pattern (1, 0)
• On input transition to not match pattern (0, 1)
• On input transition to match or not match pattern (1, 1)
When set, events are latched until acknowledged. A new
event is lost if the previous event has not been • 0 = Not latched (default)
Eventxx.LatchEn BOOL acknowledged. When not set, new events overwrite old • 1 = Latched
events.
When transitions from 0 to 1, resets all events and clears the • 0 = Events are not cleared.
Eventxx.ResetEvent BOOL event queue on the point. • 1 = Events are cleared when a rising edge occurs.
• 0 = When all selected conditions achieve the
For events, determines whether each condition that is configured values, an event is triggered.
Eventxx.IndependentConditionTriggerEn BOOL indicated in the trigger definition can initiate an event
independently. • 1 = When any selected condition achieves the
configured value, an event is triggered.
The controller writes back the EI:Event[<n>].EventNumber
into this EO:Event[<n>].EventNumberAck to indicate receipt All values.
Eventxx.EventNumberAck DINT of the event. All events with I:EventNumbers that occurred
before EventNumberAck is acknowledged.
• 0 = Corresponding counter does not participate in the event
When set, indicates that the corresponding counter is to trigger definition
Eventxx.CounterxxSelect BOOL participate in the event trigger definition. • 1= Corresponding counter participates in the event trigger
definition
When set, indicates that the corresponding data value is to 0 or 1
Eventxx.PtxxDataSelect BOOL participate in the event trigger definition.
If the counter function is selected in the event trigger
Eventxx.CounterxxValue BOOL definition, this member indicates that value that is to trigger 0 or 1
the event.
• 0 = Input inactive
Eventxx.PtxxDataValue BOOL Indicates the input value of the event point data.
• 1 = Input active

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 133

Appendix B Module Tag Definitions

5094-OA16 Module Tags This section describes the tags that are associated with the 5094-OA16 module.
Applies to these modules:
5094 Standard I/O Modules
Configuration Tags
Table 47 describes the 5094-OA16 module configuration tags.
Table 47 - 5094-OA16 Module Configuration Tags
Name Data Type Definition Valid Values
Selects the behavior the output point takes if a • 0 = Go to a user-defined value
Ptxx.FaultMode BOOL communication fault occurs. FaultValue defines the value to
go to when set to user-defined value. • 1 = Hold last state
Defines the value that the discrete output should assume if a • 0 = Off
Ptxx.FaultValue BOOL communication fault occurs when FaultMode = 0. • 1 = On
Selects the behavior the output point should take when • 0 = Go to a user-defined value
Ptxx.ProgMode BOOL transitioned into Program mode. ProgValue defines the value
to go to when set to user-defined value. • 1 = Hold last state
Defines the value that the output should take when the • 0 = The output state is Off during Program mode.
Ptxx.ProgValue BOOL connection transitions to Program mode if the ProgMode bit is
set to "User-Defined Value". • 1 = The output state is On during Program mode.
• 0 = The output state is Off after the
If FaultValueStateDuration is nonzero determines the final FaultValueStateDuration time expires.
Ptxx.FaultFinalState BOOL Output state after the configured FaultValueStateDuration
time out occurs. • 1 = The output state is On after the
FaultValueStateDuration time expires.
Determines if an output should transition to the Fault Mode if • 0 = Stay in Program Mode
Ptxx.ProgramToFaultEn BOOL the connection faults while in Program Mode. • 1 = Go to Fault mode
This value determines the length of time the Fault Mode state • 0 = Hold forever (default).
Ptxx.FaultValueStateDuration SINT is held before the FaultFinalState being applied. • 1, 2, 5, or 10 seconds

Input Tags
Table 48 describes the 5094-OA16 module input tags.
Table 48 - 5094-OA16 Module Input Tags
Name Data Type Definition Valid Values
• 0 = Idle
RunMode BOOL The point’s operating state
• 1 = Run Mode
Indicates if a connection is running. • 0 = Connection running
ConnectionFaulted BOOL The module sets this tag to 0 when connected. If the module
is not connected, it changes the tag to 1. • 1 = Connection not running
• 0 = No diagnostics active
Indicates if any diagnostics are active or if the prognostics
DiagnosticActive BOOL • 1 = One or more diagnostics are active or the
threshold is reached.
prognostics threshold is reached
Increments for each time a distinct diagnostic condition is
detected, and when a distinct diagnostic condition transitions -128…+127
DiagnosticSequenceCount SINT from detected to not detected. The value of 0 is skipped except during module
Set to zero by product reset or power cycle. Wraps from 255 powerup.
(-1) to 1, skipping zero.
• 0 = Off
Ptxx.Data BOOL Indicates the current digital input value.
• 1 = On
• 0 = Good
• 1 = Bad, causing fault
The typical causes of uncertain data are the
following:
Indicates that point data is inaccurate and cannot be trusted – Field Power Loss condition
for use in the application. – No Load condition
Ptxx.Fault BOOL For more information, see Module Data Quality Reporting on – Short Circuit condition
page 36. If the tag is set to 1, you must troubleshoot the
module to correct the cause of the inaccuracy.
IMPORTANT: Once the condition that causes the
tag to change to 1 is removed, the tag automatically
resets to 0.

134 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix B Module Tag Definitions

Table 48 - 5094-OA16 Module Input Tags (Continued)

Name Data Type Definition Valid Values
• 0 = Good data
Indicates that the point data can be inaccurate but the • 1 = Uncertain data
degree of inaccuracy is not known. If the tag is set to 1, you must troubleshoot the
Ptxx.Uncertain BOOL module to correct the cause of the inaccuracy.
For more information, see Module Data Quality Reporting on
page 36. IMPORTANT: Once the condition that causes the
tag to change to 1 is removed, the tag automatically
resets to 0.

Output Tags
Table 49 describes the 5094-OA16 module output tags.
Table 49 - 5094-OA16 Module Output Tags
Name Data Type Definition Valid Values
• 0 = Off
Ptxx.Data BOOL Current digital input value.
• 1 = On

5094-OB8 Module Tags This section describes the tags that are associated with the 5094-OB8 module.
Applies to these modules:
5094 Standard I/O Modules
Configuration Tags
Table 50 describes the 5094-OB8 module configuration tags.
Table 50 - 5094-OB8 Module Configuration Tags
Name Data Type Definition Valid Values
Selects the behavior the output point takes if a • 0 = Go to a user-defined value
Ptxx.FaultMode BOOL communication fault occurs. FaultValue defines the value to
go to when set to user-defined value. • 1 = Hold last state
Defines the value that the discrete output should assume if a • 0 = Off
Ptxx.FaultValue BOOL communication fault occurs when FaultMode = 0. • 1 = On
Selects the behavior the output point should take when • 0 = Go to a user-defined value
Ptxx.ProgMode BOOL transitioned into Program mode. ProgValue defines the value
to go to when set to user-defined value. • 1 = Hold last state
Defines the value that the output should take when the • 0 = The output state is Off during Program mode.
Ptxx.ProgValue BOOL connection transitions to Program mode if the ProgMode bit is
set to "User-Defined Value". • 1 = The output state is On during Program mode.
• 0 = The output state is Off after the
If FaultValueStateDuration is nonzero determines the final FaultValueStateDuration time expires.
Ptxx.FaultFinalState BOOL Output state after the configured FaultValueStateDuration
time out occurs. • 1 = The output state is On after the
FaultValueStateDuration time expires.
Determines if an output should transition to the Fault Mode if • 0 = Stay in Program Mode
Ptxx.ProgramToFaultEn BOOL the connection faults while in Program Mode. • 1 = Go to Fault mode
• 0 = Disable
Ptxx.NoLoadEn BOOL Enables no load detection for output points.
• 1 = Enable
This value determines the length of time the Fault Mode state • 0 = Hold forever (default).
Ptxx.FaultValueStateDuration SINT is held before the FaultFinalState being applied. • 1, 2, 5, or 10 seconds

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 135

Appendix B Module Tag Definitions

Input Tags
Table 51 describes the 5094-OB8 module input tags.
Table 51 - 5094-OB8 Module Input Tags
Name Data Type Definition Valid Values
• 0 = Idle
RunMode BOOL The point’s operating state
• 1 = Run Mode
Indicates if a connection is running. • 0 = Connection running
ConnectionFaulted BOOL The module sets this tag to 0 when connected. If the module
is not connected, it changes the tag to 1. • 1 = Connection not running
• 0 = No diagnostics active
Indicates if any diagnostics are active or if the prognostics
DiagnosticActive BOOL • 1 = One or more diagnostics are active or the
threshold is reached.
prognostics threshold is reached
Indicates if the module is operating outside is designed • 0 = Good
Uncertain BOOL operating range of if data is under manual or override
control. • 1 = Uncertain
Increments for each time a distinct diagnostic condition is
detected, and when a distinct diagnostic condition transitions -128…+127
DiagnosticSequenceCount SINT from detected to not detected. The value of 0 is skipped except during module
Set to zero by product reset or power cycle. Wraps from 255 powerup.
(-1) to 1, skipping zero.
• 0 = Off
Ptxx.Data/PtxxData BOOL Indicates the current digital input value.
• 1 = On
• 0 = Good
• 1 = Bad, causing fault
The typical causes of uncertain data are the
following:
Indicates that point data is inaccurate and cannot be trusted – Field Power Loss condition
for use in the application. – No Load condition
Ptxx.Fault/PtxxFault BOOL For more information, see Module Data Quality Reporting on – Short Circuit condition
page 36. If the tag is set to 1, you must troubleshoot the
module to correct the cause of the inaccuracy.
IMPORTANT: Once the condition that causes the
tag to change to 1 is removed, the tag automatically
resets to 0.
• 0 = Good data
Indicates that the point data can be inaccurate but the • 1 = Uncertain data
degree of inaccuracy is not known. If the tag is set to 1, you must troubleshoot the
Ptxx.Uncertain BOOL module to correct the cause of the inaccuracy.
For more information, see Module Data Quality Reporting on
page 36. IMPORTANT: Once the condition that causes the
tag to change to 1 is removed, the tag automatically
resets to 0.
Indicates that the signal wire has been disconnected from • 0 = No fault
Ptxx.NoLoad BOOL one of its terminals or the RTB has been removed. Used with
Output points. • 1 = Fault
• 0 = No short circuit
Ptxx.ShortCircuit BOOL Indicates an output short circuit or overcurrent.
• 1 = Short circuit or overcurrent

Output Tags
Table 52 describes the 5094-OB8 module output tags.
Table 52 - 5094-OB8 Module Output Tags
Name Data Type Definition Valid Values
• 0 = Off
Ptxx.Data/PtxxData BOOL Current digital input value.
• 1 = On

136 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix B Module Tag Definitions

5094-OB16 Module Tags This section describes the tags that are associated with the 5094-OB16 module.
Applies to these modules:
5094 Standard I/O Modules
Configuration Tags
Table 53 describes the 5094-OB16 module configuration tags.
Table 53 - 5094-OB16 Module Configuration Tags
Name Data Type Definition Valid Values
Selects the behavior the output point takes if a • 0 = Go to a user-defined value
Ptxx.FaultMode BOOL communication fault occurs. FaultValue defines the value to
go to when set to user-defined value. • 1 = Hold last state
Defines the value that the discrete output should assume if a • 0 = Off
Ptxx.FaultValue BOOL communication fault occurs when FaultMode = 0. • 1 = On
Selects the behavior the output point should take when • 0 = Go to a user-defined value
Ptxx.ProgMode BOOL transitioned into Program mode. ProgValue defines the value
to go to when set to user-defined value. • 1 = Hold last state
Defines the value that the output should take when the • 0 = The output state is Off during Program mode.
Ptxx.ProgValue BOOL connection transitions to Program mode if the ProgMode bit is
set to "User-Defined Value". • 1 = The output state is On during Program mode.
• 0 = The output state is Off after the
If FaultValueStateDuration is nonzero determines the final FaultValueStateDuration time expires.
Ptxx.FaultFinalState BOOL Output state after the configured FaultValueStateDuration
time out occurs. • 1 = The output state is On after the
FaultValueStateDuration time expires.
Determines if an output should transition to the Fault Mode if • 0 = Stay in Program Mode
Ptxx.ProgramToFaultEn BOOL the connection faults while in Program Mode. • 1 = Go to Fault mode
• 0 = Disable
Ptxx.NoLoadEn BOOL Enables no load detection for output points.
• 1 = Enable
This value determines the length of time the Fault Mode state • 0 = Hold forever (default).
Ptxx.FaultValueStateDuration SINT is held before the FaultFinalState being applied. • 1, 2, 5, or 10 seconds

Input Tags
Table 54 describes the 5094-OB16 module input tags.
Table 54 - 5094-OB16 Module Input Tags
Name Data Type Definition Valid Values
• 0 = Idle
RunMode BOOL The point’s operating state
• 1 = Run Mode
Indicates if a connection is running. • 0 = Connection running
ConnectionFaulted BOOL The module sets this tag to 0 when connected. If the module
is not connected, it changes the tag to 1. • 1 = Connection not running
• 0 = No diagnostics active
Indicates if any diagnostics are active or if the prognostics
DiagnosticActive BOOL • 1 = One or more diagnostics are active or the
threshold is reached.
prognostics threshold is reached
Indicates if the module is operating outside is designed • 0 = Good
Uncertain BOOL operating range of if data is under manual or override
control. • 1 = Uncertain
Increments for each time a distinct diagnostic condition is
detected, and when a distinct diagnostic condition transitions -128…+127
DiagnosticSequenceCount SINT from detected to not detected. The value of 0 is skipped except during module
Set to zero by product reset or power cycle. Wraps from 255 powerup.
(-1) to 1, skipping zero.
• 0 = CIP Sync is not available
CIPSyncValid BOOL Indicates whether the module is synced with a 1588 master.
• 1 = CIP Sync is available
• 0 = A valid time master has not timed out
Indicates that the module was once synced with a 1588 • 1 = A valid time master was detected on the
CIPSyncTimeout BOOL backplane, but the time master has timed out. The
master, but is not now due to a timeout.
module is using its local clock and can be drifting
away from the last known master time.
• 0 = Off
Ptxx.Data BOOL Indicates the current digital input value.
• 1 = On

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 137

Appendix B Module Tag Definitions

Table 54 - 5094-OB16 Module Input Tags (Continued)

Name Data Type Definition Valid Values
• 0 = Good
• 1 = Bad, causing fault
The typical causes of uncertain data are the
following:
Indicates that point data is inaccurate and cannot be trusted – Field Power Loss condition
for use in the application. – No Load condition
Ptxx.Fault BOOL For more information, see Module Data Quality Reporting on – Short Circuit condition
page 36. If the tag is set to 1, you must troubleshoot the module
to correct the cause of the inaccuracy.
IMPORTANT: Once the condition that causes the tag
to change to 1 is removed, the tag automatically resets
to 0.
• 0 = Good data
Indicates that the point data can be inaccurate but the • 1 = Uncertain data
degree of inaccuracy is not known. If the tag is set to 1, you must troubleshoot the module
Ptxx.Uncertain BOOL For more information, see Module Data Quality Reporting on to correct the cause of the inaccuracy.
page 36. IMPORTANT: Once the condition that causes the tag
to change to 1 is removed, the tag automatically resets
to 0.
Indicates that the signal wire has been disconnected from • 0 = No fault
Ptxx.NoLoad BOOL one of its terminals or the RTB has been removed. Used with
Output points. • 1 = Fault
• 0 = No short circuit
Ptxx.ShortCircuit BOOL Indicates an output short circuit or overcurrent.
• 1 = Short circuit or overcurrent

Output Tags
Table 55 describes the 5094-OB16 module output tags.
Table 55 - 5094-OB16 Module Output Tags
Name Data Type Definition Valid Values
Indicates the TimeBase for all schedule times in a scheduled
output consumed assembly or point. The TimeBase + The
TimeBase LINT Schedule[n].TimeOffset determines the time for the schedule. Any positive value.
Base/Offset scheme that is used to fit enough schedules into
the assembly.
• 0 = Off
Ptxx.Data BOOL Current digital input value.
• 1 = On
• 0 = Normal output data
Ptxx.ScheduleEn BOOL Specifies the use of normal output data or scheduled data.
• 1 = Scheduled data
Indicates which schedule to load from 32 available • 1…32 = Valid schedule
Schedulex SINT schedules. • 0, 129…255 = No schedule
There are 32 schedules available (for Neo R1 products). • 1…32 = Valid schedule
Schedulex.ID SINT Indicates which schedule to load. • 0 or 129…255 = No schedule
Indicates that the schedule information is valid and that this All values.
Schedulex.SequenceNumber SINT schedule should be processed.
Selects the output point that this schedule applies to. 0xFF 0…15
Schedulex.OutputPointSelect SINT means no output point selected.
Output data to be applied at time that is specified in
Schedulex.Data BOOL 0 or 1
schedule.
Offset from schedule base time. Used for scheduled output
Schedulex.TimeOffset DINT consumed tags. Base/Offset scheme that is used to fit All values.
enough schedules in the assembly.

5094-OB32 Module Tags This section describes the tags that are associated with the 5094-OB32 module.
Applies to these modules:
5094 Standard I/O Modules
Configuration Tags
Table 56 describes the 5094-OB32 module configuration tags.

138 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix B Module Tag Definitions

Table 56 - 5094-OB32 Module Configuration Tags

Name Data Type Definition Valid Values
Selects the behavior the output point takes if a • 0 = Go to a user-defined value
Ptxx.FaultMode BOOL communication fault occurs. FaultValue defines the value to
go to when set to user-defined value. • 1 = Hold last state
Defines the value that the discrete output should assume if a • 0 = Off
Ptxx.FaultValue BOOL communication fault occurs when FaultMode = 0. • 1 = On
Selects the behavior the output point should take when • 0 = Go to a user-defined value
Ptxx.ProgMode BOOL transitioned into Program mode. ProgValue defines the value
to go to when set to user-defined value. • 1 = Hold last state
Defines the value that the output should take when the • 0 = The output state is Off during Program mode.
Ptxx.ProgValue BOOL connection transitions to Program mode if the ProgMode bit is
set to "User-Defined Value". • 1 = The output state is On during Program mode.
• 0 = The output state is Off after the
If FaultValueStateDuration is nonzero determines the final FaultValueStateDuration time expires.
Ptxx.FaultFinalState BOOL Output state after the configured FaultValueStateDuration
time out occurs. • 1 = The output state is On after the
FaultValueStateDuration time expires.
Determines if an output should transition to the Fault Mode if • 0 = Stay in Program Mode
Ptxx.ProgramToFaultEn BOOL the connection faults while in Program Mode. • 1 = Go to Fault mode
• 0 = Disable
Ptxx.NoLoadEn BOOL Enables no load detection for output points.
• 1 = Enable
This value determines the length of time the Fault Mode state • 0 = Hold forever (default).
Ptxx.FaultValueStateDuration SINT is held before the FaultFinalState being applied. • 1, 2, 5, or 10 seconds

Input Tags
Table 57 describes the 5094-OB32 module input tags.
Table 57 - 5094-OB32 Module Input Tags
Name Data Type Definition Valid Values
• 0 = Idle
RunMode BOOL The point’s operating state
• 1 = Run Mode
Indicates if a connection is running. • 0 = Connection running
ConnectionFaulted BOOL The module sets this tag to 0 when connected. If the module
is not connected, it changes the tag to 1. • 1 = Connection not running
• 0 = No diagnostics active
Indicates if any diagnostics are active or if the prognostics
DiagnosticActive BOOL • 1 = One or more diagnostics are active or the
threshold is reached.
prognostics threshold is reached
Indicates if the module is operating outside is designed • 0 = Good
Uncertain BOOL operating range of if data is under manual or override
control. • 1 = Uncertain
Increments for each time a distinct diagnostic condition is
detected, and when a distinct diagnostic condition transitions -128…+127
DiagnosticSequenceCount SINT from detected to not detected. The value of 0 is skipped except during module
Set to zero by product reset or power cycle. Wraps from 255 powerup.
(-1) to 1, skipping zero.
• 0 = Off
Ptxx.Data/PtxxData BOOL Indicates the current digital input value.
• 1 = On
• 0 = Good
• 1 = Bad, causing fault
The typical causes of uncertain data are the
following:
Indicates that point data is inaccurate and cannot be trusted – Field Power Loss condition
for use in the application. – No Load condition
Ptxx.Fault/PtxxFault BOOL For more information, see Module Data Quality Reporting on – Short Circuit condition
page 36. If the tag is set to 1, you must troubleshoot the
module to correct the cause of the inaccuracy.
IMPORTANT: Once the condition that causes the
tag to change to 1 is removed, the tag automatically
resets to 0.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 139

Appendix B Module Tag Definitions

Table 57 - 5094-OB32 Module Input Tags (Continued)

Name Data Type Definition Valid Values
• 0 = Good data
Indicates that the point data can be inaccurate but the • 1 = Uncertain data
degree of inaccuracy is not known. If the tag is set to 1, you must troubleshoot the
Ptxx.Uncertain BOOL module to correct the cause of the inaccuracy.
For more information, see Module Data Quality Reporting on
page 36. IMPORTANT: Once the condition that causes the
tag to change to 1 is removed, the tag automatically
resets to 0.
Indicates that the signal wire has been disconnected from • 0 = No fault
Ptxx.NoLoad BOOL one of its terminals or the RTB has been removed. Used with
Output points. • 1 = Fault
• 0 = No short circuit
Ptxx.ShortCircuit BOOL Indicates an output short circuit or overcurrent.
• 1 = Short circuit or overcurrent

Output Tags
Table 58 describes the 5094-OB32 module output tags.
Table 58 - 5094-OB32 Module Output Tags
Name Data Type Definition Valid Values
• 0 = Off
Ptxx.Data BOOL Current digital input value.
• 1 = On

5094-OW8I Module Tags This section describes the tags that are associated with the 5094-OW8I module.
Applies to these modules:
5094 Standard I/O Modules
Configuration Tags
Table 59 describes the 5094-OW8I module configuration tags.
Table 59 - 5094-OW8I Module Configuration Tags
Name Data Type Definition Valid Values
Selects the behavior the output point takes if a • 0 = Go to a user-defined value
Ptxx.FaultMode BOOL communication fault occurs. FaultValue defines the value to
go to when set to user-defined value. • 1= Hold last state
Defines the value that the discrete output should assume if a • 0 = Off
Ptxx.FaultValue BOOL communication fault occurs when FaultMode = 0. • 1 = On
Selects the behavior the output point should take when • 0 = Go to a user-defined value
Ptxx.ProgMode BOOL transitioned into Program mode. ProgValue defines the value
to go to when set to user-defined value. • 1= Hold last state
Defines the value that the output should take when the • 0 = The output state is Off during Program mode.
Ptxx.ProgValue BOOL connection transitions to Program mode if the ProgMode bit is
set to “User-Defined Value”. • 1 = The output state is On during Program mode.
• 0 = The output state is Off after the
If FaultValueStateDuration is nonzero determines the final FaultValueStateDuration time expires.
Ptxx.FaultFinalState BOOL Output state after the configured FaultValueStateDuration
time out occurs. • 1 = The output state is On after the
FaultValueStateDuration time expires.
Determines if an output should transition to the Fault Mode if • 0 = Stay in Program Mode
Ptxx.ProgramToFaultEn BOOL the connection faults while in Program Mode. • 1 = Go to Fault mode
This value determines the length of time the Fault Mode state • 0 = Hold forever (default).
Ptxx.FaultValueStateDuration SINT is held before the FaultFinalState being applied. • 1, 2, 5, or 10 seconds

140 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix B Module Tag Definitions

Input Tags
Table 60 describes the 5094-OW8I module input tags.
Table 60 - 5094-OW8I Module Input Tags
Name Data Type Definition Valid Values
• 0 = Idle
RunMode BOOL The point’s operating state
• 1 = Run Mode
Indicates if a connection is running. • 0 = Connection running
ConnectionFaulted BOOL The module sets this tag to 0 when connected. If the module
is not connected, it changes the tag to 1. • 1 = Connection not running
• 0 = No diagnostics active
Indicates if any diagnostics are active or if the prognostics
DiagnosticActive BOOL • 1 = One or more diagnostics are active or the
threshold is reached.
prognostics threshold is reached
Increments for each time a distinct diagnostic condition is
detected, and when a distinct diagnostic condition transitions -128…+127
DiagnosticSequenceCount SINT from detected to not detected. The value of 0 is skipped except during module
Set to zero by product reset or power cycle. Wraps from 255 powerup.
(-1) to 1, skipping zero.
• 0 = Off
Ptxx.Data BOOL Indicates the current digital input value.
• 1 = On
• 0 = Good
• 1 = Bad, causing fault
The typical causes of uncertain data are the
Indicates that point data is inaccurate and cannot be trusted following:
for use in the application. – Field Power Loss condition
Ptxx.Fault BOOL For more information, see Module Data Quality Reporting on If the tag is set to 1, you must troubleshoot the
page 36. module to correct the cause of the inaccuracy.
IMPORTANT: Once the condition that causes the
tag to change to 1 is removed, the tag automatically
resets to 0.
• 0 = Good data
Indicates that the point data can be inaccurate but the • 1 = Uncertain data
degree of inaccuracy is not known. If the tag is set to 1, you must troubleshoot the
Ptxx.Uncertain BOOL module to correct the cause of the inaccuracy.
For more information, see Module Data Quality Reporting on
page 36. IMPORTANT: Once the condition that causes the
tag to change to 1 is removed, the tag automatically
resets to 0.

Output Tags
Table 61 describes the 5094-OW8I module outputs tags.
Table 61 - Relay Output High Current Module Output Tags
Name Data Type Definition Valid Values
• 0 = Off
Ptxx.Data BIT Indicates the current digital input value.
• 1 = On

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 141

Appendix B Module Tag Definitions

5094-IB16S Module Tags This section describes the tags that are associated with the 5094-IB16S module.
Applies to these modules:
5094 Safety I/O Modules
Input Tags
Table 62 describes the 5094-IB16S module input tags.
Table 62 - 5094-IB16S Module Safety Input Tags
Name Data Type Definition Valid Values
• 0 = Idle
RunMode BOOL Module’s operating state
• 1 = Run
Indicates if a connection is running. • 0 = Connection running
ConnectionFaulted BOOL The module sets this tag to 0 when connected. If the module
is not connected, it changes the tag to 1. • 1 = Connection not running
• 0 = No diagnostics active
Indicates if any diagnostics are active or if the prognostics
DiagnosticActive BOOL • 1 = One or more diagnostics are active or the
threshold is reached.
prognostics threshold is reached
Increments for each time a distinct diagnostic condition is
detected, and when a distinct diagnostic condition transitions -128…+127
DiagnosticSequenceCount SINT from detected to not detected. The value of 0 is skipped except during module
Set to zero by product reset or power cycle. Wraps from 255 powerup.
(-1) to 1 skipping zero.
• 0 = Off
Ptxx.Data BOOL Indicates the current safety input value.
• 1 = On
• 0 = Good data
• 1 = Bad data (faulted) or set to Not Used
• Indicates that channel data is inaccurate and cannot be – If the tag is set to 1, you must troubleshoot the
trusted for use in the application. module to correct the cause of the inaccuracy.
Ptxx.Fault BOOL For more information, see Module Data Quality Reporting on IMPORTANT: Once the condition that causes the
page 36. tag to change to 1 is removed, you must
complete the steps described in Safety Input
• The channel is set to Not Used.
Fault Reset on page 63 to reset this tag to 0.
– If the tag is 1 because the channel is set to Not
Used, no action is required.
• 0 = Good data
• 1 = Uncertain data
Indicates that the channel data can be inaccurate but the This tag is set to 1 when the module has reached a
degree of inaccuracy is not known. critical operating temperature or is higher the
Ptxx.Uncertain BOOL For more information, see Module Data Quality Reporting on acceptable operating temperature.
page 36. IMPORTANT: Once the condition that causes the
tag to change to 1 is removed, the tag automatically
resets to 0.
• 0 = No short circuit
Ptxx.ShortCircuit BOOL Indicates a short circuit.
• 1 = Short circuit
• 0 = Bad, causing a fault
Ptxx.Status BOOL Indicates the status of the channel.
• 1 = Good

142 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix B Module Tag Definitions

Test Output Tags

Table 63 - 5094-IB16S Module Test Output Tags
Name Data Type Definition Valid Values
Indicates that a 24V DC power source is present at the • 0 = 24V DC power is not present
Testxx.Readback BOOL test output. • 1 = 24V DC power is present
• Indicates that channel data is inaccurate and cannot be • 0 = Good data
trusted for use in the application. • 1 = Bad data (faulted) or set to Not Used
Testxx.Fault BOOL • For more information, see Module Data Quality Reporting on – If the tag is set to 1, you must troubleshoot the
page 36. module to correct the cause of the inaccuracy.
– If the tag is 1 because the channel is set to Not
• The channel is set to Not Used. Used, no action is required.
• 0 = Good data
• 1 = Uncertain data
Indicates that the channel data can be inaccurate but the This tag is set to 1 when the module has reached a
degree of inaccuracy is not known. critical operating temperature or is higher the
Testxx.Uncertain BOOL For more information, see Module Data Quality Reporting on acceptable operating temperature.
page 36. IMPORTANT: Once the condition that causes the
tag to change to 1 is removed, the tag automatically
resets to 0.
• 0 = No short circuit
Testxx.ShortCircuit BOOL Indicates an output short circuit
• 1 = Short circuit
Indicates that a field power loss condition exists on the • 0 = No field power off condition
Testxx.FieldPowerOff BOOL channel. • 1 = Field power off condition
• 0 = Fault
Testxx.Status BOOL Indicates the channel status.
• 1 = Good

Output Tags
Table 64 describes the 5094-IB16S module output tags.
Table 64 - 5094-IB16S Module Safety Output Tags
Name Data Type Definition Valid Values
When ‘Latch Fault until reset via output tag’ mode is Enabled,
the IO channel will hold safety input fault indications until it Rising edge: the fault status is released if the fault has
Pt00.ResetFault BOOL checks that the fault is removed. If the fault is removed, it will been removed.
clear only the fault status upon detecting that the ResetFault
bit in its channel sees a rising edge.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 143

Appendix B Module Tag Definitions

5094-OB16S Module Tags This section describes the tags that are associated with the 5094-OB16S
module.
Applies to these modules:
5094 Safety I/O Modules
Input Tags
Table 65 describes the 5094-OB16S module input tags.
Table 65 - 5094-OB16S Module Safety Input Tags
Name Data Type Definition Valid Values
• 0 = Idle
RunMode BOOL The point’s operating state
• 1 = Run Mode
Indicates if a connection is running. • 0 = Connection running
ConnectionFaulted BOOL The module sets this tag to 0 when connected. If the module
is not connected, it changes the tag to 1. • 1 = Connection not running
• 0 = No diagnostics active
Indicates if any diagnostics are active or if the prognostics
DiagnosticActive BOOL • 1 = One or more diagnostics are active or the
threshold is reached.
prognostics threshold is reached
Increments for each time a distinct diagnostic condition is
detected, and when a distinct diagnostic condition transitions -128…+127
DiagnosticSequenceCount SINT from detected to not detected. The value of 0 is skipped except during module
Set to zero by product reset or power cycle. Wraps from 255 powerup.
(-1) to 1, skipping zero.
• 0 = Off
Ptxx.Readback BOOL Indicates the current digital output value.
• 1 = On
• 0 = Good data
• 1 = Bad data (faulted) or set to Not Used
• Indicates that point data is inaccurate and cannot be If the tag is set to 1, you must troubleshoot the
trusted for use in the application. module to correct the cause of the inaccuracy.
Ptxx.Fault BOOL For more information, see Module Data Quality Reporting on IMPORTANT: Once the condition that causes the
page 36. tag to change to 1 is removed, you must complete
the steps described in Safety Output Fault Reset on
• The channel is set to Not Used.
page 69 to reset this tag to 0.
If the tag is 1 because the channel is set to Not
Used, no action is required.
• 0 = Good data
Indicates that the point data can be inaccurate but the
degree of inaccuracy is not known. • 1 = Uncertain data
For more information, see Module Data Quality Reporting on If the tag is set to 1, you must troubleshoot the
Ptxx.Uncertain BOOL module to correct the cause of the inaccuracy.
page 36.
Indicates OverTemperature and CriticalTemperature situation IMPORTANT: Once the condition that causes the
in 5094-OB16S module. tag to change to 1 is removed, the tag automatically
resets to 0.
• 0 = No fault
Indicates that the signal wire has been disconnected from
one of its terminals or that the RTB has been removed. • 1 = Fault
Ptxx.NoLoad BOOL Used with Output points. IMPORTANT: For firmware revision 2.011 onwards,
IMPORTANT: The guaranteed load detection is 10 mA for both you must enable No Load diagnostic as described
Off and On states. in Enable 5094-OB16S or 5094-OB16SXT No Load
Diagnostic on page 52.
Indicates that a field power loss condition exists on the • 0 = No field power off condition
Ptxx.FieldPowerOff BOOL channel • 1 = Field power off condition
• 0 = No short circuit
Ptxx.ShortCircuit BOOL Indicates an output short circuit or overcurrent.
• 1 = Short circuit or overcurrent
• 0 = Bad, causing a fault
Ptxx.Status BOOL Indicates the status of the channel.
• 1 = Good

144 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix B Module Tag Definitions

Output Tags
Table 66 describes the 5094-OB16S module output tags.
Table 66 - 5094-OB16S Module Safety Output Tags
Name Data Type Definition Valid Values
• 0 = Off
Ptxx.Data BOOL Indicates the current digital output value.
• 1 = On
When ‘Latch Fault until reset via output tag’ mode is Enabled,
the
I/O channel will hold safety output fault indications until it Rising edge: the fault status is released if the fault has
Ptxx.ResetFault BOOL checks that the fault is removed. If the fault is removed, it will been removed.
clear only the fault status upon detecting that the ResetFault
bit in its channel sees a rising edge.

5094-OW4IS Module Tags This section describes the tags that are associated with the 5094-OW4IS
module.
Applies to these modules:
5094 Safety I/O Modules
Input Tags
Table 67 describes the 5094-OW4IS module input tags.
Table 67 - 5094-OW4IS Module Safety Input Tags
Name Data Type Definition Valid Values
• 0 = Idle
RunMode BIT The point’s operating state
• 1 = Run Mode
Indicates if a connection is running. • 0 = Connection running
ConnectionFaulted BIT The module sets this tag to 0 when connected. If the
module is not connected, it changes the tag to 1. • 1 = Connection not running
• 0 = No diagnostics active
Indicates if any diagnostics are active or if the prognostics
DiagnosticActive BIT • 1 = One or more diagnostics are active or the prognostics
threshold is reached.
threshold is reached
Increments for each time a distinct diagnostic condition is
detected, and when a distinct diagnostic condition
transitions from detected to not detected. -128…+127
DiagnosticSequenceCount SINT Set to zero by product reset or power cycle. Wraps from The value of 0 is skipped except during module powerup.
255
(-1) to 1, skipping zero.
• 0 = Off
Ptxx.Readback BOOL Indicates the current digital output value.
• 1 = On
• 0 = Good data
• 1 = Bad data (faulted) or set to Not Used
• Indicates that point data is inaccurate and cannot be If the tag is set to 1, you must troubleshoot the module to
trusted for use in the application. correct the cause of the inaccuracy.
Ptxx.Fault BOOL For more information, see Module Data Quality IMPORTANT: Once the condition that causes the tag to
Reporting on page 36. change to 1 is removed, you must complete the steps
described in Safety Relay Output Fault Reset on page 70
• The channel is set to Not Used.
to reset this tag to 0.
If the tag is 1 because the channel is set to Not Used, no
action is required.
• Indicates that the point data can be inaccurate but the
degree of inaccuracy is not known. • 0 = Good data
For more information, see Module Data Quality • 1 = Uncertain data
Ptxx.Uncertain BOOL Reporting on page 36. If the tag is set to 1, you must troubleshoot the module to
• Indicates OverTemperature and CriticalTemperature correct the cause of the inaccuracy.
situation in 5094-OW4IS module. IMPORTANT: Once the condition that causes the tag to
change to 1 is removed, the tag automatically resets to 0.
• Indicates Shock & Vibration reaching operation limits.
Indicates that a field power loss condition exists on the • 0 = No field power off condition
Ptxx.FieldPowerOff BOOL channel. • 1 = Field power off condition
• 0 = Bad, causing a fault
Ptxx.Status BOOL Indicates the status of the channel.
• 1 = Good

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 145

Appendix B Module Tag Definitions

Output Tags
Table 68 describes the 5094-OW4IS modules output tags.

Table 68 - 5094-OW4IS Module Safety Output Tags

Name Data Type Definition Valid Values
• 0 = Off
Ptxx.Data BOOL Indicates the current digital output value.
• 1 = On
When ‘Latch Fault until reset via output tag’ mode is
Enabled, the I/O channel will hold safety output fault
indications until it checks that the fault is removed. If the Rising edge: the fault status is released if the fault has been
Ptxx.ResetFault BOOL fault is removed, it will clear only the fault status upon removed.
detecting that the ResetFault bit in its channel sees a
rising edge.

146 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix C

Module Diagnostic Assembly

Create User-defined You can use the Studio 5000 Logix Designer application to create user-defined
Diagnostic Assembly Types Diagnostic Assembly types.

Applies to these modules:

5094 Standard I/O Modules
5094 Safety I/O Modules

5094-IA16, 5094-IA16XT Module

Applies to these modules:
There are 3 Diagnostic Assemblies under these modules including 1 Diagnostic
5094 Standard I/O Modules Channel. From the Controller Organizer pane, expand Data Types and create
user-defined data types for the module.

Diagnostic Assemblies
1. Diagnostic Digital 16 Point w/Diagnostics Assembly (Input)
- DATATYPE: AB: 5000_DI16_Diag:D:0
- Instance ID: 0x315 (789)
- Size = 416 bytes

Follow the information in Table 69 to add each member.

Table 69 - Diagnostic Assembly Instance 789
Name Data Type Size in Bytes
RunMode BOOL
Reserved1(1) BOOL
DiagnosticActive BOOL
CIPSyncValid BOOL
1
CIPSyncTimeout BOOL
Reserved2 BOOL
Reserved3 BOOL
Reserved4 BOOL
DiagnosticSequenceCount SINT 1

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 147

Appendix C Module Diagnostic Assembly

Table 69 - Diagnostic Assembly Instance 789 (Continued)

Name Data Type Size in Bytes
Reserved5 BOOL
Reserved6 BOOL
Reserved7 BOOL
Reserved8 BOOL
Reserved9 BOOL
Reserved10 BOOL
Reserved11 BOOL
Reserved12 BOOL
2
Reserved13 BOOL
Reserved14 BOOL
BaseUnsupportedFault (5094 Only) (DIAG 1) BOOL
BaseIDFault (5094 Only) (DIAG 1) BOOL
FlashUpdateRequired (DIAG 1) BOOL
SelfTestFault (DIAG 1) BOOL
Reserved15 BOOL
Reserved16 BOOL
Reserved17 DINT 4
LocalClockOffset LINT 8
LocalClockOffsetTimestamp LINT 8
GrandMasterClockID[8] SINT 8
Point0_Diagnostic AB:5000_DI_Diag_Channel:D:0(2) 24
Point1_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point2_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point3_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point4_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point5_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point6_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point7_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point8_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point9_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point10_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point11_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point12_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point13_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point14_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point15_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
(1) These data types act as padding to enable byte alignment. They can be renamed.
(2) See Table 70 for structure "AB: 5000_DI_Diag_Channel:D:0"

Diagnostic Channel

The following Data Types must be retrieved as part of the Diagnostic

Assemblies Instance.
1. Diagnostic Digital w/Diagnostics Channel (Input)
- DATATYPE: AB:5000_DI_Diag_Channel:D:0
- Size = 24 bytes

148 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix C Module Diagnostic Assembly

Follow the information in Table 70 to add each member.

Table 70 - Structure for Data Type "AB:5000_DI_Diag_Channel:D:0"
Name Data Type Byte
Reserved1(1) BOOL
Fault BOOL
Uncertain BOOL
Reserved2 BOOL
Reserved3 BOOL
Reserved4 BOOL
FieldPowerOff (DIAG 1) BOOL
Reserved5 BOOL
2
Reserved6 BOOL
Reserved7 BOOL
Reserved8 BOOL
Reserved9 BOOL
Reserved10 BOOL
Reserved11 BOOL
Reserved12 BOOL
Reserved13 BOOL
Reserved14 INT 2
Reserved15 DINT 4
FieldPowerOnTimestamp LINT 8
FieldPowerOffTimestamp LINT 8
(1) These data types act as padding to enable byte alignment. They can be renamed.

2. Diagnostic Counters Base I/O Assembly

- DATATYPE: AB:5000_IO:DC:0
- Instance ID: 0x301 (769)
- Size = 16 bytes
Follow the information in Table 71 to add each member.
Table 71 - Diagnostic Assembly Instance 769
Name Data Type Size in Bytes
RunMode BOOL
Reserved1(1) BOOL
DiagnosticActive BOOL
Reserved2 BOOL
1
Reserved3 BOOL
Reserved4 BOOL
Reserved5 BOOL
Reserved6 BOOL
DiagnosticSequenceCount SINT 1
CIPConnections SINT 2
CIPLostPackets BOOL 4
CIPTimeouts BOOL 4
CPUUtilization BOOL 2
Reserved7 BOOL 2
(1) These data types act as padding to enable byte alignment. They can be renamed.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 149

Appendix C Module Diagnostic Assembly

Applies to these modules:

5094-IM8, 5094-IM8XT Module
5094 Standard I/O Modules
There are 3 Diagnostic Assemblies under these modules including 1 Diagnostic
Channel. From the Controller Organizer pane, expand Data Types and create
user-defined data types for the module.

Diagnostic Assemblies
1. Diagnostic Digital 8 Point w/Diagnostics Assembly (Input)
- DATATYPE: AB:5000_DI8_Diag:D:0
- Instance ID: 0x3CE (974)
- Size = 224 bytes

Follow the information in Table 72 to add each member.

Table 72 - Diagnostic Assembly Instance 974
Name Data Type Size in Bytes
RunMode BOOL
Reserved1(1) BOOL
DiagnosticActive BOOL
CIPSyncValid BOOL
1
CIPSyncTimeout BOOL
Reserved2 BOOL
Reserved3 BOOL
Reserved4 BOOL
DiagnosticSequenceCount SINT 1
Reserved5 BOOL
Reserved6 BOOL
Reserved7 BOOL
Reserved8 BOOL
Reserved9 BOOL
Reserved10 BOOL
Reserved11 BOOL
Reserved12 BOOL
2
Reserved13 BOOL
Reserved14 BOOL
BaseUnsupportedFault (5094 Only) (DIAG 1) BOOL
BaseIDFault (5094 Only) (DIAG 1) BOOL
FlashUpdateRequired (DIAG 1) BOOL
SelfTestFault (DIAG 1) BOOL
Reserved15 BOOL
Reserved16 BOOL
Reserved17 DINT 4
LocalClockOffset SINT 2
LocalClockOffsetTimestamp BOOL 4
GrandMasterClockID[8] BOOL 4
Point0_Diagnostic AB:5000_DI_Diag_Channel:D:0(2) 24
Point1_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point2_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point3_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point4_Diagnostic AB:5000_DI_Diag_Channel:D:0 24

150 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix C Module Diagnostic Assembly

Table 72 - Diagnostic Assembly Instance 974 (Continued)

Name Data Type Size in Bytes
Point5_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point6_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point7_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
(1) These data types act as padding to enable byte alignment. They can be renamed.
(2) See Table 73 for structure "AB: 5000_DI_Diag_Channel:D:0"

Diagnostic Channel

The following Data Types must be retrieved as part of the Diagnostic

Assemblies Instance.
1. Diagnostic Digital w/Diagnostics Channel (Input)
- DATATYPE: AB:5000_DI_Diag_Channel:D:0
- Size = 24 bytes

Follow the information in Table 73 to add each member.

Table 73 - Structure for Data Type "AB:5000_DI_Diag_Channel:D:0"
Name Data Type Byte
(1) BOOL
Reserved1
Fault BOOL
Uncertain BOOL
Reserved2 BOOL
Reserved3 BOOL
Reserved4 BOOL
FieldPowerOff (DIAG 1) BOOL
Reserved5 BOOL
2
Reserved6 BOOL
Reserved7 BOOL
Reserved8 BOOL
Reserved9 BOOL
Reserved10 BOOL
Reserved11 BOOL
Reserved12 BOOL
Reserved13 BOOL
Reserved14 INT 2
Reserved15 DINT 4
FieldPowerOnTimestamp LINT 8
FieldPowerOffTimestamp LINT 8
(1) These data types act as padding to enable byte alignment. They can be renamed.

2. Diagnostic Counters Base I/O Assembly

- DATATYPE: AB:5000_IO:DC:0
- Instance ID: 0x301 (769)
- Size = 16 bytes

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 151

Appendix C Module Diagnostic Assembly

Follow the information in Table 74 to add each member.

Table 74 - Diagnostic Assembly Instance 769
Name Data Type Size in Bytes
RunMode BOOL
Reserved1(1) BOOL
DiagnosticActive BOOL
Reserved2 BOOL
1
Reserved3 BOOL
Reserved4 BOOL
Reserved5 BOOL
Reserved6 BOOL
DiagnosticSequenceCount SINT 1
CIPConnections SINT 2
CIPLostPackets BOOL 4
CIPTimeouts BOOL 4
CPUUtilization BOOL 2
Reserved7 BOOL 2
(1) These data types act as padding to enable byte alignment. They can be renamed.

5094-IB16, 5094-IB16XT Module

Applies to these modules:
There are 3 Diagnostic Assemblies under these modules including 1 Diagnostic
5094 Standard I/O Modules Channel. From the Controller Organizer pane, expand Data Types and create
user-defined data types for the module.

Diagnostic Assemblies
1. Diagnostic Digital 16 Point w/Diagnostics Assembly (Input)
- DATATYPE: AB:5000_DI16_Diag:D:0
- Instance ID: 0x315 (789)
- Size = 416 bytes
Follow the information in Table 75 to add each member.
Table 75 - Diagnostic Assembly Instance 789
Name Data Type Size in Bytes
RunMode BOOL
Reserved1(1) BOOL
DiagnosticActive BOOL
CIPSyncValid BOOL
1
CIPSyncTimeout BOOL
Reserved2 BOOL
Reserved3 BOOL
Reserved4 BOOL
DiagnosticSequenceCount SINT 1

152 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix C Module Diagnostic Assembly

Table 75 - Diagnostic Assembly Instance 789 (Continued)

Name Data Type Size in Bytes
Reserved5 BOOL
Reserved6 BOOL
Reserved7 BOOL
Reserved8 BOOL
Reserved9 BOOL
Reserved10 BOOL
Reserved11 BOOL
Reserved12 BOOL
2
Reserved13 BOOL
Reserved14 BOOL
BaseUnsupportedFault (5094 Only) (DIAG 1) BOOL
BaseIDFault (5094 Only) (DIAG 1) BOOL
FlashUpdateRequired (DIAG 1) BOOL
SelfTestFault (DIAG 1) BOOL
Reserved15 BOOL
Reserved16 BOOL
Reserved17 DINT 4
LocalClockOffset LINT 8
LocalClockOffsetTimestamp LINT 8
GrandMasterClockID[8] SINT 8
Point0_Diagnostic AB:5000_DI_Diag_Channel:D:0(2) 24
Point1_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point2_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point3_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point4_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point5_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point6_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point7_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point8_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point9_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point10_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point11_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point12_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point13_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point14_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point15_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
(1) These data types act as padding to enable byte alignment. They can be renamed.
(2) See Table 76 for structure "AB: 5000_DI_Diag_Channel:D:0"

Diagnostic Channel

The following Data Types must be retrieved as part of the Diagnostic

Assemblies Instance.
1. Diagnostic Digital w/Diagnostics Channel (Input)
- DATATYPE: AB:5000_DI_Diag_Channel:D:0
- Size = 24 bytes

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 153

Appendix C Module Diagnostic Assembly

Follow the information in Table 76 to add each member.

Table 76 - Structure for Data Type "AB:5000_DI_Diag_Channel:D:0"
Name Data Type Byte
Reserved1(1) BOOL
Fault BOOL
Uncertain BOOL
Reserved2 BOOL
Reserved3 BOOL
Reserved4 BOOL
FieldPowerOff (DIAG 1) BOOL
Reserved5 BOOL
2
Reserved6 BOOL
Reserved7 BOOL
Reserved8 BOOL
Reserved9 BOOL
Reserved10 BOOL
Reserved11 BOOL
Reserved12 BOOL
Reserved13 BOOL
Reserved14 INT 2
Reserved15 DINT 4
FieldPowerOnTimestamp LINT 8
FieldPowerOffTimestamp LINT 8
(1) These data types act as padding to enable byte alignment. They can be renamed.

2. Diagnostic Counters Base I/O Assembly

- DATATYPE: AB:5000_IO:DC:0
- Instance ID: 0x301 (769)
- Size = 16 bytes
Follow the information in Table 77 to add each member.
Table 77 - Diagnostic Assembly Instance 769
Name Data Type Size in Bytes
RunMode BOOL
Reserved1(1) BOOL
DiagnosticActive BOOL
Reserved2 BOOL
1
Reserved3 BOOL
Reserved4 BOOL
Reserved5 BOOL
Reserved6 BOOL
DiagnosticSequenceCount SINT 1
CIPConnections SINT 2
CIPLostPackets BOOL 4
CIPTimeouts BOOL 4
CPUUtilization BOOL 2
Reserved7 BOOL 2
(1) These data types act as padding to enable byte alignment. They can be renamed.

154 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix C Module Diagnostic Assembly

5094-IB32, 5094-IB32XT Module

Applies to these modules: There are 4 Diagnostic Assemblies under these modules including 1 Diagnostic
5094 Standard I/O Modules Channel. From the Controller Organizer pane, expand Data Types and create
user-defined data types for the module.

Diagnostic Assemblies
1. Diagnostic Digital 32 Point w/Diagnostics Assembly A (Input)
- DATATYPE: AB:5000_DI32_Diag_A:D:0
- Instance ID: 0x3C9 (969)
- Size = 416 bytes

Follow the information in Table 78 to add each member.

Table 78 - Diagnostic Assembly Instance 969
Name Data Type Size in Bytes
RunMode BOOL
Reserved1(1) BOOL
DiagnosticActive BOOL
CIPSyncValid BOOL
1
CIPSyncTimeout BOOL
Reserved2 BOOL
Reserved3 BOOL
Reserved4 BOOL
DiagnosticSequenceCount SINT
Reserved5 BOOL
Reserved6 BOOL
Reserved7 BOOL
Reserved8 BOOL
Reserved9 BOOL
Reserved10 BOOL
Reserved11 BOOL
Reserved12 BOOL 2
Reserved13 BOOL
Reserved14 BOOL
BaseUnsupportedFault (5094 Only) (DIAG 1) BOOL
BaseIDFault (5094 Only) (DIAG 1) BOOL
FlashUpdateRequired (DIAG 1) BOOL
SelfTestFault (DIAG 1) BOOL
Reserved15 BOOL
Reserved16 BOOL
Reserved17 DINT 4
LocalClockOffset LINT 8
LocalClockOffsetTimestamp LINT 8
GrandMasterClockID[8] SINT 8
Point0_Diagnostic AB:5000_DI_Diag_Channel:D:0(2) 24
Point1_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point2_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point3_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point4_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point5_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point6_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point7_Diagnostic AB:5000_DI_Diag_Channel:D:0 24

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 155

Appendix C Module Diagnostic Assembly

Table 78 - Diagnostic Assembly Instance 969 (Continued)

Name Data Type Size in Bytes
Point8_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point9_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point10_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point10_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point12_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point13_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point14_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point15_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
(1) These data types act as padding to enable byte alignment. They can be renamed.
(2) See Table 80 for structure "AB: 5000_DI_Diag_Channel:D:0"

2. Diagnostic Digital 32 Point w/Diagnostics Assembly B (Input)

- DATATYPE: AB:5000_DI32_Diag_B:D:0
- Instance ID: 0x3CA (970)
- Size = 384 bytes

Follow the information in Table 79 to add each member.

Table 79 - Diagnostic Assembly Instance 970
Name Data Type Size in Bytes
Point16_Diagnostic AB:5000_DI_Diag_Channel:D:0(1) 24
Point17_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point18_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point19_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point20_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point21_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point22_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point23_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point24_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point25_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point26_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point27_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point28_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point29_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point30_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
Point31_Diagnostic AB:5000_DI_Diag_Channel:D:0 24
(1) See Table 81 for structure "AB:5000_DO_Diag2_Channel:D:0"

Diagnostic Channel

The following Data Types must be retrieved as part of the Diagnostic

Assemblies Instance.
1. Diagnostic Digital w/Diagnostics Channel (input)
- DATATYPE: AB:5000_DI_Diag_Channel:D:0
- Size = 24 bytes

156 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix C Module Diagnostic Assembly

Follow the information in Table 80 to add each member.

Table 80 - Structure for Data Type "AB:5000_DI_Diag_Channel:D:0"
Name Data Type Byte
Reserved1(1) BOOL
Fault BOOL
Uncertain BOOL
Reserved2 BOOL
Reserved3 BOOL
Reserved4 BOOL
FieldPowerOff (DIAG 1) BOOL
Reserved5 BOOL
2
Reserved6 BOOL
Reserved7 BOOL
Reserved8 BOOL
Reserved9 BOOL
Reserved10 BOOL
Reserved11 BOOL
Reserved12 BOOL
Reserved13 BOOL
Reserved14 INT 2
Reserved15 DINT 4
FieldPowerOnTimestamp LINT 8
FieldPowerOffTimestamp LINT 8
(1) These data types act as padding to enable byte alignment. They can be renamed.

2. Diagnostic Counters Base I/O Assembly

- DATATYPE: AB:5000_IO:DC:0
- Instance ID: 0x301 (769)
- Size = 16 bytes
Follow the information in Table 81 to add each member.
Table 81 - Diagnostic Assembly Instance 769
Name Data Type Size in Bytes
RunMode BOOL
Reserved1(1) BOOL
DiagnosticActive BOOL
Reserved2 BOOL
1
Reserved3 BOOL
Reserved4 BOOL
Reserved5 BOOL
Reserved6 BOOL
DiagnosticSequenceCount SINT 1
CIPConnections SINT 2
CIPLostPackets BOOL 4
CIPTimeouts BOOL 4
CPUUtilization BOOL 2
Reserved7 BOOL 2
(1) These data types act as padding to enable byte alignment. They can be renamed.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 157

Appendix C Module Diagnostic Assembly

5094-OA16, 5094-OA16XT Module

Applies to these modules: There are 2 Diagnostic Assemblies under these modules including 1 Diagnostic
5094 Standard I/O Modules Channel. From the Controller Organizer pane, expand Data Types and create
user-defined data types for the module.

Diagnostic Assemblies
1. Diagnostic Counters Base I/O Assembly
- DATATYPE: AB:5000_IO:DC:0
- Instance ID: 0x301 (769)
- Size = 16 bytes

Follow the information in Table 82 to add each member.

Table 82 - Diagnostic Assembly Instance 769
Name Data Type Size in Bytes
RunMode BOOL
Reserved1(1) BOOL
DiagnosticActive BOOL
Reserved2 BOOL
1
Reserved3 BOOL
Reserved4 BOOL
Reserved5 BOOL
Reserved6 BOOL
DiagnosticSequenceCount SINT 1
CIPConnections SINT 2
CIPLostPackets BOOL 4
CIPTimeouts BOOL 4
CPUUtilization BOOL 2
Reserved7 BOOL 2
(1) These data types act as padding to enable byte alignment. They can be renamed.

2. Diagnostic Digital 16 Point w/Diagnostics (Type 3) Assembly (Output)

- DATATYPE: AB:5000_DO16_Diag3:D:0
- Instance ID: 0x319 (793)
- Size = 416 bytes

Follow the information in Table 83 to add each member.

Table 83 - Diagnostic Assembly Instance 793
Name Data Type Size in Bytes
RunMode BOOL
Reserved1(1) BOOL
DiagnosticActive BOOL
CIPSyncValid BOOL
1
CIPSyncTimeout BOOL
Reserved2 BOOL
Reserved3 BOOL
Reserved4 BOOL
DiagnosticSequenceCount SINT 1

158 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix C Module Diagnostic Assembly

Table 83 - Diagnostic Assembly Instance 793 (Continued)

Name Data Type Size in Bytes
Reserved5 BOOL
Reserved6 BOOL
Reserved7 BOOL
Reserved8 BOOL
Reserved9 BOOL
Reserved10 BOOL
Reserved11 BOOL
Reserved12 BOOL
2
Reserved13 BOOL
Reserved14 BOOL
BaseUnsupportedFault (5094 Only) (DIAG 1) BOOL
BaseIDFault (5094 Only) (DIAG 1) BOOL
FlashUpdateRequired (DIAG 1) BOOL
SelfTestFault (DIAG 1) BOOL
Reserved15 BOOL
Reserved16 BOOL
Reserved17 SINT[4] 4
LocalClockOffset LINT 8
LocalClockOffsetTimestamp LINT 8
GrandMasterClockID SINT[8] 8
Point1_Diagnostic AB:5000_DO_Diag3_Channel:D:0(2) 24
Point2_Diagnostic AB:5000_DO_Diag3_Channel:D:0 24
Point3_Diagnostic AB:5000_DO_Diag3_Channel:D:0 24
Point4_Diagnostic AB:5000_DO_Diag3_Channel:D:0 24
Point5_Diagnostic AB:5000_DO_Diag3_Channel:D:0 24
Point6_Diagnostic AB:5000_DO_Diag3_Channel:D:0 24
Point7_Diagnostic AB:5000_DO_Diag3_Channel:D:0 24
Point8_Diagnostic AB:5000_DO_Diag3_Channel:D:0 24
Point9_Diagnostic AB:5000_DO_Diag3_Channel:D:0 24
Point10_Diagnostic AB:5000_DO_Diag3_Channel:D:0 24
Point11_Diagnostic AB:5000_DO_Diag3_Channel:D:0 24
Point12_Diagnostic AB:5000_DO_Diag3_Channel:D:0 24
Point13_Diagnostic AB:5000_DO_Diag3_Channel:D:0 24
Point14_Diagnostic AB:5000_DO_Diag3_Channel:D:0 24
Point15_Diagnostic AB:5000_DO_Diag3_Channel:D:0 24
(1) These data types act as padding to enable byte alignment. They can be renamed.
(2) See Table 84 for structure "AB:5000_DO_Diag3_Channel:D:0"

Diagnostic Channel

The following Data Types must be retrieved as part of the Diagnostic

Assemblies Instance.
1. Diagnostic Digital w/Diagnostics (Type 3) Channel (Output)
- DATATYPE: AB:5000_DO_Diag3_Channel:D:0
- Size = 24 bytes

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 159

Appendix C Module Diagnostic Assembly

Follow the information in Table 84 to add each member.

Table 84 - Structure for Data Type "AB:5000_DO_Diag3_Channel:D:0"

Name Data Type Byte
Reserved1(1) BOOL
Fault BOOL
Uncertain BOOL
Reserved2 BOOL
Reserved3 BOOL
Reserved4 BOOL
FieldPowerOff BOOL
Reserved5 BOOL
2
Reserved6 BOOL
Reserved7 BOOL
Reserved8 BOOL
Reserved9 BOOL
Reserved10 BOOL
Reserved11 BOOL
Reserved12 BOOL
Reserved13 BOOL
Reserved14 SINT[6] 6
FieldPowerOnTimestamp LINT 8
FieldPowerOffTimestamp LINT 8
(1) These data types act as padding to enable byte alignment. They can be renamed.

5094-OB8, 5094-OB8XT Module

Applies to these modules:
There are 2 Diagnostic Assemblies under these modules including 1 Diagnostic
5094 Standard I/O Modules Channel. From the Controller Organizer pane, expand Data Types and create
user-defined data types for the module.

Diagnostic Assemblies
1. Diagnostic Counters Base I/O Assembly
- DATATYPE: AB:5000_IO:DC:0
- Instance ID: 0x301 (769)
- Size = 16 bytes

Follow the information in Table 85 to add each member.

Table 85 - Diagnostic Assembly Instance 769
Name Data Type Size in Bytes
RunMode BOOL
Reserved1(1) BOOL
DiagnosticActive BOOL
Reserved2 BOOL
1
Reserved3 BOOL
Reserved4 BOOL
Reserved5 BOOL
Reserved6 BOOL
DiagnosticSequenceCount SINT 1
CIPConnections SINT 2
CIPLostPackets BOOL 4

160 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix C Module Diagnostic Assembly

Table 85 - Diagnostic Assembly Instance 769 (Continued)

Name Data Type Size in Bytes
CIPTimeouts BOOL 4
CPUUtilization BOOL 2
Reserved7 BOOL 2
(1) These data types act as padding to enable byte alignment. They can be renamed.

2. Diagnostic Digital 8 Point w/Diagnostics, High Current

Assembly (Output)
- DATATYPE: AB:5000_DO8_HighCurrent:D:0
- Instance ID: 0x30F (783)
- Size = 352 bytes

Follow the information in Table 86 to add each member.

Table 86 - Diagnostic Assembly Instance 783
Name Data Type Size in Bytes
RunMode BOOL
Reserved1(1) BOOL
DiagnosticActive BOOL
1
CIPSyncValid BOOL
CIPSyncTimeout BOOL
Reserved2 BOOL
DiagnosticSequenceCount SINT 1
Reserved3 BOOL
Reserved4 BOOL
Reserved5 BOOL
Reserved6 BOOL
Reserved7 BOOL
Reserved8 BOOL
Reserved9 BOOL
Reserved10 BOOL
2
Reserved11 BOOL
Reserved12 BOOL
BaseUnsupportedFault (5094 Only) (DIAG 1) BOOL
BaseIDFault (5094 Only) (DIAG 1) BOOL
FlashUpdateRequired (DIAG 1) BOOL
SelfTestFault (DIAG 1) BOOL
Reserved13 BOOL
Reserved14 BOOL
Reserved15 SINT[4] 4
LocalClockOffset LINT 8
LocalClockOffsetTimestamp LINT 8
GrandMasterClockID SINT[8] 8
Point1_Diagnostic AB:5000_DO_Diag2_Channel:D:0(2) 40
Point2_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point3_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point4_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point5_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point6_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point7_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
(1) These data types act as padding to enable byte alignment. They can be renamed.
(2) See Table 87 for structure "AB:5000_DO_Diag2_Channel:D:0"

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 161

Appendix C Module Diagnostic Assembly

Diagnostic Channel

The following Data Types must be retrieved as part of the Diagnostic

Assemblies Instance.
1. Diagnostic Digital w/Diagnostics (Type 2) Channel (Output)
- DATATYPE: AB:5000_DO_Diag2_Channel:D:0
- Size = 40 bytes

Follow the information in Table 87 to add each member.

Table 87 - Structure for Data Type "AB:5000_DO_Diag2_Channel:D:0"

Name Data Type Byte
Reserved1(1) BOOL
Fault BOOL
Uncertain BOOL
NoLoad (DIAG 1) BOOL
ShortCircuit (DIAG 1) BOOL
Reserved2 BOOL
FieldPowerOff (DIAG 1) BOOL
Reserved3 BOOL
2
Reserved4 BOOL
Reserved5 BOOL
Reserved6 BOOL
Reserved7 BOOL
Reserved8 BOOL
Reserved9 BOOL
Reserved10 BOOL
Reserved11 BOOL
Reserved12 SINT[6] 6
NoLoadTimestamp LINT 8
ShortCircuitTimestamp LINT 8
FieldPowerOnTimestamp LINT 8
FieldPowerOffTimestamp LINT 8
(1) These data types act as padding to enable byte alignment. They can be renamed.

5094-OB16, 5094-OB16XT Module

Applies to these modules:
There are 3 Diagnostic Assemblies under these modules including 1 Diagnostic
5094 Standard I/O Modules Channel. From the Controller Organizer pane, expand Data Types and create
user-defined data types for the module.

Diagnostic Assemblies
1. Diagnostic Counters Base I/O Assembly
- DATATYPE: AB:5000_IO:DC:0
- Instance ID: 0x301 (769)
- Size = 16 bytes

162 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix C Module Diagnostic Assembly

Follow the information in Table 88 to add each member.

Table 88 - Diagnostic Assembly Instance 769
Name Data Type Size in Bytes
RunMode BOOL
Reserved1(1) BOOL
DiagnosticActive BOOL
Reserved2 BOOL
1
Reserved3 BOOL
Reserved4 BOOL
Reserved5 BOOL
Reserved6 BOOL
DiagnosticSequenceCount SINT 1
CIPConnections SINT 2
CIPLostPackets BOOL 4
CIPTimeouts BOOL 4
CPUUtilization BOOL 2
Reserved7 BOOL 2
(1) These data types act as padding to enable byte alignment. They can be renamed.

2. Diagnostic Digital 16 Point w/Diagnostic (Type 2) Assembly A (Output)

- DATATYPE: AB:5000_DO16_Diag2_A:D:0
- Instance ID: 0x316 (790)
- Size = 352 bytes

Follow the information in Table 89 to add each member.

Table 89 - Diagnostic Assembly Instance 352
Name Data Type Size in Bytes
RunMode BOOL
Reserved1(1) BOOL
DiagnosticActive BOOL
CIPSyncValid BOOL
1
CIPSyncTimeout BOOL
Reserved2 BOOL
Reserved3 BOOL
Reserved4 BOOL
DiagnosticSequenceCount SINT 1
Reserved3 BOOL
Reserved4 BOOL
Reserved5 BOOL
Reserved6 BOOL
Reserved7 BOOL
Reserved8 BOOL
Reserved9 BOOL
Reserved10 BOOL
2
Reserved11 BOOL
Reserved12 BOOL
BaseUnsupportedFault (5094 Only) (DIAG 1) BOOL
BaseIDFault (5094 Only) (DIAG 1) BOOL
FlashUpdateRequired (DIAG 1) BOOL
SelfTestFault (DIAG 1) BOOL
Reserved13 BOOL
Reserved14 BOOL
Reserved15 SINT[4] 4
LocalClockOffset LINT 8

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 163

Appendix C Module Diagnostic Assembly

Table 89 - Diagnostic Assembly Instance 352 (Continued)

Name Data Type Size in Bytes
LocalClockOffsetTimestamp LINT 8
GrandMasterClockID SINT[8] 8
Point0_Diagnostic AB:5000_DO_Diag2_Channel:D:0(2) 40
Point1_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point2_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point3_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point4_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point5_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point6_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point7_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
(1) These data types act as padding to enable byte alignment. They can be renamed.
(2) See Table 91 for structure "AB:5000_DO_Diag2_Channel:D:0"

3. Diagnostic Digital 16 Point w/Diagnostic (Type 2) Assembly B (Output)

- DATATYPE: AB:5000_DO16_Diag2_B:D:0
- Instance ID: 0x317 (791)
- Size = 320 bytes

Follow the information in Table 90 to add each member.

Table 90 - Diagnostic Assembly Instance 791
Name Data Type Size in Bytes
Point8_Diagnostic AB:5000_DO_Diag2_Channel:D:0(1) 40
Point9_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point10_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point11_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point12_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point13_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point14_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point15_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
(1) See Table 91 for structure "AB:5000_DO_Diag2_Channel:D:0"

Diagnostic Channel

The following Data Types must be retrieved as part of the Diagnostic

Assemblies Instance.
1. Diagnostic Digital w/Diagnostics (Type 2) Channel (Output)
- DATATYPE: AB:5000_DO_Diag2_Channel:D:0
- Size = 40 bytes

164 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix C Module Diagnostic Assembly

Follow the information in Table 91 to add each member.

Table 91 - Structure for Data Type "AB:5000_DO_Diag2_Channel:D:0"
Name Data Type Byte
Reserved1(1) BOOL
Fault BOOL
Uncertain BOOL
NoLoad (DIAG 1) BOOL
ShortCircuit (DIAG 1) BOOL
OverTemperature (DIAG 4) BOOL
FieldPowerOff (DIAG 1) BOOL
Reserved2 BOOL
2
Reserved3 BOOL
Reserved4 BOOL
Reserved5 BOOL
Reserved6 BOOL
Reserved7 BOOL
Reserved8 BOOL
Reserved9 BOOL
Reserved10 BOOL
CalFault (DIAG 4) BOOL
Reserved11 BOOL
Reserved12 BOOL
Reserved13 BOOL
Reserved14 BOOL
Reserved15 BOOL
Reserved16 BOOL
Reserved17 BOOL
2
Reserved18 BOOL
Reserved19 BOOL
Reserved20 BOOL
Reserved21 BOOL
Reserved22 BOOL
Reserved23 BOOL
Reserved24 BOOL
Reserved25 BOOL
Reserved26 SINT[2] 2
InternalErroCount (DIAG 2) SINT 1
CalRange SINT 1
CalOffset REAL 4
CalGain REAL 4
CalLastDate LINT 8
NoLoadTimestamp LINT 8
ShortCircuitTimestamp LINT 8
OerTemperatureTimestamp LINT 8
FieldPowerOnTimestamp LINT 8
FieldPowerOffTimestamp LINT 8
(1) These data types act as padding to enable byte alignment. They can be renamed.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 165

Appendix C Module Diagnostic Assembly

5094-OB32, 5094-OB32XT Module

Applies to these modules:
There are 4 Diagnostic Assemblies under these modules including 1 Diagnostic
5094 Standard I/O Modules Channel. From the Controller Organizer pane, expand Data Types and create
user-defined data types for the module.

Diagnostic Assemblies
1. Diagnostic Counters Base I/O Assembly
- DATATYPE: AB:5000_IO:DC:0
- Instance ID: 0x301 (769)
- Size = 16 bytes

Follow the information in Table 92 to add each member.

Table 92 - Diagnostic Assembly Instance 769
Name Data Type Size in Bytes
RunMode BOOL
Reserved1(1) BOOL
DiagnosticActive BOOL
Reserved2 BOOL
1
Reserved3 BOOL
Reserved4 BOOL
Reserved5 BOOL
Reserved6 BOOL
DiagnosticSequenceCount SINT 1
CIPConnections SINT 2
CIPLostPackets BOOL 4
CIPTimeouts BOOL 4
CPUUtilization BOOL 2
Reserved7 BOOL 2
(1) These data types act as padding to enable byte alignment. They can be renamed.

2. Diagnostic Digital 32 Point w/Diagnostics (Type 2) Assembly A (Output)

- DATATYPE: AB:5000_DO32_Diag2_A:D:0
- Instance ID: 0x3CB (971)
- Size = 432 bytes

Follow the information in Table 93 to add each member.

Table 93 - Diagnostic Assembly Instance 971
Name Data Type Size in Bytes
RunMode BOOL
Reserved1(1) BOOL
DiagnosticActive BOOL
CIPSyncValid BOOL
1
CIPSyncTimeout BOOL
Reserved2 BOOL
Reserved3 BOOL
Reserved4 BOOL
DiagnosticSequenceCount SINT 1

166 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix C Module Diagnostic Assembly

Table 93 - Diagnostic Assembly Instance 971 (Continued)

Name Data Type Size in Bytes
Reserved3 BOOL
Reserved4 BOOL
Reserved5 BOOL
Reserved6 BOOL
Reserved7 BOOL
Reserved8 BOOL
Reserved9 BOOL
Reserved10 BOOL
2
Reserved11 BOOL
Reserved12 BOOL
BaseUnsupportedFault (5094 Only) (DIAG 1) BOOL
BaseIDFault (5094 Only) (DIAG 1) BOOL
FlashUpdateRequired (DIAG 1) BOOL
SelfTestFault (DIAG 1) BOOL
Reserved13 BOOL
Reserved14 BOOL
Reserved15 SINT[4] 4
LocalClockOffset LINT 8
LocalClockOffsetTimestamp LINT 8
GrandMasterClockID SINT[8] 8
Point0_Diagnostic AB:5000_DO_Diag2_Channel:D:0(2) 40
Point1_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point2_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point3_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point4_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point5_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point6_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point7_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point8_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point9_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
(1) These data types act as padding to enable byte alignment. They can be renamed.
(2) See Table 96 for structure "AB:5000_DO_Diag2_Channel:D:0"

3. Diagnostic Digital 32 Point w/Diagnostics (Type 2) Assembly B (Output)

- DATATYPE: AB:5000_DO32_Diag2_B:D:0
- Instance ID: 0x3CC (972)
- Size = 440 bytes

Follow the information in Table 94 to add each member.

Table 94 - Diagnostic Assembly Instance 972
Name Data Type Size in Bytes
Point10_Diagnostic AB:5000_DO_Diag2_Channel:D:0(1) 40
Point11_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point12_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point13_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point14_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point15_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point16_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point17_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point18_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point19_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point20_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
(1) See Table 96 for structure "AB:5000_DO_Diag2_Channel:D:0"

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 167

Appendix C Module Diagnostic Assembly

4. Diagnostic Digital 32 Point w/Diagnostics (Type 2) Assembly C (Output)

- DATATYPE: AB:5000_DO32_Diag2_C:D:0
- Instance ID: 0x3CD (973)
- Size = 440 bytes

Follow the information in Table 95 to add each member.

Table 95 - Diagnostic Assembly Instance 973
Name Data Type Size in Bytes
Point10_Diagnostic (1) 40
AB:5000_DO_Diag2_Channel:D:0
Point11_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point12_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point13_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point14_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point15_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point16_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point17_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point18_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point19_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
Point20_Diagnostic AB:5000_DO_Diag2_Channel:D:0 40
(1) See Table 96 for structure "AB:5000_DO_Diag2_Channel:D:0"

Diagnostic Channel

The following Data Types must be retrieved as part of the Diagnostic

Assemblies Instance.
1. Diagnostic Digital w/Diagnostics (Type 2) Channel (Output)
- DATATYPE: AB:5000_DO_Diag2_Channel:D:0
- Size = 40 bytes

Follow the information in Table 96 to add each member.

Table 96 - Structure for Data Type "AB:5000_DO_Diag2_Channel:D:0"

Name Data Type Byte
(1) BOOL
Reserved1
Fault BOOL
Uncertain BOOL
NoLoad (DIAG 1) BOOL
ShortCircuit (DIAG 1) BOOL
Reserved2 BOOL
FieldPowerOff (DIAG 1) BOOL
Reserved3 BOOL
2
Reserved4 BOOL
Reserved5 BOOL
Reserved6 BOOL
Reserved7 BOOL
Reserved8 BOOL
Reserved9 BOOL
Reserved10 BOOL
Reserved11 BOOL
Reserved12 SINT[6] 6
NoLoadTimestamp LINT 8

168 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix C Module Diagnostic Assembly

Table 96 - Structure for Data Type "AB:5000_DO_Diag2_Channel:D:0" (Continued)

Name Data Type Byte
ShortCircuitTimestamp LINT 8
FieldPowerOnTimestamp LINT 8
FieldPowerOffTimestamp LINT 8
(1) These data types act as padding to enable byte alignment. They can be renamed.

5094-OW8I, 5094-OW8IXT Module

Applies to these modules:
There are 2 Diagnostic Assemblies under these modules including 1 Diagnostic
5094 Standard I/O Modules Channel. From the Controller Organizer pane, expand Data Types and create
user-defined data types for the module.

Diagnostic Assemblies
1. Diagnostic Counters Base I/O Assembly
- DATATYPE: AB:5000_IO:DC:0
- Instance ID: 0x301 (769)
- Size = 16 bytes

Follow the information in Table 97 to add each member.

Table 97 - Diagnostic Assembly Instance 769
Name Data Type Size in Bytes
RunMode BOOL
Reserved1(1) BOOL
DiagnosticActive BOOL
Reserved2 BOOL
1
Reserved3 BOOL
Reserved4 BOOL
Reserved5 BOOL
Reserved6 BOOL
DiagnosticSequenceCount SINT 1
CIPConnections SINT 2
CIPLostPackets BOOL 4
CIPTimeouts BOOL 4
CPUUtilization BOOL 2
Reserved7 BOOL 2
(1) These data types act as padding to enable byte alignment. They can be renamed.

2. Diagnostic Digital 8 Point Diag (Type 3) Assembly (Output)

- DATATYPE: AB:5000_DO8_Diag3:D:0
- Instance ID: 0x389 (905)
- Size = 224 bytes

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 169

Appendix C Module Diagnostic Assembly

Follow the information in Table 98 to add each member.

Table 98 - Diagnostic Assembly Instance 905
Name Data Type Size in Bytes
RunMode BOOL
Reserved1(1) BOOL
DiagnosticActive BOOL
CIPSyncValid BOOL
1
CIPSyncTimeout BOOL
Reserved2 BOOL
FieldPowerOff (DIAG 1) BOOL
Reserved3 BOOL
DiagnosticSequenceCount SINT 1
Reserved4 BOOL
Reserved5 BOOL
Reserved6 BOOL
Reserved7 BOOL
Reserved8 BOOL
Reserved9 BOOL
Reserved10 BOOL
Reserved11 BOOL
2
Reserved12 BOOL
Reserved13 BOOL
BaseUnsupportedFault (5094 Only) (DIAG 1) BOOL
BaseIDFault (5094 Only) (DIAG 1) BOOL
FlashUpdateRequired (DIAG 1) BOOL
SelfTestFault (DIAG 1) BOOL
Reserved14 BOOL
Reserved15 BOOL
Reserved16 SINT[4] 4
LocalClockOffset LINT 8
LocalClockOffsetTimestamp LINT 8
GrandMasterClockID SINT[8] 8
FieldPowerOnTimestamp LINT 8
FieldPowerOffTimestamp LINT 8
Point0_Diagnostic (2)
AB:5000_DO_Diag3_Channel:D:0 24
Point1_Diagnostic AB:5000_DO_Diag3_Channel:D:0 24
Point2_Diagnostic AB:5000_DO_Diag3_Channel:D:0 24
Point3_Diagnostic AB:5000_DO_Diag3_Channel:D:0 24
Point4_Diagnostic AB:5000_DO_Diag3_Channel:D:0 24
Point5_Diagnostic AB:5000_DO_Diag3_Channel:D:0 24
Point6_Diagnostic AB:5000_DO_Diag3_Channel:D:0 24
Point7_Diagnostic AB:5000_DO_Diag3_Channel:D:0 24
(1) These data types act as padding to enable byte alignment. They can be renamed.
(2) See Table 99 for structure "AB:5000_DO_Diag3_Channel:D:0"

Diagnostic Channel

The following Data Types must be retrieved as part of the Diagnostic

Assemblies Instance.
1. Diagnostic Digital w/Diagnostics (Type 3) Channel (Output)
- DATATYPE: AB:5000_DO_Diag3_Channel:D:0
- Size = 24 bytes

170 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix C Module Diagnostic Assembly

Follow the information in Table 99 to add each member.

Table 99 - Structure for Data Type "AB:5000_DO_Diag3_Channel:D:0"
Name Data Type Byte
Reserved1(1) BOOL
Fault BOOL
Uncertain BOOL
Reserved2 BOOL
Reserved3 BOOL
Reserved4 BOOL
FieldPowerOff (DIAG 1) BOOL
Reserved5 BOOL
2
Reserved6 BOOL
Reserved7 BOOL
Reserved8 BOOL
Reserved9 BOOL
Reserved10 BOOL
Reserved11 BOOL
Reserved12 BOOL
Reserved13 BOOL
Reserved14 SINT[6] 6
FieldPowerOnTimestamp LINT 8
FieldPowerOffTimestamp LINT 8
(1) These data types act as padding to enable byte alignment. They can be renamed.

5094-IB16S, 5094-IB16SXT Module

Applies to these modules:
There are 4 Diagnostic Assemblies under these modules including 2 different
5094 Safety I/O Modules types of Diagnostic Channel. From the Controller Organizer pane, expand
Data Types and create user-defined data types for the module.

Diagnostic Assemblies
1. Diagnostic Counters Base I/O Assembly
- DATATYPE: AB:5000_IO:DC:0
- Instance ID: 0x301 (769)
- Size = 16 bytes

Follow the information in Table 100 to add each member.

Table 100 - Diagnostic Assembly Instance 769
Name Data Type Size in Bytes
RunMode BOOL
Reserved1(1) BOOL
DiagnosticActive BOOL
Reserved2 BOOL
1
Reserved3 BOOL
Reserved4 BOOL
Reserved5 BOOL
Reserved6 BOOL
DiagnosticSequenceCount SINT 1
CIPConnections INT 2
CIPLostPackets DINT 4

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 171

Appendix C Module Diagnostic Assembly

Table 100 - Diagnostic Assembly Instance 769 (Continued)

Name Data Type Size in Bytes
CIPTimeouts DINT 4
CPUUtilization INT 2
Reserved7 INT 2
(1) These data types act as padding to enable byte alignment. They can be renamed.

2. Diagnostic Digital Safety 16 Point Assembly A (Input)

- DATATYPE: AB:5000_SDI16_A:D:0
- Instance ID: 0x311 (785)
- Size = 480 bytes

Follow the information in Table 101 to add each member.

Table 101 - Diagnostic Assembly Instance 785
Name Data Type Size in Bytes
RunMode BOOL
Reserved1(1) BOOL
DiagnosticActive BOOL
CIPSyncValid BOOL
1
CIPSyncTimeout BOOL
Reserved2 BOOL
FieldPowerOff BOOL
Reserved3 BOOL
DiagnosticSequenceCount SINT 1
Reserved4 SINT[6] 6
LocalClockOffset LINT 8
LocalClockOffsetTimestamp LINT 8
GrandMasterClockID SINT[8] 8
Point0_Diagnostic AB:5000_SDI_Diag_Channel:D:0(2) 56
Point1_Diagnostic AB:5000_SDI_Diag_Channel:D:0 56
Point2_Diagnostic AB:5000_SDI_Diag_Channel:D:0 56
Point3_Diagnostic AB:5000_SDI_Diag_Channel:D:0 56
Point4_Diagnostic AB:5000_SDI_Diag_Channel:D:0 56
Point5_Diagnostic AB:5000_SDI_Diag_Channel:D:0 56
Point6_Diagnostic AB:5000_SDI_Diag_Channel:D:0 56
Point7_Diagnostic AB:5000_SDI_Diag_Channel:D:0 56
(1) These data types act as padding to enable byte alignment. They can be renamed.
(2) See Table 104 for structure "AB:5000_SDI_Diag_Channel:D:0"

3. Diagnostic Digital Safety 16 Point Assembly B (Input)

- DATATYPE: AB:5000_SDI16_B:D:0
- Instance ID: 0x31B (795)
- Size = 448 bytes

Follow the information in Table 102 to add each member.

Table 102 - Diagnostic Assembly Instance 795
Name Data Type Size in Bytes
Point8_Diagnostic AB:5000_SDI_Diag_Channel:D:0(1) 56
Point9_Diagnostic AB:5000_SDI_Diag_Channel:D:0 56
Point10_Diagnostic AB:5000_SDI_Diag_Channel:D:0 56
Point11_Diagnostic AB:5000_SDI_Diag_Channel:D:0 56
Point12_Diagnostic AB:5000_SDI_Diag_Channel:D:0 56

172 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix C Module Diagnostic Assembly

Table 102 - Diagnostic Assembly Instance 795 (Continued)

Name Data Type Size in Bytes
Point13_Diagnostic AB:5000_SDI_Diag_Channel:D:0 56
Point14_Diagnostic AB:5000_SDI_Diag_Channel:D:0 56
Point15_Diagnostic AB:5000_SDI_Diag_Channel:D:0 56
(1) See Table 104 for structure "AB:5000_SDI_Diag_Channel:D:0"

4. Diagnostic Digital Safety 16 Point Assembly C (Input)

- DATATYPE: 5000_SDI16_C:D:0
- Instance ID: 0x386 (902)
- Size = 384 bytes

Follow the information in Table 103 to add each member.

Table 103 - Diagnostic Assembly Instance 902
Name Data Type Size in Bytes
Point0_SafetyReadback AB:5000_SafetyReadback_Channel:D:0(1) 48
Point1_SafetyReadback AB:5000_SafetyReadback_Channel:D:0 48
Point2_SafetyReadback AB:5000_SafetyReadback_Channel:D:0 48
Point3_SafetyReadback AB:5000_SafetyReadback_Channel:D:0 48
Point4_SafetyReadback AB:5000_SafetyReadback_Channel:D:0 48
Point5_SafetyReadback AB:5000_SafetyReadback_Channel:D:0 48
Point6_SafetyReadback AB:5000_SafetyReadback_Channel:D:0 48
Point7_SafetyReadback AB:5000_SafetyReadback_Channel:D:0 48
(1) See Table 105 for structure "AB:5000_SafetyReadback_Channel:D:0"

Diagnostic Channel

The following Data Types must be retrieved as part of the Diagnostic

Assemblies Instance.
1. Diagnostic Digital Diag Safety Channel (Input)
- DATATYPE: AB:5000_SDI_Diag_Channel:D:0
- Size = 56 bytes

Follow the information in Table 104 to add each member.

Table 104 - Structure for Data Type "AB:5000_SDI_Diag_Channel:D:0"
Name Data Type Byte
(1) BOOL
Reserved1
Fault BOOL
Uncertain BOOL
Reserved2 BOOL
1
ShortCircuit BOOL
Reserved3 BOOL
FieldPowerOff BOOL
Reserved4 BOOL
Reserved5 SINT 1

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 173

Appendix C Module Diagnostic Assembly

Table 104 - Structure for Data Type "AB:5000_SDI_Diag_Channel:D:0" (Continued)

Name Data Type Byte
InternalFault BOOL
OverTemperature BOOL
CriticalTemperature BOOL
Reserved6 BOOL
1
Reserved7 BOOL
Reserved8 BOOL
Reserved9 BOOL
Reserved10 BOOL
Reserved11 SINT[5] 5
ShortCircuitTimestamp LINT 8
InternalFaultTimestamp LINT 8
FieldPowerOnTimestamp LINT 8
FieldPowerOffTimestamp LINT 8
OverTemperatureTimestamp LINT 8
CriticalTemperatureTimestamp LINT 8
(1) These data types act as padding to enable byte alignment. They can be renamed.

2. Diagnostic Safety Readback Channel (Output)

- DATATYPE: AB:5000_SafetyReadback_Channel:D:0
- Size = 48 bytes

Follow the information in Table 105 to add each member.

Table 105 - Structure for Data Type "AB:5000_SafetyReadback_Channel:D:0"
Name Data Type Byte
Reserved1(1) BOOL
Fault BOOL
Uncertain BOOL
Reserved2 BOOL
1
ShortCircuit BOOL
Reserved3 BOOL
FieldPowerOff BOOL
Reserved4 BOOL
Reserved5 SINT 1
InternalFault BOOL
Overload BOOL
Reserved6 BOOL
Reserved7 BOOL
1
Reserved8 BOOL
Reserved9 BOOL
Reserved10 BOOL
Reserved11 BOOL
Reserved12 SINT[5] 5
ShortCircuitTimestamp LINT 8
InternalFaultTimestamp LINT 8
OverloadTimestamp LINT 8
FieldPowerOnTimestamp LINT 8
FieldPowerOffTimestamp LINT 8
(1) These data types act as padding to enable byte alignment. They can be renamed.

174 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix C Module Diagnostic Assembly

5094-OB16S, 5094-OB16SXT Module

Applies to these modules:
There are 5 Diagnostic Assemblies under these modules including 1 Diagnostic
5094 Safety I/O Modules Channel. From the Controller Organizer pane, expand Data Types and create
user-defined data types for the module.

Diagnostic Assemblies
1. Diagnostic Counters Base I/O Assembly
- DATATYPE: AB:5000_IO:DC:0
- Instance ID: 0x301 (769)
- Size = 16 bytes

Follow the information in Table 106 to add each member.

Table 106 - Diagnostic Assembly Instance 769
Name Data Type Size in Bytes
RunMode BOOL
Reserved1(1) BOOL
DiagnosticActive BOOL
Reserved2 BOOL
1
Reserved3 BOOL
Reserved4 BOOL
Reserved5 BOOL
Reserved6 BOOL
DiagnosticSequenceCount SINT 1
CIPConnections INT 2
CIPLostPackets DINT 4
CIPTimeouts DINT 4
CPUUtilization INT 2
Reserved7 INT 2
(1) These data types act as padding to enable byte alignment. They can be renamed.

2. Diagnostic Digital Safety 16 Point Assembly A (Input)

- DATATYPE: AB:5000_SDO16_A:D:0
- Instance ID: 0x314 (788)
- Size = 384 bytes

Follow the information in Table 107 to add each member.

Table 107 - Diagnostic Assembly Instance 788
Name Data Type Size in Bytes
RunMode BOOL
Reserved1(1) BOOL
DiagnosticActive BOOL
CIPSyncValid BOOL
1
CIPSyncTimeout BOOL
Reserved2 BOOL
FieldPowerOff BOOL
Reserved3 BOOL
DiagnosticSequenceCount SINT 1
Reserved4 SINT[8] 8
LocalClockOffset LINT 8
LocalClockOffsetTimestamp LINT 8

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 175

Appendix C Module Diagnostic Assembly

Table 107 - Diagnostic Assembly Instance 788 (Continued)

Name Data Type Size in Bytes
GrandMasterClockID SINT[8] 8
Point0_Diagnostic AB:5000_SDO_Diag2_Channel:D:0(2) 88
Point1_Diagnostic AB:5000_SDO_Diag2_Channel:D:0 88
Point2_Diagnostic AB:5000_SDO_Diag2_Channel:D:0 88
Point3_Diagnostic AB:5000_SDO_Diag2_Channel:D:0 88
(1) These data types act as padding to enable byte alignment. They can be renamed.
(2) See Table 111 for structure "AB:5000_SDO_Diag2_Channel:D:0"

3. Diagnostic Digital Safety 16 Point Assembly B (Input)

- DATATYPE: AB:5000_SDO16_B:D:0
- Instance ID: 0x31A (794)
- Size = 352 bytes

Follow the information in Table 108 to add each member.

Table 108 - Diagnostic Assembly Instance 794
Name Data Type Size in Bytes
Point4_Diagnostic AB:5000_SDO_Diag2_Channel:D:0(1) 88
Point5_Diagnostic AB:5000_SDO_Diag2_Channel:D:0 88
Point6_Diagnostic AB:5000_SDO_Diag2_Channel:D:0 88
Point7_Diagnostic AB:5000_SDO_Diag2_Channel:D:0 88
(1) See Table 111 for structure "AB:5000_SDO_Diag2_Channel:D:0"

4. Diagnostic Digital Safety 16 Point Assembly C (Input)

- DATATYPE: AB:5000_SDO16_C:D:0
- Instance ID: 0x31F (799)
- Size = 352 bytes
Follow the information in Table 109 to add each member.
Table 109 - Diagnostic Assembly Instance 799
Name Data Type Size in Bytes
Point8_Diagnostic AB:5000_SDO_Diag2_Channel:D:0(1) 88
Point9_Diagnostic AB:5000_SDO_Diag2_Channel:D:0 88
Point10_Diagnostic AB:5000_SDO_Diag2_Channel:D:0 88
Point11_Diagnostic AB:5000_SDO_Diag2_Channel:D:0 88
(1) See Table 111 for structure "AB:5000_SDO_Diag2_Channel:D:0"

5. Diagnostic Digital Safety 16 Point Assembly D (Input)

- DATATYPE: AB:5000_SDO16_D:D:0
- Instance ID: 0x385 (901)
- Size = 352 bytes

Follow the information in Table 110 to add each member.

Table 110 - Diagnostic Assembly Instance 901
Name Data Type Size in Bytes
Point12_Diagnostic AB:5000_SDO_Diag2_Channel:D:0(1) 88
Point13_Diagnostic AB:5000_SDO_Diag2_Channel:D:0 88
Point14_Diagnostic AB:5000_SDO_Diag2_Channel:D:0 88
Point15_Diagnostic AB:5000_SDO_Diag2_Channel:D:0 88
(1) See Table 111 for structure "AB:5000_SDO_Diag2_Channel:D:0"

176 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix C Module Diagnostic Assembly

Diagnostic Channel

The following Data Types must be retrieved as part of the Diagnostic

Assemblies Instance.
1. Diagnostic Digital Safety Diag 2 Input Channel (Output)
- DATATYPE: AB:5000_SDO_Diag2_Channel:D:0
- Size = 88 bytes

Follow the information in Table 111 to add each member.

Table 111 - Structure for Data Type "AB:5000_SDO_Diag2_Channel:D:0"
Name Data Type Byte
Reserved1(1) BOOL
Fault BOOL
Uncertain BOOL
NoLoad BOOL
1
ShortCircuit BOOL
Reserved2 BOOL
FieldPowerOff BOOL
Reserved3 BOOL
DualChannelFault BOOL
Reserved4 BOOL
Reserved5 BOOL
Reserved6 BOOL
1
Reserved7 BOOL
Reserved8 BOOL
Reserved9 BOOL
Reserved10 BOOL
InternalFault BOOL
Overload BOOL
ShortCircuitGround BOOL
OverTemperature BOOL
1
CriticalTemperature BOOL
Reserved11 BOOL
Reserved12 BOOL
Reserved13 BOOL
Reserved14 SINT[5] 5
NoLoadTimestamp LINT 8
ShortCircuitTimestamp LINT 8
DualChannelFaultTimestamp LINT 8
InternalFaultTimestamp LINT 8
OverloadTimestamp LINT 8
ShortCircuitGroundTimestamp LINT 8
FieldPowerOnTimestamp LINT 8
FieldPowerOffTimestamp LINT 8
OverTemperatureTimestamp LINT 8
CriticalTemperatureTimestamp LINT 8
(1) These data types act as padding to enable byte alignment. They can be renamed.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 177

Appendix C Module Diagnostic Assembly

5094-OW4IS, 5094-OW4ISXT Module

Applies to these modules:
There are 2 Diagnostic Assemblies under these modules including 1 Diagnostic
5094 Safety I/O Modules Channel. From the Controller Organizer pane, expand Data Types and create
user-defined data types for the 5094-OW4IS or 5094-OW4ISXT module:

Diagnostic Assemblies
1. Diagnostic Counters Base I/O Assembly
- DATATYPE: AB:5000_IO:DC:0
- Instance ID: 0x301 (769)
- Size = 16 bytes

Follow the information in Table 112 to add each member.

Table 112 - Diagnostic Assembly Instance 769
Name Data Type Size in Bytes
RunMode BOOL
Reserved1(1) BOOL
DiagnosticActive BOOL
Reserved2 BOOL
1
Reserved3 BOOL
Reserved4 BOOL
Reserved5 BOOL
Reserved6 BOOL
DiagnosticSequenceCount SINT 1
CIPConnections INT 2
CIPLostPackets DINT 4
CIPTimeouts DINT 4
CPUUtilization INT 2
Reserved7 INT 2
(1) These data types act as padding to enable byte alignment. They can be renamed.

2. Diagnostic Digital Safety 4 Output Point Relay Assembly (Input)

- DATATYPE: AB:5000_SDO4_Relay:D:0
- Instance ID: 0x31C (796)
- Size = 224 bytes

Follow the information in Table 113 to add each member.

Table 113 - Diagnostic Assembly Instance 796
Name Data Type Size in Bytes
RunMode BOOL
Reserved1(1) BOOL
DiagnosticActive BOOL
CIPSyncValid BOOL
1
CIPSyncTimeout BOOL
Reserved2 BOOL
FieldPowerOff BOOL
Reserved3 BOOL
DiagnosticSequenceCount SINT 1
Reserved4 SINT[8] 8
LocalClockOffset LINT 8
LocalClockOffsetTimestamp LINT 8

178 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix C Module Diagnostic Assembly

Table 113 - Diagnostic Assembly Instance 796 (Continued)

Name Data Type Size in Bytes
GrandMasterClockID SINT[8] 8
Point0_Diagnostic AB:5000_SDO_Relay_Channel:D:0(2) 48
Point1_Diagnostic AB:5000_SDO_Relay_Channel:D:0 48
Point2_Diagnostic AB:5000_SDO_Relay_Channel:D:0 48
Point3_Diagnostic AB:5000_SDO_Relay_Channel:D:0 48
(1) These data types act as padding to enable byte alignment. They can be renamed.
(2) See Table 114 for structure "AB:5000_SDO_Relay_Channel:D:0"

Diagnostic Channel

The following Data Types must be retrieved as part of the Diagnostic

Assemblies Instance.
1. Diagnostic Digital Safety Relay Input Channel (Output)
- DATATYPE: AB:5000_SDO_Relay_Channel:D:0
- Size = 48 bytes

Follow the information in Table 114 to add each member.

Table 114 - Structure for Data Type "AB:5000_SDO_Relay_Channel:D:0"
Name Data Type Byte
Reserved1(1) BOOL
Fault BOOL
Uncertain BOOL
Reserved2 BOOL
1
Reserved3 BOOL
Reserved4 BOOL
FieldPowerOff BOOL
Reserved5 BOOL
Reserved6 SINT 1
InternalFault BOOL
Reserved7 BOOL
Reserved8 BOOL
OverTemperature BOOL
1
CriticalTemperature BOOL
Reserved9 BOOL
Reserved10 BOOL
Reserved11 BOOL
Reserved12 SINT[5] 5
InternalFaultTimestamp LINT 8
FieldPowerOnTimestamp LINT 8
FieldPowerOffTimestamp LINT 8
OverTemperatureTimestamp LINT 8
CriticalTemperatureTimestamp LINT 8
(1) These data types act as padding to enable byte alignment. They can be renamed.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 179

Appendix C Module Diagnostic Assembly

Create Message Type User Create MESSAGE type user tags for requests and associated response user tags
Tags for each of the new user-defined diagnostic assembly types.

Applies to these modules:

5094 Standard I/O Modules
5094 Safety I/O Modules

From the Controller Organizer pane, expand Tasks > MainTask >
MainProgram
1. Create MESSAGE type user tags for each request
2. Create associated response user tags for each new user-defined
diagnostic assembly type.
3. Add the user tags to your ladder program.

4. Expand the message tag to open the message configuration dialog

5. On the Configuration tab, select:
• Service type: Get Attribute Single
• Class: 4
• Attribute: 3
• Instance:
5094-IA16 and 5094-IA16XT
769 (301h) Diagnostic Counters Base I/O Assembly
789 (315h) Diagnostic Digital 16 Point w/Diagnostics Assembly (input)
5094-IM8 and 5094-IM8XT
769 (301h) Diagnostic Counters Base I/O Assembly
974 (3CEh) Diagnostic Digital 8 Point w/Diagnostics Assembly (Input)
5094-IB16 and 5094-IB16XT
769 (301h) Diagnostic Counters Base I/O Assembly
789 (315h) Diagnostic Digital 16 Point w/Diagnostics Assembly (Input)
5094-IB32, 5094-IB32XT
769 (301h) Diagnostic Counters Base I/O Assembly
969 (3C9) Diagnostic Digital 32 Point w/Diagnostics Assembly A
(Input)
970 (3CA) Diagnostic Digital 32 Point w/Diagnostics Assembly B
(Input)
5094-OA16 and 5094- OA16XT
769 (301h) Diagnostic Counters Base I/O Assembly
793 (319h) Diagnostic Digital 16 Point w/Diagnostics (Type 3) Assembly
(Output)
5094-OB8 and 5094- OB8XT
769 (301h) Diagnostic Counters Base I/O Assembly
783 (30Fh) Diagnostic Digital 8 Point w/Diagnostics, High Current
Assembly (Output)
5094-OB16 and 5094- OB16XT
769 (301h) Diagnostic Counters Base I/O Assembly
790 (316h) Diagnostic Digital 16 Point w/Diagnostics (Type 2) Assembly

180 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix C Module Diagnostic Assembly

A (Output)
791 (317h) Diagnostic Digital 16 Point w/Diagnostics (Type 2) Assembly
B (Output)
5094-OB32 and 5094-OB32XT
769 (301h) Diagnostic Counters Base I/O Assembly
971 (3CBh) Diagnostic Digital 32 Point w/Diagnostics (Type 2)
Assembly A (Output)
972 (3CCh) Diagnostic Digital 32 Point w/Diagnostics (Type 2)
Assembly B (Output)
973 (3CDh) Diagnostic Digital 32 Point w/Diagnostics (Type 2)
Assembly C (Output)
5094-OW8I and 5094- OW8IXT
769 (301h) Diagnostic Counters Base I/O Assembly
905 (389h) Diagnostic Digital 8 Point Diag (Type 3) Assembly (Output)
5094-IB16S, 5094- IB16SXT
769 (301h) Diagnostic Counters Base I/O Assembly
788 (314h) Diagnostic Digital Safety 16 Point Assembly A (Input)
794 (31Ah) Diagnostic Digital Safety 16 Point Assembly B (Input)
799 (31Fh) Diagnostic Digital Safety 16 Point Assembly C (Input)
901 (385h) Diagnostic Digital Safety 16 Point Assembly D (Input)
5094-OB16S, 5094- OB16SXT
769 (301h) Diagnostic Counters Base I/O Assembly
788 (314h) Diagnostic Digital Safety 16 Point Assembly A (Input)
794 (31Ah) Diagnostic Digital Safety 16 Point Assembly B (Input)
799 (31Fh) Diagnostic Digital Safety 16 Point Assembly C (Input)
901 (385h) Diagnostic Digital Safety 16 Point Assembly D (Input)
5094-OW4IS, 5094- OW4ISXT
769 (301h) Diagnostic Counters Base I/O Assembly
796 (31Ch) Diagnostic Digital Safety 4 Output Point Relay Assembly
(Input)
• Destination element: User-defined data type suitable for the instance
entered.
6. On the Communication tab, select the path to the module that you wish
to send the messages to.
7. Download the project and set to Run mode.

You can monitor the user-defined tag values from the Program Parameters
and Local Tags window, under the MainProgram task in the Controller
Organizer pane.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 181

Appendix C Module Diagnostic Assembly

Definitions for Diagnostic Table 115 describes the members inside Diagnostic Assembly Data Types:
Assembly Types
Table 115 - Definition of Members in Diagnostic Assembly Data Types
Name Data Type Definition Valid Values
• 0 = Idle.
RunMode BOOL Module's operating state
• 1 = Run.
• 0 = No diagnostics active.
Indicates if any diagnostics are active or if the prognostics
DiagnosticActive BOOL • 1 = One or more diagnostics are active or the
threshold is reached.
prognostics threshold is reached.
• 0 = Module is not synced.
CIPSyncValid BOOL Indicates if the module is synced with a 1588 master.
• 1 = Module is synced.
• 0 = A valid time master has not timed out.
Indicates if the module was once synced with a 1588 master, • 1 = A valid time master is detected on the backplane, but
CIPSyncTimeout BOOL the time master has timed out. The module is using its
but is not now due to a timeout
local clock and can be drifting away from the last known
time master.
Indicates that a field power loss condition exists on the • 0 = No field power off condition.
FieldPowerOff BOOL channel. • 1 = Field power off condition.
Increments for each time a distinct diagnostic condition is
detected, and when a distinct diagnostic condition transitions 0…255
DiagnosticSequenceCount SINT from detected to not detected. The value of 0 is skipped except during module power-up.
Set to zero by product reset or power cycle. Wraps from 255 (-
1)…1 skipping zero.
The offset from the local clock to the system time. This value
LocalClockOffset LINT helps to detect steps in time. This value updates when a PTP All.
update is received.
Shows the timestamp of the local clock offset in YYYY-MM-DD-
HH:mm:SS_mmm_uuu_nnn(UTC-00:00) format.
• YYYY = year
• MM = month
• DD = day
• HH = hour (24 hour)
LocalClockOffsetTimestamp LINT • mm = minutes A valid time or None if there is no recorded event time.
• SS = seconds
• mmm = milliseconds
• uuu = microseconds
• nnn = nanoseconds
• UTC-00:00 = Time zone
The EUI-64 Identity of the CIP Sync Grandmaster clock the
GrandMasterClockID SINT[8] All.
module is synced to.
• 0 = Good.
• 1 = Bad, causing fault.
Indicates that counter data is inaccurate and cannot be trusted If the bit is set to 1, you must troubleshoot the module to
Fault BOOL for use in the application. correct the cause of the inaccuracy.
IMPORTANT: Once the condition that caused the tag to
change to 1 is removed, the bit automatically resets to 0.
• 0 = Good data.
• 1 = Uncertain data.
Indicates that the counter data can be inaccurate but the If the bit is set to 1, you must troubleshoot the module to
Uncertain BOOL degree of inaccuracy is not known. correct the cause of the inaccuracy.
IMPORTANT: Once the condition that caused the tag to
change to 1 is removed, the bit automatically resets to 0.
• 0 = No Load condition does not exist.
NoLoad BOOL Shows whether a load fault is present.
• 1 = No Load condition exists.
Shows whether an output short circuit or overcurrent fault is • 0 = No Short Circuit condition exists.
ShortCircuit BOOL present on the point. • 1 = Short Circuit condition is present.
• 0 = Field Power is not present.
FieldPower BOOL Shows whether field power is present on the point
• 1 = Field Power is present.
• 0 = Good.
DualChannelFault BOOL Shows whether a dual channel fault is present
• 1 = Fault is present.
Shows whether an internal fault is present. If there is an • 0 = No internal issue found in the product.
Internal Fault BOOL internal fault, cycle power to the module. • 1 = One or more of several internal diagnostics indicate
If the problem persists, contact Technical Support. an internal issue in the product.

182 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix C Module Diagnostic Assembly

Table 115 - Definition of Members in Diagnostic Assembly Data Types (Continued)

Name Data Type Definition Valid Values
• 0 = No Overload condition exists.
Overload BOOL Shows whether an overload fault is present on the point.
• 1 = Overload condition exists.
Shows whether a short circuit to ground fault is present on the • 0 = No fault.
ShortCircuitGround BOOL point. • 1 = Module is above the critical temperature limit.
Shows whether an over temperature fault is present. • 0 = No fault.
OverTemperature BOOL Over temperature means that the device is at a normal or • 1 = Module is at a higher temperature than its rated
higher temperature than its rated operating limits. operating limits.
Shows whether a critical temperature fault is present.
Critical temperature means that the device is above the critical • 0 = No fault.
CriticalTemperature BOOL temperature limit for proper operation and may shut down • 1 = Module is above the critical temperature limit.
without further warning.
Shows the timestamp of the last no load fault in YYYY-MM-DD-
HH:mm:SS.mmm (UTC-00:00) format.
• YYYY = year
• MM = month
• DD = day
• HH = hour (24 hour)
NoLoadTimestamp LINT A valid time or None if there is no recorded event time.
• mm = minutes
• SS = seconds
• mmm = milliseconds
• uuu = microseconds
• nnn = nanoseconds
• UTC-00:00 = Time zone
Shows the timestamp of the last output short circuit or
ShortCircuitTimestamp LINT A valid time or None if there is no recorded event time.
overcurrent fault. See NoLoadTimestamp for the format.
Shows the timestamp of the last dual channel fault. See
DualChannelFaultTimestamp LINT A valid time or None if there is no recorded event time.
NoLoadTimestamp for the format.
Shows the timestamp of the last internal fault. See
InternalFaultTimestamp LINT A valid time or None if there is no recorded event time.
NoLoadTimestamp for the format.
Shows the timestamp of the last overload fault. See
OverloadTimestamp LINT A valid time or None if there is no recorded event time.
NoLoadTimestamp for the format.
Shows the timestamp of the last short circuit to ground fault. A valid time or None if there is no recorded event time.
ShortCircuitGroundTimestamp LINT See NoLoadTimestamp for the format.
Shows the timestamp of the last time field power turned on. A valid time or None if there is no recorded event time.
FieldPowerOnTimestamp LINT See NoLoadTimestamp for the format.
Shows the timestamp of the last time field power turned off. A valid time or None if there is no recorded event time.
FieldPowerOffTimestamp LINT See NoLoadTimestamp for the format.
Shows the timestamp of the last over temperature fault. See A valid time or None if there is no recorded event time.
OverTemperatureTimestamp LINT NoLoadTimestamp for the format.
Shows the timestamp of the last critical temperature fault. See A valid time or None if there is no recorded event time.
CriticalTemperatureTimestamp LINT NoLoadTimestamp for the format.
Shows the number of CIP connections currently open to and 0…32767
CIPConnections INT through the adapter.
Shows the running sum of the number of Sequenced Address
CIPLostPackets DINT Item Sequence Numbers that are skipped in Class 0 and Class 1 0…2147483647
connections consumed by the adapter and its children.
Shows the running count of the number of connections that
CIPTimeouts DINT time out, both originated and targeted, to and through the 0…2147483647
adapter.
CPUUtilization INT Shows the usage of the compute engine. 0…100%

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 183

Appendix C Module Diagnostic Assembly

Notes:

184 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix D

Application/Wiring Examples for Safety

I/O Modules

Topic Page
Applies to these modules:
5094-IB16S and 5094-IB16SXT Module Wiring Diagrams 185
5094 Safety I/O Modules 5094-OB16S and 5094-OB16SXT Module Wiring Diagrams 189
5094-OW4IS and 5094-OW4ISXT Relay Module Wiring Diagrams 191

This appendix provides example wiring diagrams for the FLEX 5000 I/O safety
modules that can be used in functional safety applications.

The wiring configuration affects the safety application level to which a

FLEX 5000 I/O safety module is suitable.

IMPORTANT Conformity to requirements of the safety category and safety integrity level
must be determined for the entire system. You need to consider fault
exclusion specified in each of the wiring configurations.

5094-IB16S and The following wiring diagrams show the input modules in Safety Mode and
5094-IB16SXT Module Safety Pulse Mode.

Wiring Diagrams Test Output Association with Safety Input:

TO_0: SI_0, SI_8
TO_1: SI_1, SI_9
TO_2: SI_2, SI_10
TO_3: SI_3, SI_11
TO_4: SI_4, SI_12
TO_5: SI_5, SI_13
TO_6: SI_6, SI_14
TO_7: SI_7, SI_15

Note: In Safety Pulse mode, if external wiring short of 2 Safety inputs from the same Test Output point, the short circuit is not
detectable. Hence, in Dual Channel mode, use 2 Safety Inputs from different Test Output points.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 185

Appendix D Application/Wiring Examples for Safety I/O Modules

Figure 32 - 5094-IB16S Module - SIL 3, PLc, Cat. 2 in Safety Pulse Mode or Safety Mode
SI_n(n = 0...15)
TO_n(n = 0...7)
TO_n configured to Test Output with Pulse when using Safety
Pulse mode
SIL level and Category: SIL 3, PLc, Cat. 2
TO_n configured to Power Supply when using Safety mode
Fault Exclusion: None TO_n
Other: External connected device must be SIL 3 rated.
Point Mode: Safety Pulse Mode, Safety Mode

SI_n or SI_n+8

Figure 33 - 5094-IB16S Module - SIL 3, PLc, Cat. 2 in Safety Mode

SI_n(n = 0...15)
TO_n(n = 0...7)

SIL level and Category: SIL 3, PLc, Cat. 2

TO_n
Fault Exclusion: None
Other: External connected device must be
SIL 3 rated.
Point Mode: Safety Mode

SI_n

Figure 34 - 5094-IB16S Module - SIL 3, PLe, Cat. 4 in Safety Pulse Mode or Safety Mode
SI_n(n = 0...15)
TO_n(n = 0...7)
TO_n configured to Test Output with Pulse when using Safety
Pulse mode
TO_n configured to Power Supply when using Safety mode
SIL level and Category: SIL 3, PLe, Cat. 4
Fault Exclusion: External Wiring fault TO_n
Other: Use SIL 3/CAT 4/PLe qualified sensor.
Point Mode: Safety Pulse mode, Safety mode

SI_n or SI_n+8

186 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix D Application/Wiring Examples for Safety I/O Modules

Figure 35 - 5094-IB16S Module - SIL 3, PLe, Cat. 4 in Safety Mode

SI_n(n = 0...15)
TO_n(n = 0...7)

SIL level and Category: SIL 3, PLe, Cat. 4 TO_n

Fault Exclusion: External Wiring fault
Other: Use SIL 3/CAT 4/PLe qualified sensor.
Point Mode: Safety mode

SI_n or SI_n+8

Figure 36 - 5094-IB16S Module - SIL 3, PLe, Cat. 4 in Safety Pulse Mode

SI_n(n = 0...15)
TO_n(n = 0...7)
TO_n
SIL level and Category: SIL 3, PLe, Cat. 4
Fault Exclusion: None
SI_n
Point Mode: Safety Pulse Mode

The second SI channel can be any

TO_n+1 channel other than SI_n+8.

SI_n+1

Figure 37 - 5094-IB16S Module - SIL 3, PLe, Cat. 4 in Safety Mode

SI_n(n = 0...15)
TO_n(n = 0...7)
SIL level and Category: SIL 3, PLe, Cat. 4 TO_n
Fault Exclusion: External Wiring fault
Point Mode: Safety Mode
SI_n

TO_n+1 The second SI channel can be any

channel other than SI_n+8.

SI_n+1

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 187

Appendix D Application/Wiring Examples for Safety I/O Modules

Figure 38 - 5094-IB16S Module - SIL 3, PLe, Cat. 4 in Safety Pulse Mode

SI_n(n = 0...15)
TO_n(n = 0...7)
TO_n
SIL level and Category: SIL 3, PLe, Cat. 4
Fault Exclusion: None
Point Mode: Safety Pulse Mode SI_n
Equivalent Sensor

The second SI channel can be any

TO_n+1
channel other than SI_n+8.

SI_n+1

Figure 39 - 5094-IB16S Module - SIL 3, PLe, Cat. 4 in Safety Mode

SI_n(n = 0...15)
TO_n(n = 0...7)
TO_n
SIL level and Category: SIL 3, PLe, Cat. 4
Fault Exclusion: External Wiring fault
Point Mode: Safety Mode SI_n Equivalent Sensor

The second SI channel can be any

TO_n+1 channel other than SI_n+8.

SI_n+1

Figure 40 - 5094-IB16S Module - SIL 3, PLe, Cat. 4 in Safety Pulse Mode

SI_n(n = 0...15)
TO_n(n = 0...7)

SIL level and Category: SIL 3, PLe, Cat. 4 TO_n

Fault Exclusion: None
Point Mode: Safety Pulse Mode
SI_n Non-Equivalent Sensor

The second SI channel can be any

TO_n+1 channel other than SI_n+8.

SI_n+1

188 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix D Application/Wiring Examples for Safety I/O Modules

Figure 41 - 5094-IB16S Module - SIL 3, PLe, Cat. 4 in Safety Mode

SI_n(n = 0...15)
TO_n(n = 0...7)

SIL level and Category: SIL 3, PLe, Cat. 4 TO_n

Fault Exclusion: External Wiring fault
Point Mode: Safety Mode
SI_n Non-Equivalent Sensor

The second SI channel can be any

TO_n+1 channel other than SI_n+8.

SI_n+1

5094-OB16S and The following wiring diagrams show the output modules in Safety Mode and
5094-OB16SXT Module Safety Pulse Mode.

Wiring Diagrams IMPORTANT The Safety level shown in the diagrams is applicable to the module itself.
Connected devices must have their own status monitoring to achieve
application safety level.

Figure 42 - 5094-OB16S Module - SIL 3, PLc, Cat. 2 in Safety Mode or Safety Pulse Mode

n = 0…15

SIL level and Category: SIL 3, PLc, Cat. 2 SO_n

Fault Exclusion: None
Other: External connected device must be SIL 3 rated.
Point Mode: Safety Pulse Mode, Safety Mode

SO_n_RETURN

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 189

Appendix D Application/Wiring Examples for Safety I/O Modules

Figure 43 - 5094-OB16S Module - SIL 3, PLe, Cat. 4 in Safety Pulse Mode

SIL level and Category: SIL 3, PLe, Cat. 4 SO_n

Fault Exclusion: None
Point Mode: Safety Pulse Mode
SO_n_RETURN

n = 0…15
The channel pairs that support
Dual mode are:
Channel 0, 1 pair SO_n+1
Channel 2, 3 pair
Channel 4, 5 pair
SO_n+1_RETURN
Channel 6, 7 pair
Channel 8, 9 pair
Channel 10, 11 pair
Channel 12, 13 pair
Channel 14, 15 pair

Figure 44 - 5094-OB16S Module - SIL 3, PLe, Cat. 4 in Safety Mode

SIL level and Category: SIL 3, PLe, Cat. 4

Fault Exclusion: External Wiring fault SO_n
Point Mode: Safety Mode
SO_n_RETURN

n = 0…15
The channel pairs that support
Dual mode are: SO_n+1
Channel 0, 1 pair
Channel 2, 3 pair
Channel 4, 5 pair SO_n+1_RETURN
Channel 6, 7 pair
Channel 8, 9 pair
Channel 10, 11 pair
Channel 12, 13 pair
Channel 14, 15 pair

Figure 45 - 5094-OB16S Module - SIL 3, PLe, Cat. 4 in Safety Pulse Mode or Safety Mode

n = 0…15
Channel_n

SO_n
SIL level and Category: SIL 3, PLe, Cat. 4
Fault Exclusion: External Wiring fault
Other: Use IEC 60947 Safety Contactor.
Point Mode: Safety Pulse mode, Safety mode

SO_n_RETURN

190 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix D Application/Wiring Examples for Safety I/O Modules

5094-OW4IS and The following wiring diagrams show the relay output modules.
5094-OW4ISXT Relay Module
IMPORTANT The Safety level shown in below diagram is applicable to module itself.
Wiring Diagrams Connected device shall have their own status monitoring to achieve
application safety level.

ATTENTION: When you are using the relay to drive DC/AC inductive load, you
must connect a snubber across the load. Failure to connect a snubber across
the load (relay contacts) can result in generation of electromagnetic noise that
could disrupt nearby electrical equipment, including your FLEX 5000 chassis.
See the Industrial Automation Wiring and Grounding Guidelines, publication
1770-4.1

Figure 46 - 5094-OW4IS Module - SIL3, PLe, CAT4

SIL level and Category:

SIL3, PLe, CAT4
(Signal state change at least once a month)

SIL2, PLd, CAT3

(Signal state change at least once a year)

Fault Exclusion:
External Wiring fault

Other:
Qualified actuator must be used in the application
Fuse with proper rating should be connected to
prevent relay contacts from overload and short
circuit.

Figure 47 - 5094-OW4IS Module - SIL3, PLe, CAT4

SIL level and Category:

SIL3, PLe, CAT4
(Ladder logical alternative toggle each channel at
least once a month)

Fault Exclusion:
External Wiring fault

Other:
Qualified actuator must be used in the application
Fuse with proper rating should be connected to
prevent relay contacts from overload and short
circuit.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 191

Appendix D Application/Wiring Examples for Safety I/O Modules

Notes:

192 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix E

Safety Data for I/O Modules

This appendix lists calculated values for probability of a dangerous failure on

demand (PFD), average frequency of a dangerous failure per hour (PFH), and
Applies to these modules: mean time to failure (MTTF). PFD and PFH calculations comply with
IEC61508, edition 2, 2010.
5094 Safety I/O Modules
Calculated values of PFD and PFH appear in Table 116 on page 193. PFD and PFH
must be calculated for the devices within the system to comply with the SIL
level that is required for application.
You must be responsible for following the requirements of ISO 13849-1:2015,
to assess Performance Levels in their safety system.
You must functionally test every I/O module by individually toggling each
input point and also verify that the controller detects it within the safety
reaction time (SRT). Additionally, you must individually toggle each output
point by the controller and user-verify that the output point changes state.

For more information, refer to the FLEX 5000 safety controller manuals listed
in Additional Resources on page 11.

FLEX 5000 I/O Safety Input Table 116 lists the safety data for the 5094-IB16S and 5094-IB16SXT modules.
Module Safety Data Table 116 - 5094-IB16S and 5094-IB16SXT Digital Safety Parameter Data
Point Operation Type
Dual Channel
Single Channel (at controller
Attribute instruction)
Total Failure Rate (λ (safety related)) 1.246E-06 1.397E-06
Safe Failure Fraction (SFF) 99.969% 99.967%
Safe Failure Rate (λS) 7.97E-07 8.63E-07
Diagnostic Coverage (DC) 99.867% 99.913%
Safe Detected Failure Rate (λSD) 7.96E-07 8.62E-07
Safe Undetected Failure Rate (λSU) 1.06E-09 7.53E-10
Dangerous Failure Rate (λD) 4.4950E-07 5.3402E-07
Dangerous Detected Failure Rate (λDD) 4.4890E-07 5.3356E-07
Dangerous Undetected Failure Rate (λDU) 3.81E-10 4.6619E-10
Diagnostic Test Interval (hours) 4 4
Hardware Fault Tolerance (HFT) 0 1
Spurious Trip Rate (STR) 5.40 E-06 —
Mean Time to Failure, Spurious (MTTF-spurious), (hours) 185068 —
PFH (1/hours) 3.81E-10 4.6619E-10
PFDAVE, at Mission Time of 20 years 3.34E-05 4.08E-05
Safety Reaction Time (SRT), (millisecond) 6 6

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 193

Appendix E Safety Data for I/O Modules

FLEX 5000 I/O Safety Output Table 117 lists the safety data for the 5094-OB16S and 5094-OB16SXT modules.
Module Safety Data Table 117 - 5094-OB16S and 5094-OB16SXT Digital Safety Parameter Data
Point Operation Type
Attribute Single Channel Dual Channel
Total Failure Rate (λ (safety related)) 2.0565E-06 2.5524E-06
Safe Failure Fraction (SFF) 99.977% 99.983%
Safe Failure Rate (λS) 1.3238E-06 1.5666E-06
Safe Detected Failure Rate (λSD) 1.32E-06 1.57E-06
Safe Undetected Failure Rate (λSU) 8.40E-10 6.86E-10
Diagnostic Coverage (DC) 99.937% 99.956%
Dangerous Failure Rate (λD) 7.3278E-07 9.8585E-07
Dangerous Detected Failure Rate (λDD) 7.3232E-07 9.8541E-07
Dangerous Undetected Failure Rate (λDU) 4.6523E-10 4.3173E-10
Diagnostic Test Interval (hours) 4 4
Hardware Fault Tolerance (HFT) 0 1
Spurious Trip Rate (STR) 5.68E-06 —
Mean Time to Failure, Spurious (MTTF-spurious), (hours) 176037 —
PFH (1/hours) 4.6523E-10 4.3173E-10
PFDAVE, at Mission Time of 20 years 4.0754E-05 3.7819E-05
Safety Reaction Time (SRT), (millisecond) 4.5 4.5

FLEX 5000 I/O Safety Relay Table 118 lists the safety data for the 5094-OW4IS and 5094-OW4ISXT
Output Module Safety Data modules.
Table 118 - 5094-OW4IS and 5094-OW4ISXT Digital Safety Parameter Data
Point Operation Type
Attribute Single Channel Dual Channel
Total Failure Rate (λ (safety related)) 2.2470E-06 2.8740E-06
Safe Failure Fraction (SFF) 99.978% 99.984%
Safe Failure Rate (λS) 1.7129E-06 2.2634E-06
Diagnostic Coverage (DC) 99.909% 99.924%
Safe Detected Failure Rate (λSD) 1.71E-06 2.26E-06
Safe Undetected Failure Rate (λSU) 1.56E-09 1.73E-09
Dangerous Failure Rate (λD) 5.3388E-07 6.1058E-07
Dangerous Detected Failure Rate (λDD) 5.3340E-07 6.1011E-07
Dangerous Undetected Failure Rate (λDU) 4.8580E-10 4.6557E-10
Diagnostic Test Interval (hours) 4 4
Hardware Fault Tolerance (HFT) 0 1
Spurious Trip Rate (STR) 5.25E-06 —
Mean Time to Failure, Spurious (MTTF-spurious), (hours) 190638 —
PFH (1/hours) 4.8580E-10 4.6557E-10
PFDAVE, at Mission Time of 20 years 4.2556E-05 4.0784E-05
Safety Reaction Time (SRT), (millisecond) 20 20

194 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Appendix F

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.
5094-UM001E-EN-P, April 2020
Change
Add standard I/O modules 5094-IA16, 5094-IA16XT, 5094-IM8, 5094-IM8XT, 5094-IB32, 5094-IB32XT, 5094-OA16, 5094-
OA16XT, 5094-OB8, 5094-OB8XT, 5094-OB32, and 5094-OB32XT.
Add publications for new standard I/O modules to Additional Resources table.
Add SA field-side power source requirements for AC catalogs to section FLEX 5000 I/O SA Field-Side Power.
Add table Input Filter and Delays for input modules.
Update table Fault and Data Status for input modules.
Update table Time for a Module Output to Change States.
Update table Fault and Data Status for output modules.
Update table Module Definition Parameters.
Update section Events Category with information on 5094-IB32 and 5094-IB32XT modules.
Add topic Edit 5094-IA16 and 5094-IM8 Module Configuration.
Add topic Edit 5094-OA16 Module Configuration.
Add status indicators drawings for 5094-IA16, 5094-IA16XT, 5094-IM8, 5094-IM8XT, 5094-IB32, 5094-IB32XT, 5094-OA16,
5094-OA16XT, 5094-OB8, 5094-OB8XT, 5094-OB32, and 5094-OB32XT modules to Appendix A, Troubleshoot Your Module.
Add module tag definitions for 5094-IA16, 5094-IA16XT, 5094-IM8, 5094-IM8XT, 5094-IB32, 5094-IB32XT, 5094-OA16,
5094-OA16XT, 5094-OB8, 5094-OB8XT, 5094-OB32, and 5094-OB32XT modules to Appendix B, Module Tag Definitions.

5094-UM001D-EN-P, July 2019

Change
Added safety catalog numbers 5094-OW4IS and 5094-OW4ISXT.
Updated Chapter 5, Safety I/O Module Features.
Updated Chapter 7, Configure and Replace Safety Modules.
Updated Appendix C, Application/Wiring Examples for Safety I/O Modules.
Updated Appendix D, Safety Data for I/O Modules.

5094-UM001C-EN-P, April 2019

Change
Added safety catalog numbers 5094-IB16S, 5094-IB16SXT, 5094-OB16S, 5094-OB16SXT.
Added Chapter 5, Safety I/O Module Features.
Added Chapter 7, Configure and Replace Safety Modules.
Added Appendix C, Application/Wiring Examples for Safety I/O Modules.
Added Appendix D, Safety Data for I/O Modules.

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 195

Appendix F History of Changes

5094-UM001B-EN-P, September 2018

Change
Updated sentence on modules and modes with one owner-controller under the topic Ownership.
Updated Important table under the section Multiple Owners of FLEX 5000 Input Modules.
Added topic Configuration Changes in an Input Module with Multiple Owners.

196 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Index

Numerics counters category

5094-IB16 module 80
5094-IA16 15 5094-IB32 module 80
5094-IA16XT 15
5094-IB16 15
5094-IB16S 15 D
5094-IB16SXT 15 data exchange
5094-IB16XT 15 data echo 49
5094-IB32 15 data tags
5094-IB32XT 15 fault and status reporting
5094-IM8 15 input module 43
output modules 50
5094-IM8XT 15 data transmission
5094-OA16 15 multicast method 22
5094-OA16XT 15 data types 22, 24
5094-OB16 15 available with I/O modules 22
5094-OB16S 15 define module
5094-OB16SXT 15 Logix Designer application 78, 93
5094-OB16XT 15 diagnostic assembly
5094-OB32 15 instance 147, 149, 150, 151, 152, 154, 155, 156,
5094-OB32XT 15 157, 158, 160, 161, 162, 163, 164, 165,
166, 167, 168, 169, 170, 171, 172, 173,
5094-OB8 15
174, 175, 176, 177, 178, 179
5094-OB8XT 15 types 147, 150, 155, 158, 160, 162, 166, 169
5094-OW4IS 15 user tag 180
5094-OW4ISXT 15 user-defined 147, 150, 155, 158, 160, 162, 166,
5094-OW8I 15 169, 180
digital I/O module
5094-OW8IXT 15
configuration 89
digital input module
C filter time 41
digital output module
compatible Logix 5000 controllers 13 short circuit protection 53
configuration thermal switch 53
Logix Designer application 73 - 87, 89 - 98
Connection category 78, 94
Counters category 80 E
Events category 82
General category 77, 91 EDS
Input Points category 96 See electronic data sheet
module definition 78, 93 electronic data sheet 10
Module Info category 79, 96 electronic keying 28, 38, 78
Points category 80, 81, 85, 86, 87 events category 82 - 84
Test Output Points category 97
Time Sync category 85
module tags 117 - 141 F
configure
fault and status reporting 112 - 116
with Logix Designer application 37
connection 9 input module 43
output modules 50
fault handling
output modules 46 - 47 fault handling
inhibit the module 79 output modules 46 - 47
connection category 94 filter time
safety I/O modules 94 digital input module 41
standard I/O modules 78 firmware
connection types 22, 78 obtain from PCDC 37
controller organizer
monitor tag 87, 98 G
view module tag 87, 98
Controller Organizer pane general category 77, 91
MainProgram 181

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 197

Index

I module tags
5094-IA16 module 119 - 120
I/O status indicator
5094-IB16 module 122 - 127
description 106 - 112 5094-IB16S module 142 - 143
display 105 - 111 5094-IB32 module 128 - 133
input filter time 42, 80, 81 5094-IM8 module 120 - 121
5094-OA16 module 134 - 135
5094-OB16 module 137 - 138
L 5094-OB16S module 144 - 145
load current 5094-OB32 module 138 - 140
5094-OB8 module 135 - 136
digital output module 51
5094-OW4IS module 145 - 146
Logix 5000 controllers
5094-OW8I module 140 - 141
compatible with FLEX 5000 I/O modules 13 definitions 117
ownership of FLEX 5000 I/O modules 17 fault and status reporting
Logix Designer application 37 input module 43
configuration overview 20 output modules 50
configure safety I/O modules 89 - 98 naming 118
configure standard I/O modules 73 - 87 tag editor 118
Connection category 78, 94 viewing 87
connection types 22 module types 16
Counters category 80 multicast
digital I/O module configuration 89
data broadcast method 25
Events category 82
General category 77, 91
Input Points category 96 N
module definition 78, 93
Module Info category 79, 96 no load detection
module tag definitions 117 minimum time 51
module tags
5094-IA16 module 119 - 120
5094-IB16 module 122 - 127 O
5094-IB16S module 142 - 143
ODVA 10
5094-IB32 module 128 - 133
5094-IM8 module 120 - 121 output behavior
5094-OA16 module 134 - 135 after connection fault
5094-OB16 module 137 - 138 output modules 46 - 47
5094-OB16S module 144 - 145 output state
5094-OB32 module 138 - 140 change time 46
5094-OB8 module 135 - 136 ownership 17
5094-OW4IS module 145 - 146 multiple owners of input modules 18
5094-OW8I module 140 - 141
name module tag 118
Points category 80, 81, 85, 86, 87 P
tag editor 118
Test Output Points category 97 PCDC
Time Sync category 85 obtain firmware 37
troubleshooting 112 - 116 PFD 10
view module tag 87, 98 See probability of failure on demand.
PFH 10
See probability of failure per hour.
M points category
MainProgram 5094-IA16 module 80
Controller Organizer pane 181 5094-IB16 module 81 - 82
masters 9 5094-IB32 module 81 - 82
module definition 5094-IM8 module 80
dialog box 78, 93 5094-OA16 module 85
5094-OB16 module 86
module feature
5094-OB32 module 86
data echo 49 5094-OB8 module 86
module info category 5094-OW8I module 87
safety I/O modules 96 probability of failure
standard I/O modules 79 on demand 10
module keying 17 per hour 10
module status indicator proof test 10
description 104
display 105 - 111
module tag
viewing 98

198 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 Index

R troubleshooting 103 - 116

connection category 113
relay output module 16, 45, 69, 98, 111, 145, 191, 194
general category 113
Logix Designer application 112 - 116
module Info category 113
S module status indicator 17
SA Power status indicator tag editor 116
description 103 - 104
display 105 - 111
safety module U
5094-IB16S 15 unicast
5094-IB16SXT 15 data broadcast method 25
5094-OB16S 15
5094-OB16SXT 15
5094-OW4IS 15
5094-OW4ISXT 15
safety network number 10
safety relay output module 45, 69, 98, 145, 191,
194
short circuit protection
digital output module 53
slaves 9
SNN 10
See safety network number.
standard 10
standard module
5094-IA16 15
5094-IA16XT 15
5094-IB16 15
5094-IB16XT 15
5094-IB32 15
5094-IB32XT 15
5094-IM8 15
5094-IM8XT 15
5094-OA16 15
5094-OA16XT 15
5094-OB16 15
5094-OB16XT 15
5094-OB32 15
5094-OB32XT 15
5094-OB8 15
5094-OB8XT 15
5094-OW8I 15
5094-OW8IXT 15
status indicator, description
I/O status indicator 106 - 112
module status indicator 104
SA Power status indicator 103 - 104
status indicator, display
I/O status indicator 105 - 111
module status indicator 105 - 111
SA Power status indicator 105 - 111

T
thermal switch
digital output module 53
time sync category 85
time-scheduled output
accuracy 54
resolution 54
timestamping
selection 82

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 199

Index

Notes:

200 Rockwell Automation Publication 5094-UM001F-EN-P - May 2022

 FLEX 5000 Standard and Safety I/O Modules User Manual

Rockwell Automation Publication 5094-UM001F-EN-P - May 2022 201

Rockwell Automation Support
Use these resources to access support information.

Technical Support Center Find help with how-to videos, FAQs, chat, user forums, and product notification updates. rok.auto/support
Knowledgebase Access Knowledgebase articles. rok.auto/knowledgebase
Local Technical Support Phone Numbers Locate the telephone number for your country. rok.auto/phonesupport
Literature Library Find installation instructions, manuals, brochures, and technical data publications. rok.auto/literature
Product Compatibility and Download Center Get help determining how products interact, check features and capabilities, and find rok.auto/pcdc
(PCDC) associated firmware.

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 information on its website at rok.auto/pec.

Allen-Bradley, CompactLogix, ControlLogix, expanding human possibility, FactoryTalk, FLEX 5000, GuardLogix, Logix 5000, Rockwell Automation, RSNetWorx, Studio 5000, Studio 5000 Logix Designer, and
TechConnect are trademarks of Rockwell Automation, Inc.
CIP, CIP Safety, 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

Connect with us.

Publication 5094-UM001F-EN-P - May 2022

Supersedes Publication 5094-UM001E-EN-P - April 2020 Copyright © 2022 Rockwell Automation, Inc. All rights reserved.