> 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-7000-and-7000-sdc/troubleshoot/controller-7000-run-led-diagnostics-an.md). # Run LED diagnostics and shutdown codes Diagnose Controller 7000 startup states and shutdown events using Run LED patterns and codes. Two diagnostic reference tables for Gallagher controllers: the Run LED flash states (visible on the physical controller) and the shutdown codes (found in the controller error log or Command Centre event messages). This reference also applies to Controller 7000 SDC. *** ## Run LED flash states #### What does the Run LED flash pattern mean? The red **Run LED (D9)** flashes to indicate the controller's operating status. | Flash | Sequence | Meaning | | ---------------------------------------- | -------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Slow** | 2000 ms on, 1000 ms off | Controller is searching for software FTS files | | **Fast** | 130 ms on, 130 ms off (4 Hz flash) | Initialising | | **1 Flash** | 500 ms on, 500 ms off (1 Hz flash) | **Normal running** | | **2 Flash** | 2 flashes, then pause (each flash 50 ms on, 400 ms off, 1.2 s pause) | Controller has an IP but no configuration, or has been configured incorrectly | | **3 Flash** | 3 flashes, then pause (each flash 50 ms on, 400 ms off, 1.2 s pause) | Controller requires an IP address. Ensure BootP Service (CCFTBPS.exe) is running, the controller is configured correctly, and it has connected to the network | | **4 Flash** | 4 flashes, then pause (each flash 50 ms on, 400 ms off, 1.2 s pause) | No private key or certificate loaded. Note: this can only be reset by the factory of manufacture. | | **5 Flash** | 5 flashes, then pause (each flash 50 ms on, 400 ms off, 1.2 s pause) | Invalid private key or certificate loaded, or key and certificate do not match the controller serial number. See [DIP Switch 8 Recovery](/knowledge-hub/products/cc-hardware/controllers/controller-7000-and-7000-sdc/troubleshoot/controller-7000-dip-switch-8-recovery.md) or contact Gallagher Tech Support. | | **6 Flash** | 6 flashes, then pause (each flash 50 ms on, 400 ms off, 1.2 s pause) | The controller has dropped its code. See [DIP Switch 8 Recovery](/knowledge-hub/products/cc-hardware/controllers/controller-7000-and-7000-sdc/troubleshoot/controller-7000-dip-switch-8-recovery.md) or contact Gallagher Tech Support. | | **7 Flash** | 7 flashes, then pause (each flash 50 ms on, 400 ms off, 1.2 s pause) | USB upgrade complete. Remove the USB drive to complete installation | | *(no flash number)* | 450 ms on, 50 ms off (2 Hz flash) | Controller Resetting | | **Short flash / long flash (1 s cycle)** | 100 ms on, 250 ms off | Boot code monitor running, network unplugged | *** ## Shutdown codes #### Where do I find shutdown codes, and what do they mean? Every time a controller shuts down, an `SC` code is recorded in the controller's error log (accessible via web browse) and may appear in Command Centre event messages. | Shutdown Code | Meaning | Fault or Normal | Likely Cause | | ------------- | -------------------------- | -------------------------- | ------------------------------------------------- | | **0** | Normal Termination (debug) | Normal | — | | **1** | Remote Reset Request | Normal | Reset request after a code download | | **2** | Power Fail | Normal | Power has failed | | **3** | Hardware watchdog timeout | Software or hardware fault | S/W or H/W fault | | **4** | Startup Failed | Software fault | Corrupt version of controller software | | **5** | Configuration Failed | Fault | Invalid configuration | | **6** | Out of Memory | Fault | Software bug, or too much activity | | **7** | Assertion | Fault | Software bug, should only occur in debug versions | | **8** | RAM error | Hardware fault | Faulty RAM chip | | **9** | Code checksum error | Fault | Controller code has been corrupted | | **10** | FTP server running | Normal | Controller was started with the `/FTP` parameter | | **11** | Uncaught exception | Software fault | Depends on the exception | | **12** | Caught exception | Software fault | Depends on the exception | | **255** | Undefined Fault | Fault | Almost anything | #### Which codes point to a hardware fault versus normal behavior? > **Troubleshooting:** Repeated SC codes 3, 6, 8, or 255 in the error log point to hardware faults or memory corruption. SC 4 and 9 with repeated occurrences suggest corrupt firmware, so reapply firmware. SC 5 (Configuration Failed) is commonly caused by pushing configuration that is too large for the controller's current capacity limits. *** 🔗 **Related** * [DIP Switch 8 Recovery](/knowledge-hub/products/cc-hardware/controllers/controller-7000-and-7000-sdc/troubleshoot/controller-7000-dip-switch-8-recovery.md). Recovery for 4-flash, 5-flash, 6-flash, and solid-on states. * [Certificates and Keys](/knowledge-hub/products/cc-hardware/controllers/controller-7000-and-7000-sdc/reference/controller-7000-certificates-and-keys.md). Why a 4-flash or 5-flash state indicates a key or certificate problem. * [Limits](/knowledge-hub/products/cc-hardware/controllers/controller-7000-and-7000-sdc/reference/controller-7000-limits.md). Capacity limits behind an SC 5 (Configuration Failed). --- # 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-7000-and-7000-sdc/troubleshoot/controller-7000-run-led-diagnostics-an.md?ask=&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.