> 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/linking-inputs-and-outputs-to-devices.md).

# Linking Inputs and Outputs to devices

Sensors can connect to any device that contains an Input. Equipment activators can connect to any device that contains an output.

The table below shows which devices contain inputs and outputs, and how many of each.

<table><thead><tr><th width="200">Device</th><th width="110">Type</th><th width="102">Inputs</th><th>Outputs</th></tr></thead><tbody><tr><td rowspan="2">Controller 6000/7000</td><td>4R/4H</td><td>12</td><td>4</td></tr><tr><td>8R/8H</td><td>24</td><td>8</td></tr><tr><td rowspan="2">Controller 7000 Single Door</td><td>RS-485</td><td>6</td><td>2 *</td></tr><tr><td>Wiegand</td><td>5</td><td>2 *</td></tr><tr><td colspan="2">HBUS 8-In 2-Out Door Module</td><td>8</td><td>2</td></tr><tr><td colspan="2">HBUS 8-In Board</td><td>8</td><td>0</td></tr><tr><td colspan="2">HBUS 8-In 4-Out Board</td><td>8</td><td>4</td></tr><tr><td colspan="2">HBUS 16-In 16-Out Board</td><td>16</td><td>16</td></tr><tr><td colspan="2">HBUS F31 Fence Controller</td><td>2</td><td>4</td></tr><tr><td colspan="2">HBUS F32 Fence Controller</td><td>3</td><td>5</td></tr><tr><td colspan="2">HBUS F41 Fence Controller</td><td>2</td><td>4</td></tr><tr><td colspan="2">HBUS F42 Fence Controller</td><td>3</td><td>5</td></tr><tr><td colspan="2">HBUS F22 Fence Controller</td><td>3</td><td>2</td></tr></tbody></table>

\* using a Controller 7000 Single Door Relay Board.

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. Locate the device to which you want to link the input/output.
3. **Right click** and select **Properties**.
4. Click the **Connections** tab.

   The window displayed will vary depending on the device you selected in Step 2.

   **Note:** Instead of a **Connections** tab, a Controller 6000 with a plug-in module selected, (i.e. 4H, 8H, 4R or 8R module) has an **Outputs** tab (to link Outputs) and an **Inputs** tab (to link Inputs). Click these as appropriate.
5. For the appropriate Input/Output, click within the edit box.

   From the displayed drop-down menu, select the input/output name.
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/linking-inputs-and-outputs-to-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.
