> 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-contact-card-reader.md).

# Configuring an HBUS Contact Card Reader

### Introduction

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

Other procedures associated with configuring an HBUS Contact Card Reader 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 Contact Card Reader.
* To change the date and time format, for all HBUS Contact Card Readers, 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 HBUS Contact Card Reader, is configured on the **Software** tab of the host Controller’s properties. When configured for English text (the default), the HBUS Contact Card Reader displays the month using abbreviations, (e.g. Jan, Feb, Mar) When configured for non-English text, the HBUS Contact Card Reader 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 HBUS Contact Card Reader 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 HBUS Contact Card Reader, as entered in Command Centre.

***

### PIV functionality

* Only PIV cards can be read by the reader's card slot.
* Both Global and Application PINs are supported. The PIN used is the preferred PIN according to the card's Discovery object. When there is no preferred PIN, the Application PIN is used.
* When using PIV cards, if the logon credentials are set to "Card" and "User Code", the reader will accept a card and PIV PIN only.
* When using PIV cards, duress logon and duress access are not supported.
* When using PIV cards, PIV PIN to PACS is not supported. When PIN entry is required, (e.g. the access mode is set to "Secure – PIN") you will need to insert your PIV card and enter your PIV PIN. Only the PIV PIN will be accepted.
* When using the Arm/Disarm/Mode soft keys and PIV cards, you will need to select the soft key prior to the card being inserted.
* When using two PIV cards for card entry, it is recommended that you increase the Door's **Second card (for two-card entry) must be swiped within** timeout to 10 seconds or greater; providing enough time to validate the first PIV card, then presentation or insertion of the second PIV card.
* When using PIV cards, the access decision is displayed when the card is removed from the reader. If a card is left in the reader longer than 40 seconds, the access decision will be cancelled.
* When using PIV cards, logon occurs when the card is removed from the reader, hence if the card is left in the reader accidentally, logon will occur when the card is removed.

***

### Minimum configuration requirements

The HBUS Contact Card Reader will display the message "Not Configured" unless the following configuration has been completed:

* On the **Connections** tab, assign the HBUS Contact Card Reader to a Controller 6000 or 7000, and enter the HBUS Contact Card Reader's HBUS serial number (10 character hexadecimal string).
* If using alarms management functionality, on the **Alarm Zones** tab, assign at least one Alarm Zone to the HBUS Contact Card Reader.

  **Note:** Alarms management functionality is not available when the HBUS Contact Card Reader is assigned as the Reader for an Elevator Car.
* If used for access control, assign the HBUS Contact Card Reader as the Reader for a Door or Elevator Car.

***

### Configuration

To configure an HBUS Contact Card 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 Contact Card 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-8490ef9fcd7783d5f01255b9fe4583beee7b14fb%2Fhbuscontactcardreader_1.png?alt=media)

   Information about the reader status, revision and supported card technologies display on this screen. For the T21 REV1 variant the status only updates when the reader goes offline.

   **Note:** The T21 REV1 variant does not support 125 card technologies.

   If the HBUS Contact Card 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-7175ec8ce3b09351d87b8bf374633b80b911e07a%2Fhbuscontactcardreader_2.png?alt=media)
2. Select the Controller 6000 or 7000 you want to assign this HBUS Contact Card Reader to, from the **Controller** drop-down list.

   **Notes:**

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

   **Note:** For the HBUS Contact Card Reader to report its current version of software, an Alarm Zone must be assigned to the **Event Response** tab of the HBUS Contact Card Reader’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-98e54a9f96c69203e4dc01259adbd68152e1aa10%2Fhbuscontactcardreader_3.png?alt=media)

   This screen enables you to display the status of a selected Alarm Zone and control the logon credentials and timeouts for this HBUS Contact Card Reader, when a Cardholder attempts to log on or perform a local override using the function keys on this HBUS Contact Card Reader.
2. Configure as required.

   <table><thead><tr><th width="186">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 HBUS Contact Card Reader, 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>When assigned as an entry reader, the <strong>Display Alarm Zone</strong> field is populated with the Alarm Zone assigned to the Door’s entry Access Zone. When assigned as an exit reader, the <strong>Display Alarm Zone</strong> field is populated with the Alarm Zone assigned to the Door’s exit Access Zone.</li><li>If not assigned as an entry or exit reader, the choice of Alarm Zone is restricted to only those associated with the HBUS Contact Card Reader on the <strong>Alarm Zones</strong> tab.</li><li>Deselect the <strong>Display Alarm Zone Status</strong> <strong>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 HBUS Contact Card Reader an indication of how long they have left until exit delay expires. These checkboxes will be disabled if a Display Alarm Zone has not been selected or if the HBUS Contact Card Reader has been assigned as a reader.</li></ul></td></tr><tr><td>Logon Credentials</td><td>Specify the first and second <strong>Logon Credentials</strong> required to log on to the HBUS Contact Card Reader. The default first logon credential required is "Card". The default second logon credential required is "PIN".<br><br><strong>Note:</strong> If you select "User Code" or "Card or User Code" as the <strong>First</strong> logon credential, then the <strong>Second</strong> credential field becomes disabled and displays "None".</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 HBUS Contact Card Reader. Default 20 seconds.<br><br><strong>Note:</strong> If the HBUS Contact Card Reader 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 HBUS Contact Card Reader 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 HBUS Contact Card Reader 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 HBUS Contact Card Reader.</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 HBUS Contact Card Reader, when one or more inputs in any of the Alarm Zones associated with the HBUS Contact Card Reader is shunted or isolated.<br><br><strong>Note:</strong> If the Input is not assigned to the HBUS Contact Card Reader, the banner will display without the ability for a user to address the issue directly from the HBUS Contact Card Reader.</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 HBUS Contact Card Reader.<br>Select the <strong>Lockout for 90 seconds after failed logon attempts</strong> checkbox. The HBUS Contact Card Reader 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 HBUS Contact Card Reader 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 HBUS Contact Card Readers installed. For sites installing new HBUS Contact Card Readers 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 HBUS Contact Card Reader 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. The PIV card will be locked after 5 consecutive failed PIN entries.</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-6a4e221ae5d2c933a626d46a6204b833e730452d%2Fhbuscontactcardreader_4.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 HBUS Contact Card Reader, and drag and drop them into the **Alarm Zones** grid.

   **Notes:**

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

     Assigning many Alarm Zones that are hosted by remote Controllers, may impact on the performance of the HBUS Contact Card Reader.
   * All inactive/acknowledged alarms and all inactive/processed alarms older than 28 days are not displayed on the HBUS Contact Card Reader.
   * Duress alarms are not displayed on the HBUS Contact Card Reader.
   * 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 HBUS Contact Card Reader cannot be assigned to an Elevator Car or Elevator Car HLI, if Alarm Zones have been assigned to the HBUS Contact Card Reader.
   * If a Short Name has been entered for an Alarm Zone, this will be displayed in the HBUS Contact Card Reader user interface, instead of the Name.
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 HBUS Contact Card Reader user interface.
4. Configure as required.

   <table><thead><tr><th width="186">Field</th><th>Description</th></tr></thead><tbody><tr><td>Use site default Alarms List settings</td><td>When checked, the HBUS Contact Card Reader 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 HBUS Contact Card Reader will display all alarms at or above ‘Very Low Priority’ for the Alarm Zone(s) assigned to the HBUS Contact Card Reader.<br><br><strong>Note:</strong> This functionality does not apply when disarming an Alarm Zone based on an access decision.<br>To configure the Alarm List settings specific for this HBUS Contact Card Reader, deselect the <strong>Use site default Alarm List settings</strong> checkbox. Configure the Alarm List settings for this HBUS Contact Card Reader 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 HBUS Contact Card Reader 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 HBUS Contact Card Reader, deselect the <strong>Use site default Arming settings</strong> checkbox. Enter the arming/disarming failed message to be displayed by this HBUS Contact Card Reader. 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-b73535baf813aae316e2a20dcde3a1f6aff4f293%2Fhbuscontactcardreader_5.png?alt=media)
2. From the **Hardware** List Window, select the Inputs you wish to have controlled by this HBUS Contact Card Reader.

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

   **Notes:**

   * Up to 100 Inputs can be monitored by one HBUS Contact Card Reader.
   * If a Short Name has been entered for an Input, this will be displayed in the HBUS Contact Card Reader 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-0779fd69f3491405ed9cd5c5a0fee87468731550%2Fhbuscontactcardreader_6.png?alt=media)

   This tab allows you to configure Fence Controllers so they can be monitored and controlled from this HBUS Contact Card Reader.
2. From the Hardware List Window, select the Fence Controllers you wish to associate with this HBUS Contact Card Reader, 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 HBUS Contact Card Reader.
   * Only F31, F32, F41, F42 and F22 Fence Controllers can be associated with this HBUS Contact Card Reader.
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 HBUS Contact Card Reader 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-a751f15dbb15ce7b3979e25cced36993e94c66f2%2Fhbuscontactcardreader_7.png?alt=media)

   This screen enables you to configure the 8 LEDs on either side of the HBUS Contact Card Reader 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 HBUS Contact Card Reader, select the **Display labels on Welcome Screen** checkbox. The name shown in the free text label field will be displayed on the HBUS Contact Card Reader beside the relevant LED, when the HBUS Contact Card Reader is idle.

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

   **Notes:**

   * Press the **\*** key on the HBUS Contact Card Reader 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-bf6b1cc5969f1835b75521ea0189aa77b8bbb684%2Fhbuscontactcardreader_8.png?alt=media)
2. From the **Hardware** List Window, select the Outputs you wish to trigger (On/Off) using this HBUS Contact Card Reader.

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

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

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

   If you require a non-authorised user, (i.e. HBUS Contact Card Reader 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 HBUS Contact Card Reader 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 HBUS Contact Card Reader.
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 HBUS Contact Card Reader user interface.

</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-6b04786a185fedb29f555f4a72de1f2955dd8a59%2Fhbuscontactcardreader_9.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><p>When checked the Cardholder’s user code will be required in place of a PIN for any access transactions at this HBUS Contact Card Reader and the <strong>User Code grants access when the zone is armed</strong> option activates.<br><br><strong>Notes:</strong></p><ul><li>For Access Mode and Arming local overrides, the HBUS Contact Card Reader uses the Log On Credentials configured on the <strong>Welcome Screen</strong> tab of the HBUS Contact Card Reader.</li><li>PIN is user code is not supported when using PIV cards for access.</li></ul></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 <strong>PIN is user code</strong> checkbox first.</td></tr><tr><td>Require MIFARE Enhanced Security encoded cards</td><td><p>When checked, the HBUS Contact Card 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 HBUS Contact Card 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 HBUS Contact Card 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 Contact Card 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 HBUS Contact Card 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 HBUS Contact Card Reader, 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.

   **Note:** 'Double card overrides' are not supported when using PIV cards.
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 and select the appropriate checkboxes.
5. 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.
6. Check the **Enforce MIFARE Plus X Card Proximity Checking** checkbox.

   The HBUS Contact Card Reader will perform proximity checks when reading a MIFARE Plus X card.

   **Notes:**

   * Checking this option disables all other card technologies.
   * The **Enforce 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.
   * For the HBUS Contact Card Reader to accept both contact and contactless PIV cards, check the **PIV Contactless** checkbox in the Permitted Card Technology section.
   * For the non Multi Tech variant, all 125 kHz cards will be denied.
7. The **Operate as cipher pad for Card + PIN** option allows sites to reduce the risk of cardholder PINs being discovered by someone looking over a cardholder’s shoulder while they enter their PIN at the reader.

   With this option enabled and the reader in PINs mode, each time a user badges their card a randomised number keypad will display on the reader screen. Users then need to follow the scrambled keys on the screen to enter their PIN correctly, (e.g. for the PIN 1234, the user would have to press 5170 on the keypad).

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

   If your site requires this functionality, tick the **Operate as cipher pad for Card + PIN** checkbox.

   **Notes:**

   * This feature can be disabled for visually impaired cardholders. See [Adding a card to a Cardholder](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/cardholders/adding-a-card-to-a-cardholder.md) for further detail.
   * Cipher pad functionality is not supported with the Car Park Management feature.

</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-7990d47e9f39c6cda65d56e9f7e6149c09fb44e2%2Fhbuscontactcardreader_11.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 HBUS Contact Card Reader 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 HBUS Contact Card Reader screen to always be on. This option is useful when using the Mimic Panel functionality.<br>You can display an Idle Image on the HBUS Contact Card Reader, (e.g. company logo). This image will display instead of the Welcome screen, (i.e. when logged off) and the HBUS Contact Card Reader 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 (configured 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 HBUS Contact Card Reader. 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 HBUS Contact Card Reader.</li></ul></li></ul></td></tr></tbody></table>

</details>

<details>

<summary>PIV Settings tab</summary>

This tab is only applicable if you are configuring a PIV Card Reader.

Refer to [Configuring a PIV Card Reader](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/piv-card-support/configuring-a-piv-card-reader.md) for details on configuring the PIV settings.

</details>

<details>

<summary>Mobile Access Settings tab</summary>

If required, this tab allows you to associate a relay Output with this HBUS Contact Card Reader, so that when a card is badged at the HBUS Contact Card Reader, the relay will be triggered.

1. Click the **Mobile Access Settings** tab.

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

   <table><thead><tr><th width="192">Field</th><th>Description</th></tr></thead><tbody><tr><td>Mobile Connect NFC</td><td>Select an option from the drop-down list. When ON, Android devices will use NFC to request access at the reader. NFC applies to Auto Connect only. If the user disables NFC it will not be able to get access with NFC. The default uses the <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/mobile-access-settings.md">Server Properties</a> settings, which is OFF by default.</td></tr><tr><td>Second factor always required for mobile</td><td>Select an option from the drop-down list. When ON, presentation of a second authentication factor is required at the reader at all times, unless the access mode is set to ‘Free-No PIN’. The default uses the <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/mobile-access-settings.md">Server Properties</a> settings, which is OFF by default. Second factor authentication is enforced for mobile credentials only.<br><br><strong>Note:</strong> If the access mode is set to ‘Free-No PIN’ and a personalised action has been assigned to the user, a second authentication factor will be required. Refer to <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/access-zones/configuring-personalised-actions-for-access-zones.md">Configuring Personalised Actions for Access Zones</a> for details on how personalised actions work.<br>NFC works over a short range, hence a user may take their device out of range to provide their second factor. When this happens, the App displays an icon encouraging the user to re-enter the field.</td></tr></tbody></table>

</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-184802c7ce5f080a29928d02ba8f248ac1253bc6%2Fhbuscontactcardreader_12.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 HBUS Contact Card Reader.

   **Note:** Badging a card at this HBUS Contact Card 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 HBUS Contact Card Reader at a time. Each HBUS Contact Card Reader will cause the relay to pulse.

</details>

8. Click the **Cameras** tab if you want to associate a DVR Camera(s) with this HBUS Contact Card 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 HBUS Contact Card 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 the **Custom Fields** tab if you want to add and assign a custom field value to this HBUS Contact Card 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 HBUS Contact Card 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 Contact Card 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-contact-card-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.
