> For the complete documentation index, see [llms.txt](https://manual.edgetx.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.edgetx.org/v2.9/edgetx-user-manual/user-manual-for-color-screen-radios/channel-monitor.md).

# Channel Monitor

The Channel Monitor shows both the output value (top bar) and mix value (bottom bar) for each of the 32 radio channels, spread across 4 pages of 8.

<figure><img src="https://2538274303-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjAgpAXMB9RpRNV8hOqZD%2Fuploads%2F2s7sRtjyibf6eSX1j61B%2Fchannelmonitor.png?alt=media&amp;token=4953e831-b626-4b13-b8ae-568fff394549" alt=""><figcaption><p>Channels Monitor</p></figcaption></figure>

The 5th page of the channel monitor is the logical switches monitor. On this page, you will see the status (activated/non-activated) of all logical switches. Logical switches that are activated are highlighted.

<figure><img src="https://2538274303-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjAgpAXMB9RpRNV8hOqZD%2Fuploads%2Fk0MyMjnu901admy5pxmN%2Fchannelmonitor2.png?alt=media&amp;token=aef982b1-6cbc-4299-92e2-30f2e23352ae" alt=""><figcaption><p>Logical Switches Monitor</p></figcaption></figure>


---

# 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://manual.edgetx.org/v2.9/edgetx-user-manual/user-manual-for-color-screen-radios/channel-monitor.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.