> 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/application-notes/application-note-neovi-logging-neoecu-daq.md).

# Application Note: neoVI Logging neoECU DAQ

### Introduction:

This application note will go over how to use a neoECU 10's analog inputs and send the data over HS CAN to a neoVI **FIRE**. The neoVI **FIRE** will record the data via standalone mode using CoreMini. In this example a neoECU 10 will be used, but with a few changes, any neoECU device can be used.

### Files To Reference For This Example:

Included in this [AppNeoECULogging.zip](https://cdn.intrepidcs.net/support/VehicleSpy/AppneoECUlogging.zip) file:

1. ECUCoreMini.vs3
2. FIRELogging.vs3

### Hardware Required:

1. neoECU
2. neoVI capable of standalone mode.


---

# 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/application-notes/application-note-neovi-logging-neoecu-daq.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.
