> 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/automation-api-and-scripting/automate-using-testview/test-commands-reference/main/multi-breaker.md).

# Multi-Breaker

## Description

This command is used to program several groups of breakers in parallel. If the HYPERSIM network topology has previously been analyzed, all breakers from the model will be available in the dropdown menu in the selection section.

{% hint style="danger" %}
This command must be in a loop before the **HypProc** command (Processing).
{% endhint %}

## Parameters

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

<table><thead><tr><th width="145.8182373046875">Function</th><th>Description</th></tr></thead><tbody><tr><td><strong>Title</strong></td><td>To enter the name of the Multi Breakers command.</td></tr><tr><td><strong>Category</strong></td><td><p>Lists switches and breakers sub-categories. Example:</p><ul><li>hyDisjTerre is for faults</li><li>hyDisjoncteur is for breakers</li></ul></td></tr><tr><td><strong>Name</strong></td><td>Dropdown menu that lists all the breakers and faults found in the design.</td></tr><tr><td><strong>Enable Ground</strong></td><td>If the selected type includes g, this option is automatically updated.</td></tr><tr><td><strong>Type</strong></td><td>The user can select one or several default types. There will be as many iterations as default types under Group Tabs. The type suite adapts to the breaker Category and Name.<br><strong>For HyDisjoncteur:</strong> <img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-0dc1d5f7571308f6ea1958dc4958e0d0cda41a3b%2Fimage%20(1253).png?alt=media" alt=""><br><strong>For HyDisjTerre:</strong> <img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-f026ee7ffaef5324a6e3fcafe4d651d5e3d5c20e%2Fimage%20(1254).png?alt=media" alt=""></td></tr><tr><td><strong>Switching Times</strong></td><td>Timing of the operation of the selected breaker or fault. This timing is relative to the Point-On-Wave synchronization. Up to 8 switching times can be configured.</td></tr><tr><td><strong>Groups</strong></td><td>The user must ensure that the number of circuit breakers in each group is consistent. In the example below, we see that each group has 5 default definitions:<br><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-499f7da9b6977fc9c1ecea33c5119163acdf1364%2Fimage%20(1255).png?alt=media" alt=""></td></tr><tr><td><strong>Add</strong></td><td>Add an iteration using the configured switching time, the type, and the selected breaker defined. The iterations are relative to the <strong>Loop</strong> command. Note that you must enter at least one switching time to add an iteration. This button is only available when Group 1 tab is selected.</td></tr><tr><td><strong>Replace</strong></td><td>Replace one or several iterations with another. You must select line(s) you want to replace. This button is only available from Group 2, therefore it is not available when Group 1 tab is selected.</td></tr><tr><td><strong>Disable</strong></td><td>Disable iterations. You must select line(s) you want to disable within the current group. This button is only available from Group 2, therefore it is not available when Group 1 tab is selected. Disabling an iteration is equivalent to write "-" in the breaker column. In the example below, we see that the 3 latest iterations are disabled:<br><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-e3deb230fd9030edac8b6029830cc0e346df2907%2Fimage%20(1256).png?alt=media" alt=""></td></tr><tr><td><strong>Remove</strong></td><td>Remove one iteration at a time. It will remove one iteration for all groups. If you remove Group 1, it will remove all Groups.</td></tr><tr><td><strong>Remove All</strong></td><td>Remove all iterations for all groups.</td></tr><tr><td><strong>Arrow buttons</strong></td><td>Move a selected iteration up or down the list.</td></tr><tr><td><strong>New Brk Group</strong></td><td>Create a new Group. To remove a Group, right-click on the tab of the group you want to delete.</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/automation-api-and-scripting/automate-using-testview/test-commands-reference/main/multi-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.
