> 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-hardware/input-and-output-io-devices/io-devices-legacy.md).

# Legacy I/O devices

Identify legacy GBUS and Local BUS hardware, support limits, and HBUS replacements.

Identify legacy Gallagher hardware that current Command Centre versions no longer support. Use this information to plan an HBUS replacement.

### Overview

The hardware listed on this page is **no longer supported in the current versions of Command Centre**. It is documented so you can identify what is on an existing site and know what the upgrade path looks like.

{% hint style="warning" %}
**Do not recommend this hardware or include it in new projects.** The current equivalent is [HBUS I/O devices](/knowledge-hub/products/cc-hardware/input-and-output-io-devices/io-devices-hbus.md).
{% endhint %}

### Support cutoff versions

| Protocol family | Last Command Centre version that supports it |
| --------------- | -------------------------------------------- |
| **GBUS**        | vEL9.00                                      |
| **Local BUS**   | vEL8.0                                       |

> ⚠️ **Check the I/O protocol family before quoting a Command Centre upgrade.** A site running GBUS expansion hardware cannot upgrade its Command Centre server past **vEL9.00** without first replacing the I/O hardware. A site running Local BUS hardware is capped at **vEL8.0**.

### GBUS hardware

{% hint style="warning" %}
**The below GBUS hardware is no longer supported or available from Gallagher Security.**

See the HBUS equivalent table further below for currently supported models.
{% endhint %}

<table><thead><tr><th width="130.4000244140625">Part Number</th><th width="441">Description</th></tr></thead><tbody><tr><td>C200680</td><td>GBUS 8 Input Expansion Board</td></tr><tr><td>C200684</td><td>GBUS 8 In 4 Out I/O Expansion</td></tr><tr><td>C200688</td><td>GBUS 16 In 16 Out High Density I/O</td></tr><tr><td>C200660</td><td>GBUS URI 8 In 2 Out Cardax IV</td></tr><tr><td>C200665</td><td>GBUS URI 4 In 2 Out Wiegand</td></tr><tr><td>C200601, C200602</td><td>GBUS Remote Arming Terminal</td></tr></tbody></table>

#### HBUS equivalents

<table><thead><tr><th width="340.5999755859375">GBUS (legacy)</th><th>HBUS (current)</th></tr></thead><tbody><tr><td>C200680 (8 Input)</td><td>C300680 (8 Input)</td></tr><tr><td>C200684 (8 In 4 Out)</td><td>C300684 (8 In 4 Out)</td></tr><tr><td>C200688 (16 In 16 Out)</td><td>C300688 (16 In 16 Out)</td></tr><tr><td>C200660 (URI 8 In 2 Out)</td><td>C300660 (Door Module)</td></tr><tr><td>C200665 (URI 4 In 2 Out Wiegand)</td><td>C300665 (Door Module - Wiegand)</td></tr></tbody></table>

### Local BUS hardware

| Description                                                        |
| ------------------------------------------------------------------ |
| Local BUS URI 6 In 2 Out Cardax IV or Wiegand                      |
| Local BUS Relay Interface 20 Out                                   |
| Local BUS I/O Interface 15 In 5 Out                                |
| Local BUS FT Reader I/O Interface 24 In 8 Out 16 Cardax IV Readers |
| Cardax FT Digital Camera                                           |

Local BUS predates GBUS. If a site still runs Local BUS hardware, it is most likely running on Cardax FT era controllers.

### Upgrade options

* **GBUS sites.** Replace each GBUS board with the equivalent HBUS board. Verify the replacement against its install note. Enable HBUS on the controller. Then bring the new boards online.
* **Local BUS sites.** A Local BUS to HBUS migration is a controller refresh. Scope a full controller and I/O replacement.


---

# 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-hardware/input-and-output-io-devices/io-devices-legacy.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.