> 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.12/vehicle-network-interface-hardware/getting-started-with-neoecu/neoecu-requirements.md).
# neoECU Requirements
Below are the requirements for properly using and developing with the neoECU devices.
* neoECU Device: This could be neoECU 10, neoECU 20, or other neoECU device
* Vehicle Spy 3 Pro: Vehicle Spy 3 is used to develop, test, and scripts
* Power: 6 to 26 volts to power the neoECU
If you are using a neoECU 10 or a neoECU device that is programmed over CAN, the following is also needed
* An Intrepid Control Systems CAN tool: This can be a neoVI **FIRE**, neoVI RED, ValueCAN 3, and so on. This will be used to send the Script (CoreMini) to the device. The pin out for Intrepid hardware can be found on the sticker on the box.
* Terminated CAN network: If needed this can be built. Two 120 ohm resistors can be used to terminate the network. Figure 1 shows how to make a simple CAN network that can be used to program CAN based neoECU devices.
---
# 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.12/vehicle-network-interface-hardware/getting-started-with-neoecu/neoecu-requirements.md?ask=&goal=
```
`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.