> 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/example-models/get-started-with-sps/switching-an-inductive-circuit-using-a-breaker-with-no-snubber.md).

# Switching an Inductive Circuit Using a Breaker with No Snubber

This example shows the Ideal Switching device solution method of the Powergui block to model a circuit breaker.

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

## Description

The use of the Ideal Switching device solution method allows simulation of a circuit breaker without a snubber and connected in series with an inductive circuit.

Zoom on the breaker current and note the "exact" zero current when the breaker is open.

This solution technique (introduced in R2008b) is available with continuous solvers. To enable this option, check the "Enable use of ideal switching devices" parameter of the powergui block.

{% hint style="info" %}
To enable the Ideal Switching device solution method: open the powergui block and check "Enable use of ideal switching devices".
{% endhint %}

## Command

Example model name: power\_breaker

{% code lineNumbers="true" %}

```matlab
open('power_breaker')
```

{% endcode %}


---

# 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/example-models/get-started-with-sps/switching-an-inductive-circuit-using-a-breaker-with-no-snubber.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.
