> 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/library-blocks-reference/network-switches-and-breakers/fault-1-phase.md).

# Fault, 1-Phase

## Description

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

The **Circuit Breaker, 1-Phase** block, located in the **Network Switches and Breakers** library, simulates a single-phase breaker modeled as a variable resistance connected to ground. The resistance is very low when closed and very high when open. The breaker can be controlled by internal timing, by an external schematic control signal, or by simulator digital inputs.

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

## Mask parameters

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

{% tabs %}
{% tab title="Timing" %}

<table><thead><tr><th width="200.20001220703125" valign="top">Parameter</th><th>Description</th></tr></thead><tbody><tr><td valign="top"><strong>Time units</strong></td><td>Units applied to programmed state transitions<br>- Second (s): All T<sub>n</sub> in seconds.<br>- Millisecond (ms): All T<sub>n</sub> in milliseconds.<br>- Cycle (c): All T<sub>n</sub> in electrical cycles (set Base frequency).</td></tr><tr><td valign="top"><strong>General operation</strong></td><td>Master enable for programmed operations at acquisition trigger EnaGen (0: Disable, 1: Enable).</td></tr><tr><td valign="top"><strong>Steady-state condition</strong></td><td>Breaker state in steady state: open or closed EtatIniA (0 or 1).</td></tr><tr><td valign="top"><strong>Network frequency</strong></td><td>Legacy parameter, use Base frequency instead (Hz) Freq [45, 70].</td></tr><tr><td valign="top"><strong>Model type</strong></td><td>Component behavior, TypeA (0 Breaker, 1 Switch).<br>- Breaker: After the time condition, waits for the current to cross the breaking threshold before changing state.<br>- Switch: Changes state as soon as the time condition is met.</td></tr><tr><td valign="top"><strong>Enable (per operation)</strong></td><td>Enable/disable the state transition for each operation line, EnaTn (0 Disable, 1 Enable).<br>If enabled but the line has no time information, the operation is ignored.</td></tr><tr><td valign="top"><strong>Time</strong></td><td><p>Relative time (referenced to <a href="https://www.opal-rt.com/docs/hypersim/library-blocks-reference/network-tools/point-on-wave-synchronization.md">POW synchronization</a>) when the command is sent to change state. Enter as a single string (no alias for timing type in the API). There are four formats:</p><ul><li><strong>Fixed</strong>: <em>f: fixed time</em> T<sub>n</sub> is constant across acquisitions.</li><li><strong>Incremental</strong>: <em>i: initial/final/increment</em> T<sub>n</sub> starts at initial, increases by increment each acquisition, and resets after reaching final</li><li><strong>Uniform</strong>: <em>u: min/max</em> T<sub>n</sub> is uniformly random within [min, max] each acquisition.</li><li><strong>Uniform gaussian</strong>: <em>ug: min/max/dispersion</em> T<sub>n</sub> is random with a gaussian distribution within [min, max].<br></li></ul><p>Important notes:<br>- Programmed operation times must satisfy: T<sub>n</sub> > T<sub>(n-1)</sub></p><p>- If a time field is blank or contains “-”, no switching occurs for that line.<br>- With referenced operations, the computed time is applied after the command is received from the reference component.</p></td></tr><tr><td valign="top"><strong>Referenced operations</strong></td><td>Trigger T<sub>n</sub> based on another breaker's programmed transition (all columns required). See Referenced Operations<br>- Component: Name or path of the referenced breaker. Variables: Eref1 = 'path.name', Eref2 = 'path.name', ...<br>- Time: ID of the referenced breaker's T<sub>n</sub> step Tref1 = T<sub>n</sub>, Tref2 = T<sub>n</sub>, ...<br>- Phase/Command: Activate (Phase) or deactivate (Command) the reference dependency. T1RPh, T2RPh, ...</td></tr><tr><td valign="top"><strong>Phase operated</strong></td><td>Change of state when the timing condition is reached for each operation line T1Pa, T2Pa, ...</td></tr></tbody></table>
{% endtab %}

{% tab title="General" %}

<table><thead><tr><th width="201">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Description</strong></td><td>Free-text field for documenting the block.</td></tr><tr><td><strong>Control type</strong></td><td>Select the control source for the breaker state CmdBlockSelect.<br>- Internal (0): Control defined in the Timing tab.<br>- External (input sensors) (1): Simulator digital inputs on CMD(a,b,c) sensors.<br>- External (input pins) (3): Schematic control signal (binary).</td></tr><tr><td><strong>Ropen</strong></td><td>Open-state resistance (Ω) of the breaker, ROpen [0, 1e12].</td></tr><tr><td><strong>Rclosed</strong></td><td>Closed-state resistance (Ω) of the breaker RClose [0, 1e12].</td></tr><tr><td><strong>Current chopping limit</strong></td><td>Threshold for for the absolute value of current (A) below which the breaker is forced to open to emulate current chopping, IMargin [0, 1e64].<br>Applies only when Model type is set to Breaker.</td></tr><tr><td><strong>Base power</strong></td><td>Base value for per-unit conversion (MVA total), pBase [1, 1e64].</td></tr><tr><td><strong>Base voltage</strong></td><td>Base value for per-unit conversion (kV rms LN), vBase [1, 1e64].</td></tr><tr><td><strong>Base frequency</strong></td><td>Base value for per-unit conversion (Hz), fbase [1, 1e64].</td></tr></tbody></table>
{% endtab %}
{% endtabs %}

## Conserving ports

| Port       | Description                                             |
| ---------- | ------------------------------------------------------- |
| **Net\_1** | Network connection (supports only 1-phase connections). |

## Inputs

| Input | Description                            |
| ----- | -------------------------------------- |
| **P** | Control input for the breaker command. |

## Outputs

This block has no outputs.

## Signals available for monitoring and external I/O connections (via sensors form)

All block inputs and outputs are available as signals for monitoring and for external I/O connections.

Additional signals are also available and are listed below with their descriptions.

<table><thead><tr><th width="199.60003662109375">Signal</th><th>Description</th></tr></thead><tbody><tr><td><strong>CMD</strong></td><td>Breaker command.</td></tr><tr><td><strong>I</strong></td><td>Breaker current (A).</td></tr><tr><td><strong>Psw</strong></td><td>Instantaneous apparent power at the positive breaker port (VA).</td></tr><tr><td><strong>STATE</strong></td><td>Breaker state (may differ from the command depending on Model type).</td></tr><tr><td><strong>V</strong></td><td>Phase breaker voltage (V).</td></tr></tbody></table>


---

# 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/library-blocks-reference/network-switches-and-breakers/fault-1-phase.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.
