Understanding Control Interlock
- Last UpdatedNov 02, 2023
- 2 minute read
The interlock field in the analog, status, and multistate tables is related to the Control Interlock feature.
|
Field Name |
Data Type |
Description |
|---|---|---|
|
warn |
oas_boolean_t |
Warn mode. |
|
anaenable |
oas_boolean_t |
Analog interlock enable. |
|
staenable |
oas_boolean_t |
Status interlock enable. |
|
multistaenable |
oas_boolean_t |
Multistate interlock enable. |
|
anaslot |
analogslot |
Interlock Analog. |
|
staslot |
statusslot |
Interlock Status. |
|
multistaslot |
multistateslot |
Interlock multistate. |
|
anastate |
msgstring |
Interlock analog state string. |
|
stastate |
msgstring |
Interlock status state string. |
|
mulstate |
msgstring |
Interlock multistate state string. |
|
stacmdwhitelist |
msgstring |
A comma-separated list of allowable commands for the provided state on a status point. |
When analog, status, or multistate interlock is enabled, Controllers cannot issue commands to analog, status, or multistate points when the configured interlock state string matches the interlock analog, status, or multistate alarm state flag.msgtxt field, respectively.
Warn Mode
When an analog, a status, or a multistate point is in Warn Mode, Controllers receive a command confirmation dialog box if they attempt to issue commands.
Note: Open Platform Communications (OPC) setpoints are not affected by this setting.
The warning message takes the following format:
"'Warning' tag on <command name> command has interlock active for point <point name>:<point description> in state <state name> Confirm Override"
Prevent Mode
When an analog, a status, or a multistate point is in Prevent Mode, the system prevents Controllers from following through with processes that make use of setpoints and function put commands to issue commands to field devices. This also applies to OPC setpoints or digital commands. Prevent Mode is the default mode for Control Interlock.
Note: Placing an analog, a status, or a multistate point into Prevent Mode is the same as placing a "No Command" tag against the point (refer to the AVEVA Enterprise SCADA HMI Controller documentation).
The prevent message takes the following format:
"Command <command name> has interlock active for point <point name>:<point description> in state <state name> Command rejected"