> 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-software/troubleshoot/command-centre-diagnostic-logs/getting-logs-from-a-t2x-reader.md).

# Getting logs from a T2X Reader

The **T20 and T21** series of readers have their own logging capability, recording the reader's ongoing state and errors for fault finding. The data on the reader is encrypted and can only be collected by web browsing into the controller the reader is connected to, **and only if the reader is connected by HBUS**.

**Prerequisite:** Enable Web connections on the Controller via Configuration Client before connecting.

1. Identify the serial number of the T20/T21: open the reader's properties, go to the **Connections** tab, where the serial is listed.
2. Web browse to the controller's IP address followed by `/debug.` Enter username `diagnostic` and the password (contact Technical Support, or use the password set for your site on **Server Properties → Advanced** tab).
3. Go to the **HBUS Manager** page.

![Controller debug Active Threads list with the HBUS Manager link highlighted](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-338091d7376209905f14b2dab1848539714c7fcf%2FSECHUB-CCS-DIAG-t2x-hbus-manager.png?alt=media)

4. In the **HBUS Thread** section, identify the reader by its serial number and click the matching **Unit X** link (Unit 21 in the example, serial 2316427001).

![HBUS Thread table listing units, with Unit 21 and its serial number highlighted](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-b2e6a9657c38ad1944f0b0d0f974d0824a9c0653%2FSECHUB-CCS-DIAG-t2x-hbus-thread-table.png?alt=media)

5. On the unit page, click the **Unit Log** link.

![T20 unit log page showing the Encryption checkbox and ChangeEncryption button](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-9ee66a27f65ffa2355ce46d3c9ace6ec4eb4b880%2FSECHUB-CCS-DIAG-t2x-unit-log-encryption.png?alt=media)

6. The first visit shows no information. Click **RetrieveLog**. A message tells you to go back and refresh the page; do this.

![T20 Log Retrieval page with an empty file-number field and RetrieveLog / ClearLog buttons](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-c6f05ab7583b74aabbc39fb5218a9d8e002e0916%2FSECHUB-CCS-DIAG-t2x-log-retrieval.png?alt=media)

7. After refreshing, the log appears. Cut and paste it into a text document to capture the logs, and send them to Gallagher for fault analysis.

![Retrieved T20 unit log showing kernel log entries](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-6946f6aa199250ab9a5eb5130e60db34129f51b1%2FSECHUB-CCS-DIAG-t2x-retrieved-log.png?alt=media)

8. To go further back in history, add a number to the file field (`1`, `2`, and so on for the previous log).

![T20 log retrieval showing /var/log/messages file number 49 with log entries](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-27cf60052e8a083cb43e0f5b8548bceee2b016cb%2FSECHUB-CCS-DIAG-t2x-history-file-49.png?alt=media)

> **Note:** **49 is the maximum** you can go up to.

## Known issues

1. Exceeding 49 returns `Error: File not found`. **Resolution:** go back to file number 0 once you have reached the maximum limit of 49.

![T20 log retrieval with file number 50 entered, returning File Not Found](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-7801a71eb901afa60c19d3a7faf2ff7a06435eaf%2FSECHUB-CCS-DIAG-t2x-file-not-found.png?alt=media)

2. Typing a string into the field (for example `messages`) returns an invalid file number. **Resolution:** use a file number from 0 to 49, not a string.

![T20 log retrieval with the string "messages" entered, returning Invalid file number](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-7feeec853f4b55aee69df9c4ae4b4132b280bbf3%2FSECHUB-CCS-DIAG-t2x-invalid-file-number.png?alt=media)

***

🔗 **Related**

* [Getting logs from a Controller](/knowledge-hub/products/cc-software/troubleshoot/command-centre-diagnostic-logs/command-centre-diagnostic-logs-getting.md). The controller web-browse method these readers depend on.


---

# 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-software/troubleshoot/command-centre-diagnostic-logs/getting-logs-from-a-t2x-reader.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.