> 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/get-started/run-your-integration-project/run-the-model.md).

# Run the Model

{% stepper %}
{% step %}

### Verify the configuration

1. Open the **Execution** tab and ensure that the **Real-time simulation mode** is set to **Hardware synchronized**.
2. Open the **Assignment** tab and ensure that the **XHP** box is checked (enabled).

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

{% step %}

### Load and execute the model <a href="#step-5-load-and-execute-the-model" id="step-5-load-and-execute-the-model"></a>

1. Click the **Load** button and wait for the process to complete.
2. Click **Execute**. If an **SC\_\[name]** (Subsystem Console) is present in the model, a new Simulink console window will appear. If not, double-click **Dashboards** in the **Project Explorer** to open the **Dashboards** Panel.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-8957ade8bd71f9324e40b8584d1bc86e0c495aaf%2Frtlab-load-execute-button.png?alt=media" alt=""><figcaption></figcaption></figure>

3. You can observe the signals in the Simulink or Dashboards scopes and displays.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-f76fa12feb25d9ad7ece6dc30574ed465b9e7d51%2Fproject-signals-dashboard-simulink.png?alt=media" alt=""><figcaption><p>Example of Simulink scopes and displays</p></figcaption></figure>

4. You can also use an oscilloscope to probe analog and digital outputs of the simulator.
   {% endstep %}

{% step %}

### Reset the model <a href="#step-6-reset-the-model" id="step-6-reset-the-model"></a>

Click the **Reset** button to stop the simulation and reset the model execution.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-1ded0bde6f10b118664495f8c636a6b98043c69c%2Frtlab-reset-button.png?alt=media" alt=""><figcaption></figcaption></figure>
{% 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/rt-lab/get-started/run-your-integration-project/run-the-model.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.
