> 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/library-blocks-reference/network-tools/point-on-wave-synchronization.md).

# Point on Wave Synchronization

## Description

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

The **Point on wave synchronization (POW)** block, located in the **Network Tools** library, synchronizes data acquisition and timed operations such as programmable voltage sources or breakers. By default, it uses phase A at the bus where it is connected as the reference signal. All simulated networks must have a unique POW component. Because the synchronization signal is generated by a voltage threshold crossing, connect the POW component to a bus where no fault occurs.

When displaying the POW time sensor in Scopeview, the total circuit time since the start of the simulation is shown. This parameter defines how often the time value is updated in Scopeview.

Scopeview always displays time in seconds (the model unit). However, selecting **Time-Step** updates the display at every simulation step, resulting in a continuous ramp, whereas selecting **Seconds** produces stepwise increments in the graph.

Time value in Scopeview does not depend on the simulation Mode (real-time or non real-time).

$$
simulationStepNumber = \frac{POW\.Time}{simulationTimeStepDuration}
$$

Let the POW be connected to a 3-phase bus *WES7* and configured as follows:

| Parameter                        | Value       |
| -------------------------------- | ----------- |
| **Detection slope**              | Negative    |
| **Reference phase**              | B           |
| **Detection level**              | 200 kV      |
| **Duration of sensor 'SyncOut'** | 1 Time step |
| **Base unit for sensor 'Time'**  | TimeStep    |

{% hint style="info" %}
If Sync is not checked in ScopeView, POW is ignored, and 0.0 is the moment when the user requests the acquisition.
{% endhint %}

The simulation is done in RTA mode and acquisition requested around 3 seconds after starting the simulation.

0 is detected when phase *Reference phase* (B = WES7.Vb) crosses the *Detection level* (200 kV) with the *Detection slope* (Negative).

The acquisition was started at 18.195 seconds and finished at 'acquisition start time + time length'. With a simulation time step of 50 µs the values from step 363900 to 365900 are shown.

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

## Mask parameters

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

<table><thead><tr><th width="298.7999267578125">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Description</strong></td><td>Use this field to add all kinds of information about the component.</td></tr><tr><td><strong>Detection mode</strong></td><td>Use either the internal algorithm (with the analog signal at the connected bus) or an external signal (analog or digital).</td></tr><tr><td><strong>Detection mode - external</strong></td><td>When external is selected, use either the analog or digital signal at the A or P input pins.</td></tr><tr><td><strong>Detection slope</strong></td><td>Positive — The synchronization is done on the positive slope (rising part) of the reference signal.<br>Negative — The synchronization is done on the negative slope (falling part) of the signal.</td></tr><tr><td><strong>Reference phase</strong></td><td>Signal at the connected bus to use as reference (A, B or C).</td></tr><tr><td><strong>Detection level</strong></td><td>Value of the reference voltage at which the synchronization is triggered (kV).</td></tr><tr><td><strong>Duration of sensor pulse 'SyncOut'</strong></td><td>Whenever an acquisition is triggered and the condition is met, a pulse is output with the specified duration (time steps). If the time step = 50 us and the duration value is 10, then the output pulse duration will be 500 us.</td></tr><tr><td><strong>Time source</strong></td><td>Use only system time. <em>IRIG-B is for legacy</em>.</td></tr><tr><td><strong>Base unit for sensor 'Time'</strong></td><td>(Time steps, Seconds, Minutes, Hours)</td></tr><tr><td><strong>IRIG-B reader access speed</strong></td><td>Legacy</td></tr><tr><td><strong>IRIG-B reader number</strong></td><td>Legacy</td></tr></tbody></table>

## Conservating ports

<table><thead><tr><th width="200.4000244140625">Port</th><th>Description</th></tr></thead><tbody><tr><td><strong>Net_1</strong></td><td>Network connection (supports both 1-phase and 3-phase connections)</td></tr></tbody></table>

## Inputs

<table><thead><tr><th width="199.5999755859375">Input</th><th>Description</th></tr></thead><tbody><tr><td><strong>A</strong></td><td>Analog signal used for external synchronization.</td></tr><tr><td><strong>P</strong></td><td>Digital signal used for external synchronization.</td></tr><tr><td><strong>D</strong></td><td><strong>Delay:</strong> The value is sent directly to ScopeView to create an offset between signals, for example to synchronize an acquisition with another acquisition system where a delay between the systems is required to obtain waveforms at the same time.</td></tr></tbody></table>

## Outputs

This block has no outputs.

## Signals available for monitoring and external I/O connections (via sensors form) <a href="#signals-available-for-monitoring-and-external-i-o-connections-via-sensors-form" id="signals-available-for-monitoring-and-external-i-o-connections-via-sensors-form"></a>

All block inputs and outputs are available as signals for monitoring and for external I/O connections.

Additional signals are also available and are listed below with their descriptions.

<table><thead><tr><th width="240.4000244140625">Signal</th><th>Description</th></tr></thead><tbody><tr><td><strong>SyncOut</strong></td><td>Synchronization pulse triggered when conditions are met</td></tr><tr><td><strong>Time</strong></td><td>Time elapsed since the beginning of the simulation.</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/library-blocks-reference/network-tools/point-on-wave-synchronization.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.
