> 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/basic-operation-of-vehicle-spy.md).

# Basic Operation of Vehicle Spy

### Overview

Vehicle Spy is a vehicle network tool. As such, it can read and transmit messages on a vehicle network. In Vehicle Spy, messages that are received are grouped into the Receive table in [Messages Editor](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-spy-networks/message-editor.md) view. Messages that are transmitted are called Transmit Messages. These messages are grouped into the Transmit table in Messages Editor view. Transmit messages are also displayed and transmitted from the [Transmit Panel](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-spy-networks/transmit-panel.md). Messages, whether transmitted or received, are defined as a collection of bytes which encode some type of data (called a signal) and have an identifier.\
\
For the purposes of working with multiple network vehicles, Vehicle Spy can function on more than one network. [Networks](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-spy-networks/networks.md) can be setup for a specific protocol and attached to a vehicle [Network Hardware interface](/vspy-3-documentation/vehicle-network-interface-hardware.md).\
\
Each vehicle network contains a collection of nodes or ECUs. ECUs (Electronic Control Units) act as a source or receiver of messages. Vehicle Spy allows you to assign ECU specifications to messages and signals. This lets you analyze your network based on ECUs.\
\
Vehicle Spy offers many ways in which to view vehicle network data. The first is [Messages view](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-spy-networks/messages-view.md). This view allows you to see the message traffic as it appears on the bus (scrolling mode) or as a stationary list of messages with changing data bytes (static mode).Messages displayed in Messages view are collected in a circular buffer. Vehicle Spy also contains an exciting feature called [Graphical Panels](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-measurement/graphical-panels.md) view. With Graphical Panels, users can easily create their own virtual instrument panels. These panels can include meters, graphs, LEDs and numerous other elements for visually representing data.\
\
[Function Blocks](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-scripting-and-automation/function-blocks.md) are another powerful feature found within Vehicle Spy. This feature gives users custom control over Vehicle Spy. Function Blocks support custom scripting, buffer capturing with pre/post triggering, and replaying messages.


---

# 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/basic-operation-of-vehicle-spy.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.