> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-software/configure/interface-options/facility-management-interfaces/bacnet-overview/bacnet-basic-setup-requirements.md).

# BACnet - basic setup requirements

Prepare Controller 6000 and BACnet devices for a BACnet integration.

## About BACnet

Gallagher's BACnet Protocol Interface gives Command Centre bi-directional communication with BACnet-compatible devices. Specified **Controller 6000s act as BACnet clients** to read and write BACnet Object values.

* **Inbound:** monitor BACnet objects for state changes and raise alarms.
* **Outbound:** change BACnet object state in response to events.

This makes Command Centre the central repository for all site alarms (boiler, chiller, and aircon failures, and maintenance alarms) with full event and alarm management. It also supports access-driven environment control for energy savings, such as lighting and aircon that come on with a valid badge and shut down when there is no movement.

BACnet is supported on Command Centre **v8.10 through v9.40** (every version).

## Basic setup requirements

Third-party BACnet systems need hardware so the Gallagher controller can monitor and command them. Command Centre hardware (IO, readers, doors) **cannot** be monitored by other BACnet systems.

* The Controller using the BACnet customisation must be on the **same subnet** as the BACnet devices.
* The Controller's **BACnet Device ID is derived from its MAC address**. The message *"The BACnet Device ID is already in use by another Controller"* means it is not unique.
* The Controller 6000 broadcasts the BACnet Device ID (configured on the **Setup tab** of the BACnet Device in External Systems). The third-party BACnet should respond with its IP. If it does not, the device will not come online, which is usually a network issue.
* Web-browsing the controller shows received IPs. For example, **Address Count 3/255** means 3 configured BACnet devices have broadcast the ID and received an IP. **255 is the maximum** configurable.

***

🔗 **Related**

* [BACnet - Limitations](/knowledge-hub/products/cc-software/configure/interface-options/facility-management-interfaces/bacnet-overview/bacnet-limitations.md). What BACnet cannot do.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/products/cc-software/configure/interface-options/facility-management-interfaces/bacnet-overview/bacnet-basic-setup-requirements.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
