supporting Sequence of Events
Table Of Contents
- 1732E-UM002A-EN-E 1732E EtherNet/IP ArmorBlock Supporting Sequence of Events User Manual
- Important User Information
- Table of Contents
- Preface
- Chapter 1 - About 1732E ArmorBlock Modules
- Chapter 2 - Module Overview
- Chapter 3 - Use the Module in an ArmorBlock System
- Chapter 4 - Install Your Module
- Chapter 5 - Configure the Module for Your EtherNet/IP Network
- Chapter 6 - Configure the Module Using RSLogix 5000
- Introduction
- Set Up the Hardware
- Create the Example Application
- Configure Your I/O Module
- Overview of the Configuration Process
- Add a New Bridge and Module to Your RSLogix 5000 Project
- Use the Default Configuration
- Change the Default Configuration
- Download Your Configuration
- Edit Your Configuration
- Access Module Data in RSLogix 5000
- Configure RSLogix 5000 and the 1756-EN2T Communication Module for CIP Sync
- Chapter Summary and What’s Next
- Chapter 7 - Module Features
- Introduction
- Determine Module Compatibility
- Module Features That Can Be Configured
- Chapter Summary and What’s Next
- Chapter 8 - Using the Module
- Chapter 9 - Interpret Status Indicators
- Chapter 10 - Troubleshoot the Module
- Appendix A - ArmorBlock 2 Port Ethernet Module Specifications
- Appendix B - Module Tags
- Appendix C - 1732E EtherNet/IP ArmorBlock Supporting Sequence of Events Data Tables
- Appendix D - Connect to Networks via Ethernet Interface
- Appendix E - 1732E ArmorBlock I/O Embedded Web Server
- Glossary
- Index
- How Are We Doing?
- Back Cover

Publication 1732E-UM002A-EN-P - March 2010
Module Overview 9
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 time stamps. There are two types of SOE
applications.
First Fault
First Fault measures the time between events with no correlation to events
outside of that system.
Real Time
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 time stamps on I/O allows very accurate first fault detection
making it easy to identify the initial fault that caused machine down time.