> 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.13/vehicle-spy-tutorials/tutorial-1-basics-of-vehicle-spy/part-3-examine-messages.md).

# Part 3 - Examine Messages

The Messages view can be set up to display precisely what needs to be seen. It can be customized for any need and can display specific messages in message traffic. In the next couple steps a basic message specification will be set up. This is a good place to begin exploring Vehicle Spy's filtering capabilities.

### 1. Switch to Messages Editor View:

From the Menu Bar select **Spy Networks > Messages Editor**. The panel in the main workspace changes from the **Messages** view to the **Messages Editor** view.

![Figure 1: Building a receive message with the Messages Editor.](/files/lis66q66j4rLSDU1dzTz)

### 2. Create a New Message Specification:

For this exercise specify a received High Speed CAN message. Select **HS CAN** from the **Network** dropdown (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smOne.gif)) and check that the **Receive** tab (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smTwo.gif)) is selected. Now click the **+ button** (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smThree.gif)) at the top of the panel to create a new message specification. (Specifications can be removed just as easily. With Vehicle Spy stopped, simply select the row to be removed and click the **- button** (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smThree.gif)).) We will define our new specification using the Setup dialog.

### 3. Enter Module Message in the Description Field:

Attach a description to the message. Label it **Module Message** inside the **Description** field (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smFour.gif)) in the Setup dialog.

### 4. Enter an Arbitration ID of 110:

Now enter an arbitration ID of 110 into the **Arb ID** field (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smFive.gif)). This attaches the "Module Message" description to messages with Arb ID 110.

### 5. Give the Message a Color:

With so many messages flying by, custom colors make instant visual identification possible. Select the **Color** dropdown field (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smSix.gif)) and choose desired color.

### 6. Examine Completed Message:

Examine message in the grid portion of the Messages Editor panel (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smSeven.gif)). All the specifications entered in the Setup dialog are automatically added to the spreadsheet. Make sure message looks exactly like the one found above in **Figure 1**. (For a more complete explanation of the options found in the Setup dialog, please [click here](/vspy-3-documentation/3.9.13/vehicle-spy-main-menus/main-menu-spy-networks/message-editor.md).)\
\
\&#xNAN;**\*Note:** Depending on preference, message information such as Description or Arb ID can be entered directly into the grid or in the Setup dialog. The changes made in one area will also occur in the other.


---

# 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:

```
GET https://docs.intrepidcs.com/vspy-3-documentation/3.9.13/vehicle-spy-tutorials/tutorial-1-basics-of-vehicle-spy/part-3-examine-messages.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.