> 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/mep-xcp-ccp-memory-edit-protocol/mep-setup/mep-setup-daq-tables.md).

# MEP Setup - DAQ Tables

The [MEP Setup](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-measurement/mep-xcp-ccp-memory-edit-protocol/mep-setup.md) DAQ Tables tab (Figure 1) displays information about [event based data acquisition](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-measurement/mep-xcp-ccp-memory-edit-protocol/data-acquisition-with-ccp-xcp.md) with CCP/XCP. ECUs with CCP/XCP have the option to use events and DAQ lists to organize and report their data. Event based DAQ'ing can help synchronize ECU measurements and free up its resources for other activities.

Each ECU event can trigger multiple DAQ lists.\
Each DAQ list can have multiple ODTs (Object Descriptor Tables).\
Each ODT can have multiple [A2L file data items](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-measurement/mep-xcp-ccp-memory-edit-protocol/mep-setup.md#a2l-file-data-item-tree-refer-to-figure-1), also known as elements.

![Figure 1: The MEP Setup DAQ Tables tab displays information regarding event based DAQ'ing.](/files/CE5G8NwwfqfYO1eaRfGc)

The DAQ Tables tab will show information after Vehicle Spy goes online in MEP mode with an ECU while VehicleScape DAQ has at least one A2L file data item assigned to an event. Refer to Table 1 to help understand the information shown in the DAQ Tables area.

**Table 1: MEP Setup DAQ Tables Items**

| DAQ Tables Item   | Description                                                          |
| ----------------- | -------------------------------------------------------------------- |
| DAQ\_#            | ECU DAQ list number. (not the VehicleScape DAQ session name)         |
| \_FirstPID        | Number assigned to the first ODT in this DAQ list.                   |
| \_Event           | Event number that this DAQ list is part of. (-1 if not assigned)     |
| \_Full            | 0 false/1 true. True if this DAQ list is full.                       |
| \_HasItems        | 0 false/1 true. True if this DAQ list has any data items.            |
| \_Size            | Maximum number of ODTs in this DAQ list.                             |
|                   |                                                                      |
| ODT\_#            | Object Descriptor Table number within this DAQ list.                 |
| \_ELM\_#          | Element number of item within this ODT.                              |
| For each element: | A2L data file item name, memory start address, memory size in 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, and the optional `goal` query parameter:

```
GET https://docs.intrepidcs.com/vspy-3-documentation/vehicle-spy-main-menus/main-menu-measurement/mep-xcp-ccp-memory-edit-protocol/mep-setup/mep-setup-daq-tables.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.