> 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/rt-lab/simulink-blocks-reference/artemis-library/25-synchronism-check-relay.md).

# 25 Synchronism check Relay

## Description

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-ff160bc788fcff05b631ad4f091353d85c34a8e0%2FArtemis_25_synch_check_relay_block.png?alt=media" alt="" width="143"><figcaption></figcaption></figure>

The **Sync-Check Relay** block, located in the **ARTEMiS/Tools/Protection Relays** library, models a generic ANSI 25 sync-check relay used to verify synchronism before closing a circuit breaker. It also includes a Voltage Check function to allow breaker closing on de-energized networks. The model supports 50 Hz and 60 Hz systems.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-5c41e25040455e20680aeff4188fda606f59e0f6%2FArtemis_25_synch_check_relay_schme.png?alt=media" alt="" width="258"><figcaption><p>Schematic for the relay operation</p></figcaption></figure>

{% hint style="danger" %}
In Voltage Check mode, the measured frequencies on both sides must not deviate from the rated frequency by more than ±5 Hz.
{% endhint %}

The relay verifies that bus and line frequency, voltage magnitude, and phase angle are within configured limits before permitting the breaker to close. It uses a three-phase phase-locked loop (PLL) to estimate bus and line frequencies, and it operates on the fundamental Phase A-to-ground voltage. A freezing time prevents maloperation at simulation start, and a breaker operation time can be applied to account for closing delay.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-597c69cbb59687446ca3bbc418ef8bc110a8257f%2FArtemis_25_synch_check_relay_schem_detail.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

### Live Bus and Live Line operation

The function will compare the values of the bus and line voltage with the set values for V<sub>Max</sub> which is a supervision to check whether both the bus and the line are live. : V<sub>Bus</sub> > V<sub>Max</sub> and V<sub>Line</sub> > V<sub>Max</sub>.

**1 - Static condition**

If |f<sub>Bus</sub> − f<sub>Line</sub>| ≤ 0.01 Hz, voltages are considered static.

If both |V<sub>Bus</sub> − V<sub>Line</sub>| < ΔV<sub>threshold</sub> and |φ<sub>Bus</sub> − φ<sub>Line</sub>| < Δφ<sub>threshold</sub> persist for the Ton delay (internally preset as 1 power cycle), the relay issues CloseCB. When voltages are static, the breaker operate time is not applied.

**2 - Slipping condition**

If |f<sub>Bus</sub> − f<sub>Line</sub>| > 0.01 Hz, voltages are slipping.

CB close command is not issued unless $$|f\_{Bus} − f\_{Line}| < Δf\_{threshold}$$ . When within $$Δf\_{threshold}$$, the relay evaluates the instant to close. There are two possibilities for the revolving phasors:

* Approaching phasors: $$CB \ closing \ angle \ (degrees) = −Δf × 360 × (Breaker \ close \ time)$$, where $$Δf = f\_{Bus} − f\_{Line}$$. If breaker delay = 0 s, the closing angle is 0 degrees.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-a14863c932f36ab9891e1163e79c5efcf2d61dd3%2FArtemis_25_synch_check_relay_CBclose.png?alt=media" alt="" width="281"><figcaption><p>CB closing in case when both the voltages<br>are slipping and are approaching each other</p></figcaption></figure>

* Parting phasors: CB close command will be issued at close in the range of :
  * $$\[ (-Δφ\_{threshold} −Δf × 360 × Breaker \ close \ time), (Δf × 360 × Breaker \ close \ time)] \ when \ Δf <0$$
  * $$\[ (−Δf × 360 × Breaker \ close \ time), (Δφ\_{threshold} - Δf × 360 × Breaker \ close \ time)] \ when \ Δf >0$$

    <figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-ae89852b62ce00f058e70d2f04d23a06c6e8e0c2%2FArtemis_25_synch_check_relay_CBclose_2voltages.png?alt=media" alt="" width="286"><figcaption><p>CB closing in case when both the voltages<br>are slipping and are parting from each other</p></figcaption></figure>

### Dead Bus and/or Dead Line (Voltage Check mode)

In addition to normal conditions where both line and bus voltages are within live limits, the Voltage Check mode of operation, when selected, also allows the closing of the CB when the following conditions are met:

* Dead Line Operation: V<sub>Line</sub> < V<sub>Min</sub>; bus voltage and frequency within programmed limits.
* Dead Bus Operation: V<sub>Bus</sub> < V<sub>Min</sub>; line voltage and frequency within programmed limits.
* Dead Bus and Dead Line Operation: V<sub>Bus</sub> < V<sub>Min</sub> and V<sub>Line</sub> < V<sub>Min</sub>.

{% hint style="danger" %}
This block requires a valid RT-LAB license on the simulator with the feature ARTEMiS enabled. Refer to[ ARTEMiS Requirements](https://www.opal-rt.com/docs/rt-lab/model-and-simulation/power-systems-with-artemis/artemis-requirements.md) for details.
{% endhint %}

## Mask parameters

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-052f889300472bc01f98612be9b7300c1b04fd6e%2FArtemis_25_synch_check_relay_mask.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

{% tabs %}
{% tab title="General parameters" %}

<table><thead><tr><th width="240.20001220703125">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Frequency</strong></td><td>System frequency in Hz. Supports 50 Hz and 60 Hz.</td></tr><tr><td><strong>Rated system voltage</strong></td><td>Line-to-line RMS voltage in V.</td></tr><tr><td><strong>Sample Time</strong></td><td>Model time step in s.</td></tr></tbody></table>
{% endtab %}

{% tab title="Settings" %}

<table><thead><tr><th width="240.20001220703125">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Enable</strong></td><td>Enable or disable relay operation.</td></tr><tr><td><strong>Voltage difference threshold</strong></td><td>Voltage difference limit for synchronizing, expressed as % of rated line-to-line voltage.</td></tr><tr><td><strong>Phase angle difference threshold</strong></td><td>Phase angle difference limit for synchronizing in degrees.</td></tr><tr><td><strong>Frequency difference threshold</strong></td><td>Frequency difference limit for synchronizing in Hz.</td></tr><tr><td><strong>Breaker close time</strong></td><td>Breaker closing time in s.</td></tr><tr><td><strong>Freeze time</strong></td><td>Initial time in s during which CloseCB remains 0 (breaker stays open).</td></tr><tr><td><strong>Voltage Check</strong></td><td>Enable or disable Voltage Check functionality.</td></tr><tr><td><strong>VMin</strong></td><td>Threshold voltage, as % of rated line-to-line voltage, below which bus/line is considered dead/non-energized.</td></tr><tr><td><strong>VMax</strong></td><td>Threshold voltage, as % of rated line-to-line voltage, above which bus/line is considered live/energized.</td></tr></tbody></table>
{% endtab %}
{% endtabs %}

## Conservating port

<table><thead><tr><th width="241.20001220703125">Input</th><th>Description</th></tr></thead><tbody><tr><td><strong>VBus</strong></td><td>Three-phase bus voltage input as a 3-element vector ordered Va, Vb, Vc.</td></tr><tr><td><strong>VLine</strong></td><td>Three-phase line voltage input as a 3-element vector ordered Va, Vb, Vc.</td></tr><tr><td><strong>Reset</strong></td><td>Relay reset signal. The relay resets when this signal is 1.</td></tr><tr><td><strong>CloseCB</strong></td><td>Circuit breaker close command. Default is 0. It becomes 1 when sync-check conditions are met and remain true for the Ton delay (internally preset as 1 power cycle).</td></tr></tbody></table>

## Inputs

This block has no inputs.

## Outputs

<table><thead><tr><th width="239.60003662109375">Output</th><th>Description</th></tr></thead><tbody><tr><td><strong>m</strong></td><td>Monitoring signals</td></tr></tbody></table>

<details>

<summary>m: available monitoring signals</summary>

<table><thead><tr><th width="125.20001220703125">Name</th><th>Description</th></tr></thead><tbody><tr><td><strong>dV</strong></td><td>Calculated magnitude difference of bus and line voltages (Phase A) in V.</td></tr><tr><td><strong>dPhi</strong></td><td>Calculated phase angle difference between bus and line (Phase A) in degrees.</td></tr><tr><td><strong>df</strong></td><td>Calculated frequency difference between bus and line in Hz.</td></tr></tbody></table>

</details>


---

# 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/rt-lab/simulink-blocks-reference/artemis-library/25-synchronism-check-relay.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.
