> 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/power-transmission-and-distribution/surge-arrester.md).

# Surge Arrester

## Description

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

The **Surge Arrester** block, located in the **OPAL-RT SPS Software/Passives** library, implements a highly nonlinear resistor used to protect power equipment against over voltages.

For applications requiring high power dissipation, several columns of metal-oxide discs are connected in parallel inside the same porcelain housing. The nonlinear V-I characteristic of each column of the surge arrester is modeled by a combination of three exponential functions of the form

$$
\frac{V}{V\_{\text{ref}}}
\= k\_i \left( \frac{I}{I\_{\text{ref}}} \right)^{1/\alpha\_i},
\quad i = 1,2,3.
\\\[8pt]
$$

The protection voltage obtained with a single column is specified at a reference current (usually 500 A or 1 kA). Default parameters *k* and *α* given in the dialog box fit the average V–I characteristic provided by the main metal-oxide arrester manufacturers and they do not change with the protection voltage. The required protection voltage is obtained by adding discs of zinc oxide in series in each column.

This figure represents such a V–I characteristic.

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

Numbers 1, 2, and 3 identify the three segments (or the exponential functions defining the model). The letter *n* is the number of metal-oxide disc columns.

The transition currents from segment 1 to segment 2 and from segment 2 to segment 3 are equal to:

$$
i\_1 = P\_1 \left( \frac{P\_1}{P\_2} \right)^{\frac{\alpha\_1}{\alpha\_2 - \alpha\_1}} \\\[8pt]

i\_2 = P\_2 \left( \frac{P\_2}{P\_3} \right)^{\frac{\alpha\_2}{\alpha\_3 - \alpha\_2}} \\\[8pt]
$$

Where:

$$
P\_i = \frac{n I\_{\text{ref}}}{K\_i, \alpha\_i}, \quad i = 1,2,3.
$$

You may need to tune the parameters of the three segments to fit the V–I characteristic usually provided in the surge arrester datasheets.

## Parameters

<table data-header-hidden><thead><tr><th width="249.55560302734375"></th><th></th></tr></thead><tbody><tr><td><strong>Protection voltage Vref</strong></td><td>The protection voltage of the Surge Arrester block, in peak voltage (V). Default is 500e+03.</td></tr><tr><td><strong>Number of columns</strong></td><td>The number of metal-oxide disc columns. The minimum is one. Default is 2.</td></tr><tr><td><strong>Reference current per column Iref</strong></td><td>The reference current of one column used to specify the protection voltage, in peak amperes (A). Default is 500.</td></tr><tr><td><strong>Segment 1 characteristics</strong></td><td>The k and α parameters of segment 1. Default is [.955 50].</td></tr><tr><td><strong>Segment 2 characteristics</strong></td><td>The k and α parameters of segment 2. Default is [1.0 25].</td></tr><tr><td><strong>Segment 3 characteristics</strong></td><td>The k and α characteristics of segment 3. Default is [.9915 16.5].</td></tr><tr><td><strong>Measurements</strong></td><td><p>Select Branch voltage to measure the voltage across the Surge Arrester block terminals.</p><ul><li>Select Branch current to measure the current flowing through the Surge Arrester block.</li><li>Select Branch voltage and current to measure the surge arrester voltage and current.</li><li>Default is None.</li></ul></td></tr></tbody></table>

Place a Multimeter block in your model to display the selected measurements during the simulation. In the Available Measurements list box of the Multimeter block, the measurement is identified by a label followed by the block name.

| Measurement    | Label |
| -------------- | ----- |
| Branch voltage | Ub:   |
| Branch current | Ib:   |

### Advanced Tab

The **Advanced** tab of the block is not visible when you set the **Simulation type** parameter of the powergui block to `Continuous`, or when you select the **Automatically handle discrete solver** parameter of the powergui block. The tab is visible when you set the **Simulation type** parameter of the powergui block to `Discrete`, and when the **Automatically handle discrete solver** parameter of the powergui block is cleared.

**Break algebraic loop in discrete model**: When selected, a delay is inserted at the output of the model. This delay eliminates the algebraic loop resulting from trapezoidal discretization methods and speeds up the simulation of the model. However, this delay introduces a one simulation step time delay in the model and can cause numerical oscillations if the sample time is too large. The algebraic loop is required in most cases to get an accurate solution.

When cleared (default), the discretization method of the model is specified by the **Use robust solver in discrete model** parameter.

**Use robust solver in discrete model**: When cleared, Simulink® iterates to resolve the algebraic loop. Although this method produces correct results, it is not recommended because Simulink tends to slow down and may fail to converge (simulation stops) especially when the number of surge arresters is increased. Also, because of the Simulink algebraic loop constraint, this method cannot be used in real time. In R2018b and earlier releases, this method was used when the **Break Algebraic loop in discrete saturation model** parameter was cleared.

When selected, the robust solver iterates to resolve the algebraic loop. The maximum number of iterations is specified in the **Preferences** tab of the powergui block, in the Solver details for nonlinear elements section. For real time applications, you may need to limit the number of iterations. Usually, limiting the number of iterations to 2 produces acceptable results. The robust solver is the recommended method for discretizing the surge arrester model.

For more information on what method to use in your application, see [Simulate Discretized Electrical Systems.](https://www.opal-rt.com/docs/smart-power-simulation-software-sps/simulation-and-analysis/simulate-discretized-electrical-systems.md)

## Limitations

The Surge Arrester block is modeled as a current source driven by the voltage appearing across its terminals. Therefore, it cannot be connected in series with an inductor or another current source. As the Surge Arrester block is highly nonlinear, a stiff integrator algorithm must be used to simulate the circuit. de23t with default parameters usually gives the best simulation speed. For continuous simulation, in order to avoid an algebraic loop, the voltage applied to the nonlinear resistance is filtered by a first-order filter with a time constant of 0.01 microseconds. This very fast time constant does not significantly affect the result accuracy.

When you use the Surge Arrester block in a discrete system, see the **Advanced** tab.


---

# 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/power-transmission-and-distribution/surge-arrester.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.
