> 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/site-installation/hardware/configuring-hbus-terminals/configuring-an-hbus-alarms-only-terminal.md).

# Configuring an HBUS Alarms Only Terminal

### Introduction

This procedure describes how to configure an HBUS Alarms Only Terminal in Command Centre.

Other procedures associated with configuring an HBUS Alarms Only Terminal are:

* [Configuring Access Group Privileges for Terminal Access](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/access-groups/configuring-access-group-privileges-for-terminal-access.md)
* [Configuring User Codes for Terminal Access](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/cardholders/configuring-a-user-code-for-terminal-access.md)
* [HBUS Terminal Defaults](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/hbus-terminal-defaults.md)

**Notes:**

* Operators require the "Edit Site" operator privilege to perform this procedure and must be in the same or parent Division of the HBUS Alarms Only Terminal.
* To change the date and time format, for all terminals, refer to the topic [HBUS Terminal: Date and time format](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/configuring-hbus-terminals/hbus-terminal-date-and-time-format.md).
* The language displayed on the terminal, is configured on the **Software** tab of the host Controller’s properties. When configured for English text (the default), the terminal displays the month using abbreviations, (e.g. Jan, Feb, Mar) When configured for non-English text, the terminal displays the month as configured for the selected language. Ensure you configure messages for terminals in the same language as is set on their host Controller's Software tab.
* Command Centre data, (e.g. Event messages and item states) are sent to the terminal using the language selected on the Command Centre server. Command Centre editable fields, (e.g. Alarm Zone names and Input names) are sent to the terminal, as entered in Command Centre.

***

### Minimum configuration requirements

The terminal will display the message "Not Configured" unless the following configuration has been completed:

* On the **Connections** tab, assign the terminal to a Controller 6000 or 7000 and enter the terminal's HBUS serial number (10 character hexadecimal string).
* On the **Alarm Zones** tab, assign at least one Alarm Zone to the terminal.

***

### Configuration

To configure an HBUS Alarms Only Terminal, 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 **HBUS Alarms Only Terminal**.

   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 and configure the reader properties as required:

<details>

<summary>Status and Overrides tab</summary>

1. Click the **Status and Overrides** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-1004922313001710670c30bab7815c817c5b5afc%2Fhbusalarmsonlystatustab.png?alt=media)

   If the terminal is removed (from the wall), a tamper alarm is generated. To prevent this from happening, tick the **Disable Tamper** checkbox.
2. To perform an override, click within the **Override** field and select the required override action from the drop-down list, then click the **Override Now** button.

   For a description on each of the override actions that can be performed for this device, see [Performing Overrides](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/status-and-overrides/performing-overrides.md).

   **Note:** This device does not support timed overrides. All overrides are immediate and persist until specifically cancelled by an operator.

</details>

<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-57968b05785c160697d216a9523ad7e1261126e1%2Fhbusalarmsonlyconnectionstab.png?alt=media)
2. Select the Controller 6000 or 7000 you want to assign this terminal to, from the **Controller** drop-down list.

   **Notes:**

   * HBUS Alarms Only Terminals can be created via the **HBUS Devices** tab of a Controller. In that case the **Controller** field would be pre-populated with that Controller name. Refer to the topic [Configuring HBUS Devices](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/configuring-hbus-devices.md).
   * When a terminal is connected to a Controller 6000 or 7000 it will automatically be upgraded or downgraded to the version of T20 firmware held by the Controller. This will only happen if the terminal is correctly configured. A download bar displays on the **Connections** tab, showing the approximate progress of the download.

     If the download fails for whatever reason, the terminal will revert to the previous version of code. A Code Download Fail event is raised in Command Centre.
3. Enter the HBUS serial number (10 character hexadecimal string) into the **HBUS Serial Number** field. This serial number is located on the unit.

   **Note:** The HBUS serial number is optional, however the terminal 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 FTS file, (i.e. **not** the version of the Controller software). The **Current Version** is the version of software as last reported by the terminal itself.

   **Note:** For the terminal to report its current version of software, an Alarm Zone must be assigned to the **Event Response** tab of the terminal’s properties.

</details>

<details>

<summary>Welcome Screen tab</summary>

1. Click the **Welcome Screen** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-7721440b492db098364463f4b19d70de58feb744%2Fhbusalarmsonlywelcomescreentab.png?alt=media)

   This screen enables you to display the status of a selected Alarm Zone and control the timeouts for this terminal, when a Cardholder attempts to log on using the function keys on this terminal.
2. Configure as required.

   <table><thead><tr><th width="192">Field</th><th>Description</th></tr></thead><tbody><tr><td>Display Alarm Zone</td><td><p>Select the Alarm Zone that will be displayed on the terminal, from the <strong>Display Alarm Zone</strong> drop-down list. When the Alarm Zone is armed, the armed icon displays.<br><br><strong>Notes:</strong></p><ul><li>The choice of Alarm Zone is restricted to only those associated with the terminal on the <strong>Alarm Zones</strong> tab.</li><li>Deselect the <strong>Display Alarm Zone Status on Welcome Screen</strong> checkbox, if you do not want to display the status of the Alarm Zone.</li><li>Check the <strong>Display Entry Delay Countdown</strong> and/or <strong>Display Exit Delay Countdown</strong> checkboxes if required. Displaying the Entry Delay Countdown informs a user of the time left before an alarm is triggered. Displaying the Exit Delay Countdown provides a user arming an Alarm Zone via the T20 an indication of how long they have left until exit delay expires. These checkboxes will be disabled if no Display Alarm Zone is selected.</li></ul></td></tr><tr><td>Timeouts</td><td>In the <strong>Inactivity</strong> timeout field, enter the period of time (in seconds) of inactivity before a Cardholder will be logged off the terminal. Default 20 seconds.<br><br><strong>Note:</strong> If the terminal has not been used for 30 seconds, the screen and keypad backlight will dim. Hence if the inactivity period is greater than 30 seconds and the terminal has not been used, the screen and backlight will dim whilst the user is logged on.<br>In the <strong>PIN</strong> timeout field, enter the period of time (in seconds) that a user has to enter their PIN or User Code at the terminal in order to log on. Default 10 seconds.</td></tr><tr><td>Display Alarms in System notifications</td><td>Deselect the <strong>Display Alarms in System notification</strong> checkbox, if you do not want to display the red alarm notification banner on the Welcome screen or Mimic Panel screen of the terminal.</td></tr><tr><td>Display Inputs Isolated / Shunted notification</td><td>Deselect the <strong>Display Inputs Isolated / Shunted notification</strong> checkbox, if you do not want to display the yellow isolated/shunted banner on the Welcome screen of the terminal, when one or more inputs in any of the Alarm Zones associated with the T20 is shunted or isolated.<br><br><strong>Note:</strong> If the Input is not assigned to the terminal, the banner will display without the ability for a user to address the issue directly from the terminal.</td></tr><tr><td>Use site default Failed Logon Lockout settings</td><td><p>Deselect the <strong>Use site default Failed Logon Lockout settings</strong> checkbox, if you want to configure the failed logon lockout settings specifically for this terminal.<br>Select the <strong>Lockout for 90 seconds after failed logon attempts</strong> checkbox. The terminal will be locked out for a period of 90 seconds after the <strong>Number of failed logon attempts</strong> has been exceeded. Default 3. Range 3-10.<br>If required, enter the <strong>Number of subsequent failed logon attempts</strong> to occur before the terminal is locked out again. Default 1. Range 1-10.<br><br><strong>Notes:</strong></p><ul><li>Failed Logon Lockout is configurable via the Server Properties. The default will be off for sites that already have T20s installed. For sites installing new T20s the default will be on.</li><li>The repeated use of the same user code or PIN will only count as a single attempt.</li><li>If the number of failed logon attempts reaches a certain number, then a tamper alarm is raised. This number is either the total of the two configurable amounts plus 1, or 7 attempts - whichever is reached first. The terminal will display the message "<em>Temporarily locked out</em>" with a red "X" on screen.</li></ul></td></tr></tbody></table>

</details>

<details>

<summary>Alarm Zones tab</summary>

1. Click the **Alarm Zones** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-d9eff91b752bb7b9a77f6e814a5d01bfa71ece9f%2Fhbusalarmsonlyalarmzonestab.png?alt=media)
2. Click **Configure** from the menu bar, then **Alarm Zones**.

   The **Alarm Zone** List Window opens.

   Select the Alarm Zones you wish to associate with this terminal, and drag and drop them into the **Alarm Zones** grid.

   **Notes**:

   * In order to display Inputs, Outputs, Fence Controllers and Fence Zones within the terminal user interface, the Alarm Zones assigned to these items must be assigned to the terminal.
   * Up to 50 Alarm Zones can be associated with one terminal.

     Assigning many Alarm Zones that are hosted by remote Controllers, may impact on the performance of the terminal.
   * All inactive/acknowledged alarms and all inactive/processed alarms older than 28 days are not displayed on the terminal.
   * Duress alarms are not displayed on the terminal.
   * A maximum of 200 alarms are displayed on the Current Alarms screen, listed in order of priority.
   * A maximum of 100 alarms are displayed on the Alarm History screen, listed in order of date/time occurrence.
   * The terminal cannot be assigned to an Elevator Car or Elevator Car HLI, if Alarm Zones have been assigned to the terminal.
   * If a Short Name has been entered for an Alarm Zone, this will be displayed in the terminal user interface, instead of the Name.
   * It is not possible to assign an HBUS Terminal with Alarm Zones to a Locker Bank.
3. Once you have all the Alarms Zones you require in the window, you can re-order the Alarm Zones by using the **up** and **down** arrow buttons to the right of the window.

   **Note:** The order you sort the Alarm Zones in here will be the order they appear in the terminal user interface.
4. Configure as required.

   <table><thead><tr><th width="192">Field</th><th>Description</th></tr></thead><tbody><tr><td>Use site default Alarms List settings</td><td>When checked, the terminal will use the Alarms List Defaults, configured on the <strong>HBUS Terminal Defaults</strong> tab in the <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/hbus-terminal-defaults.md">Server Properties</a>. By default the terminal will display all alarms at or above ‘Very Low Priority’ for the Alarm Zone(s) assigned to the terminal.<br>To configure the Alarm List settings specific for this terminal, deselect the <strong>Use site default Alarm List settings</strong> checkbox. Configure the Alarm List settings for this terminal as required.<br><br><strong>Note:</strong> The alarms displayed and acknowledged are determined by the Alarm Zones assigned to the Cardholder’s Access Group(s) and the Terminal Privileges configured within these Access Groups.</td></tr><tr><td>Use site default Arming settings</td><td>When checked the terminal will use the Arming Defaults, configured on the <strong>HBUS Terminal Defaults</strong> tab in the <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/hbus-terminal-defaults.md">Server Properties</a>. By default, no arming/disarming failed message is displayed.<br>To configure the Arming settings specific for this terminal, deselect the <strong>Use site default Arming settings</strong> checkbox. Enter the arming/disarming failed message to be displayed by this terminal. Maximum 60 characters.</td></tr></tbody></table>
5. Depending on the required configuration, you can prevent certain Access Groups from Controlling (arming or disarming) a specified Alarm Zone from this terminal.

   Do you want to configure this option?

   If **yes**, go to Step 6.

   If **no**, go to the next tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-c5e89fe8e70329f34ab50429622a207cfa5540e5%2Fhbusterminal_alarmzone_preventag2.png?alt=media)
6. Click **Manage** from the menu bar, then **Access Groups**.

   The **Access Group** List Window opens.

   Select the Access Group(s) you wish to associate with this terminal, and drag and drop them into the bottom grid.
7. Click the Access Group to select it.

   The Alarm Zone drop-down list activates.
8. From the **Alarm Zone** drop-down list, select the Alarm Zone which you do not want the Access Group to Control (i.e. arm/disarm).

</details>

<details>

<summary>Inputs tab</summary>

1. Click the **Inputs** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-372d1de7e23174a7e993021991c684f16db2a5b7%2Fhbusalarmsonlyinputstab.png?alt=media)
2. From the **Hardware** List Window, select the Inputs you wish to have controlled by this terminal.

   Drag and drop them into the **Inputs** tab window.

   **Notes:**

   * Up to 100 Inputs can be monitored by one terminal.
   * If a Short Name has been entered for an Input, this will be displayed in the terminal user interface, instead of the Name.

</details>

<details>

<summary>Fence Controllers tab</summary>

1. Click the **Fence Controllers** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-712e1b461e21499c903bb49be48580c54b55fdfb%2Fhbusalarmsonlyfencecontrollerstab.png?alt=media)

   This tab allows you to configure Fence Controllers so they can be monitored and controlled from this terminal.
2. From the Hardware List Window, select the Fence Controllers you wish to associate with this terminal, and drag and drop them into the **Fence Controllers** tab window.

   **Notes:**

   * Up to 25 Fence Controllers, (e.g. 50 Fence Zones) can be associated with one terminal.
   * Only F31, F32, F41, F42 and F22 Fence Controllers can be associated with this terminal.
3. Once you have all the Fence Controllers you require in the window, you can re-order the Fence Controllers by using the **up** and **down** arrow buttons to the right of the window.

   **Note:** The order you sort the Fence Controllers in here will be the order they appear in the terminal user interface.

</details>

<details>

<summary>Mimic Panel tab</summary>

1. Click the **Mimic Panel** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-81d9140c2fdd94be59c31687afbf07378dbdf9bf%2Fhbusalarmsonlymimicpaneltab.png?alt=media)

   This screen enables you to configure the 8 LEDs on either side of the terminal to show the status of Alarm Zones, Inputs or Outputs.
2. Select the drop-down arrow for the LED number (1-8) you wish to assign an Alarm Zone, Input or Output to. Select an Alarm Zone, Input or Output from the drop-down list.

   The item’s name is automatically populated in the free text label field below.

   To display the Alarm Zone, Input or Outputs name on the terminal, select the **Display labels on Welcome Screen** checkbox. The name shown in the free text label field will be displayed on the terminal beside the relevant LED, when the terminal is idle.

   If required, edit the free text label field for each item. Maximum 60 characters.

   **Notes:**

   * Press the \* key on the terminal to display the free text labels at any time.
   * The colour of the LEDs and flash states can be configured on the **HBUS Terminal Defaults** tab in the Server Properties.

</details>

<details>

<summary>Outputs tab</summary>

1. Click the **Outputs** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-d7ca72706e79c0e30a1a72cd402f356283495494%2Fhbusalarmsonlyoutputstab.png?alt=media)
2. From the **Hardware** List Window, select the Outputs you wish to trigger (On/Off) using this terminal.

   Drag and drop them into the **Outputs** tab window.

   The default **Menu item name** 'Actions' will be used within the terminal user interface. Change the **Menu item name**, if required. Maximum of 25 characters.

   The Output Name will be used within the terminal user interface. To use a different name within the terminal user interface, enter a **Label** for the Output. Maximum of 60 characters.

   If you require a non-authorised user, (i.e. terminal log on is not required) to be able to activate an Output, check the **On Options Menu** checkbox for the Output. The Output will appear on the Options Menu within the terminal user interface. A maximum of 5 Outputs can be added to the Options Menu. The Options softkey will only display if one or more Outputs have been configured to display on the Options Menu.

   **Note:** Up to 100 Outputs can be monitored by one terminal.
3. Once you have all the Outputs you require in the window, you can re-order the Outputs by using the **up** and **down** arrow buttons to the right of the window.

   **Note:** The order you sort the Outputs in here will be the order they appear in the terminal user interface.

</details>

<details>

<summary>Audio Visual tab</summary>

1. Click the **Audio Visual** tab.

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

   <table><thead><tr><th width="192">Field</th><th>Description</th></tr></thead><tbody><tr><td>LED</td><td>This can be set to either Off or On.<br>(Default = On)</td></tr><tr><td>Volume</td><td>This can be set to Off, Quiet, Normal or Loud.<br>(Default = Normal)</td></tr><tr><td>Warning beep when alarms in system</td><td>When checked, the terminal will beep if an alarm is in the system. Configure the appropriate volume, as required.<br>Default = Unchecked</td></tr><tr><td>Screen</td><td><p>Check the <strong>Always on</strong> checkbox if you want the terminal screen to always be on. This option is useful when using the Mimic Panel functionality.<br>You can display an Idle Image on the terminal, (e.g. company logo). This image will display instead of the Welcome screen, (i.e. when logged off) and the terminal has been idle for 10 seconds. Either:</p><ul><li>leave the <strong>Use site default Idle Image settings</strong> checkbox checked to use the site wide image setting (on the <strong>HBUS Terminal Defaults 1</strong> tab of the Server Properties),<br>OR</li><li><p>uncheck the <strong>Use site default Idle Image settings</strong> checkbox and check the <strong>Display custom image when idle</strong> checkbox instead to select an image for this terminal. Type in the name of the image file to be displayed or click the <strong>Browse</strong> button to locate the image file.<br><br><strong>Notes:</strong></p><ul><li>When browsing for an image, only <strong>.png</strong>, <strong>.jpg</strong> and <strong>.jpeg</strong> files display.</li><li>The image size should be 320x240 pixels.</li><li>Select the <strong>Preview</strong> button, to preview how the image will look when displayed on the terminal.</li></ul></li></ul></td></tr></tbody></table>

</details>

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

   For further details regarding the **Cameras** tab, see [Cameras](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 terminal.

   For further details regarding the **Icons** tab, see [Icons](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/icons.md).
10. Click the **Notes** tab if you want to add a note(s) about this terminal.

    For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).
11. 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.

### Result

An HBUS Alarms Only Terminal has been configured, assigned to a Controller 6000 or 7000, and is ready for use.


---

# 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/site-installation/hardware/configuring-hbus-terminals/configuring-an-hbus-alarms-only-terminal.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.
