> 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/c37.118-slave.md).

# C37.118 Slave

## Introduction to C37.118 <a href="#whatisdnp3" id="whatisdnp3"></a>

**IEEE C37.118** is the standard protocol for **synchrophasor measurements** in electric power systems. It defines how phasor measurement units (**PMUs**) and phasor data concentrators (**PDCs**) exchange time‑synchronized data, such as **phasors**, **frequency**, and **ROCOF**, with precise timestamps for grid monitoring, protection, and wide‑area situational awareness. Communication is typically carried over **TCP or UDP** on IP networks, with continuous high‑rate data streaming from PMUs to masters (PDCs or applications).

## Protocol characteristics

* **PMU/PDC Architecture**\
  PMUs produce time‑synchronized measurement frames; a master (often a PDC or control application) subscribes to and aggregates streams from multiple PMUs.
* **Time‑Synchronized Measurements**\
  Each frame includes precise timestamps (e.g., aligned via GPS/IRIG‑B or PTP in the device), enabling coherent phasor aggregation across the grid.
* **Data Types**\
  Standardized payloads include **voltage/current phasors**, **frequency**, **ROCOF**, **status bits**, and **analog/digital channels**.
* **Frame Types & Configuration**\
  Devices exchange **Data**, **Configuration** (CFG‑1/CFG‑2/CFG‑3), and **Header** frames; **Command** frames control reporting rate, data format, and stream behavior.
* **Transport Options**\
  Supports **TCP** (reliable, ordered delivery) and **UDP** (lower latency; may be multicast in some deployments). Reporting rates commonly range from **10 to 60 frames per second** (and higher where supported).
* **Reliability & Latency Considerations**\
  The protocol itself provides sequence numbers and status to detect loss; reliability is typically ensured by TCP, while low‑latency needs may prefer UDP with network QoS.
* **Security Model (Protocol‑agnostic)**\
  C37.118 does not natively define encryption/authentication; deployments typically rely on **network segmentation, VPNs, firewalls**, or secure tunnels. (Security is handled outside the protocol.)

## How the protocol works

* **Configuration exchange**\
  The master retrieves **configuration frames** to learn channel counts, scaling, phasor formats (polar/rectangular), reporting rate, and time base.
* **Subscription/commands**\
  The master issues **command frames** to start/stop data, adjust reporting rate, or request headers/config updates.
* **Streaming data**\
  PMUs send **continuous data frames** with timestamps and sequence numbers over TCP or UDP. The master parses, validates, time‑aligns, and aggregates these streams.
* **Aggregation & forwarding**\
  A PDC (acting as master) aligns multi‑PMU data by timestamp and can forward consolidated streams to downstream applications or other PDCs.

## Example applications

* **Wide‑Area Monitoring Systems (WAMS)**\
  Real‑time visualization of grid dynamics using synchronized phasors, frequency, and ROCOF across multiple substations.
* **Oscillation & Disturbance Analysis**\
  Detect inter‑area oscillations, angle instability, and transient events using high‑rate time‑aligned data.
* **Model Validation & System Identification**\
  Validate dynamic models of generators and networks by comparing measured synchrophasors to simulation outputs.
* **Event Playback & Forensics**\
  Archive and replay synchronized data streams for post‑event analysis and compliance reporting.
* **Adaptive Protection & Control**\
  Use synchrophasors for faster, more accurate control actions (e.g., remedial action schemes) in advanced deployments.


---

# 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/c37.118-slave.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.
