> 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/configure-ios/communication-protocol-ios/iec-61850-9-2-sv.md).

# IEC 61850-9-2 SV

## Introduction to IEC 61850‑9‑2 Sampled Values <a href="#introductiontoiec6185092sampledvalues" id="introductiontoiec6185092sampledvalues"></a>

IEC 61850 Sample Values (SV) provide a standardized mechanism for transmitting time‑critical, high‑frequency digitized current and voltage measurements across digital substations. They replace traditional copper wiring between instrument transformers and protection IEDs by streaming measurement data over an Ethernet process‑bus network. SV allows merging units (MUs) and other publishers to broadcast sampled analog values, typically at 80 samples/cycle or 256 samples/cycle, to multiple subscribing protection, control, and monitoring IEDs. Sample Values provide deterministic, multicast, real‑time measurement exchange suitable for protection functions requiring sub‑millisecond performance.

## Protocol characteristics <a href="#protocolcharacteristics" id="protocolcharacteristics"></a>

* **Multicast Publisher/Subscriber Architecture**\
  Sample Values use a one‑to‑many publisher/subscriber model. A Merging Unit or process‑level device publishes digitized currents and voltages as multicast Ethernet frames. Any number of IEDs can subscribe to these streams simultaneously. There is **no client/server communication**, and no request‑response pattern; SV is a continuous, unidirectional data stream.
* **Time‑Critical, Event‑Independent Streaming**\
  SV transmission is continuous and periodic, not triggered by events or requests. Measurements are published at fixed sampling rates (e.g., 4000 samples/second for 50 Hz at 80 samples/cycle). The data flow is constant regardless of system events, ensuring deterministic delivery for protection algorithms.
* **Data Model**\
  Sample Values carry digitized representations of primary system currents and voltages, encapsulating Logical Device identifiers, SV Control Block identifiers, sequence numbers, sample count (SmpCnt), timestamp information, and individual phase measurement values encoded as integers; the structure and encoding follow the standard mapping rules defined in IEC 61850‑9‑2, IEC 61850‑9‑2LE, or IEC 61850‑9‑2‑1 depending on the vendor’s implementation and selected interoperability profile.
* **SV Control Blocks & Datasets**\
  SV communication is governed by SV Control Blocks (SVCBs) that define which dataset of analog values is published and at what sampling rate. Datasets typically include the three‑phase currents and voltages (or three‑phase currents only in standalone MUs). SVCBs define MAC addresses, VLAN IDs, sampling configuration, and multicast behavior.
* **Transport Mechanism**\
  Sample Values are transmitted as **raw, connectionless multicast Ethernet frames** (layer‑2) using specific EtherType values (e.g., 0x88BA). They rely on time‑sensitive networking characteristics and VLANs to ensure deterministic delivery. Because no TCP/IP stack is used, latency remains extremely low and predictable.
* **Reliability & Responsiveness**\
  Reliability is achieved through deterministic Ethernet, redundant network paths such as PRP/HSR, and subscriber‑side validation using SmpCnt increments, synchronized timestamps, and sequence checks. Because Sample Values provide no acknowledgments or retransmissions, any missing frames must be detected and handled directly by the protection algorithms. Overall responsiveness is in the microsecond to sub‑millisecond range, making SV streams suitable for high‑speed protection and fast tripping applications.
* **Security Model (Protocol‑agnostic)**\
  IEC 61850 SV inherently provides no encryption or authentication, so security must be enforced through external mechanisms such as IEC 62351‑6 for process‑bus protection, network access controls, VLAN segregation with multicast filtering, and PRP/HSR redundancy for resilient communication; all security functions are implemented outside the SV protocol itself.

## How the protocol works <a href="#howtheprotocolworks" id="howtheprotocolworks"></a>

* **Dataset & SV Control Block configuration**\
  Engineering tools define SVCBs and datasets through SCL files that specify sampling rates, included data channels (such as IA, IB, IC, IN, VA, VB, VC, VN), VLAN tags, multicast MAC addresses, and synchronization or timing behavior; IEDs and Merging Units load these parameters at startup to determine how Sample Values will be generated and streamed.
* **Data access & subscription**\
  IEDs subscribe to SV streams by listening to the configured multicast MAC address and VLAN‑tagged Ethernet traffic. No requests are issued. Subscribers continuously decode incoming frames, validate SmpCnt and timestamps, and feed measurement values into protection algorithms and control logic.
* **SV generation**\
  The publisher, typically a Merging Unit, samples analog waveforms, digitizes them, and publishes the encoded values at fixed intervals, with each frame containing an incremented sample count, timestamp synchronization cues when applicable, and the dataset of measurement values; these frames are sent continuously and time‑aligned according to IEEE 1588‑2/PTP or IRIG‑B time sources to ensure deterministic, synchronized measurement streaming.
* **Reception & subscription**\
  Any IED configured for the corresponding multicast address receives the SV stream. Protection relays, bay controllers, and measuring devices process the frames in real time. Since communication is connectionless, subscribers may join or leave without affecting the publisher.
* **Application processing**\
  SV streams feed protection function algorithms (such as differential, distance, and overcurrent), phasor and RMS calculations, power quality computations, and even synchrophasor estimation in some implementations; IEDs depend on precise timing and deterministic sampling from these streams to perform fast tripping and execute protection logic reliably.

## Example applications <a href="#exampleapplications" id="exampleapplications"></a>

* **Real‑Time Protection**\
  Sample Values provide the continuous, time‑synchronized measurement data required for a wide range of protection functions, including differential protection across bays or transformers, distance protection for transmission lines, and high‑speed overcurrent or earth‑fault protection. Because SV streams deliver deterministic, low‑latency data, they are fundamental to modern process‑bus protection architectures where protection IEDs depend on precise, real‑time digitized currents and voltages to execute fast and reliable tripping decisions.
* **Merging Units & Digital Instrument Transformers**\
  By transmitting digitized currents and voltages over Ethernet rather than through traditional copper wiring, Sample Values enable the use of stand‑alone merging units, non‑conventional instrument transformers (NCITs), and other point‑on‑wave measurement devices. This digital interface simplifies installation, enhances safety by reducing high‑energy copper circuits, and supports flexible deployment of measurement equipment within the substation process level.
* **Process‑Bus Architectures**\
  Sample Values form the backbone of the digital substation process bus by providing a scalable and multicast‑based mechanism for distributing measurement data. A single SV stream can feed multiple IEDs simultaneously, allowing protection, control, and monitoring functions to share the same data source. This architecture dramatically reduces wiring complexity, minimizes installation costs, and enables more streamlined, modular substation designs.
* **Testing & Simulation**\
  Sample Values are also widely used in testing environments, where specialized test equipment publishes simulated SV streams to emulate real‑world primary system conditions. These simulated streams allow protection engineers to validate protection schemes, inject fault scenarios, verify configuration changes, and perform both commissioning and periodic maintenance testing without requiring direct physical access to primary equipment.
* **Monitoring & Analytics**\
  Beyond protection applications, SV streams support advanced monitoring and analytical functions. When combined with disturbance recorders, power quality analyzers, or waveform processing tools, SV data enables detailed power quality assessments, waveform capture, and disturbance analysis. This makes Sample Values a versatile data source not only for protection but also for long‑term asset monitoring and operational diagnostics.


---

# 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/configure-ios/communication-protocol-ios/iec-61850-9-2-sv.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.
