> 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-crps-plugin.md).

# Middleware Framework - CRPS plugin

Use the CRPS plugin for controller-resident ASCII text communication.

The Controller-Resident Plugin (CRPS) lets a C6000 send ASCII straight out its TCP or RS232 port, without a middleware PC.

## Replacing the CCTV Module

The CCTV Module handles serial camera switching, and is often repurposed for pager messaging. It is **not supported on Windows 10** and has been removed from the ISOs. Replace it with CRPS, or with the harder-to-set-up ASCII Plugin for Middleware.

> ⚠️ A controller serial port cannot accept incoming connections, because it is an application connection. The CRPS must connect to a **server** serial device. Two applications cannot reliably connect to each other; one must be a server.

***

🔗 **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.
* [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-crps-plugin.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.