> 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/hyperlab/simulation-control-monitoring-and-logging/interacting-with-the-simulation/connecting-block-parameters-and-signals-with-widgets.md).

# Connecting Block Parameters & Signals with Widgets

Block parameters & signals can be connected to graphical widgets in two ways:

* Starting from block the parameter or signal, and choosing the associated widget.
* Starting from the widget, and choosing the associated block parameter or signal.

## Starting from the model parameter or signal

1. Double-click on the model block containing the parameter or signal of interest.
2. From the side bar, identify the parameter or signal, and click on the **+** icon at the right.
3. The Data Point window is displayed: choose the desired widget.
4. Double-click on the widget attribute to which the parameter or signal has to be connected.

<figure><img src="https://2712201518-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fbs0l9jugXixa0ghErrqs%2Fuploads%2F9s4ziyGN4AqURKhUK7yw%2FConnection_block_to_widget.png?alt=media&amp;token=7db4f360-12c0-49bc-aca7-04433051e1ba" alt=""><figcaption></figcaption></figure>

## Starting from the widget

1. Double-click on the widget to be connected.
2. From the side bar, identify the field **Data** and click on the **+** icon at the right <mark style="color:$warning;">**OR**</mark> click on the blue <mark style="color:blue;">**⊞**</mark> next to the widget.

<figure><img src="https://2712201518-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fbs0l9jugXixa0ghErrqs%2Fuploads%2FwLXKgMwfU0xDtkj3zhMg%2Fwidget_connect.png?alt=media&amp;token=1f5228af-4be2-4613-a9d4-e25b132b6aeb" alt="" width="375"><figcaption></figcaption></figure>

3. The Data Point window is displayed: choose the desired model block.
4. Double-click on the block parameter or signal to which the widget has to be connected.

<figure><img src="https://2712201518-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fbs0l9jugXixa0ghErrqs%2Fuploads%2FVMQwnoPaZOKm8VN86R1v%2FConnection_widget_to_block.png?alt=media&amp;token=836a3b90-3fca-4279-9f85-30d175c6ed4f" alt=""><figcaption></figcaption></figure>


---

# 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/hyperlab/simulation-control-monitoring-and-logging/interacting-with-the-simulation/connecting-block-parameters-and-signals-with-widgets.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.
