> 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.19/vehicle-spy-main-menus/main-menu-embedded-tools/intrepid-ecu-flasher-definitions.md).

# Intrepid ECU Flasher: Definitions

![](/files/XTCz2ritu6JL6EEqnvRc)

### Transfer Action

The Transfer action is used to transmit data from an Intel HEX, S19, or VBF file. These file formats will contain multiple sectors, or contiguous blocks, of binary data. The ECU flasher can transfer sectors of data to the ECU and can also run Actions before any sector transfer happens, or it can run Actions before and/or after each sector in the associated file is run. The execution of the Transfer action follows the steps below:

* Execute 'before\_transfer\_for\_each\_sector'
* For each sector in the file:
  * keywords 'SECTOR\_ADDR' and 'SECTOR\_LEN' are updated for this sector
  * Execute 'before\_sector\_action'
  * Execute 'Request Download' job
  * Execute 'Multiple Transfer Data' job to transmit data
  * Execute 'after\_sector\_action'
* end

| TRANSFER                                    |                                                                                    |
| ------------------------------------------- | ---------------------------------------------------------------------------------- |
| File                                        | File path to the Intel HEX or S19 file.                                            |
| before\_transfer\_for\_each\_sector\_action | Action to be performed at the start of the transfer action. This only occurs once. |
| before\_sector\_action                      | Action to be performed prior to each sector request download / transfer data       |
| after\_sector\_action                       | Action to be performed after each sector request download / transfer data          |

### Transmit Action

The Transmit Action transmits an arbitrary message. This functions differently from calling a diagnostic job in that it will only transmit the defined message. Once the message is transmitted, execution immediately moves on to the next step.

| TRANSMIT |                                                                                             |
| -------- | ------------------------------------------------------------------------------------------- |
| ID       | The ARB ID for the Transmit Message. This value is in Hexidecimal.                          |
| Bytes    | The bytes that should be transmitted. This works as described under Funtional Job => Bytes. |


---

# 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:

```
GET https://docs.intrepidcs.com/vspy-3-documentation/3.9.19/vehicle-spy-main-menus/main-menu-embedded-tools/intrepid-ecu-flasher-definitions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.