> 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.16/vehicle-spy-main-menus/main-menu-setup/ecus-view/ecu-a2l-import-options.md).
# ECU A2L Import Options
This dialog allows the user to fine-tune the import of an A2L file into a new or existing ECU.
ECU A2L dialog box
* **The title bar** (Figure 1:) indicates what is happening. Here you will see if you're importing an A2L into an exsiting ECU, or if you are creating a new ECU.
* **A2L Location**: the full path to the A2L file you want to import. Click the elipsis (...) button to open a file picker dialog. (Figure 1:)
* **Load CHARACTERISTIC items** (Figure 1:) **checkbox**: Check this box if you want to import CHARACTERISTIC data elements from the A2L file as well as MEASUREMENT data elements. CHARACTERISTIC data elements are typically multi-dimensional values that are used for calibration, while MEASUREMENT data elements are typically intended for data acquisition. This setting will be remembered for future imports.
* **Expand arrays** (Figure 1:) **checkbox**: Check this box if you want to expand arrays or MATRIX data elements from the A2L file. If there was a MEASUREMENT data element that was specified as a MATRIX with 1000 items, checking this box would create 1000 individual items for data collection. With the box unchecked, only the first element will be created. This is a way to reduce the size of the channels list if you have a lot of array-type items that you're not interested in. This setting will be remembered for future imports.
---
# 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.16/vehicle-spy-main-menus/main-menu-setup/ecus-view/ecu-a2l-import-options.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.
