> 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/configure-ios/communication-protocol-ios/signal-generator/connect-sensors-to-connectable-points.md).

# Connect Sensors to Connectable Points

{% stepper %}
{% step %}

### Connect sensors to the I/O interface connectable points

1. Either right‑click a component and select **Open Sensors Form** to configure its sensors and I/O connections, or click **Sensor Summary** in the **Sensors & I/Os** section of the **HYPERSIM** tab to configure I/O connections for multiple components with previously activated sensors at once.
2. Click the **Edit** **I/O connection** icon for the desired sensor to open the **I/O Selector** window.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-5d23bacce871896b9a72db86a06859f8ec43af3e%2FDR-hyp-c37-connect.png?alt=media" alt=""><figcaption></figcaption></figure>

3. In the **I/O Selector** window, double‑click the desired I/O channel to connect the sensor. Use the **text field** to quickly filter and locate available connectable points, or use the **dropdown menus** to filter by driver and/or by I/O direction. Only one signal is allowed per I/O connection. If multiple signals are assigned to the same connectable point, HYPERSIM will detect the conflict during simulation initialization, raise an error, and prevent the simulation from starting.

If a more explicit and visual representation of I/O connections is preferred, I/O blocks from the [Target Inputs and Outputs](broken://pages/7F50Ym2bMjwzhmhPZ5uX) library can be added directly to the schematic and connected to components. After placing the I/O block, open its **Sensors Form** to complete the I/O connection. In this workflow, the component connects to the I/O block, which is then linked to the **I/O Interface**. This approach produces the same functional result as a direct sensor‑to‑I/O connection, but makes the I/O mapping more visible and easier to interpret when viewing the schematic alone.
{% endstep %}

{% step %}

### Review the I/O connections

Once a sensor is connected to a connectable point, the connection type is displayed. For example, **C37.118 Slave/Slaves/OPALRT‑PMU\_2/Phasors/I‑PHASOR/Angle** indicates that the sensor is connected to the **Angle** component of the **I‑PHASOR** measurement provided by the **OPALRT‑PMU\_2** C37.118 slave configured in the **C37.118 Slave I/O Interface**. The **I/O Factor** column is used to scale signals when needed. For output signals, the simulation value is divided by the I/O Factor. For input signals, the value received from the I/O Interface is multiplied by the I/O Factor.
{% endstep %}

{% step %}

### Start the simulation

​In the **HYPERSIM** tab, click **Start**. Once the simulation is running, the **Start** button becomes grayed out, and the **Stop** button becomes active, allowing you to halt execution if required.
{% 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/configure-ios/communication-protocol-ios/signal-generator/connect-sensors-to-connectable-points.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.
