> 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/command-centre-diagnostic-logs-getting.md).

# Getting logs from a Controller

There are three methods for collecting logs directly from controllers.

## Method 1: Web browsing to the controller

1. Ensure the controller has DIP Switch 1 on, **or** enable WWW connections in the controller's Status and Overrides.

![Controller Properties, Status and Overrides tab, with Enable WWW Connections selected and an override duration set](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-23eb03d1140f41a0d3543177d5374582d476e0e2%2FSECHUB-CCS-DIAG-controller-enable-www.png?alt=media)

2. Browse to the controller's IP address with `/debug.` appended (the trailing full stop is required), for example `172.16.241.100/debug.`

![Browser address bar showing the controller IP followed by /debug.](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-3e628bea02c0b8da80efd6d4fb0da75a3ac4cf80%2FSECHUB-CCS-DIAG-controller-debug-url.png?alt=media)

3. Enter the username and password when prompted.
   * Username: always `diagnostic`
   * Password: contact Technical Support if you do not have it (it can differ between 2-flash and 1-flash controllers).

![Browser authentication prompt requesting a username and password for the controller debug interface](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-b9504e827523c451ebcedb05de62b4a9d9a816c5%2FSECHUB-CCS-DIAG-controller-auth-prompt.png?alt=media)

**Linux Controllers.** The first page shows the controller's Active Threads and a list of logs. Gallagher prefers the contents of the **Application**, **System** and **Boot** logs. Browse to each, copy the text, and paste it into a separate text file named appropriately. Return the files to Technical Support.

![Linux controller debug page (Gallagher Controller 6000, "Grover") showing Active Threads and Application Log / System Log / Boot Log links](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-464a81294d75088651bac8f1e8584d7225523e7d%2FSECHUB-CCS-DIAG-controller-linux-debug-page.png?alt=media)

![Controller directory listing of /YAFFS/AppMan/Log/ showing a timestamped .log file](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-1d663d4828067254601e9cab6da5ef6571772d26%2FSECHUB-CCS-DIAG-controller-linux-log-directory.png?alt=media)

**WinCE Controllers.** The page looks different on older Windows CE controllers. The highlighted links are the most likely log files Technical Support will ask for. Click the **Application Manager Log Listing** and **Error Log** links, copy the text into text files named accordingly, and return them to Technical Support.

![Windows CE controller debug page showing Application Manager Log Listing and Error Log links](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-eccf54afbbc28ee7d49ce8fd90ab517aaac7d42a%2FSECHUB-CCS-DIAG-controller-wince-debug-page.png?alt=media)

## Method 2: FTSupportTool

1. On the server, enable web browsing on the controllers Technical Support have asked for logs from.
2. Locate `FTSupportTool.exe` in `C:\Program Files (x86)\Gallagher\Command Centre\Bin`.

![File Explorer showing FTSupportTool.exe highlighted in the Command Centre Bin folder](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-767982c8d7ad83e6ca090c9cceefbbf52e3e4102%2FSECHUB-CCS-DIAG-ftsupporttool-bin.png?alt=media)

3. Recommended: move the file somewhere else first so you can easily find the log it generates (`FTSupportInfo.txt`).
4. Run it as Administrator (right-click → Run as Administrator). It opens a Command Prompt and runs. Depending on site size, it may take a while.
5. Return `FTSupportInfo.txt` to Technical Support.

## Method 3: Support Log Tool

See [Gathering Logs - Why and how](/knowledge-hub/products/cc-software/troubleshoot/command-centre-diagnostic-logs/command-centre-diagnostic-logs-gatheri.md) for the automated Support Log Tool.

> **Important:** Remember that `TraceOn` and `GeneralOn` should be disabled (set back to 0) after fault replication is complete.

***

🔗 **Related**

* [Getting logs from a T2X Reader](/knowledge-hub/products/cc-software/troubleshoot/command-centre-diagnostic-logs/getting-logs-from-a-t2x-reader.md). The reader-specific log capture.
* [Gathering Logs - Why and how](/knowledge-hub/products/cc-software/troubleshoot/command-centre-diagnostic-logs/command-centre-diagnostic-logs-gatheri.md). Raising the logging level and collecting logs.


---

# 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/command-centre-diagnostic-logs-getting.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.