> 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/configuration-client/licensable-features/perimeter-fence-controllers/overriding-a-fence-controller.md).

# Overriding a Fence Controller

### Introduction

You may choose to temporarily override a Fence Controller when testing the associated fences. Overrides that can be performed at a Fence Controller are:

* **Shunt**

  Stops communication with the Fence Controller. Alarms raised by the Fence Controller are suppressed. Command Centre will not send commands to the Fence Controller, Fence Zones, Inputs or Outputs until you 'Unshunt'.
* **Unshunt**

  Starts communication with the Fence Controller.
* **Reset**

  Performs a software reset on the Fence Controller. When performed on an F3x, F4x, F5x or F6x Fence Controller all inactive alarms (shown on the Fence Controller cover) will be reset (cleared).

### Before you begin

Before you begin this procedure:

* Ensure that the Fence Controller has been assigned to a Gallagher Controller 7000 or 6000.
* You need to be in the same or parent Division of the Division holding the Fence Controller, and have the "Maintenance Override" operator privilege to perform this procedure.

### Procedure

1. Click **Configure** from the menu bar, then **Hardware**.

   The **Hardware** List Window opens (in [tree view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/tree-view.md)).
2. Highlight the Fence Controller you want to override.
3. Either:

   * **Right click** and select **Properties,** then click the **Status and Overrides** tab.

   OR

   * **Right click** and select **Override...**

     The **Status and Overrides** tab displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-b7bad9a24a5c4d601e187b6ee6fcc5336ae95cd5%2Ffencecontroller_statustab.png?alt=media)
4. Click within the **Override** field and select the required override action from the drop-down list, (i.e. "Shunt", "Unshunt" or "Reset").

   **Note:** This function will not turn the associated Fence Zones on or off.
5. Click the **Override Now** button.

### Result

An override has been applied to this Fence Controller.


---

# 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/configuration-client/licensable-features/perimeter-fence-controllers/overriding-a-fence-controller.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.
