Rockwell Automation 1732E-OB8M8SR EtherNet/IP Dual Port 8-Point SOE Input and Scheduled Output Modules UM - Manual (Page 25)

Rockwell Automation Publication 1732E-UM003B-EN-E - March 2014 15
Chapter
3
Use the Modules in an ArmorBlock System
Introduction This chapter describes how the 1732E ArmorBlock EtherNet/IP Dual Port 8-
Point Sequence of Events Input and Scheduled Output Modules 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 the
following table.
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. The following
table describes the similarities.
Topic Page
Differences Between Module and Standard I/O 15
Similar Functionality to Standard ArmorBlock 15
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.
Only one owner-controller per module While multiple controllers can simultaneously own other digital input
modules, the module only supports a single owner-controller.
Concept Description
Ownership Every module in an ArmorBlock system must be owned by a Logix5000 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.