> 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-main-menus/main-menu-scripting-and-automation/c-code-interface/c-code-interface-functions-and-events/functions-and-events-application-signals.md).

# Functions and Events: Application Signals

[Application signals](/vspy-3-documentation/3.9.15/vehicle-spy-main-menus/main-menu-scripting-and-automation/application-signals.md) are variables used in Vehicle Spy to share data between various objects in Vehicle Spy. [Function Block scripts](/vspy-3-documentation/3.9.15/vehicle-spy-main-menus/main-menu-scripting-and-automation/function-blocks/function-blocks-types/script-type-function-block.md) and [Graphical Panels](/vspy-3-documentation/3.9.15/vehicle-spy-main-menus/main-menu-measurement/graphical-panels.md) can use these variables as well. The C Code Interface has support for accessing and changing these values. All application signals defined in your vs3 file have a set function, a get function, and an optional event function. The set and get functions set either a number, normal text, or unicode (wide text). All application signals start with the "AS\_" prefix.

![Figure 1: Application Signal Functions allow you to interact with app signals.](https://2396693198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlRJv2XDCMeZSU0VbeZlG%2Fuploads%2Fgit-blob-be63312730f600419734c3c46f727ce7cd005a8c%2Fappsignal_functions.gif?alt=media)

For the event function, you can add these to your project setup by selecting the "Application Signal Events" tab in the C Code Module Setup as shown in Figure 2. Here, you can select any of the application signals for an event. This means Vehicle Spy will automatically call these functions when the application signal changes. Make sure to not use the \_Set function of the application signal in the change event to avoid a cascading situation.

![Figure 2: Application Signal Events are called whenever an application signal changes](https://2396693198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlRJv2XDCMeZSU0VbeZlG%2Fuploads%2Fgit-blob-f8b3649e8802c342efe7d43823b9d6cad0b15f6a%2Fappsignal_event.gif?alt=media)

![Figure 3: The event for an application signal passes the value back as a double.](https://2396693198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlRJv2XDCMeZSU0VbeZlG%2Fuploads%2Fgit-blob-9e31a35ed74d224402831919d7d46f769ef99573%2Fappsignal_event_code.gif?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-main-menus/main-menu-scripting-and-automation/c-code-interface/c-code-interface-functions-and-events/functions-and-events-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.