> 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.15/vehicle-spy-tutorials/tutorial-decode-signals-from-messages/part-2-enter-a-message.md).

# Part 2 - Enter a Message

### 1. Create a Message:

Open up the **Messages Editor** panel in the main workspace using the custom tab set or by selecting **Spy Networks> Messages Editor**. Define a new **Receive message** for HS CAN by selecting **HS CAN** from the **on Network** pull down and clicking the **+ button** (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smOne.gif)).\
\
Using the **Setup** dialog, enter the following specifications:

**Description: Engine Parameters**\
**Type: Std 11 bit**\
**Arbitration ID: 110**\
**Choose Custom Color**

![Figure 1: Specifying a signal within a message.](https://2396693198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlRJv2XDCMeZSU0VbeZlG%2Fuploads%2Fgit-blob-6cbc6c68551eb54975a9761bcb8076c8821ff2e5%2Fspyexample3.2.gif?alt=media)

### 2. Create a Signal:

The lower portion of the Setup dialog contains a **Signals in Message** area. Click the **+ button** in this area to add a blank 8 bit signal specification (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smTwo.gif)).

### 3. Enter a Signal Description:

Give the signal the description **Throttle Position**. This is done by double clicking the default description (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smThree.gif)) and typing in a new description.

### 4. Set Signal Decoding:

To tell Vehicle spy how to decode this signal, the **fx Edit** button (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smFour.gif)) can be clicked to bring up the decoding options.


---

# 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.15/vehicle-spy-tutorials/tutorial-decode-signals-from-messages/part-2-enter-a-message.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.