> 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-sensors/performing-a-maintenance-mode-override.md).

# Performing a Maintenance Mode Override

### Introduction

This procedure describes how to perform a Maintenance Mode override for a Z10 Tension Sensor Group.

When a sensor group is placed into Maintenance Mode all tension related alarms (attack and maintenance) are suppressed.

Maintenance Mode can be used when tensioning during installation, re-tensioning, or performing maintenance on the fence. To help tension the wires, each sensor is equipped with a tension status LED. This LED provides a visual indication of the current wire tension, based on the fence configuration.

When in Maintenance Mode only, the sensor's LED will display one of the following flash patterns:

<table><thead><tr><th width="246">LED</th><th>Wire Tension Status</th></tr></thead><tbody><tr><td>1 Flash per second (Green)</td><td>The wire tension is within target tension range.</td></tr><tr><td>1 Flash per second (Red)</td><td>The wire is over tensioned.</td></tr><tr><td>1 Flash per second (Blue)</td><td>The wire is under tensioned.</td></tr></tbody></table>

<table><thead><tr><th width="246">LED</th><th>Diagnostic Status</th></tr></thead><tbody><tr><td>3 Flash per second (Red)</td><td>No communications with the Controller.</td></tr><tr><td>2 Flash per second (Red)</td><td>Communications with the Controller, but sensor is not configured.</td></tr><tr><td>1 Flash per second (Green, Red or Blue)</td><td><p>Fully configured and functioning normally.</p><p>The sensor's LED displays the current wire tension status.</p></td></tr></tbody></table>

<table><thead><tr><th width="246">LED</th><th>Tension Overload Status</th></tr></thead><tbody><tr><td>3 Flash for 3 seconds (Green), then<br>3 Flash for 3 seconds (Red, Blue then Green)</td><td>The wire tension is within target tension range. The sensor has reported a tension overload event.</td></tr><tr><td>3 Flash for 3 seconds (Red), then<br>3 Flash for 3 seconds (Red, Blue then Green)</td><td>The wire is over tensioned. The sensor has reported a tension overload event.</td></tr><tr><td>3 Flash for 3 seconds (Blue), then<br>3 Flash for 3 seconds (Red, Blue then Green)</td><td>The wire is under tensioned. The sensor has reported a tension overload event.</td></tr></tbody></table>

**Notes:**

* A Maintenance Mode override is retained during a power or communications failure. If the override mode is changed during this time, the sensor group will follow the new override mode as soon as communications are restored.
* Shunting a sensor group takes precedence over a Maintenance Mode override. When a sensor group is shunted, all tension related alarms (attack and maintenance) are suppressed. All sensor LED activity ceases. However, each sensor will continue to report tension and temperature.

### Before you begin

Before you begin this procedure:

* Ensure you have configured a sensor group. Refer to the topic [Configuring a Z10 Tension Sensor Group](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/perimeter-sensors/configuring-a-z10-tension-sensor-group.md).
* Ensure the operator has been assigned the "Maintenance Override" operator privilege.

### Procedure

1. Click **Configure** from the menu bar, then **Z10 Tension Sensor Group**.

   The **Z10 Tension Sensor Group** List Window opens.
2. **Right click** the appropriate Z10 Tension Sensor Group, and click **Override...** from the drop-down menu.

   The **Status and Overrides** tab on the Properties window for the item displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-74775e0f4b166cb801a72c988e84c13427bb2899%2Fdts_maintenancemodeoverride.png?alt=media)
3. Click within the Override field and select **Maintenance Mode** from the drop-down list.
4. Click the **Override Now** button.

   From this screen you can see the status change as a result of the override.
5. Click the **OK** button.

### Result

The Z10 Tension Sensor Group is now in Maintenance Mode:

* The Z10 Tension Sensor Group icon now displays a yellow screw driver, indicating the sensor group is in Maintenance Mode.
* All tension related alarms (attack and maintenance) for this group are suppressed. Voltage and offline alarms will still be generated.
* LED activity commences for all sensors within this group.
* A Maintenance Mode alarm is raised in Command Centre. For example, *\[Z10 Tension Sensor Group Name] - Maintenance Mode override in effect*. This alarm remains active, until the Maintenance Mode override is cancelled.


---

# 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-sensors/performing-a-maintenance-mode-override.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.
