> 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/using-service-mode.md).

# Using Service mode

### Introduction

Service mode is available on the F31, F32, F41 and F42 Fence Controllers only.

Service mode provides a convenient means for controlling Fence Zones at the Fence Controller, without using Command Centre or a terminal. It ensures the technician’s safety when working on the fence by temporarily removing Fence Zone control from Command Centre and its associated terminals.

### Procedure

1. To enable Service mode, check the **Allow use of Service Mode for local control** checkbox on the **Advanced** tab in the appropriate Fence Controller’s properties.
2. To enter Service mode, set the Service Mode SW1 dipswitch 1 to ON.

   When Service mode is entered:

   * An active Service mode alarm is raised (the Service icon on the Fence Controller is lit, red and flashing while the Fence Controller is in Service mode). The alarm remains active and cannot be processed until you exit Service mode.
   * All system and fence alarms continue to be raised while in Service mode. The alarms are visible via the Fence Controller icons, in Command Centre and at a terminal.

     Inactive alarms reset at the Fence Controller will remain visible in Command Centre and at a terminal. Inactive alarms processed in Command Centre but not reset at the Fence Controller, remain visible at the Fence Controller.
   * The Fence Zones are initially disarmed.
   * The Fence Controller no longer responds to Command Centre or terminal state changes to arm or disarm the Fence Zones.
   * The Fence Controller continues to follow the set HV/LF mode and responds to any changes made to the HV/LF mode.
   * The Fence Zone control via the magnetic key operates on a toggle; arming the Fence Zone if it is currently disarmed; disarming the Fence Zone if it is currently armed. Each Fence Zone operates independently by presenting the magnetic key to each Fence Zone icon "+" or "-".

     Presenting the magnetic key to the Fence Controller will reset all inactive alarms displayed on the Fence Controller.

     Inactive alarms reset at the Fence Controller will remain visible in Command Centre and at a terminal. Inactive alarms processed in Command Centre but not reset at the Fence Controller, remain visible at the Fence Controller.

   When Service mode is exited:

   * The Service icon on the Fence Controller is restored (solid red).
   * The Service mode alarm changes to inactive and can be processed.
   * The Fence Zones immediately follow the status as set by Command Centre.
   * Presenting the magnetic key no longer arms or disarms the Fence Zones but will reset all inactive alarm conditions.

   **Notes:**

   * If a Fence Zone is placed in Lockout mode from a terminal, no indication of Lockout mode is visible on the Fence Controller. When subsequently placed in Service mode, the magnetic key cannot be used to arm/disarm Fence Zones that are in Lockout. The magnetic key will clear all inactive alarms.
   * Placing the Fence Controller in Service mode when the Fence Controller is offline or shunted has no effect on behaviour, (i.e. Fence Zones cannot be controlled via the magnetic key), even if Service mode was enabled prior to the Fence Controller going offline or being shunted.
   * If the Fence Controller is in HBUS mode (not Stand Alone mode) and not connected to Command Centre, Service mode cannot be entered.


---

# 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/using-service-mode.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.
