> 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/the-how-to-guide/retrieving-the-datalog.md).
# Retrieving the Datalog
### Step 1
Connect the logger to the PC via USB.
Status Bar will display the logger status and time information.
### Step 2
Click on the "Internal Storage"
The below window will open up:
### Step 3
Load the XML confiugation which contain the channel names.
### Step 4
The log files in the internal logger memory will be displayed.
Select the files to be retrieved.
### Step 5
Click Export.
### Step 6
Select the TC channel required for exporting.
### Step 7
Select the required output format.
{% hint style="info" %}
#### Notes:
* Enabling "Use full date/time "allows user to export data in real-time stamp "dd:mm: yyyy: hh:mm:ss"
{% endhint %}
### Step 8
Browse and choose a location to save the data
### Step 9
Click process to export the file
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.influxtechnology.com/support_guides/k-series-product-manual/k-series-product-manual/k-tc-user-quick-start-guide/the-how-to-guide/retrieving-the-datalog.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.