> For the complete documentation index, see [llms.txt](https://docs.influxtechnology.com/support_guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.influxtechnology.com/support_guides/k-series-product-manual/k-series-product-manual/k-tc-user-quick-start-guide/software-introduction/configuration-panel.md).

# Configuration Panel

The configuration panel comprises the available TC channels with respect to the device connected and the sampling rates for each Channel in the corresponding dropbox.

<figure><img src="https://1039220062-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRhWtYvkHNZy7Jvdnc3wk%2Fuploads%2Fih4l2ZFp7Nb3QTAHq935%2Fimage.png?alt=media&amp;token=4848dbf8-9e91-4940-93de-35575d595a00" alt=""><figcaption></figcaption></figure>

Users can also specify the names for each channel, which the TC Logger software will use during data export.

The channel names and the rates will be saved with the configuration in xml format.

Users can import the configuration before exporting the data so that the data exported will have the labels specified by the user.

<br>


---

# 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://docs.influxtechnology.com/support_guides/k-series-product-manual/k-series-product-manual/k-tc-user-quick-start-guide/software-introduction/configuration-panel.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.