> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/pe-add-on-opal-rt/system-definition-configuration/configure-the-hardware-fpga.md).

# Configure the Hardware (FPGA)

## Overview

The **Hardware Configuration section** is populated with one or more subsections named **FPGAx**, depending on the number of FPGAs targeted. One **FPGA** **Section** is added to the configuration tree for each available FPGA board in a Circuit Model.

In the **System Explorer** window configuration tree, expand the **Power Electronics Add-On** custom device and select **Hardware Configuration >>** **FPGAxx** to display this page and configure the FPGA board properties. The available configuration options are defined by the capabilities of the FPGA hardware, as summarized in the table below.

<figure><img src="https://1300141755-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCyfrFRdgX5VC5iwM13Zm%2Fuploads%2FlfYfUgcLcxtmj8aKWCY5%2Fimage.png?alt=media&amp;token=447b6338-c616-477f-9af4-9f081a9acb1f" alt=""><figcaption></figcaption></figure>

The **FPGA*****X*** sections are further separated into subsections representing **digital I/O** channels they support.

{% hint style="danger" %}
**Analog I/O** are defined only in the **Schematic Editor**.
{% endhint %}

## Parameters

<table><thead><tr><th width="180.22222900390625">Parameter</th><th width="430.5555419921875">Description</th><th>Supported Hardware</th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>Displays the name of the FPGA target onto which the device settings will be applied. This name and the name of the targeted FPGA board in the NI Measurement and Automation Explorer must match each other exactly.</td><td>PXIe-7891</td></tr><tr><td><strong>Description</strong></td><td>Displays a description of the features included in the selected hardware configuration. For more detailed information about a configuration, refer to <a href="https://www.opal-rt.com/docs/pe-add-on-opal-rt/hardware-configurations-reference/default-hardware-configuration-fpga-firmwares.md"><strong>Default Hardware Configurations</strong></a></td><td>PXIe-7891</td></tr><tr><td><strong>DIO Line Voltage</strong></td><td>Specifies the digital I/O line voltage level for each connector on the FPGA board. The available options are defined by the supported voltage levels of the targeted FPGA board.</td><td>PXIe-7891</td></tr><tr><td><strong>Direction</strong></td><td><p>Specifies the line direction of the digital channel. Each channel can be configured as an <strong>Input</strong> or an <strong>Output</strong> to the real time target.</p><p>Modifying the line directions of digital channels will affect the distribution of those channels between the <strong>Digital Input</strong> and <strong>Digital Output</strong> sections. Other sections with Digital I/O mapping options, such as the <strong>Gates</strong>, may also be affected.</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>It is recommended to review all custom device mappings after making changes to digital channel directions.</p></div></td><td>PXIe-7891</td></tr></tbody></table>


---

# 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://www.opal-rt.com/docs/pe-add-on-opal-rt/system-definition-configuration/configure-the-hardware-fpga.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.
