> 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/schlage-lock-interface/configuring-a-universal-card-format-to-support-different-schlage-credential-formats.md).

# Configuring a Universal Card Format to support different Schlage Credential Formats

### Introduction

Schlage credentials can be in different Wiegand formats, (i.e. 26A, 32X, 35X, 35C, 36X, 37H, 37X, 40X and 48X), of which some may not be supportedby default, (e.g. the standard 26A format works, however 37H format does not unless a Universal Card Format is configured in Command Centre). A Schlage Credential Formats document can be obtained from Allegion on request, and you should contact Allegion if you intend using any credentials other than the standard 26A format.

The default Schlage 26A format contains a total of 26 bits. The 8-bit facility code of this format will be randomly generated with the badge ID.

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

Additional credential detail can be found in the **Schlage Credential Formats-200624** documentation located in the `'Utilities\Schlage\Documentation'` directory.

Schlage MIFARE Classic 26A standard card data will be encoded on sector 1, while Schlage Mifare DESFire EV1 to EV3 card data will be encoded using AppID F532F0. Other Command Centre encoded card data, (i.e. Morpho) should be co-located around the fixed Schlage data.

### Schlage Card Indentification

The Schlage encoded card format and badge ID can be identified by applying the following key to the text printed on the credential (ISO card shown).

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

Should the site inherent Schlage encoded cards that fall outside of the standard 26A format, then Command Centre will look for the card format configuration found within the Universal Card Format (UCF) configurator. A UCF format will need to be created to suit.

This procedure describes how to configure a new Card Type and a Universal Card Format to support the 37H format.

### Procedure

1. Click **Configure** from the menu bar, then **Card Types**.

   The **Card Type** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. **Right click** and select **New\...Card Type.**

   By default the **General** tab displays.
3. Enter a Name and Description, and select the division for this Card Type.
4. Configure the remaining tabs as required, and click the **OK** button.
5. **Configure** from the menu bar, then **Universal Card Format**.

   The **Universal Card Format** List Window opens.
6. **Right click** and select **New\...Universal Card Format**.
7. Enter a Name and Description, and select the division for this Universal Card Format.
8. Click the **Format** tab.
9. Select the **Wiegand** radio button to indicate the required format.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-62be26968446643a3277397a4e7b56b7a478d1af%2Fschlage_ucf.png?alt=media)
10. Change the parameters to describe the data on the cards to be supported as follows:

    | **Number of Bits**                  | = 37 |
    | ----------------------------------- | ---- |
    | **Bits in Facility Code**           | = 0  |
    | **Bits in Card Number**             | = 35 |
    | **First Bit of Card Number**        | = 2  |
    | **Bits to Sum for Even Party**      | = 19 |
    | **Bits to Sum for Odd Party**       | = 19 |
    | **First Bit to Sum for Odd Parity** | = 19 |
11. Select the **Facility Code** on the Card Type you created that will be used when you create Schlage credentials later.
12. Click the **OK** button.
13. Assign the new Universal Card Format to the Controller's **Card Formats** property page.

    For further information about Universal Card Formats, refer to [Universal Card Format](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/universal-card-format.md).

### How to read Schlage card details and create a cardholder

1. Connect the MT20 Allegion card reader to the PC, and open a notepad++ or similar application.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-a6f0d5c7f7e3984e720a2c9c9bc09c45113597d7%2Fmt20allegioncardreader.png?alt=media)
2. Badge a Schlage card.
3. Check the information on the card, it basically contains the following details:

   *For example:*

   UCF 26-Bit Standard(26A) format, once the card is badged, the card information displays as follows:

   **EE006680;26A;220;205;**

   |          | Engage Card format | Facility Code | Card number |
   | -------- | ------------------ | ------------- | ----------- |
   | EE006680 | 26A                | 220           | 205         |
4. Create a card type by using the above information.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-d2d1d24b48977db832829b4569f8d24a75070b91%2Fschlagecardtypedetails.png?alt=media)
5. Create a cardholder with this correct card type and card number.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-e398b811bfd56526653fca40897f3f0975b213cd%2Fschlagecardassignedtoch.png?alt=media)
6. Badge the card at an Allegion door and check the correct cardholder has gained access to door lock.


---

# 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/schlage-lock-interface/configuring-a-universal-card-format-to-support-different-schlage-credential-formats.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.
