Latching of alarms, Module inhibiting, Latching of alarms module inhibiting – Rockwell Automation 1756-OF8I ControlLogix Eight-channel Isolated Analog I/O Modules User Manual
Page 26

26
Rockwell Automation Publication 1756-UM540A-EN-P - May 2014
Chapter 2
ControlLogix Isolated Analog I/O Module Features
Latching of Alarms
This feature latches a module alarm in the set position once the alarm is triggered.
The alarm remains on, even if the condition causing it to occur disappears, until
the alarm is unlatched.
To see where to latch alarms, see
Module Inhibiting
This feature suspends the connection between an owner-controller and a
module. This process can occur in either of the following ways:
•
You write configuration for an I/O module but inhibit the module to
prevent it from communicating with the owner-controller.
In this case, the owner does not establish a connection and configuration is
not sent to the module until the connection is uninhibited.
•
A controller owns a module and has downloaded configuration to it. Data
is currently being exchanged over the connection between the devices.
In this case, when you inhibit the module and the owner-controller
behaves as if the connection to the module does not exist.
IMPORTANT
You must manually unlatch the alarm. You can unlatch the alarm, by using one
of the following methods:
• While the project is online, click the Alarm Configuration tab on the
Module. Then click Unlatch to unlatch a specific alarm or Unlatch All to
unlatch all alarms.
• Change the module output tag for the alarm that you want to unlatch. For
example, the Ch[x].LLAlarmUnlatch tag to unlatch a Low Low Alarm.
For more information on module tags, see Appendix A,
Module Tag Definitions on page 173
.
• Use a CIP Generic message.
For more information how to use a CIP Generic message, see Rockwell
Automation Knowledgebase article #63046, How to Reset Latched Status
of an Analog Module. You can access the article at: (Login required)
IMPORTANT
Whenever you inhibit an output module, it enters Program mode and all
outputs change to the state configured for the Program mode. For example,
if an output module is configured so that the state of the outputs go to zero
(0) during Program mode, whenever that module is inhibited, the outputs
go to zero (0).