IoTServa Get Started
Protocol Support

BACnet Integration

Read chillers, air handlers and VAV boxes over BACnet/IP and BACnet MS/TP, with COV subscriptions so changes arrive when they happen.

Standard
ASHRAE 135 / ISO 16484-5
Medium
IP networks (BACnet/IP over UDP, BACnet/SC over secure WebSocket) or RS-485 (MS/TP)
Topology
Peer to peer, routed between networks
Data Model
Objects with properties: Analog Input, Analog Value, Binary, Multi-state, Schedule, Trend Log
A DIN-rail IoT gateway inside a building control cabinet with RS-485 terminals and an Ethernet patch cable

What BACnet Is

BACnet is the open standard most building management systems use to talk to HVAC equipment. Every device exposes objects (a temperature input, a fan command, a schedule) and every object has properties, the most important being present value. Devices announce themselves with Who-Is and I-Am, then answer ReadProperty requests or push changes through COV subscriptions.

Native Address

Device 1204
analog-input,3
present-value
units: degrees-celsius

Node

Tower A > AHU-02 > Supply Air Temperature

13.4°C

How IoTServa Connects BACnet

Discover Devices

Broadcast Who-Is across a BACnet/IP network or a routed range, and list every device with its object list.

Subscribe to Changes

Use COV where the controller supports it, and fall back to scheduled ReadPropertyMultiple polling where it does not.

Write with Priority

Send WriteProperty commands at a chosen priority-array level, and release it cleanly so you never leave an override stuck.

MS/TP and IP Together

Read RS-485 MS/TP trunks through a wired gateway and BACnet/IP controllers on the LAN in the same project.

Typical Jobs

  • Chilled water and AHU monitoring
  • VAV zone temperature and damper trending
  • Schedule and setpoint changes from one console
  • Alarm forwarding from legacy BMS controllers

Plan for These

  • Device instance numbers must be unique across the whole internetwork. Duplicates break discovery and can send reads and writes to the wrong device.

  • MS/TP trunks are slow and shared. Polling too many points starves the bus, so COV and sensible poll groups matter.

  • Writes land in a priority array. Agree who owns which priority before enabling control.

Works Alongside the Others

A site rarely runs a single protocol. The same project can read all eight.

BACnet Questions

Does IoTServa support BACnet/IP and MS/TP?

Yes. BACnet/IP controllers are read over your LAN, and MS/TP trunks are read through a wired RS-485 gateway placed on the trunk. Both end up as the same normalized tags, so a floor of IP controllers and a plant room on MS/TP can sit in one dashboard.

Can IoTServa write to BACnet points?

Yes, at a priority level you choose, and writes can be switched off per site so a monitoring-only project stays read-only. When control is enabled, a priority level can be released cleanly, so an override is never left stuck on a point.

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

BACnet/IP carries BACnet messages over Ethernet and IP networks, usually on UDP port 47808, and crosses subnets through a router or a BBMD (BACnet broadcast management device). BACnet MS/TP runs over RS-485 serial trunks with token passing, so it is slower and shared. Both use the same objects and properties, and many buildings run MS/TP trunks behind a BACnet/IP controller.

What is BACnet COV?

COV means change of value. Instead of polling a point repeatedly, a client subscribes and the device sends a notification when the value changes. For analog points the change must exceed a COV increment, and binary and multi-state points notify on any state change. It cuts traffic on slow networks. Not every controller supports COV, so a reader still needs scheduled polling as a fallback.

Bring Your BACnet Devices. We Will Read Them.

Tell us the make and model of what is on site. We will scope a pilot against your real equipment.

WhatsApp