> 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/smart-power-simulation-software-sps/blocks-functions-tools/basics/breakers-and-faults/breaker.md).

# Breaker

## Description

<figure><img src="https://799605156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdlNg8IbOdahCpFCyzxSN%2Fuploads%2Fgit-blob-ba318de5078b617c04148906787f094621bf5c80%2Fbreaker_block.png?alt=media" alt=""><figcaption></figcaption></figure>

The **Breaker** block, located in the **OPAL-RT SPS Software/Power Grid Elements** library, implements a circuit breaker where the opening and closing times can be controlled either from an external Simulink® signal (external control mode), or from an internal control timer (internal control mode).

A series Rs-Cs snubber circuit is included in the model. It can be connected to the circuit breaker. If the Breaker block happens to be in series with an inductive circuit, an open circuit or a current source, you must use a snubber.

When the Breaker block is set in external control mode, a Simulink input appears on the block icon. The control signal connected to the Simulink input must be either 0, which opens the breaker, or any positive value, which closes the breaker. For clarity, a 1 signal is commonly used to close the breaker.

When the Breaker block is set in internal control mode, the switching times are specified in the dialog box of the block.

When the breaker is closed, it is represented by a resistance Ron. To be negligible compared to external components, you can set the Ron value as small as necessary. A typical value is 10 milliohms. When the breaker is open, it has an infinite resistance.

The arc extinction process is simulated by opening the breaker device when its current passes through 0 at the first current zero crossing following the transition of the Simulink control input from 1 to 0.

<table data-header-hidden><thead><tr><th width="215.60003662109375"></th><th></th></tr></thead><tbody><tr><td><strong>Operation</strong></td><td><strong>Conditions</strong></td></tr><tr><td>The Breaker closes when</td><td>Control signal goes to 1 (for discrete systems, control signal must stay at 1 for at least three times the sampling period)</td></tr><tr><td>The Breaker opens when</td><td>Control signal goes to 0 Breaker current passes through 0</td></tr></tbody></table>

{% hint style="info" %}
The Breaker block may not be the appropriate switching device to use for DC circuits. For such applications, it is recommended that you use the Ideal Switch block as a switching device.
{% endhint %}

## Ports

### Input

<table data-header-hidden><thead><tr><th width="156.39996337890625"></th><th></th></tr></thead><tbody><tr><td><strong>c</strong> — Breaker operation control<br>Simulink signal</td><td>Signal to control the breaker operation. The control signal connected to this Simulink input must be either 0, which opens the breaker, or any positive value, which closes the breaker. For clarity, a 1 signal is commonly used to close the breaker.<br><strong>Dependencies</strong> To enable this port, select the <strong>External</strong> parameter.</td></tr></tbody></table>

### Conserving

<table data-header-hidden><thead><tr><th width="141.199951171875"></th><th></th></tr></thead><tbody><tr><td><strong>1</strong> — Terminal 1<br>SPS electrical</td><td>SPS electrical conserving port associated with the terminal 1 of the breaker.</td></tr><tr><td><strong>2</strong> — Terminal 2<br>SPS electrical</td><td>SPS electrical conserving port associated with the terminal 2 of the breaker.</td></tr></tbody></table>

### Parameters

<table data-header-hidden><thead><tr><th width="186"></th><th></th></tr></thead><tbody><tr><td><strong>Initial status</strong> — Initial status of breaker<br>0 (default)</td><td>Initial state of the breaker. A closed contact is displayed in the block icon when it is set to <code>1</code>, and an open contact is displayed when it is set to <code>0</code>. If the breaker initial state is set to 1 (closed), the software automatically initializes all the states of the linear circuit and the Breaker block initial current, so that the simulation starts in steady state.</td></tr><tr><td><strong>Switching times</strong> — Vector of switching times<br>[1/60 5/60] (default)</td><td>Vector of switching times when using the Breaker block in internal control mode. At each switching time the Breaker block opens or closes depending on its initial status. For example, if the <strong>Initial status</strong> parameter is <code>0</code> (open), the breaker closes at the first switching time, opens at the second switching time, and so on.<br><strong>Dependencies</strong> To enable this parameter, clear the <strong>External</strong> parameter.</td></tr><tr><td><strong>External</strong> — Option for external control<br>on (default) | off</td><td>If selected, adds a Simulink input to the Breaker block for external control of the switching times of the breaker. The switching times are defined by a logical signal (0 or 1) connected to the Simulink input. Default is selected.</td></tr><tr><td><strong>Breaker resistance Ron</strong> — Internal breaker resistance<br>0.01 (default)</td><td>Internal breaker resistance, in ohms (Ω). The <strong>Breaker resistance Ron</strong> parameter cannot be set to 0.</td></tr><tr><td><strong>Snubber resistance Rs</strong> — Snubber resistance<br>1e6 (default)</td><td>Snubber resistance, in ohms (Ω). Set this parameter to inf to eliminate the snubber from the model.</td></tr><tr><td><strong>Snubber capacitance Cs</strong> — Snubber capacitance<br>inf (default)</td><td>Snubber capacitance, in farads (F). Set this parameter to 0 to eliminate the snubber, or to inf to get a resistive snubber.</td></tr><tr><td><strong>Measurements</strong> — Measurements<br>None (default) | Branch voltage | Branch current | Branch voltage and current</td><td>Select Branch voltage to measure the voltage across the Breaker block terminals. Select Branch current to measure the current flowing through the Breaker block. If the snubber device is connected to the breaker model, the measured current is the one flowing through the breaker contacts only. Select Branch voltage and current to measure the breaker voltage and the breaker current. Place a Multimeter block in your model to display the selected measurements during the simulation. In the <strong>Available Measurements</strong> list box of the Multimeter block, the measurement is identified by a label followed by the block name:<br>Branch voltage - Ub:<br>Branch current - Ib:</td></tr></tbody></table>

### Limitations

When the block is connected in series with an inductor or another current source, you must add the snubber circuit. In most applications, you can use a resistive snubber (**Snubber capacitance** parameter set to inf) with a large resistor value (**Snubber resistance** parameter set to 1e6 or so). Because of modeling constraints, the internal breaker inductance Ron cannot be set to 0.

Use a stiff integration algorithm to simulate circuits with the Breaker block. ode23tb with default parameters usually gives the best simulation speed.

For discretized models, the control signal must stay at 1 for a minimum of three sampling time periods to correctly close the Breaker block, otherwise the device stays open.


---

# 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/smart-power-simulation-software-sps/blocks-functions-tools/basics/breakers-and-faults/breaker.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.
