> 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/products/integrations/third-party-readers/idemia-morpho/reference/idemia-readers-idemia-enrollment-readers.md). # IDEMIA enrollment readers Identify IDEMIA enrollment devices, template types, licensing needs, and product lifecycle status. Enrolment readers capture templates at Command Centre workstations. There are several, because different readers use different styles of biometric. * **MSO300 / MSO FVP / MSO330 / MSO1300** are required at workstations that capture fingerprint and finger-vein templates to cardholders, for SIGMA and VP Dual Finger Vein readers. * **MorphoWave Compact XP / SP** is required at workstations that capture multi-finger templates (4 fingers), for Wave XP and SP readers. * **VisionPass** is required at workstations that capture face templates. **No Verif licence** or dongle is required for face capture. Enrolling workstations must have a **Verif licence dongle or software** connected, except for VisionPass and VisionPass SP. Enrolment part numbers and more information are on the [Gallagher IDEMIA Biometric Integration product page](https://products.security.gallagher.com/security/us/en_US/products/integrations/idemia-biometric-integration/p/INT163). Part numbers, firmware and driver versions for each enrolment reader are on [IDEMIA reader compatibility and specifications](/knowledge-hub/products/integrations/third-party-readers/idemia-morpho/reference/idemia-readers-supported-morpho-readers.md), which also shows which reader captures which template. ### Enrollment reader comparison | | Model Range | Model Range | Model Range | Model Range | Model Range | Model Range | Model Range | Model Range | | | ------------------------ | ------------------------- | ------------------------- | ----------------- | ----------- | ------------------------- | ----------------------------- | ----------------------------- | ----------- | ------------- | | Features & Compatibility | MSO 300 Enrollment Reader | MSO FVP Enrollment Reader | Wave Compact / XP | Wave SP | MSO 330 Enrollment Reader | MSO 1300 Enrollment Reader v3 | MSO 1300 Enrollment Reader v4 | VisionPass | VisionPass SP | | Finger | Y | Y | | | Y | Y | Y | | | | Wave Template | | | Y | Y | | | | | | | Finger Vein | | Y | | | | | | | | | Face Template | | | | | | | | Y | Y | | Bio Read Rate | 1.0s | 1.0s | 1.0s | 1.0s | 1.0s | 1.0s | 1.0s | 1.0s | 1.0s | | Order Status | EOL March 2022 | EOL June 2021 | Current | Current | Current | EOL January 2024 | Current | Current | Current | | Supported CC Version | vEL7.30 | vEL7.30 | vEL8.10 | vEL8.80 | vEL8.90 | vEL8.50 | vEL8.50 | vEL8.90 | vEL9.30 | | Supported Driver | 3.59.1.0 | 3.59.1.0 | n/a | n/a | 4.6.0.0 | 3.59.1.0 | 4.8.4 | n/a | n/a | | Verif License required | Y | Y | Y | Y | Y | Y | Y | | | Order status: MSO300 reached end of life March 2022, MSO FVP June 2021, and MSO1300 v3 January 2024. The rest are current. {% hint style="info" %} Wave reader minimum requirements are one hand and one finger. {% endhint %} {% hint style="warning" %} This table gives the **MSO 1300 v3** as supported from **vEL8.50**. The enrolment table on [IDEMIA reader compatibility and specifications](/knowledge-hub/products/integrations/third-party-readers/idemia-morpho/reference/idemia-readers-supported-morpho-readers.md) gives the **MSO1300 E3** from **vEL8.20**. Both values are shown until this is confirmed. {% endhint %} ### VisionPass and VisionPass SP templates (vEL9.30 and later) If your site uses both VisionPass and VisionPass SP access readers, you **must enrol with VisionPass**. If the site uses only VisionPass SP readers, a VisionPass SP enrolment reader is enough. SP-enrolled face templates are **not compatible** with VisionPass readers. {% hint style="info" %} The VisionPass reader needs firmware **2.14.4** to enrol face templates from 9.30 or later. This supports VisionPass SP template enrolment. {% endhint %} ### Unused fingers When you enrol in the Command Centre Client, you can select **Unused** and then select the fingers you are not using. The settings for this are in the **Morpho Biometric Type** card type settings. ### Enrolment errors These errors can appear when you capture finger biometrics: | Error | Meaning | | ---------------------------------------------------- | --------------------------------------------------------- | | `No biometric capture devices were found.` | Your MSO enrolment device is not found. | | `Unable to capture biometrics. Error: 15` | Your VERIF dongle or VERIF Software licence is not found. | | `Enrolment terminated` (enrolling with a MorphoWave) | Your VERIF dongle or VERIF Software licence is not found. | Check that your MSO enrolment device and VERIF dongle show in **Multiprotect License Manager**. If they have the wrong driver or Multiprotect License Manager version, they do not show. Check that the version is supported. {% hint style="info" %} Use the latest **Multiprotect License Manager v6.3.0** and **Driver v4.8.4**. The **MSO1300 v4 requires this driver** to work. {% endhint %} --- # 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/products/integrations/third-party-readers/idemia-morpho/reference/idemia-readers-idemia-enrollment-readers.md?ask=&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.