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

# Controllers Legacy - Limits

> ⚠️ **Legacy controllers are not supported above CC v8.20.** See [Controllers - Legacy](/knowledge-hub/products/cc-hardware/controllers/controllers-legacy.md).

## Bus distances

| Bus                                  | Maximum distance |
| ------------------------------------ | ---------------- |
| **Local Bus** (5000 and 5000GL only) | 500 metres       |
| **GBUS**                             | 1,220 metres     |

***

## Parts limits (from SCR901)

| Controller  | Typical parts       |
| ----------- | ------------------- |
| **C3000**   | 500 typical parts   |
| **C5000GL** | 1,000 typical parts |

"Typical parts" describes the average part memory usage. Heavy-weight parts will consume more memory (reducing the limit). Lighter parts will occupy less memory (allowing more parts).

***

## Network connections (3000, 5000, 5000GL)

| Direction            | Limit |
| -------------------- | ----- |
| Incoming connections | 30    |
| Outgoing connections | 30    |

***

## 3000-8R limits

* **8 CardaxIV readers**, or **4 Wiegand readers**
* **8 GBus devices** and **4 RATs**
* Controls up to **8 doors**
* Stores up to **46,000 cardholders** (depending on allocation settings)
* **No support for Local Bus**

***

## 3000-4R limits

* **4 CardaxIV readers**, or **2 Wiegand readers**
* **8 GBus devices** and **4 RATs**
* Controls up to **4 doors**
* Stores up to **46,000 cardholders**
* **No support for Local Bus**

***

## 5000 limits

* **16 Local Bus** devices (access control and alarm monitoring)
* **8 doors**
* **46,000 cardholders** (depending on allocation settings)

***

## 5000GL limits

* Up to **8 doors**
* Up to **92,000 cardholders** (depending on database allocation settings)
* Bus options:
  * **16 Local Bus devices, 8 GBus units, and 4 RATs**, or
  * **16 GBus devices and 8 RATs**

***

## Capacity allocation reference

For approximations of various database allocation settings for legacy controllers, refer to **Command Centre Classic Online Help: Altering Controller memory between Cards and Events**.

For C6000 limits (current product family), see [Controller 6000 - Limits](/knowledge-hub/products/cc-hardware/controllers/controller-6000/reference/controller-6000-limits.md).

***

🔗 **Related**

* [Controllers - Legacy](/knowledge-hub/products/cc-hardware/controllers/controllers-legacy.md). Variants and lifecycle.
* [FTP Upgrading legacy controllers](/knowledge-hub/products/cc-hardware/controllers/controllers-legacy/ftp-upgrading-legacy-controllers.md). The manual firmware upgrade path.


---

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