supporting Sequence of Events

11 Publication 1732E-UM002A-EN-P - March 2010
3
Use the Module in an ArmorBlock System
Introduction
This chapter describes how the 1732E EtherNet/IP ArmorBlock Supporting
Sequence of Events module operates in an ArmorBlock system.
Differences Between
Module and Standard I/O
In many aspects, the module behaves the same as other ArmorBlock digital
input modules. However, the module offers several significant differences
from other EtherNet/IP ArmorBlock digital input modules, including those
described in the following table.
Similar Functionality to
Standard ArmorBlock
With respect to general module operation in an ArmorBlock I/O system, the
module operates similarly to other ArmorBlock, single and dual port
EtherNet/IP I/O modules in many ways. This chapter focuses on how the
module’s behavior differs from that of other ArmorBlock I/O modules.
However, you should be aware of aspects in which the module is similar to
Topic Page
Differences Between Module and Standard I/O 11
Similar Functionality to Standard ArmorBlock 11
Difference Description
Additional data produced for controller The module produces 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 module produces 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 This module has an internal clock that is synchronized with a master clock using CIP Sync.
This clock is used for time stamping inputs.
Only one owner-controller per module While multiple controllers can simultaneously own other digital input modules, the module
only supports a single owner-controller.
No listen-only connections Controllers cannot make listen-only connections to the module. All connections between
the module and its owner-controller are direct connections.