> 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-request-and-save-dtc-data/part-2-create-function-block-to-request-and-save-data.md). # Part 2 - Create Function Block to Request and Save Data ### 1. Open Function Blocks View: From the main menu select **Scripting and Automation> Function Blocks**. ### 2. Create a Function Block: Click the **+ button** and select **Script** to create a new Script type function block. Change the description of the function block to something more descriptive like **Check Codes and Log Them to a File**. ### 3. Write the Script: Now a script needs to be entered. For this task 4 steps will be needed (Table 1). For **Diag Job Action** double clicking on the **Value** cell will allow selection of the diagnostic job to act on and how to act on it. For more information on this command see the help for the [Diag Job Action command](/vspy-3-documentation/3.9.15/vehicle-spy-main-menus/main-menu-scripting-and-automation/function-blocks/function-blocks-types/script-type-function-block-commands/script-type-function-block-command-diag-job-action.md). **Table 1: Script function block steps.**

Step	Command	Value	Reason for Step
1	Diag Job Action	Start Request DTCs from all nodes	Starts, or launches, the diagnostic service.
2	Diag Job Action	Wait until Complete Request DTCs from all nodes	Waits at this step until the selected diagnostic service is finished. When completed, continues to the next step.
3	Diag Job Action	Save Request DTCs from all nodes	Saves the received data and message traffic to a log file.
4	Stop	n/a	Ends this function block.

### Configure the Start Setting: On the **Start** tab select **Manual Start**. This allows the Script function block to be started using Graphical Panel controls that will be set up in the next part of this tutorial. --- # 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-request-and-save-dtc-data/part-2-create-function-block-to-request-and-save-data.md?ask=&goal= ``` `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.