> 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/overrides-on-morpho-osdp-readers.md).

# Overrides on Morpho OSDP Readers

### Introduction

This topic describes how to perform overrides on a Morpho Reader added to an OSDP connection.

### Configuration

#### Shunt and Unshunt overrides

Shunt overrides stop communication to the reader, and all inputs and outputs on that reader will no longer be available by the system. It will remain that way until you perform an "Unshunt" override.

**Note:** Shunt and unshunt overrides only display for Morpho readers that have been added to an OSDP connection.

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

   The **Hardware** List Window opens.
2. **Right click** on the appropriate Morpho Reader, and click **Override…** from the drop-down menu.
3. Click within the **Override** field and select **Shunt** from the drop-down list.

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

   **Note:** When the "Shunt" override is selected, the Time setting and **Cancel Overrides** button is disabled.
4. Click the **Override Now** button.

   From this screen you can see the status change as a result of the override.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-e9d8573bc00e28085cb9624166154c45a6e32d58%2Fmorphoreader_shuntoverride.png?alt=media)
5. Click the **OK** button.

   **Result**

   The reader has been shunted, and a "Device Shunted" event is generated. It will remain that way until you perform an "Unshunt" override.

   While the "Shunt" override is in place, the system will not monitor the reader, and the reader will not generate alarms or cause event initiated actions.

#### Re-initialise Encryption overrides

If a reader is replaced, the new one will still be using the previous reader’s IP address. To correct this, a "Re-initialise Encryption" override is required.

During the OSDP assignment, if the status shows as "Encryption required" the operator can still use this override to solve this problem.

This override only works if the device is online. Performing the override when the device is offline has no effect.

The override can be performed as follows:

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

   The **Hardware** List Window opens.
2. **Right click** on the appropriate Morpho Reader, and click **Override…** from the drop-down menu.

   The **Status and Overrides** tab of the Morpho Reader properties displays with the reader status displaying as "Encryption required".

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f0d233049db7d8011628c609a5bc83ccca250c68%2Fmorphoreader_encryptionrequired.png?alt=media)
3. Click within the **Override** field and select **Re-initialise encryption** from the drop-down list.

   **Note:** When the "Encryption required" override is selected, the Time setting and **Cancel Overrides** button is disabled.
4. Click the **Override Now** button.

   From this screen you can see the status change back to "Secure OSDP Communication" as a result of the override.
5. Click the **OK** button.


---

# 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/overrides-on-morpho-osdp-readers.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.
