> 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/configuration-client/site-installation/hardware/configuring-hbus-devices.md).

# Configuring HBUS Devices

### Introduction

Controller 6000s and Controller 7000s Single Door that are on-line and configured for HBUS (in the **RS-485 Bus 1** or **2** fields on the **Setup** tab), will auto-detect HBUS devices on the **HBUS Devices** tab. There are three ways of using the auto-detection functionality, as follows:

* **Plug-and-play.** Connect an HBUS device to a Controller, which gets auto-detected in Command Centre.
* **Partial pre-configuration.** Create an HBUS device in Command Centre. Assign it to a Controller with NO serial number. Connect an HBUS device to the Controller.
* **Full pre-configuration.** Create an HBUS device in Command Centre. Assign it to a Controller with the correct serial number. Connect an HBUS device to the Controller.

**Note:** HBUS Readers contain a list of valid facility codes. The card type and facility code must exist in Command Centre before the reader will pass the card read to the Controller.

***

### Configuration

Perform the appropriate procedure below for auto-detection functionality in Gallagher Configuration Client:

<details>

<summary>Plug-and-play</summary>

1. Physically connect an HBUS device to the Controller's HBUS port, and power on the device.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-8cd8eb225e0dee8bdc6d7ffc009855cd31316253%2Fftc6000_detectedhbusdevices.png?alt=media)

   Within 20 seconds a detected item displays in Command Centre, on the Controllers **HBUS Devices** tab under the Bus node, (i.e. RS485 port) it is detected on. The item will have the correct icon for the type of device detected, and the item name displays as:

   *\<Item type detected> \<serial number detected>.*
2. **Right click** on the detected item and select **Use this device**.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-4c0d59766083bcbb77ca433a1439a1288938fe05%2Fftc6000_detectedhbusdevices_usethisdevice.png?alt=media)

   The properties for a new Command Centre item, matching the type of HBUS device detected displays, with the default name:

   *\<Controller name> - \<Item type> \<number>*

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-e1f057a2484897abc3c9b1dd600012d78aa668a2%2Fhbusreader.png?alt=media)

   The items **Event Response** tab is populated with the same Alarm Zone as the hosting Controller, and the **Connections** tab is populated with the hosting Controller and the serial number of the detected HBUS device.

   **Note:** Other tabs for the item contain the default settings for a new item of that type.
3. Click the **OK** button.

   The new item is saved and displays on the **HBUS Devices** tab of the Controller and on the **Hardware** List Window with the new name entered.

</details>

<details>

<summary>Partial pre-configuration</summary>

1. Create a new HBUS device. Either:
   * from the **Hardware** List Window, right click and select **New\...HBUS Devices**, OR
   * from the **HBUS Devices** tab of the Controller the device is to be assigned to, right click in the grid and select **New\...**
2. Click the **Event Response** tab of the HBUS device, and enter an Alarm Zone.
3. Click the **Connections** tab of the HBUS device.
4. Assign it to a Controller by selecting the appropriate one from the **Controller** drop-down list, and click the **Apply** button.
5. Open the properties of the Controller you have assigned the HBUS device to, and click the **HBUS Devices** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-e47c6a04b37fbaa4667c6032c4b59ade70d98332%2Fftc6000_detectedhbusdevices1.png?alt=media)

   The new item appears under the "Undetected devices" node on the Controllers **HBUS Devices** tab, and below the Controller on the **Hardware** List Window. In both places, the items icon has the unconfigured blue jigsaw overlay.
6. Physically connect an HBUS device of the same type to one of the Controllers RS485 (HBUS) ports.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-a6877de16374534ba6362b76cd15e736ed815a70%2Fftc6000_detectedhbusdevices2.png?alt=media)

   The device is auto-detected and a detected item displays on the Controllers **HBUS Devices** tab under the Bus node that the device was detected on. The items name will display as: *\<Item type detected> \<serial number detected>*.
7. Right click on either the detected item or the undetected device, and click **Associate this device**.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-897e4438120b475790831e757c2a1b38dbfa8063%2Fftc6000_detectedhbusdevices3.png?alt=media)

   Only items of the same type that are assigned to this Controller, but do not have a serial number entered, will appear in the sub-menu.
8. Select the appropriate item.

   Alternatively, you can drag and drop the detected item onto the undetected device, but not the other way around.

   The selected item is removed from the "Undetected devices" node and merged with the detected item. The name of the detected item changes to match the name of the undetected device, and the item's icon and status show as online.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-89cf1cf5c2a3bf522f7a32199cf5b454d4154ae1%2Fftc6000_detectedhbusdevices4.png?alt=media)

</details>

<details>

<summary>Full pre-configuration</summary>

1. Create a new HBUS device. Either:
   * from the **Hardware** List Window, right click and select **New\...HBUS Devices**, OR
   * from the **HBUS Devices** tab of the Controller the device is to be assigned to, right click in the grid and select **New\...**
2. Click the **Connections** tab of the HBUS device.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-d6bd09e7ba42c83de6551ed9c6aa9e5a78f1171e%2Fhbusreader_connectionstab.png?alt=media)
3. Assign it to a Controller by selecting the appropriate one from the **Controller** drop-down list.
4. Enter the serial number of the unconnected HBUS device in the **HBUS Serial Number** field, and click the **Apply** button.
5. Open the properties of the Controller you have assigned the HBUS device to, and click the **HBUS Devices** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-11ac73409eb85ef4e32b694548428c52cdeff80e%2Fftc6000_detectedhbusdevices5.png?alt=media)

   The new item appears under the "Undetected devices" node on the Controllers **HBUS Devices** tab, and below the Controller on the **Hardware** List Window. In both places, the items icon shows the not responding red 'banned' overlay.
6. Physically connect the HBUS device with the matching serial number to one of the Controllers RS485 (HBUS) ports.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-89cf1cf5c2a3bf522f7a32199cf5b454d4154ae1%2Fftc6000_detectedhbusdevices4.png?alt=media)

   The device is auto-detected and the configured matching item is removed from the "Undetected devices' node and placed under the corresponding Bus node. The item's icon and status show as online.

</details>


---

# 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/configuration-client/site-installation/hardware/configuring-hbus-devices.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.
