A disturbance recorder is an automated data capture function embedded in a substation Intelligent Electronic Device (IED) that continuously samples voltage and current waveforms into a circular buffer. When a trigger condition—such as a protection trip, undervoltage threshold, or binary status change—is detected, the recorder freezes the buffer, storing pre-fault, fault, and post-fault data in the standardized COMTRADE (IEEE C37.111) format for offline analysis.
Glossary
Disturbance Recorder

What is a Disturbance Recorder?
A disturbance recorder is a specialized function within an Intelligent Electronic Device (IED) that captures high-resolution, time-synchronized analog and binary signal waveforms during power system anomalies for post-mortem analysis.
The recorded files contain time-stamped instantaneous values from instrument transformers and status changes from circuit breakers and relays, enabling protection engineers to perform precise fault location, verify protection scheme operation, and analyze transient stability events. Modern disturbance recorders leverage Precision Time Protocol (PTP) or GPS synchronization to align waveforms across multiple IEDs, creating a system-wide, microsecond-accurate view of a cascading grid disturbance.
Core Characteristics of a Disturbance Recorder
A disturbance recorder is not merely a data logger; it is a high-resolution forensic tool embedded within an Intelligent Electronic Device (IED) that captures the transient electrical signatures of power system faults for precise post-mortem analysis.
High-Resolution Waveform Capture
The primary function is the synchronous recording of analog current and voltage waveforms at high sampling rates, typically 1 kHz to 15 kHz. This granularity captures the high-frequency transient phenomena and DC offset decay that occur during the first few cycles of a fault, which are invisible to standard SCADA polling. The recorder stores pre-fault, fault, and post-fault data to provide a complete picture of the event evolution.
Binary Signal & Sequence of Events
Alongside analog data, the recorder captures the state changes of binary inputs and outputs with microsecond timestamp resolution. This includes:
- Protection element pickups and trips
- Circuit breaker auxiliary contacts (52a/52b)
- Communication-assisted trip signals (POTT, DTT) This creates a precise Sequence of Events (SOE) log, allowing engineers to verify that the protection scheme operated correctly and within its designed clearing time.
COMTRADE File Standardization
Disturbance recorders store data in the IEEE C37.111 (COMTRADE) format, a universal standard ensuring interoperability between different manufacturers' IEDs and analysis software. A COMTRADE record consists of:
- .CFG: Configuration file defining channel scaling and sampling rate
- .DAT: Binary or ASCII data file containing the sample values This standardization is critical for fault location calculations and protection coordination studies across a heterogeneous substation asset base.
Precision Time Synchronization
Accurate fault analysis requires all recordings across a substation or wide-area network to be aligned to a common time reference. Disturbance recorders utilize IRIG-B or IEEE 1588 (PTP) to timestamp samples with absolute time accuracy down to 1 microsecond. This allows engineers to overlay recordings from different bays to analyze traveling wave phenomena and precisely locate faults on transmission lines using double-ended methods.
Triggering & Auto-Recloser Integration
Recording is initiated by sophisticated triggers, not just a simple threshold crossing. Triggers include:
- Protection element start/trip signals
- Rate-of-change-of-frequency (ROCOF)
- Analog magnitude violation The recorder is tightly integrated with the auto-recloser logic, capturing the complete sequence of a transient fault, the dead time, and the subsequent successful or unsuccessful reclose attempt, which is vital for distinguishing transient from permanent faults.
Fault Location Calculation
Modern disturbance recorders perform embedded impedance-based fault location using the captured voltage and current phasors. By applying the Takagi algorithm or similar methods, the IED calculates the reactance to the fault point, compensating for load current and arc resistance. The result is a distance-to-fault estimate (e.g., 12.3 miles from the substation) that is appended to the event record, drastically reducing patrol time for line crews.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Frequently Asked Questions
Clear, technical answers to the most common questions about disturbance recorder functionality, COMTRADE file structure, and fault analysis workflows.
A disturbance recorder is a dedicated function within an Intelligent Electronic Device (IED) that continuously captures high-resolution analog and binary signal waveforms during power system anomalies. It operates as a circular buffer, constantly sampling voltage and current channels at rates typically between 1 kHz and 14.4 kHz. When a trigger condition is met—such as a protection element pickup, a binary input change, or an under/over voltage threshold—the recorder freezes a configurable window of pre-fault, fault, and post-fault data. This captured record is then time-stamped using a common time source like GPS or PTP and stored in non-volatile memory in the COMTRADE (Common Format for Transient Data Exchange) format, preserving the precise sequence of events for post-mortem analysis.
Related Terms
Key concepts and standards that interact with disturbance recorders to enable comprehensive power system fault analysis.
Fault Location Algorithms
Post-processing functions that use disturbance recorder data to calculate the physical distance to a fault on a transmission or distribution line. Common methods include:
- Impedance-based: Uses voltage and current phasors to compute reactance to the fault point
- Traveling wave: Measures the time difference between high-frequency wavefront reflections at line terminals Accurate fault location reduces patrol time and outage duration, directly improving SAIDI reliability metrics.
Time Synchronization
Disturbance recorders require sub-microsecond accuracy time-stamping to align waveforms captured at different substations. This is achieved through:
- GPS/GNSS receivers providing IRIG-B or 1PPS signals
- IEEE 1588 Precision Time Protocol (PTP) over the substation network Without precise synchronization, comparing the arrival time of traveling waves at line terminals for fault location becomes impossible.
Triggering Logic
The configurable conditions that cause a disturbance recorder to capture and store a waveform. Typical triggers include:
- Protection element pickup: When a distance or overcurrent element starts timing
- Breaker status change: Auxiliary contact transitions indicating open/close operations
- Analog threshold crossing: Voltage sag below 90% or current surge above a setpoint
- External binary input: A signal from another IED or manual trigger Pre-fault and post-fault recording durations are configurable to capture the complete event sequence.
Post-Mortem Analysis Software
Specialized tools used by protection engineers to visualize and analyze COMTRADE files. Capabilities include:
- Phasor calculation: Computing magnitude and angle from raw samples
- Symmetrical component decomposition: Extracting positive, negative, and zero-sequence quantities
- Impedance trajectory plotting: Visualizing the apparent impedance locus on R-X diagrams
- Harmonic analysis: FFT-based frequency spectrum for identifying transformer inrush or ferroresonance These tools validate whether protection schemes operated correctly and within design specifications.
Digital Fault Recorder (DFR)
A dedicated standalone device distinct from a disturbance recorder function embedded in a protection IED. DFRs typically offer:
- Higher sampling rates: Often 256+ samples per cycle for traveling wave capture
- More analog channels: Monitoring multiple feeders and bus voltages simultaneously
- Longer recording duration: Continuous recording with circular buffers
- Centralized substation monitoring: Aggregating data from multiple bays While functionally similar, DFRs serve as an independent, non-protection-grade monitoring layer for post-event analysis.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us