Module inhibiting -15, Module inhibiting – Rockwell Automation 1756-IH16ISOE ControlLogix Sequence of Events Module User Manual

Page 67

Advertising
background image

Publication 1756-UM528A-EN-P - April 2004

Using the Sequence of Events Module Features 5-15

Module Inhibiting

With module inhibiting, you can indefinitely suspend a connection
between an owner-controller and a Sequence of Events module.
This process can occur in the following way:

• You write configuration for a Sequence of Events module but

inhibit the module to prevent it from communicating with the
owner-controller. In this case, the owner-controller does not
establish a connection and configuration is not sent to the
module until the connection is uninhibited.

The following examples are instances where you may need to use
module inhibiting:

• You want to FLASH upgrade your module. We recommend

you:

a. Inhibit the module.

b. Perform the upgrade.

c. Uninhibit the module.

• You are using a program that includes a module that you do

not physically possess yet, but you do not want the controller
to continually look for a module that does not exist yet. In
this case, you can inhibit the module in your program until it
physically resides in the proper slot.

You can inhibit your Sequence of Events module on the
Connection tab in RSLogix 5000, as shown in the example below.

Click on this box to inhibit
or uninhibit the module

Advertising
This manual is related to the following products: