> 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/examples/emtp-compatibility/emtp-compatibility-introduction.md).

# EMTP Compatibility Introduction

## Description

The **EMTP Compatibility Introduction** example, located in **File > Open an Example File > EMTP**, demonstrates EMTP Network Compatibility between EMTP and HYPERSIM. The model contains a passive circuit, a voltage source, and a switch that is closed in steady state and opens at 0.004 s. The objective is to illustrate the steps to run an EMTP model in HYPERSIM and to highlight differences in time handling and switch modeling between the two tools.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-6a39151460b0e0cf7ac82477f5d4c31ed7818a34%2Fimage%20(70).png?alt=media" alt=""><figcaption></figcaption></figure>

## Requirements

This example model does not require any additional hardware or licenses.

## Detailed explanation

As opposed to EMTP, the end of a simulation in HYPERSIM is undefined. In HYPERSIM, the simulation is stopped manually by the user and the time is defined as absolutely or relatively. This example would help to show the notion of time and to better understand the difference between EMTP and HYPERSIM when modeling a switch.

EMTP Network Compatibility allows editing and simulating in HYPERSIM a circuit originally developed in EMTP. EMTP and HYPERSIM share the same user interface and network data format (\*.ecf), so EMTP models can be loaded directly in HYPERSIM.

{% hint style="info" %}
For background and workflow details, see the following section [Import from EMTP](https://www.opal-rt.com/docs/hypersim/model-and-simulation/import-models-from-external-software-or-code/import-from-emtp.md)
{% endhint %}

This example was created in EMTP and opened in HYPERSIM. After a few block-level adjustments, it is ready to run in HYPERSIM.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-1c1c66df5b40daf553f1bdd598803ea8183ddd70%2Fimage%20(1635).png?alt=media" alt=""><figcaption><p>A closer look of the model in HYPERSIM</p></figcaption></figure>

## Simulation and results

Make sure the CB1 1-phase breaker settings are as shown in the following picture with the timing of 0.004 seconds:

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-ebfee4815ab3c28f1d4ecea5554c97cf8b03090d%2Fimage%20(1636).png?alt=media" alt=""><figcaption></figcaption></figure>

Run the simulation at the time step of 1 us and open the ScopeView Template **EMTP\_Compatibility\_Introduction.svt**.

The ScopeView template superimposes the results from the HYPERSIM model and reference data from the EMTP model. But when the template is opened for the first time, users need to replace the reference data as the data source.

Like it is shown in the following picture, just choose the Data Source next to the data from MAT1 and click on Replace.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-ca5a45c8af2ef9636535058015f7f810178f0388%2Fimage%20(1637).png?alt=media" alt=""><figcaption></figcaption></figure>

Then, according to the picture below, find the reference data in the example model folder. The Files of type option needs to be set to MATLAB files to show the reference (\*.mat) file. The reference data is called "EMTP\_Compatibility\_Introduction.mat"

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

Start the simulation in ScopeView and see the results, make sure Sync and Trig are on in ScopeView

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-b49097f4ceaf9455dd04835c34ce580d76635e07%2Fimage%20(62).png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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/examples/emtp-compatibility/emtp-compatibility-introduction.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.
