BACnet discovery
BACnet discovery tools and workflow
Choose a BACnet discovery tool by the work you need to finish. Use an explorer for direct inspection and writes, a packet analyzer for wire evidence, and an API-first scanner when you need repeatable inventories, semantic tags, or exports. No single tool covers every BACnet transport and field workflow.
Match the tool to the job
Start with the required transport and output. A Windows BACnet explorer, a packet analyzer, and a connector daemon solve different problems.
| Job | Useful tool type | Check before use |
|---|---|---|
| Browse devices and properties by hand | Graphical BACnet explorer such as YABE | Supported datalink, network interface, and write controls |
| Prove what crossed the wire | Wireshark with BACnet filters | Capture point, routed path, and permission to collect traffic |
| Test a BACnet implementation | VTS or bacnet-stack demo clients | Protocol service coverage and build requirements |
| Create a repeatable point inventory | API-first discovery and export tool | Completeness markers, error reporting, and output format |
| Normalize points for analytics | Discovery tool with a semantic model | Tag provenance, correction path, and Haystack compatibility |
A bounded survey sequence
- Confirm the BACnet transport, local interface, UDP port, routed networks, and any BBMD or foreign-device requirement.
- Run broadcast Who-Is on the local broadcast domain. Use a device-instance range only when you have a reason to narrow the request.
- For a known remote IP, run targeted discovery and a directed ReadProperty check. Broadcast and unicast do not prove the same path.
- For each device, read the Object_List length, walk the array by index, and record whether enumeration finished cleanly.
- Read object name, type, units, present value, and status. Keep faults and silent devices visible instead of dropping them.
- Export the inventory with the scan date, tool version, scope, partial-scan limits, and unresolved errors.
Sondwave for BACnet discovery
The isolated BACnet driver supports BACnet/IP broadcast Who-Is, targeted unicast Who-Is, a ReadProperty fallback for known targets that do not answer directed Who-Is, indexed Object_List enumeration, batched reads, scan status, a web reference client, semantic proposals, and Haystack-oriented exports.
Sondwave has been tested with BACnet inventories above 5,000 objects on a small, low-power computer.
It turns discovery results into a persistent point inventory that can be reviewed in the browser or exported for another system.
Tool selection checklist
- Can it reach the BACnet datalink used at this site?
- Does it show a timeout, abort, reject, or partial result by name?
- Can it preserve device instance, object type, object instance, name, unit, and status?
- Can it prove when an inventory is complete instead of only showing a point count?
- Can it export a stable format that the next system can consume?
- If it can write, does it require an explicit priority and keep an audit trail?