> 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/creating-devices.md).

# Creating Devices

Equipment connected to the RS-485 building cabling are classed as devices; Readers, Terminals, Sensors, etc.

These devices are added using the **Hardware** List Window.

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\...**
3. From the displayed sub-menu(s), select the appropriate device type.

   For example: **HBUS Devices** > **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. Configure devices as required.

   **Note:** The HBUS 8-In 4-Out Board and HBUS 8-In Board can be mounted in a Gallagher cabinet and used in conjunction with a Tamper Board. Only one of the expansion boards can be connected to the Tamper Board. Once connected, the Tamper Board will become the monitoring board for the whole cabinet. Therefore, for the expansion boards that are **NOT** connected to the Tamper Board, click the **Status and Overrides** tab and tick the **Disable Tamper** checkbox.

   This will prevent incorrect (or continuous) tamper alarms being generated by the expansion boards not connected to the Tamper Board.
6. Click **OK**.


---

# 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/creating-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.
