> 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/scopeview/get-started/load-and-manage-data-sources.md).

# Load & Manage Data Sources

## Select the Data Source

ScopeView supports a wide variety of data sources and allows multiple sources to be loaded and used simultaneously.

From ScopeView **Signals** form, select **Data Source > Load...** and click the tab corresponding to the type of data source you want to load.

<figure><img src="https://1028368895-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfwfLeQP2Iaoefor0ZUNi%2Fuploads%2FwS955QViSdlH8rIEhTCU%2Fimage.png?alt=media&amp;token=541e835e-e336-455e-ac12-fc86120a9b8c" alt=""><figcaption></figcaption></figure>

### File (with pre-recorded data)

1. Select **File** from the Data Source Chooser.
2. Choose the **File Type** from the drop-down list.
3. Browse and select the file you want to load
4. Set the **File Format** according to your workstation’s operating system (PC or UNIX).
5. Click **Load** to load the File data source.

### HYPERSIM

1. Select **HYPERSIM** from the Data Source Chooser.
2. Configure the following:
   * **Host Name:** select from the pull-down menu.
   * **Display:** select from the pull-down menu.
   * **Pre-Macro / Post-Macro** (as required)
3. Click **Load** to load the HYPERSIM data source.

{% hint style="info" %}
If you launch ScopeView from HYPERSIM while a simulation is running, ScopeView automatically synchronizes with the simulation and sets HYPERSIM as the active Data Source.
{% endhint %}

### TestView

1. Select **TestView** from the Data Source Chooser.
2. Enter the project name in the **Project** text box (preceding `.prj`) or navigate via the ellipses (`...`).
3. Where applicable, select options from the following pull-downs: **Study**, **Test**, **Test No**, **Processing**, **Data**.
4. Select one of the data types: **Signals data**, **General data**, or **General sequence data**.
5. Click **Load** to load the TestView data source.

### SV61850

1. Select **SV61850** from the Data Source Chooser.
2. Choose a **Source Type**:
   * **Network Adapter:** select a network adapter from the pull-down.
   * **TCP Dump File:** enter the file name or navigate using the ellipses (`...`).
3. Click **Load** to load the SV61850 data source.

### DataLogger (configured in RT-LAB or HYPERSIM)

ScopeView supports both post-simulation and live simulation data from **DataLogger** configured in RT-LAB or HYPERSIM.

**Option 1 – Viewing Recorded Data After Simulation:**

1. Open the Data Source Chooser and select the **File** tab.
2. Select the file type according to your format.
3. Select the file and click **Load**.
4. Navigate the loaded signals as needed.

**Option 2 – Live Data Stream During Simulation:**

1. Confirm that the simulation is running on the simulator.
2. Open the Data Source Chooser and select the **DataLogger** tab
3. Enter the IP address of the simulator running the DataLogger.
4. Click **Fetch Signal Groups** to populate the **Signal Group** dropdown.
5. Select the signal group you want to monitor.
6. Click **Load** to establish the live connection.

{% hint style="info" %}
Data acquisition is frame-based. Due to hardware bandwidth limits, consecutive frames may have small blind zones. Adjust **Duration/Frame Size** to optimize data fidelity.
{% endhint %}

### FPGA scope

1. Select **FPGAScope** from the Data Source Chooser.
2. Configure the following:
   * **Target:** type your simulator's IP address and click the **Refresh** icon.
   * **Simulations:** select from the pull-down menu.
3. Click **Load** to load the HyperWorks data source.

### HyperWorks

1. Select **HyperWorks** from the Data Source Chooser.
2. Configure the following:
   * **Host Name:** select from the pull-down menu.
   * **HyWorks** selection
   * **DesignId** selection
   * **Pre-Macro / Post-Macro** (as required)
3. Click **Load** to load the HyperWorks data source.

## **Removing a Data Source**

You can remove individual sources or clear all loaded sources.

**To remove a specific source:**

1. In the **Loaded Data Source** list, select the source you want to remove.
2. Open the **Data Source** menu and click **Remove Current Data Source**.

**To remove all sources:**

* Click **Remove All** to clear the entire list.

{% hint style="danger" %}
If any formulas reference signals from a source you're removing, ScopeView will warn you.

* Confirm the removal to proceed.
* Any formulas that depended on that source will be automatically deleted from the evaluation list.
  {% endhint %}

## **Replacing a Data Source**

The **Replace** function lets you swap an existing source with another one **while keeping your formulas intact**. This is useful when you want to evaluate the same formulas using signals from a different dataset.\
The only requirement is that the new source must provide **the same list of available signals**.

**To replace a source:**

1. In the **Signals** form, open the **Data Source** menu.
2. Select the source you want to modify.
3. Click **Replace** and choose the new source.

ScopeView automatically checks whether the replacement meets the required criteria.\
If the new source is incompatible, the operation is refused and no changes are applied.


---

# 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/scopeview/get-started/load-and-manage-data-sources.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.
