> 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/ehs/3.7/model-in-schematic-editor/library-blocks-reference/passive-blocks/surge-arrester.md).

# Surge Arrester

## Description

<figure><img src="https://521571437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fo99Izmvvw5eHT4ldzI4g%2Fuploads%2Fgit-blob-023e48075521708069732d2e0d68a4ca9ff6a6ec%2FSE_surgearester.png?alt=media" alt=""><figcaption></figcaption></figure>

The **Surge Arrester** block models a metal‑oxide varistor (MOV), commonly used to protect electrical equipment against overvoltages. The nonlinear MOV V‑I characteristic is approximated by a piecewise linear curve defined by up to 17 V‑I points, including the origin.

The model consists of a controlled current source in parallel with an RC snubber. The value of the generated current is determined by the voltage measured across it, which is then sent to a lookup table that has the V-I data points mentioned above.

<figure><img src="https://521571437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fo99Izmvvw5eHT4ldzI4g%2Fuploads%2Fgit-blob-5468812e4cffcb6813f16f81b15b00755dce1e85%2FSE_surgearester_modelcircuit.png?alt=media" alt="" width="311"><figcaption></figcaption></figure>

The Surge Arrester block includes a “**Current‑voltage characteristic**” parameter. When selected, you can specify a file containing the current‑voltage characteristics in the “Current voltage lookup table” field.

{% hint style="info" %}
This block is only available in the eHS library.
{% endhint %}

### Parameter constraints - **k and alpha parameters mode**

The calculation of those data points is based on the MOV protection voltage (V<sub>ref</sub>), the reference current (I<sub>ref</sub>) and the number of columns (metal-oxide discs of the MOV). Then three exponential segments of the curve are calculated with the parameters $$k$$ and $$\bold {\alpha}$$. The default values for the latter two parameters are chosen to fit the average V-I characteristics of MOV manufacturers. Therefore, based on the parameters listed here, 17 data points (including zero) are calculated with the following equations.

The V-I characteristic of the curve:

$$
\frac{V}{V\_{\mathrm{ref}}} = k\_i \left( \frac{I}{I\_{\mathrm{ref}}} \right)^{\frac{1}{\alpha\_i}},\ i = 1,2,3
$$

The current values at the transition points between segments 1 to 2 and 2 to 3:

$$
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]
P\_i = \frac{N\_c I\_{\mathrm{ref}}}{k\_i^{\alpha\_i}},\ i = 1,2,3
$$

where $$N\_c$$ is the number of columns.

By design, such 2 constraints apply :

* 𝛼<sub>1</sub> > 𝛼<sub>2</sub> > 𝛼<sub>3</sub>
* k<sub>1</sub> < k<sub>2</sub> > k<sub>3</sub>

### Parameter constraints - Current-voltage table mode

The following constraints applies the saturation characteristic:

$$
V \ge 0 \quad I \ge 0 \\\[8pt]
V\_{i+1} > V\_i ;\Longrightarrow; I\_{i+1} > I\_i\ \text{(strictly monotonically increasing)}
$$

where $$V$$is the voltage, and $$I$$ is the current.

Additionally, the number of elements of the array “currentBreakpoints“ shall be the same of “voltageValues“ and the number of points shall be less than or equal to 17.

By design, such constraints apply :

* A minimum of 3 points and a maximum of 17 points for the current breakpoints and voltage values.
* The same number of points for the current breakpoints and voltage values.
* The voltage values need to be monotonically increasing

## Parameters

<figure><img src="https://521571437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fo99Izmvvw5eHT4ldzI4g%2Fuploads%2Fgit-blob-5c71bb383dfea278e0950e433241277d40d4f2b2%2FSE_surgearester_param.png?alt=media" alt=""><figcaption></figcaption></figure>

| Parameter                           | Description                                                                                                                                                   | Sets feature | I/O & Monitoring |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ---------------- |
| **IVc**                             | The current voltage characteristics Two options: k and alpha parameters or Current-voltage table                                                              | No           | N/A              |
| **IV**<sub>**t**</sub>              | <p>if <strong>k and alpha parameters selected</strong><br>The current voltage IV lookup table file</p>                                                        | No           | N/A              |
| **V**<sub>**ref**</sub>\*\* (V)\*\* | <p>if <strong>k and alpha parameters selected</strong><br>The protection voltage of the Surge Arrester block, in peak volts (V)</p>                           | No           | N/A              |
| **N**<sub>**c**</sub>               | <p>if <strong>k and alpha parameters selected</strong><br>The number of metal-oxide disc columns; the minimum is one</p>                                      | No           | N/A              |
| **I**<sub>**ref**</sub>\*\* (A)\*\* | <p>if <strong>k and alpha parameters selected</strong><br>The reference current of one column used to specify the protection voltage, in peak amperes (A)</p> | No           | N/A              |

<details>

<summary><strong>How to specify IV parameters file?</strong></summary>

The current voltage parameters are described in a JSON format. The following parameters must appear in the file.

| Parameter (JSON key)   | Value type | Unit | Description                                                      | Example                                                                                                                         |
| ---------------------- | ---------- | ---- | ---------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| **currentBreakpoints** | double\[]  | A    | Current breakpoints of the Surge Arrester                        | <p>"currentBreakpoints":\[<br>0.0,<br>1.0e-3,<br>3.0e-3,<br>1.0e-2,<br>1.0e-1,<br>10.0,<br>200.0,<br>600.0<br>],</p>            |
| **voltageValues**      | double\[]  | V    | Voltage values for each current breakpoint of the Surge Arrester | <p>"voltageValues": \[<br>0.0,<br>426.4e3,<br>450.18e3,<br>455.92e3,<br>467.4e3,<br>501.84e3,<br>519.88e3,<br>527.26e3<br>]</p> |

All the examples above concatenated would give in a valid JSON format:

{% code overflow="wrap" lineNumbers="true" %}

```json
{
  "currentBreakpoints": [
    0.0,
    1.0e-3,
    3.0e-3,
    1.0e-2,
    1.0e-1,
    10.0,
    200.0,
    600.0
  ],
  "voltageValues": [
    0.0,
    426.4e3,
    450.18e3,
    455.92e3,
    467.4e3,
    501.84e3,
    519.88e3,
    527.26e3
  ]
}
```

{% endcode %}

</details>

### Segment 1 Characteristics (only if **k and alpha parameters selected)**

| Parameter              | Description                           | Sets feature | I/O & Monitoring |
| ---------------------- | ------------------------------------- | ------------ | ---------------- |
| **k**<sub>**1**</sub>  | k<sub>1</sub> value in the equations  | No           | N/A              |
| **𝛼**<sub>**1**</sub> | 𝛼<sub>1</sub> value in the equations | No           | N/A              |

### Segment 2 Characteristics (only if **k and alpha parameters selected)**

| Parameter              | Description                           | Sets feature | I/O & Monitoring |
| ---------------------- | ------------------------------------- | ------------ | ---------------- |
| **k**<sub>**2**</sub>  | k<sub>2</sub> value in the equations  | No           | N/A              |
| **𝛼**<sub>**2**</sub> | 𝛼<sub>2</sub> value in the equations | No           | N/A              |

### Segment 3 Characteristics (only if **k and alpha parameters selected)**

| Parameter              | Description                           | Sets feature | I/O & Monitoring |
| ---------------------- | ------------------------------------- | ------------ | ---------------- |
| **k**<sub>**3**</sub>  | k<sub>3</sub> value in the equations  | No           | N/A              |
| **𝛼**<sub>**3**</sub> | 𝛼<sub>3</sub> value in the equations | No           | N/A              |

### Snubber

| Parameter                                        | Description                              | Sets feature | I/O & Monitoring |
| ------------------------------------------------ | ---------------------------------------- | ------------ | ---------------- |
| **Snubber resistance (R**<sub>**sn**</sub>**)**  | Snubber resistance value in ohm (Ω).     | Yes          | N/A              |
| **Snubber capacitance (C**<sub>**sn**</sub>**)** | Snubber capacitance value in farads (F). | Yes          | N/A              |

## Conserving ports

| Port   | Description   |
| ------ | ------------- |
| **p1** | Positive port |
| **n1** | Negative port |


---

# 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/ehs/3.7/model-in-schematic-editor/library-blocks-reference/passive-blocks/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.
