> 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/v-one/learn-v-one/circuit-design-for-v-one/ecad-export-guides/eagle-export-guide.md).

# EAGLE Export Guide

### Gerber Export Guide

For **EAGLE v9.0.1+** users, we have a pre-configured CAM file for exporting your Gerbers:

1. Download and extract the [Voltera CAM file](https://github.com/VolteraInc/circuit-design-resources/raw/master/EAGLE%20CAM/voltera-cam.zip)
2. Open your board in EAGLE.
3. Run the **CAM Processor** - Navigate to *File > CAM Processor.*
4. Within the CAM Processor window, select *File > Open > Job*, and select the Voltera CAM file.
5. Click 'Process Job'. This will generate the Gerbers and save them in a **outputs** folder in the same directory as your .brd file.

### Design Rule Check

To ensure your circuit can be printed by the V-One. We recommend downloading the Design Rule Check file as well. This will help catch design rule errors before printing your circuit.

To use the Voltera DRC, do the following:

1. Download and extract the [Voltera DRU file](https://github.com/VolteraInc/circuit-design-resources/raw/master/EAGLE%20DRC/voltera-dru.zip)
2. Open your design in EAGLE
3. From the menu bar, click *Tools > DRC*
4. Click *Load...* and select the voltera.dru file


---

# 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/v-one/learn-v-one/circuit-design-for-v-one/ecad-export-guides/eagle-export-guide.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.