> 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/readers/t-series.md).

# T-Series

Compare T-Series readers and terminals, their access and alarm capabilities, and supported communication methods.

T-Series is Gallagher Security's current range of access readers and terminals. It includes reader-only models, display terminals, and keypad readers for card, PIN, mobile and code-based access.

![T-Series readers product range](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2F2YjhhCX5QFxxePfxWU5a%2FReader%20labelled.png?alt=media\&token=57982040-212a-4a28-8ace-b00e23bdea3e)

### Reader and terminal options

| Reader or terminal                     | Supported communication |
| -------------------------------------- | ----------------------- |
| T10, T11, T12, T15, and Standard T20   | HBUS or CardaxIV        |
| T20 Alarms Terminal and all T30 models | HBUS only               |

The T20 is a color screen terminal for card-and-PIN access, alarm control, and system messages.

The T30 is a screenless keypad reader for card-and-PIN or code-only access.

### Information in this section

| Page                                                                                                                                   | Description                                                                                                     |
| -------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| [T-Series models and accessories](/knowledge-hub/products/cc-hardware/readers/t-series/t-series-models-and-accessories.md)             | Compare reader and terminal models, part numbers, protocols, installation notes, and accessories                |
| [T20 terminal](/knowledge-hub/products/cc-hardware/readers/t-series/t-series-t20-user-guide-and-resolution.md)                         | Learn about T20 access methods, alarm functions, display resolution, and Alarms Terminal limitations            |
| [T30 keypad](/knowledge-hub/products/cc-hardware/readers/t-series/t-series-t30-operation.md)                                           | Review T30 keypad variants, access behavior, door requirements, and alarm-zone functions                        |
| [T-Series reader common questions](/knowledge-hub/products/cc-hardware/readers/t-series/t-series-frequently-asked-questions-fa.md)     | Find answers about reader revisions, T20 capabilities, firmware upgrades, card encoding, and Mobile Credentials |
| [Cleaning T-Series readers](/knowledge-hub/products/cc-hardware/readers/t-series/t-series-reader-materials-and-cleaning.md)            | Identify safe cleaning agents for readers, keypads, covers, and component materials                             |
| [HBUS encryption keys report tampered](/knowledge-hub/products/cc-hardware/readers/t-series/t-series-encryption-keys-reporting-tam.md) | Resolve encryption-key mismatches after device moves or extended offline periods                                |
| [T20 firmware upgrade fails](/knowledge-hub/products/cc-hardware/readers/t-series/t-series-t20-firmware-upgrade-issues.md)             | Complete the required staged upgrade for legacy T20 firmware                                                    |
| [T-Series readers without HBUS support](/knowledge-hub/products/cc-hardware/readers/t-series/t-series-non-hbus-compatible.md)          | Identify Revision 0 readers and their HBUS and DESFire key limitations                                          |


---

# 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/readers/t-series.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.