> 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/hypersim/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

* 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.

## Visualize the signals in ScopeView

{% stepper %}
{% step %}
Launch **ScopeView** from HYPERSIM.
{% 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://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-d7c2c31d42a7188ec9f6163a9703e4370e26f598%2Fimage%20(6).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 **minimum acquisition period** depends on the number of selected signals. As a rule of thumb, it is approximately the number of signals plus one FPGA clock cycle. With a **200 MHz FPGA clock**, this corresponds to about **10 ns** for one signal, **15 ns** for two, **20 ns** for three, and so on. Some signal groups can be acquired in parallel and count as a single signal. For example, all **32 signals of a digital input conditioning module** count as one signal when calculating the minimum acquisition period.

The **acquisition window length** is limited by **4 MB of available RAM**. Its maximum duration is **inversely proportional to the number of acquired signals** and **directly proportional to the acquisition period**. By default, ScopeView automatically sets the acquisition window to the maximum duration permitted for the selected signals and acquisition period. If the acquisition period is reduced, the window duration must also be reduced; conversely, if the acquisition period is increased, a longer acquisition window can be used.


---

# 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/hypersim/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.
