> 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/model-and-simulation/phasor-domain-with-ephasorsim/configure-ephasorsim-block-ports.md).

# Configure ePHASORSIM Block Ports

## Complete the Excel configuration file

For the power system model integrated into the **ePHASORSIM Interface** block to exchange signals with the surrounding HYPERSIM model, **I/O pins** must be defined. I/O pins are configured in an Excel configuration file and determine the ports exposed by the **ePHASORSIM Interface** block.

{% stepper %}
{% step %}

### Open the Excel configuration file

Open the Excel configuration file saved in your model directory.

* When using a model built with native components, keep all worksheets.
* When using an imported model, only the **General** and **Pins** are required by default. All other worksheets may be removed unless they contain additional components that were added after the import process.
  {% endstep %}

{% step %}

### Review the General worksheet

The **General** worksheet defines the basic properties of the power system. Set the **Network Frequency (Hz)** and **Power Base (MVA)** values. You may modify the **Name** field, but do not change the **Excel file version**.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-546014fd6c2e8f98bc9ce9facffe4127b30f29f8%2Feph-general-worksheet.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

{% endstep %}

{% step %}

### Configure the Pins worksheet

{% endstep %}

{% step %}
Complete the **Pins** worksheet according to the following format:
{% endstep %}

{% step %}
**Column A** of the **Pins** worksheet defines the **pin type**. Two types of pins are available:
{% endstep %}

{% step %}

* **outgoing** : Send measurements and status information from the power system to the <code class="expression">space.vars.Software</code> model (for example, bus voltage or shunt status).
* **incoming** : Send commands from the <code class="expression">space.vars.Software</code> model to the power system (for example, fault application commands). Incoming pins must be connected; otherwise, the **ePHAORSIM** block may behave unexpectedly.
  {% endstep %}

{% step %}
**Column B** defines the **pin label** displayed on the **ePHASORSIM** block.
{% endstep %}

{% step %}
**Columns C and beyond** define the power system signals associated with the pin. A single signal column creates a scalar pin, while multiple signal columns create a vector pin whose size corresponds to the number of signal columns.
{% endstep %}

{% step %}
Each signal is identified by a **Pin Identifier**, which consists of a **component identifier** and a **signal identifier** separated by a forward slash (`/`).. For example, in `bus_2/Vmag`, `bus_2` is the component identifier and `Vmag` is the signal identifier.
{% endstep %}

{% step %}
The following example shows a **Pins** worksheet configuration for an imported PSS®E model:
{% endstep %}

{% step %} <img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-da3b3c1c009bfa5d1948679eeae65e1de2bb6b91%2Feph-pins-worksheet.png?alt=media" alt="" data-size="original">
{% endstep %}

{% step %}
The available **Pin Identifiers** for each component type are listed in the following sections:
{% endstep %}

{% step %}

* [Positive-sequence Pin Identifiers](https://www.opal-rt.com/docs/hypersim/model-and-simulation/phasor-domain-with-ephasorsim/configure-ephasorsim-block-ports/positive-sequence-pin-identifiers.md)
* [Multiphase Pin Identifiers](https://www.opal-rt.com/docs/hypersim/model-and-simulation/phasor-domain-with-ephasorsim/configure-ephasorsim-block-ports/multiphase-pin-identifiers.md)
* [FMU Pin Identifiers](https://www.opal-rt.com/docs/hypersim/model-and-simulation/phasor-domain-with-ephasorsim/configure-ephasorsim-block-ports/fmu-pin-identifiers.md)
  {% endstep %}

{% step %}

### Save the Excel configuration file

{% endstep %}

{% step %}

### Associate the dedicated configuration file

In the **ePHASORSIM Interface** block mask, next to the **I/O Pins file** field, click **Select file** and browse to the Excel configuration file in the model directory. Click **Create** to regenerate the ePHASORSIM block ports and update the block configuration.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-9270ef2466d2c5c4e75bb6717539a963fbe7130a%2Feph-hyp-io-pins.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Configure power flow

With the block I/O pins now defined, continue to [Configure Power Flow](https://www.opal-rt.com/docs/hypersim/model-and-simulation/phasor-domain-with-ephasorsim/configure-power-flow.md) to analyze the network steady-state operating point and prepare the model for dynamic simulation.
{% endstep %}
{% endstepper %}

| Column A                                                          | Column B                                                               | Columns C to Z                                                                                             |
| ----------------------------------------------------------------- | ---------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
| <p><strong>Pin type</strong><br>(e.g., <code>Outgoing</code>)</p> | <p><strong>Pin label</strong><br>(e.g., <code>Bus\_voltage</code>)</p> | <p><strong>Component identifier / Signal identifier</strong><br>(e.g., <code>30/Vmag</code>)</p>           |
| <p><strong>Pin type</strong><br>(e.g., <code>Incoming</code>)</p> | <p><strong>Pin label</strong><br>(e.g., <code>Fault</code>)</p>        | <p><strong>Component identifier / Signal identifier</strong><br>(e.g., <code>30/active3PGFault</code>)</p> |


---

# 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/model-and-simulation/phasor-domain-with-ephasorsim/configure-ephasorsim-block-ports.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.
