> 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-tutorials.md).

# Vehicle Spy Tutorials

Vehicle Spy tutorials have been created to make learning Vehicle Spy quick and easy. The current available tutorials are listed below.

### Basics:

* [Vehicle Spy Tutorial Files](/vspy-3-documentation/vehicle-spy-tutorials/vehicle-spy-tutorial-files.md)
* [Getting Comfortable with the User Interface](/vspy-3-documentation/vehicle-spy-tutorials/getting-comfortable-with-the-user-interface.md)
* [Tabs in the User Interface](/vspy-3-documentation/vehicle-spy-tutorials/tabs-in-the-user-interface.md)

### Tutorials:

1. [Basics of Vehicle Spy](/vspy-3-documentation/vehicle-spy-tutorials/tutorial-1-basics-of-vehicle-spy.md)
2. [Transmit Messages with Vehicle Spy](/vspy-3-documentation/vehicle-spy-tutorials/tutorial-transmit-messages-with-vehicle-spy.md)
3. [Decode Signals From Messages](/vspy-3-documentation/vehicle-spy-tutorials/tutorial-decode-signals-from-messages.md)
4. [Database Setup](/vspy-3-documentation/vehicle-spy-tutorials/tutorial-database-setup.md)
5. [Function block Capture](/vspy-3-documentation/vehicle-spy-tutorials/tutorial-basics-of-capture-function-block-and-graphical-panels.md)
6. [Function block Script and Playback](/vspy-3-documentation/vehicle-spy-tutorials/tutorial-basics-of-scripting-and-playback.md)
7. [Request and Save DTC Data](/vspy-3-documentation/vehicle-spy-tutorials/tutorial-request-and-save-dtc-data.md)
8. [DPS Programming Automation](/vspy-3-documentation/vehicle-spy-tutorials/tutorial-dps-programming-automation.md)
9. [Getting Fancy with Diagnostics](/vspy-3-documentation/vehicle-spy-tutorials/tutorial-getting-fancy-with-diagnostics.md)
10. [Sort Messages by ECU](/vspy-3-documentation/vehicle-spy-tutorials/tutorial-sort-messages-by-ecu.md)
11. [Configuring and using CoreMini](/vspy-3-documentation/vehicle-spy-tutorials/tutorial-configuring-and-using-coremini.md)
12. [Video Logging](/vspy-3-documentation/vehicle-spy-tutorials/tutorial-standalone-video-logging.md)
13. [Simple Standalone Logging](/vspy-3-documentation/vehicle-spy-tutorials/tutorial-simple-standalone-logging.md)
14. [C Code Interface Intro](/vspy-3-documentation/vehicle-spy-tutorials/tutorial-c-code-interface.md)
15. [Using Multiple Hardware Devices](/vspy-3-documentation/vehicle-spy-tutorials/tutorial-how-to-run-multiple-devices-in-one-vs3-file.md)

**\*\*Please note that each of these topics assumes the knowledge gained in the previous tutorial.**

More examples and advanced topics can be found under [Application Notes](/vspy-3-documentation/application-notes.md).


---

# 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-tutorials.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.