> 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-main-menus/main-menu-spy-networks/message-editor/message-signals.md).

# Message Signals

Vehicle network messages contain raw data with signal information. Vehicle Spy allows decoding of this signal information from received messages and encodes this information into transmit messages. Signal definitions must always be associated with a message.

**Figure 1** shows the **Signals In Message** area, located near the bottom of the [Messages Editor](/vspy-3-documentation/3.9.17/vehicle-spy-main-menus/main-menu-spy-networks/message-editor.md). Signals in the selected message can be seen and changed here. Click the **+ or - buttons** (Figure 1: ![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smOne.gif)) to add or remove signals in a message. The **+** button defaults to adding a signal that is 8 bits long. Using the pull down next to the **+** button 1 bit signals, 8 bit signals, 16 bit signals, 32 bit signals, 64 bit signals, and 128 bit signals can be chosen to add.

Every signal in the message has a row showing its Description and Type. To edit the signal name, double click on it and type a new one. To change the [signal type](/vspy-3-documentation/3.9.17/vehicle-spy-main-menus/main-menu-spy-networks/message-editor/message-signals/message-signal-type.md), click its Type cell and use the pulldown list.

Blue colored cells in each row represent the signal's bit length and bit position within the message. Signal position can be adjusted (Figure 1: ![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smTwo.gif)) by dragging the signal back and forth along the row. Signal length can be changed in a similar way by dragging on either edge of the signal (Figure 1: ![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smThree.gif)). The blue bits turn brown while the signal position or length are being dragged.

The click & drag feature for the blue signal bits is limited to 64 bytes. Signal position or length that goes beyond 64 bytes must be specified using the Edit Signal dialog. To open the Edit Signal dialog, click the **fx Edit** button (Figure 1: ![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smFour.gif)) or double click on the blue signal bits. Use [Live Edit](/vspy-3-documentation/3.9.17/vehicle-spy-main-menus/main-menu-spy-networks/message-editor/message-signals/live-edit.md) (Figure 1: ![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smFive.gif)) to see raw data and decoded signals within the signal editor itself while Vehicle Spy is online.

![Figure 1: Use the Signals in Message area near the bottom of the Messages Editor to edit signal information.](https://content.gitbook.com/content/ZqysKgxMTlY1CiNX5qrT/blobs/H6roXPxFuSHsNAmYwLMc/spyindecode.png)

As signals are moved around and change their lengths the colors will change near the top where the bit numbers are shown (Figure 2). The colors can quickly help show conflicts that may require further attention.

![Figure 2: Use these colors to help you avoid mistakes while editing message signals.](https://content.gitbook.com/content/ZqysKgxMTlY1CiNX5qrT/blobs/0Ul0k2RtnCrGpDSnWyPF/spyindecode2.gif)

Refer to **Table 1** to see what each color indicates.

**Table 1: Signal Editor Color Coding**

| Color  | Condition          | Details                                                                                                                                                                               |
| ------ | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Gray   | Unused bit.        | Bits are undefined.                                                                                                                                                                   |
| Green  | No conflicts.      | Bits defined by 1 signal equation.                                                                                                                                                    |
| Yellow | Possible conflict. | Bits defined by 2 or more signal equations.                                                                                                                                           |
| Purple | Defined in table.  | Bits defined by [Message Data Bytes](/vspy-3-documentation/3.9.17/vehicle-spy-main-menus/main-menu-spy-networks/message-editor/messages-editor-message-fields/message-data-bytes.md). |
| Red    | Conflict.          | Bits defined by equation and Message Data Bytes.                                                                                                                                      |

Some signal types have unique characteristics that become clear while using the signal editor grid. [Digital](/vspy-3-documentation/3.9.17/vehicle-spy-main-menus/main-menu-spy-networks/message-editor/message-signals/message-signal-type-digital.md) signals are 1 bit long. [Text](/vspy-3-documentation/3.9.17/vehicle-spy-main-menus/main-menu-spy-networks/message-editor/message-signals/message-signal-type-text.md) signals are a multiple of 8 bits long and byte aligned. [DTC](/vspy-3-documentation/3.9.17/vehicle-spy-main-menus/main-menu-spy-networks/message-editor/message-signals/message-signal-type-dtc.md) signals are 16 bits long and byte aligned.

Other signal parameters like [analog value type](/vspy-3-documentation/3.9.17/vehicle-spy-main-menus/main-menu-spy-networks/message-editor/message-signals/message-signal-type-analog.md), [state table values](/vspy-3-documentation/3.9.17/vehicle-spy-main-menus/main-menu-spy-networks/message-editor/message-signals/message-signal-type-state-encoded.md), endianness, [format](/vspy-3-documentation/3.9.17/vehicle-spy-main-menus/main-menu-spy-networks/message-editor/message-signals/message-signal-format-and-units.md), min, max, [units](/vspy-3-documentation/3.9.17/vehicle-spy-main-menus/main-menu-spy-networks/message-editor/message-signals/message-signal-format-and-units.md), scaling, and J1939 settings can also be edited. Double click on the blue signal bits or press the **fx Edit** button (Figure 1: ![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smFour.gif)) to open the Edit Signal dialog customized to the selected signal type.


---

# 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.17/vehicle-spy-main-menus/main-menu-spy-networks/message-editor/message-signals.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.