> 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/vehicle-spy-main-menus/main-menu-measurement/graphical-panels/graphical-panels-tools/graphical-panel-controls-function-block-button.md).

# Graphical Panel Controls: Function Block Button

The Function Block button provides the ability to control [Function Block](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-scripting-and-automation/function-blocks.md) scripts from a graphical panel. Function blocks can be started, stopped, triggered ([capture-type function blocks only](/vspy-3-documentation/vehicle-spy-tutorials/tutorial-sort-messages-by-ecu/part-3-setup-capture-type-function-blocks.md)), or instructed to save their collected data (again, capture blocks only).

![Figure 1: An example Function Block control.](https://3170208387-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL6lcovCpkhoS9uTOFtEp%2Fuploads%2F59t1qmfBf0wxjB1TrR7F%2FgpctrlFBButton.gif?alt=media\&token=7a7869a2-00e1-47ef-85e2-b2b2f23f8aff)

Table 1 lists the special properties associated with Function Block controls. A list of common properties can be found under [Common Control Properties](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-measurement/graphical-panels/graphical-panels-tools/graphical-panel-controls-common-control-properties.md).

**Table 1: Function Block Control Properties**

| Property      | Function and Options                                                                                                                                                                                                                                                        |
| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| OnText        | The text shown when the button is pushed in or held down (**On** state).                                                                                                                                                                                                    |
| OffText       | The text string shown when the button is up (**Off** state).                                                                                                                                                                                                                |
| FBlockAction  | <p>Sets the action to be taken by the function block when the button is pressed:</p><ul><li><strong>0-Start</strong></li><li><strong>1-Trigger</strong></li><li><strong>2-Stop</strong> (capture block only)</li><li><strong>3-Save</strong> (capture block only)</li></ul> |
| FunctionBlock | The function block associated with this control; clicking in this field will cause a list of all available function blocks in the setup to be presented in a drop-down box.                                                                                                 |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.intrepidcs.com/vspy-3-documentation/vehicle-spy-main-menus/main-menu-measurement/graphical-panels/graphical-panels-tools/graphical-panel-controls-function-block-button.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.