> 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-an-hbus-i-o-interface.md).

# Configuring an HBUS I/O Interface

### Introduction

The HBUS I/O Interface enables you to configure an HBUS I/O expansion board, (i.e. 8-In Board, 8-In 2-Out Door Module, 8-In 4-Out Board, 16-In 16-Out Board, or 4-In 2-Out Door Module - Wiegand) in Command Centre.

**Notes:**

* By default, the 8-In 2-Out Door Module is selected when the HBUS I/O Interface is first created. You will need to select the correct hardware variant when configuring the HBUS I/O Interface.
* Operators require the "Edit Site" operator privilege to perform this procedure, and must be in the same or parent Division of the HBUS I/O Interface.

***

### Configuration

To configure an HBUS I/O Interface, perform the following procedures in Gallagher Configuration Client:

1. Click **Configure** from the menu bar, then **Hardware**.

   The **Hardware** List Window opens (in [tree view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/tree-view.md)).
2. **Right click** and select **New\...HBUS Devices**.
3. Select **HBUS I/O**.

   By default the **General** tab displays.
4. Complete the fields as required.

   For further detail see [General tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/general-tab.md).
5. Click the **Event Response** tab, and configure as required.

   For further detail see [Event Response tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/event-response-tab.md).
6. Click the **Alarm Instructions** tab, and configure as required.

   For further detail see [Alarm Instructions tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/alarm-instructions-tab.md).
7. Click each tab in turn and configure the reader properties as required:

<details>

<summary>Status and Overrides tab</summary>

1. Click the **Status and Overrides** tab.

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

   To prevent continuous tamper alarms, tick the **Disable Tamper** checkbox.

   **Notes:**

   * The 16-In 16-Out Board has a **Disable Front Tamper** and a **Disable Rear Tamper** checkbox so that the Tampers can be enabled/disabled independently.
   * When correctly configured, the detected hardware variant is displayed in the **Status** field.
2. To perform an override, click within the **Override** field and select the required override action from the drop-down list, then click the **Override Now** button.

   For a description on each of the override actions that can be performed refer to [Performing Overrides](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/status-and-overrides/performing-overrides.md).

   **Note:** This device does not support timed overrides. All overrides are immediate and persist until specifically cancelled by an operator.

</details>

<details>

<summary>Connections tab</summary>

1. Click the **Connections** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-a2758f1e960fd7272f00f432fc4f03372701cdef%2Fhbusio_2.png?alt=media)
2. Select the Controller 6000 or 7000 you want to assign this HBUS I/O Interface to, from the **Controller** drop-down list.

   **Notes:**

   * HBUS I/O Interfaces can be created via the **HBUS Devices** tab of a Controller. In that case the **Controller** field would be pre-populated with that Controller name. Refer to [Configuring HBUS Devices](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/configuring-hbus-devices.md).
   * When an HBUS I/O Interface is connected to a Controller 6000 or 7000 it will automatically be upgraded or downgraded to the version of I/O firmware (vHI firmware) held by the Controller. This will only happen if the HBUS I/O Interface is correctly configured. A download bar displays on the **Connections** tab, showing the approximate progress of the download. If the download fails for whatever reason, the HBUS I/O Interface will revert to the previous version of code. A Code Download Fail event is raised in Command Centre.
3. Enter the HBUS serial number (10 character hexadecimal string) into the **HBUS Serial Number** field. This serial number is located on the board sticker.

   **Note:** The HBUS serial number is optional, however the I/O Interface will be considered as not properly configured unless one is entered.
4. If you click the **Apply** button, software version numbers display.

   The **Configured Version** is the version of the device software in the configured Controller FTS file, (i.e. **not** the version of the Controller software).

   The **Current Version** is the version of software as last reported by the HBUS I/O Interface itself.

   **Note:** For the HBUS I/O Interface to report its current version of software, an Alarm Zone must be assigned to the **Event Response** tab of the HBUS I/O’s properties.
5. Select the appropriate hardware variant, from the **Hardware Variant** drop-down list.

   **Notes:**

   * 'Bad Unit' type alarms may occur if the hardware variant attached to the Controller does not match to the hardware variant selected.
   * If "4-In 2-Out Door Module - Wiegand" was selected from the Hardware Variant drop-down list, an additional **Readers** tab will appear after the **Outputs** tab.

</details>

<details>

<summary>Inputs tab</summary>

1. Click the **Inputs** tab.

   **Note:** The appearance of this screen may differ depending on the hardware variant selected, (e.g. If "4-In 2-Out Door Module - Wiegand" was selected, there will only be 4 Inputs available). Likewise, the **Reserved Inputs** sub-tab will not appear if either "8-In 2-Out Door Module" or "4-In 2-Out Door Module - Wiegand" were selected, as these variants do not support reserving inputs.

   The **Reserved Inputs** sub-tab provides a simple way of designating physical tampers and power supply monitoring inputs.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-e9bd898fb388c059cd4e1d975c84235505ecc5b6%2Fhbusio_3_reservedinputs.png?alt=media)
2. Assign each Input to the correct address. For details on how to create an Input, refer to [Creating Inputs and Outputs](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-inputs-and-outputs.md).
3. If applicable, click the **Reserved Inputs** sub-tab.

   **Note:** Operators require the "Edit Site" privilege to reserve inputs.

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

   By default, all the Reserved Inputs will have "—None Selected --". They will however already be populated if the **Reserve inputs on creation of I/O module** checkbox has been ticked on the Server Properties **Reserved Input Defaults** tab.
4. If the fields are not already populated or have been changed, and you want to set the site defaults from the Server Properties, click the **Use Site Defaults** button, otherwise select the required input for each field.

   Notes:

   * If Input 1 is already in use, ticking the **Use Input 1 for cabinet tamper** checkbox will generate the following message:

     *"Input is assigned as a tamper input. Please remove the first input from this controller."*
   * If you attempt to assign an input more than once, the following error message displays:

     *"Cannot reserve input, it is already allocated"*
   * When reserved inputs are configured for **Cabinet Front Tamper** and **Cabinet Rear Tamper**, the optical tampers on the **Status and Overrides** tab are disabled, (i.e. the **Disable Front Tamper** and **Disable Rear Tamper** checkboxes).
   * The **Clear All** button can be used to clear reserved inputs and return them to "—None Selected --".

   As inputs are reserved, they become disabled (greyed out) on the **Inputs** sub-tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-379200008b7b3d0c7b13d2e8d318f8e51100ff90%2Fhbusio_inputstab.png?alt=media)
5. Click the **EOL Resistors** tab.

   This screen allows you to define the wiring and resistance values used on inputs that are connected to this device. Refer to [Configuring EOL Resistors for devices](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/configuring-eol-resistors-for-devices.md).

</details>

<details>

<summary>Outputs tab</summary>

1. Click the **Outputs** tab.

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

   **Note:** The appearance of this screen will differ depending on the hardware variant selected.
2. Assign each Output to the correct address. For details on how to create an Output, refer to [Creating Inputs and Outputs](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-inputs-and-outputs.md).

</details>

<details>

<summary>Readers tab</summary>

1. Click the **Readers** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-32706e3ae948abd96fd4f7918f3856ae06c6530c%2Fhbusio_5.png?alt=media)
2. Select the appropriate readers from the **Reader 1** and **Reader 2** drop-down lists.

   **Note:** Only third party readers can be assigned to an "HBUS 4-In 2-Out Door Module - Wiegand".

</details>

**Note:** This tab will only appear if "4-In 2-Out Door Module - Wiegand" was selected from the Hardware Variant drop-down list on the **Connections** tab.

8. Click the **Cameras** tab if you want to associate a DVR Camera(s) with this HBUS I/O Interface.

   For further details see [Cameras tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/cameras-tab.md).
9. Click the **Icons** tab if you want to change the Icon Set for this HBUS I/O Interface.

   For further details regarding the **Icons** tab, see [Icons](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/icons.md).
10. Click the **Custom Fields** tab if you want to add and assign a custom field value to this HBUS I/O Interface.

    For further details regarding the **Custom Fields** tab, see [Custom Fields](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/custom-fields.md).
11. Click the **Notes** tab if you want to add a note(s) about this HBUS I/O Interface.

    For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).
12. Click **OK** to exit and save your changes.

    Click **Cancel** to exit without saving your changes.

    Click **Apply** to save your changes and stay in this window.

### Result

An HBUS I/O Interface has been configured, assigned to a Controller 6000 or 7000, and is ready for use.

If you have configured an 8-In 2-Out Door Module, the HBUS devices connected to the module display in tree view. Refer to [Configuring HBUS Devices](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/configuring-hbus-devices.md).


---

# 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-an-hbus-i-o-interface.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.
