Rockwell Automation Allen-Bradley ArmorBlock 5000 Series User manual

User Manual Original Instructions
ArmorBlock 5000 8-channel
IO-Link Master Module
Catalog Numbers 5032-8IOLM12DR, 5032-8IOLM12M12LDR,
5032-8IOLM12P5DR

2Rockwell Automation Publication 5032-UM001A-EN-P - April 2023
ArmorBlock 5000 8-channel IO-Link Master Module User Manual
Important User Information
Read this document and the documents listed in the additional resources section about installation, configuration, and operation of this equipment before
you install, configure, operate, or maintain this product. Users are required to familiarize themselves with installation and wiring instructions in addition to
requirements of all applicable codes, laws, and standards.
Activities including installation, adjustments, putting into service, use, assembly, disassembly, and maintenance are required to be carried out by suitably
trained personnel in accordance with applicable code of practice.
If this equipment is used in a manner not specified by the manufacturer, the protection provided by the equipment may be impaired.
In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use or application of this
equipment.
The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and requirements associated with
any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for actual use based on the examples and diagrams.
No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software described in this manual.
Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation, Inc., is prohibited.
Throughout this manual, when necessary, we use notes to make you aware of safety considerations.
These labels may also be on or inside the equipment to provide specific precautions.
The following icon may appear in the text of this document.
Rockwell Automation recognizes that some of the terms that are currently used in our industry and in this publication are not in alignment
with the movement toward inclusive language in technology. We are proactively collaborating with industry peers to find alternatives to such
terms and making changes to our products and content. Please excuse the use of such terms in our content while we implement these
changes.
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 Publication 5032-UM001A-EN-P - April 2023 3
Table of Contents
Preface
About This Publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Download Firmware, AOP, EDS, and Other Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Chapter 1
Introduction Highly Integrated IO-Link. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Controller and Software Compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Module Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Secure Access to the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Power the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Module and Device Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Module and Device Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Requested Packet Interval. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Cyclic Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Change of State Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Protected Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Chapter 2
Module Features Software Configurable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Configurable Channel Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Fault and Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Module Inhibiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Electronic Keying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Update Module Firmware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Input Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Independent Point Trigger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Pattern Match Trigger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Input Event Latching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Additional Event Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Use CIP Sync Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Protected Mode for IO-Link Master Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Enter and Exit Implicit Protected Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Enter and Exit Explicit Protected Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Restrictions Imposed By Implicit Protected Mode . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Restrictions Imposed By Explicit Protected Mode . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Perform Tasks When Restricted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Chapter 3
I/O Channel Features Software Configurable Input Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Input Timestamping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Pulse Latching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Chatter Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

4Rockwell Automation Publication 5032-UM001A-EN-P - April 2023
Table of Contents
Configure Channel Output State When Module is in Program Mode or Inhibited . . . . . 24
Configure Channel Output State in Fault Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Output Behavior Immediately After a Connection Fault. . . . . . . . . . . . . . . . . . . . . . 25
Fault Mode State Duration After Connection Fault . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Final Fault Mode State Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Short Circuit Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Group Short Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
No Load Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Fault and Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Chapter 4
Common Features of IO-Link
Device Integration
IO-Link Device Identity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
IO-Link Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
IODD-Based AOP for IO-Link Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Fallback Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
IO-Link Device Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Connection Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
IO-Link Device Inhibiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
IO-Link Device Electronic Keying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Automatic Device Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Configuration Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Data Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
IO-Link Device Parameters Classification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Device Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Device Correlation Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Get/Set IO-Link Device Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Configure IO-Link Process Data Output State When IO-Link Device is in Program Mode
or Inhibited . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Configure Process Data Output State in Fault Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
IO-Link Device Information and Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Fault and Status Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
IO-Link Device Configuration Change Notification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Execute IO-Link Commands Through Explicit Messaging . . . . . . . . . . . . . . . . . . . . . . . . 36
Protected Mode for IO-Link Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Enter and Exit Protected Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Restrictions Imposed By Protected Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
IO-Link Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Chapter 5
Configure the IO-Link Master
Module
Configure the Module IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Set the Network Address Switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Use the BOOTP/DHCP Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Add the Module to a Studio 5000 Logix Designer Application Project . . . . . . . . . . . . . . 40
Discover Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
New Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Edit the Module Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
General View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Connection View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Module Info View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Rockwell Automation Publication 5032-UM001A-EN-P - April 2023 5
Table of Contents
Channels View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Input Events View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Internet Protocol View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Port Configuration View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Network View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Time Sync View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Servers View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Switch Channel Mode from IO-Link or Fallback to Digital Output . . . . . . . . . . . . . . . . . . 60
Reset Module to Factory Default. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Chapter 6
Configure the IO-Link Device Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Register IO-Link Device IODD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Add IO-Link Devices to Your Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Discover Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
New Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Add a Preconfigured Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Edit the IO-Link Device Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
General View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Connection View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Device Info View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Configuration View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Parameters View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Replace IO-Link Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Prerequisite Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Replace a Device with ADC Disabled and DS Not Supported . . . . . . . . . . . . . . . . . . 74
Replace with a Used Device when ADC Disabled and DS Supported. . . . . . . . . . . . 74
Replace a Device on a Fallback Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Replace with a Used Master Module when any Device Supports DS and ADC Disabled
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Replace a Master Module and Devices with Device ADC Disabled. . . . . . . . . . . . . . 75
Adjust Device Configuration After Replacement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
After Adjusting the Device Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Clone/Duplicate a Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Reset IO-Link Device to Factory Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Appendix A
Troubleshoot Your IO-Link
Master Module
Module Status Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Network Status Indicator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Link Status Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Power Status Indicator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Channel Status Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Troubleshoot Wiring Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Use the Studio 5000 Logix Designer Application for Troubleshooting. . . . . . . . . . . . . . 82
Warning Signal in the I/O Configuration Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Status and Fault Information in Module Properties . . . . . . . . . . . . . . . . . . . . . . . . . 82
Diagnostics in Studio 5000 Logix Designer Application. . . . . . . . . . . . . . . . . . . . . . 84
Studio 5000 Logix Designer Application Tag Editor . . . . . . . . . . . . . . . . . . . . . . . . . 86
Module Diagnostic Webpages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

6Rockwell Automation Publication 5032-UM001A-EN-P - April 2023
Table of Contents
Appendix B
Troubleshoot Your IO-Link
Device
Use the Studio 5000 Logix Designer Application for Troubleshooting. . . . . . . . . . . . . . 89
Warning Signal in the I/O Configuration Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Status and Fault Information in Module Properties . . . . . . . . . . . . . . . . . . . . . . . . . 90
General Troubleshooting Tips for Configuration and Connection Issues . . . . . . . 92
Studio 5000 Logix Designer Application Tag Editor . . . . . . . . . . . . . . . . . . . . . . . . . 94
IO-Link Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Use CIP Messages to Retrieve the IO-Link Event Log . . . . . . . . . . . . . . . . . . . . . . . . 96
Appendix C
IO-Link Master Module and IO-
Link Device Tag Definitions
Tag Name Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Access the Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
IO-Link Master Module Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Configuration Tags for IO-Link Master Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Input Tags for IO-Link Master Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Output Tags for IO-Link Master Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Event Input Tags for IO-Link Master Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Event Output Tags for IO-Link Master Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Status Tags for IO-Link Master Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
IO-Link Device Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Configuration Tags for IO-Link Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Input Tags for IO-Link Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Output Tags for IO-Link Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Appendix D
Module Diagnostic Assembly Create User-defined Diagnostic Assembly Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Diagnostic Assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Diagnostic Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Create Message Type User Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Appendix E
IO-Link Connectivity Example Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Index
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Rockwell Automation Publication 5032-UM001A-EN-P - April 2023 7
Preface
About This Publication This manual describes how to configure and troubleshoot your ArmorBlock 5000™ 8-channel
IO-Link master module.
Download Firmware, AOP,
EDS, and Other Files
Download firmware, associated files (such as AOP, EDS, and IODD), and access product release
notes from the Product Compatibility and Download Center at rok.auto/pcdc.
Additional Resources These documents contain additional information concerning related products from Rockwell
Automation. You can view or download publications at rok.auto/literature.
Resource Description
ArmorBlock 5000 I/O Modules Technical Data, publication 5032-TD001 Provides specifications for ArmorBlock 5000 I/O modules and accessories.
ArmorBlock 5000 8-channel IO-Link Master Module Installation Instructions,
publication 5032-IN001 Describes how to install and wire the ArmorBlock 5000 8-channel IO-Link master modules.
EtherNet/IP Network Devices User Manual, publication ENET-UM006 Describes how to configure and use EtherNet/IP™ devices to communicate on the
EtherNet/IP network.
Ethernet Reference Manual, publication ENET-RM002 Describes basic Ethernet concepts, infrastructure components, and infrastructure features.
System Security Design Guidelines Reference Manual,
publication SECURE-RM001
Provides guidance on how to conduct security assessments, implement Rockwell
Automation products in a secure system, harden the control system, manage user access,
and dispose of equipment.
UL Standards Listing for Industrial Control Products,
publication CMPNTS-SR002
Assists original equipment manufacturers (OEMs) with construction of panels, to help ensure
that they conform to the requirements of Underwriters Laboratories.
Safety Guidelines for the Application, Installation, and Maintenance of
Solid-state Control, publication SGI-1.1
Designed to harmonize with NEMA Standards Publication No. ICS 1.1-1987 and provides
general guidelines for the application, installation, and maintenance of solid-state control in
the form of individual devices or packaged assemblies incorporating solid-state
components.
Industrial Automation Wiring and Grounding Guidelines, publication 1770-4.1 Provides general guidelines for installing a Rockwell Automation industrial system.
Product Certifications website, rok.auto/certifications Provides declarations of conformity, certificates, and other certification details.

8Rockwell Automation Publication 5032-UM001A-EN-P - April 2023
Preface
Notes:

Rockwell Automation Publication 5032-UM001A-EN-P - April 2023 9
Chapter 1
Introduction
The ArmorBlock 5000 8-channel IO-Link master module provides 16 channels that can be
configured for IO-Link, digital input, and digital output. The module supports up to 8 channels
for IO-Link master communication with IO-Link compatible devices. In standard digital I/O
mode, the module supports up to 12 channels of digital inputs and up to 16 channels of digital
outputs. Standard digital input channels support IEC 61131-2 type 3 input. Channels can also be
disabled if not in use.
The module provides isolated power for Class B IO-Link devices and provides diagnostics for
module and individual channels. The module also supports CIP Sync™ with time stamps for
input events and faults.
Highly Integrated IO-Link Highly integrated IO-Link is the integration of IO-Link technology into the Studio 5000® design
environment. All IO-Link devices become CIP™ nodes and are configured in the same way as
other CIP devices. For example, all registered IO-Link devices have their unique identity,
Add-on Profiles (AOP), tags, and appear in the I/O configuration tree under the IO-Link bus.
IO-Link technology is a worldwide open-standard protocol that integrates sensors and other
field devices into our Connected Enterprise® by connecting the IO-Link enabled device to an
IO-Link master module. You can use it to deliver data from smart devices directly into a
control system. The flexibility of IO-Link capable devices allows machines to operate more
effectively by providing diagnostics and data including detailed machine health status to
improve uptime and increase productivity.
The benefits of IO-Link technology include:
• A worldwide open-standard peer-to-peer serial communication protocol according to
IEC 61131-9.
• Forward/backward compatibility with standard sensors.
• Uses the same cables as standard sensors.
• Allows exchange of I/O, diagnostic, and configuration data simultaneously.
The benefits of integration into the Studio 5000 Logix Designer® application include:
• Each IO-Link device has its own independent identity and connection. You can inhibit
an individual device connection.
• Add and view IO-Link devices in the I/O configuration tree.
• Each IO-Link device has an AOP and can be configured like a CIP device.
• Supports Automatic Device Configuration (ADC) and if applicable, the Data Storage
feature.
• Named Configuration/Input/Output tags are created for each IO-Link device.
• Configure IO-Link devices in both offline and online mode.
• Import/Export configuration for individual IO-Link devices.
• Back up configuration data for IO-Link devices into a project file in both ADC and non-
ADC (Data Storage) modes.
• Provides recovery of configuration data for IO-Link devices in both ADC and non-ADC
(Data Storage) modes by restoring the device configuration that is saved in a project
file to the devices.

10 Rockwell Automation Publication 5032-UM001A-EN-P - April 2023
Chapter 1 Introduction
• Ease of commissioning by cloning the configuration data to another system with the
same physical setup.
Controller and Software
Compatibility
Controller and programming software compatibility requirements apply when you use the
ArmorBlock 5000 8-channel IO-Link master module, as described in Table 1.
For more information on the controllers, see the following publications:
• CompactLogix™ 5380 and Compact GuardLogix® 5380 Controllers User Manual,
publication 5069-UM001.
• CompactLogix 5480 Controllers User Manual, publication 5069-UM002.
• ControlLogix® 5580 and GuardLogix 5580 Controllers User Manual,
publication 1756-UM543.
Table 1 - Module Compatibility
Module Controllers Logix Designer
Application Version
FactoryTalk Linx
Software Version
System Catalog Numbers
5032-8IOLM12DR
5032-8IOLM12M12LDR
5032-8IOLM12P5DR
CompactLogix 5380
Standard and Process
controllers
5069-L306ER, 5069-L306ERM, 5069-L310ER, 5069-L310ERM,
5069-L310ERMK, 5069-L310ER-NSE, 5069-L320ER, 5069-L320ERM,
5069-L320ERMK, 5069-L320ERP, 5069-L330ER, 5069-L330ERM,
5069-L330ERMK, 5069-L340ER, 5069-L340ERM, 5069-L340ERP,
5069-L350ERM, 5069-L350ERMK, 5069-L380ERM, 5069-L3100ERM
35.00.00 or later
6.31.00 (with
patches(1))
or later
Compact GuardLogix 5380
SIL 2 controllers
5069-L306ERS2, 5069-L306ERMS2, 5069-L310ERS2, 5069-L310ERS2K,
5069-L310ERMS2, 5069-L310ERMS2K, 5069-L320ERS2,
5069-L320ERS2K, 5069-L320ERMS2, 5069-L320ERMS2K,
5069-L330ERS2, 5069-L330ERS2K, 5069-L330ERMS2,
5069-L330ERMS2K, 5069-L340ERS2, 069-L340ERMS2,
5069-L350ERS2, 5069-L350ERS2K, 5069-L350ERMS2,
5069-L350ERMS2K, 5069-L380ERS2, 5069-L380ERMS2,
5069-L3100ERS2, 5069-L3100ERMS2
Compact GuardLogix 5380
SIL 3 controllers
5069-L306ERMS3, 5069-L310ERMS3, 5069-L310ERMS3K,
5069-L320ERMS3, 5069-L320ERMS3K, 5069-L330ERMS3,
5069-L330ERMS3K, 5069-L340ERMS3, 5069-L350ERMS3,
5069-L350ERMS3K, 5069-L380ERMS3, 5069-L3100ERMS3
CompactLogix 5480
controllers
5069-L430ERMW, 5069-L450ERMW, 5069-4100ERMW,
5069-L4200ERMW, 5069-L46ERMW
ControlLogix 5580
Standard and Process
controllers
1756-L81E, 1756-L81EK, 1756-L81E-NSE, 1756-L81EXT, 1756-L81EP,
1756-L82E, 1756-L82EK, 1756-L82E-NSE, 1756-L82EXT, 1756-L83E,
1756-L83EK, 1756-L83E-NSE, 1756-L83EXT, 1756-L83EP, 1756-L84E,
1756-L84EK, 1756-L84E-NSE, 1756-L84EXT, 1756-L85E, 1756-L85EK,
1756-L85E-NSE, 1756-L85EXT, 1756-L85EP
GuardLogix 5580
controllers
1756-L81ES, 1756-L81ESK, 1756-L82ES, 1756-L82ESK, 1756-L83ES,
1756-L83ESK, 1756-L84ES, 1756-L84ESK, 1756-L8SP, 1756-L8SPK,
1756-L81EXTS, 1756-L82EXTS, 1756-L83EXTS, 1756-L84EXTS,
1756-L8XTSP
(1) You must also install the following software patches for FactoryTalk® Linx software version 6.31.00:
- Patch Roll-up for CPR9 SRx, #QA49264
- Patch: Incorrectly displays catalog name BMP 01-EL1PP21A for a BFS 26K-GI-L04-S92 device, FactoryTalk Linx 6.31, #BF29098
- Patch: FactoryTalk Linx Network Browser unexpectedly shutdown after detecting an IO-Link device with a name longer than 100 characters, FactoryTalk Linx 6.31, #BF29219
To download the patches, go to the technical support center at rok.auto/knowledgebase and sign in with your TechConnectSM account.

Rockwell Automation Publication 5032-UM001A-EN-P - April 2023 11
Chapter 1 Introduction
Module Overview Figure 1 shows the parts of an ArmorBlock 5000 8-channel IO-Link master module.
Figure 1 - ArmorBlock 5000 8-channel IO-Link Master Module Overview
5032-8IOLM12DR 5032-8IOLM12P5DR 5032-8IOLM12M12LDR
4-pin mini power
connector (male)
4-pin mini power
connector (female)
5-pin mini power
connector (male)
5-pin mini power
connector (female)
M12, L-coded power
connector (male)
M12, L-coded power
connector (female)
M12, A-coded
I/O connectors (Class A)
M12, A-coded I/O
connectors (Class A)
M12, D-coded network
connector (Link 1)
M12, D-coded network
connector (Link 2)
M12, A-coded I/O
connectors (Class B)
M12, A-coded I/O
connectors (Class B)
Network address switches
Functional Earth A (1)
Functional Earth B (2) Functional Earth B (2) Functional Earth B (2)
(1) Functional Earth A grounds the module EtherNet/IP communication circuitry, which is designed to mitigate the effect of noise on the network. The module requires a solid earth ground connection, either through a
metal screw to a grounded metal panel or through a wire.
(2) Functional Earth B grounds the module I/O and power circuitries to mitigate the effect of noise on the network. Functional Earth B is internally connected to pin 5 of power connectors in 5032-8IOLM12P5DR and
5032-8IOLM12M12LDR. The module requires a solid earth ground connection, either through the 5-pin mini or M12 L-coded power patchcord, or through a wire to the screw point.
(3) The QR Code contains a link to the product webpage that provides details on the product such as lifecycle status and documentation.
Removable IP switch cover
QR Code (3)
IP switch cover lock

12 Rockwell Automation Publication 5032-UM001A-EN-P - April 2023
Chapter 1 Introduction
Secure Access to the
System
To secure access to a Logix 5000® controller, ArmorBlock 5000 8-channel IO-Link master
module, and IO-Link devices by authorized users only, consider the following options:
• Follow the guidelines provided in the System Security Design Guidelines Reference
Manual, publication SECURE-RM001.
• Password protect the source and execution of the control program.
• Deploy EtherNet/IP devices in accordance with recommended architectures and
concepts. See the Converged Plantwide Ethernet (CPwE) Design and Implementation
Guide, publication ENET-TD001.
• Implement physical barriers, such as locked cabinets.
To secure access to the system, consider the following options:
• Follow industry best practices to harden your PCs and servers, including anti-virus/
anti-malware and application whitelisting solutions.
The recommendations are published at the Rockwell Automation technical support
center in Knowledgebase article Rockwell Automation Customer Hardening Guidelines,
#546987. The technical support center is available at: rok.auto/knowledgebase.
• Develop and deploy backup and disaster recovery policies and procedures. Test
backups on a regular schedule.
• Minimize network exposure for all control system devices and systems, and make sure
that they are not accessible from the Internet.
• Locate control system networks and devices behind firewalls and isolate them from the
business network.
• Subscribe to Knowledgebase article Industrial Security Advisory Index, #54102 at the
Rockwell Automation technical support center so you have access to information about
security matters that affect Rockwell Automation products. The technical support
center is available at: rok.auto/knowledgebase.
Ownership Every IO-Link master module and IO-Link device in a Logix 5000 control system must be
owned by a controller. In a Logix 5000 control system, the controller performs the following:
• Establishes the connection to the IO-Link master module and IO-Link devices to begin
operation in the control system.
• Sends the configuration data to the IO-Link master module and IO-Link devices (only
when Automatic Device Configuration (ADC) is enabled).
Each IO-Link master module and IO-Link device must continuously maintain communication
with its controller during normal operation.
Power the Module The ArmorBlock 5000 8-channel IO-Link master module uses two 24V DC (nominal) power
supplies. These supplies are called the MSA power (Module/Sensor/Actuator) and LA power
(Local Actuator). Internally, the MSA power and LA power are isolated from each other.
• MSA power provides power to the module and all eight IO-Link channels of the module.
• LA power provides power for the IO-Link Class B isolated extra power supply or 2 A for
digital outputs.
Power can be daisy chained from one module to the next. You can also install a separate
power supply to each module.
Take note of the following when supplying power to your system:
• The voltage range for MSA power is 18...30V DC for digital I/O mode.
• The voltage range for MSA power is 20...30V DC for IO-Link master mode.
• The maximum current that any module can carry is 10 A.
• The maximum current that any pin on the 4-pin or 5-pin mini power connectors can
carry is 10 A.

Rockwell Automation Publication 5032-UM001A-EN-P - April 2023 13
Chapter 1 Introduction
• The maximum current that any pin on the M12 L-coded power connectors can carry is
16 A.
• Confirm that the external module power supply is adequately sized for the total current
draw of the module power bus in the system.
• Not all power supplies are certified for use in all applications, for example,
nonhazardous and hazardous environments.
Module and Device
Configuration
You must create a Studio 5000 Logix Designer application project for the controller that owns
the ArmorBlock 5000 8-channel IO-Link master module and the IO-Link devices. You can
configure the IO-Link master module and the IO-Link devices in the project.
The Studio 5000 Logix Designer application transfers the project to the controller during the
program download.
For more information on how to configure an IO-Link master module or IO-Link device, see the
following:
•Configure the IO-Link Master Module on page 39
•Configure the IO-Link Device on page 61
Module and Device
Operation
Both the IO-Link master module and IO-Link device operate through connections. Connections
work in either cyclic mode or Change of State (COS) mode.
Requested Packet Interval
The Requested Packet Interval (RPI) is a configurable parameter that defines a specific rate at
which the controller exchanges data with the IO-Link master module or IO-Link device.
You set the RPI value during initial module or device configuration and can adjust it as
necessary after operation has begun.
For more information on guidelines for specifying RPI rates, see the Logix 5000 Controllers
Design Considerations Reference Manual, publication 1756-RM094.
Cyclic Mode
All connections work in cyclic mode, except for input event connections. In cyclic mode, both
the IO-Link master module and the IO-Link device send input data at the time that is defined in
the Requested Packet Interval (RPI). Similarly, the controller sends output data at the time that
is defined in the RPI.
ATTENTION: You must use two separate SELV-listed power supplies or one
SELV-listed power supply with two pairs of separately isolated terminals for
module power.
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 IO-Link
master module or IO-Link device is closed and reopened in one of the
following ways:
• You inhibit the connection to the module or device, 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 or
device configuration.

14 Rockwell Automation Publication 5032-UM001A-EN-P - April 2023
Chapter 1 Introduction
Change of State Mode
For input event connections, the IO-Link master module uses Change of State (COS) mode to
update the input data. New data is sent to the controller immediately when a transition occurs.
When there is no change of state, the data is sent at the time that is defined in the RPI.
Connections You can define connections for the IO-Link master module and IO-Link devices by choosing a
connection type. A connection is a real-time data transfer link between the controller and the
module or device that the project references.
During IO-Link master module or IO-Link device configuration, the connection type determines
what data is exchanged between the controller and the module or device. When you uninhibit a
module or device in online mode, or download the project with modules or devices that are
uninhibited to the controller, the controller attempts to establish a connection to each module
and device.
One of the following occurs:
• If the configuration is appropriate to the module or device that is detected, a
connection is made and operation begins.
• If the configuration is not appropriate to the module or device that is detected, the data
is rejected and the Studio 5000 Logix Designer application indicates that an error
occurred.
The configuration can be inappropriate for many reasons. For example, a mismatch in
Electronic Keying that prevents normal operation.
For more information on how to troubleshoot issues, see the following:
-Troubleshoot Your IO-Link Master Module on page 79.
-Troubleshoot Your IO-Link Device on page 89.
The controller monitors its connection with an IO-Link master module and IO-Link devices. Any
break in the connection, for example, the loss of power to the system, causes a fault. The
Studio 5000 Logix Designer application monitors the fault status tags to indicate when a fault
occurs on an IO-Link master module or IO-Link device.
To see where to change the connection type:
• For the IO-Link master module, see Module Definition on page 45.
• For the IO-Link device, see Module Definition on page 68.

Rockwell Automation Publication 5032-UM001A-EN-P - April 2023 15
Chapter 1 Introduction
Protected Operations To maintain the secure operation of your IO-Link master module and IO-Link devices,
operations that can disrupt the module and device operations are restricted based on the
operating mode.
Table 2 describes the restrictions.
For more information on the protected operating modes, see the following:
•Protected Mode for IO-Link Master Module on page 21.
•Protected Mode for IO-Link Devices on page 36.
Table 2 - Protected Operations on ArmorBlock 5000 8-channel IO-Link Master Modules and IO-Link Devices
Current
Operation
Activity
Firmware Update
Request (1) Reset Request Connection
Request
Configuration
Change
Connection or
Data Format
Change
Electronic Keying
Change RPI Change
Connection
not running Accepted
Connection
running Rejected Rejected Accepted (2) Not allowed (3) Accepted (4)
Firmware update
in process Rejected
(1) Firmware update for IO-Link devices is not supported.
(2) Configuration change is accepted in the following scenarios:
- Changes are made in the Module Properties window and you select Apply.
- Changes are made in the Configuration tags and you send a Reconfigure Module MSG instruction to the module or device.
- IO-Link device configuration changes are made in the ladder diagram through connected explicit messaging.
(3) The difference between Rejected and Not allowed is that rejected activities can be attempted in the Studio 5000 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 Studio 5000 Logix Designer application.
For example, if you attempt to reset a module that is connected to the controller, the Studio 5000 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 a controller, the Studio 5000 Logix Designer application does not execute the attempted change. The application only
alerts you that the change is not allowed. In this case, if the change is attempted online, the Module Definition dialog 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 online and select Apply or OK in the Module Properties window. In this case, before the change is made, a dialog box alerts you of the ramifications before the
change is made.
- Change the project while it is offline and download the updated project before going online again.

16 Rockwell Automation Publication 5032-UM001A-EN-P - April 2023
Chapter 1 Introduction
Notes:

Rockwell Automation Publication 5032-UM001A-EN-P - April 2023 17
Chapter 2
Module Features
This chapter describes the general features of the ArmorBlock 5000 8-channel IO-Link master
module.
To learn more about the other features of the IO-Link master module, see the following:
•I/O Channel Features on page 23.
•Common Features of IO-Link Device Integration on page 29.
Software Configurable You use the Studio 5000 Logix Designer application to configure the module, monitor system
operation, and troubleshoot issues.
The software makes module configuration easier and more reliable by minimizing the need for
tasks such as setting hardware switches and jumpers.
Configurable Channel
Modes
You can configure each channel of the ArmorBlock 5000 8-channel IO-Link master module as
IO-Link, digital input, or digital output mode. You can also configure some channels as a
Class B power supply for IO-Link devices.
To configure the channel mode, see General View on page 45.
Fault and Status Reporting The ArmorBlock 5000 8-channel IO-Link master module reports fault and status data along
with channel data. Fault and status data is reported in the following ways:
• Fault and status bits in the input data tags
• Studio 5000 Logix Designer application
• Module status indicators
Table 3 lists the fault and status tags that are available for the IO-Link master module in the
Studio 5000 Logix Designer application.
For more information on fault reporting in the Studio 5000 Logix Designer application and
module status indicators, see Troubleshoot Your IO-Link Master Module on page 79.
Table 3 - Fault and Status Tags for ArmorBlock 5000 8-channel IO-Link Master Module
Data Type Tag Name Triggering Event That Sets the Tag
Fault ConnectionFaulted (1)
(1) This tag provides module-wide data and affects all channels simultaneously.
The controller loses its connection to the module.
Status
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 a diagnostic condition is detected
or removed.
You can monitor this count during module operation and check the
channel diagnostics when the count value changes.

18 Rockwell Automation Publication 5032-UM001A-EN-P - April 2023
Chapter 2 Module Features
Module Inhibiting Module inhibiting lets you indefinitely suspend a connection between a controller and a
module without removing the module from the configuration. This process temporarily stops
the connection between the controller and the module.
You can use module inhibiting in the following scenarios.
• You want to perform maintenance on the module.
• You want to update a module, for example, update the module firmware revision.
• You use a program that includes a module that you do not physically possess yet. You
do not want the controller to look for a module that does not yet exist. In this case, you
can inhibit the module in your program until it physically resides in the system.
Use the following procedure.
1. Inhibit the module.
2. Perform the action on the module.
3. Uninhibit the module.
To inhibit a module, see Connection View on page 48.
Electronic Keying Electronic Keying reduces the possibility that you use the wrong device in a control system. It
compares the device that is defined in your project to the installed device. If keying fails, a
fault occurs. These attributes are compared.
The following Electronic Keying options are available.
IMPORTANT Whenever you inhibit a module with outputs, all outputs change to the
state that is configured for Program mode.
For more information, see Configure Channel Output State in Fault Mode
on page 25.
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
Keying Option Description
Compatible
Module
Lets the installed device accept the key of the device that is defined in the project when the
installed device can emulate the defined device. With Compatible Module, you can typically
replace a device with another device that has the following characteristics:
• Same catalog number
• Same or higher Major Revision
• Minor Revision as follows:
– If the Major Revision is the same, the Minor Revision must be the same or higher.
– If the Major Revision is higher, the Minor Revision can be any number.
Disable Keying
Indicates that the keying attributes are not considered when attempting to communicate with
a device. With Disable Keying, communication can occur with a device other than the type
specified in the project.
WARNING: Be extremely cautious when using Disable Keying; if used incorrectly, this option
can lead to personal injury or death, property damage, or economic loss.
We strongly recommend that you do not use Disable Keying.
If you use Disable Keying, you must take full responsibility for understanding whether the
device being used can fulfill the functional requirements of the application.
Exact Match Indicates that all keying attributes must match to establish communication. If any attribute
does not match precisely, communication with the device does not occur.

Rockwell Automation Publication 5032-UM001A-EN-P - April 2023 19
Chapter 2 Module Features
Carefully consider the implications of each keying option when selecting one.
For more detailed information on Electronic Keying, see Electronic Keying in Logix 5000
Control Systems Application Technique, publication LOGIX-AT001.
Update Module Firmware The ArmorBlock 5000 8-channel IO-Link master module is manufactured with module
firmware installed. If updated module firmware revisions are available in the future, you can
update the firmware.
Updated firmware revisions are available for various reasons, for example, to correct an
anomaly that existed in previous module firmware revisions.
You access updated firmware files at the Rockwell Automation Product Compatibility and
Download Center (PCDC) at: rok.auto/pcdc.
At the PCDC, you can use the module catalog number to check for firmware updates. If the
catalog number is not available, no updates exist then.
Input Events The ArmorBlock 5000 8-channel IO-Link master module can be configured with four input
event definitions.
To use Input Events, select the “Data with Events” or “Data with Events and Ethernet Status”
connection type in the IO-Link master Module Definition dialog.
To change the connection type, see General View on page 45.
The following conditions can trigger events:
• An input state change
• A counting input done bit change
• A pattern of input state changes on multiple module inputs
When the module reports an input event to the controller, the module can trigger an event task
to execute in the controller. The event task lets you execute a section of logic immediately
when an event, or receipt of new data, occurs.
For more information on event tasks, see the Logix 5000 Controllers Tasks, Programs, and
Routines Programming Manual, publication 1756-PM005.
Independent Point Trigger
An input state change or a counting input bit done change that triggers an event is known as
an independent point trigger.
To use this type of trigger, you must enable the Independent Point Trigger option in the event
definition. Set the EO.Eventxx.IndependentConditionTriggerEn tag to 1.
IMPORTANT Changing Electronic Keying parameters while the project is online
interrupts connections to the device and any devices that are
connected through the device. Connections from other controllers can
also be broken.
If an I/O connection to a device is interrupted, the result can be a loss
of data.
IMPORTANT Verify that you are using the correct firmware revisions for your modules
before commissioning your system.

20 Rockwell Automation Publication 5032-UM001A-EN-P - April 2023
Chapter 2 Module Features
Pattern Match Trigger
When a pattern of input state changes triggers an event, multiple points participate in the
event trigger. To use this type of trigger, you must disable the Independent Point Trigger
option in the event definition. Set the EO.Eventxx.IndependentConditionTriggerEn tag to 0.
Every point that participates in an event trigger is configured separately. Depending on the
event definition, the collective status of all points that matches the pattern triggers the event.
Input Event Latching
To use input event latching, you must select the Latch Event checkbox for that input event. Set
the EO.Eventxx.LatchEn tag to 1.
When input event latching is used, the event in the input data must be acknowledged before a
new event is sent out.
To acknowledge the current event in the input data, set the EO.Eventxx.EventNumberAck tag to
the event number (EI.Eventxx.EventNumber tag) in the input data.
If the current event is not acknowledged, subsequent events are stored in a queue. The queue
can store up to four events. If the queue is full, excess events are dropped.
Additional Event Considerations
When you use the Input Events feature, also consider the following:
• An Event task only actuates if an event occurs.
• An event is recognized only when it maintains the same state for the minimum duration
that is determined by the input filter time specified.
For example, if the input filter time is set at 2 ms, and the input filter time accuracy is
-50…+400 µs (except for 0 µs filter time setting), this means that:
- A pulse width that is shorter than 1.95 ms is not detected.
- A pulse width that is longer than 2.4 ms is detected.
- A pulse width that is between 1.95…2.4 ms may or may not be detected.
• When you configure the RPI of the input event connection, consider that the minimum
interval between two input data packets of event connection is one quarter of the RPI
connection.
• After the event task executes, it does not execute again until the event occurs again.
• When the input event connection is reopened, the EI.Eventxx.PtxxData tag is reset to 0.
Use CIP Sync Time 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 ArmorBlock 5000 8-channel IO-Link master module is a CIP Sync slave-only device. 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® and CIP Sync
Configuration Application Technique, publication IA-AT003.
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.