Rockwell Automation Allen-Bradley ArmorBlock 1732E-IB8M8SOER User manual

ArmorBlock EtherNet/IP Dual
Port 8-point Sequence of
Events Input and Scheduled
Output Modules
Catalog Numbers 1732E-IB8M8SOER, 1732E-OB8M8SR
User Manual Original Instructions

2Rockwell Automation Publication 1732E-UM003D-EN-E - November 2021
ArmorBlock EtherNet/IP Dual Port 8-point Sequence of Events Input and Scheduled Output Modules User Manual
Important User Information
Read this document and the documents listed in the additional resources section about installation, configuration, and
operation of this equipment before you install, configure, operate, or maintain this product. Users are required to familiarize
themselves with installation and wiring instructions in addition to requirements of all applicable codes, laws, and standards.
Activities including installation, adjustments, putting into service, use, assembly, disassembly, and maintenance are required to
be carried out by suitably trained personnel in accordance with applicable code of practice.
If this equipment is used in a manner not specified by the manufacturer, the protection provided by the equipment may be
impaired.
In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use
or application of this equipment.
The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and
requirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for
actual use based on the examples and diagrams.
No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software
described in this manual.
Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation, Inc., is
prohibited.
Throughout this manual, when necessary, we use notes to make you aware of safety considerations.
Labels may also be on or inside the equipment to provide specific precautions.
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).

Rockwell Automation Publication 1732E-UM003D-EN-E - November 2021 3
Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
About This Publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Who Should Use this Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Download Firmware, AOP, EDS, and Other Files . . . . . . . . . . . . . . . . . . . . 7
Studio 5000 Logix Designer Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Summary of Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Chapter 1
About ArmorBlock Modules Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Module Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Hardware/Software Compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Use of the Common Industrial Protocol (CIP). . . . . . . . . . . . . . . . . . . . . . 10
Understand the Producer/Consumer Model . . . . . . . . . . . . . . . . . . . . . . . 10
Specify the Requested Packet Interval (RPI) . . . . . . . . . . . . . . . . . . . . . . . 10
Chapter 2
Module Overview and Features Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
EtherNet/IP Network Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Introduction to CIP Sync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
What is IEEE 1588 PTP (Precision Time Protocol)? . . . . . . . . . . . . . . 13
CIP Sync Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
What is CIP Sync? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
What is Time Stamping? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Introduction to the Sequence of Events Input Module . . . . . . . . . . . . . . 14
High Performance Sequence of Events Applications in the Logix
Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
First Fault Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Time Stamped I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
High Speed Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Motion Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Global Position Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Introduction to Scheduled Output Module . . . . . . . . . . . . . . . . . . . . . . . . 16
Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
High Speed Product Reject . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Chapter 3
Use the Modules in an
ArmorBlock System
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Differences Between Module and Standard I/O . . . . . . . . . . . . . . . . . . . . 19
Similar Functionality to Standard ArmorBlock. . . . . . . . . . . . . . . . . . . . . 20
Chapter 4
Install Your Module Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Install the Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4Rockwell Automation Publication 1732E-UM003D-EN-E - November 2021
Table of Contents
Set the Network Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Mount the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Wire the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Power Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Chapter 5
Configure the Module for Your
EtherNet/IP Network
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Configuration Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Gateway Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Subnet Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Set the Network Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Use the Rockwell Automation BootP/DHCP Utility . . . . . . . . . . . . . . . . . 30
Save the Relation List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Use DHCP Software to Configure Your Module . . . . . . . . . . . . . . . . . . . . 33
Chapter 6
Configure the Module Using
Studio 5000 Logix Designer
Software
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Set Up the Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Create an Example Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Configure Your I/O Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Overview of the Configuration Process in
Studio 5000 Logix Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Add a New Bridge and Module to Your Project . . . . . . . . . . . . . . . . . . . . . 37
Add the Local EtherNet/IP Bridge to the I/O Configuration . . . . . . 38
Add the I/O module as a child of the 1756-EN2T module . . . . . . . . . 39
Use the Default Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Change the Default Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Download Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Edit Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Access Module Data in Studio 5000 Logix Designer Software. . . . . . . . 45
Configure Studio 5000 Logix Designer and the 1756-EN2T
Communication Module for CIP Sync. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Chapter 7
Common Features of the 1732E-
IB8M8SOER and 1732E-OB8M8SR
Modules
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Communications Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Electronic Keying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Module Inhibiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Module Fault Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Fully Configurable via Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Producer/Consumer Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Status Indicator Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Rockwell Automation Publication 1732E-UM003D-EN-E - November 2021 5
Table of Contents
Chapter 8
Specific Features of the 1732E-
IB8M8SOER Sequence of Events
Input Module
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Determine Module Compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Operational Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Timestamp Latching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Software-configurable Input Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Sync to Master. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Chapter 9
Specific Features of the 1732E-
OB8M8SR Scheduled Output
Module
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Determine Module Compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Operational Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Time-Scheduled Output Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Configurable Point-Level Output Fault States. . . . . . . . . . . . . . . . . . . . . . 56
Output State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Chapter 10
Usethe Sequence of Events Input
and Scheduled Output Modules
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Use the Sequence of Events Input Module . . . . . . . . . . . . . . . . . . . . . . . . . 60
How Does 1732E-IB8M8SOER Store Timestamp Data? . . . . . . . . . . 60
Use Timestamp Latching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Use Timestamp Capture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Operational Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Manage the Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Module Sends Data to the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Copy Relevant Input Data to a Separate Data Structure . . . . . . . . . 69
Acknowledge Timestamp Latching Timestamp Data . . . . . . . . . . . . 70
Sort the Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Propagate a Signal From Input Pin to Ethernet . . . . . . . . . . . . . . . . . 72
Per Point Mode of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Use the Scheduled Output Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Usage with MAOC Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
I/O Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Schedule Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Chapter 11
Troubleshoot the Module Troubleshoot the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Determine Fault Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Chapter 12
Interpret Status Indicators Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Appendix A
Module Tags Fault and Status Reporting Between the Module and Controllers . . . . 83
Module Tag Names and Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Tags Used. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

6Rockwell Automation Publication 1732E-UM003D-EN-E - November 2021
Table of Contents
Appendix B
Data Tables Communicate with Your Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Connection Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Appendix C
Connect to Networks via
Ethernet Interface
ArmorBlock Module and Ethernet Communication . . . . . . . . . . . . . . . 101
ArmorBlock Module and PC Connections to the Ethernet Network . 101
Connecting to an Ethernet Network . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
EtherNet/IP Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Duplicate IP Address Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Configure Ethernet Communications on the ArmorBlock Module . . 103
Configure Using Studio 5000 Logix Designer Software . . . . . . . . . . . . 104
Enable or Disable the Web Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Configure Using Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Appendix D
ArmorBlock Embedded Web
Server
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Typical Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Browser Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Enable or Disable the Web Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Access the Home Page of the Web Server . . . . . . . . . . . . . . . . . . . . . . . . . 107
Log On to the Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Navigate the
ArmorBlock I/O. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Access Diagnostic Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Rockwell Automation Publication 1732E-UM003D-EN-E - November 2021 7
Preface
About This Publication This manual is a reference guide for the 1732E-IB8M8SOER, 1732E-OB8M8SR
modules. It describes the procedures you use to install, wire, troubleshoot,
configure, and use your module.
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.
Who Should Use this Manual Use this manual if you are responsible for designing, installing, programming,
or troubleshooting control systems that use ArmorBlock® EtherNet/IP™ Dual
Port 8-point Sequence of Events Input and Scheduled Output Modules.
You should have a basic understanding of electrical circuitry and familiarity
with relay logic. If you do not, obtain the proper training before using this
product.
Download Firmware, AOP,
EDS, and Other Files
Download firmware, associated files (such as AOP, EDS, and DTM), and access
product release notes from the Product Compatibility and Download Center at
rok.auto/pcdc.
Studio 5000 Logix Designer
Application
The Studio 5000 Logix Designer® application is the re branding of
RSLogix 5000® software and will continue to be the product to program
Logix 5000™ controllers for discrete, process, batch, motion, safety, and drive
based solutions.
Summary of Changes This publication contains the following new or updated information. This list
includes substantive updates only and is not intended to reflect all changes.
Topic Page
Updated template throughout
Added inclusive language acknowledgment 7
Added section Enable or Disable the Web Server 104, 106
Corrected web server user name and password details 107

8Rockwell Automation Publication 1732E-UM003D-EN-E - November 2021
Preface
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 Dual-Port EtherNet/IP 8-Point Digital Modules 1732E-WD002 Information on wiring the ArmorBlock Dual-Port EtherNet/IP 8-point Digital Modules.
1732E ArmorBlock 2 Port Ethernet Module Installation Instructions,
publication 1732E-IN007 Information on installing the ArmorBlock EtherNet/IP module.
ControlLogix Sequence of Events Module User Manual, publication 1756-UM528 A manual on how to install, configure and troubleshoot the ControlLogix Sequence of Events
module in your ControlLogix application.
EtherNet/IP Embedded Switch Technology Application Guide,
publication ENET-AP005 A manual on how to install, configure and maintain linear and Device Level Ring (DLR) networks
using Rockwell Automation® EtherNet/IP devices with embedded switch technology.
EtherNet/IP Modules in Logix 5000 Control Systems User Manual,
publication ENET-UM001 A manual on how to use EtherNet/IP modules with Logix 5000 controllers and communicate with various devices on the Ethernet network.
Integrated Architecture and CIP Sync Configuration Application Techniques,
publication IA-AT003 A manual on how to configure CIP Sync with Integrated Architecture products. and applications.
EtherNet/IP Network Devices User Manual, ENET-UM006 Describes how to configure and use EtherNet/IP devices to communicate on the EtherNet/IP
network.
Ethernet Reference Manual, ENET-RM002 Describes basic Ethernet concepts, infrastructure components, and infrastructure features.
System Security Design Guidelines Reference Manual, 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.
Industrial Components Preventive Maintenance, Enclosures, and Contact Ratings
Specifications, publication IC-TD002 Provides a quick reference tool for Allen-Bradley® industrial automation controls and
assemblies.
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.

Rockwell Automation Publication 1732E-UM003D-EN-E - November 2021 9
Chapter 1
About ArmorBlock Modules
Overview This chapter is an overview of the ArmorBlock family of modules. You will need
to understand the concepts discussed in this chapter to configure your module
and use it in an EtherNet/IP control system. The following table guides you
where to find specific information in this chapter.
Module Features The module features include:
• Use of EtherNet/IP messages encapsulated within standard TCP/UDP/IP
protocol.
• Common application layer with ControlNet® and DeviceNet®.
• Interfacing via Category 5 rated twisted pair cable.
• Half/full duplex 10 Mbit or 100 Mbit operation.
• Mounting on a wall or panel.
• Communication supported by RSLinx® software.
• IP address assigned via standard DHCP tools.
• I/O configuration via Studio 5000 Logix Designer software.
• No network scheduling required.
• No routing tables required.
• Supports connections from multiple controllers simultaneously.
Hardware/Software
Compatibility
The module and the applications described in this manual are compatible with
the following firmware versions and software releases.
Contact Rockwell Automation if you need software or firmware upgrades to
use this equipment.
Topic Page
Module Features 9
Hardware/Software Compatibility 9
Use of the Common Industrial Protocol (CIP) 10
Understand the Producer/Consumer Model 10
Specify the Requested Packet Interval (RPI) 10
Product Firmware Revision / Software Version
1732E-IB8M8SOER and 1732E-OB8M8SR Firmware revision 1.001 or later
1756-EN2T, 1756-EN2TR, 1756-EN3TR 3.x version when using Studio 5000 Logix Designer v18 or later
Studio 5000 Logix Designer(1)
(1) Studio 5000 Logix Designer is the replacement for RSLogix 5000 (since v21). It provides one software package for discrete,
process, batch, motion, safety and drive-based applications.
18 or later
Studio 5000 Logix Designer Add-on Profile 3.01.01 or later
RSLinx software 2.56 or later

10 Rockwell Automation Publication 1732E-UM003D-EN-E - November 2021
Chapter 1 About ArmorBlock Modules
For a complete ControlLogix® compatibility matrix, see the Integrated
Architecture® and CIP Sync™ Configuration Application Technique,
publication IA-AT003.
Use of the Common
Industrial Protocol (CIP)
The 1732E-IB8M8SOER and 1732E-OB8M8SR modules use the Common
Industrial Protocol (CIP™). CIP is the application layer protocol specified for
EtherNet/IP, the Ethernet Industrial Protocol. It is a message-based protocol
that implements a relative path to send a message from the “producing” device
in a system to the “consuming” devices.
The producing device contains the path information that steers the message
along the proper route to reach its consumers. Because the producing device
holds this information, other devices along the path simply pass this
information; they do not need to store it.
This has two significant benefits:
• You do not need to configure routing tables in the bridging modules,
which greatly simplifies maintenance and module replacement.
• You maintain full control over the route taken by each message, which
enables you to select alternative paths for the same end device.
Understand the Producer/
Consumer Model
The CIP “producer/consumer” networking model replaces the old source/
destination (“master/slave”) model. The producer/consumer model reduces
network traffic and increases speed of transmission. In traditional I/O
systems, controllers poll input modules to obtain their input status. In the CIP
system, input modules are not polled by a controller. Instead, they produce
their data either upon a change of state (CoS) or periodically. The frequency of
update depends upon the options chosen during configuration and where on
the network the input module resides. The input module, therefore, is a
producer of input data and the controller is a consumer of the data.
The controller can also produce data for other controllers to consume. The
produced and consumed data is accessible by multiple controllers and other
devices over the EtherNet/IP network. This data exchange conforms to the
producer/consumer model.
Specify the Requested
Packet Interval (RPI)
The Requested Packet Interval (RPI) is the update rate specified for a
particular piece of data on the network. This value specifies how often to
produce the data for that device. For example, if you specify an RPI of 50 ms, it
means that every 50 ms the device sends its data to the controller or the
controller sends its data to the device.
RPIs are only used for devices that exchange data. For example, a ControlLogix
EtherNet/IP bridge module in the same chassis as the controller does not
require an RPI because it is not a data-producing member of the system; it is
used only as a bridge to remote modules.

Rockwell Automation Publication 1732E-UM003D-EN-E - November 2021 11
Chapter 2
Module Overview and Features
Overview This chapter provides an overview of the ArmorBlock EtherNet/IP Dual Port 8-
point Sequence of Events Input and Scheduled Output Modules,
1732E-IB8M8SOER and 1732E-OB8M8SR. The modules provide time-stamping
functionality when an input event occurs and allow for scheduling of outputs.
Although primarily described in this manual as having CIP Sync functionality,
both modules can be configured to function as standard I/O modules.
The following table indicates where you can information on this chapter:
Topic Page
EtherNet/IP Network Overview 12
Introduction to CIP Sync 13
What is IEEE 1588 PTP (Precision Time Protocol)? 13
CIP Sync Support 13
What is CIP Sync? 13
What is Time Stamping? 14
Introduction to the Sequence of Events Input Module 14
High Performance Sequence of Events Applications in the Logix Architecture 15
First Fault Detection 15
Time Stamped I/O 15
High Speed Applications 16
Motion Control 16
Global Position Registration 16
Introduction to Scheduled Output Module 16
Operation 16
High Speed Product Reject 17

12 Rockwell Automation Publication 1732E-UM003D-EN-E - November 2021
Chapter 2 Module Overview and Features
EtherNet/IP
Network Overview
The modules incorporate embedded switch technology. They support Star,
Tree, Daisychain or Linear, and Ring network topologies.
• Star or Tree topologies can connect to either Port 1 or Port 2.
• Daisy Chain/Linear topologies will pass communications from Port 1 to
2, or Port 2 to 1.
• Ring topology will pass communications from Port 1 to 2, or Port 2 to 1.
The 1732E-IB8M8SOER and 1732E-OB8M8SR modules support the
management of network traffic to ensure timely delivery of critical data,
Quality of Service (QoS) and Internet Group Management Protocol (IGMP)
protocols are supported.
If the ring topology is used, the Ring Master (not the ArmorBlock EtherNet/IP
Dual Port 8-point Sequence of Events Input or Scheduled Output Modules)
must be designated in the system, and determines the beacon rate and the
timeout period. For more information on topologies, see the EtherNet/IP
Device Level Ring Application Technique, publication ENET-AT007. The 1732E-
IB8M8SOER and 1732E-OB8M8SR modules are CIP Sync slave only devices.
There must be another module on the network that functions as a master
clock.
LINK1
NET
MOD
X10
X100 X1
LINK2
Functional Earth ground(1)
M8 I/O connectors
Node address switches
EtherNet/IP D-Code M12
connector
EtherNet/IP D-Code M12
connector
M8 I/O connectors/
status indicators
Power status
indicator
Network status LED
Link 1 status LED Link 2 status LED
Module status LED
Node address switches
Power connector
Power connector
(1) Functional Earth grounds the I/O block’s EtherNet/IP communication circuitry which is designed to mitigate the effect
of noise on the network. It requires a solid earth ground connection, either through a metal screw to a grounded
metal panel or through a wire.

Rockwell Automation Publication 1732E-UM003D-EN-E - November 2021 13
Chapter 2 Module Overview and Features
Introduction to CIP Sync CIP is the Common Industrial Protocol that we use to let all
Rockwell Automation products communicate with each other whether it be on
a DeviceNet, ControlNet, and/or an Ethernet network. Since it is an ODVA
standard, other industrial product manufacturers develop products to
communicate via the CIP protocol.
CIP Sync is a CIP implementation of the IEEE 1588 PTP (Precision Time
Protocol) in which devices can bridge the PTP time across backplanes and on to
other networks via EtherNet/IP ports.
What is IEEE 1588 PTP (Precision Time Protocol)?
The IEEE 1588 standard specifies a protocol to synchronize independent clocks
running on separate nodes of a distributed measurement and control system
to a high degree of accuracy and precision. The clocks communicate with each
other over a communication network. In its basic form, the protocol is
intended to be administration free. The protocol generates a master slave
relationship among the clocks in the system. Within a given subnet of a
network there will be a single master clock. All clocks ultimately derive their
time from a clock known as the grandmaster clock. This is called Precision
Time Protocol (PTP).
The PTP is a time-transfer protocol defined in the IEEE 1588-2008 standard
that allows precise synchronization of networks, for example, Ethernet.
Accuracy within the nanosecond range can be achieved with this protocol
when using hardware generated synchronization.
IEEE 1588 is designed for local systems requiring very high accuracies beyond
those attainable using Network Time Protocol (NTP). NTP is used to
synchronize the time of a computer client or server to another server or
reference time source, such as a GPS.
CIP Sync Support
CIP Sync supports the IEEE 1588-2008 synchronization standard. In this
architecture, a grandmaster clock provides a master time reference for the
system time. The 1732E-IB8M8SOER, 1732E-OB8M8SR modules are CIP Sync
slave only devices. There must be another module on the network that will
function as a master clock. The grandmaster could be:
• A ControlLogix L7 or L8 controller when using Studio 5000 Logix
Designer software v18 or later, or
• An Ethernet bridge that supports IEEE 1588 V2, or
• A Symmetricom Grand Master GPS or equivalent.
What is CIP Sync?
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
connected over CIP networks. This technology supports highly distributed
applications that require time stamping, sequence of events recording,
distributed motion control, and increased control coordination.

14 Rockwell Automation Publication 1732E-UM003D-EN-E - November 2021
Chapter 2 Module Overview and Features
What is Time Stamping?
Each input has its own individual timestamp recorded for both ON and OFF
transitions. The offset from the timestamp to the local clock is also recorded so
that steps in time can be detected and resolved.
Timestamping uses the 64-bit system time whose time base is determined by
the modules master clock resolved in microseconds. Each timestamp is
updated as soon as an input transition is detected, before input filtering
occurs. When filtering is enabled, the transition is only recorded if the
transition passes the filter.
The module starts timestamping as soon as it powers up, even if it is not
synchronized to a master clock. If it is synchronized to a master clock and then
becomes unsynchronized it continues to time stamp. All time stamps and
offsets have a value of zero at power-up.
For more information on how to use CIP Sync technology, see the Integrated
Architecture and CIP Sync Configuration Application Technique publication
IA-AT003.
Introduction to the
Sequence of Events Input
Module
The 1732E-IB8M8SOER is an input module that offers sub-millisecond
timestamping on a per point basis in addition to providing the basic ON/OFF
detection. It supports two modes of operation: Per Point Mode and FIFO (First
In First Out) Mode. To learn more about using the modules in these modes of
operation, see Operational Modes on page 63.
All input point event times are recorded and returned in a single buffer. The
module returns two 64-bit timestamps for each input, thus allowing:
• ON and OFF events for each point to be displayed simultaneously in the
input data.
• Ladder logic not being explicitly required to see events, although needed
to archive events.
• Events to be kept in the controller memory during remote power loss
thus eliminating data loss.
All inputs on the module can be filtered for both ON to OFF and OFF to ON
transitions. The timestamp for a filtered input will be the time of the initial
transition to the new state and not the time that the filter validates the event as
real.
Selective Event Capturing allows particular events to be disabled per input and
per transition, ON to OFF or OFF to ON.
Event latching ensures that events are not overwritten. A single transition in
each direction is recorded per point. Any new event, which occurs after the
point has captured a timestamp, is dropped until the stored events have been
acknowledged.
If latching is not enabled in point mode, new events will overwrite old events
when they are received. In FIFO mode, up to 256 events per input will be
buffered before events are overwritten. Thus, if inputs are changing rapidly it
may be possible that events will be lost either in the module or the controller
prior to an event being operated on by ladder logic.
When events are lost, either old ones being overwritten or new ones being
ignored due to latching, an EventOverflow bit will be set for each point that
loses an event. The EventOverflow bit will clear when the blocking events for
that point are acknowledged.

Rockwell Automation Publication 1732E-UM003D-EN-E - November 2021 15
Chapter 2 Module Overview and Features
Timestamping is a feature that registers a time reference to a change in input
data. For the 1732E-IB8M8SOER, the time mechanism used for timestamping
is (PTP) system time. The 1732E-IB8M8SOER module is a PTP slave-only
device. There must be another module on the network that functions as a
master clock.
High Performance Sequence of Events Applications in the Logix
Architecture
Sequence of Events (SOE) applications span a wide range of industry
applications. Typically any event that needs to be compared against a second
event can be classified as SOE:
• Used on discrete machines to identify failure points.
• Used in Power Substations or power plants to indicate first fault
conditions.
• Used in SCADA applications to indicate pump failures or other discrete
events.
• Used in motion control applications to increase control coordination.
• Used in high speed applications.
• Used in Global Position Registration.
In today's environment, specifications for SOE applications typically require
1 ms or better resolution on timestamps. There are two types of SOE
applications.
• First Fault – measures the time between events with no correlation to
events outside of that system.
• Real Time – captures the time of an event occurrence as it relates to some
master clock. Typically this is a GPS, NTP server or some other very
accurate clock source. This method allows distributed systems to capture
events and build a history of these events. These events are almost always
digital, however some are analog for which lower performance
requirements can be configured.
First Fault Detection
An example of first fault detection would be intermittent failure from a sensor
on a safety system faults a machine and halts production cascading a flood of
other interrelated machine faults. Traditional fault detection or alarms may
not appear in the correct timed order of actual failure making root cause of the
down time difficult or impossible.
Time Stamped I/O
High precision timestamps on I/O allows very accurate first fault detection
making it easy to identify the initial fault that caused machine down time.
Common Time base for Alarming System logs user interaction as well as alarm
events using common time reference.
The power industry requires sub 1 ms accuracy on first fault across
geographically dispersed architecture.

16 Rockwell Automation Publication 1732E-UM003D-EN-E - November 2021
Chapter 2 Module Overview and Features
High Speed Applications
Packaging machines or sorters that have fast part cycles are often bottlenecked
by controller scan times. By switching to a time-based solution, you can
remove many scan time critical components of the system. This programming
technique allows you to do predictive events and schedule outputs to run
things like diverters without having a scan time to match the part cycle time.
Motion Control
CIP Sync also provides a common time reference for distributed VFD drives,
servos, and controllers throughout the system. This allows controllers to
request axes, reach a predefined position at a known time reference, or run at
a set speed using the same reference. Since all drives and controllers in the
system have the same reference to time, the controller can issue simple
requests for axes to reach target positions in a synchronized fashion.
Global Position Registration
Registration refers to a function usually performed by the drive where a
physical input is triggered causing the drive to precisely capture the actual axis
position when the input event occurred. Rather than wiring inputs to the
registration input on all of the drives, this time-based system lets you wire an
input to only one time based SOE input module. The timestamp returned for
that input, can be used by the motion planner to calculate the actual axis
position at the time the input triggered. This simplifies system installation,
reduces wiring costs, and provides a global machine registration for all the
axes in the system through one SOE input.
Introduction to Scheduled
Output Module
The 1732E-OB8M8SR Scheduled Output module is designed to work in
conjunction with the MAOC motion instruction to provide position-based
output control (also known as PLS). The MAOC instruction by itself allows
position-based output control using the position of any motion axis in
ControlLogix as the position reference and any output or boolean as the
output. The MAOC updates the outputs based on motion axis position at the
motion group coarse update rate (typically 2…10 ms). While this is adequate for
some applications, it is too slow for many high speed applications typically
found in converting and packaging segments. The 1732E-OB8M8SR module
improves performance by supporting the ability to schedule the output turn-
on/turn-off time of its 8 outputs (outputs 0…7) in 1 μs increments. Outputs are
scheduled by entering data into one or more of the 16 schedules provided by
the output connection data store.
Operation
This scheduled output implementation schedules outputs on a per point basis
and each individual output point is controlled by its own timestamp.
Individual schedules are created in the controller, stored in the output image
table for the module, and sent over the backplane to the Scheduled Output
module. The schedule specifies a sequence count, the output point to be
associated with the schedule, the time at which an output value should be
applied to the physical output point, and the value to be applied at the
IMPORTANT When using the 1732E-OB8M8SR module with the MAOC instruction, make
sure that you are using Studio 5000 Logix Designer, version 21 or later. You
must also select Yes for MAOC support and Per Point under Time Stamping.

Rockwell Automation Publication 1732E-UM003D-EN-E - November 2021 17
Chapter 2 Module Overview and Features
scheduled time. The I/O module receives and stores the schedule. The CIP Sync
time of each schedule is monitored by the module. When a schedule has
expired, that is the current time, matches the scheduled timestamp, the output
value is then applied to the corresponding output bit. Timer hardware in the
ASIC is used to optimize the scheduling algorithm. This hardware also reduces
the latency and jitter performance. Status of each schedule is reported in the
output echo connection and reflected in the input image for the module.
The scheduled output functionality relies on CIP Sync time. Unused outputs
may be used as normal outputs and are applied immediately rather than
waiting for the CIP Sync time to expire. A mask is sent to the module to
indicate which outputs are to function as normal outputs. The scheduled
output module supports up to 8 outputs that can be individually scheduled.
The scheduled outputs must be between output points 0 and 7. The 1732E-
OB8M8SR module supports up to 16 schedules with two schedules per output.
Outputs that are not “scheduled” are used as normal output points. A mask is
used to indicate which points are scheduled and which points are
unscheduled. Jitter performance is less than 25 μs. All of the scheduling
configuration is done through the MAOC instruction.
If a new schedule as indicated by a change in the sequence count is received by
the I/O module before the current schedule has expired, the current schedule is
overwritten. This mechanism can be used to cancel currently active schedule.
Status bits returned in the output echo connection may be used to determine
the current state of each schedule and to trigger corresponding event tasks.
If a new schedule is sent by the controller and the CIP Sync time has already
past, the output is asserted until the CIP Sync time has completely wrapped
around. The module does not check for an expired CIP Sync time.
High Speed Product Reject
In a control system you can program a scheduled output module, which can
trigger multiple outputs simultaneously or trigger a reject at the precise point
a product is at the reject station.
By using time to schedule the output in advance, and identifying when the
product will be at a known position, hitting the exact point when a part is in
front of a reject station on a high speed packaging machine, can be controlled.
WARNING: If the time between two schedules is less than the minimum schedule
interval (for example, 100 µs), then deviation occurs. This means that even though
two outputs are scheduled at different times (for example, time 90 and time 110),
they both activate at the same time (for example, time 90). The minimum schedule
interval should not be set to faster than 100 µs.

18 Rockwell Automation Publication 1732E-UM003D-EN-E - November 2021
Chapter 2 Module Overview and Features
Notes:

Rockwell Automation Publication 1732E-UM003D-EN-E - November 2021 19
Chapter 3
Use the Modules in an ArmorBlock System
Introduction This chapter describes how the ArmorBlock EtherNet/IP Dual Port 8-point
Sequence of Events Input and Scheduled Output Modules operate in an
ArmorBlock system.
Differences Between Module
and Standard I/O
In many aspects, the modules behave the same as any other ArmorBlock digital
module. However, the modules offer several significant differences from other
EtherNet/IP ArmorBlock digital input modules, including those described in
Table 1.
Topic Page
Differences Between Module and Standard I/O 19
Similar Functionality to Standard ArmorBlock 20
Table 1 - Differences Between Module and Standard I/O
Difference Description
Additional data produced for controller
The modules produce significantly more data for its owner-controller than
standard ArmorBlock digital input modules. While other input modules
only produce ON/OFF and fault status, the modules produce data such as
ON/OFF and fault status, timestamp data, indication of whether new data
was produced for specific input points or if transitions were not
timestamped.
CIP Sync These modules have an internal clock that is synchronized with a master clock using CIP Sync. This clock is used for time stamping inputs and
outputs.
Position Based Control using MAOC
The Motion Axis Output Cam (MAOC) instruction provides position-based
control of outputs by using position and velocity information of any motion
axis.
The 1732E-OB8M8SR module can be specified as the output source for the
MAOC instruction, then the MAOC instruction automatically handles the
time-based output scheduling and enables it on the eight outputs on the
1732E-OB8M8SR module. The benefit of using output scheduling in this
manner is that the resolution of the output control is improved from the
motion coarse update rate (typically 1...32 ms) to 100 μs.
Only one owner-controller per module While multiple controllers can simultaneously own other digital input
modules, the module only supports a single owner-controller.

20 Rockwell Automation Publication 1732E-UM003D-EN-E - November 2021
Chapter 3 Use the Modules in an ArmorBlock System
Similar Functionality to
Standard ArmorBlock
This chapter focuses on how the module behavior differs from that of other
ArmorBlock modules. However, you should be aware of aspects in which the
module is similar to standard EtherNet/IP ArmorBlock modules. Table 2
describes the similarities.
Table 2 - Similarities to Standard I/O
Concept Description
Ownership
Every module in an ArmorBlock system must be owned by a Logix 5000
controller. This owner-controller:
•Stores configuration data for every module that it owns.
•Sends the module configuration data to define the module behavior and
begin operation with the control system.
This module does not support multiple owner-controllers.
Using Studio 5000 Logix Designer software
The I/O configuration portion of Studio 5000 Logix Designer software,
version 18 or later, generates the configuration data for each module.
Configuration data is transferred to the controller during the program
download and subsequently transferred to the appropriate modules.
Modules are ready to run as soon as the configuration data has been
downloaded.
Configure all modules for a given controller using Studio 5000 Logix
Designer software and download that information to the controller.