> 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.md).

# Schlage Lock Interface

### Introduction

The Schlage Lock Interface is a licensed feature of Gallagher Command Centre. This feature supports Schlage wired (AD30X) and wireless (AD40X) locks with Gallagher Controller 6000s.

{% hint style="danger" %}
**Important:** This integration is not intended for use in cases where encryption is required.
{% endhint %}

The Schlage Lock Interface allows one Gallagher Controller 6000 or 7000 to manage up to 8 Panel Interface Modules (PIM’s), and either 16 Schlage AD40X locks ot 8 Schlage AD30X locks, or a combination of both totaling 16. The hardware will consume allocations as below:

* PIM400 will consume one PIM allocation
* AD40X will consume one lock allocation
* AD30X will consume one PIM allocation and one lock allocation

A single PIM400 can have up to 16 Schlage AD40X devices connected to it. If more than one PIM400 is connected to the controller, it is important to note that the total number of locks the controller can manage is still 16, it does not increase.

In Command Centre, a Schlage PIM400 is attached to one of the two RS-485 buses on the Controller 6000 or 7000, and a Schlage AD40X Lock is assigned to a Schlage PIM400. The Schlage AD30X is attached directly to one of the two RS-485 buses on the Controller 6000 or 7000.

Physically, a Schlage PIM400 is wired to one of the two RS-485 ports on a Controller 6000 or 7000. If more than two PM400s need to be connected, they can be wired together into the RS-485 bus, or an extension board can be used. A Schlage AD40X lock talks to a Schlage PIM400 via 900 MHz wireless communication. The Schlage AD30X lock is wired directly into one of the two RS-485 buses, and they can also be wired together, or an extension board used, if more than two AD30X devices need to be connected to a single controller.

If the site wishes to use both Gallagher and the Schlage AD series of locks, an HBUS can be connected to a free RS-485 bus.

**Note:** If the site is using the PIV functionality available in the AD302 and AD402 locks, a Gallagher High Sec Controller 6000 or 7000 is required.

<details>

<summary>Schlage High Security (PIV Card) System Diagram</summary>

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

Schlage AD302 and AD402 lock hardware is supplied with the Schlage FMK reader. In addition to supporting PIV cards (for FIPS 202-2 compliance), this reader is also able to support Schlage encoded MIFARE Classic and DESFire credentials.

The AD302 and AD402 locks will require the Gallagher High Sec Controller 6000 device in order to manage the challenge response for PIV credential certificates.

The Keypad PIN functionality for this reader would be configured from within Command Centre. For entering PINS the **\*** button on the door lock keypad will clear any numbers entered, and the **#** button is the **Enter** button.

Enrolment of PIV credentials will be performed through the PIV enrolment reader.

**Note:** Refer to [PIV Card Support](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/piv-card-support.md) for further details on how PIV cards work in Command Centre.

</details>

<details>

<summary>Schlage Standard (non-PIV) System Diagram</summary>

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

Schlage AD300 and AD400 hardware is able to support various card technologies supplied by Allegion and HID. This integration has been tested with Low Frequency (125KHz), and High Frequency readers. Schlage and HID credential types 125KHz, MIFARE Classic, DESFire EV1, IClass and IClass SE has been tested with Command Centre. Support of these Credential formats are managed through the configuration of the Universal Card Format section.

**Note:** The USB enrolment reader used for PIV card enrolment is not required.

</details>

***

### Command Centre Door Licensing

Each Schlage AD30X and AD40X lock will require a Command Centre Schlage Door License (2A08900 - Schlage license without hardware (per door)).

The license file must contain the following option:

`[Limits]`\
`Schlage Doors=X`

A Command Centre PIV license is required to enable PIV cards to be enrolled.

***

### Schlage Hardware Device Limits

* One Schlage RS485/900MHz PIM400 supports up to 16 Schlage AD40X 900MHz Doors
* One RS-485 port on Controller 6000 or 7000 supports up to 8 Schlage RS485/900MHz PIM400s’
* One RS-485 port on Controller 6000 or 7000 supports up to 16 Schlage AD40X Doors or 8 Schlage AD30X Doors
* One Controller 6000 or 7000 supports up to 8 Schlage RS485/900MHz PIM400s’
* One High Sec Controller 6000 or 7000 can support up to 16 Schlage AD40X Doors or 8 Schlage AD30X Doors
* One Controller 6000 or 7000 supports up to 16 Schlage AD400 Doors or 8 Schlage AD300 Doors

***

### Schlage Configuration Settings

* To receive battery status messages from the Wireless AD-40X devices at a frequency of less than 10 minutes, the heartbeat must be manually configured via the Schlage hand-held device.

  **Note:** Changing the Schlage Door's heartbeat time can cause issues. Therefore, we recommend not changing it where possible.
* For AD40X devices, PIM400 wakeup, Permitted Card Technology and PIV Authentication Mode changes may require up to 2 door heartbeat cycles to take effect. The recommended default door heartbeat period is 10 minutes.
* Access Zones can be in Secure, Secure + PIN and Free access mode.
* Configuration changes and Access Zone access mode changes should not be made at the same time.
* Custom site keys are not available with the GGL/Schlage integration.

{% hint style="danger" %}
RS-485 communications between the controller and Schlage locks or PIM 400's (Panel Interface Modules) are **not encrypted and should be physically secured against tampering**.
{% endhint %}

***

### Tips

* If you change the RS-485 address of the PIM it will be dynamically updated on the controller. The RS-485 address of the PIM sepcified in Command Centre needs to match the one configured in the Schlage HHD.
* All values for RS485 Address and AD-Series Doors must be between 0-254.
* Address values cannot be duplicated on a common RS485 Bus.
* High door value must be >= Low door value.
* High door value cannot be any more than 16 higher than the Low door value.
* If you attempt to give two PIMs on the same bus the same address you will get the following error:

  *RS-485 Addresses on the same bus must be unique.*
* Wakeup is enabled by default to 10 seconds (from v8.40). This is required to support remote lock overrides from the Command Centre server.

***

### Battery Management

Command Centre is able to monitor the voltage level status of each AD series lock, and display the current voltage level in the Status and Overrides property page of the Schlage Door, as shown in the screen shot below. Low and Critical battery alarms are available help to manage lock failure due to battery depletion.

#### AD30X Locks

AD30X locks must never be powered with batteries. The AD30X requires 12 or 24 VDC 250 ma AUX power. The AD300 must be powered from an external AUX supply to provide sufficient power for the RS-485 communication, the AD30x will not function on batteries.

#### AD40X Locks

AD40X locks can be powered by 4 or 8 batteries. Reader types determine voltage levels needed for operation. Locks with smart card readers, SM & MT, require higher voltage levels. Locks with Prox and Mag card readers can operate to lower voltages. A low or critical battery alarm is raised when the battery pack of the lock depletes to a certain threshold. The table below shows the battery voltage levels corresponding to the low and critical alarms.

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

<table><thead><tr><th width="193"></th><th width="342">4 Battery Holder</th><th>8 Battery Holder</th></tr></thead><tbody><tr><td>New batteries</td><td>6.2 VDC</td><td>12.4 VDC</td></tr><tr><td>Low battery alarm</td><td><p>4.7 VDC (for SM &#x26; MT readers)</p><p>3.7 VDC (for Magnetic swipe and 125KHz readers)</p></td><td>7.2 VDC</td></tr><tr><td>Critical battery alarm</td><td><p>4.6 VDC (for SM &#x26; MT readers)</p><p>3.4 VDC (for Magnetic swipe and 125KHz readers)</p></td><td>6.9 VDC</td></tr></tbody></table>

USB communication with the HHD will stop working at 4 VDC.

Gallagher recommends checking the voltage of all locks at the time when a low battery alarm occurs so other locks close to low level can undergo battery replacement at the same time. At critical level, AD40X locks will fail to operate, go to Fail mode of "As-is; Safe; Secure", and lose any data stored within the lock.

***

### Emergency Opening

A mechanical key override is provided with All Schlage AD series locks. This can be used to mechanically open the door for emergency recovery or for manual entry.

**Note:** The mechanical key override event may not be raised by the lock if the battery depletes to critical level.

***

Select the item below that you require further detail on:

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Schlage Device Setup and Configuration](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/schlage-lock-interface/schlage-device-setup-and-configuration.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Configuring a Gallagher Controller for Schlage RS485 Devices](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/schlage-lock-interface/configuring-a-gallagher-controller-for-schlage-rs485-devices.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Creating a Schlage PIM (Panel Interface Module)](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/schlage-lock-interface/creating-a-schlage-pim-panel-interface-module.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Creating a Schlage Door in Command Centre](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/schlage-lock-interface/creating-a-schlage-door-in-command-centre.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Assigning Devices](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/schlage-lock-interface/assigning-devices.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Performing Overrides on a Schalge Door](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/schlage-lock-interface/performing-overrides-on-a-schlage-door.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Configuring a Universal Card Format to support different Schlage Credential Formats](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)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Configuring PIN Only function on a Schlage AD Series Reader](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/schlage-lock-interface/configuring-pin-only-function-on-a-schlage-ad-series-reader.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/configuration-client/integrated-systems/schlage-lock-interface.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.
