BACnet Protocol Basics: A Field Guide to Objects, Instances & Network Communication

BACnet (Building Automation and Control networks) is an international standard (ISO 16484-6) developed by ASHRAE, designed to facilitate communication between different building automation and control systems. By providing a standardized language, it allows devices from various manufacturers to interoperate seamlessly — which is essential for energy-efficient building management.

Core Concepts of BACnet

1. The BACnet Device

Every BACnet-compliant system consists of Devices. A device is essentially a physical or logical entity on the network — for example, a thermostat, a lighting controller, or an air handling unit (AHU) controller. Every device is represented by a single Device Object, which must have a unique identifier across the entire BACnet internetwork.

2. Objects: The Building Blocks of Data

BACnet uses an object-oriented approach to represent data. Instead of raw memory addresses, it organizes information into "objects" that define what the data is and how it behaves. Standard object types include:

• Analog Input / Output (AI/AO): Represents sensors or actuators with continuous values, such as temperature readings.
• Binary Input / Output (BI/BO): Represents on/off or digital states, such as switch or valve status.
• Analog / Binary Value: Used for software-based setpoints or parameters.
• Trend Log / Schedule: Specialized objects for time-based data or historical recording.

3. Properties and Instances

Every object contains a set of Properties — such as Present_Value, Object_Name, and Reliability — that describe its current state.

Within a device, each object is uniquely identified by an Object Type combined with an Instance Number. For example, two temperature sensors in the same device might be identified as Analog Input 1 and Analog Input 2. This combination must be unique within that specific device.

Network Communication

BACnet does not rely on a single physical medium. Instead, it defines a standard "application layer" that can operate over various networking technologies.

Data Representation

When a system requests data, it asks for specific properties of a specific object within a specific device. Because the objects are "network-visible," the requesting device does not need to know the controller's internal programming or hardware layout — it simply interacts with the object.

Interoperability

Because the BACnet standard defines exactly how objects and properties must behave, a third-party software system can read an Analog Input from a controller made by Manufacturer A and write to an Analog Output on a controller made by Manufacturer B — without needing proprietary drivers for each.

BACnet/IP

For modern building networks, BACnet is frequently encapsulated within IP (Internet Protocol) frames. This allows BACnet messages to traverse standard enterprise Ethernet and Wi-Fi infrastructure, often requiring specialized routers or Packet-Assembler-Disassemblers (PADs) to connect different physical subnets.

Summary Table

Concept	Description
Device	A unique, network-accessible controller with a globally unique Device Instance Number.
Object	A standardized way to represent a piece of data — sensor reading, actuator command, setpoint, etc.
Instance	A unique number assigned to an object type within a device to distinguish it from others of the same type.
Property	Attributes of an object (e.g., Present_Value, Object_Name) that define and describe its current state.

← Back to all articles