> 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/phasor-domain-with-ephasorsim/integrate-a-power-system-model-to-ephasorsim/native-library-components/multiphase-fault-component.md).

# Multiphase Fault Component

## Multiphase Fault

The multiphase fault component models faults involving one, two, or three phases in a **multiphase network**. It supports **phase-to-ground** and **phase-to-phase** faults.

Each selected phase is connected to a virtual fault point through the fault impedance **Zf**. For phase-to-ground faults, the virtual fault point is connected to ground through the ground impedance **Zg**.

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

{% hint style="info" %}
**Impedance definitions:**

The impedance between each selected phase and the virtual fault point is: Z\_f = R\_f + jX\_f

For phase-to-ground faults, the impedance between the virtual fault point and ground is: Z\_g = R\_g + jX\_g
{% endhint %}

Populate the **Bus1**, **Bus2**, and **Bus3** columns from left to right according to the phases involved in the fault. Unused bus fields may be left empty, but they must follow all populated fields. For example, **Bus2** cannot be populated if **Bus1** is empty.

The connected phases do not need to be consecutive phases. For example, **Bus1** and **Bus2** may identify phases A and C.

**Phase-to-ground faults:**

* **Single-phase**-to-ground fault: Complete **Bus1**.
* **Two-phase**-to-ground fault: Complete **Bus1** and **Bus2**.
* **Three-phase**-to-ground fault: Complete **Bus1**, **Bus2**, and **Bus3**.

**Phase-to-phase faults:**

* **Two-phase** fault: Complete **Bus1** and **Bus2**.
* **Three-phase** fault: Complete **Bus1**, **Bus2**, and **Bus3**.

| Excel Column Name / Native Component Parameter | Description                                                                                                                                                                                                             |
| ---------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Bus1**                                       | Bus identifier for the first phase involved in the fault.                                                                                                                                                               |
| **Bus2**                                       | Bus identifier for the second phase involved in the fault. Leave empty for a single-phase fault.                                                                                                                        |
| **Bus3**                                       | Bus identifier for the third phase involved in the fault. Leave empty for single-phase and two-phase faults.                                                                                                            |
| **ID**                                         | Unique fault identifier.                                                                                                                                                                                                |
| **Type**                                       | <p>Fault connection type.<br><code>phase2ground</code>: Connects the virtual fault point to ground through <strong>Zg</strong>.</p><p><code>phase2phase</code>: Does not connect the virtual fault point to ground.</p> |
| **R\_f**                                       | Resistance from each selected phase to the virtual fault point (Ω).                                                                                                                                                     |
| **X\_f**                                       | Reactance from each selected phase to the virtual fault point (Ω).                                                                                                                                                      |
| **R\_g**                                       | Resistance from the virtual fault point to ground (Ω). Used for `phase2ground` faults.                                                                                                                                  |
| **X\_g**                                       | Reactance from the virtual fault point to ground (Ω). Used for `phase2ground` faults.                                                                                                                                   |
| **Active**                                     | Initial fault status (`1` = active, `0` = inactive).                                                                                                                                                                    |


---

# 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/phasor-domain-with-ephasorsim/integrate-a-power-system-model-to-ephasorsim/native-library-components/multiphase-fault-component.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.
