> 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/interact-using-dashboards/synchronize-with-hypersim.md).

# Synchronize with HYPERSIM

To ensure that **OPAL-RT Dashboards** functions correctly with a target running **OPAL-RTLinux 3**, verify in **Target Manager** that the **Network Configuration** for the target is **not set to Automatic**.

Instead, configure either:

* A **fixed IP address**, or
* A specific **network interface**.

This configuration is required to ensure reliable communication between the **OPAL-RT Dashboards data acquisition services** and the **simulator** running on the target. Automatic network configuration may prevent the proper establishment of these communication channels.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-69b5f4773b2ca4aba38d45fc9d104008c7f1338c%2FDH-taget-manager.png?alt=media" alt=""><figcaption></figcaption></figure>

## Prepare the model

{% stepper %}
{% step %}

### Analyze

A **first analysis must be performed in HYPERSIM** before data points become available in the model table. Once the analysis is complete, all model parameters, along with the **selected inputs and outputs**, are accessible from **OPAL-RT Dashboards**.

As with any model modification, if blocks are added or removed, or if the network topology is changed, the model must be **reanalyzed** for the updates to be reflected in Dashboards.
{% endstep %}

{% step %}

### Synchronize

Parameter values can be edited in HYPERSIM and Dashboards.

**Changes made in Dashboards are automatically applied to HYPERSIM whenever the entered values are valid.**

However, changes made directly to parameter values in **HYPERSIM** are not automatically reflected in **Dashboards**. To synchronize the displayed values, a **manual refresh (fetch)** must be performed in Dashboards.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-d00256c4f7932045b2fb8817a78a95b5625aeb33%2FDH-synchronize-hypersim.png?alt=media" alt=""><figcaption></figcaption></figure>

The simulation status is displayed next to the model name. If the automatic synchronization does not update the status correctly, click **Fetch Data** to refresh it manually.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-3bdba5bfa4c3a7aa00f45bcf1c3a653fdec63d04%2FDH-hypersim-status.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Add sensors

In **OPAL-RT Dashboards**, HYPERSIM sensors are exposed as **Inputs** and **Outputs**.

To add a sensor, open the parameter dialog of the desired block in HYPERSIM and navigate to the **Sensors** section. Select the required sensor(s), then apply the changes.

{% hint style="info" %}
Currently, only **output sensors** can be exposed in Dashboards.
{% endhint %}

Once enabled, the sensors appear in the **Model Table** under **Outputs** and can be connected to visualization widgets, such as displays, gauges, charts, and trends.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-27f39303a96645175f9aab4a3f232760fb4bb704%2FDH-sensor-HYPERSIM.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Run the simulation

The **Simulation** menu is located in the upper-right corner of the interface. Click the menu to open a dropdown panel that lets you monitor and control the simulation status of each model in your project.

The menu provides regular status updates, allowing you to quickly determine whether a model is:

* **Waiting to load**
* **Running**
* **Waiting to stop**
* **Stopped**

These real-time updates help you track simulation progress and manage multiple models efficiently.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-1a1e96cb615d4b21000d756221748937142d98eb%2FDH-simulation-controlhypersim.png?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Changes made during a simulation** are automatically sync and saved with HYPERSIM.
{% endhint %}
{% endstep %}
{% endstepper %}


---

# 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/interact-using-dashboards/synchronize-with-hypersim.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.
