> 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/application-notes/application-note-vehiclescape-standalone-logging/application-note-vehiclescape-standalone-logging-part-4-neovi-mote-setup.md).

# Application Note: VehicleScape Standalone Logging - Part 4: neoVI MOTE Setup

### 1. Open the CoreMini Console:

Once you have completed the setup for the Logger, go to the CoreMini Console using the Generate button in VehicleScape DAQ or through Tool --> Utilities --> CoreMini Console. 

### 2. Send the CoreMini to the neoVI MOTE:

Figure 1 shows the CoreMini Executable Generator.  Click on the neoECU (CAN) tab (Figure 1: ![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smOne.gif)). With a neoVI or ValueCAN device connected to the neoVI MOTE, click on the to program the neoECU/neoVI MOTE connected.  You will now need to locate the neoECU/neoVI MOTE by clicking the "Poll for neoECUs" button (Figure 1: ![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smTwo.gif)).  Make sure that you have the correct network selected to the left of this button.  If you are using the provided cable with the OBD-II to 25 Pin with 9 Pin offshoot you will choose HS CAN 3 from this drop down.  Next, set the CoreMini to Download to be Logger CoreMini.  On the bottom left you will find the "Send" (Figure 1: ![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smThree.gif)). Click this button when you are ready to send the CoreMini to the device.  If you wish to erase the CoreMini from the device later you may do so by pressing "Clear" ![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smFour.gif).

![Figure 1: CoreMini Console](/files/WhcsKChylaVXesCAULMl)


---

# 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/application-notes/application-note-vehiclescape-standalone-logging/application-note-vehiclescape-standalone-logging-part-4-neovi-mote-setup.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.