> 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/how-to/pscad-import-ieee-39-bus-system.md).

# PSCAD Import IEEE 39 Bus System

## Description

The **PSCAD Import 39-Bus** example, located in **File > Open an Example File > How To**, is based on the IEEE 39-bus (10-machine New England) system originally presented in \[1] and distributed as an example in PSCAD v5 \[2]. The PSCAD reference model provided with this example includes additional blocks to exercise fault transients and is imported into HYPERSIM using the Unified Database workflow. In both the PSCAD and HYPERSIM models, each generator is modeled as a voltage source with a 10 Ω source impedance.

The objective is to demonstrate a successful import, verify parameter mapping, and validate HYPERSIM results against PSCAD for two fault scenarios on Bus 1.

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

## Requirements

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

## Detailed explanation

The PSCAD reference model is provided in the PSCAD\_ref\_model folder. The example folder structure is:

**PSCAD\_Import\_39\_Bus**├─ PSCAD\_Import\_39\_Bus.ecf

├─ PSCAD\_Import\_39\_Bus.svt

├─ PSCAD\_Import\_39\_Bus.csv

├─ PSCAD\_Import\_39\_Bus\_hyp

├─ PSCAD\_ref\_model

└─ IEEE\_39\_bus.pscx

└─ intermediate.pslx

└─ lib

**Import workflow**

The Network Import tool converts the PSCAD project content into a list of objects, filters power and control blocks and their parameters, maps them to the Unified Database (UDB), and then generates the HYPERSIM model. For details on the Unified Database, see <https://opal-rt.atlassian.net/wiki/pages/createpage.action?spaceKey=UDD&title=The%20Unified%20Database>.

To import the PSCAD model into HYPERSIM:

1. Create a new HYPERSIM model.
2. Follow the steps in [PSCAD Network Import](broken://pages/3fc3f4635bdd1ce1d14d31675de46c8b5a467c43) to import the model.
3. Wait for the “Import successful” message in the Import Panel to confirm completion.

**Model preparation and library notes**

Prior to import, the PSCAD model `IEEE_39_bus.pscx` includes two additional breakers and a three‑phase fault block to validate fault transients after import. These breakers, the fault block, and associated timed control devices are imported into HYPERSIM. Breakers are configured as externally controlled devices.

The fixed load block references the Intermediate Library instead of the master library to address a known issue with `fixed_load` (bug number 2 in \[3]). See \[3] for the PSCAD V5 Intermediate Library details.

After import, the HYPERSIM schematic is generated automatically. A conversion report containing import logs is created in the PSCAD project directory.

In the current version, some connections may appear as general signals rather than three-phase signals; this does not affect the simulation.

A three-phase load may appear isolated, but it is connected via the bus name. These display issues will be corrected in a future release.

**Recording results with Datalogger**

The model time step in HYPERSIM is 5 μs to match the PSCAD settings. Use the [Datalogger](https://opal-rt.atlassian.net/wiki/spaces/HDI/pages/3548177/Datalogger) to record sensor measurements from t = 0 s to t = 1 s with a decimation factor of 10. You can add more sensors as described in [Sensor Management](broken://pages/aba45e983e3f844f3fd10e5d74b669b1c1ac002d).

To configure the Datalogger:

1. Click the Control Center icon in the Datalogger group on the HYPERSIM tab.
2. Select Signal Groups to access the default configuration.
3. Clear Output file auto naming to overwrite a single output file at each run.
4. Set Frame length to 1 s.
5. Set Decimation factor to 10.
6. Set Number of frames to 1.

This records the first 1 s of simulation at a 50 μs plot time step, allowing comparison of voltages and currents at different buses with PSCAD.

The provided <https://opal-rt.atlassian.net/wiki/spaces/PSV> template `PSCAD_Import_39_Bus.svt` can be used to compare recordings from PSCAD and HYPERSIM. Replace the source files before playback. Run `IEEE_39_bus.pscx` in `PSCAD_ref_model` to generate PSCAD recordings; the PSCAD `.inf` file is located in `.\PSCAD_ref_model\IEEE_39_bus.if15_x86`. After running the imported HYPERSIM model `PSCAD_Import_39_Bus.ecf`, the HYPERSIM `.oprec` file is created in `PSCAD_Import_39_Bus_hyp`.

## Simulation and results

A three-phase-to-ground fault is included to validate the imported model. By changing fault block parameters, you can simulate various transients. Two scenarios are provided.

### Scenario 1: Three-phase fault on Bus 1

The default PSCAD scenario applies a three-phase ground fault on Bus 1 at 0.3 s for 0.2 s. After import, the timed fault logic block in HYPERSIM is configured with the same timings. You can adjust TF (fault activation) and DF (fault clearing) to study different cases.

In the PSCAD reference model, Bus 1 is disconnected at 0.4 s using two breakers. These breakers and their switching operations are imported and configured in HYPERSIM via a breaker logic block.

Instantaneous waveforms from the imported HYPERSIM model overlap with those from the PSCAD reference model, validating the import accuracy.

### Scenario 2: Single-phase fault on Bus 1

This scenario applies a phase‑A‑to‑ground fault with the same default timings (activate at 0.3 s, clear after 0.2 s). By default, only the three‑phase fault is enabled; to run this scenario, change the fault type to a single‑phase (A‑ground) fault. The timed fault logic and breaker operations are identical to Scenario 1.

Results show that the imported HYPERSIM model also matches the PSCAD reference model for this unbalanced fault, confirming consistent accuracy.

## References

\[1] T. Athay, R. Podmore and S. Virmani, "A Practical Method for the Direct Analysis of Transient Stability," in IEEE Transactions on Power Apparatus and Systems, vol. PAS-98, no. 2, pp. 573-584, March 1979, doi: 10.1109/TPAS.1979.319407.

\[2] \[PSCAD Models and Examples] <https://www.pscad.com/knowledge-base/article/28>

\[3] \[Intermediate Library for PSCAD V5] <https://www.pscad.com/knowledge-base/article/808>


---

# 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/how-to/pscad-import-ieee-39-bus-system.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.
