> 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/rt-lab/configure-ios/analog-digital-and-sfp-ios/opal-rt-board-workflow/opal-rt-board-configuration.md).

# OPAL-RT Board Configuration

### OPAL-RT Board general section

In the **Folders** list, click **General** to configure the general settings.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-c0eeb9dca68bcb8c3b46fbe0cdcb827d7d088960%2FDR-add-opal-board.png?alt=media" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="165">Parameter</th><th>Value (Description)</th></tr></thead><tbody><tr><td><strong>Chassis type</strong></td><td><p>Selects the chassis used for the simulation.</p><p>When <strong>OP4810</strong> or <strong>OP4815</strong> is selected, two additional parameter must be configured:</p><ul><li><strong>IP address:</strong> IP address displayed on the chassis LCD screen. Press the <strong>menu</strong> button on the unit to navigate to the <strong>ID page</strong>. Required to allow bitstream programming.</li><li><strong>Chassis name:</strong> Custom name displayed on the chassis LCD screen. Press the <strong>menu</strong> button on the unit to navigate to the <strong>ID page</strong>.</li></ul></td></tr><tr><td><strong>Chassis ID</strong></td><td>Identifier of the selected FPGA board used in the simulation. Refer to your <strong>System Description Document</strong>.</td></tr><tr><td><strong>Use external synchronization source</strong></td><td><p><strong>Checked:</strong> The FPGA board uses an external synchronization source instead of its internal clock. Two additional parameter must be configured:</p><ul><li><strong>Operate as hardware synchronization source:</strong> When <strong>checked</strong>, the FPGA synchronizes the simulation using the external clock (master with external clock). When <strong>unchecked</strong>, the FPGA uses the external clock but does not drive the simulation (slave mode).</li><li><strong>Type of expected synchronization signal:</strong> Select the synchronization medium: <strong>Copper</strong> or <strong>Optical</strong>.</li></ul><p><strong>Unchecked:</strong> The FPGA board internal clock is used. The following parameter must be configured:</p><ul><li><strong>Type of generated synchronization signal:</strong> Select where the FPGA outputs its synchronization pulse: <strong>Optical</strong> or <strong>Audio</strong>.</li></ul></td></tr><tr><td><strong>Bitstream configuration location</strong></td><td>Selects how the configuration file is chosen:<br>• <strong>File system</strong> (browse using Windows File Explorer)<br>• <strong>Standard repositories</strong> (preinstalled OPAL‑RT configurations)</td></tr><tr><td><strong>Bitstream configuration file</strong></td><td><strong>File system:</strong> Browse to a configuration file.<br><strong>Standard repositories:</strong> Select from a drop‑down list.<br>File format must be <code>[board_type]_[file_name].opal</code> or <code>.opbin</code> (e.g., <code>VC707_Config1.opal</code>).</td></tr><tr><td><strong>Bitstream file name</strong></td><td>Read‑only field showing the detected bitstream file associated with the selected configuration.</td></tr><tr><td><strong>Show advanced configuration</strong></td><td><p><strong>Checked:</strong> Advanced configuration parameters are displayed:</p><ul><li><strong>Time step factor:</strong> Multiplier defining the FPGA board speed relative to the model’s timestep.</li><li><strong>Enable FPGA register logger:</strong> When <strong>checked,</strong> all FPGA register accesses during model initialization and reset are logged in files <code>register_trace*</code>. These files are retrieved on the workstation after reset. When <strong>unchecked</strong>, register accesses are not logged.</li></ul><p><strong>Unchecked:</strong> Advanced parameters are hidden.</p></td></tr><tr><td><strong>Automatic bitstream reprogramming</strong></td><td><strong>Checked:</strong> Bitstream programming is automatically triggered when the model is loaded. If the currently programmed bitstream matches the expected one, it is reloaded.<br><strong>Unchecked:</strong> No automatic programming or reload occurs.</td></tr><tr><td><strong>Force</strong></td><td><strong>Checked:</strong> Forces bitstream programming even if the same bitstream is already programmed on the board.<br><strong>Unchecked:</strong> Programming is skipped if the same bitstream is detected.</td></tr><tr><td><strong>Disable strict hardware mismatch validation</strong></td><td><strong>Checked:</strong> Allows the use of multiple I/O module types based on general compatibility rules instead of exact hardware ID matching.<br><strong>Unchecked:</strong> Exact hardware ID validation is enforced.</td></tr><tr><td><strong>Enable FPGA Scope</strong></td><td><em>Option visible only if supported by the selected bitstream configuration.</em><br><strong>Checked:</strong> FPGA Scope is available when the model is executed.<br><strong>Unchecked:</strong> FPGA Scope is not available.</td></tr><tr><td><strong>Enable virtual mode</strong></td><td><strong>Checked:</strong> The model can execute even if the I/O interface is incompatible with the physical hardware. Connections are initialized, but no hardware I/O is performed. Useful for troubleshooting, development, or model preparation without target hardware.<br><strong>Unchecked:</strong> Hardware compatibility is required for execution.</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/rt-lab/configure-ios/analog-digital-and-sfp-ios/opal-rt-board-workflow/opal-rt-board-configuration.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.
