> 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/product-advisories/historical-notices/controller-3000-5000-and-trophy-ft-sup.md). # Controller 3000, 5000GL, and Trophy FT support Review end-of-support details for Controller 3000, Controller 5000GL, and Trophy FT. The Gallagher **Controller 3000 and 5000GL** products were placed on run-out status in **2011** due to component obsolescence, and were obsoleted from the Gallagher product range on **1 April 2017**. Gallagher **ended support for the 3000 and 5000GL Controllers on 1 April 2020**. From that date, 3000 and 5000GL controller support was removed from **Command Centre v8.30 and higher**, and technical support ceased. Sites wishing to remain on the latest version of Command Centre from that point onwards need to have upgraded all controllers to the **Controller 6000** platform. In line with this, **support for the Trophy FT Fence Controller also ended 1 April 2020**. Sites wishing to remain on the latest Command Centre version need to have upgraded all Trophy FT Fence Controllers to **F Series Fence Controllers connected to Controller 6000s**. {% file src="/files/vio1wIiorB5Tud2g559Y" %} Gallagher Controller 3000, 5000 & Trophy FT Support Statement {% endfile %} *** 🔗 **Related** * [Trophy product range end of life](/knowledge-hub/products/product-advisories/historical-notices/trophy-product-range.md). Review the wider Trophy end-of-life position. * [Controller 6000 extended support statement — April 2020](/knowledge-hub/products/product-advisories/historical-notices/controller-6000-extended-support-state.md). Review the replacement platform support window. --- # 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/product-advisories/historical-notices/controller-3000-5000-and-trophy-ft-sup.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.