> 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/api/crps-basic-configuration.md).

# Controller Resident Plugin (CRPS)

Configure Controller-Resident ASCII Text Plugin messages for external systems.

These are the basic configuration patterns for the Controller-Resident ASCII Text (CRPS) plugin.

## Incoming

1. Configure an **External System** and create External Items.
2. Send the activation string **"Alarm"** over TCP. It appears in the Event and Alarm Viewer (Activation window).
3. Send **"Normal"** to move it to the Return to Normal window.

## Outgoing via an Output

1. Create an External Item on the External System.
2. Add a virtual or physical output in the trigger window.
3. Set the per-state messages in the **Messages** tab.

## Outgoing via a Door (access event)

1. Note the door's Access Zone.
2. Create an External Item with that Access Zone.
3. Add the events to push, for example cardholder name `CH`, FT Item ID `CI`, card number `CN`, and source `ES`.
4. Assign the External Item to an **Action Plan**.
5. Assign the Action Plan to the door's **Event Response**.

The message format is fully configurable (see the release note). Mobile-credential card numbers appear as hex, for example `0x8EC2…`.

***

🔗 **Related**

* [Middleware Framework - ASCII Interface (CRPS) Plugins](/knowledge-hub/products/cc-software/configure/interface-options/api/controller-api-ftcapi-and-middleware-f/middleware-framework-ascii-interface-crps-plugins.md). The three ASCII options.
* [Middleware Framework - CRPS Plugin](/knowledge-hub/products/cc-software/configure/interface-options/api/controller-api-ftcapi-and-middleware-f/middleware-framework-crps-plugin.md). Using CRPS in place of the CCTV Module.


---

# 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/api/crps-basic-configuration.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.