> 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.17/vehicle-spy-introduction/vehicle-spy-overview/vehicle-spy-tour/vehicle-spy-tour-4-node-vehicle-simulation.md).

# Vehicle Spy Tour 4: Node/Vehicle Simulation

![](https://content.gitbook.com/content/ZqysKgxMTlY1CiNX5qrT/blobs/6gAsRU89wDBZ1ErW6AAE/spyTour4NodeSim.jpg)

Node/Vehicle simulation is simulating an electronic module or car on a network. Many times a development engineer needs to develop the network software interface but has no network or car to talk to. The modules intended to communicate with may not be available at all. Using Vehicle Spy's simulation features, engineers can perform their test without those modules.

Responding to a message received is a very common task in node simulation. This means that when a module receives a specific message, it should respond with a message within a certain period of time. This response can be a function of the message received. For example, the value responded with can be the same as received with a few bits of the message received changed.

The Vehicle Spy playback feature allows vehicle traffic to be simulated. For instance, data can be collected in the car and stored. Later, this same data can be played back to a module. Captured problems can be repeated and tests can be accomplished.

Vehicle Spy is also able to generate messages periodically or when specified events occur, two more features often useful for Node/Vehicle Simulation.

[**Introduction**](https://docs.intrepidcs.com/vspy-3-documentation/3.9.17/vehicle-spy-introduction.md) **-** [**Overview**](https://docs.intrepidcs.com/vspy-3-documentation/3.9.17/vehicle-spy-introduction/vehicle-spy-overview.md) **-** [**Applications Tour**](https://docs.intrepidcs.com/vspy-3-documentation/3.9.17/vehicle-spy-introduction/vehicle-spy-overview/vehicle-spy-tour/vehicle-spy-tour-1-bus-monitor.md) **-** [**Users**](https://docs.intrepidcs.com/vspy-3-documentation/3.9.17/vehicle-spy-introduction/other-vehicle-spy-users.md) **-** [**Specifications**](https://docs.intrepidcs.com/vspy-3-documentation/3.9.17/vehicle-spy-introduction/vehicle-spy-specifications.md) **-** [**Required Hardware**](https://docs.intrepidcs.com/vspy-3-documentation/3.9.17/vehicle-spy-introduction/vehicle-spy-required-hardware-pc-system-requirements.md) **-** [**Website**](https://intrepidcs.com/products/software/vehicle-spy/vspy-float/)


---

# 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/3.9.17/vehicle-spy-introduction/vehicle-spy-overview/vehicle-spy-tour/vehicle-spy-tour-4-node-vehicle-simulation.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.
