> 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.13/vehicle-network-interface-hardware/getting-started-with-neoecu/neoecu-10/neoecu-10-power-up-and-buttons.md).

# neoECU 10: Power Up and Buttons

neoECU10 has four internal buttons (Figure 1). The buttons can be used with scripts or for setting power up conditions. Table 1 shows all four Power up conditions. The purpose of the power up conditions is to set the neoECU10 to a known state when there is a problem. An example would be not knowing the baudrate stored inside of the device. Using one of the buttons for a reset, would set a default baudrate inside the device so it could be connected to program again.

To activate the condition, hold that button while powering up the unit. Once the unit has powered up, the button can be released. Holding button 3 down while powering the neoECU10 has the same function as holding pin 2 to ground while powering the neoECU10

![Figure 1: neoECU 10 Internal Switches](https://content.gitbook.com/content/jb1RvXgxzxcqgZdVpbGb/blobs/AnIZRbw8yGbyil9Cz9KZ/NE10Buttons.jpg)

**Table 1: neoECU 10 Switches Actions**

| Switch   | Description                                                                                                    |
| -------- | -------------------------------------------------------------------------------------------------------------- |
| Switch 1 | Prevents neoECU from Automatically running the CoreMini Script                                                 |
| Switch 2 | Sets application settings to default states                                                                    |
| Switch 3 | Forces neoECU into Boot-Loader Mode (This can also be done by holding Pin 2 of the 25 pin connector to ground) |
| Switch 4 | Forces neoECU into Boot-Loader mode and sets application settings to default states                            |


---

# 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.13/vehicle-network-interface-hardware/getting-started-with-neoecu/neoecu-10/neoecu-10-power-up-and-buttons.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.