> 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/wiring-morpho-readers-for-osdp.md).

# Wiring Morpho Readers for OSDP

### Introduction

This topic describes how to wire Morpho readers for Open Supervised Device Protocol (OSDP).

### Configuration

1. On the back of the Morpho Reader, find the bundle labelled RS485 or RS422.
2. Separate three lines on in the bundle.

Notes:

* **Controller 6000:** Maximum of 16 OSDP Readers (16 per RS485 port)
* **Controller 7000:** Maximum of 32 OSDP Readers (16 per RS485 port)
* Refer to section **2.4 RS485 cabling** of the [3E2028 Install Note Gallagher Controller 6000](https://media.gallagher.com/m/5c1c1876fd96d379/original/3E2028-Install-Note-Controller-6000-Series.pdf) for further information.

### For Sigma Lite, Sigma Lite+, Sigma Touch Go and Sigma Touch Pro readers:

<table><thead><tr><th width="526">Morpho Readers that supports RS485 only</th><th>Controller RS485 Port</th></tr></thead><tbody><tr><td>RS485_A Blue</td><td>A</td></tr><tr><td>RS485_B Blue / Red</td><td>B</td></tr><tr><td>RS485_GND Black / Red</td><td>-</td></tr></tbody></table>

### For VisionPass SP, VisionPass, MorphoWave, Sigma Extreme and Sigma Wide readers:

<table><thead><tr><th width="526">Morpho Readers that supports RS422 &#x26; RS485</th><th>Controller RS485 Port</th></tr></thead><tbody><tr><td>RS485_TX_Y Green / Black</td><td>A</td></tr><tr><td>RS485_TX_Z Green / White</td><td>B</td></tr><tr><td>RS485_GND Black / Red (Black for VisionPass SP)</td><td>-</td></tr></tbody></table>


---

# 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/wiring-morpho-readers-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.
