> 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/controllers/controllers-legacy.md).

# Controllers - Legacy

Prior to the C7000 and C6000, Gallagher produced three controller families: the **5000**, **5000GL**, and **3000**.

{% hint style="danger" %}
**End-of-life:** These controllers were placed on **run-out status in 2011**. They are no longer available for purchase, no longer manufactured, and Command Centre **no longer supports** them in supported versions. They cannot be brought online to current Command Centre installations.
{% endhint %}

## Variants

| Part Number | Name    | Description                                                                        | Support dropped at |
| ----------- | ------- | ---------------------------------------------------------------------------------- | ------------------ |
| C200111     | 5000    | Local Bus only controller                                                          | CC 8.30            |
| C200190     | 5000GL  | Local Bus / GBus controller                                                        | CC 8.30            |
| C200116     | 3000 8R | 8 CardaxIV reader / 4 Wiegand reader ports; 8 Outputs, 16 Inputs; RS485 GBus comms | CC 9.10            |
| C200118     | 3000 4R | 4 CardaxIV reader / 2 Wiegand reader ports; 4 Outputs, 8 Inputs; RS485 GBus comms  | CC 9.10            |

![Cardax 3000 8R controller unit](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-00eccf9ab037f91b2d5a5a60488329ee9da96288%2FSECHUB-LEGACY-CTRL-01-cardax-3000-8r.jpg?alt=media)

> **Note:** The maximum supported Command Centre version for **any** legacy controller is **CC 8.20**. See [Controllers Legacy - Limits](/knowledge-hub/products/cc-hardware/controllers/controllers-legacy/controllers-legacy-limits.md) for the hardware capacity per model.

For sites still running legacy controllers (for example, firmware 5.21 or lower), the **FTP upgrade procedure** can manually upgrade controllers via a direct FTP connection. See [FTP Upgrading legacy controllers](/knowledge-hub/products/cc-hardware/controllers/controllers-legacy/ftp-upgrading-legacy-controllers.md).

For current controller options, see [Controller 7000](broken://pages/873trKCrdhjXzfqYdsdU) and [Controller 6000](/knowledge-hub/products/cc-hardware/controllers/controller-6000.md).

***

🔗 **Related**

* [Controllers Legacy - Limits](/knowledge-hub/products/cc-hardware/controllers/controllers-legacy/controllers-legacy-limits.md). Hardware capacity per model.
* [FTP Upgrading legacy controllers](/knowledge-hub/products/cc-hardware/controllers/controllers-legacy/ftp-upgrading-legacy-controllers.md). The manual firmware upgrade path.
* [Controller 7000](broken://pages/873trKCrdhjXzfqYdsdU). The current enterprise controller.


---

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