> 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/morpho-biometric-integration/morpho-osdp-configuration/configuring-the-controller-rs-485-bus-for-osdp.md).

# Configuring the Controller RS-485 Bus for OSDP

### Introduction

This topic describes how to configure the Controller RS-485 Bus for Open Supervised Device Protocol (OSDP) and assign the Morpho reader to the Controller.

### Configuration

1. In Command Centre Configuration Client, click **Configure** from the menu bar, then **Hardware**.

   The **Hardware** List Window opens.
2. Highlight the Controller you want to configure the RS-485 Bus for OSDP.
3. **Right click** and select **Properties**.
4. Click the **Setup** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-bd269dcd232f6cb82127dc2f9048addd03478b05%2Fcontroller_setuptab_osdp.png?alt=media)
5. In the Hardware section of this screen, select the 'OSDP' option form the **RS-485 Bus 1** and/or **RS-485 Bus 2** drop-down lists as appropriate.

   Depending on which RS-485 Bus option(s) you selected 'OSDP' for, an **OSDP Devices** and/or **OSDP Devices 2** tab appears, allowing you to add up to 16 OSDP Readers and/or Morpho Biometric Readers to the Bus port on this Controller.

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

   **Note:**

   * **Controller 6000:** Supports up to 16 OSDP and/or Morpho Biometric readers per controller, split across runs (maximum 16 readers per run).
   * **Controller 7000:** Supports up to 32 OSDP and/or Morpho Biometric readers per controller, split across runs (maximum 16 readers per run).
   * The total number of Morpho readers allowed across the site is determined by the license file.
6. Click the **OSDP Devices** tab.
7. From the **Hardware** List Window, select the Morpho Readers attached to this Bus.

   Drag and drop each Reader into the grid on the **OSDP Devices** tab.

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

   **Notes:**

   * Each Morpho reader that is added receives a unique address (Address Range = 0 - 126). The **Configured Address** automatically increases.
   * If readers don’t have a unique **Configured Address** and you click **Apply**, the following error message displays:

     *"Device addresses on the same bus must be unique."*
   * The **Change Device Address** section only works for OSDP readers, and is disabled for Morpho readers.
8. If you want to change the **OSDP Bus Baudrate** for communication between the reader and the Controller, select the appropriate **Baudrate** from the drop-down list.

   **Note:** The default baud rate for newly created Controllers will be "115200", but for existing Controllers it will remain as "9600". We recommend "115200" is used for better performance.
9. 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.

The reader status should display as "Secure OSDP Communication" on the reader’s **Status and Overrides** tab.

By default, the communicationbetween controller and reader is encrypted.

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


---

# 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/morpho-biometric-integration/morpho-osdp-configuration/configuring-the-controller-rs-485-bus-for-osdp.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.
