> 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/t-series-non-hbus-compatible.md).

# T-Series readers without HBUS support

Identify Revision 0 T-Series readers without HBUS support or Admin Card DESFire key updates.

When T-Series readers were first introduced they only supported **Cardax IV** communication protocols (Revision 0).

This can pose a problem for customers who have them installed but want to upgrade to **HBUS** devices.

***

### Identify Revision 0 readers

{% hint style="warning" %}
All identification methods require the reader to be **removed from the wall** to be examined for 100% confirmation.
{% endhint %}

Units that do **NOT have V1 (or higher)** on them and were manufactured **before 2012** will not be HBUS compatible.

#### Revision 0 part numbers and dates

Part numbers like `C3002XX` indicate Rev 0. `C3004XX` means HBUS compatible.

The Revision 0 readers predominantly have just the **Gallagher logo** on the front face (no diamond, no 125 symbol).

![Rev 0 reader front face](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-15f783a0c6d9cd91aed67aaccdf46719a9299334%2FSECHUB-TSERIES-NONHBUS-01-rev0-front.jpg?alt=media)

![Rev 0 reader back label showing Cardax IV only wiring and no Rev designation](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-19047c43a55d1d490f32c4489b27b640f35c84b7%2FSECHUB-TSERIES-NONHBUS-02-rev0-back.jpg?alt=media)

> ⚠️ **Important:** Revision 0 readers **cannot have their DESFire keys updated via an Admin Card**. Revision 1 and later can.

***

### Revision 1 and higher (HBUS compatible)

The next released versions of the readers would have a **small diamond**, and if they were Multitech Readers, also have a **125** symbol on them. These are HBUS compatible.

The **next generation Multitech** readers have a **diamond and a WiFi-like indicator above the diamond**. These are HBUS compatible.

![Rev 1 MIFARE reader front (diamond visible)](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-3cc828a750c0b6a547fe33985bdb4b9076ab8729%2FSECHUB-TSERIES-NONHBUS-03-rev1-mifare-front.jpg?alt=media)

![Rev 1 Multitech reader front (diamond and 125)](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-616e172438f6cc86107585463707334864078c9a%2FSECHUB-TSERIES-NONHBUS-04-rev1-multitech-front.jpg?alt=media)

![Next generation Multitech reader (diamond and WiFi-like indicator above the diamond)](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-93de77d280631e2cf1dfc1916c565ca8916889c8%2FSECHUB-TSERIES-NONHBUS-05-rev1-multitech-next-gen.jpg?alt=media)

Note: Rev 1 backs show **wiring indications for both HBUS and Cardax IV** wiring, and a Revision 1 designation.

![Rev 1 reader back label showing HBUS and Cardax IV wiring](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-c1331f6d368105d15fadde0f75f47e669b8b449e%2FSECHUB-TSERIES-NONHBUS-06-rev1-back.jpg?alt=media)

***

### Last manufacturing dates for Revision 0 readers (C3002XX hardware)

| Part Number | Description                     | Last Made        |
| ----------- | ------------------------------- | ---------------- |
| C300200     | T10 MIFARE READER BLACK -24     | 18 January 2012  |
| C300201     | T10 MIFARE READER WHITE -24     | 20 December 2011 |
| C300210     | T11 MIFARE READER BLACK -24     | 3 February 2012  |
| C300211     | T11 MIFARE READER WHITE -24     | 3 February 2012  |
| C300220     | T12 MIFARE READER BLACK -22     | 12 March 2012    |
| C300221     | T12 MIFARE READER WHITE -22     | 2 September 2011 |
| C300230     | T11 MULTI TECH READER BLACK -24 | 9 August 2012    |
| C300231     | T11 MULTI TECH READER WHITE -22 | 9 August 2012    |
| C300240     | T12 MULTI TECH READER BLACK -24 | 28 February 2012 |
| C300241     | T12 MULTI TECH READER WHITE -24 | 6 September 2011 |

***

🔗 **Related**

* [T-Series](/knowledge-hub/products/cc-hardware/readers/t-series.md). Current HBUS part numbers (C3004XX and above).
* [T-Series - Frequently Asked Questions (FAQ)](/knowledge-hub/products/cc-hardware/readers/t-series/t-series-frequently-asked-questions-fa.md). Why there are multiple revisions of T10/T11/T12.
* [T-Series - T20 Firmware upgrade issues](/knowledge-hub/products/cc-hardware/readers/t-series/t-series-t20-firmware-upgrade-issues.md). Migrating older CardaxIV readers to HBUS.


---

# 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/t-series-non-hbus-compatible.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.