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

# Compatibility & Limitations

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

## Supported components and features

### Supported Versions

The following PSS®E versions are supported:

* Version 32
* Version 34
* Version 35

### Component mapping

Each PSS®E component may be converted into one or more HYPERSIM components, depending on its type and parameter values.

### Supported PSS®E components and features

The complete list of supported PSS®E 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 **PSSe** to view the list of PSS®E 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-8c1a880c96d02bc43edca35ed99dfa13237ecb8c%2Fpsse-condition.png?alt=media" alt=""><figcaption></figcaption></figure>

### Sequence data

Sequence data can be provided using a **`.seq`** file. This data is used to calculate unbalanced fault currents under steady-state conditions.

When a `.seq` file is present, **line** and **transformer** parameters are populated using sequence data.

{% hint style="info" %}
Machine sequence data is not imported from the `.seq` file, as machine parameters are defined in the **`.dyr`** file and may conflict with sequence data.
{% endhint %}

### Coordinates

The coordinates of the components can be defined by a \*.gps or \*.substations file.

An example of a \*.gps file is as follows:

```
Substation,Latitude,Longitude,BUS#,BUS NAME,BUS VOLTAGE (kV),PSSE Bus Name,
STATION1,45.5019,73.5674,1,BUS1,345,,
STATION2,45.5666,73.5444,1,BUS2,345,,
```

The header of the file is parsed to determine what type of conversion to apply so it must respect the convention above. Coordinates can be expressed as a `x, y` couple or as `Latitude, Longitude`. If `x, y` is preferred the header becomes:

```
Substation,x,y,BUS#,BUS NAME,BUS VOLTAGE (kV),PSSE Bus Name,
```

An example of a \*.substations file is as follows:

```
Substation,BUS#,BUS NAME,x,y
STATION1,1,b1,-100,0
STATION2,1,b2,-120,10
```

If a \*.substations file is provided, the components on the specified buses will be grouped by substations.

### Auto-layout

If neither a `.gps` nor a `.substations` file is provided, an automatic layout algorithm generates component positions in HYPERSIM

## Limitations

* In `.raw` files, **bus base voltages** are interpreted as **RMS line-to-line voltages**, expressed in **kV**.
* When exporting `.raw` files from PSS®E:
  * The **Output bus names** option must be **unchecked**, as it is not supported during import.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-26a338193aff1bdc3d32b3b6d75d7ba4a764ea54%2Fpsse-limitation.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/model-and-simulation/import-models-from-external-software-or-code/import-from-pss-e/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.
