> 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/rexdesk-configuration-software-s/rexdesk-rexgen-series-configuration-software/rexdesk-manual/quick-start-guide/preparation-of-configuration/logging-digital-channels.md).
# Logging Digital Channels
* Create a new project.
* Drag and drop the Digital tool to the Channels area of the configuration window.
* Select the Digital channel from Digital channel Dropbox. Enter the sampling rate required for logging in to the sampling rate column.
The ‘Add’ option enables the user to add another digital channel to the configuration.
The ‘Edit’ option enables the user to edit the current configuration.
The ‘Remove’ option lets the user remove the added analogue channel.
* Click “Run Configuration,” save the project, and provide a name for it. The logger will create files with the project name.
 The configuration will be loaded in the data logger, and logging will start immediately.
[Video Tutorial](https://youtu.be/ksjbOI8hGXU?si=itNxoDHbLOjw3vcS)
---
# 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/rexdesk-configuration-software-s/rexdesk-rexgen-series-configuration-software/rexdesk-manual/quick-start-guide/preparation-of-configuration/logging-digital-channels.md?ask=&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.
