BACnet objects and properties: types, identifiers and the priority array

Catalin NegruPublished 6 min read

Part of the BACnet guide

A BACnet object is one point or function inside a device, such as a temperature input, a fan command or a schedule, and a property is one named fact about it: its present value, its name, its units, its status. Every object is addressed by an object type and an instance number, and every property by a numeric identifier, so reading “the supply air temperature” means reading property 85 (Present_Value) of, say, analog input 3 in device 1001.

This page is part of the BACnet guide. For the protocol around the objects, see What is BACnet?; for the frames that carry a read, see BACnet/IP.

The object identifier

An object identifier is 32 bits: a 10-bit object type followed by a 22-bit instance number. Instance numbers run from 0 to 4194302, and 4194303 is reserved to mean “unspecified”. The pair is unique within one device, so two devices can both have an analog input 1.

analog-input 3 type 0, instance 3 0x00000003 analog-value 5 type 2, instance 5 0x00800005 binary-input 12 type 3, instance 12 0x00C0000C device 1234 type 8, instance 1234 0x020004D2

The type occupies the top 10 bits, so the encoded value is type x 4194304 + instance.

Object types

Clause 12 of ASHRAE 135 defines the standard object types. These are the ones a monitoring or integration project meets most:

Type numberObject typeRepresents
0Analog InputA measured value: temperature, pressure, flow
1Analog OutputA commanded value: valve or damper position, speed reference
2Analog ValueA setpoint or calculated number held in the controller
3Binary InputA two-state status: fan proof, filter switch
4Binary OutputA two-state command: start and stop
5Binary ValueA two-state flag or mode held in the controller
8DeviceThe device itself; exactly one per device
13Multi-state InputA status with several named states
14Multi-state OutputA command with several named states
15Notification ClassWhere alarms are sent and at what priority
17ScheduleA weekly and exception schedule
19Multi-state ValueA mode with several named states
20Trend LogA buffer of logged samples

Input objects report what the equipment measures, output objects drive physical outputs, and value objects hold numbers that exist only in software. A vendor may also define proprietary object types, with type numbers from 128 upward.

The data type of Present_Value follows the object type. Analog objects carry a REAL (a 32-bit IEEE 754 float). Binary objects carry an enumeration, inactive (0) or active (1), with optional Inactive_Text and Active_Text properties that say what the states mean. Multi-state objects carry an unsigned integer that starts at 1, not 0, with the State_Text array naming each state.

The properties you read most

IdentifierPropertyMeaning
85Present_ValueThe current value of the point
77Object_NameThe name, unique within the device
28DescriptionFree text set by the installer
117UnitsEngineering units, as an enumeration (analog objects)
111Status_FlagsFour bits summarizing the point’s health
36Event_Statenormal, fault, offnormal, high-limit, low-limit
103ReliabilityWhy the value cannot be trusted, such as no-sensor or over-range
81Out_Of_ServiceTrue when the object is decoupled from its physical input or output
87Priority_ArrayThe 16 command slots of a commandable object
104Relinquish_DefaultThe value used when every slot is empty
76Object_ListIn the Device object: every object the device contains

The standard marks each property of each object type as required or optional. An Analog Input must have Object_Identifier, Object_Name, Object_Type, Present_Value, Status_Flags, Event_State, Out_Of_Service and Units; Description and Reliability are optional. Reading an optional property a device does not implement returns the error unknown-property.

Array properties accept an index. Reading Object_List at index 0 returns the number of elements, and reading index n returns the nth element. On a device with a small maximum APDU and no segmentation, walking the array one element at a time is the only way to get a long object list.

Status flags

Status_Flags is a string of four bits, and it should travel with every Present_Value that feeds an alarm or a report.

BitFlagSet when
0in-alarmEvent_State is anything other than normal
1faultReliability is anything other than no-fault-detected
2overriddenThe point has been overridden by a mechanism local to the device
3out-of-serviceOut_Of_Service is true

A temperature that reads a steady 72.0 with the fault bit set is a failed sensor holding its last value. A point with out-of-service set returns whatever a technician last wrote to it, not what the equipment is doing.

Commandable objects and the priority array

Several systems may want to command the same output: a schedule, an operator, a fire alarm interface, a demand limiting routine. BACnet settles the conflict with a priority array. A commandable object has 16 slots, each empty (NULL) or holding a value, and Present_Value takes the value in the occupied slot with the lowest number.

PriorityAssigned use in the standard
1Manual Life Safety
2Automatic Life Safety
3, 4Available
5Critical Equipment Control
6Minimum On/Off
7Available
8Manual Operator
9 to 16Available

Analog Output, Binary Output and Multi-state Output objects are always commandable. Value objects may be, depending on the device. A WriteProperty request to Present_Value carries an optional priority from 1 to 16; without one, the write goes in at priority 16.

Three consequences catch people out:

  1. A write can succeed and change nothing. If an operator override sits at priority 8, a write at 16 is stored in slot 16 and Present_Value stays where it was. Read Priority_Array to see who holds the point.
  2. A command has to be released, not overwritten. Writing NULL at your priority empties the slot and hands control to the next occupied one. A system that writes a value and never relinquishes it holds the point forever.
  3. When all 16 slots are empty, Present_Value falls back to Relinquish_Default.

Priority 6 is tied to minimum on and off times: a Binary Output with Minimum_On_Time or Minimum_Off_Time configured holds its state at that level until the time expires, which is why a stop command to a compressor may appear to be ignored for a few minutes.

Polling and change of value

A client can get values in two ways. Polling repeats ReadProperty or ReadPropertyMultiple on a timer. Change of value (COV) reverses the direction: the client sends SubscribeCOV once, and the device sends a notification whenever Present_Value or Status_Flags changes. For analog objects the COV_Increment property sets how far the value must move before a notification goes out. COV is optional in a device, and subscriptions have a lifetime, so a subscriber has to renew them.

ReadPropertyMultiple cuts the cost of polling. One request can name many objects and properties, limited by the maximum APDU length of the two devices: 1476 bytes on BACnet/IP, usually 480 on BACnet MS/TP.

How BACnet objects compare with Modbus registers

A Modbus register is a 16-bit number at an address; its meaning, scale and units exist only in the manual. A BACnet object carries its name, units and status with it and can be discovered on the live network. BACnet vs Modbus goes through the difference in detail.

Mapping BACnet objects in ControlCom

In the ControlCom Edge Server’s BACnet client, the Objects tab holds one entry per property read from the controller. Each entry has an Object Type (AnalogInput, AnalogOutput, AnalogValue, BinaryInput, BinaryOutput, BinaryValue, MultiStateInput, MultiStateOutput or MultiStateValue), an Instance Number from 0 to 4194302, and a Property Identifier that defaults to 85, Present_Value. To read a second property of the same object, such as 111 for Status_Flags, add another entry with that identifier. The Topic Property Path selects the platform variable that receives the value, and number objects can be given a Scale, Offset and Decimals.

Writing is off by default. Selecting a Write Variable lets the platform write to the object when a matching command is sent, and Write Priority sets the slot, 1 to 16; left empty, writes use 16.

To find the objects in the first place, the BACnet tool in the Edge Server’s local web interface expands a discovered device, runs ReadPropertyMultiple across its objects and shows a property tree for each one. The BACnet client documentation  covers the object fields and the BACnet tool documentation  covers discovery. The page for controls engineers describes the commissioning workflow.

Each BACnet object you map on the Edge Server becomes a variable in ControlCom Connect that can be trended, alarmed on and placed on a dashboard.