> 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/library-blocks-reference/target-inputs-and-outputs/target-i-o-interface.md).

# Target I/O Interface

## Description

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-b95ed3f58e9c52b0eef22195754dec6330572d37%2Fimage%20(1041).png?alt=media" alt="" width="134"><figcaption></figcaption></figure>

The **Target I/O Interface** block, located in the **Target Inputs And Outputs** library, helps visualize I/O connections in the schematic and directly connects to components that send or receive data to or from the I/Os.

By default, the block contains two empty bundles: **IN** and **OUT**. When the component configuration changes, input data points are mapped to pins in the **IN** bundle, and output data points are mapped to pins in the **OUT** bundle.

When you apply changes in the form, the block updates in the schematic with the selected exchanger names and the number of input/output pins. During model analysis, sensors from devices connected to the Target I/O Interface are automatically selected and assigned to the matching I/O specified by each pin. Because I/Os are set automatically, you cannot edit them in the component form. To remove an I/O connection, break the connection in the schematic.

The Target I/O Interface represents the I/O interface but is not a network component in the simulation. It does not appear in the netlist, and its use does not affect simulation performance compared to manually connecting sensors via the Sensor summary.

## Mask parameters

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-8635557fddde614f3f0fd28bc90aa650cf98d10e%2Fimage%20(1042).png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

<table><thead><tr><th width="238.79998779296875">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>I/O selection</strong></td><td>Select multiple I/Os to populate the device bundles. Selections can be cleared with the Broom icon. Filtering features are similar to the I/O Selector in Sensor Management.</td></tr></tbody></table>

Open the **I/O Interfaces menus** using the buttons in the top right of the form. When the I/O configuration changes, the form refreshes with updated data points.

Open the **pin assignment menu** to add, delete, or rename pins. After applying the assignment, you can reassign I/Os to specific pins. Unused pins are not shown on the schematic. Choose the destination pin for each I/O.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-ac3a0a9d583d770ec76d0e913bade9cf37873026%2Fimage%20(1043).png?alt=media" alt=""><figcaption><p>Pin assignement menu</p></figcaption></figure>

After applying the pin assignment, I/Os can be reassigned to specific pins. Not all pins need to be used; unused pins are not displayed in the schematic. Assign an alias to each data point to define the pin name. If no alias is specified, HYPERSIM automatically assigns a unique pin name based on the original data point name.

Depending on the pin assignation and the aliases given to each I/O, the component will have different pin/bundle naming:

* If the pin is assigned only once, the signal will be contained in a simple pin on the device. The pin name will be the same as the value in the pin column, regardless of the defined alias.
* If the pin is assigned multiple times, the pin will become a bundle. For each I/O, the matching pin in the bundle will be named by :
  * The alias, if defined
  * The datapoint name's full text, starting from the end. The name will be made as precise as the schematic allows it.

The total number of selected I/Os updates at the bottom of the form. Clicking the count brings selected nodes of the matching type to the top of the table.

To illustrate the method, let use this example :

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-167f413998875eb3b9e5494e6fa7114e4d274e5f%2Fimage%20(1044).png?alt=media" alt=""><figcaption></figcaption></figure>

\
As a simple example, we are using a Signal Generator, controlling the amplitude and frequency, while receiving the output, displayed as a Flat List.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-b6578e78e12c3a26eb83c7e8f60c3a2723ea5213%2Fimage%20(1045).png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

We connect the model to the Target I/O Interface block. The exchanger name shows, as well as the number of connections. We can either create a breakout or connect directly to the other devices on the pin. The unconnected pins will then be ignored.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-3b34b9f8fcea016f21db079f801690e30183bf78%2Fimage%20(1046).png?alt=media" alt=""><figcaption></figcaption></figure>

When opening the sensor summary, we can see the following configuration. Each sensor is automatically connected. The connection cannot be edited, and a tooltip explains why it is not possible.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-dc9270e7649a17f055d0d37fb1da9c64a4d73acf%2Fimage%20(1047).png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

## Inputs

| Input  | Description                                                                      |
| ------ | -------------------------------------------------------------------------------- |
| **IN** | Bundle automatically populated with pins mapped from selected input data points. |

## Outputs

| Output  | Description                                                                       |
| ------- | --------------------------------------------------------------------------------- |
| **OUT** | Bundle automatically populated with pins mapped from selected output data points. |

## Signals available for monitoring and external I/O connections (via sensors form)

All block inputs and outputs are available as signals for monitoring and for external I/O connections.


---

# 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/library-blocks-reference/target-inputs-and-outputs/target-i-o-interface.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.
