BACnet in Enture¶
BACnet/IP is the standard protocol of building automation. It is used by air handling units, chillers, VAV controllers, pumps, energy meters and the building management systems that run them. The Enture BACnet connector reads values from BACnet/IP controllers and can send values back to the points that allow it, such as setpoints and on/off commands.
How Enture uses BACnet¶
- A BACnet Device represents one controller, identified by its IP address, port and BACnet device instance number.
- BACnet Parameters map individual points of that controller to data points in Enture. In BACnet, a point is called an object — for example "Analog Input 3" might be a supply air temperature.
Once configured, the Enture edge device at your facility reads each point at the interval you choose — or, for points set to change of value, is told by the controller as soon as the value changes — and streams the values to the platform. Points that are set up for writing can also be sent values from the platform.
What you can read and write¶
| Object type | Typical use | Access |
|---|---|---|
| Analog input | Temperatures, pressures, flow, power | Read only |
| Analog output | Valve positions, damper positions, setpoints sent to the controller | Read, write |
| Analog value | Setpoints and calculated values held in the controller | Read, write |
| Binary input | Run status, alarms, switches | Read only |
| Binary output | Start/stop and enable commands | Read, write |
| Binary value | On/off flags held in the controller | Read, write |
| Multi-state input | Operating mode or state reported by the controller | Read only |
| Multi-state output | Mode or speed commands | Read, write |
| Multi-state value | Mode selections held in the controller | Read, write |
Enture reads the present value of each point.
Network requirements¶
- The edge device reaches each controller directly by its IP address, so the controller must be reachable from the edge device — normally on the same network.
- BACnet/IP normally uses UDP port 47808. If a firewall sits between the edge device and the controller, allow this port in both directions (or the port you set on the device).
- Finding controllers automatically asks the edge device's own network first. Controllers on other networks are found only if you also give an address range and the edge device can reach those addresses — see Finding controllers automatically.
Not available in this version¶
- Controllers on a serial MS/TP network, or on a different network that the edge device cannot reach directly by IP. A search may report such controllers as "behind a BACnet router"; they cannot be added.
- BACnet alarm and event notifications. Values, including binary alarm points, are read like any other point.
Typical setup workflow¶
- Add a BACnet Device — let the edge device find the controllers on its network, or enter a controller's IP address, port and device instance yourself — see Adding a BACnet Device.
- Add BACnet Parameters — read the controller's point list and pick the points you need, import them from a CSV or EDE file, or add them one by one — see Adding BACnet Parameters.
- Write values if needed — see Writing a value or releasing control.
Data flows automatically once the edge device picks up the configuration (within approximately 30 seconds).