> 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/c37.118-master/configure-c37.118-master.md).

# Configure C37.118 Master

When working with communication protocols, it is recommended to begin by configuring the protocol through the **I/O Interfaces** section in <code class="expression">space.vars.Software</code> before proceeding with other steps.

## Configure the C37.118 master I/O interface

{% stepper %}
{% step %}

### Add a new I/O interface

1. In the **HYPERSIM** tab, click **I/O Interface** in the **Sensors & I/Os** section to open the **I/O Interface Configuration** window.

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

2. Right‑click **C37.118 Master** and select **Add**. Keep the default name or enter a custom one. If multiple **C37.118 Master** are added, each one must have a unique name.

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

{% step %}

### Configure the general settings

Click the newly added **C37.118 Master** in the **I/O Interface Configuration** window and configure the general settings.

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

<table><thead><tr><th width="160">Parameter</th><th>Value (Description)</th></tr></thead><tbody><tr><td><strong>Use an RT core for asynchronous computation</strong></td><td><strong>Checked:</strong> The driver reserves a dedicated real‑time CPU core for its communication system, allowing support for a larger number of slaves and more phasor, analog, and digital values.<br><strong>Unchecked:</strong> The communication system runs on core 0 alongside the operating system.</td></tr><tr><td><strong>Listening timeout (ms)</strong></td><td>The maximum number of milliseconds the driver waits for a response after sending a command to the PMU.</td></tr><tr><td><strong>Enable verbose mode</strong></td><td><strong>Checked:</strong> Displays the full configuration during model loading for debugging.<br><strong>Unchecked:</strong> Only standard log messages are displayed.</td></tr><tr><td><strong>Enable virtual mode</strong></td><td><strong>Checked:</strong> Allows the model to execute even if the I/O interface is not compatible with the system’s hardware configuration. Connections are initialized, but the I/O interface does not perform any actual data exchange. Useful for troubleshooting without hardware or preparing models for future platforms.<br><strong>Unchecked:</strong> The interface operates normally and requires compatible hardware.</td></tr></tbody></table>
{% endstep %}

{% step %}

### Manage devices: add, remove, rename, or reorder

Click **Devices** and use:

* **+** icon to add devices
* **–** icon to remove devices
* **Arrow** icons to reorder devices

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

{% step %}

### Configure the device(s) settings

Click a device under the **Devices** folder to configure its settings. Repeat this step for each additional device that needs to be reached.

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

<table><thead><tr><th width="150">Parameter</th><th>Value (Description)</th></tr></thead><tbody><tr><td><strong>ID</strong></td><td>Identifier of the PMU, as defined in IEEE Std C37.118.2‑2011. The C37.118 master must use the correct PMU ID to receive data; an incorrect ID prevents data reception.</td></tr><tr><td><strong>Protocol</strong></td><td>Select <strong>TCP</strong>, <strong>UDP</strong>, or <strong>TCP and UDP</strong>, depending on how the remote PMU is configured to communicate.</td></tr><tr><td><strong>TCP port</strong></td><td>The TCP port used by the C37.118 master to establish the connection with the PMU. Visible only when using <strong>TCP</strong> or <strong>TCP+UDP</strong> mode.</td></tr><tr><td><strong>UDP port</strong></td><td>The UDP port used by the C37.118 master to communicate with the PMU. Visible only in <strong>UDP</strong> or <strong>TCP+UDP</strong> mode.</td></tr><tr><td><strong>Use specific port for reception</strong></td><td><strong>Checked:</strong> The user specifies the UDP port on which the master expects packets from this PMU.<br><strong>Unchecked:</strong> The port is automatically selected from the list of free ports. Only visible in <strong>UDP</strong> mode.</td></tr><tr><td><strong>Local port</strong></td><td>The UDP port the master listens on for packets from the PMU. Visible only when using <strong>UDP</strong> and when <strong>Use specific port for reception</strong> is checked.</td></tr><tr><td><strong>NIC name</strong></td><td>Network interface name. Select the correct interface based on your <strong>System Description Document</strong> or Linux <code>ifconfig</code> command. For local testing on the same simulator, use the loopback interface <strong>lo</strong>.</td></tr><tr><td><strong>IP address</strong></td><td>IP address of the remote PMU. For local testing on the same simulator, use <strong>127.0.0.1</strong>.</td></tr><tr><td><strong>Phasors representation</strong></td><td>Select <strong>POLAR</strong> or <strong>RECTANGULAR</strong>, depending on how the PMU sends phasors.</td></tr><tr><td><strong>Phasors format</strong></td><td>Select <strong>INT16</strong> or <strong>FLOAT</strong>, according to the PMU configuration.</td></tr><tr><td><strong>Enable automatic data request</strong></td><td><strong>Checked:</strong> The master automatically sends a command to the PMU to start data transmission once connected and after receiving configuration frames.<br><strong>Unchecked:</strong> Exposes the <strong>Enable reception of data</strong> connectable point for the device. This connectable point allows to enable or disable data transmission <strong>from the model</strong> during execution.</td></tr><tr><td><strong>Apply phasor factor automatically</strong></td><td><strong>Checked:</strong> Applies the INT16 phasor scale factor automatically before sending values to the model.<br><strong>Unchecked:</strong> Raw INT16 values are sent to the model, but the scale factor remains available through a connection point. Only available if phasors are configured as <strong>INT16</strong>.</td></tr><tr><td><strong>Apply digital valid‑bit mask automatically</strong></td><td><strong>Checked:</strong> Automatically applies the PMU’s digital valid‑bit mask before sending digital values to the model.<br><strong>Unchecked:</strong> Raw digital values are sent without applying the mask.</td></tr></tbody></table>
{% endstep %}

{% step %}

### Configure the device(s) channels

1. Expand a device to reveal it's channel types.

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

2. Click a channel type (**Phasors**, **Analogs**, or **Digitals**) and use:

* **+** icon to add data points
* **–** icon to remove data points
* **Arrow** icons to reorder data points

3. Change names if desired.
4. For **digitals**, there is one parameter option: **Enable reception of normal bit states**. When **checked**, it exposes the **Normal state status word** connectable point. This connectable point allows to **receive and monitor** the normal status word of the current digital signal **in the model** during execution. When **unchecked**, the connectable point is not exposed.
   {% endstep %}

{% step %}

### Save the configuration

Click **Ok** or **Apply** to save the configuration.
{% 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/c37.118-master/configure-c37.118-master.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.
