> For the complete documentation index, see [llms.txt](https://docs.voltera.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.voltera.io/docs/nova/getting-started/nova-user-manual/4.-hardware-overview-and-network-capabilities.md).

# 4. Hardware overview and network capabilities

NOVA is a precision dispensing platform for additive electronics. NOVA’s software independently runs on its own standalone compute module, the NVIDIA Jetson Nano. The Nano module integrates a Realtek RTL81119ICG Gigabit Ethernet controller. To connect the Nano module to the Internet, a Wi-Fi adapter or an Ethernet cable must be plugged into NOVA.

The Wi-Fi adapter that is shipped with NOVA is a TP-link AC600 Nano Wireless USB Adapter. A different Wi-Fi adapter can be used instead of the one provided by Voltera if desired, but Voltera cannot guarantee it will be compatible with NOVA’s system.

NOVA receives commands from users through a browser-based web app. A network connection, whether local or on the Internet, is required between NOVA and a computer for operation. Various connection methods are detailed in sections 3.3-3.6.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.voltera.io/docs/nova/getting-started/nova-user-manual/4.-hardware-overview-and-network-capabilities.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.