> 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-card-technologies/hid-26-8-cards.md).

# Configuring HID 26/8 cards for use at Aperio Doors

### Introduction

There are two types of HID 26/8 cards that can be used at Aperio doors:

* HID IClass 26/8 (high frequency) cards, and
* HID 125khz 26/8 (low frequency) cards

While both types can interact with doors fitted with Aperio locks within a Command Centre environment, the HID IClass 26/8 (high frequency) cards need no additional settings in PAP are required to set this up. Unlike the HID 125khz 26/8 (low frequency) cards which do require additional set up in PAP.

Therefore, this procedure only relates to configuring HID 125khz 26/8 (low frequency) cards.

### Prerequisites

The latest version of the Aperio Programming Application Protocol (PAP) must be installed from the `'Utilities\Aperio'` directory of the Command Centre installation files.

### Procedure

You need to apply the HID 125khz 26/8 configuration to a lock in Aperio PAP.

1. **Right click** the lock and select **Lock/sensor** > **Configure…**

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

   The Configure Lock/sensor screen opens.
2. Select **Low frequency** from the drop-down list and click **Add...**

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

   The Low Frequency Configuration dialog displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-e9a52e374a8bb9dbe3d0952a76e2568d7c6dccd6%2Flowfrequencytype.png?alt=media)
3. Select ‘HID Prox’ from the drop-down list, then click **OK**.

   The Low Frequency Configuration dialog closes and you are returned to the Configure Lock/Sensor screen.
4. Click the **Next** button on each screen until you reach the ‘Device Update’ screen.

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

   **Note:** We recommend that you save the configuration at this point in order to more easily apply the configuration to other locks.
5. Click **Apply** and badge an HID 125khz 26/8 card at the Aperio lock to upload the new configuration to the lock.

   If the lock is updated successfully, the following screen displays:

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

   See [Locks failing to update](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/aperio-integration/configuring-the-aperio-locks-readers/configuring-card-technologies/locks-failing-to-update.md) for details of what happens if the lock configuration fails.


---

# 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-card-technologies/hid-26-8-cards.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.
