> 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-scripting-and-automation/function-blocks/function-blocks-types.md).

# Function Blocks Types

Vehicle Spy supports three types of Function Blocks:

* [Script Type](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-scripting-and-automation/function-blocks/function-blocks-types/script-type-function-block.md): Lets you write a program consisting of a set of *command steps* that control the operation of Vehicle Spy. You can use messages and signals as part of the script; for example, you could write a script to transmit a set of messages in response to receipt of an **Engine RPM** message. These are often called *function block scripts*.
* [Capture Type:](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-scripting-and-automation/function-blocks/function-blocks-types/capture-type-function-block.md) Captures messages and signals and logs them to a file, based on parameters you select. The recorded file can be used for playback, simulation or analysis. This function block type is also known as a *capture block*.
* [Playback Type](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-scripting-and-automation/function-blocks/function-blocks-types/playback-type-function-block.md): Allows a data file to be played back through hardware. This is a quick way to set up a simulation for a node or vehicle. This type of function block is also called a *playback block*.

The type of block is selected at the time it is added by clicking the ![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/function_block_toolbar_add.gif) button at the far left of the [toolbar](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-scripting-and-automation/function-blocks/function-blocks-toolbar.md). There you will see a small submenu appear, as shown in Figure 1, showing the three types. After you select the type of function block you want to create, it will be added to the [Function Block List](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-scripting-and-automation/function-blocks/function-block-list.md).

The type of function block chosen determines what is found in the setup area that comprises most of the function block window.

![Figure 1: Add Function Block submenu.](/files/8HlAwLVxm9W2i5aQql69)


---

# 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/vehicle-spy-main-menus/main-menu-scripting-and-automation/function-blocks/function-blocks-types.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.