> 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/application-notes/sample-replay-files.md).

# Sample Replay Files

Below are links to files that were collected from an automobile or module subsystem. These files can be used to simulate bus traffic.

\*\*Note: You can replay any buffer you collect with Vehicle Spy; these are included here for your convenience.

To use these files, you must first save them to disk. To save, follow the steps listed below:

1. For Internet Explorer users, right click the link below and select "Save Target As..". For help users click the link.
2. Next a dialog will appear. Select to save it to your hard disk.
3. To replay the file, open Vehicle Spy, click on the Tools menu and then Options. In the window that opens, click on the Browse button and locate the replay file on your PC. Make sure the "Simulation Mode" check box is checked. Then start Vehicle Spy. (Notice that bus hardware setup can be done in this same window too.)

### Replay Files

[All Bus Traffic.csv](https://cdn.intrepidcs.net/support/VehicleSpy/All%20Bus%20Traffic.csv) - Messages from three CAN networks, both J1850s, and Keyword 2000


---

# 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.intrepidcs.com/vspy-3-documentation/application-notes/sample-replay-files.md?ask=<question>&goal=<endgoal>
```

`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.