> 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/controller-6000/troubleshoot/controller-6000-run-led-diagnostics-and-shutdown-codes.md).

# Run LED diagnostics and shutdown codes

Diagnose Controller 6000 startup states and shutdown events using Run LED patterns.

Run LED behaviour and shutdown codes are shared between the C6000 and the C7000. For the full tables, see [Controller 7000 - Run LED Diagnostics and Shutdown Codes](/knowledge-hub/products/cc-hardware/controllers/controller-7000-and-7000-sdc/troubleshoot/controller-7000-run-led-diagnostics-an.md).

For the C6000-specific Run LED and DIP Switch reference (including the C6000 DIP Switch defaults table), see [Run LED and DIP Switches](/knowledge-hub/products/cc-hardware/controllers/controller-6000/troubleshoot/controller-6000-run-led-and-dip-switches.md).

For the C6000 shutdown code reference, see [Shutdown Codes](/knowledge-hub/products/cc-hardware/controllers/controller-6000/troubleshoot/controller-6000-shutdown-codes.md).

***

🔗 **Related**

* [Run LED and DIP Switches](/knowledge-hub/products/cc-hardware/controllers/controller-6000/troubleshoot/controller-6000-run-led-and-dip-switches.md). The C6000 Run LED and DIP switch tables.
* [Shutdown Codes](/knowledge-hub/products/cc-hardware/controllers/controller-6000/troubleshoot/controller-6000-shutdown-codes.md). The C6000 shutdown code reference.


---

# 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/controller-6000/troubleshoot/controller-6000-run-led-diagnostics-and-shutdown-codes.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.