> 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/perimeter-solutions/f22-fence-controller-obsolescence-august-2021.md).

# F22 Fence Controller obsolescence - August 2021

Identify F22 Fence Controller retirement timing and supported F3-series replacements.

The **F22 Fence Controller (G21902)** obsolescence starts from September 2021. As the F3x and F4x Fence Controllers have been designed as both Network and Stand-alone they have naturally superseded the F22 Fence Controller.

#### Replacement Product![Edit section](https://resources.security.gallagher.com/skins/common/icons/icon-trans.gif)

The F3 range of Fence Controllers will serve as a direct replacement to the F22 Fence Controller. Module support for sites operating on older versions of Command Centre (pre CCFT v7.40), will continue whilst unique component stocks last.

#### Alternative Parts![Edit section](https://resources.security.gallagher.com/skins/common/icons/icon-trans.gif)

G21940 F32 Fence Controller\
G21941 F32 Fence Controller – Canadian Variant\
G21942 F32 Fence Controller – Apave

{% hint style="warning" %}
These fence controllers has now be replaced with the next generation (F5x and F6x)
{% endhint %}


---

# 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/perimeter-solutions/f22-fence-controller-obsolescence-august-2021.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.
