Although Priority 8 is the default, objects can be commanded at different priorities in the web interface using the Priority array command. This property opens a window with 16 slots for each priority where you can override and change default values, command priorities, and release priorities. The commanding property will be highlighted in the Priority array command.

The highest present value in the list takes priority over all other commands in the array. For example, if the present value at Priority 4 is commanded but you want to command the present value at Priority 8, you must release Priority 4, Priority 5, Priority 6, and Priority 7 so that Priority 8 becomes the highest present value. Enter a new value in a priority's text field to change the current value. Only numeric, Boolean, and enumerated priority arrays are supported on PXC.A controllers.

When commanding P1 unbundled subpoints, the following rules apply:

  • If you have two BACnet objects representing the same subpoint and they are both commanded at Priority 16, the last command wins.
  • If you have two BACnet objects representing the same subpoint and they are both commanded at any priority between Priority 1-15, they will throw a configuration error.
  • If you have two BACnet objects and one is commanding at any priority between Priority 1-15 and the other is commanding at Priority 16, the command at Priority 1-15 will win.

To release a priority from the Priority array command, select a value, clear the entry, and click .

There are no values at Priority 1-4, so they are not being commanded.

Grey border indicates a read-only priority.
This priority is the highest present value, therefore the object is being commanded at Priority 5.

Dark grey border indicates a writeable priority.

Orange hand indicates a priority is in a manual override state.

No hand indicates that the priority is in the normal operation state.