BACnet — Building Automation and Control Networks is a vendor-independent communication standard developed specifically for building automation and control systems. BACnet enables equipment from different manufacturers to exchange information for HVAC, lighting, energy management, access control, fire systems and other building automation applications.

In simple terms: BACnet gives thermostats, controllers, sensors, air-handling units, meters and HVAC drives a common way to describe their data and communicate with a building-management system. It is not limited to one cable type or one manufacturer.

BACnet is standardized as ANSI/ASHRAE Standard 135 and internationally as ISO 16484-5. The current BACnet International glossary identifies the current protocol standard as ANSI/ASHRAE 135-2024.

When was BACnet developed?

The ASHRAE committee that developed BACnet first met in 1987. After several years of development and public review, BACnet was approved and published as ANSI/ASHRAE Standard 135-1995.

Its purpose was to reduce dependence on closed manufacturer-specific building networks and create a standardized method for products from different suppliers to interoperate.

How does BACnet represent data?

One of the most important characteristics of BACnet is its object-oriented data model. A BACnet device presents its information as standardized objects with defined properties rather than only as anonymous register numbers.

Common BACnet object types include:

Analog Input — AI: Temperature, pressure, humidity, flow or another analog measurement.
Analog Output — AO: Analog control output.
Analog Value — AV: Analog software value that does not have to represent a physical I/O terminal.
Binary Input — BI: Two-state input such as open/closed.
Binary Output — BO: Two-state control output.
Binary Value — BV: Software-based binary value.
Multi-state objects: Values with more than two operating states.
Schedule: Time-based operating schedules.
Calendar: Calendar and special-day information.
Trend Log: Historical logging of process values.
Notification Class: Alarm and event notification management.
Device: Describes the BACnet device itself and its capabilities.

For example, room temperature from an industrial sensor can be presented as an Analog Input object. BACnet can also associate properties such as engineering units, status and alarm information with that object.

What is a BACnet property?

Each BACnet object contains properties that describe its value and behaviour. An Analog Input can contain properties such as Present_Value, Units and Status_Flags.

This is useful when integrating measurements such as temperature or pressure, because the supervisory system can work with structured information rather than interpreting an unexplained raw integer.

What are BACnet services?

BACnet services define how devices discover each other, read and write information, report changes and generate alarms.

ReadProperty: Reads a property from a BACnet object.
WriteProperty: Writes a supported property.
Who-Is: Searches for BACnet devices.
I-Am: Announces a device in response to discovery.
COV — Change of Value: Reports selected changes without requiring constant polling.
Alarm and Event services: Communicate alarm and event information.

COV can be especially useful in a large automation system. Instead of a supervisory controller continuously asking hundreds of devices for the same value, a device can notify subscribers when a relevant value changes.

What does BACnet mean in HVAC?

HVAC is one of BACnet's primary application areas. Air-handling units, chillers, boilers, pumps, fans, VAV controllers, room controllers and thermostats can exchange data through one BACnet building-management architecture.

For example, a room temperature sensor can provide feedback to a controller, which calculates the required heating or cooling demand and sends a new command to an HVAC variable frequency drive.

A practical example is the ABB ACH580 HVAC drive, which supports BTL-certified BACnet MS/TP and can support BACnet/IP through appropriate configurations.

Legacy HVAC installations may also include products such as the Schneider / Telemecanique Altivar 61, which was designed for fan and pump applications and supported major building-automation networks including BACnet.

How is BACnet used with sensors?

A smart BACnet sensor or transmitter can publish temperature, humidity, pressure, indoor-air-quality or other process measurements directly as BACnet objects.

A conventional 0–10 V, 4–20 mA, NPN or PNP sensor does not need to contain BACnet itself. It can connect to a local controller or I/O module, and that controller can expose the measured value to the BACnet network.

This is common with pressure and differential-pressure transmitters used for duct pressure, filter monitoring, pump systems and air-flow control.

What does a BACnet controller do?

A BACnet controller is normally more than a communication gateway. It can execute local logic, PID loops, schedules, alarms and control sequences while sharing its data with other BACnet devices.

For example, a controller can read temperature, pressure and CO₂ values, calculate demand and control valves, dampers, pumps and fans. These devices form part of the wider family of electronic control devices.

Can a PLC use BACnet?

Yes. A PLC with native BACnet support or a suitable BACnet communication module/gateway can exchange information with a building-automation system.

A machine PLC and a building controller are not necessarily designed for the same task. PLCs are often optimized for fast sequential machine control, while BACnet controllers are commonly optimized for HVAC, energy and building-control applications.

How are HMI and SCADA systems used with BACnet?

BACnet object values can be shown on an HMI panel or building-management workstation as temperatures, fan states, setpoints, energy values and alarms.

Larger installations can also integrate BACnet information into a SCADA system for visualization, trending, alarms and reporting.

Is BACnet only for HVAC?

No. BACnet was designed for building automation broadly, including HVAC, lighting, access control, elevators, energy management, security and fire-detection applications.

Energy meters, intelligent breakers and power-monitoring devices can provide information to a BACnet BMS. Their local electronics may still require suitable industrial power supplies.

Conventional contactors, relays and switchgear are not automatically BACnet devices. Their states can be connected to BACnet I/O or intelligent motor-control equipment where required.

What is BACnet/IP?

BACnet/IP — B/IP transports BACnet messages over IP network infrastructure. It is widely used for controllers, servers, gateways and other higher-level building-automation equipment.

BACnet/IP is commonly carried over standard Ethernet infrastructure using switches, routers, IP addresses and subnetting.

BACnet and Ethernet are not the same technology. Ethernet provides lower-layer networking, IP handles network addressing and routing, while BACnet defines building-automation objects, services and application behaviour.

Does BACnet/IP use TCP or UDP?

Classic BACnet/IP uses UDP/IP messaging. It is incorrect to describe BACnet/IP as choosing between TCP and UDP according to whether speed or reliability is more important.

BACnet International defines B/IP specifically as the BACnet MAC layer that transports BACnet messages using UDP/IP.

A newer BACnet networking option called BACnet/SC — Secure Connect uses a different architecture based on secure WebSocket connections and TLS.

Which port does BACnet/IP use?

The standard default BACnet/IP UDP port is 47808. In hexadecimal this is 0xBAC0.

Other UDP port values can be configured in certain BACnet/IP designs, so troubleshooting should include both the device IP configuration and its BACnet UDP-port configuration.

Does BACnet use IP addresses?

BACnet/IP devices use normal IP addressing, but the IP address is not the same as the BACnet device identity.

Every BACnet Device object also has a Device Instance. Device Instance values must be unique within the BACnet internetwork.

It is therefore possible for Ethernet and IP connectivity to work while BACnet discovery still behaves incorrectly because two devices have duplicate Device Instance values.

How do Who-Is and I-Am work?

Who-Is and I-Am are fundamental BACnet discovery services.

A controller or workstation can send a Who-Is request to discover BACnet devices. Appropriate devices respond with an I-Am message describing their BACnet identity.

This allows a BMS commissioning tool to discover devices instead of requiring every point to be entered manually.

What is a BBMD?

BBMD — BACnet Broadcast Management Device is used in BACnet/IP systems that span more than one IP subnet.

Some BACnet operations depend on broadcast traffic. Normal IP routers do not forward local broadcasts between subnets, so BBMDs forward the required BACnet broadcasts between configured BACnet/IP subnets.

An incorrect BBMD or Broadcast Distribution Table configuration can cause device-discovery failures, duplicate traffic and unnecessary broadcast loading.

What is a BACnet Foreign Device?

A BACnet/IP device located outside the normal BACnet/IP subnet structure can register with a BBMD as a Foreign Device.

Foreign Device Registration — FDR can be useful for a remote workstation or service tool that needs temporary participation in a BACnet/IP system.

What is BACnet MS/TP?

BACnet MS/TP — Master-Slave/Token-Passing, now commonly described with manager/subordinate terminology is the serial BACnet data-link commonly implemented over EIA-485 / RS-485.

MS/TP remains common in field-level devices such as thermostats, VAV controllers, fan-coil controllers and HVAC drives.

Manager-capable devices pass a token around the serial network. A manager with the token can initiate eligible communication before passing control onward.

BACnet MS/TP and Modbus RTU can both use RS-485 electrical signalling, but they are completely different application and framing protocols.

What is the difference between BACnet/IP and BACnet MS/TP?

BACnet/IP is normally used on IP/Ethernet networks and is well suited to larger controllers, workstations, gateways and building-backbone communication.

BACnet MS/TP provides a cost-effective RS-485 field bus and is widely used for room controllers, VAV boxes, thermostats and similar building devices.

A real building can use both at the same time. BACnet/IP can form the backbone while BACnet routers connect multiple MS/TP field segments below it.

What is BACnet/SC — Secure Connect?

BACnet/SC is the secure IP networking option added to BACnet for modern IT environments.

BACnet/SC uses WebSockets and TLS to provide peer authentication, encryption and reliable connection-oriented communication between BACnet devices.

Unlike classic BACnet/IP broadcast-oriented architectures, BACnet/SC uses secure connections and hub-based communication. Certificate management therefore becomes an important part of commissioning.

BACnet/SC does not replace BACnet/IP or MS/TP in every installation; it provides another BACnet data-link option for projects where cybersecurity and IT-network integration are important.

Is BACnet secure?

A working BACnet network is not automatically a secure network. Segmentation, firewall rules, engineering-station security, user access and device-management practices remain important.

BACnet/SC adds standardized authentication and encryption for suitable IP-based BACnet systems, but protocol security is only one part of the cybersecurity architecture.

What is the difference between BACnet and Modbus?

BACnet and Modbus are both widely used in automation, but their data models are significantly different.

BACnet uses objects, properties and services and includes building-oriented functions such as schedules, alarms, trend logs and device discovery.

Modbus uses a simpler data model based primarily on coils, registers and function codes and is common in PLCs, drives, meters, power equipment and industrial field devices.

For example, a VFD may expose motor current as a holding register in Modbus, while a BACnet implementation can expose the same information as a named Analog Value object with associated engineering properties.

Can Modbus be converted to BACnet?

Yes. A protocol gateway can map Modbus registers to BACnet objects and provide bidirectional integration where supported.

This is common when a building-management system uses BACnet but pumps, meters or drives use Modbus RTU or Modbus TCP.

A gateway still needs correct point mapping. Register address, data type, scaling and read/write behaviour must be associated with the appropriate BACnet object and property.

Can BACnet be used for servo and high-speed motion control?

BACnet can monitor motors, drives and equipment status, but it was not designed as the primary microsecond-class synchronized motion network for multi-axis servo systems.

High-performance motion control applications normally use networks such as EtherCAT, Sercos or other dedicated real-time motion technologies.

BACnet can still be used at a supervisory level to monitor energy consumption, HVAC interaction or machine-room environmental conditions around those systems.

What is BTL Certification?

BTL — BACnet Testing Laboratories manages BACnet product conformance testing and certification under BACnet International.

A BTL-listed product has been independently tested against defined BACnet requirements. This can reduce integration uncertainty in multi-vendor projects, although correct project configuration is still required.

What is a BACnet PICS?

PICS — Protocol Implementation Conformance Statement documents the BACnet objects, services and capabilities implemented by a particular BACnet product.

A statement such as “supports BACnet/IP” does not mean the device supports every BACnet object or service. The PICS should be checked when a project depends on a specific function such as COV, schedules, alarms or writable objects.

Is BACnet open source?

The terms open standard and open-source software should not be confused.

BACnet is an open, vendor-independent communication standard maintained by ASHRAE. It is not a proprietary building protocol owned for exclusive implementation by one automation manufacturer.

Individual BACnet software stacks may be commercial, proprietary or open source. BACnet International itself has also released an open-source BACnet/SC reference implementation, but that does not mean the BACnet standard itself is simply a software source-code project.

What will replace BACnet?

There is currently no single announced protocol intended to replace BACnet. BACnet continues to evolve through revisions and addenda rather than remaining frozen as a legacy HVAC technology.

The publication of ANSI/ASHRAE Standard 135-2024, continued BACnet/SC development and ongoing certification activity show that the standard remains actively maintained.

What OSI layer is BACnet?

It is too simplistic to say that “BACnet is only an OSI application-layer protocol.” BACnet defines a rich application layer with objects and services, but the BACnet architecture also defines its own network layer and standardized data-link options such as BACnet/IP and MS/TP.

In practice, engineers normally discuss the BACnet application model separately from the Ethernet, IP, RS-485 or Secure Connect technology carrying the messages.

Why does a BACnet system fail to communicate?

First determine which BACnet data-link is being used: BACnet/IP, BACnet MS/TP or BACnet/SC. Troubleshooting steps differ substantially.

For BACnet/IP, check the IP address, subnet mask, BACnet UDP port, Device Instance and IP-subnet architecture.

If devices can be discovered on the local subnet but not across another subnet, inspect the BBMD / broadcast-distribution configuration.

For BACnet MS/TP, verify baud rate, MAC address, RS-485 polarity, termination and network-manager parameters.

If a device can be discovered but a specific value or command is unavailable, check whether the required object, property or service is actually listed in the manufacturer's PICS.

Also inspect device power. A controller, gateway or HVAC drive that repeatedly resets because of an unstable 24 VDC power supply can appear to have an intermittent network fault.

Practical BACnet troubleshooting checklist

1. Is the device using BACnet/IP, BACnet MS/TP or BACnet/SC?

2. Is every BACnet Device Instance unique?

3. For BACnet/IP, are IP address, subnet and UDP-port settings correct?

4. Does the IP architecture require BBMD or Foreign Device Registration?

5. For MS/TP, are baud rate, MAC address and RS-485 wiring correct?

6. Does the device PICS support the required object, property and service?

7. For BACnet/SC, are certificates and hub connections healthy?

8. Are controller, sensor, gateway and drive power supplies stable?

Related Building and Industrial Communication Pages

Building Automation · Industrial Communication · Ethernet · Modbus

Related Field and Control Equipment

PLCs · HMI Panels · SCADA · Sensors · Pressure Sensors · AC Drives and VFDs · ABB ACH580 HVAC · Altivar 61 HVAC · Controllers · Power Supplies · Switchgear · Servo Systems · Motion Control