> 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-walk-test-mode-override.md).

# Performing a Walk Test Mode Override

### Introduction

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

When a sensor group is placed into Walk Test Mode the sensor's LED will turn solid green. If the sensor has reported a tension overload event, the sensor's LED will display the tension overload status. When an alarm condition is detected, the sensor's LED will change to red, and remain red until the alarm condition is removed.

Walk Test Mode can be used to provide visual evidence that an alarm can be generated by the sensor.

When such an event occurs, a Walk Test Mode Attack alarm is raised in Command Centre. For example, \[*Z10 Tension Sensor Group Name* ] wire \[*Number* ] detected an attack. This alarm allows an operator to generate an Activity Report detailing all alarms raised.

**Notes:**

* A Walk Test 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 Walk Test 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 **Walk Test 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 Walk Test Mode:

* The Z10 Tension Sensor Group icon now displays a yellow screw driver, indicating the sensor group is in Walk Test Mode.
* The Event Group Walk Test Mode Attack will be used to report attack alarms for this sensor group.
* LED activity commences for all sensors within this group.
* A Walk Test Mode alarm is raised in Command Centre. For example, *\[Z10 Tension Sensor Group Name] - Walk Test Mode override in effect*. This alarm remains active, until the Walk Test 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-walk-test-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.
