> 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/creating-readers.md).

# Creating Readers

### Introduction

There are a number of different readers that can be configured in Command Centre, as follows:

* Cardax IV Readers
* Third Party Readers
* HBUS Readers
* HBUS Terminals

  Refer to [Configuring an HBUS Terminal](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/configuring-hbus-terminals/configuring-an-hbus-terminal.md) for the procedure.
* HBUS Contact Card Readers

  Refer to [Configuring an HBUS Contact Card Reader](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/configuring-an-hbus-contact-card-reader.md) for the procedure.
* Morpho Biometric Readers

  **Note:** Your license file will determine whether or not you can configure biometric readers for your site. Refer to [Creating a new Morpho Biometric Reader](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/creating-a-new-morpho-biometric-reader.md) for the procedure.
* OSDP Readers

  **Note:** The Open Supervised Device Protocol (OSDP) Integration is covered in the Integrated Systems section. Refer to [Configuring an OSDP Reader](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/open-supervised-device-protocol-osdp-integration/configuring-an-osdp-reader.md) for the procedure.

This procedure describes how to configure a reader in Command Centre.

***

### Configuration

To configure a 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\...**, and then the appropriate reader type.

   By default the **General** tab displays.

   **Note:** You may need to select the device type from the sub-menu before selecting the reader type, (e.g. HBUS Devices or OSDP Devices).
3. 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).
4. Are you configuring a Third Party Reader?

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

   If **no**, go to Step 5.
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>Connections tab</summary>

1. Click the **Connections** tab.

   **Note:** The screen example shown is that of the Cardax IV Reader. This tab will look slightly different for other reader types.

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

   The fields that appear depend on the type of reader, as follows:

   <table><thead><tr><th width="156">If a...</th><th>then there will be a...</th></tr></thead><tbody><tr><td>Cardax IV or Third Party Reader,</td><td><strong>Reader interface</strong> and <strong>Reader number</strong> field, which will be populated once you assign this reader to a device, which is explained later in this procedure.</td></tr><tr><td>HBUS Reader,</td><td><p><strong>Controller</strong> and <strong>HBUS Serial Number</strong> field.</p><ol><li>Select the Controller 6000 or 7000 you want to assign this reader or terminal to, from the <strong>Controller</strong> drop-down list.<br><br><strong>Note:</strong> HBUS readers and terminals can be created via the <strong>HBUS Devices</strong> tab of a Controller 6000 or 7000. In which case the <strong>Controller</strong> field would be pre-populated with that Controller name.</li><li>Enter a 10 character hexadecimal string in the <strong>HBUS Serial Number</strong> field.<br><br><strong>Note:</strong> The HBUS serial number is optional, however the reader or terminal will be considered as not properly configured unless one is entered.</li><li>If you click the <strong>Apply</strong> button, software version numbers display.<br>The <strong>Configured Version</strong> is the version of the device software in the configured Controller FTS file, (i.e. <strong>not</strong> the version of the Controller software).<br>The <strong>Current Version</strong> is the version of software as last reported by the reader or terminal itself.</li></ol></td></tr></tbody></table>

</details>

<details>

<summary>Advanced tab</summary>

1. Click the **Advanced** tab.

   **Note:** The screen example shown is that of the Cardax IV Reader. This tab will look slightly different for other reader types.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-0ed1f67518a1871c0a11431eb22f4b10f85828a1%2Fcardaxivadvanced.png?alt=media)
2. Is there a **PIN is user code** option for this reader?

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

   If **no**, go to Step 5.
3. Terminals can be configured as keypads for readers that have no keypad. As part of this functionality, you can configure a user code to be used for gaining access in place of a PIN, for added security.

   If you want to use this functionality, check the **PIN is user code** check box.
4. With **PIN is user code** checked, the user code will be required in place of a PIN for any transactions at the reader which would normally require a PIN. This includes door access, overrides and Terminal logon.

   **Note:** For Access Mode and Arming local overrides, the HBUS Terminal and HBUS Contact Card Reader uses the Log On Credentials configured on the **Welcome Screen** tab. In this instance the PIN is usercode functionality is not applicable.
5. What type of reader are you creating?

   <table><thead><tr><th width="156">If...</th><th>then...</th></tr></thead><tbody><tr><td>Third Party Reader,</td><td>go to Step 6.</td></tr><tr><td>Cardax IV or HBUS Reader,</td><td>the following two check boxes are also available.<br><br><strong>Note:</strong> These features cannot be used at the same time, therefore when one of these check boxes is selected, the other check box is disabled.<br>Require MIFARE Enhanced Security encoded cards<br>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.<br><strong>IMPORTANT:</strong><br>When this check box is unchecked, the reader will be instructed not to send the enhanced security data to the Controller, even if present.<br>Leave this check box unchecked in the following situations:<br>1. When not using the MIFARE Enhanced Security feature or when not using it for part of a site.<br>2. 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.<br>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.<br>In the event of this being enabled, all types of cards, (i.e. high or low security), will be denied with an event saying <em>"Denied - MIFARE High Security Card Required at [Door]”</em>. To enable both types of card to be used uncheck the check box for the Door Reader.<br>Use MIFARE Serial Number as Card Data<br>HBUS Readers and Cardax IV 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>For this feature to work for Cardax IV Readers connected to Universal Reader Interfaces (URI), on the URIs <strong>Readers</strong> tab 'Universal' must be selected from the <strong>Format</strong> drop-down list.<br><strong>IMPORTANT:</strong><br>If using the Card Serial Number (CSN) functionality with Cardax IV MIFARE cards, the CSN may be transmitted where an incorrect card read of the Gallagher data occurs.<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>
6. If you want to configure **Double card overrides** for this 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.
7. Is there a **Permitted Card Technology** section for this reader?

   **Note:** The Permitted Card Technology options are only applicable to Gallagher T series readers.

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

   If **no**, go to the next tab.
8. 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** check box and select the appropriate checkboxes.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-ed2fc64eb7783f30ad1f6980560060f2f700e727%2Fcardtechnologies.png?alt=media)
9. 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.
10. 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.
    * For a MIFARE only reader, all 125 kHz cards will be denied.
    * For Cardax IV connected Gallagher T series readers, any changes to the Permitted Card Technology options will take approximately 40 seconds for the new setting to be sent to the reader.

</details>

<details>

<summary>Type tab</summary>

Configuration on this tab is only required if you are configuring a Third Party Reader supporting a keypad or needing the special card format.

1. Click the **Type** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-93eb624918abbb2ac9878778c04e340dfd4e00ff%2Fthirdpartyreader_typetab.png?alt=media)
2. Select the appropriate **Format** from the drop-down list.
3. Did you select 'Salto' as the Format?

   If **yes**, no **Key Map** is necessary. Go to the next tab.

   If **no**, go to Step 4.

   **Note:** The current Wiegand Format supported will display on the **Status and Overrides** tab of the Salto Server properties.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-6adabaa30cfd9939e94d07b645f52f52922d98dd%2Fsaltostatus%26overridestab_wiegandformat.png?alt=media)
4. Select the appropriate key press mapping option from the **Key map** drop-down list for the type of reader as follows:

   <table><thead><tr><th width="264">For a...</th><th>select...</th></tr></thead><tbody><tr><td>HID iClass Reader</td><td>Unbuffered 4-bit burst (e.g. HID iClass RK40/RWK400 Reader).</td></tr><tr><td>MR20 Reader</td><td>Unbuffered 8-bit burst (e.g. MR20 Magnetic Card Reader).</td></tr><tr><td>BQT COTAG Format</td><td>Unbuffered 8-bit burts (BQT COTAG)</td></tr><tr><td>OSDP Reader</td><td>Open Supervised Device Protocol (OSDP)</td></tr></tbody></table>

   **Note:** When a key press mapping option is selected, 12 binary data boxes appear relevant to the selection, allowing you to select a known key press mapping or configure a custom mapping.

</details>

<details>

<summary>Audio Visual tab <em>(HBUS Readers only)</em></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-5aad3d931ccb67e5b1d999ad092359f8511f822c%2Fhbusreaderaudiovisual.png?alt=media)
2. Configure the settings as required.

   <table><thead><tr><th width="94">Field</th><th>Description</th></tr></thead><tbody><tr><td>Volume</td><td>This can be set to Off or Normal.<br>(Default = Normal)</td></tr><tr><td>LED</td><td>This can be set to either Off or On.<br>(Default = On)</td></tr></tbody></table>

</details>

<details>

<summary>Mobile Access Settings tab <em>(HBUS Readers only)</em></summary>

This tab allows you to configure an HBUS Multi-Tech reader for Bluetooth® connectivity.

Refer to [Configuring a reader for Bluetooth® connectivity](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>

Configuration on this tab is only required if you want to associate a relay output with this reader, so that when a card is badged at the reader, the relay will be triggered.

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-5eb09df8dafcad585d7dae55ce63f80ef8403063%2Fcdxivoutput.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 the 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 see [Cameras tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/cameras-tab.md).
9. Click the **Icons** tab if you want to change the Icon Set for this 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 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.

#### Assigning the Reader

Once configured, you need to assign the reader to the appropriate devices, (i.e. Gallagher Controller, Door, Elevator Car and/or HLI Elevator Car).

13. From the appropriate List Window, highlight the device you want to assign the reader to.

    **Note:** HBUS Readers, HBUS Terminals, HBUS Contact Card Readers, Cardax IV, and Third Party Readers can be connected directly to a Controller or to reader interface.
14. **Right click** and select **Properties**.
15. What type of device are you assigning the reader to?

    <table><thead><tr><th width="288">If...</th><th>then click the...</th></tr></thead><tbody><tr><td>Controller</td><td><strong>HBUS Devices</strong> tab or <strong>Readers</strong> tab.</td></tr><tr><td>Door</td><td><strong>Entry Zone</strong> tab or <strong>Exit Zone</strong> tab.</td></tr><tr><td>Elevator Car or HLI Elevator Car</td><td><strong>Connections</strong> tab.<br></td></tr></tbody></table>

    The window displayed will vary depending on the device you selected. The example shown below is for a Door.

    ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-9de0c300be82b8157a73fdec32d15472af428b62%2Fentryzone.png?alt=media)
16. Assign the reader to the appropriate reader address by selecting it from the relevant **Reader** drop-down list.
17. 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

A reader has been configured, assigned to a device, 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/creating-readers.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.
