> 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-sort-messages-by-ecu/part-5-setup-application-signals.md).

# Part 5 - Setup Application Signals

### 1. Setup Application Signals:

To keep things organized, save your work and start a new Vehicle Spy file. (If you do not wish to build a new file then a finished file can be opened from the Examples tab in the Logon screen called "Tutorial 4 - Part 2".)\
\
Open up the "Application Signals" view found under Scripting and Automation --> Application Signals. You can think of Application Signals as being like variables used in software programming. They can be set to different values or store different values for later use.\
\
For this tutorial we need seven Application Signals to help control Playback function blocks. Click the "+" to make a new Application Signal. Enter "60EcuTrigger" for the description. Change the Signal Type to "Digital" and set the Format to "On/Off".\
\
Repeat the previous steps for the other six ECU source IDs (10, 1A, 29, 40, 58, and 97) using the same naming convention.

![Figure 1: Adding and editing Application Signals.](https://2396693198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlRJv2XDCMeZSU0VbeZlG%2Fuploads%2Fgit-blob-251a42e5b3cb8421297e39a9e47864288b34322d%2FspyExample4Part5Pic1.jpeg?alt=media)


---

# 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-sort-messages-by-ecu/part-5-setup-application-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.