> 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/import-models-from-external-software-or-code/import-from-emtp/use-an-emtp-circuit-in-hypersim.md).

# Use an EMTP Circuit in HYPERSIM

This page describes how to prepare and simulate an **EMTP circuit** in **HYPERSIM**. Since EMTP and HYPERSIM share the same user interface and network data format (`*.ecf`), an EMTP model can be opened directly in HYPERSIM. However, some components and simulation behaviors are not fully compatible. Minor modifications are also required to ensure correct execution.

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

## EMTP circuit modifications procedure

{% stepper %}
{% step %}

### Prepare the EMTP Model for HYPERSIM

Review the lists of **compatible components**, **partially compatible components**, and the relevant **adjustment pages** to ensure compatibility with HYPERSIM solvers and real‑time execution constraints.

Typical adjustments include:

* Replacing or adapting unsupported components
* Resolving control‑system modeling discrepancies
* Ensuring compatibility with balanced load‑flow initialization
* Adapting switching devices and event timing
* Adjusting modeling choices for real‑time execution
  {% endstep %}

{% step %}

### Open the EMTP Circuit in HYPERSIM

Launch HYPERSIM and load the EMTP project (`*.ecf` file). The model is imported directly and can be edited using HYPERSIM tools.
{% endstep %}

{% step %}

### Add a Point-on-Wave (POW) block

HYPERSIM requires a [Point-on-Wave (POW)](https://www.opal-rt.com/docs/hypersim/library-blocks-reference/network-tools/point-on-wave-synchronization.md) block to define simulation timing and initialization.

1. Add a **POW** block to the model.
2. If required, connect the POW to an auxiliary voltage source.

{% hint style="info" %}
EMTP and HYPERSIM use different waveform references (cosine vs. sine), which may require adjustment depending on the model.
{% endhint %}
{% endstep %}

{% step %}

### Replace EMTP switches

Switches defined in EMTP are not always directly compatible with HYPERSIM.

1. Identify switches that are not externally controlled.
2. Replace them with **HYPERSIM circuit breaker components**.
3. Define:
   * Initial state (steady-state condition)
   * Switching sequence (at least two events)
     {% endstep %}

{% step %}

### Initialize load flow (optional)

If the simulation must start from steady-state conditions:

1. Set the **bus voltage values**.
2. Execute the **load flow calculation**. HYPERSIM supports **balanced load flow only**.
   {% endstep %}

{% step %}

### Verify control systems (optional)

If the model includes synchronous machines or blocks from **Exciters and Governors** libraries, then controller compatibility must be verified.

1. Identify control subsystems.
2. Ensure all internal components are supported.
3. Modify the control structure if required (e.g., resolve algebraic loops).

Refer to **EMTP Control Compatibility** for guidance.
{% endstep %}

{% step %}

### Run the Simulation

After completing the required adjustments, run the simulation in HYPERSIM.

If issues are encountered:

* Verify component compatibility
* Review control systems
* Check switching definitions
  {% 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/model-and-simulation/import-models-from-external-software-or-code/import-from-emtp/use-an-emtp-circuit-in-hypersim.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.
