> 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-an-hbus-keypad-reader.md).

# Configuring an HBUS Keypad Reader

### Introduction

This procedure describes how to configure an HBUS Keypad Reader in Command Centre.

***

### Configuration

To configure an HBUS Keypad Reader, 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 Keypad Reader**.

   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-7ef257f592133a508c243213fd4c3f9d2cd4ab53%2Ft30_statusoverridestab.png?alt=media)

   If the keypad reader is removed (from the wall), a tamper alarm is generated. To disable the tamper, 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-8601c142b57455c6cbc195b10bf0edd032f4a3e2%2Ft30_connectionstab.png?alt=media)
2. Select the Controller 6000 or 7000 you want to assign this HBUS Keypad Reader to, from the **Controller** drop-down list.

   **Notes:**

   * HBUS Keypad Readers 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 an HBUS Keypad Reader is connected to a Controller 6000 or 7000 it will automatically be upgraded or downgraded to the version of T30 firmware held by the Controller. This will only happen if the HBUS Keypad Reader 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 HBUS Keypad Reader 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 HBUS Keypad Reader 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 HBUS Keypad Reader itself.

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

</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-7d3cee5eb2a508b744638e2f240982396a5059e3%2Ft30_advancedtab.png?alt=media)
2. Configure as required.

   <table><thead><tr><th width="192">Field</th><th>Description</th></tr></thead><tbody><tr><td>PIN is user code</td><td>When checked the Cardholder’s user code will be required in place of a PIN for any access transactions at this reader and the <strong>User Code grants access when the zone is armed</strong> option activates.</td></tr><tr><td>User code grants access when the zone is armed</td><td>When checked, a Cardholder can gain access to an armed zone using User Code without disarming any Alarm Zone. However, if the Cardholder has the ‘Change to Disarmed state’ privilege, the Alarm Zone(s) will be disarmed upon access.<br><br><strong>Note:</strong> To be able to select this option, you need to select the PIN is user code checkbox first.</td></tr><tr><td>Require MIFARE Enhanced Security encoded cards</td><td><p>When checked, the reader is instructed to only accept cards that have the enhanced security data when deciding whether to grant a Cardholder access. The MIFARE Enhanced security key is configured on the <strong>Card Security</strong> tab of the Server Properties.</p><p><strong>IMPORTANT:</strong></p><p>When this checkbox is unchecked, the reader will be instructed not to send the enhanced security data to the Controller, even if present.</p><p>Leave this checkbox unchecked in the following situations:</p><ol><li>When not using the MIFARE Enhanced Security feature or when not using it for part of a site.</li><li>When some Cardholders requiring access using this reader have not yet had their cards re-encoded. It is important to remember to enable the setting once all cards have been re-encoded.</li></ol><p>Disabling this setting will also allow cards encoded at sites using the MIFARE Enhanced Security feature to be used at sites who are not using this feature.</p><p>In the event of this being enabled, all low security cards will be denied with an event saying <em>"Denied - MIFARE High Security Card Required at [Door]”</em>. To enable both high and low security cards to be used uncheck the checkbox for the Door Reader.</p></td></tr><tr><td>Use MIFARE Serial Number as Card Data</td><td>HBUS Keypad Readers can be set to read the Card Serial Number (CSN) from a MIFARE Card and use it to identify a Cardholder in Command Centre. When enabled, this allows the reader to send the CSN as Cardholder identification to the Controller if it does not detect any other form of Cardholder identification on the card.<br><strong>Additional required configuration:</strong><br>For the Controller to interpret the CSN as a Cardholder's card number, you also need to configure and assign a Universal Card Format. Once this is configured, you can assign cards to Cardholders using the CSN as the card 'Number'. See <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/universal-card-format/universal-card-formats-for-use-mifare-serial-number-as-card-data-csn-mode.md">Universal Card Formats for 'Use MIFARE Serial Number as Card Data' (CSN mode)</a> for the procedure.</td></tr></tbody></table>
3. If you want to configure Double card overrides for this terminal, see [Configuring Local Overrides at Card Readers](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/status-and-overrides/configuring-local-overrides-at-card-readers.md) for further instructions.
4. In the Permitted Card Technology section, **Use the server settings** is selected by default.

   If you want to select other types of cards to be accepted at the reader, uncheck the **Use the server settings** checkbox.

   The other card technologies are enabled.
5. Select the appropriate checkboxes for the types of cards to be accepted.
6. If your site is using MIFARE Plus cards with the ‘X’ feature set and you wish to prevent relay attacks occurring over HBUS, check the **MIFARE Plus** checkbox to enable the **Enforce MIFARE Plus X Card Proximity Checking** checkbox.
7. Check the **Enforce MIFARE Plus X Card Proximity Checking** checkbox.

   The terminal will perform proximity checks when reading a MIFARE Plus X card.

   **Notes:**

   * Checking this option disables all other card technologies.
   * The MIFARE Plus X Card Proximity Checking feature will only work if the site that issued the card is using the same MIFARE Plus/DESFire key seed as your site.
   * Operators need the "Edit Site" privilege to be able to amend this setting.

</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-970654fad71f87a8daa92c458fd33fffc3c99047%2Ft30_audiovisualtab.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>Squiggle LED on</td><td>The squiggle LED can be set to either Off or On. By default, this option is checked. Uncheck it if you want the squiggle LED to be off.</td></tr><tr><td>Volume</td><td>This can be set to Off or Normal.<br>(Default = Normal)</td></tr><tr><td>Alarm Zone</td><td>Click the appropriate radio button for when you want the status of the Alarm Zone to be indicated at the reader:<br><strong>Indicate Alarm Zone status at all times:</strong> (default)<br>When the reader is armed, the Arm button will be red. When disarmed the Arm button will be green.<br><strong>Only indicate Alarm Zone status when changed at the reader:</strong><br>When the Alarm Zone is armed at the reader (via double card override or using the Arm button), the Arm button will indicate the new Alarm Zone status for 10 seconds and then turn off. This gives the user confirmation at the reader that the status change was successful.</td></tr><tr><td>Keep keypad LEDs always on when keypad enabled</td><td>Check this option if you want the HBUS Keypad Reader LEDs to always be active and dimmed when access mode is 'Code Only'.</td></tr></tbody></table>

</details>

<details>

<summary>Mobile Access Settings tab and Bluetooth Actions tab</summary>

These two tabs allow you to configure an HBUS Keypad Reader for Bluetooth® connectivity.

Refer to [Configuring a reader for Mobile Connect](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/mobile-connect/configuring-a-reader-for-mobile-connect.md) for the procedure.

</details>

<details>

<summary>Card Read Output tab</summary>

1. Click the **Card Read Output** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-333e1e3a1cd3b7c067787c11e48a30e262f56335%2Ft30_cardreadoutputtab.png?alt=media)
2. From the **Card Read Output** drop-down list (which includes virtual Outputs), select the Output to switch on when a card is badged at this reader.

   **Note:** Badging a card at this reader will switch on the associated relay. The relay will then be immediately switched off unless the relay Output is configured to pulse, in which case the relay will stay on for the pulse time and then be switched off. The card format does not have to be correct, nor does the card have to be assigned to a Cardholder to trigger the relay.

   **Recommendation:** It is recommended that the Output be configured to pulse (via the **Advanced** tab of the Output's properties). If the Output is not configured as a pulse output then the relay will pulse for 1 second. The Output can be assigned to more than one reader at a time. Each reader will cause the relay to pulse.

</details>

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

   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 reader.

   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 Click the **Custom Fields** tab if you want to add and assign a custom field value to this reader.

    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 this reader.

    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.

### Result

An HBUS Keypad Reader 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-an-hbus-keypad-reader.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.
