> 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/configure/set-up-an-idemia-visionpass-reader.md).

# Set up an IDEMIA VisionPass reader

Set up an IDEMIA VisionPass face-recognition reader for access at a door or for enrolment.

VisionPass integration allows effortless, contactless biometric enrolment, with template management in Command Centre. It gives secure, contactless facial-recognition access through doors, which can be protected with **TLS 1.2** encryption.

**Compatibility:** Command Centre **v8.90+**. Command Centre **v9.00+** added support for **OSDP** with IDEMIA biometric readers.

**Features:**

* An OSDP connection, from v9.00.
* TLS 1.2 encryption.
* No USB drivers need to be installed.
* **QR code** support. This needs version **9.10**: make sure the VisionPass reader firmware is **2.8.9 onwards** and the controller firmware is updated to **9.10.xxxxxxx** or later.
* It can be used as an **enrolment device**.

{% hint style="info" %}
You can select only one option: the VisionPass is used **either** solely for enrolment **or** for access at the door. VisionPass does **not** need a verification licence or dongle for enrolment.
{% endhint %}

### The two VisionPass readers

| Reader                                                                                                                                                                      | Card technology                                                                                                                                                                                                                     | Features                                                                                                                                          |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| <p><strong>IDEMIA VisionPass MD</strong><br><br>Unit Part No:<br>C864203<br>293744571<br><br><strong>Note:</strong> Available for the rest of the region.</p>               | <p>Supported:<br><br>Mifare Desfire EV1, EV2, EV3 (Frequency 13.56MHZ)<br><br>Classic<br><br>Not Supported:<br><br>iClass legacy, SR, SE, SEOS (Frequency 13.56 MHz)<br><br>HID Prox (Frequency 125KHz<br><br>HID Mobile Access</p> | <p>Supported:<br><br>Facial<br><br>PIN<br><br>Card<br><br>QR Code<br><br>LCD Screen<br><br>Default User DB: 20k<br><br>Expansion User DB: 40K</p> |
| <p><strong>IDEMIA VisionPass MDPI</strong><br><br>Unit Part No:<br>C864204<br>293744604<br><br><strong>Note:</strong> Only available in the <strong>US region</strong>.</p> | <p>Supported:<br><br>Mifare Desfire EV1, EV2, EV3 (Frequency 13.56MHZ)<br><br>Classic<br><br>iClass legacy, SR, SE, SEOS (Frequency 13.56 MHz)<br><br>HID Prox (Frequency 125KHz<br><br>Not Supported:<br><br>HID Mobile Access</p> | <p>Supported:<br><br>Facial<br><br>PIN<br><br>Card<br><br>QR Code<br><br>LCD Screen<br><br>Default User DB: 20k<br><br>Expansion User DB: 40K</p> |

For the supported firmware versions, see [IDEMIA reader compatibility and specifications](https://help.security.gallagher.com/knowledge-hub/products/integrations/third-party-readers/idemia-morpho/reference/idemia-readers-supported-morpho-readers.md).

### Hardware and wiring

Configuring the VisionPass reader needs supported hardware.

| **Hardware**                               | **Wiring**                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
| ------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| HBUS Wiegand Door Module                   | <p>Wiegand OUT 0 - Green R1 DATA 0<br><br>Wiegand OUT 1 - White R1 DATA 1<br><br>Wiegand LED 1 - Blue R1 OUT 1<br><br>Wiegand LED 2 - Blue/Red R1 OUT 2<br><br>Wiegand Ground - Red/Black GND -</p>                                                                                                                                                                                                                                                                                                                        |
| GBUS Wiegand URI                           | <p>Wiegand OUT 0 - Green R1 DATA 0<br><br>Wiegand OUT 1 - White R1 DATA 1<br><br>Wiegand LED 1 - Blue R1 OUT 1<br><br>Wiegand LED 2 - Blue/Red R1 OUT 2<br><br>Wiegand Ground - Red/Black GND -</p>                                                                                                                                                                                                                                                                                                                        |
| Module 4R / 8R                             | <p>Wiegand OUT 0 - Green R1 In<br><br>Wiegand OUT 1 - White R2 In<br><br>Wiegand LED 1 - Blue R2 OUT<br><br>Wiegand LED 2 - Blue/Red R1 OUT<br><br>Wiegand Ground - Red/Black GND -<br><br><strong>ATTENTION</strong>: The "v" for the VisionPass Reader module must be powered and wired from the same physical power source as the controller 6000</p>                                                                                                                                                                   |
| Controller 7000 Single Door Wiegand Module | <p>Wiegand OUT 0 - Green D0 Wiegand Data Input 0<br><br>Wiegand OUT 1 - White D1 Wiegand Data Input 1<br><br>Wiegand LED 1 - Blue LD Wiegand LED<br><br>Wiegand LED 2 - Blue/Red BZ Wiegand Buzz<br><br>Wiegand Ground - Red/Black - Common GND<br><br><strong>ATTENTION:</strong> VisionPass reader draw significantly more current than Gallagher readers. It is strongly advised to connect the biometric reader directly to the system’s power supply instead of linking it through a Gallagher Controller or URI.</p> |
| OSDP connection                            | <p>RS485\_TX\_Z Green/Black Controller RS485 Port - A<br><br>RS485\_TX\_Y Green/White Controller RS485 Port - B<br><br>RS485\_GND Black/RED -<br><br><strong>Note:</strong> TX and RX are short forms for Transmit and Receive</p>                                                                                                                                                                                                                                                                                         |

### Set up access at a door

#### Prerequisites

1. Command Centre **8.90+** installed.
2. Licence requirement: **Sagem Fingerprint Readers**.
3. 1 x Controller 6000 with an 8R module. (This varies with the hardware you use, such as a Controller 7000 or an HBUS Wiegand Door Module: see [Hardware and wiring](#hardware-and-wiring).)
4. 1 x Access Zone.
5. 1 x Morpho Biometric Reader. How it is assigned to the controller depends on the connection: **OSDP** (Command Centre 9.00+), **HBUS Wiegand**, or **Wiegand**.
6. 1 x Door.
7. 1 x Access Group.
8. Create a **Morpho Biometric Type** under Card Type: assign a Facility Code under **Card Encoding**, generate the **MIFARE Classic A Key**, and generate the **DESFire Key**.

   ![Morpho Biometric Type 1 Properties, Card Encoding: Region Code A, Facility Code 49999, fingerprint and finger vein starting sectors, and the MIFARE Classic A Key and DESFire Key fields (masked) with Generate key](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-570ce53b5a26c7af32a144c25d6f3aa9f1fcf170%2FSECHUB-TS-VISIONPASS-01-morpho-biometric-type-card-encoding.png?alt=media)
9. Create a card type with a card number between **31** and **8388607**, and add the object **Morpho VisionPass DESFire**.

   ![Card editor: a card design with the Morpho VisionPass DESFire object](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-6007c5439e10ab292fe2619cd3ca0719487b908a%2FSECHUB-TS-VISIONPASS-02-card-type-visionpass-object.png?alt=media)

#### Assign an IP address to the reader

To bring the reader online, install **MorphoBioToolBox (MTBT)** and give the reader an IP address in your network's range.

1. Open MTBT.
2. Terminal type: **Sigma, MorphoWave, VisionPass**.
3. Use the default IP **192.168.1.10** to connect to the VisionPass reader through MTBT. Once testing is complete, reset the reader's IP address to the default **192.168.1.10**, so the person allocated can connect and change it to their own network range.
4. Default port: **11010**.

   ![MTBT Connection tab: Terminal Type Sigma, MorphoWave, VisionPass; TCP/IP, IPv4, the address (covered) and port 11010](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-5c8c967bc1ab8d040159d5301aa7dfed9d13c942%2FSECHUB-TS-VISIONPASS-03-mtbt-connection.png?alt=media)
5. On the **Communication Configuration** tab, enter the IP, network mask, gateway and preferred DNS. Use an address from your own allocated range, not the one in the screenshot.
6. Click **Write** to save the configuration.

   ![MTBT Communication Configuration, IP Address Settings: Ethernet, IPv4, Static, the IP address and gateway (covered), network mask 255.255.255.0, host name VisionPass, DNS 8.8.8.8 and 8.8.4.4](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-45e6d9a44ae0e570d17e155e10afec3085d31c81%2FSECHUB-TS-VISIONPASS-04-mtbt-ip-settings.png?alt=media)

#### Set up for OSDP

1. Check the **serial speed**: set it to **115200** for best performance.

   ![MTBT Communication Configuration: IP address and gateway (covered), and Serial Settings with Baud Rate 115200, 8 data bits, 1 stop bit, no parity](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-b4846b1add1f4024a6e18d94a1981b4a3163bec2%2FSECHUB-TS-VISIONPASS-05-mtbt-serial-settings-115200.png?alt=media)
2. In Command Centre, on the controller the device is connected to, set the **RS485 Bus** to **OSDP** on the **Setup** tab, and apply.

   ![Controller 7000 Properties, Setup: RS-485 Bus 1 set to OSDP, RS-485 Bus 2 HBUS](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-340358fff3de6a08ddeee0019722b1f5db19e4ba%2FSECHUB-TS-VISIONPASS-06-controller-rs485-bus-osdp.png?alt=media)
3. Wire the device to the RS485 bus.

From **v9.10**, Command Centre should assign the OSDP device an address automatically when you add the reader to the OSDP reader window. If it does not, remove the reader and add it again. In **9.00 and below** you may need to set the device address.

**If the OSDP reader does not come online on the OSDP Devices tab,** set the device address in MBTB:

1. Search on **osdp** in the search key.
2. Change `OSDP.device_serial_address` to the address you want.
3. Click the tick.
4. **Write** the device configuration.

   ![MBTB Manage Configuration Keys: search key osdp, OSDP.device\_serial\_address set to 1, then the tick and Write](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-fd3497fef315141664aeb41add67e6c46fd71411%2FSECHUB-TS-VISIONPASS-07-mtbt-osdp-device-serial-address.png?alt=media)

Then, on the **OSDP Devices** tab of the controller:

1. Drag and drop (or copy and paste) the Morpho reader you created into the reader window.
2. Select the address you configured in MBTB.
3. Select the baud rate to match the one configured in MBTB.

![Controller 7000 Properties, OSDP Devices: Morpho Biometric Reader 1 at address 1, the configured address 1, and baud rate 115200](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-135cca8fcafab1f82cc4ebc59216b5531e5a300f%2FSECHUB-TS-VISIONPASS-08-controller-osdp-devices.png?alt=media)

The icon next to the reader changes, as above, once it has a connection.

#### Capture a cardholder's biometric

Biometrics are captured in Command Centre. In a test with only one VisionPass reader, designate it as the enrolment reader temporarily, to capture and enrol a cardholder. A real site needs **1 x enrolment reader and 1 x reader** for access at the door.

1. Assigning the reader as the enrolment reader requires the **Morpho Biometric Type**, with the VisionPass reader's IP address.

   ![Morpho Biometric Type 1 Properties, VisionPass: the enrolment reader VisionPass with its IP address (covered) and workstation, and Add](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-f0b4db5f3f1dcc769df14375604ce74c66f3be03%2FSECHUB-TS-VISIONPASS-09-enrolment-reader-ip.png?alt=media)
2. In Command Centre, select the cardholder to capture. Make sure the **Cardholder Biometrics** tile is in the viewer, then choose **Face** and **Capture**.

   ![Cardholder Viewer for a test cardholder: the Cardholder Biometrics tile with the Face tab and Capture highlighted (the site name in the title bar is covered)](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-37c0b78c41b0c8386f47bc77830a34fad5681514%2FSECHUB-TS-VISIONPASS-10-cardholder-biometrics-capture.png?alt=media)

   ![A VisionPass reader showing Face Enrollment with a progress bar](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-824e2d1279f5e36716c11ff5e8bfae805284373e%2FSECHUB-TS-VISIONPASS-11-face-enrolment-on-reader.png?alt=media)

   After the face enrolment, remove the VisionPass reader from its enrolment-reader role.

   The reader's database shows that the cardholder has been added:

   ![VisionPass Reader Properties, Status: VisionPass MD (MA5G), firmware 2.10.7, 1/20000 biometric records in the reader's database](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-76b61a5bfb3638f91742a8dc01280ec31e2dc34c%2FSECHUB-TS-VISIONPASS-12-reader-database-record.png?alt=media)
3. **Access Granted** shows once the VisionPass reader identifies the face.

   ![Event Properties: a test cardholder was granted entry into the Office Access Zone through the Office Door](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-683e1d5779a2dd7a494931dd1a7624f3c2a56ecd%2FSECHUB-TS-VISIONPASS-13-event-access-granted.png?alt=media)

#### Ways to use the reader for access

1. **Card number + biometrics:** the cardholder's card is encoded and their face enrolled through the VisionPass reader. They then gain entry with card and face.

   ![Card type Face Recog + Card: the DESFire Properties of the Morpho VisionPass object set to Card Number + Biometrics, Reader ignores PIN ticked](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-a56ea04ef2623b895d698371c6ce37ebf2028ceb%2FSECHUB-TS-VISIONPASS-14-card-number-plus-biometrics.png?alt=media)
2. **Card only:** if the site wants card access without face recognition, set the Morpho VisionPass object to **Card Number Only**.

   ![Card type Card for VisionPass Reader: the Morpho VisionPass object set to Card Number Only](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-0cae03aa65b3466509e76466bf10bc5e4c63564d%2FSECHUB-TS-VISIONPASS-15-card-number-only.png?alt=media)
3. **QR code** (from **9.10**; VisionPass firmware **2.8.9 or newer**, controller firmware **9.10.xxxxxxx or later**):
   * Enable **QR Code** on the reader's **Setup** tab.

     ![Morpho Biometric Reader Properties, Setup: Authentication Method with Biometrics, QR Code (highlighted) and Card ticked](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-1b3f097dc93b9cc16670c140dad5361a22b38c2a%2FSECHUB-TS-VISIONPASS-16-reader-setup-qr-code.png?alt=media)
   * Create a card type and add the **QR Code Access Token Object**. When using QR codes, follow the warning below this list.

     ![Card type QR Code Access Token Object in the card editor (the sample QR code is covered)](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-4088f7456022413b984d9998da3f386037b1b239%2FSECHUB-TS-VISIONPASS-17-qr-code-access-token-object.png?alt=media)
   * Assign the QR Code Access Token card type to the cardholder.

     ![Cardholder Properties, Cards: card 33, QR Code Access Token Object, issue level 1, enabled](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-ed8c524cd12c39d165bb32cba532990a2c2d3815%2FSECHUB-TS-VISIONPASS-18-cardholder-qr-code-card.png?alt=media)
   * On the **Print/Encode** tab, preview the QR code, print it, and present it to the VisionPass reader.

     ![Print/Encode: Print Card for card 33 QR Code Access Token Object, and the print preview (the QR code is covered)](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-37ceeabd60c2f4235d7cd2df8611099d3fe45011%2FSECHUB-TS-VISIONPASS-19-print-qr-code.png?alt=media)
   * Result:

     ![Event Properties: the QR-code cardholder was granted entry into the Office Access Zone through the Office Door](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-f4b97f46bb69b214300802d12a9bb3805aa97a7a%2FSECHUB-TS-VISIONPASS-20-qr-code-access-granted.png?alt=media)

{% hint style="warning" %}
When using QR codes, use a **separate facility code** from the server's, and set up an **independent QR user group**, to prevent security issues. Users with QR codes should **not** be in privileged access groups, and should **not** perform overrides.
{% endhint %}

### Use the VisionPass as an enrolment reader

The enrolment reader captures the information during enrolment. It is typically used to enrol face templates, to create and update the biometric record in the reader's database. To configure the VisionPass as an enrolment device:

1. Create a **Morpho Biometric** card type.
2. Add the VisionPass reader as an enrolment device.
3. Add the name and the VisionPass IP address.
4. Select the workstation where the VisionPass reader will be used as the enrolment device.

   ![Morpho Biometric Type Properties, VisionPass, and the Add or Modify Enrolment Readers dialog: Reader Name, IP Address and Workstation (the lab IP and the PC name are covered)](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-99aaa6bba6d451e2405b657abeef4895cfdf94f3%2FSECHUB-TS-VISIONPASS-21-add-enrolment-reader.png?alt=media)
5. In Command Centre, select the cardholder to enrol.

   ![Cardholder Viewer: the Cardholder Biometrics tile, Face tab, Capture (the site name in the title bar is covered)](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-8bbf90ef8cd874d765858d9397ebc3f049dbd4e7%2FSECHUB-TS-VISIONPASS-22-enrolment-capture.png?alt=media)

The enrolment configuration for the VisionPass reader is used solely for enrolment.

If the reader has a fault, see [VisionPass reader faults](https://help.security.gallagher.com/knowledge-hub/products/integrations/third-party-readers/idemia-morpho/troubleshoot/visionpass-reader-faults.md).


---

# 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/configure/set-up-an-idemia-visionpass-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.
