> 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-gallagher-controller-for-schlage-rs485-devices.md).

# Configuring a Gallagher Controller for Schlage RS485 Devices

### Introduction

This procedure describes how to configure a Gallagher Controller for Schlage devices.

**Note:** AD30X locks and PIMs (AD40X) can be used on the same bus.

### Procedure

1. Click **Configure** from the menu bar, then **Hardware**.

   The **Hardware** List Window opens (in [tree view](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#tree-view)).
2. Highlight the Controller you want to assign the new Schlage devices to.
3. **Right click** and select **Properties.**

   By default the **General** tab displays.
4. Click the **Setup** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-913a765568358dc0ad0233950b68772e88a218e9%2Fschlage_controller6000setup_tab.png?alt=media)
5. In the Hardware section of this screen, select the 'Schlage' option from the appropriate drop-down list, (i.e. **RS-485 Bus 1** or **RS-485 Bus 2** ).

   Depending on which RS-485 Bus option you selected 'Schlage' for, a **Schlage PIMs 1** or **Schlage PIMs 2** tab appears, allowing you to add up to 16 Schlage Doors to the Bus port on this Controller.
6. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.


---

# 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-gallagher-controller-for-schlage-rs485-devices.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.
