Unitary | Pre-APOGEE | APOGEE | BACnet | PXC.A |
|---|---|---|---|---|
| ● | ● | ● | ● |
Syntax for PXC.A controllers
RELEAS(cmdPriority)
cmdPriority | A command priority specifier. cmdPriority may be specified as @1 through @16, indicating BACnet priorities 1 (highest) through 16 (lowest). Appending a '+' to the priority specifier will release the specified priority slot and lower. For example, @9+ will release priority slots 9 through 16. If cmdPriority is not specified when writing a commandable object, the program's PPCL Program Priority value shall be used. |
RELEAS(targObjRefs)
targObjRefs | A specifier for the target object(s) of the set operation. Multiple objects may be specified. The same priority slot will be written in each target object. A targObjRef may be passed as an object reference (for example, BAC_7_AO_11, KwMeter). |
Use
The updated RELEAS() statement writes the value null to one or more specified command priority array slots of a specified object instance. RELEAS() has been modified to support BACnet command prioritization and to support releasing multiple priority slots with a single statement.
Notes
- Database migration tools should automate the transformation of Apogee proprietary priorities to BACnet priorities.
- In general, the program should limit itself to commanding at its specified priority as defined by the PPCL Program Priority property.
- If the PXC.A automation station is unable to resolve one or more object references, whether the reference is specified in valueSpec or one of the objrefs, the PPCL line will be marked unresolved.
Syntax for Legacy controllers
RELEAS(pt1,...,pt16)
pt1 through pt16 | Point name to be released to NONE priority. - This parameter can be a any logical point that has a priority array. - This command only works for points in EMER or PDL priority. To release points in OPER or SMOKE priority, the RELEAS(@prior…) command must be used. |
RELEAS(@prior, pt1,...,pt15)
@prior | Defines a specific point priority that the point is being released from. |
pt1 through pt15 | Point name to be released to NONE priority. |
Use
Changes the operational status of a point to NONE priority.
- A maximum of 16 points can be changed with one RELEAS command.
- A maximum of 15 points can be defined with one RELEAS(@prior…) command.
An LAO or LDO point that is used in a RELEAS statement can generate multiple entries in the Trend Data Report if a command statement such as SET, =, ON, or OFF is used on the same point at the same time.
Example 1
110 IF(TEMP.NE.ALARM.AND.PT2.NE.@NONE)THEN RELEAS(@EMER, PT2)
In this example, PT2 will only be released if its priority is not equal to NONE and TEMP is not in alarm.
Example 2
120 RELEAS(@SMOKE, PT1, PT2, PT3)
In this example, all three points will be released to NONE priority if they currently have a priority of SMOKE, EMER, or PDL. If any point is in OPER priority, it will not be released.
Notes
- With APOGEE and pre-APOGEE firmware, always use a priority at least as high as the one that the point will be in to ensure proper release. If the point has been commanded from the keyboard, it will require an @OPER entry to release the priority of the point to NONE.
- With BACnet firmware, the RELEAS(@prior, pt1,…,pt15) command releases the BACnet slot which is mapped to the stated APOGEE priority, but it may not release all the way to NONE priority. The BACnet Command Priority levels must be emptied to allow lower priority levels to control the point.
The standard BACnet Priority Array rules control the @prior release process as follows:
- If a value exists in a higher priority slot than the slot mapped to @prior, the value is not released.
- If the slot mapped to @prior is the highest slot, the value is released. The new value is determined by the presence, in order from higher to lower priority levels, of values in the slots below.
- If no values exist in the lower priority slots, the relinquished default value is used.