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

# FMU Pin Identifiers

## Introduction <a href="#i-o-pins-format" id="i-o-pins-format"></a>

This page lists the available **Pin Identifiers** for **FMU-based components**. Use these identifiers in the **Pins** worksheet to configure the ePHASORSIM block ports.

{% hint style="info" %}
All components, parameters, variables and pins names are case-sensitive.
{% endhint %}

## Single Controller FMU <a href="#i-o-pins-format" id="i-o-pins-format"></a>

FMUs exported from **single-component models** support a subset of Pin Identifiers that are identical to those used by the corresponding **Native Library** components. These common identifiers are listed in the following table.

| Pin Description             | Direction       | Pin Identifier                                                                                                                         |
| --------------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| Set/Get reference increment | Input or Output | <p><strong>exciterID</strong>/pins/dVref</p><p><strong>turbineID</strong>/pins/dGref</p>                                               |
| Get component output        | Output          | <p><strong>exciterID</strong>/pins/Efd</p><p><strong>turbineID</strong>/pins/Pmech</p><p><strong>stabilizerID</strong>/pins/Vothsg</p> |

Additional FMU-specific Pin Identifiers are described in the subsequent sections.

| Pin Description              | Direction | Pin Identifier                                                                                                   | Example                             |
| ---------------------------- | --------- | ---------------------------------------------------------------------------------------------------------------- | ----------------------------------- |
| Component pins               | Output    | **ComponentID**/Component pins name                                                                              | **ex1/**&#x45;F&#x44;**, ex1**/EFD0 |
| Sub-block pins               | Output    | **ComponentID**/Sub-block\_name.pins\_name                                                                       | **ex1**/add3.y, **ex1**/add3.u      |
| Component parameter/variable | Output    | <p><strong>ComponentID</strong>/Data name</p><p>Type supported: 'Real' and 'parameter Real(fixed = false)'</p>   | **ex1**/VREF\_0, **ex1**/EFD\_0     |
| Sub-block parameter/variable | Output    | <p><strong>ComponentID</strong>/Sub-block\_name.data\_name</p><p>Type supported: 'Real' and 'parameter Real'</p> | **ex1**/gain1.K, **ex1**/lag1.T     |

## GenUnit FMU

The following table lists the **Pin Identifier** formats used to access signals, parameters and variables exposed by a **GenUnit FMU**.

| Pin Description                | Direction       | Pin Identifier                                           | Example                       |
| ------------------------------ | --------------- | -------------------------------------------------------- | ----------------------------- |
| GenUnit Interface pins         | Input or Output | **GenUnitID**/Pins\_name                                 | **gen\_1\_1**/dVREF           |
| Component pins                 | Output          | **GenUnitID**/Component\_name.Pins\_name                 | **gen\_1\_1**/esst4b1.EFD     |
| Sub-block pins                 | Output          | **GenUnitID**/Component\_name.Sub-block\_name.Pins\_name | **gen\_1\_1**/esst4b1.add1.y  |
| Component parameters/variables | Output          | **GenUnitID**/Component\_name.Data\_name                 | **gen\_1\_1**/esst4b1.VREF\_0 |
| Sub-block parameters/variables | Output          | **GenUnitID**/Sub-block\_name.Data\_name                 | **gen\_1\_1**/esst4b1.gain1.K |


---

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