> 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/simulation-control-monitoring-and-logging/monitor-fpga-signals-with-fpga-scope.md).

# Monitor FPGA Signals with FPGA Scope

## Introduction

The **FPGA Scope** enables monitoring of high-speed signals internal to an FPGA board connected to an OPAL-RT Simulator. Signals are acquired directly on the FPGA at rates faster than the simulation step. When enabled, data is available for visualization in **ScopeView** or through **RT-LAB API**. Typically, all simulator I/O signals are available. FPGA-based controllers and solvers (e.g., **eHS**) and custom probes can also provide signals.

## Requirements <a href="#availability" id="availability"></a>

* Supported on all OPAL-RT firmware provided as an **OPBIN** file.
* If an expansion chassis is used, it must be connected to the simulator via **PCI-Express**. Connections through **SFP via MuSE** are not supported for FPGA Scope.

## Enable FPGA Scope in the S-Function workflow <a href="#enablingfpgascope" id="enablingfpgascope"></a>

{% stepper %}
{% step %}
Edit **OPcontrol** block parameters

Open the Simulink model and double-click the **OPcontrol** block to access its parameters.
{% endstep %}

{% step %}
**Select** the checkbox labeled **Enable FPGA Scope**

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-0a3f06ee587d0c53450d799c5ebb3fdc793bb790%2Fenable-fpgascope.png?alt=media" alt="" width="320"><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

## Enable FPGA Scope in the OPAL-RT Board workflow <a href="#enablingfpgascope" id="enablingfpgascope"></a>

{% stepper %}
{% step %}
Edit **OPAL-RT Board** parameters

In RT-LAB project explorer, locate your project and open its **OPAL-RT Board** I/O Interface.
{% endstep %}

{% step %}
**Select** the checkbox labeled **Enable FPGA Scope**

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-c80cf5a5fd7e7dfd4dcfeee11a2b430f5f18efce%2Fenable-fpgascope2.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

## Visualize the signals in ScopeView <a href="#visualizingsignalsinscopeview" id="visualizingsignalsinscopeview"></a>

{% stepper %}
{% step %}
Launch **ScopeView** from RT-LAB.
{% endstep %}

{% step %}
In ScopeView, load the **FPGAScope** Data Source.

1. Open the **FPGA Scope** tab.
2. Enter the simulator IP in the **Target** field.
3. Click **Refresh**, select the source, then click **Load**.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-d7c2c31d42a7188ec9f6163a9703e4370e26f598%2Ffpgascope-scopeview.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
In the signal selection interface, choose signals to visualize.
{% endstep %}

{% step %}
In the oscilloscope interface, configure trigger, acquisition period, and window size. Click **Start** to begin acquisition.
{% endstep %}
{% endstepper %}

## Acquisition period and window length

The minimal acquisition period depends on the number of signals selected. As a rule of thumb, it equals the number of signals plus one FPGA clock cycle. For example, with a 200 MHz FPGA clock, the minimal period is about 10 ns for one signal, 15 ns for two, 20 ns for three, and so on. In some cases, multiple signals can be acquired simultaneously, such as all 32 signals from a digital input conditioning module, which count as one signal in this calculation.

The acquisition window length is limited by 4 MB of RAM. Its maximum duration is inversely proportional to the number of signals and directly proportional to the acquisition period. By default, ScopeView sets the window to the maximum allowed for the selected signals and default period. If the acquisition period decreases, the window must be shortened; if the period increases, it can be lengthened.


---

# 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/simulation-control-monitoring-and-logging/monitor-fpga-signals-with-fpga-scope.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.
