BACnet (Building Automation and Control Networks) is one of the most widely used communication protocols in building automation systems. It enables devices from different manufacturers, such as HVAC controllers, energy meters, fire panels, and lighting systems, to communicate seamlessly. At the core of this communication are BACnet objects, which represent real-world data and control points.
Understanding the major BACnet objects useful in integration is essential for system integrators, consultants, and facility managers aiming to build reliable, scalable, and interoperable automation solutions.
What Are BACnet Objects?
BACnet objects are standardized data structures that represent physical devices, sensor readings, control points, and system logic within a BACnet network. Each object contains properties such as value, status, units, and priority, allowing systems to exchange information consistently.
During system integration, BACnet objects make it easier to:
- Map data between different systems
- Monitor and control equipment
- Integrate legacy and modern automation platforms
Following is general BACnet Object Types:
| Datapoint Type / BACnet Object Type | Object Type ID | Brief Description |
| BACnet_AI | 0 | Analog input. Defines a standard object whose properties represent the externally visible characteristics of an analog input. |
| BACnet_AO | 1 | Analog output. Defines a standard object whose properties represent the externally visible characteristics of an analog output. |
| BACnet_AV | 2 | Analog value. Defines a standard object whose properties represent the externally visible characteristics of an analog value. |
| BACnet_BI | 3 | Binary input. Defines a standard object whose properties represent the externally visible characteristics of a binary input. |
| BACnet_BO | 4 | Binary output. Defines a standard object whose properties represent the externally visible characteristics of a binary output. |
| BACnet_BV | 5 | Binary value. Defines a standard object whose properties represent the externally visible characteristics of a binary value. |
| BACnet_MSI | 13 | Multi-state input. Defines a standard object whose Present_Value (present value) can take integer values. |
| BACnet_MSO | 14 | Multi-state output. Defines a standard object whose output is an integer value. |
| BACnet_MSV | 19 | Multi-state value. Defines a standard object whose properties represent the externally visible characteristics of a multistage value. |
| BACnet_Accumulator | 23 | Addition of impulse data of measurement devices over the time. Used for balancing, statement and energy performance management (for interval mass counter see Pulse Converter). |
| BACnet_Calendar | 6 | Calendar. Defines a standard object that is used to define a list of calendar entries (date list). |
| BACnet_Schedule | 17 | Time plan. Defines a standard object that is used to define a periodic timeplan, also with optional exceptions on arbitrary days or on arbitrary dates, which can recur within a certain period of time. |
| BACnet_NOC | 15 | Alarm class. Defines a standard object that contains the necessary information for the distribution of event alarms with BACnet systems. |
| BACnet_Program | 16 | Object for program controlling in a BACnet device (e.g. load and start). |
| BACnet_PulseConverter | 24 | Object for impulse conversion for mass counting in defined time intervals. |
| BACnet_TrendLog | 20 | Trend Log. Archives a property of a referenced object and, when predefined conditions are met, saves the value of the property and a timestamp in an internal buffer for subsequent retrieval. |
| BACnet_Device | 8 | BACnet device. Defines a standard object whose properties represent the externally visible characteristics of a BACnet device. |
Why BACnet Objects Are Critical for System Integration
BACnet objects provide a common language for integration across different systems and vendors. Proper use of standard objects ensures:
- Faster and cleaner system integration
- Easier protocol conversion
- Improved system scalability
- Reduced commissioning and troubleshooting time
They also simplify integration with non-BACnet protocols when using gateways.
ProtoConvert’s Role in BACnet Integration
As automation systems grow more complex, integrating BACnet with other protocols becomes a key challenge. ProtoConvert plays a crucial role by providing reliable protocol gateways and converters that simplify BACnet-based integrations.
ProtoConvert solutions help integrators:
By acting as a bridge between systems, ProtoConvert ensures that BACnet objects are used effectively within broader automation and IoT architectures.
Understanding the major BACnet objects useful in integration is fundamental to building efficient, interoperable automation systems. From basic analog and binary objects to advanced multi-state values, each object type plays a vital role in monitoring, control, and system logic.
