> 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/open-supervised-device-protocol-osdp-integration.md).

# Open Supervised Device Protocol (OSDP) Integration

### Introduction

Open Supervised Device Protocol (OSDP) replaces the Wiegand legacy protocol, and allows security devices such as card readers, controllers and I/O boards to talk to each other through a bi-directional RS485 channel.

**Controller 6000:** Supports up to 16 OSDP-compliant readers, split across runs - maximum 16 readers per run.

**Controller 7000:** Supports up to 32 OSDP-compliant readers, split across runs - maximum 16 readers per run.

***

### Functionality

The Gallagher OSDP Integration allows security devices to communicate using the OSDP standard.

Gallagher's OSDP Integration allows messages to be displayed on OSDP readers with screens. If reader display messages are enabled, the current date and time, and the door's or Access Zone's status, are displayed on the screen when the reader is idle. Additionally, access granted and descriptive access denied messages are displayed when a card is badged. If two readers are assigned to the same Exit Zone or Entry Zone of a Door - one OSDP and one non-OSDP - a Cardholder badging at the non-OSDP reader will result in the more descriptive access message being displayed on the OSDP reader (as well as the regular message on the non-OSDP reader).

A number of various default messages will display. [Click here](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/open-supervised-device-protocol-osdp-integration/list-of-displayed-messages.md) to see the messages that are displayed by default. If your site requires these messages to be changed, including whether the date and/or time are displayed, contact the Gallagher Support Team.

***

### Configuration

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) [Configuring an OSDP Reader](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/open-supervised-device-protocol-osdp-integration/configuring-an-osdp-reader.md)

**Note:** Sites licensed for Personal Identity Verification (PIV) will also have the ability to configure OSDP Veridt Stealth PIV Readers.

See [Open Supervised Device Protocol (OSDP) Veridt Stealth PIV Readers](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/piv-card-support/open-supervised-device-protocol-osdp-veridt-stealth-piv-readers.md) for further detail.

![](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 an OSDP Compliant Reader to a Gallagher Controller](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/open-supervised-device-protocol-osdp-integration/assigning-an-osdp-compliant-reader-to-a-gallagher-controller.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) [Moving OSDP Readers between Controllers](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/open-supervised-device-protocol-osdp-integration/moving-osdp-readers-between-controllers.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/open-supervised-device-protocol-osdp-integration.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.
