Compactlogix 5069
Compactlogix 5069
Modules
Catalog Numbers 5069-IA16, 5069-IB8S, 5069-IB8SK, 5069-IB16,
5069-IB16F, 5069-IB16K, 5069-IB6F-3W, 5069-OA16, 5069-OB8,
5069-OBV8S, 5069-OBV8SK, 5069-OB16, 5069-OB16F, 5069-
OB16K, 5069-OW4I, 5069-OW16, 5069-OX4I
WARNING: Identifies information about practices or circumstances that can cause an explosion in a hazardous environment, which may lead to
personal injury or death, property damage, or economic loss.
ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or
economic loss. Attentions help you identify a hazard, avoid a hazard, and recognize the consequence.
IMPORTANT Identifies information that is critical for successful application and understanding of the product.
SHOCK HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that dangerous voltage may be
present.
BURN HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that surfaces may reach dangerous
temperatures.
ARC FLASH HAZARD: Labels may be on or inside the equipment, for example, a motor control center, to alert people to potential Arc Flash. Arc
Flash will cause severe injury or death. Wear proper Personal Protective Equipment (PPE). Follow ALL Regulatory requirements for safe work
practices and for Personal Protective Equipment (PPE).
Identifies information that is useful and can help to make a process easier to do or easier to understand.
Rockwell Automation recognizes that some of the terms that are currently used in our industry and in this
presentation 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.
Chapter 1
Digital Module Operation in a Controller and Software Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Control System Controller Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Software Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Types of Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Module Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Local I/O Modules or Remote I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . 20
Local I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Remote I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Secure Access to the System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Multiple Owners of Compact 5000 I/O Standard
Input Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Configuration Changes in a Standard Input Module with
Multiple Owners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Construct a System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Local I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Remote I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Use a 5069-ARM Address Reserve Module to Reserve a
Node Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Power the Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Use a 5069-FPD Field Potential Distributor to Establish New SA
Power Buses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Power Requirements When You Use Compact 5000 I/O
Safety Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Configure the Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Connections with Compact 5000 I/O Digital Modules . . . . . . . . . . . 36
Connections with Compact 5000 I/O Safety Modules . . . . . . . . . . . 39
Requested Packet Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Connection Over an EtherNet/IP Network . . . . . . . . . . . . . . . . . . . . . 43
Input Module Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Local Compact 5000 I/O Digital Input Modules. . . . . . . . . . . . . . . . . 43
Trigger Events for Standard Input Modules . . . . . . . . . . . . . . . . . . . . 44
Remote Compact 5000 I/O Digital Input Modules . . . . . . . . . . . . . . 44
Chapter 2
Features Common to Compact Input Module Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
5000 I/O Digital Modules Output Module Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Software Configurable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Module Data Quality Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Fault and Status Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Module Inhibiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Electronic Keying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Module Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Producer/Consumer Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Use CIP Sync Time with Fast
I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Timestamping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Chapter 5
Safety Module Features Safety Input Module Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Safety Application Suitability Levels . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Use Test Output with a Safety Input . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Single-channel Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Safety Input Fault Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Safety Input Delay Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Muting Lamp Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Discrepancy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Safety Output Module Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Safety Application Suitability Levels . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Safety Output with Test Pulse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Single-channel Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Dual-channel Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Safety Output Fault Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Fault and Status Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Appendix A
Troubleshoot Your Module Module Status Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Compact 5000 I/O Standard Input Modules Status Indicators. . . . . . 203
Compact 5000 I/O Standard Output Modules Status Indicators . . . . 205
Compact 5000 I/O Safety Input Module Status Indicators . . . . . . . . . 209
SA Status Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
I/O Status Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Compact 5000 I/O Safety Output Module Status Indicators . . . . . . . . 211
SA Status Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
I/O Status Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Use the Logix Designer Application for Troubleshooting . . . . . . . . . . . 213
Warning Signal in the I/O Configuration Tree. . . . . . . . . . . . . . . . . 213
Status and Fault Information in Module Properties Categories . 214
Module and Point Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Logix Designer Application Tag Editor. . . . . . . . . . . . . . . . . . . . . . . . 218
Internal Fault Triggered on the Safety Output Module . . . . . . . . . . . . . 218
Appendix D
Safety Data for Safety Modules Compact 5000 I/O Safety Input Module Safety Data . . . . . . . . . . . . . . . 268
Compact 5000 I/O Safety Output Module Safety Data . . . . . . . . . . . . . 269
Safety Reaction Time - 5069-OBV8S and 5069-OBV8SK Modules 270
Appendix E
Module Diagnostic Assembly Create User-defined Diagnostic Assembly Types . . . . . . . . . . . . . . . . . . 271
5069-IB8S, 5069-IB8SK Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
5069-OBV8S, 5069-OBV8SK Module . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Create Message Type User Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Definitions for Diagnostic Assembly Types . . . . . . . . . . . . . . . . . . . . . . . 279
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
About This Publication This manual describes how to use Compact 5000™ I/O digital modules in
Logix 5000™ control systems.
IMPORTANT In this manual, we use standard module to indicate a standard digital I/O
module. We use safety module to indicate a safety digital I/O module.
Further, we use Compact 5000 I/O digital module to indicate when a
concept or task applies to both the standard and safety digital I/O modules.
IMPORTANT The Compact 5000 I/O Serial module is only compatible with the
following controllers:
• CompactLogix™ 5380
• Compact GuardLogix™ 5380
• CompactLogix 5480
• ControlLogix® 5580
• GuardLogix 5580
Rockwell Automation recognizes that some of the terms that are currently
used in our industry and in this presentation 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.
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.
Upda
Topic Page
Updated Table 28 104
Added Figure: Configure No Load Detection—Compact 5000 I/O Safety Output Modules 104
Added Section: Configure Internal Short Circuit Detection for 5069-OBV8S and 5069-OBV8SK 109
Updated Tip 139
Updated Figure: Configure Points 194
Updated Figure: Point Diagnostics 217
If both standard and safety modules support a feature, you see icons for
both types.
Standard Modules Safety Modules
Timestamping
If only one type of module, standard or safety, supports a feature, you see only
one type of icon.
Standard Modules
Before Change.
CompactLogix 5380 Controller Compact GuardLogix 5380 SIL 2 Controller Compact GuardLogix 5380 SIL 3 Controller
After Change.
CompactLogix 5380 Controller Compact GuardLogix 5380 SIL 2 Controller Compact GuardLogix 5380 SIL 3 Controller
Topic Page
Controller and Software Compatibility 16
Types of Modules 18
Module Overview 19
Local I/O Modules or Remote I/O Modules 20
Secure Access to the System 25
Ownership 26
Construct a System 28
Power the Modules 30
Configure the Modules 36
Input Module Operation 43
Output Module Operation 45
Listen Only 49
External Means 53
Protected Operations 54
Considerations Specific to Safety Modules 55
Logix 5000™ controllers use Compact 5000™ I/O digital modules to control
devices in a control system.
Compact 5000 I/O digital modules use removable terminal blocks (RTBs) to
connect field-side wiring. You use the Studio 5000 Logix Designer®
application to configure the modules.
Controller and Software Controller and programming software compatibility requirements apply when
Compatibility you use Compact 5000 I/O digital modules.
Standard Modules
Controller Compatibility
Compatibility between Logix 5000 controllers and Compact 5000 I/O digital
modules varies based on module type and location. That is, whether the
module is a standard or safety I/O module and whether the module is local
or remote.
Software Compatibility
Compact 5000 I/O digital modules are supported in different minimum
versions of the Logix Designer application.
For example, Compact 5000 I/O standard modules support the Logix Designer
application, version 28 or later. Compact 5000 I/O safety modules support the
Safety Modules Logix Designer application, version 32 or later.
Table 2 - Compact 5000 I/O Digital Modules Controller and Software Compatibility Requirements
Controllers Logix Designer
Modules Location
System Cat. Nos. Application
5069-L320ER, 5069-L320ERMK, 5069-L330ERMK, 5069-L340ERM, Version 28.00.00 or later
5069-L350ERMK
5069-L306ER, 5069-L306ERM, 5069-L310ER, 5069-L310ERM,
CompactLogix 5380 5069-L310ERMK, 5069-L310ER-NSE, 5069-L310ERS2, Version 29.00.00 or later
5069-L320ERM, 5069-L320ERMK, 5069-L320ERP, 5069-L330ER, 5069-
L330ERM, 5069-L330ERMK, 5069-L340ER, 5069-L340ERP
5069-L350ERM, 5069-L350ERMK, 5069-L380ERM, 5069-L3100ERM Version 30.00.00 or later
5069-L46ERMW Version 32.00.00 or later
Local I/O modules CompactLogix 5480 5069-L430ERMW, 5069-L450ERMW, 5069-L4100ERMW, Version 32.01.00 or later
5069-L4200ERMW
5069-L306ERS2, 5069-L306ERMS2, 5069-L310ERS2,
5069-L310ERMS2, 5069-L320ERS2, 5069-L320ERS2K,
5069-L320ERMS2, 5069-L320ERMS2K, 5069-L330ERS2,
5069-5069-L330ERS2K, L330ERMS2, 5069-L330ERMS2K,
Compact GuardLogix 5380 Version 31.00.00 or later
5069-L340ERS2, 5069-L340ERMS2, 5069-L350ERS2,
Standard Modules 5069-L350ERS2K, 5069-L350ERMS2, 5069-L350ERMS2K,
5069-IA16, 5069-IB16, 5069-L380ERS2, 5069-L380ERMS2, 5069-L3100ERS2,
5069-IB16F, 5069- 5069-L3100ERMS2
IB16K, 5069-IB6F-3W, 5069-L320ER, 5069-L340ERM Version 28.00.00 or later
5069-OA16, 5069-OB8,
5069-OB16, 5069- 5069-L306ER, 5069-L306ERM, 5069-L310ER, 5069-L310ERM,
OB16F, 5069-OB16K, 5069-L310ERMK, 5069-L310ER-NSE, 5069-L310ERS2,
CompactLogix 5380 Version 29.00.00 or later
5069-OW4I, 5069- 5069-L320ERM, 5069-L320ERP, 5069-L330ER, 5069-L330ERM, 5069-
OW16, 5069-OX4I L340ER, 5069-L340ERP
5069-L350ERM, 5069-L380ERM, 5069-L3100ERM Version 30.00.00 or later
5069-L46ERMW Version 32.00.00 or later
CompactLogix 5480 5069-L430ERMW, 5069-L450ERMW, 5069-L4100ERMW, Version 32.01.00 or later
5069-L4200ERMW
Remote I/O modules 5069-L306ERS2, 5069-L306ERMS2, 5069-L310ERS2,
5069-L310ERMS2, 5069-L320ERS2, 5069-L320ERS2K,
5069-L320ERMS2, 5069-L320ERMS2K, 5069-L330ERS2,
5069-5069-L330ERS2K, L330ERMS2, 5069-L330ERMS2K,
Compact GuardLogix 5380 Version 31.00.00 or later
5069-L340ERS2, 5069-L340ERMS2, 5069-L350ERS2,
5069-L350ERS2K, 5069-L350ERMS2, 5069-L350ERMS2K,
5069-L380ERS2, 5069-L380ERMS2, 5069-L3100ERS2,
5069-L3100ERMS2
1756-L83E, 1756-L85E Version 28.00.00 or later
ControlLogix® 5580
1756-L81E, 1756-L82E, 1756-L84E Version 29.00.00 or later
GuardLogix 5580 1756-L81ES, 1756-L82ES, 1756-L83ES, 1756-L84ES Version 31.00.00 or later
5069-L306ERS2, 5069-L306ERMS2, 5069-L310ERS2,
5069-L310ERMS2, 5069-L320ERS2, 5069-L320ERS2K,
5069-L320ERMS2, 5069-L320ERMS2K, 5069-L330ERS2,
5069-5069-L330ERS2K, L330ERMS2, 5069-L330ERMS2K,
Local Compact GuardLogix 5380 5069-L340ERS2, 5069-L340ERMS2, 5069-L350ERS2,
5069-L350ERS2K, 5069-L350ERMS2, 5069-L350ERMS2K,
5069-L380ERS2, 5069-L380ERMS2, 5069-L3100ERS2,
Safety Modules 5069-L3100ERMS2
5069-IB8S, 5069-IB8SK, 5069-L306ERS2, 5069-L306ERMS2, 5069-L310ERS2, Version 32.00.00 or later
5069-OBV8S, 5069-L310ERMS2, 5069-L320ERS2, 5069-L320ERS2K,
5069-OBV8SK 5069-L320ERMS2, 5069-L320ERMS2K, 5069-L330ERS2,
5069-5069-L330ERS2K, L330ERMS2, 5069-L330ERMS2K,
Compact GuardLogix 5380
Remote 5069-L340ERS2, 5069-L340ERMS2, 5069-L350ERS2,
5069-L350ERS2K, 5069-L350ERMS2, 5069-L350ERMS2K,
5069-L380ERS2, 5069-L380ERMS2, 5069-L3100ERS2,
5069-L3100ERMS2
GuardLogix 5580 1756-L81ES, 1756-L82ES, 1756-L83ES, 1756-L84ES
Types of Modules Table 3 describes the Compact 5000 I/O digital modules.
Table 3 - Compact 5000 I/O Digital Modules
Standard Modules
Module Type Cat. No. Description
5069-IA16 79…264V AC 16-point, input module
5069-IB16 10…32V DC 16-point, sinking input module
5069-IB16K 10…32V DC 16-point, conformal coated sinking input module
5069-IB16F 10…32V DC 16-point, sinking fast input module
5069-IB6F-3W 10…32V DC 6-point, 3-wire, sinking fast input module
5069-OA16 85…264V AC 16-point, output module
Standard 5069-OB8 10…32V DC 8-point, sourcing high-current output module
5069-OB16 10…32V DC 16-point, sourcing output module
5069-OB16K 10…32V DC 16-point, conformal coated sourcing output module
5069-OB16F 10…32V DC 16-point, sourcing fast output module
5069-OW4I 5…264V AC /125V DC 4-point, isolated normally open relay output module
5069-OW16 5…264V AC/125V DC 16-point, normally open relay output module
5…264V AC /125V DC 4-point, isolated normally open/normally closed relay output
5069-OX4I module
5069-IB8S 18…32V DC 8-point, safety sinking input module
5069-IB8SK 18…32V DC 8-point, conformal coated safety sinking input module
Safety Modules 18…32V DC 8-point, safety output module that can be used as follows:
5069-OBV8S • Bipolar output module
Safety(1) • Sourcing output module
18…32V DC 8-point, conformal coated safety output module that can be used as
follows:
5069-OBV8SK • Bipolar output module
• Sourcing output module
(1) You can use the safety modules in applications that are rated up to, and including, SIL CL 3, PLe, Cat. 4 as defined in IEC 61508, IEC
61511, IEC 62061, and ISO 13849-1.
Module Overview Figure 1 shows the parts of a Compact 5000 I/O digital module.
IMPORTANT Compact 5000 I/O safety modules look the same from the front with the
Standard Modules exception that the safety modules have a red housing.
1 1
2 2
3 3
4 4
Safety Modules
Local I/O Modules or You can use Compact 5000 I/O digital modules as local or remote
Remote I/O Modules I/O modules, with some restrictions that are based on the module and
controller type. Compatibility requirements apply and are described in
Controller and Software Compatibility on page 16.
Local I/O modules are installed to the right of the controller and exchange data
with the controller over the system backplane.
Figure 2 - Local Compact 5000 I/O Digital Modules
CompactLogix 5380 Controller Local Compact 5000 I/ CompactLogix 5480 Controller Local Compact 5000 I/O Standard
O Standard Modules Modules
IMPORTANT Remember, some restrictions apply when you use the I/O modules
remotely. For example, you can use Compact 5000 I/O safety modules
as remote I/O modules only in Compact GuardLogix 5380 or GuardLogix
5380 control systems.
Figure 5 shows remote Compact 5000 I/O safety modules in a GuardLogix 5580
control application.
Figure 5 - Remote Compact 5000 I/O Safety Modules in a GuardLogix 5580 Control Application
GuardLogix 5580 Safety Controller
GuardLogix 1756-L8SP Safety Partner Compact 5000 I/O EtherNet/IP Adapter
Compact 5000 I/O Safety Modules
Secure Access to the To secure access to a Logix 5000 controller, Compact 5000 EtherNet/IP
System adapter, or I/O module by authorized users only, consider the
following options:
• Password protect the source and execution of the control program.
Standard Modules
• 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.
Ownership Every I/O module in a Logix 5000 control system must be owned by a
controller, also known as the owner-controller. When a Compact 5000 I/O
digital module is used in a Logix 5000 control system, the owner-controller
Standard Modules performs the following:
• Stores configuration data for every module that it owns.
• Can reside in a location that differs from the Compact 5000 I/O
digital modules.
• Sends the I/O module configuration data to define module behavior and
begin operation in the control system.
Safety Modules
Multiple Logix 5000 controllers can connect to Compact 5000 I/O standard
input modules as owner-controllers.
IMPORTANT If the controller that owns the module configuration changes the
configuration, the other controllers are not notified of the changes.
For more information, see Configuration Changes in a Standard Input
Module with Multiple Owners on page 27.
• 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 on page 49.
Configuration Changes in a You must be careful when changing the configuration data of an input module
Standard Input Module with in a multiple-owner scenario. If the configuration data is changed in owner A
and sent to the module, the changed configuration data is accepted as the new
Multiple 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 6 - Module Configuration Changes with Multiple Owners
Controller A sends new configuration to the module. Controller B is unaware of any configuration changes.
Construct a System Before you use your Compact 5000 I/O digital modules, you must complete
tasks that are based on whether the modules are local or remote I/O modules.
Standard Modules
Local I/O Modules
Complete the following steps.
1. Install a CompactLogix 5380, CompactLogix 5480, or
Compact GuardLogix 5380 controller.
IMPORTANT You must use a Compact GuardLogix 5380 controller if the local Compact
5000 I/O digital modules includes safety modules.
For more information on controller compatibility,
see Controller and Software Compatibility on page 16.
2. Install the modules to the right of the controller.
3. Install the end cap on the last module in the local system.
When the I/O becomes available, you complete the following tasks.
1. Remove the 5069-ARM module from the system.
2. Install the I/O module in the slot that previously contained the
5069-ARM module.
3. Replace the 5069-ARM module entry in the I/O Configuration section of
the Logix Designer application project with the new I/O module.
For more information on how to use a 5069-ARM module in a Logix
Designer application project, see
Reserve an I/O Module Slot on page 152.
Power the Modules Compact 5000 I/O digital modules receive the following power types from first
component in the system, that is, the controller or adapter:
Standard Modules • System-side Power - Powers the system and lets modules transfer data
and execute logic.
System-side power is provided through the Module (MOD) Power
connector and is passed to each module as it is added to the system.
System-side power is also known as MOD power.
• Field-side Power - Powers field-side devices that are connected to some
Compact 5000 I/O digital modules.
Field-side power is provided through the sensor actuator (SA) Power
connector and is passed to each module as it is added to the system.
Field-side power is also known as SA power.
Power begins at the leftmost device in the system and passes across the I/O
module internal circuitry via power buses. The MOD power bus and SA power
buses are isolated from each other. The leftmost device is either a controller or
an EtherNet/IP adapter.
For more information on how to power local Compact 5000 I/O digital
modules, see the following:
- CompactLogix 5380 and Compact GuardLogix 5380 Controllers User
Manual, publication 5069-UM001
- CompactLogix 5480 Controller User Manual, publication 5069-UM002
For more information on how to power remote Compact 5000 I/O digital
modules, see the Compact 5000 EtherNet/IP Adapters User Manual,
publication 5069-UM007.
You can use a 5069-FPD field potential distributor to establish a new SA power
bus in a system. The field potential distributor blocks the current that passes
across the SA power bus to the left of the field potential distributor. It then
establishes a new SA power bus for modules to the right.
The new SA power bus extends to the last module in the system or until
another field potential distributor establishes another SA power bus.
The SA power bus that a field potential distributor establishes functions in the
same way as the SA power bus that a controller or adapter establishes.
SA Power Bus For DC-type Modules SA Power Bus For AC-type Modules
IMPORTANT You must install DC-type modules and AC-type modules on separate SA
power buses.
You use 5069-FPD field potential distributors to establish SA power
buses that are separate from the SA power bus that the controller or
adapter establishes.
To install modules on separate SA power buses, complete the following
steps.
1.Install the controller or adapter.
The controller or adapter establishes the first SA power bus.
2. Install one type of modules to the right of the controller or adapter, for
example, DC-type modules.
3. Install a 5069-FPD field potential distributor.
The field potential distributor establishes a new SA power bus that
is isolated from the first one.
4. Install the other type of modules to the right of the field potential
distributor, for example, AC-type modules.
Additional requirements apply when you use a 5069-FPD field
potential distributor in a local or remote system with Compact 5000
I/O safety modules.
For more information on the additional requirements, see Power
Requirements When You Use Compact 5000 I/O Safety Modules on
page 33
Power Requirements When You Use Compact 5000 I/O Safety Modules
This section describes the requirements that apply when you connect MOD
power and SA power to a system that includes both types of Compact 5000
I/O digital modules.
Power a Compact GuardLogix 5380 System That Includes Compact 5000 I/O
Safety Modules
Table 5 describes requirements that apply when you connect MOD power and
SA power to a Compact GuardLogix 5380 system with a mix of standard and
safety modules.
Table 5 - Connect Power to a Compact GuardLogix 5380 System with Compact 5000 I/O Standard and Safety Modules
Power Requirements Example System
Type
SELV/PELV-listed +
24V DC
Power Supply -
Table 5 - Connect Power to a Compact GuardLogix 5380 System with Compact 5000 I/O Standard and Safety Modules
Power Requirements Example System
Type
Power a Remote Compact 5000 I/O System That Includes Compact 5000 I/O
Safety Modules
Table 6 describes requirements that apply when you connect MOD power and
SA power to a Compact 5000 I/O system with standard and safety modules.
Table 6 - Connect Power to a Compact 5000 I/O System with Standard and Safety Modules
Power Requirements Example System
Type
SELV/PELV-listed +
24V DC -
Power Supply
Configure the Modules You must create a Logix Designer application project for the controller that
owns the Compact 5000 I/O digital modules. The project includes module
configuration data for the module.
Standard Modules
The Logix Designer application transfers the project to the owner-controller
during the program download. Data is then transferred to the I/O modules
either across the backplane or over an EtherNet/IP network.
IMPORTANT This section shows some Logix Designer application screens; it is not a
complete description of how to configure a module.
• For more information on how to use the Logix Designer application to
configure Compact 5000 I/O standard modules, see Chapter 6, Configure
a Standard Module on page 143.
• For more information on how to use the Logix Designer application to
configure Compact 5000 I/O safety modules, see Chapter 7, Configure
and Replace Safety Modules on page 183.
The owner-controller monitors its connection with a module. Any break in the
connection, for example, the loss of power to the system, causes a fault. The
Logix Designer application monitors the fault status tags to indicate when a
fault occurs on a module.
Connection Types That Are Available with Compact 5000 I/O Standard Modules
The following are example Module Definition dialog boxes, and available
Connection choices, for Compact 5000 I/O standard modules.
Table 7 describes the connection types that you can use with
Compact 5000 I/O standard modules.
The Module Definition includes a Data parameter that matches the module
type. Standard input modules use Input Data, and standard output modules
use Output Data.
The module type and Connection choice determine the available Input Data or
Output Data choices. For example, you can configure a 5069-IB16F 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, as shown.
The 5069-IB16 input module does not support the Connection choice Data with
Events, however. As a result, the Input Data choice Timestamped Data is not
available.
For more information on how to use the Module Definition parameters with
Compact 5000 I/O digital modules, see the following:
• Module Definition on page 156
• Logix Designer application online help
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.
Because part of module configuration includes a slot number in the local
Compact GuardLogix 5380 controller system or remote Compact 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 prevent 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 Compact 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 That Are Available with Compact 5000 I/O Safety Modules
Table 8 describes the connection types that you can use with Compact 5000
I/O safety modules.
Configured by Description
Choice Compact 5000 I/O Safety Input Module Compact 5000 I/O Safety Output Module
This choice directs the controller to configure the module.
The module returns the following to the owner-controller:
The module returns the following to the owner-controller: • General fault data
This Controller • General fault data • Safety input data
• Safety input data • Safety output data
• Muting lamp points IMPORTANT: When you choose This Controller, you must define the output
mode that the module uses, that is, sourcing or bipolar output mode.
This choice directs the controller to establish only a safety input connection. When the External Means is chosen, another controller owns the module.
A controller that uses this option does not write configuration for the module or control the Test Outputs. It merely listens to the data exchanged with the
External Means owner-controller. That is, it receives Safety input data.
For more information on the External Means option, see External Means on page 53. In this case, all other connections to the module, for example, the
connection to the owner-controller must also use the Multicast option.
On the Module Definition dialog box for Compact 5000 I/O safety modules,
you must configure data type parameters.
Table 9 describes the available data type choices based on module type.
Table 9 - Compact 5000 I/O Safety Modules - Data Types
Catalog Number Supported Data Types Data Type Choices
Safety Data
Input Data Safety Packed Data
(1)
5069-IB8S, 5069-IB8SK There is not an Output Data field on the Module Definition dialog box in the Logix Designer application for the 5069-
Output Data IB8S module. However, if you enable Muting on points 02 and/or 03, output data is available in module output tags.
For more information on module tags, see Appendix B, Module Tag Definitions on page 219.
Safety Data
Input Data Safety Packed Data
Safety Data
Safety Packed Data
5069-OBV8S, 5069-OBV8SK(1) None
IMPORTANT: This field is automatically set based on how you configure the Configured By and Input Data parameters
Output Data on the Module Definition dialog box.
For example, if you configure a 5069-OBV8S module to use the Configured By parameter of This Controller and the
Input Data parameter of Safety Data, the Output Data field is automatically set to Safety Data and no other choices
are available.
(1) The conformal coated module catalog numbers are not available in the Logix Designer application. If your application uses a conformal coated module, you choose the non-conformal coated catalog
number when you add the module to the project.
Muting Lamp Points Available with Compact 5000 I/O Safety Input Module
The Module Definition for the 5069-IB8S and 5069-IB8SK safety input
modules includes the Muting Lamp Points parameter. This parameter defines
what output points on the module, if any, are connected to muting lamps.
Output Mode Available with Compact 5000 I/O Safety Output Module
For more information on the Module Definition parameters that are available
with Compact 5000 I/O digital modules, see the Logix Designer application.
You set the RPI value during initial module configuration and can adjust
it as necessary after module operation has begun. The following are valid
RPI values:
• Compact 5000 I/O standard modules - 0.2…750 ms
• Compact 5000 I/O safety modules - 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 Compact 5000 I/O Safety Modules
With Compact 5000 I/O safety modules, the Connection Reaction Time Limit
configuration affects the module RPI.
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%.
For more information on how to specify RPI rates, see the following:
• Compact 5000 I/O standard modules - page 157
• Compact 5000 I/O safety modules - page 190
• Logix 5000 Controllers Design Considerations Reference Manual,
publication 1756-RM094
Input Module Operation Logix 5000 controllers do not poll the Compact 5000 I/O standard or safety
input modules for input data.
Standard Modules
The data exchange process between the input modules and the controller
differs based on whether the module is a local I/O module or remote
I/O module.
Safety Modules
Some Compact 5000 I/O standard input modules can trigger an event.
For example, the modules can trigger the Event task. The event task lets
you execute a section of logic immediately when an event, or receipt of new
data, occurs.
For more information on how to use a Compact 5000 I/O standard input
module to trigger an event, see Events on page 86.
IMPORTANT This can only be the case if a ControlLogix 5580 or GuardLogix 5580
controller owns the I/O module.
CompactLogix 5380, CompactLogix 5480, and Compact GuardLogix 5380
controllers do not support the use of an EtherNet/IP communication
module in the local system.
Output Module Operation Logix 5000 controllers send data to Compact 5000 I/O digital output modules
at the RPI or after an Immediate Output (IOT) instruction is executed.
Standard Modules
The RPI defines when the controller sends data to an output module and when
the module echoes data. The IOT instruction sends new data to an output
module whenever new data is produced.
IMPORTANT CompactLogix 5380 and CompactLogix 5480 controllers can also send
data to Compact 5000 I/O standard output modules, that is, standard
modules, when an IOT instruction is executed.
Compact GuardLogix 5380 controllers cannot send data when an IOT
instruction is executed. You cannot use IOT instructions in safety
programs.
References to IOT instructions in this section apply only to
CompactLogix 5380 controllers.
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 channel data quality.
IMPORTANT The RPI for a Compact 5000 I/O safety output module is the Safety Task
period. Safety output data is sent at the completion of the Safety
Safety Modules Task scan.
The data exchange process between Compact 5000 I/O digital output modules
and a controller differs based on whether the module is a local I/O module or
remote I/O module.
The controller broadcasts data to its local backplane at one of the following:
• RPI
• An IOT instruction is executed.
IMPORTANT An IOT instruction sends data to the output module immediately, and
resets the RPI timer.
Compact GuardLogix 5380 controllers cannot send data when an IOT
instruction is executed. You cannot use IOT instructions in safety
programs.
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 channels can
change values multiple times during a program scan. The owner-controller
does not depend on the program scan to complete to send data.
The following events occur when the controller sends data to a local
Compact 5000 I/O output module.
1. The controller sends data to system backplane at the RPI or when an IOT
instruction is executed.
2. The local output module receives the data from the system backplane and
behaves as dictated by its configuration.
When a local Compact 5000 I/O digital 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 local Compact 5000 I/O digital output
module sends data to the controller at the RPI.
1. The module sends the data to the system backplane.
2. The controller receives the data immediately.
The controller broadcasts data to its local backplane at one of the following:
• RPI
• An IOT instruction is executed.
IMPORTANT An IOT instruction sends data to all 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 channels can
change values multiple times during a program scan. The owner-controller
does not depend on the program scan to complete to send data.
The following events occur when the controller sends data to a Compact 5000
I/O digital output module.
1. 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 Compact 5000 I/O EtherNet/IP adapter in the remote Compact 5000
I/O system receives the data from the network and transmits it to the
system backplane.
4. The remote output module receives the data from the backplane and
behaves as dictated by its configuration.
When a Compact 5000 I/O digital 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 remote Compact 5000 I/O digital output
module sends data to the controller at the RPI.
1. The module sends the data to the system backplane.
2. The Compact 5000 I/O EtherNet/IP adapter in the 5069 Compact
I/O™ system sends the data over the EtherNet/IP network.
3. One of the following:
• 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 The owner-controller, as described in Ownership on page 26, exchanges data
with I/O modules. The owner-controller owns the module configuration in its
Standard Modules Logix Designer application project.
Other controllers that do not own the module or exchange data with it can
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 choose a Listen Only connection
type. The Connection pull-down menu is available on the Module Definition
dialog box.
For more information on how to access the Module Definition dialog box for
Compact 5000 I/O standard modules, see General Category on page 155.
For more information on the Connection category for Compact 5000 I/O
standard modules, see page 157.
In some instances, the Logix Designer application lets you configure a module with
choices that result in connection request errors. However, the application does not
alert you to the error that occurs as a result of the choices until the project goes
online.
For example, if an owner-controller project uses Multicast and the listening controller
project uses Unicast, the result is a module fault and error code 16#106. However,
the Logix Designer application project in the listening controller only alerts you to the
error when the project goes online.
We recommend that you confirm the Connection Over EtherNet/IP choice in the
listening controller’s project is correct before you go online.
Module Tags
Only Input
Created
tags are
created.
External Means Any controller in the system can listen to the data from an I/O module. An
Safety Modules owner-controller, as described in Ownership on page 26, exchanges data with
I/O modules.
Controllers that do not own a module but must listen to data from it use the
following on the Module Definition dialog box:
• Compact 5000 digital safety I/O modules
—Configured By = External Means.
In this case, the ‘listening’ controller can only listen to input data. The listening
controller does not own the module configuration or exchange other data with
the module.
When the module is configured by External Means, you can disable the module
configuration signature. This disables the configuration validation check
when connections are made.
During the I/O configuration process, you can specify an External Means
connection. For more information on Connection options, see Module
Definition on page 189.
Protected Operations To maintain the secure operation of your Compact 5000 I/O digital modules,
operations that can disrupt module operation are restricted based on the
Standard Modules module operating mode.
Firmware Rejected
update is in
process
(1) Only requests for Listen Only connections are accepted.
(2) Configuration change is accepted in the following scenarios:
Safety Modules - 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, before the change is
made, a dialog box alerts you of the ramifications before the change is made.
Considerations Specific to Compact 5000 I/O safety modules have additional items of which you must be
Safety Modules aware. Type approval, certification, and suitability for use in safety
applications vary by catalog number.
Safety Modules
IMPORTANT Functional safety certification and performance of Compact 5000 I/O
safety modules requires that the modules operate in conditions at or
below the ambient operating temperature specification.
The probability of a dangerous 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 Compact 5000 I/O safety modules, see the Compact
5000 I/O Modules and EtherNet/IP Adapter Technical Data, publication
5069-TD001.
However, just because the modules are rated for use in a system with a safety
function of SIL 3, you are not required to use Compact 5000 I/O safety modules
in those applications. You can use the modules in safety applications with an
overall system safety function that is less than SIL 3.
For example, Compact GuardLogix 5380 controllers are suitable for use in
safety applications that are rated up to, and including, SIL CL 2, PLd, Cat. 3 as
defined in IEC 61508, IEC 61511, IEC 62061, and ISO 13849-1.
In this case, the overall system safety function is SIL 2. You can use Compact
5000 I/O safety modules in this application even though the modules are rated
for use in systems with higher overall system safety function.
GuardLogix 5580 controllers, when used with a safety partner are suitable for
use in SIL 3 safety applications. You can use Compact 5000 I/O safety modules
as remote I/O modules in such an application.
For more information on the suitability level of Logix 5000 safety controllers,
see the GuardLogix 5580 and Compact GuardLogix 5380 Controller Systems
Safety Reference Manual, publication 1756-RM012.
We recommend that, if you use dual channel safety instructions, for example,
the Dual Channel Input Stop (DCS) instruction, in the Safety Task, you
configure the channels for single-channel mode.
For more information on which controllers you can use with Compact 5000
I/O safety modules, see Table 2 on page 17.
You must use the Logix Designer application, version 32 or later, to configure
the Compact 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
Verify that the firmware revision of the Compact 5000 I/O safety modules that
you use is correct before commissioning the system.
Only download firmware and access product release notes from the Rockwell
Automation PCDC.
The Compact 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 the following precautions for the proper use Compact 5000 I/O
safety modules.
ATTENTION: As serious injury can occur due to loss of required safety function,
follow the following 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 Compact 5000 I/O safety modules as shown in the Compact 5000
I/O Modules and EtherNet/IP Adapters Technical Data, publication 5069-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 you start system operation.
• Do not disassemble, repair, or modify the module. This can result in loss of
safety functions.
For information on how to secure access to the system, see page 25.
Creating, recording, and verifying that 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.
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 Compact 5000 I/O safety modules only in applications where the off
state is the safe state.
Safety Status
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
Each safety device has a unique configuration signature that defines the
module configuration. The configuration signature includes the following:
• ID number
• Date
• Time
Configuration Ownership
The connection between the owner-controller and the Compact 5000 I/O
safety module is based on the following:
• Compact 5000 I/O safety module node number
• Compact 5000 I/O safety module safety network number
• Controller node or slot number
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 application 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 5069-OBV8S module, the
configuration signature parameter is disabled.
When a Compact 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 198.
You cannot reset the module to its out-of-box configuration if any of the
following conditions exist:
• There are pending edits to the module properties.
• When a safety signature exists in the controller project.
Topic Page
Input Module Compatibility 64
Output Module Compatibility 65
Software Configurable 66
Module Data Quality Reporting 67
Fault and Status Reporting 68
Module Inhibiting 69
Electronic Keying 70
Module Firmware 71
Producer/Consumer Communication 71
Use CIP Sync Time with Fast I/O Modules 72
Timestamping 72
This chapter describes features that are common to Compact 5000™ I/O digital
modules unless otherwise noted.
Some features are supported on all I/O modules and other features are specific
to module types. The differences are indicated in feature descriptions.
Input Module Compatibility Compact 5000 I/O digital input modules interface to sensing devices and
detect whether they are On or Off.
Standard Modules
The input modules convert DC On/Off signals from user devices to
appropriate logic level for use in the controller. Typical input devices include
the following:
• Proximity switches
• Limit switches
• Selector switches
• Float switches
• Push button switches
When you design systems with Compact 5000 I/O digital input modules,
consider the following factors:
• Voltage necessary for your application
• Current leakage
• Whether you need a solid-state device
• Whether your application uses sinking or sourcing wiring
Safety Modules
Output Module Compatibility Compact 5000 I/O digital output modules can be used to drive output devices.
Typical devices compatible with the following output modules include:
Standard Modules • Motor starters
• Solenoids
• Indicators
When you design systems with Compact 5000 I/O digital output modules,
follow the following guidelines:
• Make sure that the 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.
Safety Modules
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
Standard Modules application to retrieve this information from any module in the system:
• 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 provide
excellent reliability.
Safety Modules
Module Data The Compact 5000 I/O digital modules indicate the quality of channel data
Quality Reporting that is returned to the owner-controller. Data quality represents accuracy.
Levels of data quality are reported via module input tags.
Standard Modules The following input tags indicate the level of data quality.
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.
Remember 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 channel 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:
- Field Power Loss condition (output modules)
- No Load condition (standard output modules only)
- Short Circuit condition (output modules)
Safety Modules We recommend that you troubleshoot the module for the typical
causes first.
• I.Ptxx.Uncertain - This tag indicates that the reported channel data can
be inaccurate but the degree of inaccuracy is unknown. We recommend
that you do not use the reported channel data for control.
If the module sets this tag 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:
- 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.
Fault and Status Reporting The Compact 5000 I/O digital modules report fault and status data along with
channel data. Fault and status data is reported in the following ways:
Standard Modules • Logix Designer application
• Module status indicators
• I/O status indicators
IMPORTANT Do not use the module status indicators or I/O status indicators on
Compact 5000 I/O safety modules for safety operations.
Safety Modules
Module Inhibiting Module inhibiting lets you indefinitely suspend a connection, including Listen
Only connections, between an owner-controller and an I/O module without
Standard Modules removing the module from the configuration. This process lets you
temporarily disable a module, such as to perform maintenance.
You can inhibit the connection to a Compact 5000 I/O digital module on the
Connection category of the Module Properties dialog box.
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
Standard Modules installed device. If keying fails, a fault occurs. These attributes are compared.
Attribute Description
Vendor The device manufacturer.
Device Type The general type of the product, for example, digital I/O module.
Product Code The specific type of the product. The Product Code maps to a catalog number.
Major Revision A number that represents the functional capabilities of a device.
Minor Revision A number that represents behavior changes in the device.
Carefully consider the implications of each keying option when selecting one.
More Information
For more detailed information on Electronic Keying, see Electronic Keying in
Logix 5000 Control Systems Application Technique, publication
LOGIX-AT001.
Module Firmware The Compact 5000 I/O digital modules are manufactured with module
firmware installed. If updated module firmware revisions are available in the
Standard Modules future, you can update the firmware.
IMPORTANT Verify that the module firmware revisions for the Compact 5000 I/O safety
modules that you use are correct before commissioning your system.
When an input module produces data, the controllers can consume the data
simultaneously. Simultaneous data consumption minimizes the need for one
controller to send the data to other controllers.
Safety Modules
Use CIP Sync Time with Fast The following Compact 5000 I/O standard modules use CIP Sync™ for time
I/O Modules stamps and scheduling:
• 5069-IB16F
Standard Modules • 5069-IB6F-3W
• 5069-OB16F
CIP Sync is a CIP implementation of the IEEE 1588 PTP (Precision Time
Protocol). CIP Sync provides accurate real-time (Real-World Time) or
Universal Coordinated Time (UTC) synchronization of controllers and devices
that are connected over CIP networks. This technology supports highly
distributed applications that require timestamping, sequence of events
recording, distributed motion control, and increased control coordination.
The 5069-IB16F, 5069-IB6F-3W, and 5069-OB16F modules are CIP Sync slave-
only devices. There must be another module on the network that functions as a
master clock. For more information on how to use CIP Sync technology, see
the Integrated Architecture® System and CIP Sync Configuration Application
Technique, publication IA-AT003.
You can use fast Compact 5000 I/O digital modules to capture time stamps and
schedule outputs while providing the following advances:
• Fast I/O modules have much higher precision than other modules.
• Inputs are timestamped by point, so multiple inputs can be configured
for COS without losing time stamp data.
• CIP Sync is system-wide, so time stamp and schedule values are
consistent across all modules in the system.
For example, if you use time stamps on a 5069-IB16F module to schedule
outputs on a 5069-OB16F module, the controller, input module, and
output module are not required to reside in the same local system. The I/
O modules can reside in a remote I/O system.
• Output modules use all 64 bits of the time stamp to schedule, so there are
no limits on schedule ranges.
Timestamping The control system uses a 64-bit system clock. The modules support CIP Sync
timestamping by using the 1588 protocol that is passed throughout the system.
Standard Modules The 1588 protocol is defined in the IEEE 1588-2002 standard, publication
Standard for a Precision Clock Synchronization Protocol for Networked
Measurement and Control Systems.
Each input channel scan or new output application is stamped with a CIP Sync
time stamp. One time stamp is returned to the controller for the module with
the input data transfer.
Synchronized Sampling lets you configure a test stand, for example, and take
many measurements simultaneously across many modules, if needed, while
still precisely coordinating the sampling. With these modules, the
synchronized sampling coordinates within approximately ± 10 μs.
Notes:
Topic Page
Multiple Input Module Types 76
Data Transfer at RPI or Change of State 76
Software Configurable Input Filters and Delays 77
Module Health Diagnostic 80
Fault and Status Reporting 80
Simple Count Mode 83
Sequence of Events Per Point Timestamping 84
Chatter Detection 85
Events 86
Pulse Latching 90
Field Power Loss Detection 92
Short Circuit Protection 93
Thermal Shutoff 95
This chapter describes features that are supported on Compact 5000™ I/O
digital input modules.
Multiple Input Module Types The Compact 5000 I/O digital module family offers the following input
module types:
Standard Modules
• AC standard input module - 5069-IA16
• DC standard input module - 5069-IB16
• DC standard input conformal coated module - 5069-IB16K
• DC standard fast input modules - 5069-IB16F, 5069-IB6F-3W
• DC safety input modules - 5069-IB8S and 5069-IB8SK
Safety Modules
Data Transfer at RPI or Compact 5000 I/O digital input modules always send data at the RPI, but they
Change of State send data at a change of state only if the COS feature is enabled.
Standard Modules The following table describes the two ways a module sends data to the
owner-controller.
Method Description
A user-defined rate at which the module updates the information that is sent to its
RPI owner-controller.
Configurable feature that, when enabled, instructs the module to update its owner-
controller with new data whenever a specified input point transitions from On to Off and
COS Off to On. The data is sent at the RPI rate when there is no change of state. By default, this
setting is always enabled for input modules.
You set the RPI on the Connection page of the Module Properties dialog box in
the Logix Designer application.
Safety Modules
Software Configurable Input You can increase the time that it takes for an input point to transition from On
Filters and Delays to Off and Off to On for Compact 5000 I/O digital input modules. The increase
in time is a delay of the signal from the module to the controller.
Standard Modules
The increase in the time to transition from one state to another improves noise
immunity within a signal.
The input signal that is connected to the 5069-IA16 input module dictates the
valid input filter values that you can use.
Input Signal Value Filter Time: Off to On - Valid Values Filter Time: On to Off - Valid Values
Safety Modules
• 10 ms
120V AC • 1 ms
• 20 ms
• 1 ms • 5 ms
240V AC • 2 ms • 10 ms
• 5 ms • 20 ms
IMPORTANT Logix Designer application lets you choose filter time values that are invalid for
some input signals.
For example, the only valid Off to On filter value when a 120V AC signal is
connected to the module is 1 ms. However, you can choose 1 ms, 2 ms, or 5 ms.
Make sure that you select a valid input filter value when you configure the
module. If you select an invalid input filter value, the module can read signal
levels incorrectly.
To see where to set the input filter values, see the following:
• 5069-IA16 module - page 159
• 5069-IB16 and 5069-IB16K module - page 161
• 5069-IB16F module - page 163
• 5069-IB6F-3W module - page 169
To see where to set the Input Delay Time on the 5069-IB8S or 5069-IB8SK
modules, see page 193. For more information on how to use the Input Delay
Time feature on a 5069-IB8S or 5069-IB8SK module, see Safety Input Delay
Time on page 130.
The input filter time defines how long an input signal transition must remain
in the new state before the transition is valid and the input changes state.
Input and Event time stamps are only recorded with valid transitions.
A transition is only valid if the input signal remains in the new state for the
entirety of the filter duration. If the input changes state again before the
chosen input filter time elapses, the transition is not valid.
In Figure 10, the first three signal transitions--both On to Off and Off to On--
remain the same state until the filter time elapses and are not valid.
Figure 10 - Input Filter Usage on Compact 5000 I/O Fast Input Modules
ON
Input Signal
OFF
State Change
End
Off to On Filter Filter Duration
Start
ON
Module Input Data
OFF
ON
Input Signal
OFF
State Change
End
On to Off Filter Filter Duration
Start
ON
Module Input Data
OFF
Module Health Diagnostic Every Compact 5000 I/O digital module has a status indicator on the front of
Standard Modules
the module that indicates module health.
Safety Modules
Fault and Status Reporting The input modules multicast fault and status data with channel data to the
Standard Modules owner and listening controllers. The data is returned via module tags that you
can monitor in your Logix Designer application.
With some exceptions, the Compact 5000 I/O digital input modules provide
the fault and data status in a point-centric format. The tag names that
include Ptxx represent point-centric data in the table. The xx represents
the point number.
Not all tags that are listed in Table 13 apply to all Compact 5000 I/O digital
input modules. For example, the 5069-IB16F module uses the Eventx.PtxxData
tag. The 5069-IB16 or 5069-IB16K modules do not use it.
Safety Modules
IMPORTANT For more information on the valid values for each tag, see Appendix B,
Module Tag Definitions on page 219.
Table 13 - Compact 5000 I/O Standard Input Module - Fault and Data Status
Data Type Tag Name(1) Triggering Event That Sets
(2) The owner-controller loses its connection to the module.
ConnectionFaulted
Counterxx.Fault The counter data quality is bad.
Ptxx.Fault The point data quality is bad.
Fault
Eventx.CounterxxFault The corresponding counter had a fault that indicated when the event occurred.
Eventx.Fault The signal connection is lost.
Eventx.Ptxx.Fault The event data quality is bad.
RunMode The module is in Run Mode.
DiagnosticActive Indicates if any diagnostics are active or if the prognostics threshold is reached.
DiagnosticSequenceCount The count increments each time that a diagnostic condition is detected or removed.
Counterxx.Data The point input status is 0 or 1.
Counterxx.Uncertain The counter data can be imperfect.
Status
Eventx.PtxxData The point input status is 0 or 1.
Eventx.Uncertain The event data can be imperfect.
Ptxx.Data The point input status is 0 or 1.
Ptxx.Uncertain The point data can be imperfect.
Uncertain(2) The module is operating outside its designed operating range if data is under manual or override control.
(1) Not all tag names apply to all Compact 5000 I/O standard input modules. For example, only modules that support the Events feature use the Event tags but modules.
(2) This tag provides module-wide data and affects all channels simultaneously.
IMPORTANT For more information on the valid values for each tag, see Appendix B,
Module Tag Definitions on page 219.
Table 14 - Compact 5000 I/O Safety Input Module - Fault and Data Status
Data Type Tag Name Triggering Event That Sets
(1) The owner-controller loses its connection to the module.
ConnectionFaulted
Ptxx.Fault The point data quality is bad or the channel is set to Not Used.
Ptxx.ShortCircuit A short circuit condition exists on the point.
Fault
Testxx.Fault The point data quality is bad or the channel is set to Not Used.
Testxx.ShortCircuit A short circuit condition exists on the test point.
Testxx.FieldPowerOff A field power lost condition exists on the test point.
RunMode The module is in Run Mode.
DiagnosticActive Indicates if any diagnostics are active or if the prognostics threshold is reached.
DiagnosticSequenceCount The count increments each time that a diagnostic condition is detected or removed.
Ptxx.Data The data currently at the point.
Status Ptxx.Uncertain The point data can be imperfect because an Over temperature or Critical Temperature condition exists.
Ptxx.Status The point state transitions from normal to faulted or faulted to normal.
Testxx.Readback A 24V DC power is present at the test output.
Testxx.Uncertain The test point data can be imperfect.
Testxx.Status The test point state transitions from normal to faulted or faulted to normal.
(1) This tag provides module-wide data an affects all channels simultaneously.
Simple Count Mode Simple count mode is used to count input pulses.
Standard Modules
IMPORTANT The following Compact 5000 I/O standard input modules support Simple Count
mode:
• 5069-IB16
• 5069-IB16F
• 5069-IB16K
• 5069-IB6F-3W
When using the simple counter function, the module counts input pulses up to
the following frequencies:
• The simple counter maximum frequency for the 5069-IB16 and
5069-IB16K modules is 500 Hz (inv. period 2 ms).
The maximum number of counters on the 5069-IB16 and 5069-IB16K
modules is 8. You can configure channels 0…7 to be counters.
• The simple counter maximum frequency for the 5069-IB16F and
5069-IB6F-3W modules is: 30 kHz (inv. period 33.3 μs).
- The maximum number of counters on the 5069-IB16F module is 8. You
can configure channels 0…7 to be counters.
- The maximum number of counters on the 5069-IB6F-3W module is 4.
You can configure channels 0…3 to be counters.
The modules compare total count to previously programmed values and then
can activate an associated output. The modules provide for count up
functionality and counter overflow.
Sequence of Events Per Timestamping registers a time reference to a change in input data. CIP Sync is
Point Timestamping used for timestamping.
Standard Modules IMPORTANT The following Compact 5000 I/O standard input modules support Per Point
Timestamping:
• 5069-IB16F
• 5069-IB6F-3W
You can use CIP Sync to establish a sequence of events occurring at an input
module point by timestamping the input data. To determine a sequence of
events, you must perform the following:
• On the Module Definition dialog box in the Logix Designer application
project, set the Input Data parameter to Timestamp Data.
• Enable COS for the input point where a sequence occurs, and disable
COS for all other points on the module.
You can enable COS in the following ways.
Location in Logix Designer Application Action
Check the input transition type where you need to latch
short duration pulses.
Module Properties dialog box > Points category >
For example, if you need to latch short duration pulses
Ptxx subcategory for Off to On transitions, check Off -> On Input
Transition.
One or both of the following:
Module tags • Change the C.Ptxx.CaptureOffOnEn tag to 1.
• Change the C.Ptxx.CaptureOnOffEn tag to 1.
Chatter Detection Chatter Detection is a feature that is directly related to Timestamping. You
Standard Modules use the feature to detect when a device that is connected to an input module
causes chatter.
Chatter occurs when the device causes the inputs to transition falsely many
times in a relatively short period. As a result, the module timestamps invalid
input transitions.
To see where to set the Chatter Detection options, see the following:
• 5069-IB16F module - page 164
• 5069-IB6F-3W module - page 170
Standard Modules IMPORTANT The following Compact 5000 I/O standard input modules support the Events
feature:
• 5069-IB16F
• 5069-IB6F-3W
You must use the Data with Events connection type in the Module Definition
to use the Events feature.
Event Definition
You define an event. When you define an event, remember the following:
• The event definition parameters are shown on Eventsxx category in the
Module Properties dialog box. The parameters are read-only in the dialog
box as shown in this example.
To use this type of trigger, you must enable the Independent Point Trigger
option in the event definition. You set the
EO.Eventxx.IndependentConditionTriggerEn tag to 1.
IMPORTANT Make sure that you link the Event task to the Event Input tag,
not the Input tag.
Keep in mind that when the Event task executes, the input
tag data can have the same data that was sent at the
last RPI.
• An event is recognized only when it maintains the same state for at least
the duration of the input filter time specified.
• Configure the event at a rate that stops task overlap conditions. If you
enable COS for multiple points, a task overlap of the event can occur.
• Configure the event at a rate that is likely to succeed. A 2 ms signal width
is the minimum pulse width that can be used at which the
event succeeds.
• After the event executes, it does not execute again until the event
occurs again.
• For more information on event tasks, see the Logix 5000™
Controllers Tasks, Programs, and Routines Programming Manual,
publication 1756-PM005.
Pulse Latching You can use Pulse Latching to detect or latch short duration pulses. The
module can detect incoming pulses with a duration as short as 10 μs if the
Standard Modules frequency is under 4 kHz (period of 250 μs).
IMPORTANT The following Compact 5000 I/O standard input modules support
Pulse Latching:
• 5069-IB16F
• 5069-IB6F-3W
When subsequent short duration pulses are detected at the same input point,
the Latching configuration dictates what changes, if any, occur in the Logix
Designer application project.
Input Transition Type Where Change in Logix Designer Application Project
Latching Configuration Pulse Is Captured
The I.Ptxx.TimestampOffOnNumber tag increments.
Disabled (default) Off to On The new time stamp is recorded in the I.Ptxx.TimestampOffOn tag, overwriting the
The following conditions disable Timestamp Latching: previous time stamp.
• Enable Timestamp Latching field on the Module Properties
dialog box is clear The I.Ptxx.TimestampOnOffNumber tag increments.
• C.Ptxx.TimestampLatchEn tag = 0. On to Off The new time stamp is recorded in the I.Ptxx.TimestampOnOff tag, overwriting the
previous time stamp.
The I.Ptxx.TimestampOffOnNumber and I.Ptxx.TimestampOffOn tags remain latched
until the last captured pulse is acknowledged.
Enabled Off to On In other words, the tag values remain the same until the last captured pulse is
The following conditions enable Timestamp Latching: acknowledged.
• Enable Timestamp Latching field on the Module Properties
dialog box is checked. The I.Ptxx.TimestampOnOffNumber and I.Ptxx.TimestampOnOff tags remain latched
• C.Ptxx.TimestampLatchEn tag = 1. until the last captured pulse is acknowledged.
On to Off In other words, the tag values remain the same until the last captured pulse is
acknowledged.
To acknowledge the last captured pulse, set the output tag of the last input
pulse as follows:
• Off to On transition - Set the O.Ptxx.TimestampOffOnNumberAck tag =
I.Ptxx.TimestampOffOnNumber tag.
• On to Off transition - Set the O.Ptxx.TimestampOnOffNumberAck tag =
I.Ptxx.TimestampOnOffNumber tag.
Once a pulse latch is acknowledged for an input point, the next pulse at that
point increments the corresponding I.Ptxx.TimestampOffOnNumber and
records the time stamp in I.Ptxx.TimestampOffOn.
You can change tag values in program logic while normal module operation
continues or through the Logix Designer application tag editor. For more
information about module tags, see Appendix B, Module Tag Definitions on
page 219.
Field Power Loss Detection The Field Power Loss Detection feature monitors for the loss of field-side
Safety Modules power on an SA power bus.
IMPORTANT The 5069-IB8S and 5069-IB8SK are the only Compact 5000 I/O input modules
that support Field Power Loss Detection.
When power is lost from an SA power bus, the Compact 5000 I/O safety input
modules detect the loss of field power and fault. Fault data is then sent to the
controller. All points on the module fault when field power is lost.
Table 16 describes what happens when a field power loss condition is detected.
Table 16 - Field Power Loss Detection - Compact 5000 I/O Safety Input Module
Test Output I/O Status SA Status
Tag Value Diagnostic Value
Behavior Indicator State Indicator
• Faults • I.Testxx.FieldPowerOff tag = 1
FieldPowerOff diagnostic = 1 Steady red Off
• Turns off • I.Testxx.Fault tag = 1
To correct the issue, you must reapply field power to the test output.
Table 17 describes what happens when a field power is restored and the error
latch time, if set, has expired.
Table 17 - Field Power Loss Detection - Compact 5000 I/O Safety Input Module
Test Output I/O Status SA Status
Tag Value Diagnostic Value
Behavior Indicator State Indicator
Restarts in its • I.Testxx.FieldPowerOff
commanded tag = 0 FieldPowerOff diagnostic = 0 Off Steady green
state. • I.Testxx.Fault tag = 0
IMPORTANT The module can require up to 1 second to complete the recovery in addition to
the Input Error Latch Time.
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 219.
You can also monitor a point for the presence of a field power loss via the
diagnostics that are available in the Module Properties dialog box in Logix
Designer application.
Short Circuit Protection Short Circuit Protection helps prevent damage to a test output on a 5069-IB8S
Safety Modules or 5069-IB8SK module that can result when more current is present at the
output than it can handle.
IMPORTANT The 5069-IB8S and 5069-IB8SK are the only Compact 5000 I/O input
modules that support Short Circuit Protection.
The diagnostic is supported on all module outputs, that is, the Test Output
points and the Test Output/Muting Output points.
Table 19 describes what happens when the short circuit condition is corrected.
Table 19 - Short Circuit Protection - Compact 5000 I/O Safety Input Module
I/O Status Indicator
Test Output Behavior Tag Value Diagnostic Value State
Turns off if there is no
Restarts in its I.Testxx.ShortCircuit tag = 0 Short Circuit diagnostic = 0 longer a load that is
commanded state. I.Testxx.Fault tag = 0 connected to the output.
For more information on the maximum current that you can apply to an
output, see the Compact 5000 I/O Modules and EtherNet/IP Adapters
Technical Data, publication 5069-TD001.
Table 20 describes conditions within which the muting lamp fault and short
circuit diagnostics are triggered.
Table 20 - Short Circuit Protection - Compact 5000 I/O Safety Input Module
Conditions Test Output Behavior Tag(1) and Diagnositic(1) Value I/O Status Indicator State
• Muting Lamp Points in Module Definition - Point 02, Point 03, or Point • I.Testxx.ShortCircuit tag = 1
02 and 03
• Faults • I.Testxx.Fault tag = 1
• Test Output Point Mode - Muting Lamp Flashing red
• Turns off • Muting Lamp Fault diagnostic = 1
• Test Output Data tag = 1
• Short Circuit diagnostic = 1
• Test output point is shorted to 24V DC
• Muting Lamp Points in Module Definition - Point 02, Point 03, or Point
02 and 03 • I.Testxx.ShortCircuit tag = 1
• Test Output Point Mode - Muting Lamp • Faults(2) • I.Testxx.Fault tag = 1
Flashing red
• Test Output Data tag = 1 • Turns off • Muting Lamp Fault diagnostic = 1
• Test output point is shorted to another test output point • Short Circuit diagnostic = 1
• Muting Lamp Points in Module Definition - Point 02, Point 03, or Point • I.Testxx.ShortCircuit tag = 1
02 and 03
• Faults • I.Testxx.Fault tag = 1
• Test Output Point Mode - Muting Lamp Flashing red
• Turns off • Short Circuit diagnostic = 1
• Test Output Data tag = 1
• Short Circuit to Ground diagnostic = 1
• Test output point is shorted to ground
(1) The diagnostics on the fault test output point are triggered in succession. That is, the Muting Lamp Fault diagnostic changes to 1 and then the Short Circuit diagnostic is triggered.
(2) This behavior occurs only on the test output point that is faulted.
When the conditions that trigger the diagnostics as described in Table 20 are
corrected, the results are the same as described in Table 19 on page 93.
Thermal Shutoff Thermal Shutoff helps prevent damage to a test output on the 5069-IB8S
Safety Modules or 5069-IB8SK module that can result when an output gets hotter than it
can handle.
IMPORTANT The 5069-IB8S and 5069-IB8SK are the only Compact 5000 I/O input modules
that support Thermal Shutoff.
For more information on how to use the modules, see Appendix B, Module Tag
Definitions on page 219.
Notes:
Topic Page
Multiple Output Module Types 98
Module Health Diagnostics 98
Data Echo 99
Field Power Loss Detection 100
No Load Detection 102
Short Circuit Protection 106
Thermal Shutoff 113
Fault and Status Reporting 115
Output State Change Time 116
Configurable Channel-level Output State in Program Mode or Fault Mode 117
Connection Fault Handling 117
Forcing 119
Time-scheduled Output Control 122
Isolated and Non-isolated Varieties of Output Modules 124
This chapter describes features that are supported on Compact 5000™ I/O
digital output modules.
Multiple Output The Compact 5000 I/O digital module family offers the following output
Module Types module types:
• AC standard output module - 5069-OA16
Standard Modules • DC standard output modules - 5069-OB8, 5069-OB16
• DC standard output conformal coated module - 5069-OB16K
• DC standard fast output module - 5069--OB16F
• Standard relay output modules - 5069-OW4I, 5069-OW16, 5069-OX4I
• Safety output modules - 5069-OBV8S and 5069-OBV8SK
Safety Modules
Module Health Diagnostics Each output module has a status indicator on the front of the module that
Standard Modules indicates module health. For more information on module health diagnostics,
see Appendix A, Troubleshoot Your Module on page 201.
Safety Modules
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.
Standard Modules
A Compact 5000 I/O digital output module returns a value that was 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.
Safety Modules
Field Power Loss Detection The Field Power Loss Detection feature monitors for the loss of field power,
either from the SA power bus or, for some modules, from the LA
Standard Modules power terminals.
IMPORTANT The following output module support Field Power Loss detection and receive
field power from the SA power bus:
• 5069-OA16
• 5069-OW16
The following output modules that support Field Power Loss detection and
receive field power from LA power terminals:
• 5069-OB8
• 5069-OB16/B
• 5069-OB16F/B
• 5069-OB16K/B
• 5069-OBV8S
• 5069-OBV8SK
These modules do not draw current from the SA power bus.
When field power is lost, Compact 5000 I/O digital output modules detect the
loss of field power and fault. Fault data is then sent to the controller.
To correct the issue, you must reapply field power to the output module.
Table 25 describes what happens when a field power loss condition is resolved,
the error latch time, if set, has expired, and the module is recovered.
Table 25 - Field Power Loss Detection Condition is Resolved - Compact 5000 I/O Digital Output Modules
SA Status
Output I/O Status
Cat. Nos. Tag Value Diagnostic Value Indicator
Behavior Indicator State State
5069-OA16,
5069-OB8,
5069-OB16/B, I.Ptxx.Fault tag = 0 —
5069-OB16F/B, Restarts in its
5069-OB16K/B, commanded FieldPowerOff Off
5069-OW16 diagnostic = 0
state.(1)
• I.Ptxx.FieldPowerOff
5069-OBV8S, tag = 0 Steady green
5069-OBV8SK
• I.Ptxx.Fault tag = 0
(1) If the commanded state is On, the output turns on 100 ms after the Field Power Loss condition is resolved.
IMPORTANT The module can require up to 1 second to complete the recovery in addition
to the Output Error Latch Time.
Field Power Loss Detection has a corresponding tag that can be examined in
the user program if a fault occurs. For information on module s, see Appendix
B, Module Tag Definitions on page 219.
You can also monitor a point for the presence of a field power loss via the
diagnostics that are available in the Module Properties dialog box in Logix
Designer application.
No Load Detection No Load Detection detects when a wire is disconnected from an output or a
load is missing from an output.
Standard Modules
IMPORTANT The following Compact 5000 I/O digital output modules support No Load
Detection:
• 5069-OB8
• 5069-OB16
• 5069-OB16F
• 5069-OB16K
• 5069-OBV8S
• 5069-OBV8SK
IMPORTANT An output must remain in the off state a minimum of 250 ms for No Load
condition to be detected.
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 219.
You can also monitor a point for the presence of a No Load condition via the
diagnostics that are available in the Module Properties dialog box in
Logix Designer application.
A No Load condition can exist when the output is on. However, because safety
output modules cannot detect a No Load condition when the output is on, the
module appears to be working normally on the status indicators and in the
Logix Designer application project.
IMPORTANT An output must remain in the off state a minimum of 250 ms for No Load
condition to be detected.
IMPORTANT When the safety output is in the On state, and there was a load detected in
the Off state, the I/O status indicator is steady yellow.
If the load is then lost from the safety output, for example, because a wire gets
disconnected when the safety output is still in the On state, the No Load
condition is not detected.
The I/O status indicator for the safety output remains steady yellow.
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 219.
You can also monitor a point for the presence of a No Load condition via the
diagnostics that are available in the Module Properties dialog box in
Logix Designer application.
Short Circuit Protection Short Circuit Protection helps prevent damage to the output that can result
Standard Modules when more current is present at the output than it can handle.
IMPORTANT The following Compact 5000 I/O digital output modules support Short Circuit
Detection:
• 5069-OB8
• 5069-OB16
• 5069-OB16F
• 5069-OB16K
• 5069-OBV8S
• 5069-OBV8SK
To correct the issue, you must remove the short circuit condition.
Table 32 describes what happens when the short circuit condition is corrected
on a Compact 5000 I/O standard output module.
Table 32 - Short Circuit Protection - Compact 5000 I/O Standard Output Modules
I/O Status Indicator
Output Behavior Tag Value Diagnostic Value State
Restarts in its I.Ptxx.ShortCircuit tag = 0 Short Circuit diagnostic = 0 Steady yellow
commanded state
For more information on the maximum current that you can apply to an
output, see the Compact 5000 I/O Modules and EtherNet/IP Adapters
Technical Data, publication 5069-TD001.
Table 34 describes what happens when the short circuit condition is removed
from a Compact 5000 I/O safety output module and the data is set to safe state,
that is, the off state.
Table 34 - Short Circuit Protection - Compact 5000 I/O Safety Output Modules
I/O Status Indicator
Output Behavior Tag Value Diagnostic Value State
One of the following:
• If the output point was shorted
to 24V DC when the short
circuit condition was detected,
One of the following: the Short Circuit diagnostic =
• If the output point is shorted to 0.
Restarts in its 24V DC, the I.Ptxx.ShortCircuit Turns off if there is no
IMPORTANT: You must cycle longer a load that is
commanded state tag = 0. power to the module to reset connected to the output.
• If the output point is shorted to the diagnostic.
ground, no tags are changed. • If the output point is shorted to
ground when the short circuit
condition was detected, the
Short Circuit to Ground
diagnostic = 0.
For more information on the maximum current that you can apply to an
output, see the Compact 5000 I/O Modules and EtherNet/IP Adapters
Technical Data, publication 5069-TD001.
Other Conditions That Can Trigger the Short Circuit Diagnostic on the
5069-OBV8S or 5069-OBV8SK Module
Table 35 describes conditions that can trigger the Short Circuit diagnostic.
Table 35 - Conditions That Trigger Short Circuit Diagnostic
Output I/O Status Indicator
Conditions Possible Tag and Diagnostic Combinations
Behavior State
Combination 1
• I.Ptxx.ShortCircuit tag = 1
• Short Circuit diagnostic = 1
• I.Ptxx.Fault tag = 1
• Output Mode - Sourcing Combination 2
• Point Operation Type - Single • I.Ptxx.Fault tag = 1
• Faults
• Point Mode - Safety Pulse Test • Internal Fault diagnostic = 1
• Turns off
• O.Ptxx.Data tag = 1 Combination 3
• Output point is shorted to 24V DC. • I.Ptxx.Fault tag = 1
• Internal Fault diagnostic = 1
• Overload Fault diagnostic = 1
IMPORTANT: The tag and diagnostic combinations that are described occur on the
faulted output point and all of its associated group points.
Combination 1
The following conditions exist on a pair of module • I.Ptxx.ShortCircuit tag = 1 The I/O status
outputs: indicator for the
• I.Ptxx.Fault tag = 1 faulted output point
• Output Mode - Sourcing • Short Circuit diagnostic = 1 turns off.
• Point Operation Type - Dual • Faults • Internal Fault diagnostic = 1
• Point Mode - Safety Pulse Test • Turns off Combination 2
• O.Ptxx.Data tag = 1 (Either output point in the pair) • I.Ptxx.Fault tag = 1
• Output point is shorted to 24V DC (Either output • Internal Fault diagnostic = 1
point in the pair). IMPORTANT: The tag and diagnostic combinations that are described occur on the
faulted output point and all of its associated group points.
Combination 1
The following conditions exist on a pair of module • I.Ptxx.ShortCircuit tag = 1 (Both output points in the pair)
outputs: • Short Circuit diagnostic = 1 (Both output points in the pair)
• Output Mode - Sourcing • Faults • I.Ptxx.Fault tag = 1
• Point Operation Type - Dual • Turns off Combination 2
• O.Ptxx.Data tag = 1 (Both output points in the pair) • I.Ptxx.Fault tag = 1 (Faulted output point and all of its associated group points)
• Output points are shorted to each other. • Internal Fault diagnostic = 1 (Faulted output point and all of its associated group
points
When the conditions that trigger the diagnostics as described in Table 35 are
corrected, the results are the same as described in Table 34 on page 107.
IMPORTANT Internal Short Circuit Detection is only configurable when Sourcing is selected
under Module Output Mode, and Safety Pulse Test is not selected under Point
Mode.
Internal Short Circuit Detection is enabled or disabled per selected Points group
with:
• Even-numbered points (Point 0, 2, 4, and 6)
• Odd-numbered points (Point 1, 3, 5, and 7)
Table 36 describes how you can use the Short Circuit Detection enable or
disable feature.
Table 36 - Internal Short Circuit Detection Conditions–Compact 5000 I/O Safety Output Modules
Default
Operating Conditions Change Setting
Setting
• Module revision 1.011
• Default configuration profile in
Logix Designer application Not available
• Module revision 2.011 You cannot disable the feature.
• Add-On profile, version 2.01, in
Logix Designer application
• Make sure the Module Output Mode is Sourcing.
(See Figure 12)
• To disable the detection on Points 0, 2, 4, and 6:
Enabled – Verify the Point Modes for Points 0, 2, 4, and 6 are either
Safety or Not Used (1)
• Module revision 3.011 or later – Check the Disable Internal Short Circuit Detection on Even-
• Add-On profile, version 3.01 or later, in Numbered Points checkbox. (See Figure 13)
Logix Designer application
• To disable the detection on Points 1, 3, 5, and 7:
– Verify the Point Modes for Points 1, 3, 5, and 7 are either
Safety or Not Used (1)
– Check the Disable Internal Short Circuit Detection on
Odd-Numbered Points checkbox. (See Figure 14)
(1) If 1 or more Point Modes in the group are set as Safety Pulse Test, the warning box is displayed (see Figure 15 on page 111). If the
user clicks Yes, the corresponding Point Modes will be updated as Safety automatically; Otherwise, Internal Short Circuit Detection
for the group will continue as enable. The checkbox is cleared.
Figure 15 - Pop-up warning when Safety Pulse Test is selected under Point Mode
Thermal Shutoff Thermal Shutoff helps prevent damage to the output that can result when an
output gets hotter than it can handle.
Standard Modules
IMPORTANT The following Compact 5000 I/O digital output modules support the Thermal
Shutoff feature:
• 5069-OB8
• 5069-OB16
• 5069-OB16F
• 5069-OB16K
• 5069-OBV8S
• 5069-OBV8SK
For more information on how to use the modules, see Appendix B, Module Tag
Definitions on page 219.
For more information on how to use the modules, see Appendix B, Module Tag
Definitions on page 219.
Fault and Status Reporting The output modules multicast fault and status data with channel data to the
Standard Modules owner and listening controllers. The data is returned via module s that you can
monitor in your Logix Designer application.
Not all tags that are listed in Table 42 apply to all Compact 5000 I/O digital
output modules. For example, the 5069-OB8 module uses the Ptxx.NoLoad tag.
The 5069-OW4I module does not.
IMPORTANT For the 5069-OB16, 5069-OB16F, and 5069-OB16K 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.
IMPORTANT For more information on the valid values for each tag in Table 42, see Appendix
B, Module Tag Definitions on page 219.
Safety Modules
Table 42 - Compact 5000 I/O Standard Output Modules - Fault and Data Status
Data Type Tag Name Triggering Event That Sets
(1) The owner-controller loses its connection to the module.
ConnectionFaulted
Ptxx.Fault The point data quality is bad.
Fault Ptxx.NoLoad A no load condition exists on the point.
Ptxx.ShortCircuit A short circuit condition exists on the point.
Ptxx.FieldPowerOff A field power lost condition exists on the point.
RunMode The module is in Run Mode.
DiagnosticActive Indicates if any diagnostics are active or if the prognostics threshold is reached.
DiagnosticSequenceCount The count increments each time that a diagnostic condition is detected or removed.
Status
Ptxx.Data The point input status is 0 or 1.
Ptxx.Uncertain The point data can be imperfect.
Uncertain(1) The module is operating outside its designed operating range if data is under manual or override control.
(1) This tag provides module-wide data an affects all channels simultaneously.
IMPORTANT For more information on the valid values for each tag in Table 43, see
Appendix B, Module Tag Definitions on page 219.
Table 43 - Compact 5000 I/O Safety Output Modules - Fault and Data Status
Data Type Tag Name Triggering Event That Sets
(1) The owner-controller loses its connection to the module.
ConnectionFaulted
Ptxx.Fault The point data quality is bad or the channel is set to Not Used.
Fault
Ptxx.ShortCircuit A short circuit condition exists on the point.
Ptxx.FieldPowerOff A field power lost condition exists on the point.
RunMode The module is in Run Mode.
DiagnosticActive Indicates if any diagnostics are active or if the prognostics threshold is reached.
DiagnosticSequenceCount The count increments each time that a diagnostic condition is detected or removed.
Status
Ptxx.Readback A 24V DC power source is connected to the output circuit.
Ptxx.Data The data currently at the point.
Ptxx.Uncertain The point data can be imperfect.
(1) This tag provides module-wide data an affects all channels simultaneously.
Output State Change Time Table 44 lists the time that it takes for Compact 5000 I/O standard output
module outputs to change state after a command.
Standard Modules
Table 44 - Time for a Module Output to Change State
Module Time(1)
1/2 cycle, typical
For example, if the input uses a 50 Hz AC wave, 1 cycle = 1/50 or 20 ms.
5069-OA16 Because the typical time for the module output to change state is 1/2 cycle, in this
example the time is 10 ms.
5069-OB8 100 µs
5069-OB16, 5069-OB16K 100 µs
5069-OB16F 10 µs
5069-OW4I 10 ms
5069-OW16 10 ms
5069-OX4I 15 ms
(1) The times that are listed in Table 44 are from the time the module receives the message.
Configurable Channel-level You can configure individual output channels to specific states when the
Output State in Program module is in Program mode or Fault mode. The following output states are
available:
Mode or Fault Mode • Off
Standard Modules
• On
• Hold last state
To see how to configure the output states in Program mode or Fault mode, see
the following:
• 5069-OA16 module - page 174
• 5069-OB8 module - page 175
• 5069-OB16 and 5069-OB16K modules - page 176
• 5069-OB16F module - page 177
• 5069-OW4I module - page 178
• 5069-OW16 module - page 179
• 5069-OX4I module - page 180
Connection Fault Handling You can configure Compact 5000 I/O standard module behavior when a
connection fault occurs, that is, the connection between the owner-controller
Standard Modules and the output module breaks.
If you configure the output to 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.
If the Fault State Duration is set to a value other than Forever, the output state
changes to a user-configurable Final Fault State after the specified time period
elapses. For more information, see Final Fault State Value on page 118.
You can configure the output to remain at the specific value for the following
times:
• Forever
• 1 second
• 2 seconds
• 5 seconds
• 10 seconds
After the Fault State Duration time expires, the output transitions to user-
defined Final Fault State Value.
You set the value in the C.Ptxx.FaultFinalState tag. For more information on
module s, see Appendix B, Module Tag Definitions on page 219.
To see where to configure the Connection Fault Handling parameters, see the
following:
• 5069-OA16 module - page 174
• 5069-OB8 module - page 175
• 5069-OB16 and 5069-OB16K modules - page 176
• 5069-OB16F module - page 177
• 5069-OW4I module - page 178
• 5069-OW16 module - page 179
• 5069-OX4I module - page 180
Forcing Use a force to override data that your logic either uses or produces.
• Test and debug your logic.
Standard Modules
• Temporarily maintain normal system operations when an input device
has failed.
Make sure that you understand this before you use forces.
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.
The Online toolbar shows the status of forces. It shows the status of I/O forces
and SFC forces separately.
Forces tab
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.
Time-scheduled You can schedule times for module outputs to turn On or Off. The time
Output Control schedules use units in nanoseconds.
Time-scheduled output control is used with the Motion Arm Output Cam
(MAOC) instruction. The MAOC instruction enables position-based output
control in the following 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 output modules at the coarse update rate.
However, some high-speed applications require a higher degree of accuracy.
The 5069-OB16F scheduled output module improves 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 45 - 5069-OB16F Output Module Schedule Parameters
Feature 5069-OB16F
Number of schedules 32
Output points available for scheduling 16 (points 0…15)
Remote operation —
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.
IMPORTANT Before you complete the steps, make sure that Time Synchronization
is enabled in the controller and, if applicable, the EtherNet/IP
adapter, to use scheduled outputs.
3. On the Module Definition dialog box, choose Scheduled Data for the
Output Data and click OK.
Isolated and Non-isolated The 5069-OW4I and 5069-OX4I standard output modules provide point-to-
Varieties of Output Modules point wiring isolation.
IMPORTANT Although some Compact 5000 I/O digital output modules do not provide
Standard Modules wiring isolation, all Compact 5000 I/O digital output modules maintain
internal electrical isolation between the system-side and field-side power
buses.
Topic Page
Safety Input Module Features 125
Safety Output Module Features 138
Fault and Status Reporting 142
This chapter describes features that are specific to Compact 5000™ I/O
safety modules.
Safety Input This section describes features that are available on the Compact 5000 I/O
Module Features safety input module, that is, the 5069-IB8S and 5069-IB8SK modules.
The 5069-IB8S and 5069-IB8SK modules are 8-point safety sinking input
modules that use eight safety inputs and four test outputs. The 5069-IB8SK
module offers conformal coating.
In this case, Point Mode must be Safety Pulse Test. Safety input pairs must be
associated with different Test Output sources.
The test output can also be configured as a power supply to source 24V DC to an
external device, for example, a light curtain.
Figure 16 - Compact 5000 I/O Safety Input Module - Input Connected to Test Output
Channel Connections
The diagram shows devices that are connected to safety input
channels 0 and 3 and test output channel 0 and 1. You are not
restricted to using only those channels.
You can connect devices to any safety input channel or
combination of channels as needed.
We recommend that you connect even-numbered input points
to even-numbered test output points and odd-numbered
input points to odd-numbered test output points.
This wiring practice can maximize diagnostic independence
and separation.
Safety Input 0
SA Power
Connections to an external power supply that provides SA Safety Input 1
power via the SA Power RTB on one of the following: Safety Input 2
• Compact GuardLogix® 5380 Controller
• 5069-AENTR or 5069-AEN2TR EtherNet/IP™ Adapter Safety Input 3
• 5069-FPD Field Potential Distributor Safety Input 4
IMPORTANT: Remember the following:
• The 5069-IB8S and 5069-IB8SK modules use DC SA power. Safety Input 5
You must connect DC power to the component, that is, Safety Input 6
controller, adapter, or field potential distributor, that
provides SA Power to the modules. Safety Input 7
• If you install modules in a system that use AC SA power
Test Output 0
and DC SA power, you must install them on separate SA
power buses. Test Output 0
• You use a 5069-FPD field potential distributor to establish
Test Output 1
a new SA Power bus in a system. SA Power buses are
isolated from each other. To keep the modules on Test Output 1
separate SA Power buses, complete the following steps.
Test Output/Muting Output 2
1.Install the modules that use one type of SA power, for
example DC, to the right of the adapter or controller, Test Output/Muting Output 2
that is, the first SA Power bus.
2.Install the 5069-FPD field potential distributor to Test Output/Muting Output 3
establish a second SA Power bus. Test Output/Muting Output 3
3.Install the modules that use the other type of SA power,
for example AC, on the second SA Power bus. COM
COM
On
OUT
X
Off
Y
On the 5069-IB8S or 5069-IB8SK module, the test pulse width (X) is less than
700 μs; the test 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.
Figure 18 - Short Circuit Between Input Signal Lines
IN +
24V DC
COM
24V DC
0V DC
TO0
External Contact
TO1
External Contact
Single-channel Mode
If an error is detected on the input channel, Safety Input Data and Safety Input
Status turn off.
24V DC
Test Output 0
0V DC
ON
External Device
OFF
Normal Operation ON
Input Terminal 0
OFF
ON
Safety Input 0
Safety Network Data Sent Data OFF
to the Controller
ON
Safety Input 0
Status OFF
24V DC
Test Output 0
0V DC
ON
External Device
OFF
ON
Input Terminal 0
Fault Detection OFF
ON Fault Detected
Safety Input 0
Data OFF
Safety Network Data Sent
to the Controller
ON Fault is declared at the
Safety Input 0 end of the Test Output
Status OFF pulse.
After the steps are completed, the I/O indicator (red) turns off. The input data
is now active.
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.
ON
Input Signal
OFF
ON
Safety Input
Network Data
OFF
Off to 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.
ON
Input Signal
OFF
ON
Safety Input
Network Data
OFF
On to Off Delay
Figure 22 shows how muting lamp operation, status, and fault detection are
monitored.
The lamp test interval is 3 seconds. Two consecutive failed lamp tests are required
to declare a burned-out lamp condition.
The lamp test does not always run immediately after the test output is energized. It
starts at the next 3-second interval. To allow time for two consecutive test intervals,
program a minimum Test Output On Time of 6 seconds.
Figure 22 - Muting Lamp Timing Diagram
Connected
Connected
Disconnected
Muting Lamp 1 - Burnt-out lamp detected
Disconnected 2 - Good lamp detected
3 - Intermittent lamp testing stopped
Test Time 4 - Intermittent lamp testing started
Active
1 2 3 4
Lamp Test
Inactive
Test Interval
Bulb Connected/Good
Good
Muting Status
Bulb Disconnected/Burnt out
Burn-out
On
On
TO3 Output
Off Off
Table 47 shows the expected behavior of the muting status for test outputs
TO2M and TO3M. Keep the following points in mind as well:
• When power is applied to the 5069-IB8S or 5069-IB8SK module, and T2
or T3 remains commanded off, the muting status defaults to on.
This bit operation is designed to help prevent erroneous muting
instruction faults from the owner-controller. This bit status is not always
the true indication of a burned-out lamp.
Discrepancy
This section describes the following:
• Single Channel SIL 3 and Discrepancy Fault
• Transition Time Limit
• Fault Indication
If the time of the discrepancy between the two internal signals exceeds the
configured Transition Time Limit, that is, 2…500 ms, the safety input data and
the individual-safety input status turn off for the input channel. The safety
input is in the safe state.
However, a discrepancy can exist for a period of time before the safety input
data fault is generated.
• If the discrepancy is resolved before the time expires, there is no fault.
• If the discrepancy remains when the time expires, a fault occurs.
When the transition occurs in one of the internal signals before the transition
of the second internal signal, a discrepancy occurs. The threshold voltages for
the signals are slightly different.
• If the second internal signal transitions to the same state before the
Transition Time Limit elapses, the internal inputs are considered
equivalent.
In this case, no error is detected.
• If the second internal signal transition does not occur before the
Transition Time Limit elapses, the channel faults.
In the fault state, the input and status for the input channel is set low
(OFF).
IN 0
ON
Internal Signal 1 from IN 0
OFF
ON
Normal Operation Internal Signal 2 from IN 0
OFF
Transition Time Limit
IN 0
ON
Internal Signal 1 from IN 0
OFF
Fault Detection ON
Internal Signal 2 from IN 0
OFF
Transition Time Limit
Fault Indication
To clear the fault and return the module to normal operations, reset the
module. That is, cycle power to the module.
Safety Output This section describes features that are available only on the Compact 5000
Module Features I/O safety output modules, that is, the 5069-OBV8S and 5069-OBV8SK
modules.
The 5069-OBV8S and 5069-OBV8SK modules are safety output module that
uses eight safety outputs. You use the outputs in one of the following ways:
• Sourcing/sinking outputs in Bipolar Output mode
• Sourcing outputs in Sourcing Output mode.
• Solid-state outputs
• Single-channel mode uses one output signal, that is, data from an output
channel, to provide control.
If an error is detected, the safety output data and individual safety output
status turn off.
Figure 25 - 5069-OBV8S or 5069-OBV8SK Test Pulse in a Cycle
Sourcing Output
On
OUT
Off
X Y
Sinking Output
X Y
Off
OUT
On
On the 5069-OBV8S or 5069-OBV8SK module, the pulse width (X) is less than
700 μs, and the pulse period (Y) is less than100 ms.
Tip
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.
An open wire test and internal short circuit test can generate a pulse on a safety
output even in safety mode. To completely remove pulse from safety output in
Safety Mode, open wire test and internal short circuit test could be configured.
Please see Table 28 on page 104 and Table 36 on page 109.
Two successive safety output pulses are required to determine if a short circuit fault
exists. As a result, the effective pulse period is 200 ms, maximum
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.
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 Sent Safety Output 0
to the Controller Status OFF
Dual-channel Mode
IMPORTANT Dual-channel mode is only available if the module is connected so that
Output Mode is Sourcing.
When both output channels in a connection pair are in the On state and
without any faults, the safety outputs are turned on.
ON
Output 0
OFF
Normal Operation ON
Output 1
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
IMPORTANT The module can require up to 1 second in addition to the Output Error
Latch Time to complete the recovery.
Fault and Status Reporting The Compact 5000 I/O safety modules multicast 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:
• 5069-IB8S or 5069-IB8SK module - Table 14 on page 82
• 5069-OBV8S or 5069-OBV8SK module - Table 43 on page 116
• Appendix A, Troubleshoot Your Module on page 201.
Topic Page
Before You Begin 144
Create a New Module 144
Reserve an I/O Module Slot 152
Edit the Module Configuration Common Categories 154
Edit 5069-IA16 Module Configuration Categories 159
Edit 5069-IB16 Module Configuration Categories 160
Edit 5069-IB16F Module Configuration Categories 162
Edit 5069-IB6F-3W Module Configuration Categories 168
Edit 5069-OA16 Module Configuration Categories 174
Edit 5069-OB8 Module Configuration Categories 175
Edit 5069-OB16 Module Configuration Categories 176
Edit 5069-OB16F Module Configuration Categories 177
Edit 5069-OW4I Module Configuration Categories 178
Edit 5069-OW16 Module Configuration Categories 179
Edit 5069-OX4I Module Configuration Categories 180
View the Module Tags 181
This chapter describes how to configure your Compact 5000™ I/O standard
modules in a Logix Designer application project. You can use the default
module configuration or edit the module configuration.
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, Features Common to Compact 5000 I/O Digital Modules on
page 63
• Chapter 3, Input Module Features on page 75
• Chapter 4, Output Module Features on page 97
• Chapter 5, Safety Module Features on page 125
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 standard modules as remote modules, add a Compact 5000
I/O EtherNet/IP™ adapter to the project.
For more information on how to add a Compact 5000 I/O EtherNet/IP
adapter to a Logix Designer application project, see the Compact 5000
EtherNet/IP Adapters User Manual, publication 5069-UM007.
Once the project is created and, if necessary, the adapter is added, you can
create a module in the Logix Designer application project.
Create a New Module There are two methods to add modules to your Logix Designer
application project.
• Discover I/O modules
• New I/O modules
3. At the Select Module Type window, click Create to add the discovered
module to your project.
To add additional local 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…6.
• If you did not clear the Close on Create checkbox when you created the
first I/O module, repeat steps 2…6.
2. At the Select Module Type window, click Create to add the discovered
module to your project.
To add additional local 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.
3. At the Select Module Type window, click Create to add the discovered
module to your project.
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 3…6.
• If you did not clear the Close on Create checkbox when you created the
first I/O module, repeat steps 2…6.
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.
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.
Reserve an I/O Module Slot As described in page 29, the 5069-ARM address reserve module reserves a
module slot in the physical system and in the Logix Designer application
project that is configured for the system.
2. At the Select Module Type window, click Create to add the discovered
module to your project.
2. To confirm the module deletion, click Yes on the dialog box that appears.
3. To add the Compact 5000 I/O digital module that uses the node address
that the 5069-ARM module reserved, follow the steps that are described
previously in this section.
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 Compact 5000 I/
O digital modules. Some categories are specific to the module type.
For example purposes, the figures in this section are from a
5069-IB16 module.
The following categories apply to all Compact 5000 I/O standard 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 Compact 5000 I/O digital modules.
Module Definition
To change Module Definition parameters from the default values, click the
Change ellipsis on the General tab of the Module Properties dialog box.
IMPORTANT The graphic is an example of a Module Definition dialog box. The available fields
can vary between Compact 5000 I/O digital modules types.
For example, the 5069-IA16 input module does not support counters so the
Counters parameter is not available on the Module Definition dialog box for that
module.
Table 49 describes the parameters that are available on the Module Definition
dialog box.
Table 49 - 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. • Exact Match
For more information, see the following:
Electronic Keying • Compatible Module
• Electronic Keying on page 70
• Electronic Keying in Logix 5000™ Control Systems Application Technique, publication LOGIX-AT001 • Disable Keying
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
• Which tags are generated when configuration is complete • Listen Only Data(2)
• Data
All available configurations, input data. This connection type creates all controller tags specific to the module •
Input Data - Input modules only Timestamped Data
type being used.
• Packed Data
• None
• 2
Counters - Input modules only Determines the number of counters that are used for the module type.
• 4
• 8
• 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 Requested Packet
Interval on page 42.
• Set the Connection over the EtherNet/IP network type of connection.
• Inhibit the module. For more information on how to inhibit the module,
see page 69.
• 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 215.
Edit 5069-IA16 Module In addition to the General, Connection, and Module Info categories, the Points
Configuration Categories category is available when you configure a 5069-IA16 module:
IMPORTANT If you use the Listen Only 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 5069-IB16 Module To configure a 5069-IB16K module, you use the 5069-IB16 module profile in
Configuration Categories your Logix Designer application project.
IMPORTANT If you use the Listen Only connection type, the Points Category and Counters
Category do not appear.
Counters Category
The Counters category is only available if you choose a value for Counters in
the Module Definition dialog box.
The Counters category shows the configuration options available for each
counter. 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 5069-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.
The maximum number of counters that can be configured is eight channels.
That is, counters 0…7.
Points Category
The Points category shows the available input filter time values for the
module points.
Edit 5069-IB16F Module In addition to the General, Connection, and Module Info categories, the
Configuration Categories following categories are available when you configure a 5069-IB16F module:
• Counters Category
• Points Category
• Events Category
• Time Sync Category
IMPORTANT If you use the Listen Only connection type, the Points Category, Counters Category,
Events Category, and Time Sync 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
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 5069-IB16F 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.
The maximum number of counters that can be configured is eight
channels. That is, counters 0…7.
Points Category
The Points category shows the available input filter time values for the module points.
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.
For more information on the fields on this screen, see the following:
• Input filters - page 77
• Timestamping - page 84
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 166.
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
Edit 5069-IB6F-3W Module In addition to the General, Connection, and Module Info categories, the
Configuration Categories following categories are available when you configure a 5069-IB6F-3W module:
• Points Category
• Counters Category
• Events Category
• Time Sync Category
IMPORTANT If you use the Listen Only connection type, the Points Category, Counters
Category, Events Category, and Time Sync 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 for the 5069-IB6F-3W module functions the same as it
does for the other Compact 5000 I/O standard input modules. The only
difference is that the 5069-IB6F-3W module offers no more than four counters.
The Counters category shows the configuration options available for each
counter. 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 5069-IB6F-3W module to use two
counters, the number of points available on the module is four. That is,
points 2…5.
The maximum number of counters that can be configured is four
channels. That is, counter 0…3.
Points Category
The Points category shows the available input filter time values for the
module points.
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.
For more information on the fields on this screen, see the following:
• Input filters - page 77.
• Timestamping - page 84
• Chatter Detection - page 85
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 172.
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
Edit 5069-OA16 Module In addition to the General, Connection, and Module Info categories, the Points
Configuration Categories category is available when you configure a 5069-OA16 module.
IMPORTANT If you use the Listen Only 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
Edit 5069-OB8 Module In addition to the General, Connection, and Module Info categories, the Points
Configuration Categories category is available when you configure a 5069-OB8 module.
IMPORTANT If you use the Listen Only 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 5069-OB16 Module To configure a 5069-OB16K module, you use the 5069-OB16 module profile in
Configuration Categories your Logix Designer application project.
In addition to the General, Connection, and Module Info categories, the Points
category is available when you configure a 5069-OB16 module.
IMPORTANT If you use the Listen Only 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 5069-OB16F Module In addition to the General, Connection, and Module Info categories, the Points
Configuration Categories category is available when you configure a 5069-OB16F module.
IMPORTANT If you use the Listen Only 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 5069-OW4I Module In addition to the General, Connection, and Module Info categories, the Points
Configuration Categories category is available when you configure a 5069-OW4I module.
IMPORTANT If you use the Listen Only 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
Edit 5069-OW16 Module In addition to the General, Connection, and Module Info categories, the Points
Configuration Categories category is available when you configure a 5069-OW16 module.
IMPORTANT If you use the Listen Only 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
Edit 5069-OX4I Module In addition to the General, Connection, and Module Info categories, the Points
Configuration Categories category is available when you configure a 5069-OX4I module.
IMPORTANT If you use the Listen Only 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
• Communication Failure Output State
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.
Notes:
Topic Page
Before You Begin 183
Create a New Module 184
Edit the Module Configuration Common Categories 187
Edit the 5069-IB8S and 5069-IB8SK Module Configuration Categories 193
Edit the 5069-OBV8S and 5069-OBV8SK Module Points Category 194
View the Module Tags 195
Replace a Safety Module 196
This chapter describes how to configure your Compact 5000™ I/O safety
modules in a Logix Designer application project.
IMPORTANT You must use the Logix Designer application, version 32 or greater with
the modules.
By default, all safety input and output channels on Compact 5000 I/O
safety 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 safety modules as remote I/O modules, add a
Compact 5000 I/O EtherNet/IP™ adapter to the project.
For more information on how to add a Compact 5000 I/O EtherNet/IP
adapter to a Logix Designer application project, see the Compact 5000
EtherNet/IP Adapters User Manual, publication 5069-UM007.
Once the project is created and, if necessary, the adapter is added, you can
create a module in the Logix Designer application project.
Create a New Module Unlike Compact 5000 I/O standard modules, you cannot add a Compact 5000
I/O safety module to a Logix Designer application project while the project is
online. The project must be offline to add Compact 5000 I/O safety modules
to it.
You can create a new local or remote Compact 5000 I/O safety module.
Local I/O modules are installed in the same system as the Compact
GuardLogix® 5380 controllers. Remote I/O modules are installed in a
system that includes a Compact 5000 I/O EtherNet/IP adapter that connects
to an EtherNet/IP network.
2. At the Select Module Type window, click Create to add the discovered
module to your project.
To add additional local 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.
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.
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 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 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 Compact 5000 I/
O safety modules. Some categories are specific to the module type.
IMPORTANT By default, all safety input and output channels on Compact 5000 I/O safety
modules are disabled.
You must configure each point that is used in a Safety application.
The following categories apply to all Compact 5000 I/O safety modules and are
described in this section.
• 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 Compact 5000 I/O safety modules.
You use this category to complete the following tasks:
• Name the module.
• Assign a node number.
• Describe the module.
• Access the Module Definition.
The SNN is a time-based number that uniquely identifies subnets across all
networks in the safety system. All Compact 5000 I/O safety modules in a same
system use the same SNN by default.
• Local Compact 5000 I/O safety modules are automatically assigned the
same SNN as the 5069 Backplane SSN in the controller configuration.
• Remote Compact 5000 I/O safety modules are automatically assigned the
same SNN.
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.
Module Definition
Module Definition parameters are available on the General tab of the Module
Properties dialog box in the Logix Designer application project.
Table 50 describes the parameters that are available on the Module Definition
dialog box.
Table 50 - 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
• Exact Match
Software method by which you reduce the possibility of using the wrong device in a control system.
For more information, see the following: • Compatible Module
Electronic Keying • Electronic Keying on page 70 • Disable Keying
• Electronic Keying in Logix 5000™ Control Systems Application Technique, We strongly recommend that you
publication LOGIX-AT001 use Exact Match or Compatible
Module in Safety applications.
Determines the following for the module type you configure:
• Which controller tags are generated when configuration is complete • This Controller
Configured By • Whether you can choose an Output Data type - Output module only
• Whether you can choose an Output Mode - Output module only • External Means(1)
• Whether muting lamp points can be used - Input module only
Determines what type of input data is exchanged between the module and the controller.
Creates all controller tags specific to the module type being used. • Safety data
Input Data IMPORTANT: The 5069-OBV8S and 5069-OBV8SK output modules exchange input data with • Safety packed data
the controller.
• None
Muting Lamp Points - 5069-IB8S • Point 02
Determines which input channels, if any, are connected to muting lamps.
or 5069-IB8SK module only • Point 03
• Point 02 and 03
• None - If Configured By is External
Means.
Output Data - 5069-OBV8S or Determines what type of output data is exchanged between the module and the controller.
5069-OBV8SK module only The available choices are dictated by the Configured By parameter choice. • Safety data and Safety packed
data - If Configured By is This
Controller.
Determines how the outputs are used. That is, one of the following:
• Sourcing outputs. In this case, you connect the external device to only the sourcing point on an • Sourcing
Output Mode - 5069-OBV8S or output channel.
5069-OBV8SK module only • Bipolar
• As connection pairs. In this case, you connect the external device to both the sourcing and sinking
points on an output channel.
(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.
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 69.
IMPORTANT You cannot set the RPI for Compact 5000 I/O safety modules on the
Connections category. For Compact 5000 I/O safety modules, you set
the RPI on the Safety category.
Remote Compact 5000 I/O safety modules support the Connection over
EtherNet/IP parameter.
• With safety input data, you can choose Unicast or Multicast.
• With safety output data, you must use Unicast.
Safety Category
The Safety category lets you set the RPI rate. You must click the Advanced
button to change the Connection Reaction Time Limit configuration.
IMPORTANT Remember, the Safety Task period determines the 5069-OBV8S or 5069-OBV8SK
module RPI.
For more information on the RPI and the Connection Reaction Time Limit
parameters, see Requested Packet Interval on page 42.
Edit the 5069-IB8S and The following categories are available when you configure a 5069-IB8S or 5069-
5069-IB8SK Module IB8SK module:
• Input Points Category
Configuration Categories • Test Output Points Category
You must configure each point to use it in a Safety application. The inputs are
disabled by default.
IMPORTANT The Logix Designer application project limits the number of Safety Pulse
tests to which you can map a test source.
For example, you can map Test Source 0 to a maximum of two Safety Pulse
tests. If you try to exceed the maximum number, the software helps prevent
the configuration and a message similar to the following appears.
You must configure each point to use it in a Safety application. The outputs are
disabled by default.
Edit the 5069-OBV8S and The 5069-OBV8S and 5069-OBV8SK modules use the Points category.
5069-OBV8SK Module The Points category is only available if you choose This Controller for the
Points Category 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.
Figure 28 - Configure Points
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.
Replace a Safety 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 networks
in the application do not compromise communication between the correct
safety devices.
For example, when a Compact 5000 I/O EtherNet/IP adapter is used in a safety
application, the Logix Designer application project assigns it an SNN. All
Compact 5000 I/O digital modules that are installed with that adapter, are
automatically assigned the same SNN.
However, each Compact 5000 I/O safety 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 constitute the DeviceID of the
safety module.
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:
1. Right-click the module and choose Properties.
2. On the Connection tab, click Inhibit module.
3. Click Apply and then OK.
Complete the following 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.
3. When a dialog box appears asking if you want to continue with the reset,
read it and click Yes.
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 51 - Replace a Compact 5000 I/O Safety Module
Controller Safety Signature Exists Replacement Module Condition Action Required
No No SNN (Out-of-box) None. The module is ready for use.
Yes or No Same SNN as original safety task configuration None. The module is ready for use.
Yes No SNN (Out-of-box) Complete the steps in Set the SNN Manually on page 196.
Yes
Different SNN from original safety task configuration
No
If the project is configured for ‘Configure Always’, follow the appropriate steps
to replace a Compact 5000 I/O safety 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.
Topic Page
Module Status Indicator 202
Compact 5000 I/O Standard Input Modules Status Indicators 203
Compact 5000 I/O Standard Output Modules Status Indicators 205
Compact 5000 I/O Safety Input Module Status Indicators 209
Compact 5000 I/O Safety Output Module Status Indicators 211
Use the Logix Designer Application for Troubleshooting 213
Internal Fault Triggered on the Safety Output Module 218
Module Status Indicator Table 52 describes the Module (MOD) Status indicator on Compact 5000 I/O
Standard Modules digital modules.
Table 52 - Module Status Indicator - Compact 5000 I/O Digital Modules
Indicator Description Recommended Action
State
None if your application does not use the module
If your application uses the module and it is
Off The module is not powered. expected to be operating, complete the following:
• Confirm that the system is powered.
• Confirm that the module is installed properly.
The module has a connection to the owner-
Steady green None
controller and is operating normally.
One of the following:
• The module does not have a connection to the
controller. A connection can result from missing, Troubleshoot your Logix Designer application to
Flashing green incomplete, or incorrect module configuration. determine what is helping help prevent a
• Compact 5000 I/O Safety Modules only - A connection from the module to the controller and
connection can be established with the correct the issue.
controller, but the Validator has not completed
an initial Time Coordination exchange.
Complete the following actions:
Steady red The module experienced a nonrecoverable fault. 1. Cycle power to the module.
2. If the status indicator remains in the steady red
state, replace the module.
Safety Modules
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.
To clear a recoverable fault, complete one of
the following:
One of the following conditions exists: – Cycle module power.
• A module firmware update is in progress. – Click Reset Module in the Logix Designer
Flashing red • A module firmware update attempt failed. application project via the Module Info
category of the Module Properties dialog box.
• The device has experienced a recoverable fault.
• A connection to the module has timed out. If the fault does not clear after you cycle power
and click 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.
Updating red/ Compact 5000 I/O Safety Modules only - The UNID Commission the UNID in the module.
green needs to be commissioned in the module.
Compact 5000 I/O Figure 29 shows the Compact 5000 I/O standard AC input module
Standard Input Modules status indicators.
Status Indicators Figure 29 - Compact 5000 I/O Standard AC Input Module I/O Status Indicators
Table 53 describes the Compact 5000 I/O standard AC input module I/O
status indicators.
Table 53 - I/O Status Indicators - Compact 5000 I/O Standard AC Input Module
Indicator State Description Recommended Action
Off Input is Off or no module power applied None
Steady yellow The input is On. None
Table 54 describes the Compact 5000 I/O standard DC input modules I/O
status indicators.
Table 54 - I/O Status Indicators - Compact 5000 I/O Standard DC Input Modules
Indicator State Description Recommended Action
Off The input is Off, or no module power applied None
Steady yellow The input is On. None
Compact 5000 I/O Figure 31 shows the status indicators on the Compact 5000 I/O standard AC
Standard Output output module.
Modules Status Indicators Figure 31 - Compact 5000 I/O Standard AC Output Modules Status Indicators
Module Status
Indicator
Table 55 describes the I/O status indicators on Compact 5000 I/O standard AC
output modules.
Table 55 - I/O Status Indicators - Compact 5000 I/O Standard AC Output Module
Indicator State Description Recommended Action
Off Output is Off, or no module power applied. None
Steady yellow The output is On. None
Flashing red A Field Power Loss detection condition exists. Reconnect power to the input.
Figure 32 show the status indicators on the Compact 5000 I/O standard DC
output modules.
Figure 32 - Compact 5000 I/O Standard Output DC Modules Status Indicators
Table 56 describes the I/O status indicators on Compact 5000 I/O standard DC
output modules.
Table 56 - I/O Status Indicators - Compact 5000 I/O Standard DC Output Modules
Indicator State Description Recommended Action
Off Output is Off, or no module power applied None
Steady yellow The output is On. None
One of the following: One of the following:
• A No Load or Short Circuit condition exists. • Locate and correct the no load or short
Flashing red • 5069-OB8, 5069-OB16/B, 5069-OB16F/B, circuit condition.
5069-OB16K/B - A Field Power Loss • Locate and correct the cause of field power
condition exists. loss condition.
Figure 33 - Compact 5000 I/O Standard Relay Output Module Status Indicators
5069-OW4I 5069-OW16
5069-OX4I
Module Status
Indicator
(0 N.C.)
(0 N.O.)
(O COMMON)
(1 N.C.)
(1 N.O.) I/O Status Indicators
(1 COMMON)
(2 N.C.)
(2 N.O.)
(2 COMMON)
(3 N.C.)
(3 N.O.)
(3 COMMON)
Terminals
are unused
Table 57 describes the I/O status indicators on Compact 5000 I/O standard
relay output modules.
Table 57 - I/O Status Indicators - Compact 5000 I/O Standard Relay Output Modules
Indicator State Description Recommended Action
Off Output is Off, or no module power applied None
Steady yellow The output is On. None
5069-OW16 only - A Field Power Loss condition Locate and correct the cause of field power
Flashing red exists. loss condition.
Compact 5000 I/O Safety Figure 34 shows the Compact 5000 I/O safety input module status indicators.
Input Module Figure 34 - Compact 5000 I/O Safety Input Module Status Indicators
Status Indicators 5069-IB8S, 5069-IB8SK
Safety Modules
IMPORTANT: The 5069-IB8SK module status indicators appear the same as the
indicators are shown on the 5069-IB8S module.
SA Status Indicator
Table 58 describes the Compact 5000 I/O safety input module SA
status indicator.
Table 58 - SA Status Indicator - Compact 5000 I/O Safety Input Module
Indicator State Description Recommended Action
One of the following:
• There is no SA power that is applied to the
module.
• The status of SA power is unknown. Check the power source and address any
Off • The SA power is below valid range as issues.
defined by the module. That is, the power is
too low.
• During a safety critical fault, SA power was
turned off.
SA power is in a valid range as defined by the
Steady green None
module.
The SA power is outside the valid range as Diagnose and remedy the cause of the power
Steady red defined by the module. In this case, the power being outside the valid range.
can be off, too low, or too high.
Compact 5000 I/O Safety Figure 35 show the status indicators on the Compact 5000 I/O safety
Output Module Status output module.
Indicators Figure 35 - Compact 5000 I/O Safety Output Module Status Indicators
Safety Modules
5069-OBV8S, 5069-OBV8SK
IMPORTANT: The 5069-OBV8SK module status indicators appear the same as the
indicators are shown on the 5069-OBV8S module.
SA Status Indicator
Table 60 describes the Compact 5000 I/O safety output module SA
status indicator.
Table 60 - SA Status Indicator - Compact 5000 I/O Safety Output Module
Indicator State Description Recommended Action
One of the following:
• There is no power SA power that is applied
to the module.
• The status of SA power is unknown. Check the power source and remedy any
Off • The SA power is below valid range as issues.
defined by the module. That is, the power is
too low.
• During a safety critical fault, SA power was
turned off.
SA power is in a valid range as defined by the
Steady green None
module.
The SA power is outside the valid range as Diagnose and remedy the cause of the power
Steady red defined by the module. In this case, the power being outside the valid range.
can be off, too low, or too high.
Use the Logix Designer The Logix Designer application indicates the presence of fault conditions.
Application for Fault conditions are reported in the following ways:
Troubleshooting • Warning Signal in the I/O Configuration Tree
Standard Modules • Status and Fault Information in Module Properties Categories
• Logix Designer Application Tag Editor
Safety Modules
As shown in Figure 39, major and minor fault information is listed on the
Module Info tab in the Status section.
Figure 39 - Major and Minor Fault Information
Module Diagnostics
Point Diagnostics
Internal Fault Triggered on Table 62 describes conditions that can trigger InternalFault.
the Safety Output Module Table 62 - Conditions That Trigger InternalFault
Safety Modules
I/O Status
Output
Conditions Tag Value Diagnostic Value Indicator
Behavior State
• Output Mode - BIpolar
• Point Operation Type - Single
• Point Mode - Safety
• A load is connected between a
sourcing output point and a Faults I.Ptxx.Fault tag = 1 InternalFault = 1
sinking output point.
• O.Ptxx.Data tag = 0
• An overload resistor shorts the
sourcing output point to 0V DC
• Output Mode - Bipolar
• Point Operation Type - Single The I/O status
• Point Mode - Safety or Safety indicator for
Pulse Test the faulted
• A load is connected between a Faults I.Ptxx.Fault tag = 1 InternalFault = 1 output point is
sourcing output point and a steady red.
sinking output point.
• O.Ptxx.Data tag = 0
• Either output point shorts to 0V DC
• Output Mode - Sourcing I.Ptxx.Fault tag = 1 InternalFault = 1
• Point Operation Type - Single IMPORTANT: The tag IMPORTANT: The
value occurs on the diagnostic value
• Point Mode - Safety or Safety Faults faulted output point occurs on the faulted
Pulse Test and all of its output point and all of
• O.Ptxx.Data tag = 1 associated group its associated group
• Output point shorts to 24V DC points. points.
When the conditions that trigger the diagnostics as described in Table 62 are
corrected, the output faults are cleared, the tags and diagnostics reset to 0, and
the I/O status indicators turn off.
Topic Page
Name Conventions 220
Access the Tags 221
5069-IA16 Module Tags 222
5069-IB16 Module Tags 223
5069-IB16F Module Tags 225
5069-IB6F-3W Module Tags 232
5069-OA16 Module Tags 239
5069-OB8 Module Tags 241
5069-OB16 Module Tags 243
5069-OB16F Module Tags 245
5069-OW4I, 5069-OW16, and 5069-OX4I Module Tags 248
5069-IB8S and 5069-IB8SK Module Tags 250
5069-OBV8S and 5069-OBV8SK Module Tags 252
Module tags are created when you add a module to the Logix Designer
application project.
The set of tags that are associated with any module depends on the choices that
you make in the Module Definition dialog box. For example, if you use a Listen
Only Connection, the Logix Designer application creates only Input tags for
that module.
IMPORTANT The tables that are in this section list all 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.
Name Conventions The module tags use defined naming conventions. The conventions are
as follows:
Standard Modules
• One of the following:
- Module is local - Local
- Module is remote - Name of the remote adapter
• Slot number
• Tag type
• Channel/point number
• Parameter
Safety Modules
Access the Tags You can view tags from the Tag Editor.
Standard Modules 1. Open your Logix Designer application project.
2. Right-click Controller Tags and choose Monitor Tags.
Safety Modules
5069-IA16 Module Tags This section describes the tags that are associated with the 5069-IA16 module.
Standard Modules
Configuration Tags
Table 63 describes the 5069-IA16 module configuration tags.
Input Tags
Table 64 describes the 5069-IA16 module input tags.
Table 64 - 5069-IA16 Module Input Tags
Name Data Type Definition Valid Values
• 0 = Idle
RunMode BOOL Channel’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 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 • -128…+127
DiagnosticSequenceCount SINT detected to not detected.
Set to zero by product reset or power cycle. Wraps from 255 (-1) to The value of 0 is skipped except during module power-up.
1 skipping zero.
• 0 = Off
Ptxx.Data BOOL Indicates the current input value.
• 1 = On
• 0 = Good data
Indicates that channel data is inaccurate and cannot be trusted • 1 = Bad data (Faulted)
for use in the application. If the tag is set to 1, you must troubleshoot the module to
Ptxx.Faults BOOL For more information, see Module Data Quality Reporting on correct the cause of the inaccuracy.
page 67. 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 channel data can be inaccurate but the degree • 1 = Uncertain data
of inaccuracy is not known. If the tag is set to 1, you must troubleshoot the module to
Ptxx.Uncertain BOOL For more information, see Module Data Quality Reporting on correct the cause of the inaccuracy.
page 67. IMPORTANT: Once the condition that causes the tag to change
to 1 is removed, the tag automatically resets to 0.
5069-IB16 Module Tags This section describes the tags that are associated with the 5069-IB16 module.
Standard Modules You use the 5069-IB16 module profile in your Logix Designer application
project with the 5069-IB16K module.
Configuration Tags
Table 65 describes the 5069-IB16 module configuration tags.
Input Tags
Table 66 describes the 5069-IB16 module input tags.
Table 66 - 5069-IB16 Module Input Tags
Name Data Type Definition Valid Values
• 0 = Idle
RunMode BOOL Channel’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 prognostics
threshold is reached.
threshold is reached
Indicates if the module is operating outside its 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.
Set to zero by product reset or power cycle. Wraps from 255 (-1) The value of 0 is skipped except during module power-up.
to 1 skipping zero.
• 0 = Off
Counterxx.Data BOOL Indicates the current input value.
• 1 = On
• 0 = Good data
Indicates that counter data is inaccurate and cannot be trusted • 1 = Bad data (Faulted)
for use in the application. If the tag is set to 1, you must troubleshoot the module to correct
Counterxx.Fault BOOL For more information, see Module Data Quality Reporting on the cause of the inaccuracy.
page 67. 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 degree • 1 = Uncertain data
of inaccuracy is not known. If the tag is set to 1, you must troubleshoot the module to correct
Counterxx.Uncertain BOOL For more information, see Module Data Quality Reporting on the cause of the inaccuracy.
page 67. 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 (rising or • 0 = Corresponding Done bit did not trigger the event
Counterxx.Done BOOL falling depending on configuration) triggered the event. • 1 = Corresponding Done bit triggered the event
The counter counted up to Preset -1 and continued counting from • 0 = Counter has not counted up to Preset - 1 and continued
or 0. counting from 0
Counterxx.Rollover BOOL The O:RolloverAck bit transitioning from 0 to 1 or the O:Reset • 1 = Counter counted up to Preset - 1 and continued counting
transitioning from 0 to 1 clears this bit. from 0
Counterxx.Count DINT The number of input transitions counted by a counter. All values.
• 0 = Off
Ptxx.Data BOOL Indicates the current input value.
• 1 = On
• 0 = Good data
Indicates that channel data is inaccurate and cannot be trusted • 1 = Bad data (faulted)
for use in the application. If the tag is set to 1, you must troubleshoot the module to correct
Ptxx.Fault BOOL For more information, see Module Data Quality Reporting on the cause of the inaccuracy.
page 67. 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 channel data can be inaccurate but the degree • 1 = Uncertain data
of inaccuracy is not known. If the tag is set to 1, you must troubleshoot the module to correct
Ptxx.Uncertain BOOL For more information, see Module Data Quality Reporting on the cause of the inaccuracy.
page 67. IMPORTANT: Once the condition that causes the tag to change
to 1 is removed, the tag automatically resets to 0.
Output Tags
Table 67 describes the 5069-IB16 module output tags. The 5069-IB16 module
output tags are only available if you have enabled counters in the Module
Definition dialog box.
Table 67 - 5069-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 • 0 = I:Rollover bit is not cleared
Counterxx.RolloverAck BOOL from 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.
5069-IB16F Module Tags This section describes the tags that are associated with the 5069-IB16F module.
Standard Modules
Configuration Tags
Table 68 describes the 5069-IB16F module configuration tags.
Input Tags
Table 71 describes the 5069-IB16F module input tags.
Table 71 - 5069-IB16F Module Input Tags
Name Size Definition Valid Values
• 0 = Idle
RunMode BOOL Channel’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
Diagnostic Active BOOL Indicates if any diagnostics are active or if the prognostics threshold is reached. • 1 = One or more diagnostics are active or the
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 master, but is not now • 1 = A valid time master was detected on the
CIPSyncTimeout BOOL backplane, but the time master has timed out.
due to a timeout.
The module is using its local clock and can be
drifting away from the last known time master.
Output Tags
Table 72 describes the 5069-IB16F module output tags.
Table 72 - 5069-IB16F Module Output Tags
Name Size Definition Valid Values
• 0 = Do not reset
Counterxx.Reset BOOL When this bit transitions from 0 to 1, I:Count, and I:Rollover are set to zero.
• 1 = Reset
Counterxx.RolloverAck BOOL Clears the Rollunder tag in the input tag when it transitions from 0 to 1. 0 or 1
• 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, I:Count=0., else I:Done bit always = 0. Set 0…2,147,483,647
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.
• 0 = time stamps are not erased.
Ptxx.ResetTimestamps BOOL Erases all recorded time stamps for the input channel when it transitions from 0 to 1.
• 1 = time stamps are erased.
An Off to On time stamp identifier that is written by the controller to indicate that the identified
time stamp has been seen and acted on.
• When Latching is enabled and the time stamp Number that is received from the controller
transitions to the most recent time stamp that is produced, the module can produce a new All values.
Ptxx.TimestampOffOnNumberAck INT time stamp.
• When Latching is disabled and the time stamp Number that is received from the controller
transitions to the most recent time stamp that is produced, the PtxxTimestampOffOn and
the Ptxx.TimestampOverflowOffOn tags are cleared.
An On to Off time stamp identifier that is written by the controller to indicate that the identified
time stamp has been seen and acted on.
• When Latching is enabled and the time stamp Number that is received from the controller
transitions to the most recent time stamp that is produced, the module can produce a new All values.
Ptxx.TimestampOnOffNumberAck INT
time stamp.
• When Latching is disabled and the time stamp Number that is received from the controller
transitions to the most recent time stamp that is produced, the PtxxTimestampOnOff and
the Ptxx.TimestampOverflowOnOff tags are cleared.
5069-IB6F-3W Module Tags This section describes the tags that are associated with the
5069-IB6F-3W module.
Standard Modules
Configuration Tags
Table 73 describes the 5069-IF6F-3W module configuration tags.
Input Tags
Table 76 describes the 5069-IB6F-3W module input tags.
Table 76 - 5069-IB6F-3W Module Input Tags
Name Size Definition Valid Values
• 0 = Idle
RunMode BOOL Channel’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
DiagnosticActive BOOL Indicates if any diagnostics are active or if the prognostics threshold is reached. • 1 = One or more diagnostics are active or the
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 master, but is not now • 1 = A valid time master was detected on the
CIPSyncTimeout BOOL backplane, but the time master has timed out. The
due to a timeout.
module is using its local clock and can be drifting
away from the last known time master.
Increments for each time a distinct diagnostic condition is detected, and when a -127…+128
distinct diagnostic condition transitions from detected to not detected.
DiagnosticSequenceCount SINT The value of 0 is skipped except during module
Set to zero by product reset or power cycle. Wraps from 255 (-1) to 1 skipping power-up.
zero.
Indicates if the module is operating outside its designed operating range of if • 0 = Good
Uncertain BOOL data is under manual or override control. • 1 = Uncertain
• 0 = Off
Counterxx.Data BOOL Indicates the current input value.
• 1 = On
• 0 = Good data
• 1 = Bad data (Faulted)
Indicates that channel data is inaccurate and cannot be trusted for use in the If the tag is set to 1, you must troubleshoot the
Counterxx.Fault BOOL application. module to correct the cause of the inaccuracy.
For more information, see Module Data Quality Reporting on page 67. 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 If the tag is set to 1, you must troubleshoot the
Counterxx.Uncertain BOOL is not known. module to correct the cause of the inaccuracy.
For more information, see Module Data Quality Reporting on page 67. IMPORTANT: Once the condition that causes the
tag to change to 1 is removed, the tag
automatically resets to 0.
Counterxx.Done BOOL Indicates that the I:Count tag ≥ O:Preset.G430. 0 or 1
The counter counted up to RolloverValue - 1 (for HSC) or Preset -1 (for simple
counters) and then continued counting from the O:Rollunder (for HSC) or 0 (for 0 or 1
Counterxx.Rollover BOOL simple counters). The O:RolloverAck bit transitioning from 0 to 1 or the O:Reset
transitioning from 0 to 1 clears the bit.
Counterxx.Count DINT The number of input transitions counted by a counter. All values.
• 0 = A valid time master has not timed out.
Indicates that the module was once synced with a 1588 master, but is not now • 1 = A valid time master was detected on the
EventStatusx.CIPSyncTimeout BOOL backplane, but the time master has timed out. The
due to a timeout.
module is using its local clock and can be drifting
away from the last known time master.
Indicates when an event has been discarded because events are occurring faster • 0 = An event status has not been dropped
EventStatusx.EventDropped BOOL than they are being acknowledged. • 1 = An event status has been dropped
Running count of events, which increments by one each new time event. The
originator sets the Event Number ACK to the Event Number to acknowledge
EventStatusx.EventNumber DINT receipt of the event. When the EventNumber reaches it maximum value and rolls All values.
over it is to roll over to 1, not 0.
When EO.Event[<n>].ResetEvent transitions from 0 to 1,
I.EventStatus[<n>].EventReset transitions to 1 to indicate that the reset was • 0 = Do not reset
EventStatusx.EventReset BOOL received and completed. It stays 1 until EO.Event[<n>].ResetEvent transition to • 1 = Reset
zero.
The number of events currently queued in the modules. A value greater than zero All positive values.
EventStatusx.EventsPending SINT indicates that the controller is not currently keeping up with the rate of events.
Output Tags
Table 77 describes the 5069-IB6F-3W module output tags.
Table 77 - 5069-IB6F-3W Module Output Tags
Name Size Definition Valid Values
When this bit transitions from 0 to 1, I:Count, and I:Rollover • 0 = Do not reset
Counterxx.Reset BOOL are set to zero. • 1 = Reset
Clears the Rollunder bit in the input tag when it transitions
Counterxx.RolloverAck BOOL 0 or 1
from 0 to 1.
• 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. 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 time stamps for the input channel when • 0 = time stamps are not erased
Ptxx.ResetTimestamps BOOL it transitions from 0 to 1. • 1 = time stamps are erased
An Off to On time stamp identifier that is written by the
controller to indicate that the identified time stamp has been
seen and acted on. When Latching is enabled and the time
stamp Number that is received from the controller matches
Ptxx.TimestampOffOnNumberAck INT the most recent time stamp that is produced, the module can All values.
produce a new time stamp.
IMPORTANT: When this tag value matches the
Ptxx.TimestampOffOnNumber input tag value the
Pt.xxTimestampOffOn input tag value is cleared.
An On to Off time stamp identifier that is written by the
controller to indicate that the identified time stamp has been
seen and acted on. When Latching is enabled and the time
stamp Number that is received from the controller matches
Ptxx.TimestampOnOffNumberAck INT the most recent time stamp that is produced, the module can All values.
produce a new time stamp.
IMPORTANT: When this tag value matches the
Ptxx.TimestampOnOffNumber input tag value, the
Pt.xxTimestampOnOff input tag value is cleared.
5069-OA16 Module Tags This section describes the tags that are associated with the 5069-OA16 module.
Standard Modules
Configuration Tags
Table 78 describes the 5069-OA16 module configuration tags.
Input Tags
Table 79 describes the 5069-OA16 module input tags.
Table 79 - 5069-OA16 Module Input Tags
Name Size Definition Valid Values
• 0 = Idle
RunMode BOOL Channel’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 power-up.
(-1) to 1 skipping zero.
• 0 = Off
Ptxx.Data BOOL Indicates the current input value.
• 1 = On
• 0 = Good data
Indicates that channel data is inaccurate and cannot be • 1 = Bad data (Faulted)
trusted for use in the application. If the tag is set to 1, you must troubleshoot the
Ptxx.Fault BOOL on module to correct the cause of the inaccuracy.
For more information, see Module Data Quality Reporting
page 67. 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 channel 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 67. IMPORTANT: Once the condition that causes the
tag to change to 1 is removed, the tag
automatically resets to 0.
Output Tags
Table 80 describes the 5069-OA16 module output tags.
Table 80 - 5069-OA16 Module Output Tags
Name Size Definition Valid Values
• 0 = Off
Ptxx.Data BOOL Indicates the current output value.
• 1 = On
5069-OB8 Module Tags This section describes the tags that are associated with the 5069-OB8 module.
Standard Modules
Configuration Tags
Table 81 describes the 5069-OB8 module configuration tags.
Input Tags
Table 82 describes the 5069-OB8 module input tags.
Table 82 - 5069-OB8 Module Input Tags
Name Size Definition Valid Values
• 0 = Idle
RunMode BOOL Channel’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 power-up.
(-1) to 1 skipping zero.
• 0 = Off
Ptxx.Data BOOL Indicates the current input value.
• 1 = On
• 0 = Good data
Indicates that channel data is inaccurate and cannot be • 1 = Bad data (Faulted)
trusted for use in the application. If the tag is set to 1, you must troubleshoot the
Ptxx.Fault BOOL on module to correct the cause of the inaccuracy.
For more information, see Module Data Quality Reporting
page 67. 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 channel 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 67. 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 channels. • 1 = Fault
• 0 = No short circuit
Ptxx.ShortCircuit BOOL Indicates an output short circuit or overcurrent.
• 1 = Short circuit or overcurrent
Output Tags
Table 83 describes the 5069-OB8 module output tags.
Table 83 - 5069-OB8 Module Output Tags
Name Size Definition Valid Values
• 0 = Off
Ptxx.Data BOOL Indicates the current output value.
• 1 = On
5069-OB16 Module Tags This section describes the tags that are associated with the 5069-OB16 module.
You use the 5069-IB16 module profile in your Logix Designer application
Standard Modules project with the 5069-IB16K module.
Configuration Tags
Table 84 describes the 5069-OB16 module configuration tags.
Input Tags
Table 85 describes the 5069-OB16 module input tags.
Table 85 - 5069-OB16 Module Input Tags
Name Size Definition Valid Values
• 0 = Idle
RunMode BOOL Channel’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 its 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 power-up.
(-1) to 1 skipping zero.
• 0 = Off
Ptxx.Data BOOL Indicates the current input value.
• 1 = On
• 0 = Good data
Indicates that channel data is inaccurate and cannot be • 1 = Bad data (Faulted)
trusted 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 67. 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 channel 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 67. 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 channels. • 1 = Fault
• 0 = No short circuit
Ptxx.ShortCircuit BOOL Indicates an output short circuit or overcurrent.
• 1 = Short circuit or overcurrent
Output Tags
Table 86 describes the 5069-OB16 module output tags.
Table 86 - 5069-OB16 Module Output Tags
Name Size Definition Valid Values
• 0 = Off
Ptxx.Data BOOL Indicates the current output value.
• 1 = On
5069-OB16F Module Tags This section describes the tags that are associated with the 5069-OB16F
modules.
Standard Modules
Configuration Tags
Table 87 describes the 5069-OB16F module configuration tags.
Input Tags
Table 88 describes the 5069-OB16F module input tags.
Table 88 - 5069-OB16F Module Input Tags
Name Size Definition Valid Values
• 0 = Idle
RunMode BOOL Channel’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
DiagnosticActive BOOL Indicates if any diagnostics are active or if the prognostics threshold is reached. • 1 = One or more diagnostics are active or the
prognostics threshold is reached
Indicates if the module is operating outside its designed operating range of if data • 0 = Good
Uncertain BOOL is under manual or override control. • 1 = Uncertain
Increments for each time a distinct diagnostic condition is detected, and when a -128…+127
DiagnosticSequenceCount SINT distinct diagnostic condition transitions 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 (-1) to 1 skipping zero. power-up.
• 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 master, but is not now due • 1 = A valid time master was detected on the
CIPSyncTimeout BOOL backplane, but the time master has timed out. The
to a timeout.
module is using its local clock and can be drifting
away from the last known time master.
• 0 = Off
Ptxx.Data BOOL Current input value.
• 1 = On
• 0 = Good data
• 1 = Bad data (Faulted)
Indicates that channel data is inaccurate and cannot be trusted for use in the If the tag is set to 1, you must troubleshoot the
Ptxx.Fault BOOL application. module to correct the cause of the inaccuracy.
For more information, see Module Data Quality Reporting on page 67. 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 channel data can be inaccurate but the degree of inaccuracy If the tag is set to 1, you must troubleshoot the
Ptxx.Uncertain BOOL is not known. module to correct the cause of the inaccuracy.
For more information, see Module Data Quality Reporting on page 67. 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 one of its terminals or • 0 = No fault
Ptxx.NoLoad BOOL the RTB has been removed. Used with Output channels. • 1 = Fault
• 0 = No short circuit
Ptxx.ShortCircuit BOOL Indicates an output short circuit or overcurrent.
• 1 = Short circuit or overcurrent
• 1…32 = Valid schedule
Schedulex SINT Indicates which schedule to load from 32 available schedules.
• 0, 129…255 = No schedule
Output Tags
Table 89 describes the 5069-OB16F module output tags.
Table 89 - 5069-OB16F Module Output Tags
Name Size Definition Valid Values
Indicates the TimeBase for all schedule times in a scheduled
output consumed assembly or channel. The TimeBase + The
TimeBase LINT Schedule[n].TimeOffset determines the time for the Any positive value.
schedule. Base/Offset scheme that is used to fit enough
schedules into the assembly.
• 0 = Off
Ptxx.Data BOOL Current 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 to
Schedulex.SequenceNumber SINT All values.
process this schedule.
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.
5069-OW4I, 5069-OW16, and This section describes the tags that are associated with the 5069-OW4I,
5069-OX4I Module Tags 5069-OW16, and 5069-OX4I modules. The tags are the same for each module.
Standard Modules
Configuration Tags
Table 90 describes the 5069-OW4I and 5069-OX4I module configuration tags.
Input Tags
Table 91 describes the 5069-OW4I, 5069-OW16, 5069-OX4I module input tags.
Table 91 - Relay Output High Current Module Input Tags
Name Size Definition Valid Values
• 0 = Idle
RunMode BOOL Channel’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 power-up.
(-1) to 1 skipping zero.
• 0 = Off
Ptxx.Data BOOL Current input value.
• 1 = On
• 0 = Good data
Indicates that channel data is inaccurate and cannot be • 1 = Bad data (Faulted)
trusted for use in the application. If the tag is set to 1, you must troubleshoot the
Ptxx.Fault BOOL on module to correct the cause of the inaccuracy.
For more information, see Module Data Quality Reporting
page 67. 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 channel 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 67. IMPORTANT: Once the condition that causes the
tag to change to 1 is removed, the tag
automatically resets to 0.
Output Tags
Table 92 describes the 5069-OW4I, 5069-OW16, and 5069-OX4I module outputs
tags.
Table 92 - Relay Output High Current Module Output Tags
Name Size Definition Valid Values
• 0 = Off
Ptxx.Data BOOL Current input value.
• 1 = On
5069-IB8S and 5069-IB8SK This section describes the tags that are associated with the 5069-IB8S or
Module Tags 5069-IB8SK module.
Safety Modules
Input Tags
Table 93 describes the 5069-IB8S or 5069-IB8SK module input tags.
Output Tags
Table 94 describes the 5069-IB8S or 5069-IB8SK module output tags.
Table 94 - 5069-IB8S or 5069-IB8SK Module Output Tags
Name Size Definition Valid Values
• 0 = Off
Mutingxx.Data BOOL Indicates the current muting value
• 1 = On
5069-OBV8S and This section describes the tags that are associated with the 5069-OBV8S or
5069-OBV8SK Module Tags 5069-OBV8SK module.
Safety Modules
Input Tags
Table 95 describes the 5069-OBV8S and 5069-OBV8SK module input tags.
Output Tags
Table 96 describes the 5069-OBV8S and 5069-OBV8SK module output tags.
Table 96 - 5069-OBV8S and 5069-OBV8SK Module Output Tags
Name Size Definition Valid Values
• 0 = Off
Ptxx.Data BOOL Indicates the current output value.
• 1 = On
Topic Page
Before You Begin 253
Connection Details 254
5069-IB8S or 5069-IB8SK Module Wiring Diagrams 256
5069-OBV8S and 5069-OBV8SK Module Wiring Diagrams 259
Wiring Faults on Safety Modules 266
This appendix provides example wiring diagrams for the Compact 5000™ I/O
safety modules that can be used in functional safety applications.
IMPORTANT This section shows example wiring diagrams on the 5069-IB8S safety
input module and the 5069-OBV8S safety output module.
The same diagrams also apply when you use the 5069-IB8SK safety
input module and the 5069-OBV8SK safety output module, respectively.
Before You Begin Before you wire your module, remember the following:
A system can have multiple SA power buses. You use 5069-FPD field potential
distributors to establish a new SA power bus. SA power buses are isolated from
each other.
The SA power to adjacent SA Power electrical isolation that the 5069-FPD field
potential distributor provides has a rating of 240V AC (continuous) reinforced
insulation type.
Connection Details Table 97 shows the input device connection methods and their respective
safety categories.
IMPORTANT You must use an SELV/PELV-listed power supply with the safety modules.
Test Output x
Safety Input x
Connect devices between the safety
inputs and a test output. Safety Input x
The test output must be connected to a
24V DC power supply.
No 3
Test Output x
Emergency stop button
Door monitoring switch
Safety Input x
Test Output x
Test Output x
5069-IB8S or 5069-IB8SK When the module is wired as shown, it is suitable for applications that are
Module Wiring Diagrams rated up to, and including, Category 3 as defined in ISO 13849-1.
Important:
• The switches are suitable for applications that are rated
up to, and including, SIL CL 3, PLe, Cat. 3.
• The light curtain is suitable for applications that are
rated up to, and including, SIL CL 3, PLe, Cat. 4.
Channel Connections
The diagram shows devices that are connected to safety
input channels 0, 1, 6, and 7. You are not restricted to using
only those channels.
You can connect devices to any safety input channel or
combination of channels as needed.
Safety Input 0
Safety Input 1
SA Power
Connections to an external power supply that provides SA Safety Input 2
power via the SA Power RTB on one of the following: Safety Input 3
• Compact GuardLogix® 5380 controller
• 5069-AENTR or 5069-AEN2TR EtherNet/IP™ Adapter Safety Input 4
• 5069-FPD field potential distributor
Safety Input 5
IMPORTANT: Remember the following:
• The 5069-IB8S and 5069-IB8SK modules use DC SA + OSSD1 Safety Input 6
power. You must connect DC power to the component, 24V DC SELV/PELV- Light
that is, controller, adapter, or field potential distributor, listed power supply Curtain OSSD2 Safety Input 7
that provides SA Power to the modules. –
Test Output 0
• If you install modules in a system that use AC SA power
and DC SA power, you must install them on separate SA Test Output 0
power buses.
Test Output 1
• You use a 5069-FPD field potential distributor to
establish a new SA Power bus in a system. SA Power Test Output 1
buses are isolated from each other. To keep the
Test Output/Muting Output 2
modules on separate SA Power buses, complete the
following steps. Test Output/Muting Output 2
1.Install the modules that use one type of SA power, for
example DC, to the right of the adapter or controller, Test Output/Muting Output 3
that is, the first SA Power bus. Test Output/Muting Output 3
2. Install the 5069-FPD field potential distributor to
establish a second SA Power bus. COM
3. Install the modules that use the other type of SA COM
power, for example AC, on the second SA Power bus.
• The SA Power to adjacent SA Power electrical isolation
that the 5069-FPD field potential distributor provides has
a rating of 240V AC (continuous) reinforced insulation
type.
When the module is wired as shown, and the requirements listed are met in
the project of the safety controller, it is suitable for applications that are rated
up to, and including, Category 4 as defined in ISO 13849-1. To achieve that
suitability rating, you may have to perform diagnostic testing and monitoring
of the safety function.
One diagnostic test method is to configure the safety input channel for Safety
Pulse Test to test the circuit for short circuits to 24V DC. Safety input pairs
must be associated with different Test Output sources.
Channel Connections
The diagram shows devices that are connected to safety
input channels 0 and 1, and to test outputs 0 and 1.
You are not restricted to using only those safety input
channels.
You can connect devices to any channel or combination of
channels as needed.
SA Power
Connections to an external power supply that provides SA
power via the SA Power RTB on one of the following:
• Compact GuardLogix 5380 controller Safety Input 0
• 5069-AENTR or 5069-AEN2TR EtherNet/IP Adapter
• 5069-FPD field potential distributor Safety Input 1
IMPORTANT: Remember the following:
Safety Input 2
• The 5069-IB8S and 5069-IB8SK modules use DC SA
power. You must connect DC power to the component, Safety Input 3
that is, controller, adapter, or field potential distributor,
Safety Input 4
that provides SA Power to the modules.
• If you install modules in a system that use AC SA power Safety Input 5
and DC SA power, you must install them on separate SA
power buses. Safety Input 6
• You use a 5069-FPD field potential distributor to Safety Input 7
establish a new SA Power bus in a system. SA Power
buses are isolated from each other. To keep the Test Output 0
modules on separate SA Power buses, complete the
Test Output 0
following steps.
1.Install the modules that use one type of SA power, for Test Output 1
example DC, to the right of the adapter or controller,
Test Output 1
that is, the first SA Power bus.
2. Install the 5069-FPD field potential distributor to Test Output/Muting Output 2
establish a second SA Power bus.
3. Install the modules that use the other type of SA Test Output/Muting Output 2
power, for example AC, on the second SA Power bus. Test Output/Muting Output 3
Test Output/Muting Output 3
Muting
Lamp COM
IMPORTANT: When the power supply and muting lamp are COM
configured for a test output, you must connect the return
wire on the device to a COM point on the module.
When the module is wired as shown, and the requirements listed are met in
the project of the safety controller, it is suitable for applications that are rated
up to, and including, Category 3 as defined in ISO 13849-1.
To achieve that suitability rating, you must meet the following requirements:
• Fault Exclusion is External Wiring fault.
• Use a SIL CL 3, PLd, Cat. 3 qualified sensor.
• One of the following configuration combinations:
– Input Point Mode = Safety Pulse Test
– Test Output Mode = Pulse Test
– Input Point Mode = Safety
– Test Output Mode = Power Supply
Channel Connections
The diagram shows devices that are connected to safety
input channel 0 and test output channel 0. You are not
restricted to using only those channels.
You can connect devices to any safety input channel or
combination of channels as needed.
We recommend that you connect even-numbered input
points to even-numbered test output points and odd-
numbered input points to odd-numbered test output points.
This wiring practice can maximize diagnostic independence
and separation. SIL CL 3, PLd, Cat. 3 qualified sensor
5069-OBV8S and You can use the safety output modules in Bipolar mode or Sourcing mode.
5069-OBV8SK Module
Wiring Diagrams Bipolar Mode
When the module is wired as shown, and the requirements listed are met in
the project of the safety controller, it is suitable for applications that are rated
up to, and including, Category 4 as defined in ISO 13849-1.
To achieve that suitability rating, you may have to perform diagnostic testing
and monitoring of the safety function. One diagnostic test method is to
configure the safety output channel for Safety Pulse Test to test the circuit for
short circuits to 24V DC.
• We strongly recommend that you connect separate shielded cables to the
P terminal and the N terminal to reduce the possibility of a wire short
between the terminals. If a wire-short fault is detected across the PN
pair, the module outputs are turned off, but the actuator that is
connected to it remains on.
• Configure the application so that No Load and Overload conditions are
only detectable at the P terminal.
For Cat.4 applications, if your application remains in safe state, that is, the
output is off, for a prolonged duration, we recommend that you take one of the
following actions:
• Apply output monitoring at the actuator. The monitoring can be direct or
indirect.
• Limit the safe state to no more than 24 hours.
• Conduct functional test if safe state dwell time increases.
Actuator LA Power
In this wiring configuration, you must connect the LA+ terminal to an
SELV/PELV-listed power supply.
The LA+ and LA- on the actuator must be connected to the same power
supply as the LA+ and LA- on the module.
Connection Pairs
The terminals for each channel function as a Bipolar connection pair when
LA +
you use a 5069-OBV8S or 5069-OB8VSK module in Bipolar switching mode.
For example, the Safety Output 0 P (Sourcing) terminal and Safety Output
0 N (Sinking) terminal are a Bipolar connection pair. That is, they are a PN
pair. K1
When the module is in Bipolar switching mode, you must connect the Safety Output 0 P (Sourcing)
device to both terminals.
Safety Output 0 N (Sinking)
Channel Connections K2 Safety Output 1 P (Sourcing)
This wiring example shows connections to the PN pair for Safety Output 0.
You are not limited to using channel 0 in this mode. You can use all Safety Output 1 N (Sinking)
channel pairs as determined by your application. Safety Output 2 P (Sourcing)
LA –
M Safety Output 2 N (Sinking)
LA Power
The Local Actuator (LA+ and LA –) power connections are used to supply Safety Output 3 P (Sourcing)
field-side power to the module.
Safety Output 3 N (Sinking)
• The 5069-OBV8S and 5069-OBV8SK modules do not draw current
from the SA Power bus. Safety Output 4 P (Sourcing)
Still, the modules are DC-type modules and you must install them on a
Safety Output 4 N (Sinking)
DC SA Power bus.
• If you install modules in a system that use AC SA power and DC SA Safety Output 5 P (Sourcing)
power, you must install them on separate SA power buses.
Safety Output 5 N (Sinking)
• You use a 5069-FPD field potential distributor to establish a new SA
Power bus in a system. SA Power buses are isolated from each other. Safety Output 6 P (Sourcing)
To keep the modules on separate SA Power buses, complete the
Safety Output 6 N (Sinking)
following steps.
1.Install the modules that use one type of SA power, for example DC, to Safety Output 7 P (Sourcing)
the right of the adapter or controller, that is, the first SA Power bus.
Safety Output 7 N (Sinking)
2. Install the 5069-FPD field potential distributor to establish a second
SA Power bus. 24V DC + LA +
3. Install the modules that use the other type of SA power, for SELV/PELV-listed
– LA –
example AC, on the second SA Power bus. power supply
• We strongly recommend that, if you have a direct connection
between the safety output module and an input module and those
modules are powered by separate power supplies, that you connect
SA- and LA- together. This practice helps to reduce the risk of
grounding float from disrupting diagnostics.
When the module is wired as shown, and the requirements listed are met in
the project of the safety controller, it is suitable for applications that are rated
up to, and including, Category 4 as defined in ISO 13849-1.
To achieve that suitability rating, you may have to perform diagnostic testing
and monitoring of the safety function. One diagnostic test method is to
configure the safety output channel for Safety Pulse Test to test the circuit for
short circuits to 24V DC. Configure the application so that a No Load fault can
only be detected if the wires from both the P- terminal and the N- terminal are
disconnected.
For Cat.4 applications, if your application remains in safe state, that is, the
output is off, for a prolonged duration, we recommend that you take one of the
following actions:
• Apply output monitoring at the actuator. The monitoring can be direct or
indirect.
• Limit the safe state to no more than 24 hours.
• Conduct functional test if safe state dwell time increases.
Connection Pairs
The terminals for each channel function as a Bipolar connection pair
when you use a 5069-OBV8S or 5069-OB8VSK module in Bipolar switching
mode. For example, the Safety Output 0 P (Sourcing) terminal and Safety
Output 0 N (Sinking) terminal are a Bipolar connection pair. That is, they
are a PN pair.
When the module is in Bipolar switching mode, you must connect the
device to both terminals.
Channel Connections
This wiring example shows connections to the PN pair for Safety Output 0.
You are not limited to using channel 0 in this mode. You can use all K1
channel pairs as determined by your application. Safety Output 0 P (Sourcing)
Safety Output 0 N (Sinking)
LA Power
The Local Actuator (LA+ and LA –) power connections are used to supply K2 Safety Output 1 P (Sourcing)
field-side power to the module. Safety Output 1 N (Sinking)
• The 5069-OBV8S and 5069-OBV8SK modules do not draw current
from the SA Power bus. Safety Output 2 P (Sourcing)
Still, the modules are DC type modules, and you must install them on a M Safety Output 2 N (Sinking)
DC SA Power bus.
• If you install modules in a system that use AC SA power and DC SA Safety Output 3 P (Sourcing)
power, you must install them on separate SA power buses. Safety Output 3 N (Sinking)
• You use a 5069-FPD field potential distributor to establish a new SA
Power bus in a system. SA Power buses are isolated from each other. Safety Output 4 P (Sourcing)
To keep the modules on separate SA Power buses, complete the Safety Output 4 N (Sinking)
following steps.
Safety Output 5 P (Sourcing)
1.Install the modules that use one type of SA power, for example DC, to
the right of the adapter or controller, that is, the first SA Power bus. Safety Output 5 N (Sinking)
2. Install the 5069-FPD field potential distributor to establish a second
Safety Output 6 P (Sourcing)
SA Power bus.
3. Install the modules that use the other type of SA power, for Safety Output 6 N (Sinking)
example AC, on the second SA Power bus. Safety Output 7 P (Sourcing)
• We strongly recommend that, if you have a direct connection
between the safety output module and an input module and those Safety Output 7 N (Sinking)
modules are powered by separate power supplies, that you connect 24V DC + LA +
SA- and LA- together. This practice helps to reduce the risk of SELV/PELV-listed
– LA –
grounding float from disrupting diagnostics. power supply
When the module is wired as shown, and the requirements listed are met in
the project of the safety controller, it is suitable for applications that are rated
up to, and including, Category 4 as defined in ISO 13849-1. To achieve that
suitability rating, you may have to perform diagnostic testing and monitoring
of the safety function. One diagnostic test method is to configure the safety
output channel for Safety Pulse Test to test the circuit for short circuits to
24V DC.
For Cat.4 applications, if your application remains in safe state, that is, the
output is off, for a prolonged duration, we recommend that you take one of the
following actions:
• Apply output monitoring at the actuator. The monitoring can be direct or
indirect.
• Limit the safe state to no more than 24 hours.
• Conduct functional test if safe state dwell time increases.
• A qualified actuator must be installed, for example, in accordance with
IEC 60947.
Connection Pairs
The terminals for each channel function as a Bipolar connection pair when you
use a 5069-OBV8S or 5069-OB8VSK module in Bipolar switching mode. For
example, the Safety Output 0 P (Sourcing) terminal and Safety Output 0 N
(Sinking) terminal are a Bipolar connection pair. That is, they are a PN pair.
When the module is in Bipolar switching mode, you must connect the device to
both terminals.
Channel Connections
This wiring example shows connections to the PN pair for Safety Output 0. You
are not limited to using channel 0 in this mode. You can use all channel pairs Cat. 4 Actuator
as determined by your application. Subsystem
Safety Output 0 P (Sourcing)
LA Power Safety Output 0 N (Sinking)
The Local Actuator (LA+ and LA –) power connections are used to supply
field-side power to the module. Safety Output 1 P (Sourcing)
• The 5069-OBV8S and 5069-OBV8SK modules do not draw current from Safety Output 1 N (Sinking)
the SA Power bus.
Still, the modules are DC type modules, and you must install them on a DC Safety Output 2 P (Sourcing)
SA Power bus Safety Output 2 N (Sinking)
• If you install modules in a system that use AC SA power and DC SA power,
you must install them on separate SA power buses. Safety Output 3 P (Sourcing)
• You use a 5069-FPD field potential distributor to establish a new SA Power Safety Output 3 N (Sinking)
bus in a system. SA Power buses are isolated from each other. To keep the
Safety Output 4 P (Sourcing)
modules on separate SA Power buses, complete the following steps.
1.Install the modules that use one type of SA power, for example DC, to the Safety Output 4 N (Sinking)
right of the adapter or controller, that is, the first SA Power bus.
Safety Output 5 P (Sourcing)
2. Install the 5069-FPD field potential distributor to establish a second SA
Power bus. Safety Output 5 N (Sinking)
3. Install the modules that use the other type of SA power, for example AC,
Safety Output 6 P (Sourcing)
on the second SA Power bus.
• We strongly recommend that if, you have a direct connection between Safety Output 6 N (Sinking)
the safety output module and an input module and those modules are
Safety Output 7 P (Sourcing)
powered by separate power supplies, that you connect SA- and LA-
together. This practice helps to reduce the risk of grounding float from Safety Output 7 N (Sinking)
disrupting diagnostics. 24V DC + LA +
• The SA Power to adjacent SA Power electrical isolation that the 5069-FPD SELV/PELV-listed
field potential distributor provides has a rating of 240V AC (continuous) LA –
power supply –
reinforced insulation type.
Sourcing Mode
When the module is wired as shown, it is suitable for applications that are
rated up to, and including, Category 2 as defined in ISO 13849-1.
To achieve that suitability rating, you may have to perform diagnostic testing
and monitoring of the safety function. One diagnostic test method is to
configure the safety output channel for Safety Pulse Test to test the circuit for
short circuits to 24V DC.
Channel Connections
This wiring example shows connection to Safety Output 0. You
are not limited to using channel 0 in this mode. You can use all
channels as determined by your application.
LA Power
The Local Actuator (LA+ and LA –) power connections are used
to supply field-side power to the module. Safety Output 0 P (Sourcing)
• The 5069-OBV8S and 5069-OBV8SK modules do not draw K
Safety Output 0 N (Sinking)
current from the SA Power bus.
Still, the modules are DC type modules, and you must install Safety Output 1 P (Sourcing)
them on a DC SA Power bus
Safety Output 1 N (Sinking)
• If you install modules in a system that use AC SA power and
DC SA power, you must install them on separate SA power Safety Output 2 P (Sourcing)
M
buses. LA – Safety Output 2 N (Sinking)
• You use a 5069-FPD field potential distributor to establish a
new SA Power bus in a system. SA Power buses are Safety Output 3 P (Sourcing)
isolated from each other. To keep the modules on separate Safety Output 3 N (Sinking)
SA Power buses, complete the following steps.
1.Install the modules that use one type of SA power, for Safety Output 4 P (Sourcing)
example DC, to the right of the adapter or controller, Safety Output 4 N (Sinking)
that is, the first SA Power bus.
2. Install the 5069-FPD field potential distributor to Safety Output 5 P (Sourcing)
establish a second SA Power bus. Safety Output 5 N (Sinking)
3. Install the modules that use the other type of SA power,
for example AC, on the second SA Power bus. Safety Output 6 P (Sourcing)
• We strongly recommend that, if you have a direct Safety Output 6 N (Sinking)
connection between the safety output module and an input
module and those modules are powered by separate Safety Output 7 P (Sourcing)
power supplies, that you connect SA- and LA- together. Safety Output 7 N (Sinking)
This practice helps to reduce the risk of grounding float
24V DC + LA +
from disrupting diagnostics.
SELV/PELV-listed
power supply – LA –
When the module is wired as shown, it is suitable for applications that are
rated up to, and including, Category 4 as defined in ISO 13849-1.
To achieve that suitability rating, you may have to perform diagnostic testing
and monitoring of the safety function. One diagnostic test method is to
configure the safety output channel for Safety Pulse Test to test the circuit for
short circuits to 24V DC.
For Cat.4 applications, if your application remains in safe state, that is, the
output is off, for a prolonged duration, we recommend that you take one of
these actions:
• Apply output monitoring at the actuator. The monitoring can be direct or
indirect.
• Limit the safe state to no more than 24 hours.
• Conduct functional test if safe state dwell time increases.
Connection Pairs
When you use dual-channel sourcing wiring on the 5069-OBV8S or
5069-OBV8SK module, you must connect the devices to dual-channel
connection pairs. For example, the devices are connected to channels
4 and 5 because they are a connection pair. The following channels
are dual-channel connection pairs:
• Channels 0 and 1 (shown)
• Channels 2 and 3
• Channels 4 and 5
• Channels 6 and 7
Channel Connections
This wiring example shows connections to Safety Output 0 P and
Safety Output 1P. You are not limited to using channels 0 and 1 in this K1
mode. You can use all channel pairs as determined by your
Safety Output 0 P (Sourcing)
application.
Safety Output 0 N (Sinking)
LA Power Safety Output 1 P (Sourcing)
The Local Actuator (LA+ and LA –) power connections are used to K2
supply field-side power to the module. Safety Output 1 N (Sinking)
• The 5069-OBV8S and 5069-OBV8SK modules do not draw current Safety Output 2 P (Sourcing)
from the SA Power bus.
Still, the modules are DC-type modules and you must install them on Safety Output 2 N (Sinking)
a DC SA Power bus. M Safety Output 3 P (Sourcing)
• If you install modules in a system that use AC SA power and DC SA
Safety Output 3 N (Sinking)
power, you must install them on separate SA power buses. LA –
• You use a 5069-FPD field potential distributor to establish a new SA Safety Output 4 P (Sourcing)
Power bus in a system. SA Power buses are isolated from each
Safety Output 4 N (Sinking)
other. To keep the modules on separate SA Power buses, complete
the following steps. Safety Output 5 P (Sourcing)
1.Install the modules that use one type of SA power, for example DC,
Safety Output 5 N (Sinking)
to the right of the adapter or controller, that is, the first SA
Power bus. Safety Output 6 P (Sourcing)
2. Install the 5069-FPD field potential distributor to establish a
Safety Output 6 N (Sinking)
second SA Power bus.
3. Install the modules that use the other type of SA power, for Safety Output 7 P (Sourcing)
example AC, on the second SA Power bus.
Safety Output 7 N (Sinking)
• We strongly recommend that, if you have a direct connection
between the safety output module and an input module and those 24V DC + LA +
modules are powered by separate power supplies, that you connect SELV/PELV-listed
– LA –
SA- and LA- together. This practice helps to reduce the risk of power supply
grounding float from disrupting diagnostics.
When the module is wired as shown on page 266, and the requirements listed
are met in the project of the safety controller, it is suitable for applications that
are rated up to, and including, Category 4 as defined in ISO 13849-1.
To achieve that suitability rating, you may have to perform diagnostic testing
and monitoring of the safety function. One diagnostic test method is to
configure the safety output channel for Safety Pulse Test to test the circuit for
short circuits to 24V DC.
• All power source cables must be installed separately, for example, with a
separate cable duct or shielded cable. Power source cables are connections to
the MOD+, SA+, or LA+ terminals.
Otherwise, a Short Circuit condition between SA+ and P can be detected and
the output is turned off but the actuator that is connected to it remains on.
• You must connect two ground terminals. Otherwise, the maximum residual
current at signal 0 cannot be maintained if only one ground line is connected
and it is interrupted.
For more information on residual current, see the Compact 5000 I/O Modules
and EtherNet/IP™ Adapters Technical Data, publication 5069-TD001
For Cat.4 applications, if your application remains in safe state, that is, the
output is off, for a prolonged duration, we recommend that you take one of the
following actions:
• Apply output monitoring at the actuator. The monitoring can be direct or
indirect.
• Limit the safe state to no more than 24 hours.
• Conduct functional test if safe state dwell time increases.
Channel Connections
This wiring example shows connections to Safety Output 0.
You are not limited to using channel 0 in this mode. You can
use all channels as determined by your application.
Cat. 4 Actuator
Subsystem
LA Power
The Local Actuator (LA+ and LA –) power connections are used Safety Output 0 P (Sourcing)
to supply field-side power to the module. Safety Output 0 N (Sinking)
• The 5069-OBV8S and 5069-OBV8SK modules do not draw
current from the SA Power bus. Safety Output 1 P (Sourcing)
Still, the modules are DC type modules, and you must install Safety Output 1 N (Sinking)
them on a DC SA Power bus
• If you install modules in a system that use AC SA power and Safety Output 2 P (Sourcing)
LA –
DC SA power, you must install them on separate SA power Safety Output 2 N (Sinking)
buses.
• You use a 5069-FPD field potential distributor to establish a Safety Output 3 P (Sourcing)
new SA Power bus in a system. SA Power buses are Safety Output 3 N (Sinking)
isolated from each other. To keep the modules on separate
Safety Output 4 P (Sourcing)
SA Power buses, complete the following steps.
1.Install the modules that use one type of SA power, for Safety Output 4 N (Sinking)
example DC, to the right of the adapter or controller,
Safety Output 5 P (Sourcing)
that is, the first SA Power bus.
2. Install the 5069-FPD field potential distributor to Safety Output 5 N (Sinking)
establish a second SA Power bus.
Safety Output 6 P (Sourcing)
3. Install the modules that use the other type of SA power,
for example AC, on the second SA Power bus. Safety Output 6 N (Sinking)
• We strongly recommend that, if you have a direct
Safety Output 7 P (Sourcing)
connection between the safety output module and an input
module and those modules are powered by separate Safety Output 7 N (Sinking)
power supplies, that you connect SA- and LA- together. 24V DC + LA +
This practice helps to reduce the risk of grounding float SELV/PELV-listed
from disrupting diagnostics. power supply – LA –
Wiring Faults on A number of conditions can cause wiring faults on safety modules. We
Safety Modules strongly recommend that you monitor your application to detect wiring faults
as soon as they appear so you can troubleshoot and remedy the cause of the
fault.
Topic Page
Compact 5000 I/O Safety Input Module Safety Data 268
Compact 5000 I/O Safety Output Module Safety Data 269
Calculated values of PFD and PFH appear in Table 98 on page 268 for the
5069-IB8S and 5069-IB8SK modules and Table 99 on page 269 for the
5069-OBV8S and 5069-OBV8SK modules. 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 functionally test every I/O module. To functionally test the modules,
complete the following tasks:
• Input points - Toggle every input point, and verify that the system
detects the input state change within the safety reaction time (SRT).
• Output points - Use the controller to toggle every output point, and verify
that the output point changes state.
For more information, see the GuardLogix® 5580 and Compact GuardLogix
5380 Controller Systems Safety Reference Manual (TÜV), publication
1756-RM012.
Compact 5000 I/O Safety Table 98 lists the safety data for the 5069-IB8S and 5069-IB8SK modules.
Input Module Safety Data
Table 98 - 5069-IB8S and 5069-IB8SK Module Safety Parameter Data
Point Operation Type
Attribute Dual Channel
Single Channel (at controller instruction level)
Safety Function Architecture 0 1
Safe Failure Rate (s) [failures/hr] 1.16E-06 1.49E-06
Dangerous Failure Rate (D) [failures/hr] 7.38E-07 1.04E-06
Dangerous Detected Failure Rate (DD) [failures/hr] 7.37E-07 1.04E-06
Dangerous Undetected Failure Rate (DU) [failures/hr] 3.18E-10 2.54E-10
Safety Reaction Time, SRT [millisecond] 6
Automatic Diagnostic Test Interval (TD) [hr] 4
Useful Life [yr] 20
Systematic Capability (SC) 3
Safe Failure Fraction (SFF) [%] 99.98% 99.99%
PFH 3.18E-10 2.54E-10
PFDAVE 10 yrs 1.39E-05 1.11E-05
Mission Time 20 yrs 2.78E-05 2.22E-05
Diagnostic Coverage Average (DCAVE) 99.96% 99.98%
Spurious Trip Rate (STR) 3.65E-06 4.52E-06
MTTF [years] 60.05 45.25
MTTFD [years] 154.75 110.10
Added Pulse Testing Statement
The times in the previous table are subjected to an RPI of 2 ms, Input Delay of 0 ms
and Number of Input connections of 1.
For different RPI values, extend the timing by the RPI value. For additional number of
Input connections, extend the timing by 0.14 ms for each addition.
Compact 5000 I/O Safety Table 99 lists the safety data for the 5069-OBV8S and 5069-OBV8SK modules.
Output Module Safety Data
Table 99 - 5069-OBV8S and 5069-OBV8SK Module Safety Data
Output Mode
Sourcing Bipolar
Attribute
Point Operation Type Point Operation Type
Single Dual Single
Safety Function Architecture 0 1 1
Safe Failure Rate (s) [failures/hr] 1.17E-06 9.45E-07 9.63E-07
Dangerous Failure Rate (D) [failures/hr] 9.13E-07 5.98E-07 6.25E-07
Dangerous Detected Failure Rate (DD) [failures/hr] 9.12E-07 5.97E-07 6.24E-07
Dangerous Undetected Failure Rate (DU) [failures/hr] 3.29E-10 3.15E-10 3.14E-10
Safety Reaction Time, SRT [millisecond] 4.5
Automatic Diagnostic Test Interval (TD) [hr] 4
Useful Life [yr] 20
Systematic Capability (SC) 3
Safe Failure Fraction (SFF) [%] 99.98% 99.98% 99.98%
PFH 3.29E-10 3.15E-10 3.14E-10
PFDAVE 10 yrs 1.44E-05 1.38E-05 1.38E-05
Mission Time 20 yrs 2.89E-05 2.76E-05 2.75E-05
Diagnostic Coverage Average (DCAVE) 99.96% 99.95% 99.95%
Spurious Trip Rate (STR) 3.65E-06 2.34E-06 2.45E-06
MTTF [years] 54.91 74.01 71.89
MTTFD [years] 125.07 190.99 182.70
The safety data provided in the table is with Safety Pulse Test mode.
The following table lists SRT times for the Compact 5000 I/O safety
output modules.
Module is NOT used in continuous Module is used in continuous demand
Safety Reaction Time demand mode AND the safety demand mode OR the safety demand rate is more
rate is less than once per 1 s than or equal to once per 1 s
on demand 4 ms
on fault 4.5 ms 8.3 ms
on external wiring fault 200 ms
The times in the previous table are subjected to an RPI of 2 ms and Number of Input
connections of 1.
For different RPI values, extend the timing by the RPI value. For additional number of
Input connections, extend the timing by 0.14 ms for each addition.
Create User-defined You can use the Studio 5000 Logix Designer® application to create
Diagnostic Assembly Types user-defined Diagnostic Assembly types for safety I/O modules.
IMPORTANT The members indicated in the tables are arranged according to Data
Alignment Rules of controllers. Strictly follow the Data Type and sequence of
the members that are indicated in the Tables of this Appendix. Data
misalignment after executing ‘Get Attribute Single’ Message (MSG) instruction
may occur if the Data Type and sequence are not followed.
There are total of three Diagnostic Assemblies under these catalogs that
include two different types of Diagnostic Channel. From the Controller
Organizer pane, expand Data Types and create user-defined 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
Table 100 - Diagnostic Assembly Instance 769
Name Data Type Size in Byte
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.
Diagnostic Channel
There are total of three Diagnostic Assemblies under this catalog and one
Diagnostic Channel. From the Controller Organizer pane, expand Data Types
and create user-defined 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
Table 105 - Diagnostic Assembly Instance 769
Name Data Type Size in Byte
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.
Diagnostic Channel
Create Message Type Create MESSAGE type user tags for requests and associated response user tags
User Tags for each of the new user-defined diagnostic assembly types.
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 types.
3. Add the user tags to your ladder program.
5069-OBV8S, 5069-OBV8SK:
769 (301h) Diagnostic Counters Base I/O Assembly
787 (313h) Diagnostic Digital Safety 8 Output Point Assembly A (input)
798 (31Eh) Diagnostic Digital Safety 8 Output Point Assembly B (input)
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.
Definitions for Diagnostic Table 109 describes the members inside Diagnostic Assembly Data Types:
Assembly Types
Table 109 - Definition of members in Diagnostic Assembly Data Types
Data Definition
Name Valid Values
Type
• 0 = Idle
RunMode BOOL Module’s operating state
• 1 = Run
• 0 = No diagnostics active
BOOL Indicates if any diagnostics are active or if the prognostics threshold is
DiagnosticActive • 1 = One or more diagnostics are active or the prognostics
reached.
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.
• 1 = A valid time master was detected on the backplane,
BOOL Indicates if the module was once synced with a 1588 master, but is not
CIPSyncTimeout but the time master has timed out.
now due to a timeout.
The module is using its local clock and can be drifting away
from the last known time master.
• 0 = No field power off condition
FieldPowerOff BOOL Indicates that a field power loss condition exists on the channel.
• 1 = Field power off condition
Increments for each time a distinct diagnostic condition is detected, and
when a distinct diagnostic condition transitions from detected to not 0…255
DiagnosticSequenceCount SINT detected. The value of 0 is skipped except during module
Set to zero by product reset or power cycle. Wraps from 255 (-1) to 1 power-up.
skipping zero.
LINT The offset from the local clock to the system time. This value helps to
LocalClockOffset All
detect steps in time. This value updates when a PTP update is received.
LINT Shows the timestamp of the last short circuit to ground fault. Refer to
ShortCircuitGroundTimestamp A valid time or None if there is no recorded event time.
NoLoadTimestamp for the format.
LINT Shows the timestamp of the last time field power turned on. Refer to
FieldPowerOnTimestamp A valid time or None if there is no recorded event time.
NoLoadTimestamp for the format.
LINT Shows the timestamp of the last time field power turned off. Refer to
FieldPowerOffTimestamp A valid time or None if there is no recorded event time.
NoLoadTimestamp for the format.
LINT Shows the timestamp of the last over temperature fault. Refer to
OverTemperatureTimestamp A valid time or None if there is no recorded event time.
NoLoadTimestamp for the format.
Shows the timestamp of the last critical temperature fault. Refer to
CriticalTemperatureTimestamp LINT NoLoadTimestamp A valid time or None if there is no recorded event time.
for the format.
INT Shows the number of CIP connections currently open to and through the
CIPConnections 0…32767
adapter.
Shows the running sum of the number of Sequenced Address Item
CIPLostPackets DINT Sequence Numbers that are skipped in Class 0 and Class 1 connections 0…2147483647
consumed by the adapter and its children.
DINT Shows the running count of the number of connections that time out, both
CIPTimeouts 0…2147483647
originated and targeted, to and through the adapter.
CPUUtilization INT Shows the usage of the compute engine. 0%…100%
Notes:
Numerics D
5069-AENTR, 5069-AENTRK, 5069-AEN2TR data transmission
EtherNet/IP adapters multicast method 37, 40
connect power data types 38, 41
power supply considerations 30 available with I/O modules 37, 40
5069-ARM address reserve module 29, 152 - 154 diagnostic assembly
5069-FPD field potential distributor 31 types 271
operation 31 user-defined
standard I/O modules 271
discrepancy 135 - 138
C
CIP Sync Time 72
compatibility
E
Logix 5000 controllers with Compact 5000 I/O events
digital modules 16 configuration 86
configuration event task 44
reset safety modules to out-of-box events category
configuration 198 5069-IB16F module 165 - 166
configure 5069-IB6F-3W module 171 - 172
with Logix Designer application 66
connection 14
connection category
F
5069-IA16 module 157 fast I/O module
5069-IB16, 5069-IB16K modules 157 CIP sync time 72
5069-IB16F module 157 filter times
5069-IB6F-3W module 157 digital input modules 77
5069-IB8S and 5069-IB8SK modules 190 firmware
5069-OA16 module 157 obtain from PCDC 71
5069-OB16, 5069-OB16K modules 157
5069-OB16F module 157
5069-OB8 module 157 G
5069-OBV8S and 5069-OBV8SK modules 190
5069-OW16 module 157 general category
5069-OW4I module 157 5069-IA16 module 155
5069-OX4I module 157 5069-IB16, 5069-IB16K modules 155
connection types 37, 40 5069-IB16F module 155
controller organizer 5069-IB6F-3W module 155
5069-IB8S, 5069-IB8SK modules 187
monitor tags 181, 195 5069-OA16 module 155
view module tags 181, 195 5069-OB16, 5069-OB16K modules 155
counters category 5069-OB16F 155
5069-IB16, 5069-IB16K modules 160 5069-OB8 module 155
5069-IB16F module 162 5069-OBV8S, 5069-OBV8SK modules 187
5069-IB6F-3W module 168 5069-OW16 module 155
5069-OW4I module 155
5069-OX4I module 155
I M
I/O status indicators masters 14
digital output module 206 - 207 module definition
safety input modules 210 dialog box 156
safety output modules 212 safety modules 189
standard input modules 203 - 204 module info category
standard output modules 205 - 206 5069-IA16 module 158
input filter 5069-IB16, 5069-IB16K modules 158
5069-IA16 module 77 5069-IB16F module 158
5069-IB16, 5069-IB16K modules 77 5069-IB6F-3W module 158
5069-IB16F module 77 5069-IB8S, 5069-IB8SK modules 192
5069-IB6F-3W module 77 5069-OA16 module 158
5069-IB8S, 5069-IB8SK modules 78 5069-OB16, 5069-OB16K modules 158
input filter time 159, 161, 163, 169 5069-OB16F module 158
input points category 5069-OB8 module 158
5069-IB8S, 5069-IB8SK modules 193 5069-OBV8S, 5069-OBV8SK modules 192
5069-OW16 module 158
5069-OX4I module 158
L module location
local I/O modules 21, 43, 45 local I/O modules 21
remote I/O modules 22
locking tab 20 module status indicator 202
Logix 5000 controllers module tags
compatibility with Compact 5000 I/O digital definition 219
modules 16 naming 220
ownership of Compact 5000 I/O modules 26 tag editor 221
Logix Designer application 66 view 195
configuration overview 36 viewing 181
connection types 37, 40 module types 18
module definition multicast
safety modules 189
module tag definition 219 data broadcast method 43
name module tags 220
replace a safety module 196 - 200
reserve a module slot 152 - 154 N
reset safety modules to out-of-box no load detection
configuration 198 minimum time 102, 104
safety modules configuration 183 - 200 node address
safety network number 187, 196 reserve with 5069-ARM module 29, 152 - 154
standard I/O module configuration 143
tag editor 221
view module tags 181, 195 O
ODVA 14
output state
change time 116
ownership 26
multiple owners of input modules 26
P S
PCDC SA status indicator
obtain firmware 71 5069-IB8SK, 5069-IB8SK modules 210
PFD 14 5069-OBV8S, 5069-OBV8SK modules 212
See probability of failure on demand. safety category
PFH 14 5069-IB8S, 5069-IB8SK modules 191
See probability of failure per hour. 5069-OBV8S, 5069-OBV8SK modules 191
points category safety network number 14, 187
5069-IA16 module 159 set manually 196
5069-IB16, 5069-IB16K modules 161 scheduled output data
5069-IB16F module 163 - 164 fast I/O module 72
5069-IB6F-3W module 169 - 170 short circuit protection
5069-OA16 module 174 digital output modules 106
5069-OB16, 5069-OB16K modules 176 safety input modules 93
5069-OB16F module 177 simple count mode
5069-OB8 module 175 maximum frequency 83
5069-OBV8S, 5069-OBV8SK modules 194 slaves 14
5069-OW16 module 179
5069-OW4I module 178 SNN 14
5069-OX4I module 180 See safety network number.
power supply considerations standard I/O modules
5069-AENTR, 5069-AENTRK, 5069-AEN2TR configuration 143
EtherNet/IP adapters 30 status indicators
probability of failure safety input modules 209
on demand 14 I/O status indicators 210
per hour 14 SA status indicator 210
proof test 14 safety output modules 211
pulse latching 90 I/O status indicators 212
SA status indicator 212
standard input modules 203
I/O status indicators 203
R standard output modules 205
remote I/O modules 22, 44, 47 I/O status indicators 205 - 208
replace a safety module 196 - 200
reserve node address
with 5069-ARM module 29, 152 - 154
reset safety modules to out-of-box
configuration 198
RPI
valid value 42
T
test output points category
5069-IB8S, 5069-IB8SK modules 194
thermal switch
digital output modules 113
safety input modules 95
time sync category
5069-IB16F module 167
5069-IB6F-3W module 173
time-scheduled output
accuracy 122
resolution 122
timestamping
CIP sync 72
input accuracy 84
input resolution 84
selection 163, 169
sequence of events 84
troubleshooting
connection category 215
general category 214
module Info category 215
module status indicator 20, 202
safety input modules
I/O status indicators 210
SA status indicator 210
safety output modules
I/O status indicators 212
SA status indicator 212
standard input modules
I/O status indicators 203
standard output modules
I/O status indicators 205 - 208
tag editor 218
V
voltage range
digital I/O module 18
Additional Resources
These documents contain additional information concerning related products from Rockwell Automation.
Resource Description
Compact 5000 I/O™ Field Potential Distributor Installation Instructions, publication 5069-IN001 Describes how to install and wire the 5069-FPD field potential distributor.
Compact 5000 I/O Address Reserve Module Installation Instructions, publication 5069-IN002 Describes how to install the 5069-ARM address reserve module.
Compact 5000 I/O EtherNet/IP Adapters Installation Instructions, publication 5069-IN003 Describes how to install the 5069-AENTR and 5069-AEN2TR EtherNet/IP™ adapters.
Describes how to install and wire the 5069-IB16, 5069-IB16F, and 5069-IB16K
Compact 5000 I/O Digital 16-point Sinking Input Modules Installation Instructions, publication 5069-IN004 input modules.
Compact 5000 I/O Digital 3-wire Sinking Input Module Installation Instructions, publication 5069-IN006 Describes how to install and wire the 5069-IB6F-3W input module.
Compact 5000 I/O Digital 16-point Sourcing Output Modules Installation Instructions, Describes how to install and wire the 5069-OB16, 5069-OB16F, and 5069-OB16K output
publication 5069-IN007 modules.
Compact 5000 I/O Digital 4-point Isolated Relay Output Module Installation Instructions, Describes how to install and wire the 5069-OW4I output module.
publication 5069-IN008
Compact 5000 I/O Digital 4-point Isolated Normally-open/Normally-closed Relay Output Module Installation Describes how to install and wire the 5069-OX4I output module.
Instructions, publication 5069-IN009
Compact 5000 I/O Analog 8-channel Current/Vole Input Module Installation Instructions, publication Describes how to install and wire the 5069-IF8 analog input module.
5069-IN010
Compact 5000 I/O Analog 4-channel Current/Vole/RTD/Thermocouple Input Module Installation Describes how to install and wire the 5069-IY4 and 5069-IY4K analog
Instructions, publication 5069-IN011 input modules.
Compact 5000 I/O Analog Current/Vole Output Modules Installation Instructions, publication 5069- Describes how to install and wire the 5069-OF4, 5069-OF4K, and 5069-OF8 analog
IN012 output modules.
Compact 5000 I/O Digital 16-point 120/240V AC Input Module Installation Instructions, Describes how to install and wire the 5069-IA16 input module.
publication 5069-IN015
Compact 5000 I/O Digital 16-point 120/240V AC Output Module Installation Instructions, Describes how to install and wire the 5069-OA16 output module.
publication 5069-IN016
Compact 5000 I/O Digital 8-point 24V DC Output Module Installation Instructions, publication 5069-IN017 Describes how to install and wire the 5069-OB8 output module.
Compact 5000 I/O Digital 16-point Relay Output Module Installation Instructions, publication 5069-IN018 Describes how to install and wire the 5069-OW16 output module.
Describes how to install and wire the 5069-IB8S and 5069-IB8SK safety
Compact 5000 I/O Safety Sinking Input Module Installation Instructions, publication 5069-IN020 input module.
Describes how to install and wire the 5069-OBV8S and 5069-OBV8SK safety
Compact 5000 I/O Safety Output Module Installation Instructions, publication 5069-IN021 output modules.
Compact 5000 I/O Modules and EtherNet/IP Adapters Specifications Technical Data, Provides specifications, wiring diagrams, and module block diagrams for
publication 5069-TD001 Compact 5000 I/O modules.
Describes how to configure, operate, and troubleshoot CompactLogix™ 5380 and
CompactLogix™ 5380 and Compact GuardLogix® 5380 Controllers User Manual, publication 5069-UM001 Compact GuardLogix 5380 controllers.
CompactLogix 5480 Controllers User Manual, publication 5069-UM002 Describes how to configure, operate, and troubleshoot CompactLogix 5480 controllers.
Describes how to configure, operate, and troubleshoot Compact 5000 I/O
Compact 5000 I/O Analog Modules User Manual, publication 5069-UM005 analog modules.
Compact 5000 I/O High-speed Counter Module User Manual, publication 5069-UM006 Describes how to use Compact 5000 I/O high-speed counter modules.
Compact 5000 EtherNet/IP Adapters User Manual, publication 5069-UM007 Describes how to use the 5069-AENTR and 5069-AEN2TR EtherNet/IP adapters.
Describes how to configure time-scheduled output control with the
Position-based Output Control with the MAOC Instruction, publication 1756-AT017 MAOC instruction.
Logix 5000™ Controllers Tasks, Programs, and Routines Programming Manual, publication 1756-PM005 Provides more information on event tasks and event task configuration.
Describes requirements for achieving and maintaining Safety Integrity Level (SIL) 2 and
GuardLogix and Compact GuardLogix 5380 Controller Systems Safety Reference Manual, Performance Level (PL) d requirements with the GuardLogix 5580 controller system,
publication 1756-RM012 using the Studio 5000 Logix Designer® application.
Describes how to configure, operate, and troubleshoot ControlLogix® 5580 and
ControlLogix® 5580 and GuardLogix 5580 Controllers User Manual, publication 1756-UM543 GuardLogix 5580 controllers.
The SISTEMA tool automates calculation of the attained Performance Level from the
SISTEMA Performance Level Calculator, available for download at: SISTEMA safety-related parts of a machine’s control system to (EN) ISO 13849-1.
Electronic Keying in Logix 5000 Control Systems Application Technique, publication LOGIX-AT001 Describes how to use electronic keying in Logix 5000 control system applications.
Provides information about CIP Sync™ technology and how to synchronize clocks
Integrated Architecture® and CIP Sync Configuration Application Technique, publication IA-AT003 within the Rockwell Automation® Integrated Architecture® system.
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.
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.
At the end of life, this equipment should be collected separately from any unsorted municipal waste.
Rockwell Automation maintains current product environmental compliance information on its website at rok.auto/pec.
Allen-Bradley, Compact 5000, CompactLogix, ControlLogix, GuardLogix, Integrated Architecture, Kinetix, Logix 5000, PanelView, PowerFlex, Rockwell Automation, Studio 5000 Logix Designer, and Stratix
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