> 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-pscad/compatibility-and-limitations.md).

# Compatibility & Limitations

This page describes the supported **PSCAD** components and features when importing a network model into **HYPERSIM**, as well as the known limitations and constraints.

## Supported components and features

### Component mapping

Each PSCAD component may be converted into one or more HYPERSIM components, depending on its configuration, parameter values, or subtype.

For example, the PSCAD **AC Exciter (EXCAC)** component may be mapped to different exciter controller blocks in HYPERSIM, depending on its selected options.

### Supported PSCAD components and features

The complete list of supported PSCAD components is available in the **Unified Database (UDB)**:

1. In the **HYPERSIM** tab, click **User Manual** in the **Help** section and select **Unified Database.**

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

2. In the **OPAL-RT Unified Database Documentation**, navigate to **Supported Third-party Tools** and select **PSCAD** to view the list of PSCAD components that can be imported.

{% hint style="danger" %}
Inclusion in this list does not guarantee that all features or parameter options of a component are supported.
{% endhint %}

3\. Select the desired component, expand the **UDB mapped types** and review the **Condition** column. The condition specifies the supported parameter values or configurations.

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

## Limitations

### General limitations

* Blocks with identical names at the same hierarchy level are not supported.
* If a model contains unsupported components:
  * Associated buses may be removed during import
  * This occurs because unsupported branch ports and power connections cannot be resolved

### Dynamic DataTap behavior

The **dynamic\_datatap** component is supported only under specific conditions:

* **Supported case:**\
  If the **SI** port is driven by a constant value (e.g., `master:const`, constant signal, or parameter), the component behaves as a standard DataTap.
* **Unsupported case:**\
  If the **SI** port is driven by a time-varying (dynamic) signal, the component is ignored.\
  → No connection is created between its inputs and outputs.

### Numerical behavior

* **Division by zero** is not supported in HYPERSIM and results in a **NaN value**, even if handled differently in PSCAD.

  **Recommendation:**\
  Add a limiter or protective logic in the model to prevent division by zero before import.

### Frequency limitations

* The HYPERSIM equivalent of the PSCAD **master:complex** component does not support high characteristic frequencies.
* Instabilities or divergence may occur for frequencies above **9 kHz**.


---

# 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-pscad/compatibility-and-limitations.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.
