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
About 1732E ArmorBlock Modules 3
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.
Chapter Summary and
What’s Next
In this chapter you were given an overview of the 1732E ArmorBlock family
of modules. The next chapter is an overview of the 1732E EtherNet/IP
ArmorBlock Supporting Sequence of Events module.