> 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/class-5-end-of-line-module-elm/configuring-class-5-elms-for-test-modes.md).

# Configuring Class 5 ELMs for Test Modes

### Introduction

This procedure describes how to configure each Class 5 ELM that requires testing.

**Note:** The normal state of all Class 5 ELMs should be 'closed'. If an ELM is 'open' you will need to reverse the state of the ELM, by checking the ‘Input is inverted’ checkbox on the **Advanced** property page for the ELM.

### 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. **Right click** on the appropriate Class 5 ELM and select **Properties**.
3. Click the **Event Response** tab.
4. If the ELM requires a visual indication that it is working, (e.g. a light turns on when the input is activated) assign an Action Plan to the Open/Off Event Group.

   This Action Plan will need to trigger the light when the ELM changes state.
5. Assign a primary Alarm Zone for all events from the drop-down list.
6. Click the **Testing** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-55953a4bb586c0c7e295c45b65fe018f74940abf%2Fclass5elm_testingtab.png?alt=media)
7. If the ELM requires periodic or manual testing, check the **Include in Alarm Zone Input tests** checkbox.

   The ELM will be included in all periodic and manual tests.
8. If the ELM requires mask testing, check the **This Input must be triggered at least once every X days** checkbox and enter the number of days the ELM must be activated within.

   (Default = 7 days. Configurable from 1 to 30 days.)
9. If the ELM is a seismic detector, check the **Input must trigger during pre-arm** checkbox.
10. Enable the **Walktest Output** if required, by checking the **Enabled** checkbox and configuring as appropriate.

    <table><thead><tr><th width="150">Checkbox/Button</th><th>Description</th></tr></thead><tbody><tr><td>Output Inverted</td><td>When selected, the output operation is inverted, (i.e. it will be on and when operated will turn off).</td></tr><tr><td>+ Walktest Output</td><td>If selected, the output will be 'On High'.</td></tr><tr><td>- Walktest Output</td><td>If selected, the output will be 'On Low'.</td></tr></tbody></table>

    **Notes:**

    * The Walktest Output has three settings, as follows:

      **Off:** High impedence between output terminals.

      **On High:** Output driven to +13V - this will be the on state if ELM has **+ Walktest Output** selected.

      **On Low:** Output driven to GND - this will be the on state if ELM has **- Walktest Output** selected.
    * **Interaction with Input Testing and Pre Arm testing**

      IF ‘Include in Alarm Zone Inputs tests’ is selected for this ELM and the Walktest Output is configured, the Walktest Output will operate (as configured) when Test Mode is selected for the Alarm Zone from the T20 or tested during disarming.

      IF ‘Input must trigger during pre-arm’ is selected and the Walktest Output is configured, the Walktest Output will operate (as configured) during the Pre-Arm.

      IF ‘Include in Alarm Zone Inputs tests’ AND ‘Input must trigger during pre-arm’ are selected, the Walktest Output will operate (as configured).
    * **Interaction with Mask Test**

      There is no requirement to interact with the Mask Testing (this is generally long term testing) and for security purposes the Walktest LED should be disabled on a day to day basis and only turned on when required.
11. Click the **OK** button to exit and save your changes.
12. Repeat this procedure for each ELM that requires testing.


---

# 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/class-5-end-of-line-module-elm/configuring-class-5-elms-for-test-modes.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.
