Interlock Commands - Metasys - LIT-12011942 - Software Application - Metasys Open Data Server - 10.1

Metasys Open Data Server Help

Product
Building Automation Systems > Databases and Data Servers > Metasys Open Data Server
Document type
User Guide
Document number
LIT-12011942
Version
10.1
Revision date
2019-10-14

The table below lists the commands supported by the Interlock.

Table 1. Interlock Commands

Command Name

Parameters

Description

Disable

None

Locks out all outputs and prevents the Interlock functionality.

Enable

None

Ensures object reacts to any changes it may have missed while it was disabled, and returns it to normal operation.

Operator Override

The value to be written to the Present Value attribute. This parameter has a True or False data type.

Updates the Present Value at Command Priority Operator Override.
Important: The Operator Override command sends the specified command to the internal NxE object, which is then only sent to the field device when one of the following conditions is met: a) NOT Local Control and NOT Out Of Service, or b) NOT Local Control and after issuing the In Service command.

Release Operator Override

None

Releases Command Priority Operator Override from Present Value.

Re-command

None

Reissues the commands for the current state.

Release

Attribute name

Command priority

Releases the identified command priority from the specified, writable attribute, and allows it to be controlled by the

next highest priority.

Release All

Attribute name

Releases Command Priorities 3 through 16 from the specified, writable attribute. Command Priorities1 and 2 remain.
Note: The Release All command may not cause an immediate return to automatic operation. The Release All command clears all command priorities, including those that come from applications and features. When this happens, the output point goes to its Relinquish Default condition. In some cases, the application or feature may have sent a command that does not match Relinquish Default. In this instance, the output point does not end in the state that the applications or features intended. This situation can cause unexpected operation to occur; for example, a space could overcool or overheat, a fan might run longer than expected, and so on. If an operator has overridden an input, use the Release Operator Override command.