> 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-text-vs-controller-resident-plugin.md).

# Middleware Framework - ASCII text vs Controller Resident plugin

Compare middleware ASCII text plugins with controller-resident plugin deployment.

The older ASCII Text plugin needs the Middleware plus the ASCII Text Plugin, often via RS232 and a **MOXA** converter. The Controller-Resident Plugin removes the Middleware entirely, and usually the MOXA as well. A C6000 sends ASCII straight out its TCP or RS232 port.

|                | Older ASCII Text plugin | Controller-Resident Plugin     |
| -------------- | ----------------------- | ------------------------------ |
| Middleware PC  | Required                | Not required                   |
| MOXA converter | Often required (RS232)  | Usually not required           |
| ASCII path     | Middleware to device    | C6000 TCP or RS232 port direct |

***

🔗 **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 and their constraints.
* [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/controller-api-ftcapi-and-middleware-f/middleware-framework-ascii-text-vs-controller-resident-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.