> 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-a-class-5-elm.md).

# Configuring a Class 5 ELM

### Introduction

This procedure describes how to configure a Class 5 ELM in Command Centre.

***

### Configuration

To configure a Class 5 ELM, perform the following procedures in Gallagher Configuration Client:

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** and select **New\...HBUS Devices**.
3. Select **Class 5 End-of-Line Module**.

   By default the **General** tab displays.
4. Complete the fields as required.

   For further detail see [General tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/general-tab.md).
5. Click the **Event Response** tab, and configure as required.

   For further detail see [Event Response tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/event-response-tab.md).
6. Click the **Alarm Instructions** tab, and configure as required.

   For further detail see [Alarm Instructions tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/alarm-instructions-tab.md).
7. Click each tab in turn to configure the Class 5 ELM:

<details>

<summary>Connections tab</summary>

1. Click the **Connections** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-a56a82053e7eac961aca3037275b9277bbd4897c%2Fclass5elm_connectionstab.png?alt=media)
2. Select the Controller 6000 you want to assign this ELM to, from the **Controller** drop-down list.

   **Note:** When an HBUS device is added to a Controller 6000, it will appear on the **HBUS Devices** tab of the Controller. In this case, the **Controller** field will be pre-populated with that Controller name.
3. If not already present, enter the HBUS serial number (10 character hexadecimal string) into the **HBUS Serial Number** field.

   **Note:** The HBUS serial number is optional, however the ELM will be considered as not properly configured unless one is entered.
4. If you click the **Apply** button, software version numbers display.

   The **Configured Version** is the version of the device software in the configured Controller 6000 FTS file, (i.e. not the version of the Controller 6000 software). The Current Version is the version of software as last reported by the ELM itself.

</details>

<details>

<summary>Reflected Outputs tab</summary>

1. Click the **Reflected Outputs** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-ec19fd7538959f18e7434871d14fc28723187d81%2Fclass5elm_reflectedoutputstab.png?alt=media)
2. Drag and drop the appropriate Output(s) into the two grids.

   The top grid lists the Output(s) that reflect the closed state of the Input, and the bottom grid lists the Output(s) that reflect the opposite state of the Input.

   **Note:** The Output will only be reflected to the Alarm Input on the ELM.

</details>

<details>

<summary>Messages tab</summary>

1. Click the **Messages** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-12f4e9d5896566a90dedc060849616c3ff15753a%2Fclass5elm_messagestab.png?alt=media)
2. Enter the state and event names (if different from the site-wide default), that will display in Command Centre when this ELM is activated and deactivated.

</details>

<details>

<summary>Advanced tab</summary>

1. Click the **Advanced** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-e40dd9b7540954a7000e6b82c757ba44e4b9d5aa%2Fclass5elm_advancedtab.png?alt=media)
2. Tick the checkboxes as required.

   <table><thead><tr><th width="144">Checkbox</th><th>Description</th></tr></thead><tbody><tr><td>Input is inverted</td><td>If checked, the state of the Input is reversed, (i.e. the system considers the Input 'open' when it is closed, and 'closed' when it is open).</td></tr><tr><td>Input can not be isolated</td><td>If checked, the Input will not be ignored when an Alarm Zone is armed with the ‘Isolate’ option.</td></tr></tbody></table>
3. Select the required state for this Class 5 ELM from the **State Settings** drop-down list. The options are:

   <table><thead><tr><th width="274">Checkbox</th><th>Description</th></tr></thead><tbody><tr><td>Use Default</td><td><p>This is the default setting.</p><p>Selecting this option means that the global state setting (as configured on the <strong>Advanced</strong> tab of the Server Properties) will apply.</p></td></tr><tr><td>Trouble Output = Masked State</td><td>This setting indicates the Masked state.</td></tr><tr><td>Trouble + Alarm Outputs = Masked State; Trouble Output = Fault State</td><td><p>Selecting this option means that trouble and alarm means Masked, and trouble alone indicates Fault.</p><p>If this state is selected, ensure that a fault state is not raised accidentally (via the Trouble input).</p><ul><li><p>If the Trouble and Alarm inputs are opened together, one will always appear to open briefly before the other:</p><ul><li>If the Alarm input opens first, an Alarm state (Input Open) is raised just before the Masked state is raised.</li><li>If the Trouble input opens first and the Alarm input is opened within 2 seconds, only a Masked state is raised.</li><li>If the Trouble input opens first and the Alarm input is opened after 2 seconds, a Fault state is raised and then a Masked state is raised.</li></ul></li><li>If the Alarm input is opened on its own, the Alarm state will immediately initiate.</li><li>If the Trouble input is opened on its own, the Fault state will initiate after 2 seconds.</li></ul></td></tr><tr><td></td><td><p>If both the Trouble and Alarm inputs are open and the ELM is in Masked state, closing the inputs will have this effect:</p><ul><li>If the Trouble input is closed first, an Alarm (Input Open) state is reported, and then an Input Closed state once the Alarm input closes.</li><li>If the Alarm input is closed first and the Trouble input is closed within 2 seconds, only an Input Closed state is reported.</li><li>If the Alarm input is closed first and the Trouble input is closed after 2 seconds, only an Input Closed state is reported and then a Fault state is raised.</li></ul></td></tr></tbody></table>

</details>

8. Click the **Cameras** tab if you want to associate a DVR Camera(s) with this Class 5 ELM.

   For further details see [Cameras tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/cameras-tab.md).
9. Click the **Icons** tab if you want to change the Icon Set for this Class 5 ELM.

   For further details regarding the **Icons** tab, see [Icons](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/icons.md).

   **Note:** There are separate states for the Class 5 ELM, (i.e. Closed, Open, Unknown, Masked, Tamper and Offline). The Tamper state will override any other states.
10. Click the **Custom Fields** tab if you want to add and assign a custom field value to the Class 5 ELM.

    For further details regarding the **Custom Fields** tab, see [Custom Fields](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/custom-fields.md).
11. Click the **Notes** tab if you want to add a note(s) about the Class 5 ELM.

    For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).
12. Click **OK** to exit and save your changes.

    Click **Cancel** to exit without saving your changes.

    Click **Apply** to save your changes and stay in this window.


---

# 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-a-class-5-elm.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.
