> 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/connectable-elements.md).

# Connectable Elements

There are different categories of elements which can be connected to ensure data control and display.

## Core blocks

Model blocks are available in the **Library** -> **Core**

What can be connected from/to model blocks is:

* their **Inputs**
* their **Outputs**
* some of their **Parameters**

As an example:

* a **Memory** block has:
  * 1 **Input**
  * 1 **Output**
  * 1 **Parameter**: *Initial Condition*
* A **Pulse Generator** block has
  * 1 **Output**
  * 4 **Parameters**: Amplitude, Frequency, Duty cycle, Phase delay

<figure><img src="https://2712201518-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fbs0l9jugXixa0ghErrqs%2Fuploads%2F4kYCUjI9LxE9oid3uROx%2FCore_Blocks.png?alt=media&amp;token=5fdd863a-1640-403e-a85f-e06c008d4141" alt=""><figcaption></figcaption></figure>

## Electrical blocks

Electrical blocks are available in the **Library** -> **Electrical**

What can be connected from/to electrical blocks is:

* their **Inputs**
* their **Outputs**
* some of their **Parameters**

As an example:

* a **Voltmeter** block has:
  * 1 **Output**
* An **IGBT** block has
  * 1 **Input**
  * 4 **Parameters**: Ron, Roff, Sm, Gs

<figure><img src="https://2712201518-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fbs0l9jugXixa0ghErrqs%2Fuploads%2Fa6UkdNN6gMVgNKHRmzfM%2FElectrical_Blocks.png?alt=media&amp;token=98c19547-0e42-4f0e-bc03-7f9ab43bd54e" alt=""><figcaption></figcaption></figure>

## Widgets

Widgets are available in the **Library** -> **Widgets**. Although there are two categories of widgets which can be connected to other elements (**Control Widgets** and **Display Widgets**), they essentially have only one connectable element **Data**. It's used either to display data coming another element such as a model block or an I/O, or to control data going to a model block or an I/O.

Here are some examples:

<figure><img src="https://2712201518-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fbs0l9jugXixa0ghErrqs%2Fuploads%2FYfBRsk1v2b4E7CPHsZF7%2FWidgets.png?alt=media&amp;token=cfafb220-62e3-417c-a3c4-afbb82a1ebcf" alt="" width="375"><figcaption></figcaption></figure>

## I/Os

I/Os are available in the **Menu bar** -> **Interfaces**, when the [Simulator Setup](https://www.opal-rt.com/docs/hyperlab/configure-i-os/simulator-setup.md) is configured to run the simulation **in a real-time simulator**.


---

# 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/connectable-elements.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.
