> 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/integrated-systems/morpho-biometric-integration/creating-a-new-morpho-biometric-reader.md).

# Creating a new Morpho Biometric Reader

### Introduction

This procedure describes how to create a new Morpho Biometric Reader, and configure system-wide settings for it.

***

### Before you begin

Before you begin this procedure ensure that a Morpho Biometric Type has already been created. See [Creating a new Morpho Biometric Card Type](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/creating-a-new-morpho-biometric-card-type.md) for the procedure.

***

### Configuration

#### Configuring the Morpho Biometric Reader

1. In Command Centre Configuration Client, 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\...Morpho Biometric Reader**.

   By default the **General** tab displays.
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. 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).
5. 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).
6. Morpho Biometric Readers have tampers, which monitor whether the LCD screen has been removed/damaged, or the reader has been removed from the wall. By default, if either of these tampers are triggered, an alarm is raised, a buzzer sounds, and an LED flashes.

   If you want to prevent tamper alarms from being generated, click the **Status and Overrides** tab and change the **Tamper Setting** to "Disabled". Alternatively, you can change the **Tamper Setting** to "Send alarm" if you want an alarm to be raised but no buzzer activated.

   Other temporary security overrides can be performed from the **Status and Overrides** tab. See [Performing Overrides on a Morpho Biometric Reader](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/performing-overrides-on-a-morpho-biometric-reader.md) for further detail.
7. Click each tab in turn to configure the reader:

<details>

<summary>Setup tab</summary>

1. Click the **Setup** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-dfdbf9ed2eb33401a6dcbdc29b32f5ebf3a12ce0%2Fmorphobiometricreader_setuptab.png?alt=media)
2. Configure the settings in the **Reader Connection** section as appropriate.

   **Note:** The fields will be populated with any previously configured values for existing biometric readers.

   <table><thead><tr><th width="168">Field / Checkbox</th><th>Description</th></tr></thead><tbody><tr><td>IP Address</td><td><p>Enter the IP Address of this reader (as previously configured in <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/installing-morphoaccess-readers/configuring-a-biometric-reader.md">Configuring a Biometric Reader</a>).</p><p><strong>Note:</strong> DHCP is not supported for Morpho Readers' IP Addresses.</p><p>(Default = 192.168.1.10)</p></td></tr><tr><td>Encrypt TCP/IP Communications</td><td>This option is off (disabled) by default. If you want to use encrypted communications for this reader, refer to <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/communications-encryption.md">Communications Encryption</a> for further detail.</td></tr></tbody></table>
3. Configure the settings in the **Authentication Method** section as appropriate.

   <table><thead><tr><th width="168">Field / Checkbox</th><th>Description</th></tr></thead><tbody><tr><td>Authentication Method</td><td><p>This is a flag that determines whether or not the Cardholder has card-only access, or must present their finger, or enter a PIN, (or both) or use a QR Code. The reader has to authenticate a Cardholder using one of these methods. Options are:</p><ul><li><strong>Biometric</strong> (1-to-many Identification)</li><li><strong>QR Code</strong> (Verification with a QR Code)</li><li><strong>Card</strong> (1-to-1 Verification)</li></ul><p><strong>Notes:</strong></p><ul><li>If the Authentication Method is changed the database does not re-sync.</li><li>When <strong>Card</strong> mode is selected, and <strong>Require PIN to grant access</strong> (on the <strong>Advanced Settings</strong> tab) is enabled, if there is no PIN number set for the card, the cardholder will be denied access.</li></ul></td></tr></tbody></table>
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.

   **Note:** If you attempt to set a Biometric reader to follow the site default, but the site default does not allow either of the card technologies that the Morpho reader does (MIFARE Classic or DESFire), you get the error message *"The selected permitted card technology settings are not supported by the biometric reader"*.

   To resolve, you can either change the server settings to allow at least one of those two card technologies, or just not have the Morpho reader follow the site-wide settings.
5. If cards are encoded with Morpho data, the MIFARE data need to be sent down to the Morpho reader. To set the MIFARE Key, click the **Set MIFARE Key** button on each Morpho reader that will be used with the cards. When the **Set MIFARE Key** button is clicked the Reader MIFARE Key is updated.

   **IMPORTANT:** This needs to be done at least once if your site is planning to use cards with the reader.

</details>

<details>

<summary>Advanced Settings tab</summary>

1. Click the **Advanced Settings** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-270700ca2303e282d4ba90c7e4d83c909725cb64%2Fmorphobiometricreader_advancedsettingstab.png?alt=media)
2. Configure the **Communication** settings on this screen as appropriate.

   <table><thead><tr><th width="174">Field / Checkbox</th><th>Description</th></tr></thead><tbody><tr><td>Auto Synchronise</td><td><p>Enabling this checkbox means that this reader will be updated on a 'real-time basis', (i.e. as soon as a change is made in Command Centre).</p><p>If this checkbox is disabled an operator will still be able to update the reader manually using any of the manual options available, including using macros.</p><p>(Default = Checked)</p></td></tr><tr><td>Enable polling</td><td><p>If polling is enabled, the reader will be polled as soon as possible after the reader's Poll Time has elapsed since the last connectivity poll, biometric update, database resync, reader configuration or refresh status request has occurred.</p><p>(Poll Time range = 10 - 300 seconds)</p><p><strong>Notes:</strong></p><ul><li>A high polling frequency, (i.e. a low Polling Interval value), might not be achievable on sites that have a lot of readers. For more information, please contact Gallagher Technical Support.</li><li>Higher polling rates mean a longer delay before offline alarms occur.</li></ul></td></tr><tr><td>Double card overrides</td><td><p>If you want to configure double card overrides for this reader, click either the <strong>Override access zone</strong> or the <strong>Arm alarm zone</strong> radio button, depending on whether you want the double card override to override the state of the Access Zone or arm the Alarm Zone associated with the Access Zone.</p><p>Leave the <strong>Disabled</strong> radio button checked if double card overrides are not required.</p></td></tr></tbody></table>
3. Configure the **Authentication** settings as appropriate.

   <table><thead><tr><th width="174">Field / Checkbox</th><th>Description</th></tr></thead><tbody><tr><td>False Acceptance Rate (FAR)</td><td><p>This value determines the required closeness of a match when comparing two templates for the purpose of verifying captured biometric templates. The False Acceptance Rate (FAR) setting of the reader impacts on the False Rejection Rate (FRR) at that reader, (e.g. the lower the FAR setting, the higher the FRR).</p><p><strong>Note:</strong> Selecting a low FAR setting is more secure because there is less chance that the reader will positively authenticate a person that it shouldn’t, but there is also a greater chance that the reader could fail to positively authenticate a person when it should, (i.e. a higher FRR).</p><p>(Default = &#x3C; 0.01% Recommended value)</p></td></tr><tr><td>Require PIN to grant access</td><td><p>This setting only applies to biometric readers that have pin entry keypads. Enabling it will override the 'Reader ignores PIN' setting on the card layout. The reader will always request a PIN from the cardholder.</p><p><strong>Note:</strong> When <strong>Require PIN to grant access</strong> is enabled, <strong>Biometrics</strong> and <strong>QR Code</strong> authentication methods (on the <strong>Setup</strong> tab) cannot be applied.</p></td></tr></tbody></table>
4. Configure the **Reader Screen** settings as appropriate.

   <table><thead><tr><th width="174">Checkbox</th><th>Description</th></tr></thead><tbody><tr><td>Display Date and Time</td><td>Enabling this checkbox means that Morpho Reader models with screens, and in Native Mode (MA5G), will display the date and time.</td></tr><tr><td>Display Cardholder Name after access is granted</td><td><p>Enabling this checkbox means the reader will display the cardholders name ("Surname, firstname" and limited to 38-characters) in the welcome message when a biometric is recognised.</p><p>If cardholders have a <strong>Short Name</strong> (limited to 16 characters) that will be displayed when they enter. However, if they do not have a <strong>Short Name</strong>, their "Surname,firstname" will display.</p><p><strong>Note:</strong> This is not supported with OSDP.</p></td></tr></tbody></table>
5. Do you want access and status messages to be displayed on this reader's screen?

   <table><thead><tr><th width="76">If...</th><th>then if the Server Properties are configured to...</th></tr></thead><tbody><tr><td>no,</td><td>NOT show reader messages, leave the <strong>Use site default settings</strong> checkbox checked; OR<br>if the Server Properties ARE configured to display reader messages, deselect the <strong>Use site default settings</strong> checkbox and ensure the <strong>Show reader display messages</strong> checkbox is unchecked.</td></tr><tr><td>yes,</td><td>show reader messages, leave the <strong>Use site default settings</strong> checkbox checked; OR<br>if the Server Properties are configured to NOT display reader messages, deselect the <strong>Use site default settings</strong> checkbox and select the S<strong>how reader display messages</strong> checkbox.</td></tr></tbody></table>

</details>

<details>

<summary>VisionPass tab</summary>

1. Click the **VisionPass** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-be92d49dbb0b82e958de1310d8975680158261c6%2Fmorphobiometricreader_visionpasstab.png?alt=media)
2. Configure the **VisionPass** settings on this screen if this reader is a VisionPass reader.

   **Note:** The fields will be populated with any previously configured values for existing biometric readers.

   <table><thead><tr><th width="174">Field / Checkbox</th><th>Description</th></tr></thead><tbody><tr><td>User Guidance</td><td>If you want to configure user guidance for this reader, click either <strong>Icons</strong> or the <strong>Camera</strong> radio button as appropriate.<br>If <strong>Icons</strong> is selected, an icon will appear on the reader and if need be, arrows to show you where to move to be captured.<br><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-0a13ac87ddfc0635e747356448c1a7ff722c133b%2Fvisionpass_iconguidance.png?alt=media" alt=""><br>If <strong>Camera</strong> is selected, the camera will briefly show footage of you on the reader. If there is no person there it will stay up for a little longer before timing out and denying access.</td></tr><tr><td>Fake Face Detection Level</td><td><p>Click the appropriate radio button for a default acceptable fake face detection level.</p><p><strong>Low:</strong> detects and manages basic fake face attacks such as pictures presented on paper or smartphone.</p><p><strong>Medium:</strong> enhances security controls while providing good user experience.</p><p><strong>High:</strong> certified by iBeta as PAD Level 2 with an IAPMR at 0%.</p><p><strong>Notes:</strong></p><ul><li>Default = High. Recommended option is either Medium or Low if <strong>Cardholders must wear a face mask to gain access</strong> is enabled.</li><li><p>For <strong>High FFD</strong> setting these guidelines must be met:</p><ul><li>Enrolment of user on VisionPass</li><li>Biometric only (no template on card)</li><li>Standard lighting, not recommended outdoor (100 &#x3C; lux &#x3C; 5000)</li><li>No face mask</li><li>No eyewear</li></ul></li></ul></td></tr><tr><td>Camera enabled per user request</td><td><p>Checking (enabling) this setting will make a "man walking" <img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f9e85cc2435c3d47450ec78fd410bafaa767da42%2Fvisionpass_manwalkingicon.png?alt=media" alt=""> icon appear at the bottom left corner of the VisionPass reader.</p><p>This icon must be pressed for the reader to check your face.</p><p>This setting is unchecked by default. If you leave it unchecked then it operates by motion detection. Any movement at the camera will trigger it to try to capture a face.</p></td></tr><tr><td>Cardholders must wear a face mask to gain access</td><td><p>When checked (enabled) it will be mandatory for cardholders to wear a face mask otherwise access will be denied.</p><p>(Default = Unchecked)</p><p><strong>Notes:</strong></p><ul><li>If this checkbox is ticked cardholders are likely to get higher chances of access denied compared to a face mask not being enforced, especially when the <strong>Fake Face Detection Level</strong> (FFDL) is set to high. Therefore, we recommend the FFDL is set to either Medium or Low when wearing face masks is enforced.</li><li>This does not apply to VisionPass SP readers.</li></ul></td></tr></tbody></table>

</details>

<details>

<summary>Legacy tab</summary>

1. Click the **Legacy** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-376b4b02f002e028b1ce85515e4b3b318e526315%2Fmorphobiometricreader_legacytab.png?alt=media)
2. When checked, the **Fingerprint Mode** checkbox allows a Fingervein or MorphoWave reader to operate on Fingerprints only (for use during biometric enrolment transition from Fingerprint to Fingerprint +Vein).

   This setting is checked by default. Uncheck it if you do not require this functionality.
3. The **Connection Mode** field specifies the mode of communication that was originally specified for Legacy Readers. This field shows the current configuration but is 'read-only' as Legacy Readers are no longer supported.

</details>

8. Click the **Cameras** tab if you want to associate a DVR Camera(s) with this Morpho Biometric 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 Morpho Biometric 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 Morpho Biometric 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 Morpho Biometric 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 Morpho Biometric Reader

Once the configuration work is complete, you need to assign the Morpho Biometric Reader to a Gallagher Controller and other appropriate devices, (i.e. Door, HBUS Wiegand Door Module, Terminal, Elevator Car and/or HLI Elevator Car).

13. Assign this reader to a Controller. See [Configuring the Controller RS-485 Bus for OSDP](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/morpho-osdp-configuration/configuring-the-controller-rs-485-bus-for-osdp.md) for further detail.
14. From either the **Hardware** or **Door** List Window, highlight the device you want to assign this reader to.
15. **Right click** and select **Properties**.
16. What type of device are you assigning the biometric reader to?

    <table><thead><tr><th width="571">If...</th><th>then click the...</th></tr></thead><tbody><tr><td>HBUS Wiegand Door Module,</td><td><strong>Readers</strong> tab.</td></tr><tr><td>Door,</td><td><strong>Entry Zone</strong> tab.</td></tr><tr><td>Terminal, Elevator Car or HLI Elevator Car,</td><td><strong>Connections</strong> tab.</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-d5e308ad9823500c102e6b1215b87b98b26f873c%2Fdoor_entryzonetab.png?alt=media)
17. Select the appropriate Morpho Biometric Reader(s) from the relevant Reader drop-down list, as follows:

    <table><thead><tr><th width="445">Gallagher...</th><th>can host a maximum of...</th></tr></thead><tbody><tr><td>Controller 6000, Controller 7000</td><td><p>32 x Morpho readers for OSDP (16 per RS-485) Controller 7000;</p><p>16 x Morpho readers for OSDP (16 per RS-485) Controller 6000;</p><p>4 x Morpho readers for 8R;</p><p>2 x Morpho readers for 4R.</p></td></tr><tr><td>Controller 7000 Single Door</td><td>8 x Morpho reader.</td></tr><tr><td>Controller 7000 Single Door (Wiegand)</td><td>1 x Morpho reader.</td></tr><tr><td>HBUS Wiegand Door Module</td><td>2 x Morpho readers.</td></tr></tbody></table>
18. 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 Morpho Biometric Reader has been configured and is ready for use.

**Note:** A Morpho Biometric Reader can be synchronised using macros.

***

### Editing and Deleting Morpho Biometric Readers

Refer to [Editing items](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/editing-items.md) and [Deleting items](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/deleting-items.md) for procedures on how to edit and delete Morpho Biometric Readers.

**Notes:**

* You cannot delete a Morpho Biometric Reader if it appears on a Site Plan.
* It is recommended that encrypted communications be disabled on a Morpho Biometric Reader before it is deleted.


---

# 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/integrated-systems/morpho-biometric-integration/creating-a-new-morpho-biometric-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.
