> 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/products/cc-software/configure/interface-options/open-supervised-device-protocol-osdp/osdp-setting-up-an-osdp-device-for-the-first-time.md).

# OSDP - setting up an OSDP device for the first time

Assign unique addresses when connecting OSDP devices to Controller 6000.

## About OSDP

**OSDP** (Open Supervised Device Protocol) is an access-control communications standard from the **Security Industry Association (SIA)**. It is the modern replacement for the roughly 40-year-old **Wiegand** protocol. Wiegand is unencrypted (and so hackable), unsupervised, uni-directional, and cannot be daisy-chained, because each reader home-runs to the controller over a limited distance. OSDP is a non-proprietary, bi-directional RS485 interface that lets readers, controllers, and I/O boards talk to each other.

> ⚠️ OSDP, like all RS485 protocols, does **NOT** support **Star**-connected wiring. Always run OSDP in **Daisy Chain** configuration.

**Gallagher support:**

* **OSDP v2.1.6**, available from **Command Centre v7.30**.
* OSDP connectivity on **each of the two RS-485 ports of the Controller 6000 only**. Up to **16 OSDP readers per controller** across a maximum of **10 controlled doors** (**8 OSDP readers per RS485 port**).
* Supports OSDP-enabled **card** and **card + PIN** readers.

## Setting up a new device

A new OSDP device usually ships with **address 0 or 1**, which conflicts if you put more than one on a controller's OSDP bus.

1. Connect **only one OSDP device at a time** to the controller.
2. Assign it a **new, non-conflicting ID** (note the identity for future replacement).
3. With the reader online, select the new address and apply it. The device's OSDP address updates.
4. Connect the next device and re-address it. Repeat until all are connected.

![Command Centre OSDP device pairing: the Change Device Address section (device list, Configured and Device Address, Change Address) and OSDP Bus Baudrate 115200](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-12e7f3986a1f7b9b71558bc7d103fcbd9aba9700%2FSECHUB-OSDP-01-change-device-address.png?alt=media)

OSDP-connected readers also feature in specific reader integrations. For example, [IDEMIA (Morpho)](/knowledge-hub/products/integrations/third-party-readers/idemia-morpho.md) and [Invixium](/knowledge-hub/products/integrations/third-party-readers/invixium.md) readers both support OSDP.

***

🔗 **Related**

* [IDEMIA Morpho OSDP](/knowledge-hub/products/integrations/third-party-readers/idemia-morpho/configure/idemia-readers-idemia-morpho-osdp.md). OSDP with an IDEMIA reader.


---

# 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/products/cc-software/configure/interface-options/open-supervised-device-protocol-osdp/osdp-setting-up-an-osdp-device-for-the-first-time.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.