> 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/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-changing-the-hv-lf-mode-for-an.md).

# Change alarm zone voltage mode

Change all compatible fence zones within an alarm zone between high voltage and Low Feel modes.

📎 **Compatibility:** Low Feel mode is available on every Gallagher energiser.

**Required privilege:** the cardholder must belong to an Access Group that lists the Alarm Zones assigned to the Fence Zones, with the "Change fence HV/LF mode" privilege configured.

### Procedure

1. Log on to the terminal.
2. Press the **More** soft key on "Choose Action". The "Main Menu" displays.
3. Scroll to **"Alarm Zones & HV/LF"** and press the key. The "Alarm Zones L/H" screen displays.
4. Only Alarm Zones assigned to Fence Zones for which the operator has the "Change fence HV/LF mode" privilege, associated with this RAT, appear.
5. Status indicators: A = Armed, D = Disarmed, 1 = User 1, 2 = User 2, ? = Not known.
6. HV/LF indicator: HV = High Voltage, LF = Low Feel.
7. If the list is empty, "The list is empty" displays.
8. Select the required Alarm Zone and press the key. The **HV/LF mode changes for ALL fences associated with that Alarm Zone**.

***

🔗 **Related**

* [Keypads - Changing the HV//LF mode for a Fence Zone](/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-changing-the-hv-lf-mode-for-a.md). Change one fence zone rather than all fences in an alarm zone.
* [Keypads - Monitoring Fence Zone voltages](/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-monitoring-fence-zone-voltages.md). Check the current mode and voltages.


---

# 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/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-changing-the-hv-lf-mode-for-an.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.