> 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.11/vehicle-spy-tutorials/tutorial-simple-standalone-logging/part-6-coremini-console.md).

# Part 6 - CoreMini Console

### 1. Configure the CoreMini Console:

The CoreMini Console has a lot of information regarding the setup that is to be transferred. The output list (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smOne.gif)) will notify you of any errors or warnings. If any problems exist in the script, a red dot will be next to that item to warn you that something is wrong. The **Device** section (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smTwo.gif)) selects which of the connected hardware to send the script to. **The Run CoreMini After Download** checkbox (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smThree.gif))tells the hardware if it should run the script after it is loaded. If this is unchecked, the script will not run until the unit is re-powered. The **Send** button (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smFour.gif)) will send the script to the hardware. Remove scripts from the harware by selecting the **Clear** button (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smFive.gif)). More information on the Coremini Console can be found [here](/vspy-3-documentation/3.9.11/vehicle-spy-main-menus/main-menu-tools/utilities-coremini-console.md).

![Figure 1: CoreMini Console](https://2673726158-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdYdvinhoJh0IN6rV8uo3%2Fuploads%2FabAW3BVkB2CncANXfjnv%2FCoreMiniConsole.gif?alt=media\&token=73ae802e-d97f-4baa-a08e-1c40060cb208)

### 2. Connect to Vehicle or ECU:

The next step is to connect to a Vehicle or ECU and collect data!


---

# 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.11/vehicle-spy-tutorials/tutorial-simple-standalone-logging/part-6-coremini-console.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.