> 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/aperio-integration/configuring-the-aperio-locks-readers/configuring-r100-readers.md).

# Configuring R100 Readers

### Introduction

R100 readers can only be connected to Aperio AH20 Wiegand hub. They are not supported on RS485 bus. They should be configured as any standard third party reader in Command Centre.

**Important:**

* R100 readers do **NOT** support double card overrides.
* In order to get card events back in Command Centre from when the reader is in free mode, enable 'Remote Unlock' functionality on the hub in PAP.

Detailed instructions are given in the procedure below.

### Pre-requisite

Before performing this procedure, the R100 reader must be paired with AH20 hub and connected to the controller.

### Procedure

1. Create a Third-Party reader in Command Centre.

   For further detail see [Creating Readers](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-readers.md).
2. Create a door with the reader created in the above step configured at the entry zone.

   For further detail see Creating Doors.
3. Click **Configure** from the menu bar, then **Universal Card Format**.
4. Go to the Controller properties and click the **Card Format** tab.
5. Drag the Universal Card Format “Wiegand 128/16 bit” onto the card format tab of the Controller.

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

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-58e09097c897eb8b6441e20f5e682ea299bd565b%2Fr100reader_6000cardformatstab.png?alt=media)
6. Click **Apply**.

#### Enable 'Remote Unlock' on the hub

1. Go to Aperio PAP.
2. **Right-click** the hub and select **Communication Hub** > **Configure…**

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-217dd4386af457429211016d75b123d7e82681e7%2Fr100reader_papconfigure.png?alt=media)
3. Click **Next** to go to **Electronic Access Controller Settings** screen of the wizard.
4. Click **Remote Unlock** > **Change**.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-5a0cd0312e32eb5dc2cb4cdc831297be9a16e4ee%2Fr100reader_remoteunlock.png?alt=media)
5. Set the Remote unlock duration.

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

   **Important:** The duration set for Remote unlock must be greater than the scheduled time configured for the lock to be in Free mode.

   *For example:* If the Command Centre schedule configured on the lock sets the door in free mode for 8 hours, then the ‘Unlock Duration for Wiegand’ must be set to greater than 8 hours.

   This configuration is however ignored in *Secure* mode.
6. Keep clicking **Next** until you reach the Device Update Result screen.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-fc1553a466b4c86f7ae0c8db5c51e885dd7ca18d%2Fr100reader_deviceupdatescrn.png?alt=media)
7. Click **Apply**.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-273c97627d74472e1411fb1d3da28db7b4fc54b3%2Fr100reader_deviceupdateresult.png?alt=media)
8. Click **Close**.


---

# 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/aperio-integration/configuring-the-aperio-locks-readers/configuring-r100-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.
