> 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/controller-api-ftcapi-and-middleware-f/middleware-framework-ascii-interface-crps-plugins.md).

# Middleware Framework - ASCII interface (CRPS) plugins

Select a Middleware Framework or controller-resident ASCII text plugin.

Many systems accept ASCII text commands, including matrix switches, fire panels, DVRs, and paging systems. The ASCII interface (CRPS) is Part # **C12669**. There are three options.

1. **Middleware plugin.** The controller sends ASCII to the third party. This needs a **separate middleware PC**.
2. **Controller-Resident RS232 ASCII Text Plugin.** Send and receive ASCII via the **C6000 RS232** port, with no middleware PC.
3. **Controller-Resident TCP ASCII Text Plugin.** The same, via the **C6000 TCP** port.

## Constraints

* Controller-resident plugins can send and receive on a connection, but they **cannot accept an incoming TCP connection initiated by another device**.
* The connection must be **persistent**. There is no ad-hoc connection.
* Supported **v8.20 to v9.40** (the Controller Resident Plugin Support customisation). The Controller-Resident Plugin is available from **v7.20+**.

***

🔗 **Related**

* [Middleware Framework - ASCII Text Vs Controller Resident Plugin](/knowledge-hub/products/cc-software/configure/interface-options/api/controller-api-ftcapi-and-middleware-f/middleware-framework-ascii-text-vs-controller-resident-plugin.md). When to drop the middleware PC.
* [CRPS Basic Configuration](/knowledge-hub/products/cc-software/configure/interface-options/api/crps-basic-configuration.md). Configure incoming and outgoing messages.


---

# 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/controller-api-ftcapi-and-middleware-f/middleware-framework-ascii-interface-crps-plugins.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.