> 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/server-properties/hbus-terminal-defaults.md).

# HBUS Terminal Defaults

### Introduction

These tabs enable you to specify the site wide Alarms List Defaults, Arming Defaults, Idle Images and Mimic Panel LED Settings for all HBUS Terminals or HBUS Contact Card Readers.

### Procedure

1. Open the **Command Centre Server Properties** window. [How?](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/opening-the-server-properties-window.md)
2. Click the **HBUS Terminal Defaults 1** tab.

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

   <table><thead><tr><th width="144">Field</th><th>Description</th></tr></thead><tbody><tr><td>Alarms List Defaults</td><td><p>When the <strong>Acknowledge alarms when disarming</strong> checkbox is checked, all terminals configured to use the default settings will acknowledge all alarms at or above the selected priority, for the Alarm Zone(s) the Cardholder disarms using the terminal. The acknowledged alarms will only display if the <strong>View acknowledged alarms after disarming</strong> checkbox is checked.<br><br><strong>Notes:</strong></p><ul><li>This is the default setting for all terminals however this setting can be changed on individual terminals.</li><li>This functionality does not apply when the terminal is configured for access, (i.e. when the terminal is assigned as a reader, or disarming as part of an access decision).</li><li>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.</li></ul></td></tr><tr><td>Arming Defaults</td><td>This field enables you to enter an arming/disarming failed message. All terminals configured to use the default settings will display this message when an arming/disarming failed event occurs at the terminal. Maximum 60 characters.<br><br><strong>Note:</strong> This is the default setting for all terminals however this setting can be changed on individual terminals.</td></tr><tr><td>Screen</td><td><p>These options allow you to display a custom image, (e.g. company logo) on the terminal Welcome screen when idle, (i.e. when logged off), and/or a custom icon when access is granted or denied. The idle image will be displayed when the terminal has been idle for 10 seconds.<br>Check the appropriate checkbox(es) for when you want an image to display, (i.e. <strong>Display custom image when idle</strong>, <strong>Display custom image when access is granted</strong> and/or <strong>Display custom image when access is denied</strong>), then either 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>Only <strong>.png</strong>, <strong>.jpg</strong> and <strong>.jpeg</strong> files can be displayed.</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.</li><li>This is a default setting for all terminals however this setting can be changed on individual terminals.</li></ul></td></tr><tr><td>Tones</td><td><p>These options allow you to play a custom tone on the terminal when access is granted and/or denied.<br>Check the appropriate checkbox(es) for when you want a tone to play, (i.e. <strong>Play custom tone when access is granted</strong> and/or <strong>Play custom tone when access is denied</strong>), then either type in the name of the sound file to be played or click the <strong>Browse</strong> button to locate the sound file.<br><br><strong>Notes:</strong></p><ul><li>Only<strong>.wav</strong> and <strong>.mp3</strong> files can be played.</li><li>The sound file will play for a maximum of 3 seconds, and will be no bigger than 100 kilobytes.</li><li>Select the <strong>Preview</strong> button to review the selected tone.</li><li>Tones can be distorted by the limited T20 speaker, therefore it is recommended custom tones are tested on T20 hardware.</li><li>This is a default setting for all terminals however this setting can be changed on individual terminals.</li></ul></td></tr><tr><td>Failed Logon Lockout</td><td><p>When the <strong>Lockout for 90 seconds after failed logon attempts</strong> checkbox is checked, all terminals configured to use the default settings will be locked 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>The default will be off for sites that already have terminals installed. For sites installing new terminals 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><li>The above settings are not applicable when using a PIV card at an HBUS Contact Card Reader. The PIV card will be locked after 5 consecutive failed PIN entries.</li></ul></td></tr></tbody></table>
4. The **Require alarms to be acknowledged at both a Terminal and Command Centre** option is for sites wanting to ensure an alarm is acknowledged or processed locally (by the guard) whilst still requiring the monitoring station to manage alarms in the normal way.

   Ticking this checkbox means alarms that are acknowledged at a T20 or T21 will not display as acknowledged in Command Centre. Likewise, alarms that are acknowledged or processed in Command Centre will not be removed or display as acknowledged at the T20 or T21.

   **Notes:**

   * Sirens (or other outputs) will only be silenced when the alarm is acknowledged at the T2x and not when it is acknowledged in Command Centre.
   * Events indicate whether the acknowledge or processing was undertaken at the T2x or Command Centre.
5. Click the **HBUS Terminal Defaults 2** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-fb90c54f4d496f54a70c4bd93b3f255b9147dbf8%2Fhbusterminaldefaults2.png?alt=media)
6. Configure the Mimic Panel LED Response for each item state. LED Responses are:
   * Off
   * Red
   * Green
   * Orange
   * Red Slow Flash
   * Green Slow Flash
   * Orange Slow Flash
   * Red Fast Flash
   * Green Fast Flash
   * Orange Fast Flash
7. 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/site-installation/server-properties/hbus-terminal-defaults.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.
