Discover Devices
Broadcast Who-Is across a BACnet/IP network or a routed range, and list every device with its object list.
Read chillers, air handlers and VAV boxes over BACnet/IP and BACnet MS/TP, with COV subscriptions so changes arrive when they happen.

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.
site.tower-a.ahu-02.supply-air-temp
13.4°C
Broadcast Who-Is across a BACnet/IP network or a routed range, and list every device with its object list.
Use COV where the controller supports it, and fall back to scheduled ReadPropertyMultiple polling where it does not.
Send WriteProperty commands at a chosen priority-array level, and release it cleanly so you never leave an override stuck.
Read RS-485 MS/TP trunks through a wired gateway and BACnet/IP controllers on the LAN in the same project.
Device instance numbers must be unique across the whole internetwork. Duplicates cause silent misreads.
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.
Yes. BACnet/IP controllers are read over your LAN, and MS/TP trunks are read through a wired RS-485 gateway.
Yes, with a chosen priority level, and writes can be switched off per site so a monitoring-only project stays read-only.
Tell us the make and model of what is on site. We will scope a pilot against your real equipment.