> 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/3.9.16/vehicle-spy-tutorials/tutorial-simple-standalone-logging.md).

# Tutorial: Simple Standalone Logging

### Overview

This example will cover the steps needed to build a simple standalone logging script. Standalone logging setups can be much more complicated if needed. This tutorial does assume that a platform or a knowledge of building receive messages with signals is known. In this example a simple pre-post capture will be walked through step by step.

### Hardware needed

**neoVI FIRE 2, ValueCAN 4 family, RAD-Gigastar, RAD-Mars etc.** Please note that this feature is currently not supported on **neoVI FIRE 3** and **neoVI RED2**; however, a future update will include support for these devices.

### Files for this example

None


---

# 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/3.9.16/vehicle-spy-tutorials/tutorial-simple-standalone-logging.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.