> For the complete documentation index, see [llms.txt](https://docs.intrepidcs.com/vspy-3-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intrepidcs.com/vspy-3-documentation/vehicle-spy-main-menus/main-menu-setup/data-cache-disk-streaming.md).

# Data Cache Disk Streaming

Data Cache Disk Streaming provides a fast way to save large amounts of unfiltered data in a binary format (.vsb) message buffer file. This feature can be accessed using the Vehicle Spy [Setup](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-setup.md) main menu or the dropdown button next to the **Data Directory** button as shown in **Figure 1**.

![Figure 1: The dropdown button next to Data Directory can be clicked to see Data Cache selections.](https://3170208387-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL6lcovCpkhoS9uTOFtEp%2Fuploads%2FymBCnvxC1kJ11LdJJZJB%2Fspydatacache.gif?alt=media\&token=8fa21a96-5f2f-4d29-87dd-3d0f1e36c524)

To enable or disable Data Cache Disk Streaming, use the **setup dialog** checkbox or the **Data Cache On** dropdown list selection while Vehicle Spy is offline.Once enabled, all network traffic will be streamed to disk anytime Vehicle Spy is running.Data is saved in a binary format (.vsb) file in the Vehicle Spy 3\DataCache directory with a specific date and timestamp.A new data cache file is created each time Vehicle Spy transitions from offline to online while Data Cache Disk Streaming is enabled.\
\
If more advanced buffer capture features are needed then [Capture type function blocks](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-scripting-and-automation/function-blocks/function-blocks-types/capture-type-function-block.md) can be used instead.


---

# 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.intrepidcs.com/vspy-3-documentation/vehicle-spy-main-menus/main-menu-setup/data-cache-disk-streaming.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.