> 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-introduction/vehicle-spy-overview/vehicle-spy-tour/vehicle-spy-tour-1-bus-monitor.md).

# Vehicle Spy Tour 1: Bus Monitor

![Figure 1: Messages view](/files/HdS0c7hJq6xIewaJnQGC)

A bus traffic monitor is used to view messages as they appear on your network. Vehicle Spy includes two ways of displaying these messages; a static list view and a scrolling list view. You can switch between these views with just the click of a button. Each message is time-stamped and counted.

Besides allowing a view of message traffic, Vehicle Spy offers many other useful bus monitoring features. One such feature is Filtering. Filtering for messages with specific bytes is very useful because it lets you quickly focus on just the messages that you are interested in. For example, if you wanted to see only the messages from the cluster, you could filter for specific messages with ID bytes from the cluster. To make creating filters easy, filter specifications can be entered directly from a message database.

Vehicle Spy further enhances message identification by displaying message text descriptions and decoding the signals contained in messages. Color coding is also available to make messages instantly recognizable.

In bus traffic monitor applications, message buffers are typically collected and then saved. To save time, Vehicle Spy allows for automation of analysis tasks. Vehicle Spy offers useful functions such as buffer statistics and post collection filtering. Message buffers are saved as CSV (Comma Separated Value) files. These files are completely compatible with Microsoft Excel, often the tool of choice for analysis.

[**Introduction**](/vspy-3-documentation/vehicle-spy-introduction.md) **-** [**Overview**](/vspy-3-documentation/vehicle-spy-introduction/vehicle-spy-overview.md) **-** [**Applications Tour**](/vspy-3-documentation/vehicle-spy-introduction/vehicle-spy-overview/vehicle-spy-tour/vehicle-spy-tour-1-bus-monitor.md) **-** [**Users**](/vspy-3-documentation/vehicle-spy-introduction/other-vehicle-spy-users.md) **-** [**Specifications**](/vspy-3-documentation/vehicle-spy-introduction/vehicle-spy-specifications.md) **-** [**Required Hardware**](/vspy-3-documentation/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 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/vehicle-spy-introduction/vehicle-spy-overview/vehicle-spy-tour/vehicle-spy-tour-1-bus-monitor.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.