Rockwell Automation 1756-IH16ISOE ControlLogix Sequence of Events Module - Manual (Page 18)

Publication 1756-UM528A-EN-P - April 2004
2-2 How Does the Sequence of Events Module Operate in a ControlLogix System?
Similar Functionality to
Standard ControlLogix DC
Input Modules With respect to general module operation in a ControlLogix system,
the Sequence of Events module operates similarly to other
ControlLogix digital input modules in many ways. This chapter
focuses on how the Sequence of Events module’s behavior differs
from that of other ControlLogix digital input modules.
However, you should be aware of aspects in which the Sequence of
Events module is similar to standard ControlLogix digital input
modules. For more information on these similarities, see Table 2.3.
Table 2.3 Ways that a Sequence of Events Module Behave Like Other ControlLogix Digital Input Modules
Concept: Description:
Ownership Every Sequence of Events module in the ControlLogix system must be owned by a Logix5000 controller. This
owner-controller:
• stores configuration data for every module that it owns.
• can be local or remote in regard to the Sequence of Events module’s position.
• sends the Sequence of Events module configuration data to define the module’s behavior and begin
operation with the control system.
This module does not support multiple owner-controllers.
Using RSNetWorx and
RSLogix 5000 The I/O configuration portion of RSLogix5000, v13 or greater, generates the configuration data for each
Sequence of Events module in the control system, whether the module is located in a local or remote chassis.
A remote chassis, also known as networked, contains the Sequence of Events module but not the module’s
owner-controller. Remote chassis can be connected to the controller via a scheduled ControlNet or an
EtherNet/IP network.
Configuration data is transferred to the controller during the program download and subsequently transferred
to the appropriate Sequence of Events modules.
Sequence of Events modules in the local chassis, and modules in a remote chassis that is connected via the
EtherNet/IP network, are ready to run as soon as the configuration data has been downloaded. However, you
must run RSNetWorx for ControlNet to enable Sequence of Events modules in a scheduled ControlNet
chassis.
Running RSNetWorx transfers configuration data to Sequence of Events modules on scheduled ControlNet
and establishes a Network Update Time (NUT) for ControlNet that is compliant with the desired
communications options specified for each module during configuration.
Anytime a controller references a Sequence of Events module in a scheduled ControlNet chassis, you must
run RSNetWorx to configure ControlNet. Follow these general guidelines when configuring Sequence of
Events modules:
1. Configure all Sequence of Events modules for a given controller using RSLogix 5000 and download
that information to the controller.
2. If the module configuration data references a module in a remote chassis connected by scheduled
ControlNet, run RSNetWorx.
3. After running RSNetWorx, perform an online save of the RSLogix 5000 project so the configuration
information that RSNetWorx sends to the controller is saved.
IMPORTANT: You must run RSNetWorx whenever a new module is added to a scheduled ControlNet
chassis. When a module is permanently removed from a remote chassis, we recommend that RSNetWorx be
run to optimize the allocation of network bandwidth.